docs: split five documents off the line cap #538

Merged

coilyco-ops merged 1 commit from eng/split-five-docs-off-the-cap into main

2026-08-13 15:28:31 +00:00

coilyco-ops commented

2026-08-13 15:27:47 +00:00

Member

closes #527

The remainder is filed as #537 rather than left implied, so this can close #527 honestly.

The measurement, re-taken today

Eighteen of 114 docs sat at exactly 80 lines. A corpus does not settle on an exact boundary by itself. That shape means people were writing to the limit and trimming to fit rather than splitting, so the cap was working as a tripwire and failing at its purpose, which is documents small enough to read.

It has already cost a red main once (#500): two branches each added a few lines to one capped file, each passed its own gate, and the merge summed them to 84. Every branch cut from main after that failed on a file its author had never opened.

What changed

Five files with a genuinely separable subject, split rather than trimmed:

parent	was	now	new file
`sirens-echo-tools`	80	62	`sirens-echo-issue-ownership`
`sirens-echo-prompt`	80	52	`sirens-echo-prompt-snapshots`
`sirens-echo-anomaly-evidence`	80	60	`sirens-echo-anomaly-worked-example`
`response-profiles`	80	69	`coilyco-deployment-gate`
`sirens-echo-jobs`	80	72	`sirens-echo-jobs-store`

Every parent keeps a sentence and a link where the section was, so a reader following the old path still arrives rather than finding a gap.

Split, not trimmed. No sentence was deleted to make room. Trimming to fit is the habit that produced the distribution in the first place.

What this does not do

Thirteen files remain at the cap. They have no clean seam — sirens-echo-identifiers is eight sections all answering one question — and forcing one would trade a size problem for a coherence problem that no hook measures, so it would look like progress.

The collision surface dropped 28 percent. The durable fix is checking the merge rather than the branch, which lives in the lane. Both are in #537.

ward exec gate green.

closes #527 The remainder is filed as #537 rather than left implied, so this can close #527 honestly. ## The measurement, re-taken today Eighteen of 114 docs sat at **exactly** 80 lines. A corpus does not settle on an exact boundary by itself. That shape means people were writing to the limit and trimming to fit rather than splitting, so the cap was working as a tripwire and failing at its purpose, which is documents small enough to read. It has already cost a red `main` once (https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/500): two branches each added a few lines to one capped file, each passed its own gate, and the merge summed them to 84. Every branch cut from `main` after that failed on a file its author had never opened. ## What changed Five files with a genuinely separable subject, split rather than trimmed: | parent | was | now | new file | |---|---|---|---| | `sirens-echo-tools` | 80 | 62 | `sirens-echo-issue-ownership` | | `sirens-echo-prompt` | 80 | 52 | `sirens-echo-prompt-snapshots` | | `sirens-echo-anomaly-evidence` | 80 | 60 | `sirens-echo-anomaly-worked-example` | | `response-profiles` | 80 | 69 | `coilyco-deployment-gate` | | `sirens-echo-jobs` | 80 | 72 | `sirens-echo-jobs-store` | Every parent keeps a sentence and a link where the section was, so a reader following the old path still arrives rather than finding a gap. **Split, not trimmed.** No sentence was deleted to make room. Trimming to fit is the habit that produced the distribution in the first place. ## What this does not do Thirteen files remain at the cap. They have no clean seam — `sirens-echo-identifiers` is eight sections all answering one question — and forcing one would trade a size problem for a coherence problem that no hook measures, so it would look like progress. The collision surface dropped 28 percent. The durable fix is checking the merge rather than the branch, which lives in the lane. Both are in #537. `ward exec gate` green.

coilyco-ops added 1 commit

2026-08-13 15:27:47 +00:00

docs: split five documents off the line cap

ci / image-build (pull_request) Successful in 18s

Details

ci / test (pull_request) Successful in 32s

Details

ci / publish-echo-image (pull_request) Has been skipped

Details

ci / publish-observed (pull_request) Has been skipped

Details

6a3a6a32ea

Eighteen of 114 docs sat at exactly 80 lines. A corpus does not settle on an
exact boundary by itself. That shape means people were writing to the limit and
trimming to fit rather than splitting, so the cap was working as a tripwire and
failing at its purpose, which is documents small enough to read.

It has already cost a red main once. Two branches each added a few lines to one
capped file, each passed its own gate, and the merge summed them to 84. Every
branch cut from main after that failed on a file its author had never opened.

Five files with a genuinely separable subject are split rather than trimmed:
issue ownership out of the tool loop, snapshots out of the rendered prompt, the
worked example out of the evidence order, the CoilyCo gate out of the profiles,
and the store and kinds out of the job record. Each parent keeps a sentence and
a link, so a reader following the old path still arrives.

Thirteen files remain at the cap. The rest have no clean seam and want either a
rewrite or the merge-time check, which is the durable fix and lives in the lane.

Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>

coilyco-ops requested review from coilysiren

2026-08-13 15:27:47 +00:00

coilyco-ops merged commit 3501c1089d into main

2026-08-13 15:28:31 +00:00

coilyco-ops referenced this pull request from a commit

2026-08-13 15:28:32 +00:00

Merge pull request 'docs: split five documents off the line cap' (#538) from eng/split-five-docs-off-the-cap into main