advance the aos documentation-layout pin so the per-file caps bind (post-#427), narrow the README exclude #500

New issue

Closed

opened 2026-07-02 02:45:45 +00:00 by coilysiren · 3 comments

coilysiren commented

2026-07-02 02:45:45 +00:00

Owner

Why

ward#427 authored the per-repo readme_max_lines / readme_max_chars opt-up upstream in agentic-os and reframed ward's blanket README.md pyproject exclude as an intentional launch exemption until the pin advances. Meanwhile ward still pins documentation-layout at the stale v0.65.0 flat 4000-char cap, and tonight's runs keep paying trim-tax on it: #487 dropped a FEATURES bullet to stay one char under, #488 had to concision-trim AGENTS.md and FEATURES.md after a single added link tipped both over. The #488 retro names this chronic pressure explicitly.

Deliverable

Bump the rev: pin in ward's .pre-commit-config.yaml to the aos release carrying the opt-up (released automatically off #427's aos push).
Set readme_max_* values that fit the landed launch-grade README, and narrow the blanket pyproject README exclude to that cap per #427's commit message.
Pay whatever trifecta reflow the new caps demand in the same commit.

Sequencing constraint

Dispatch only after the ward#444 README epic lands - the epic holds the one-agent lock on README.md and FEATURES.md front matter tonight, and cap values chosen before the epic's README exists would be guesses.

Cross-refs

ward#427 - the cap lift and upstream opt-up.
ward#488 / ward#487 - retros documenting the trim-tax.
ward#444 - the epic whose landed README sizes the new caps.

Filed by Claude Code (Fable) during the ward#492 burndown session.

## Why ward#427 authored the per-repo `readme_max_lines` / `readme_max_chars` opt-up upstream in agentic-os and reframed ward's blanket `README.md` pyproject exclude as an intentional launch exemption until the pin advances. Meanwhile ward still pins `documentation-layout` at the stale v0.65.0 flat 4000-char cap, and tonight's runs keep paying trim-tax on it: #487 dropped a FEATURES bullet to stay one char under, #488 had to concision-trim AGENTS.md and FEATURES.md after a single added link tipped both over. The #488 retro names this chronic pressure explicitly. ## Deliverable * Bump the `rev:` pin in ward's `.pre-commit-config.yaml` to the aos release carrying the opt-up (released automatically off #427's aos push). * Set `readme_max_*` values that fit the landed launch-grade README, and narrow the blanket pyproject README exclude to that cap per #427's commit message. * Pay whatever trifecta reflow the new caps demand in the same commit. ## Sequencing constraint Dispatch only after the ward#444 README epic lands - the epic holds the one-agent lock on README.md and FEATURES.md front matter tonight, and cap values chosen before the epic's README exists would be guesses. ## Cross-refs * ward#427 - the cap lift and upstream opt-up. * ward#488 / ward#487 - retros documenting the trim-tax. * ward#444 - the epic whose landed README sizes the new caps. Filed by Claude Code (Fable) during the ward#492 burndown session.

coilyco-ops commented

2026-07-02 03:11:29 +00:00

Member

🔒 Reserved by ward agent --driver claude — container engineer-claude-ward-500 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-02T03:11:27Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); --force overrides.

— Claude (she/her), via ward agent

🔒 Reserved by `ward agent --driver claude` — container `engineer-claude-ward-500` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-02T03:11:27Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); `--force` overrides.  — Claude (she/her), via `ward agent`

coilyco-ops commented

2026-07-02 04:30:45 +00:00

Member

🔒 Reserved by ward agent --driver codex — container engineer-codex-ward-500 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-02T04:30:44Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); --force overrides.

— Codex, via ward agent

🔒 Reserved by `ward agent --driver codex` — container `engineer-codex-ward-500` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-02T04:30:44Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); `--force` overrides.  — Codex, via `ward agent`

coilysiren referenced this issue from a commit

2026-07-02 04:33:39 +00:00

chore(pre-commit): advance documentation-layout pin

coilysiren closed this issue

2026-07-02 04:33:39 +00:00

coilysiren commented

2026-07-02 04:34:14 +00:00

Author

Owner

WARD-OUTCOME: done - advanced the agentic-os pin to v0.167.0 and tightened the README ceiling to the landed launch page size.

This was straightforward once I sized the live README and verified the hook release. The only oddity was that the repo already had the per-file cap scaffolding in place, so the real work was just aligning the pin and trimming the ceiling instead of reworking the policy. Confidence is high; the one thing I’d keep an eye on is whether the README keeps growing enough to need another cap bump soon.

WARD-OUTCOME: done - advanced the agentic-os pin to v0.167.0 and tightened the README ceiling to the landed launch page size. This was straightforward once I sized the live README and verified the hook release. The only oddity was that the repo already had the per-file cap scaffolding in place, so the real work was just aligning the pin and trimming the ceiling instead of reworking the policy. Confidence is high; the one thing I’d keep an eye on is whether the README keeps growing enough to need another cap bump soon.