baldart 4.68.0 → 4.68.1

package/CHANGELOG.md

@@ -5,6 +5,17 @@ All notable changes to BALDART will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [4.68.1] - 2026-06-24
+
+**`/design-system-init` now actually ACTIVATES the closed-set gate it just populated — found on the first real `mayo` upgrade run.** The v4.68.0 upgrade correctly derived + confirmed the closed-set data (the two-header `page-header` family + a `range-slider` pair landed in the component HEADs with `canonical_for`/`selection_closed: true`), but `baldart ds-gate` stayed `no-policy` and never enforced. Root cause: step 6's serializer bundle merged "deterministic (step 3) + agentic (step 4)" but NOT the step-4b/4c selection-policy fields, so `emitSelectionPolicy` ran over components without `canonical_for` and generated an EMPTY `INDEX.md § "Selection Policy"` block (the HEADs got the fields via a side path; the gate reads the INDEX block). Data present, gate dormant.
+
+**PATCH** — corrects the bootstrap write/verify flow; no schema/API change.
+
+### Fixed
+
+- **Selection-policy fields flow into the `--index` bundle** (`design-system-init/SKILL.md` step 6 + workflow step 5) — the serializer bundle MUST carry `canonical_for`/`use_when`/`selection_closed` for ALL components so `emitSelectionPolicy` generates the populated `INDEX.md § "Selection Policy"` block. Building the bundle from `extract-manifest` only / pre-4c agentic JSON leaves the block empty.
+- **New BLOCKING verification step 6b/5b** — when any closure was confirmed, the skill now asserts `INDEX.md` contains `## Selection Policy` AND `baldart ds-gate` no longer reports `no-policy` (the gate reads the COMMITTED baseline, so the INDEX block must be committed) before declaring the closed-set bootstrapped. Closes the "data in HEADs but gate dormant" gap that would otherwise ship silently.
+
 ## [4.68.0] - 2026-06-24
 
 **Closed-Set Selection Policy — the third semantic layer that makes the "third header" structurally impossible.** Found on real `mayo` PRDs: every PRD ignored the two existing canonical headers (`SectionHeader` depth-0, `DrilldownHeader` depth-1+) and wrote new ones, requiring an expensive consolidation epic (`FEAT-0045` + an ADR) and leaving `Header.tsx` deprecated-but-live in 3 call-sites. Root cause (confirmed by a BALDART trace + 40-source 2026 research): the registry has a token layer and a component layer, but **no layer asserts the *boundary* of a category** — so adding a third header violated no rule, only an undiscovered convention. The registry-first cascade was advisory at generation-time + reactive at review-time; nothing prevented the duplicate at build-time. The 2026 market confirms the gap: no vendor (Figma Code Connect, Storybook MCP, shadcn) hard-gates the reuse decision, and no deterministic tool detects a semantically-equivalent rewrite — but BALDART already ships the machine-readable manifest signature, so it is "one manifest-signature-diff away".

package/VERSION

@@ -1 +1 @@
-4.68.0
+4.68.1

package/framework/.claude/skills/design-system-init/SKILL.md

@@ -158,8 +158,17 @@ precedence caveats: `framework/agents/effort-protocol.md`.
    Reconciliation gate: auto where confident, ask where it is the user's call.
 5. **Bootstrap the DTCG token SSOT.** See § Token SSOT bootstrap below.
 6. **Write the files — DETERMINISTICALLY (the HEAD is NEVER model-authored).**
