docs: advance the hook pin and merge 29 split pages back together #149
No reviewers
Labels
No labels
burndown-2026-08
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/agent-proxy!149
Loading…
Reference in a new issue
No description provided.
Delete branch "aos/claude/docs-merge-to-cap"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
agent-proxy carried 69 docs against the large band's 40-doc cap. Not neglect: the pinned hook (
aos-precommit-v0.18.0) enforced a flat 80-line / 4000-char cap with no count cap, so long pages had to be split. Each stub said so in its own body, "split across the pages below to stay inside the documentation caps". The count cap that punishes the result landed later.The two rules were mutually unsatisfiable at the old pin. Merging produced pages over the 4000-char cap, splitting produced pages over the 40-doc cap. Advancing to
aos-precommit-v0.49.0raises per-file caps to 120 lines / 8000 chars and makes the merge legal. That advance surfaced exactly one finding across the whole suite: the doc count itself.Sixteen families merged, 69 docs to 40. No prose deleted, corpus is 162,160 chars against a 320,000 ceiling. Six sub-700-char stubs that existed only to index their own fragments are gone. 32 doc cross-links, 5 self-links left by the merges, and 2 source files carrying
docs/pointers repointed. Full suite green.Why this is a PR and not a push to main: the pin advance also brought
pr-guard, which refuses default-branch pushes unconditionally and does not read the repo's ward lane. agent-proxy declaresmerge-remote-main. Flagged in coilysiren/inbox#439 - advancing any repo to v0.49.0 silently converts its lane to PR-only.Refs: coilysiren/inbox#439