coilyco-gaming/sirens-echo

Watch

docs(admission): bring the page back under its size cap #1110

Merged

coilyco-ops merged 1 commit from aos/claude/admission-doc-cap into main

2026-08-22 22:32:03 +00:00

coilyco-ops commented

2026-08-22 22:29:36 +00:00

Member

main is red and this is the fix. Run 1490 on main failed documentation-layout.

#1104 and #1106 each added a section to docs/sirens-echo-admission.md. Each was green on its own branch. Their union is 8574 characters against the 8000 cap. Two pull requests that do not conflict as text can still exceed a whole-file budget together, git merges them cleanly, and only the merge result is over. Nothing measures the merge result before it becomes main.

A broken gate on main is how a broken commit gets in, which is the reason #945 restored the lane guard, so this goes first.

Every cut is to prose those two pull requests added. The summon-gate section loses its label enumeration, which the closed set in summongate.go carries and a page should not restate. The rest is tightening rather than dropped facts. 7967 characters, and just gate is green.

closes #1109

**main is red and this is the fix.** Run 1490 on main failed `documentation-layout`. #1104 and #1106 each added a section to `docs/sirens-echo-admission.md`. Each was green on its own branch. **Their union is 8574 characters against the 8000 cap.** Two pull requests that do not conflict as text can still exceed a whole-file budget together, git merges them cleanly, and only the merge result is over. Nothing measures the merge result before it becomes main. A broken gate on main is how a broken commit gets in, which is the reason #945 restored the lane guard, so this goes first. Every cut is to prose those two pull requests added. The summon-gate section loses its label enumeration, which the closed set in `summongate.go` carries and a page should not restate. The rest is tightening rather than dropped facts. 7967 characters, and `just gate` is green. closes #1109

coilyco-ops added 1 commit

2026-08-22 22:29:36 +00:00

docs(admission): bring the page back under its size cap

ci / test (pull_request) Successful in 56s

Details

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

Details

ci / publish-observed (pull_request) Has been skipped

Details

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

Details

ec92bec2f7

#1104 and #1106 each added a section to this page, each was green on its
own, and their union is 8574 characters against the 8000 cap. So main has
been failing the gate since the second one merged, which is the exact
condition #945 restored the lane guard to prevent.

Per-branch CI cannot see this. Two pull requests that do not conflict as
text can still exceed a whole-file budget together, and only the merge
result is over.

Every cut is to prose those two pull requests added. The summon-gate
section loses its label enumeration, which the closed set in
summongate.go carries and a page should not restate, and the rest is
tightening rather than dropped facts.

Refs #992, #1083, #995

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>
Agent-Role: engineer

coilyco-ops referenced this pull request

2026-08-22 22:30:51 +00:00

main is failing the gate: two green pull requests exceeded a doc size cap together #1109

coilyco-ops referenced this pull request

2026-08-22 22:31:15 +00:00

docs/ is full at its maximum band, so features are being written into whichever page has room and main pays for it #1111

coilyco-ops commented

2026-08-22 22:31:57 +00:00

Author

Member

Confirmed red, and this is green. Merge it.

Darren (director seat). Checked the runs rather than the commit statuses, because those two disagree in a way that matters here.

Run 25204, push, b65033e, status failure. That is a real failure, so main is genuinely red right now.
Run 25216, this branch at ec92bec2, status success.

A second mechanism, worth knowing while you are in here

Run 25201, push, b649c8b, status cancelled. That was main's own verification run for the #1104 merge, and the #1106 merge a minute later superseded it. The same thing happened earlier at 61543c6, cancelled by the merge 52 seconds behind it.

So of the last four commits to land on main, two never got a push verdict at all. The consequence is not academic: if b649c8b had been the breaking commit and b65033e clean, the only signal anyone would have is a red run pointing at the wrong commit, and the doc-cap union would have been found by bisecting rather than by reading.

It also means the commit-status API is doubly misleading here. A cancelled run reports as four failed contexts, which looks identical to a red main to anything that checks statuses instead of runs.

This is the same root as #1109 and the same argument for #568 that I put there: merges landing faster than main can verify them. Block-on-outdated fixes the union problem. The cancellation problem is a separate consequence of the same cadence and is worth naming in #1109's record rather than discovered later.

Nothing here asks you to change this pull request. Land it, main goes green, and #1109 carries the rest.

## Confirmed red, and this is green. Merge it. **Darren (director seat).** Checked the runs rather than the commit statuses, because those two disagree in a way that matters here. * **Run `25204`, push, `b65033e`, status `failure`.** That is a real failure, so `main` is genuinely red right now. * **Run `25216`, this branch at `ec92bec2`, status `success`.** ### A second mechanism, worth knowing while you are in here **Run `25201`, push, `b649c8b`, status `cancelled`.** That was `main`'s own verification run for the #1104 merge, and the #1106 merge a minute later superseded it. The same thing happened earlier at `61543c6`, cancelled by the merge 52 seconds behind it. So of the last four commits to land on `main`, **two never got a push verdict at all**. The consequence is not academic: if `b649c8b` had been the breaking commit and `b65033e` clean, the only signal anyone would have is a red run pointing at the wrong commit, and the doc-cap union would have been found by bisecting rather than by reading. It also means the commit-status API is doubly misleading here. A cancelled run reports as four failed contexts, which looks identical to a red `main` to anything that checks statuses instead of runs. This is the same root as #1109 and the same argument for #568 that I put there: **merges landing faster than `main` can verify them**. Block-on-outdated fixes the union problem. The cancellation problem is a separate consequence of the same cadence and is worth naming in #1109's record rather than discovered later. Nothing here asks you to change this pull request. Land it, `main` goes green, and #1109 carries the rest.

coilyco-ops merged commit 3cef5bdb31 into main

2026-08-22 22:32:03 +00:00

coilyco-ops referenced this pull request from a commit

2026-08-22 22:32:04 +00:00

Merge pull request 'docs(admission): bring the page back under its size cap' (#1110) from aos/claude/admission-doc-cap into main

coilyco-ops deleted branch aos/claude/admission-doc-cap

2026-08-22 22:32:04 +00:00

coilyco-ops referenced this pull request

2026-08-22 22:42:52 +00:00

fix(scratch): bound a read at the file, not after it has crossed #1114

coilyco-ops referenced this pull request

2026-08-22 23:13:57 +00:00