-   Merge the deterministic JSON (step 3) with the agentic JSON (step 4) per
-   component into a bundle and run the serializer:
+   Merge the deterministic JSON (step 3) with the agentic JSON (step 4) **and the
+   selection-policy fields from steps 4b/4c** (`canonical_for` / `use_when` /
+   `selection_closed`) per component into a bundle and run the serializer. The
+   bundle MUST carry the selection-policy fields — they are what
+   `emitSelectionPolicy` reads to GENERATE the `INDEX.md § "Selection Policy"`
+   block. Omitting them (e.g. building the bundle from `extract-manifest` only, or
+   from the pre-4c agentic JSON) writes the closed-set fields to the HEADs via a
+   side path but leaves the INDEX block EMPTY, so `baldart ds-gate` stays
+   `no-policy` and the gate never activates. On UPGRADE, the `--index` bundle MUST
+   include ALL components (not only the changed ones) so the regenerated router +
+   policy block are complete. Run the serializer:
    ```
    node .framework/framework/.claude/skills/design-system-init/scripts/serialize-spec.mjs \
      --bundle <bundle.json> --out-dir ${paths.design_system}/components \
@@ -186,6 +195,18 @@ precedence caveats: `framework/agents/effort-protocol.md`.
    - `tokens-reference.md` — **generated** human view of `.tokens.json` (or pure
      narrative). Not a third source of values.
    - `patterns/.gitkeep` — empty dir for future pattern docs.
+6b. **VERIFY the Selection Policy activated (BLOCKING when any closure was confirmed).**
+   If step 4c confirmed any `selection_closed: true`, then after the write:
+   - `grep -q '## Selection Policy' ${paths.design_system}/INDEX.md` MUST succeed —
+     the generated block lists the closed families. If it is ABSENT, the bundle
+     dropped the selection-policy fields (step 6): rebuild the `--index` bundle
+     INCLUDING `canonical_for`/`selection_closed` for ALL components and re-run.
+   - `npx baldart ds-gate --json` MUST NOT report `"reason":"no-policy"`. If it
+     still does, the committed INDEX lacks the block — the gate reads the COMMITTED
+     baseline, so the INDEX (with the policy block) must be committed for the gate
+     to enforce. Surface this in the next-steps so the user commits it.
+   Do NOT declare the closed-set bootstrapped until both pass — otherwise the data
+   is in the HEADs but the gate is dormant (the exact gap this check closes).
 7. **Update config.** Set `features.has_design_system: true`,
    `paths.design_system: <target>`, and (when tokens bootstrapped)
    `paths.design_tokens` + `design_tokens.outputs`. Use the same YAML write path
@@ -225,11 +246,19 @@ precedence caveats: `framework/agents/effort-protocol.md`.
 4. **Token SSOT bootstrap** — § Token SSOT bootstrap (derive `.tokens.json`,
    set outputs, `baldart tokens build`, round-trip verify).
 
-5. **Write files DETERMINISTICALLY** — merge deterministic+agentic field data per
-   component and run `scripts/serialize-spec.mjs` (emits valid-YAML HEADs +
-   thin INDEX router, self-validates, fails closed). Never hand-write the HEAD.
-   Then the generated tokens-reference + `patterns/.gitkeep`. UPGRADE salvages
-   agentic values from existing (even malformed) HEADs before re-serializing.
+5. **Write files DETERMINISTICALLY** — merge deterministic+agentic+selection-policy
+   field data per component (the bundle MUST carry `canonical_for`/`use_when`/
+   `selection_closed` so the serializer GENERATES the `INDEX.md § Selection Policy`
+   block) and run `scripts/serialize-spec.mjs --index` over ALL components (emits
+   valid-YAML HEADs + thin INDEX router + policy block, self-validates, fails
+   closed). Never hand-write the HEAD. Then the generated tokens-reference +
+   `patterns/.gitkeep`. UPGRADE salvages agentic values from existing (even
+   malformed) HEADs before re-serializing.
+
+5b. **Verify the Selection Policy activated** (§ What This Skill Does step 6b) —
+   when any closure was confirmed: `INDEX.md` MUST contain `## Selection Policy`
+   AND `baldart ds-gate` MUST NOT report `no-policy` (commit the INDEX — the gate
+   reads the committed baseline). Don't declare done until both pass.
 
 6. **Persist config** — `features.has_design_system: true`, `paths.design_system`,
    and (if tokens bootstrapped) `paths.design_tokens` + `design_tokens.outputs`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "baldart",
-  "version": "4.68.0",
+  "version": "4.68.1",
   "description": "Claude Agent Framework - Reusable framework for coordinating AI agents and humans in software projects",
   "bin": {
     "baldart": "./bin/baldart.js"