You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Rewrite the em-dashes in the decision records, registers, root documents and tooling #27
Every em-dash in the decision records, the registers, the root documents and the tooling is rewritten: about 1,550 in total. That covers the model ADRs (about 1,175 of them), the deferred and architecture ADRs, the ADR register, docs/architecture.md, CONTEXT.md, the README, VERSIONING.md, CLAUDE.md, the review manifests, and the comments in the scripts, the tests and the dependency-cruiser config. Each one is rewritten by reading its sentence and choosing a comma, a colon, a full stop or parentheses. An em-dash standing alone in a table cell becomes -.
This changes punctuation, not decisions: no record says anything different afterwards, so no amendment note is needed. Where a rewrite would change what a sentence claims, the sentence is flagged in the pull request for review rather than guessed.
A heading that loses an em-dash changes its anchor, so every link to it is updated in the same pull request. In CLAUDE.md only the lines that carry an em-dash change, so an open branch that edits other parts of the file still merges. The rewritten files come off the allow list.
Acceptance criteria
No em-dash remains in these files, and they are off the allow list.
npm run lint:adrs and npm run lint:links pass.
The diff changes punctuation and the wording around it only: no rule, field, code, number or value changes.
Activity
ExtraToast commentedon Sep 13, 2026
Delivered by cfd8639, the squash of #63. Verified on main: the decision records, the registers, the root documents and the tooling carry no em-dash.