records: merge four pairs into the lower number, then renumber #649

New issue

Open

opened 2026-09-29 15:17:26 +00:00 by hexajon · 1 comment

hexajon commented

2026-09-29 15:17:26 +00:00

Owner

What to change

Merge each pair into the lower number, and delete the higher record:

0031 into 0006. Both set the rule for writes to the default branch: 0006 for finish, 0031 for commit and the ahead-of-origin warning.
0033 into 0032. 0033 already restates every part of 0032 that still holds (0033 L69-71). 0032 takes the current decision, cheshirecube as the distribution home, and goes back to accepted.
0040 into 0023. 0040 applies the rule of 0023 to script headers, and adds no new principle.
0043 into 0019. The forge-write rule in 0019 (L235-250) is an older form of the scope rule in 0043.

Each kept record gets a title that covers the merged content.

Then renumber every record above each gap, so that the numbers run from 0001 with no gap, as MADR expects ("NNNN is a consecutive number"). In the same PR, rewrite every citation of a moved or deleted number: in records, docs, code comments, tests, and scripts/.

Acceptance

Each of the four pairs is one record.
The record numbers run from 0001 with no gap.
No file cites a deleted number, or an old number of a moved record.
adr check and ./scripts/gate.sh pass.

## What to change Merge each pair into the lower number, and delete the higher record: - 0031 into 0006. Both set the rule for writes to the default branch: 0006 for `finish`, 0031 for `commit` and the ahead-of-origin warning. - 0033 into 0032. 0033 already restates every part of 0032 that still holds (0033 L69-71). 0032 takes the current decision, cheshirecube as the distribution home, and goes back to `accepted`. - 0040 into 0023. 0040 applies the rule of 0023 to script headers, and adds no new principle. - 0043 into 0019. The forge-write rule in 0019 (L235-250) is an older form of the scope rule in 0043. Each kept record gets a title that covers the merged content. Then renumber every record above each gap, so that the numbers run from 0001 with no gap, as MADR expects ("`NNNN` is a consecutive number"). In the same PR, rewrite every citation of a moved or deleted number: in records, docs, code comments, tests, and `scripts/`. ## Acceptance - Each of the four pairs is one record. - The record numbers run from 0001 with no gap. - No file cites a deleted number, or an old number of a moved record. - `adr check` and `./scripts/gate.sh` pass.