Development record
After the release-gate manifest's derived values stop being stored (the chore/merge-hotspots branch, under review on 2026-10-15), the brief's 04-surfaces/README.md register is the main remaining line every surface-adding branch edits: its chapter table ends on the newest number and two of its rows are single-line inline lists of verbs, so two such branches conflict there. Measured on the ten surface-adding pull requests of 2026-09-24 to 2026-10-15: the table end in 8, the agents-and-hosts row in 5, the one-file-per-verb list in 5.
After the release-gate manifest's derived values stop being stored (the chore/merge-hotspots branch, under review on 2026-10-15), the brief's 04-surfaces/README.md register is the main remaining line every surface-adding branch edits: its chapter table ends on the newest number and two of its rows are single-line inline lists of verbs, so two such branches conflict there. Measured on the ten surface-adding pull requests of 2026-09-24 to 2026-10-15: the table end in 8, the agents-and-hosts row in 5, the one-file-per-verb list in 5.
Progress (2026-10-15)
The fix for iss-2608220150157511 (merged as #1024) generated one of the three lines this record measures: the one-file-per-verb list in 04-surfaces/README.md is now the commands region, written from the commands/ files by go generate ./internal/surface/cli, so it no longer conflicts. The chapter table and the agents-and-hosts row stay hand-kept, because their numbering, chapter mapping and "Serves" column are not derivable from the files; those two lines were 8 and 5 of the ten measured conflicts. The record's own remedy, one entry per line in a stable order, remains the fix for them.
Frontmatter
| id | iss-2610151050395768 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610151050395768-the-surfaces-register-is-the-last-shared.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2608220150157511Merge contention is structural in the shared registers, not the prose: append logs (.abcd/work/DECISIONS.md, 154 changes; the decomposition-calibration corpus, conflicted 2026-08-22) and the lint-gated indexes that index_drift forces every branch to co-edit (brief/06-delivery/03-out-of-scope.md drafts index, conflicted the same day; 04-surfaces/README.md; decisions/adrs/README.md; intents/README.md; release/surface.json). The fix shape for the indexes is already written down: the enumeration command in out-of-scope.md derives the list from the filesystem, so the committed copy could become generated-at-build and the lint compare against the derivation instead of a hand-edited region. Append logs tolerate union merges; the indexes do not