Split documentation-layout into placement and size hooks #1392
No reviewers
Labels
No labels
burndown-2026-06
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/agentic-os!1392
Loading…
Reference in a new issue
No description provided.
Delete branch "aos/claude/ee98-docsplit"
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?
A site repo's blog posts are Markdown, so the size caps reached them, and the only way out took the placement rules with it.
documentation-placementanddocumentation-sizenow ship as two hooks a repo enables independently. Verified end to end against a fixture repo with a 201-line post undersrc/pages/posts/:[tool.agentic-os.documentation-size] enabled = false- size passes, placement still failsexcludes = ["src/pages/**"]- both passThat last line is website's recipe, and it needs both halves.
Both read band and every cap from the one
documentation-layoutconfig section, so no consumer pyproject changes, andenabled = falsethere still disables both. Two regression tests cover each direction.DEFAULT_HOOK_IDSdeliberately still names the old id: the #187 ordering test requires a tagged release to carry a hook id before the generator may emit it. Pushing this to main cuts that release, and a follow-up bumps the pin and swaps the ids.Refs #1111