Split the oversized docs under the layout caps #99
No reviewers
Labels
No labels
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/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
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!99
Loading…
Reference in a new issue
No description provided.
Delete branch "doc-layout-caps"
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?
Closes #88.
Stacked on #98 (
exception-taxonomy) because that PR editsdocs/proxy.mdanddocs/FEATURES.md, both of which this restructures. Merge #98 first and this applies cleanly.With this, both catalog exemption lists are gone —
documentation-layouthere,code-commentsin #89 — so every tracked file in the repo is governed.The citation surface was measured, not assumed
The issue's main risk is that three of these documents are cited by path from outside this repository, and the
dead-cross-linkshook cannot see those. So before splitting anything I enumerated every*.md#anchorreference in the repo. Exactly four exist, all intoproxy.md:proxy.md#validation(×3, fromapp/resilience.pycomments)proxy.md#trace-correlation-metadataproxy.md#signoz-content-viewing-contract(fromREADME.md, and per the issue fromcoilyco-bridge/deploy)proxy.md#removed-the-self-verification-claim-checkAll four headings are kept in
proxy.mdas redirect stubs naming the page that now holds the content, so any link written before this change still resolves. Everything else is cited by filename only — and every original filename survives as a parent index page. Verified with a script that resolves each cited anchor against the actual headings.Shape of the split
Nine parents, split at boundaries the documents already had:
proxy.md(378L) needed the deepest split — request path, trace correlation, correlation fields, capture contract, SigNoz viewing, capture projections, validation, configuration,num_ctxderivation, operationstrajectory-contract-v1.mdkeeps its versioned filename with envelope, identity, taxonomy, model facts, and governance beneath it — the filename carries the version other services build against, so it does not movearchitecture-v2.md,FEATURES.md,ROADMAP.md,litellm-parity.md,reliability_baseline.md,route-registry.md,trajectory-retention.mdfollow the same parent-plus-children patternTwo passes were needed: several children were still over cap after the first split, so they split again at their H3 boundaries.
One thing the mechanical split got wrong
Documents that began at an H2 (
architecture-v2.mdstarts at## Charter) had no intro text, so the generated parent was a bare title plus a link list — technically compliant and useless to a reader. Each thin parent now has a short intro saying what it covers and where to start.architecture-v2.mdsays so explicitly, sinceAGENTS.mdnames it read-first.Verification
pre-commit run --all-files— every hook passes, includingdead-cross-linksanddocumentation-layoutpytest283 passed ·ruff·mypycleanWhat I could not verify
coilyco-bridge/deploycitesproxy.mdand its capture-contract section from outside this repo. The anchor is preserved, so those links should hold — but I could not check that repository from here. Worth a grep there before considering #88 fully closed out.