Correct the container padding variables: three directional vars, no isotropic or block form
Restore the Layer 3 design review and its form; the rubric still requires the form be archived
Delete the superseded hardening and auditor pages; repoint every link at the rubric
Reviewer role: run the rubric's checks instead of a stale copy with token names that do not exist
Component Auditor: fix the renamed Design Conventions table, the ledger link, and the tool that does not exist
Ledger: the write path is a hand edit — no score-ledger tool or scores page exists yet
Component auditor: one component a night, audit-fix-reaudit, ledger as the only state, no issues
Rubric: cite the page that owns each rule, not the auditor's deleted section numbers
Accessibility Checklist: give each of the ten items its own section so citations resolve
Wiki-wide: drop the mode-letter shorthand for plain language
Revert "scores: Badge F (30.0), rubric 1.2" This reverts commit 951596572abbf832878f4f3c8ecba12ae5c752af.
scores: Badge F (30.0), rubric 1.2
Ledger: serialize with node, not python — 48.0 vs 48 The previous pass round-tripped through a serializer that writes whole-number floats with a trailing .0, so the very next --record still showed a spurious change on SideNav's score. Written by the same JSON.stringify the tool uses, the file is now byte-identical to its output.
Ledger: normalize to the tool's own serialization, and describe the new shape The file was hand-formatted with compact section objects, so every --record reflowed all of it: a one-component write produced a 384-line diff and maximised the chance that two concurrent recordings conflict. Writing it once in exactly the form the tool emits makes each future record diff as one entry. `about` said the Component-Scores page is generated from this file. It is not; that page is gone. It now says what is actually true.
Ledger: the JSON is the only stored form; delete the generated table Component-Scores.md was a second copy of component-scores.json and went stale the moment the JSON changed without a regeneration. The ledger now has exactly one stored form (the JSON) and exactly one view (the sandbox page), which fetches it at runtime and can therefore never be out of date. Every page that linked [[Component Scores]] now links the sandbox page.
Rubric: lead with what you are doing; plain language; act as the hub for the rule pages
Reviewer role: set review depth by change type, pointing at the rubric
Ledger: nothing in CI reads it while the rubric is being calibrated
Document the ledger write path end to end
Mode R: set the bar by change type — bug fix, feature, new component (core vs lab)
Mode R: derive a small check set from the diff; depth follows the existing triage
Component Scores: regenerate the table
Component Scores: the audit ledger, its generated table, and the five calibration rows
T1: colour literals are legitimate when they demonstrate theming
Mode R: judge the diff on its merits; never charge a contributor for inherited debt
Audit loop: file an issue per BLOCK, link it from the ledger, re-audit on resolution
Auditor and rubric: recording the score in the ledger is part of every audit
Rubric: state the version explicitly, with a versioning rule and change history
Rubric: check role tokens and resolved scales, not literal pixel values