Registry-driven releases: one source of truth for tokens, components, and counts
Maintained by PointSav Digital Systems. Each revision is content-addressed by its commit hash.
- editorial(design-system): fix registry-driven-releases' standing 2026-08-02 flag (Track-B) — confirmed against app-privategit-design/src/tokens_gallery.rs's own source comments: the flag's 'served exclusively from primitive.json+pointsav-brand.json, never tokens.full.json' claim was itself backwards — those files are compiled INPUTS to tokens.full.json, which IS the served/compiled export, matching this article's original mechanism claim; only the leaf count was genuinely stale, now described as current-count-not-fixed rather than re-asserting a specific number that will drift again; de-narrated per register-documentation.yaml; same fix applied to the ES pair; register-clean EN+ES
- fix(index-group): backfill index_group across 11 categories migrated to Index Topic (330 files)
- fix(design-system): add dated Correction callouts to 12 of 15 design-system/ articles — fabricated --ps-* CSS variable family across 3 articles, stale token counts across 3 more, a shipped-then-removed MCP endpoint, and a WCAG AAA overclaim already corrected once in the real source; 3 verified clean
- content(design-system): commit 8 design-system TOPICs (EN+ES) cleared by technical review 2026-07-30 — component recipes vs raw tokens, design-tokens accessibility, Figma/Tokens Studio, MCP agent-consumable design systems, registry-driven releases, self-hosting, theming via semantic tokens, what a design token is; add design-system/_index.md MOC section + reciprocal cross-links; fix the resolved Button-recipe variant-count and tokens.json-redirect open questions in place