Cut every record's status line to one line, and keep one index by domain

[WaylandYang]

Problem

• Status lines had become change logs. Five records ran past 1,000 characters (0022, 0025, 0041, 0044, 0061), and every implementing PR appended a sentence.
• The README index repeated each status line, so a PR edited two places and conflicted there (Refresh the ontology vector index when the editor creates or relabels a class or property, before alignment runs #956 did).
• docs/design/README.md kept a third table of records that stopped at 0045.
• Status words were mixed: Implemented, implemented, Built, Decided, Cut 1, written.

Change

• Each record's status is one line: one of Proposed, Accepted, In progress, Implemented, Superseded by NNNN, then the date and PR, then open: and what is not built. The longest is 199 characters.
• Nothing is lost. Where the old line was long, it is kept verbatim at the end of the record under Status history (48 records).
• One index, in the decisions README, grouped by domain. It repeats only the status word and whether a later record overtook this one. The README went from 41.8 KB to 11.9 KB.
• The design README points at that index instead of keeping its own table.
• The convention is written down in the README: a status line is one line, and a PR touches the README only when the status word changes.

Not changed

No file is renamed, moved or renumbered, and no record's body changes. The roughly 1,200 references to record numbers in code comments and the links between records all still resolve.

Three statuses were brought up to date while rewriting them: 0054 (cut 1 landed in #884), 0062 (landed in #922) and 0063 (landed as #969).

Verification

A script checked every relative link in docs/decisions and docs/design. Two links in 0054 were already broken on dev (0001-extraction.md, 0022-a-fact-has-two-clocks.md) and are left for a separate fix.

🤖 Generated with Claude Code