There was an error while loading. Please reload this page.
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
Rubric: cite the convention pages instead of copying them The API contract preamble carried API Conventions by value, and the state representation catalogue restated Design Conventions row for row. Both now cite the owning page; the rubric keeps only the verification layer — which token signature must be visibly present in the screenshot for each matched row.
Add the auditor checks the rubric was missing Consolidation surfaced seven checks that lived only on an auditor page: hasAutoFocus/data-autofocus (P37), the escape-hatch and raw-element prop- interface contract (P38), the sanctioned non-token values (T2b), the raw-to- semantic type scale mapping (T21), the primitive-reuse test (T29), when a sub-element does not earn a target (T7), and public hook export registration (P17).
Publish the Component Audit Rubric Eleven weighted sections, four run modes, per-item verification class and severity, and the screenshot gate on rendered design judgment. Adapted from the source draft: cross-references converted to wiki links, the author-facing open-decisions section dropped, and the facts it asserts re-verified against main (VariantMap extensibility, the neutral gray token names, changeAction, story counts).