baldart 4.69.0 → 4.69.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.69.1] - 2026-06-24
+
+**`/prd` and `/new` now actually USE `/ds-new` when a new STANDARDIZED component is detected** (v4.69.0 only wired it as an opt-in arm + left `/new`'s spec production unspecified). A new canonical element should be materialized through the one discipline, not hand-rolled per surface.
+
+**PATCH** — wires the just-shipped skill into the two orchestrators; no new config key.
+
+### Changed
+
+- **`/prd` defaults to `/ds-new` create-now for a STANDARD** (`ui-design-phase.md`, NEW-governed branch) — when the user confirms a new component is `standard: yes` (canonical for its role, especially a `closed` family), `/prd` now invokes `/ds-new` to materialize the canonical element + its standardized spec + INDEX entry + Selection-Policy governance **before any card runs** (so `ds-gate` enforces it and every consumer reuses it), instead of scattering the governance lazily across `/new` cards. A genuine `scope: local` one-off stays bind-and-defer.
+- **`/new` produces a new primitive's spec via the serializer, following the `/ds-new` discipline** (`implement.md`, ui-expert Post-Intervention) — a NEW canonical/standardized primitive's `components/<Name>.md` HEAD is **emitted by `extract-one.mjs` → `serialize-spec.mjs`** (filling `framework/templates/component-spec.template.md`), **never hand-written** (the serialization contract), with `canonical_for`/`use_when`/`selection_closed` set per governance when it is a standard. Closes the gap where "ship the spec" let ui-expert hand-author an untemplated, possibly invalid-YAML HEAD. Propagates to `new2` automatically (shared reference modules).
+
 ## [4.69.0] - 2026-06-24
 
 **`/ds-new` — the fifth corner of the design-system discipline: guided creation of ONE canonical element + a canonical, ENFORCED doc template.** Discovery/reuse, prevention (`/prd`), enforcement (`ds-gate`), and bulk bootstrap (`/design-system-init`) all existed — but there was no user-invocable entry point to create a single new component or token *correctly* on-the-fly (research → create → document → register → govern → verify); `ui-expert` does it inside tasks, `/design-system-init` is bulk-only. Second gap the user named: the docs were **not standardized** — the rich prose template existed but was buried in `scripts/` and (critically) **not wired into the serializer** (`emitSpec` stubbed a one-liner on empty prose), so freshly-created specs were untemplated.

package/VERSION

@@ -1 +1 @@
-4.69.0
+4.69.1

package/framework/.claude/skills/new/references/implement.md

@@ -198,7 +198,18 @@
      introduced or modified. Drift code: `DS_INDEX_DRIFT`.
    - `${paths.design_system}/components/<Name>.md` — ship the per-component
      spec for any new primitive; update the spec when a primitive's API or
-     visual changes. Drift code: `DS_COMPONENT_STALE`.
+     visual changes. Drift code: `DS_COMPONENT_STALE`. **A NEW canonical/standardized
+     primitive follows the `/ds-new` create+document+govern discipline** (the
+     single-element procedure — `framework/.claude/skills/ds-new/SKILL.md`): the spec
+     HEAD is **emitted by the serializer** (`extract-one.mjs` → `serialize-spec.mjs`
+     with `--index`, which fills the canonical template
+     `framework/templates/component-spec.template.md`) — **never hand-write the HEAD or
+     the spec body** (the serialization contract in `agents/component-manifest-schema.md`).
+     If the new primitive is a standard for its role, set its `canonical_for` /
+     `use_when` / `selection_closed` per `design-system-protocol.md § Closed-Set
+     Selection Policy` (a closure is a governance decision — flag it, don't self-approve).
+     A genuinely surface-specific one-off (`scope: local`) may use a lighter spec, but
+     still tokens-compliant + INDEX-registered.
    - `${paths.design_system}/tokens-reference.md` — add / update token entries
      when introducing new semantic tokens. Drift code: `DS_TOKENS_DRIFT`.
 

package/framework/.claude/skills/prd/references/ui-design-phase.md

@@ -186,15 +186,25 @@ Before invoking `ui-design`:
      it from then on. A new standard for *all* views also opens a **migration
      follow-up card** for the existing views (never migrate them in this PRD).
 
-7. **Create now (OPT-IN) vs bind-and-defer (default).** For each `NEW (governed)`
-   element, the default is **bind-and-defer**: persist the binding (step 6) and let
-   `ui-expert` create the component at `/new` implement time. When the user wants it
-   materialized **now** (the canonical element + its standardized spec + INDEX entry
-   + governance, before any card runs), invoke **`/ds-new`** with the resolved tuple
-   (`NewComponent — role: family@context — standard:y/n — closed:y/n`); it skips its
-   own reuse step (already reconciled here) and runs from its create step. `/prd`
-   owns the *decision*; `/ds-new` executes the *creation* — no rule is duplicated.
-   This is additive: omit it and the default bind-and-defer path is unchanged.
+7. **Materialize the new element — routed by whether it is a STANDARD.** For each
+   `NEW (governed)` element:
+   - **Standardized / canonical** (the user confirmed it `standard: yes` — it becomes
+     the canonical answer for its role, especially a `closed` family): **default to
+     invoking `/ds-new` now** with the resolved tuple (`NewComponent — role:
+     family@context — standard:yes — closed:y/n`). `/ds-new` skips its own reuse step
+     (already reconciled here) and runs from its create step, materializing the
+     canonical element + its standardized (serializer-templated) spec + INDEX entry +
+     Selection-Policy governance BEFORE any card runs — so `ds-gate` enforces it from
+     then on and every consumer reuses it. Creating a *standard* lazily at implement
+     time scatters the governance decision across cards; do it once, here, with the
+     human in the loop.
+   - **Local one-off** (`scope: local`, surface-specific, not a standard): **bind-and-defer**
+     — persist the binding (step 6) and let `ui-expert` create it at `/new` implement
+     time (following the `/ds-new` create discipline per `implement.md`, but without
+     closed-set governance).
+   `/prd` owns the *decision* (standard vs one-off); `/ds-new` / `ui-expert` execute
+   the *creation* — no rule is duplicated. (Offline / non-interactive `/prd`: record
+   the `/ds-new` create-now intent for the standard so it is not silently deferred.)
 
 Pass the resolved inventory to `ui-design`:
 

package/package.json

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