baldart 4.97.0 → 4.97.1

package/CHANGELOG.md

@@ -5,6 +5,15 @@ 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.97.1] - 2026-07-02
+
+**`/ds-new` + `/ds-edit`: locate/reuse-first is a deterministic registry lookup, never a search agent.** A live `/ds-edit` run went off-script — instead of the skill's deterministic spine (resolve the component spec → `ui-expert` source edit → `extract-one` → `serialize-spec` → `doc-reviewer` → `ds-gate`), the model improvised ad-hoc `general-purpose` agents to "find" the component and verify a formatter. Root cause: the skills said *what* to do ("resolve the existing component") but never forbade *how not to*. Reaffirmed (adversarially) that the v4.94.0 `codebase-architect` analysis profiles correctly do NOT belong in the `ds*` skills — those operate on a single, already-named element (no scope→registry fan-out), and `ds-new`'s reuse-first is a **deterministic signature detector** that an LLM `ui`-profile pass would only make fuzzier and duplicate; the `ui` profile lives in the *planning* skills (`/prd`, `/ui-design`, `/new`, `/ds-handoff`, `context-primer`) and, when it matters, already ran upstream before `/prd` delegates to `ds-new`/`ds-edit`.
+
+- **`ds-edit` P1** now states explicitly: read `components/<Name>.md` directly and take its `source` — a plain file resolution, **never** a `general-purpose` / `Explore` / `codebase-architect` spawn (grep the exported symbol if only the source path is uncertain). Skill `1.0.0 → 1.1.0`.
+- **`ds-new` step 1** now states explicitly: reuse-first stays the deterministic `ds-reuse-gate.js → signatureDuplicates` / `baldart ds-gate` detector, **never** routed through an LLM search/architect agent. Skill `1.0.0 → 1.1.0`.
+
+**PATCH** — skill-body clarification, no new surface, no install-layout change, no behavior change to the deterministic spine. **Codex parity: portable** — pure prose in the shared skill bodies (both skills already degrade `ui-expert`/`doc-reviewer` delegation to TODO on Codex; this hardening is runtime-agnostic). **Not a `baldart.config.yml` key** → the schema-change propagation rule does NOT apply.
+
 ## [4.97.0] - 2026-07-02
 
 **Change Tiers — a real Light lane, so ordinary edits stop triggering the heavy machinery.** The root primitives forced plan mode on *any* non-trivial task, a `plan-auditor` + `doc-reviewer` review gate on *every* non-trivial plan, mandatory delegation to a domain agent, and (amplified by project overlays) a worktree + backlog card whenever more than a few files were touched — so even a small direct edit spun up the full orchestration. Root cause: there were only two tiers (Trivial vs everything-else-is-Heavy); no genuine middle lane.

package/VERSION

@@ -1 +1 @@
-4.97.0
+4.97.1

package/framework/.claude/skills/ds-edit/CHANGELOG.md

@@ -2,6 +2,15 @@
 
 Formato: [Keep a Changelog](https://keepachangelog.com/) · [SemVer](https://semver.org/).
 
+## 1.1.0 — 2026-07-02
+
+- **P1 locate hardening.** Reso esplicito che lo step P1 è un lookup deterministico
+  diretto sul registro (`components/<Name>.md` → `source`) e che NON deve mai
+  spawnare un agente `general-purpose` / `Explore` / `codebase-architect` per
+  "trovare" il componente — l'unità è già nominata, non c'è fan-out da esplorare.
+  Chiude la deriva osservata in cui il modello improvvisava una ricerca ad-hoc al
+  posto dello spine deterministico della skill.
+
 ## 1.0.0 — 2026-07-01
 
 - Baseline: versioning per-skill introdotto al framework v4.82.0.

package/framework/.claude/skills/ds-edit/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: ds-edit
 effort: medium
-version: 1.0.0
+version: 1.1.0
 description: >
   Update ONE existing canonical design-system element correctly — the deliberate
   edit twin of /ds-new. Classifies the change (resync the spec to changed source /
@@ -81,9 +81,15 @@ the target component + intended variant are pre-resolved.
 ## Pre-flight
 
 - **P0 — gate.** `features.has_design_system: false` → REFUSE.
-- **P1 — locate.** Resolve the existing component (`${paths.design_system}/components/<Name>.md`
-  + its `source`). If it does NOT exist → STOP and suggest `/ds-new` (this skill
-  edits; it does not create).
+- **P1 — locate (deterministic registry lookup — NEVER a search agent).** Read
+  `${paths.design_system}/components/<Name>.md` **directly** and take its `source`
+  field — the registry IS the index, so this is a plain file resolution. Do **not**
+  spawn a `general-purpose` / `Explore` / `codebase-architect` agent to "find" the
+  component: `ds-edit` operates on a single, already-named element, so there is no
+  fan-out to explore (the `ui` analysis profile is for scope→registry discovery in the
+  *planning* skills, not here). If the spec does NOT exist → STOP and suggest `/ds-new`
+  (this skill edits; it does not create). If only the `source` path is uncertain,
+  `grep` the exported symbol — still no agent.
 - **P2 — classify the change** (the edit decision tree; ask the user when unclear):
   - **resync** — the source already changed (props/variants/a11y); only the spec
     needs to catch up. (Often you don't even need this skill — see "What this skill

package/framework/.claude/skills/ds-new/CHANGELOG.md

@@ -2,6 +2,15 @@
 
 Formato: [Keep a Changelog](https://keepachangelog.com/) · [SemVer](https://semver.org/).
 
+## 1.1.0 — 2026-07-02
+
+- **Reuse-first hardening.** Reso esplicito che lo step 1 reuse-first resta il
+  detector deterministico a firma (`ds-reuse-gate.js → signatureDuplicates` /
+  `baldart ds-gate`) e NON deve essere instradato attraverso un agente
+  `general-purpose` / `Explore` / `codebase-architect` (sostituirebbe il check a
+  firma con uno più fuzzy e duplicherebbe la Reuse Analysis che il profilo `ui`
+  possiede già nelle skill di planning). Simmetrico al P1 hardening di `ds-edit`.
+
 ## 1.0.0 — 2026-07-01
 
 - Baseline: versioning per-skill introdotto al framework v4.82.0.

package/framework/.claude/skills/ds-new/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: ds-new
 effort: medium
-version: 1.0.0
+version: 1.1.0
 description: >
   Create ONE canonical design-system element — a component OR a token — end to
   end with the full discipline: reuse-first research, (optional) scaffold, then
@@ -87,12 +87,16 @@ branch), the role/closure are pre-resolved — skip the reuse step (P1/step 1).
 
 Each step is a delegation. Read the cited SSOT; do not paraphrase it.
 
-1. **Reuse-first (BLOCKING).** Walk the Component Discovery Cascade AND query the
-   Selection Policy **by role** (`INDEX.md` § Selection Policy), per
-   `design-system-protocol.md`. Surface duplicates with the gate's own detector —
-   `node -e` over `src/utils/ds-reuse-gate.js → signatureDuplicates` (or `baldart
-   ds-gate` once a spec exists). Ask the user **only** on a real fork (a
-   suspected-duplicate, or a closed-family hit) — one consolidated
+1. **Reuse-first (BLOCKING — deterministic, NEVER a search agent).** Walk the
+   Component Discovery Cascade AND query the Selection Policy **by role**
+   (`INDEX.md` § Selection Policy), per `design-system-protocol.md`. The duplicate
+   check is the gate's own **deterministic detector** — `node -e` over
+   `src/utils/ds-reuse-gate.js → signatureDuplicates` (or `baldart ds-gate` once a
+   spec exists) — NOT an LLM pass: do **not** route reuse-first through a
+   `general-purpose` / `Explore` / `codebase-architect` agent (that would replace a
+   signature-based check with a fuzzier one and duplicate the Reuse Analysis the `ui`
+   profile already owns in the *planning* skills). Ask the user **only** on a real
+   fork (a suspected-duplicate, or a closed-family hit) — one consolidated
    `AskUserQuestion`. On a clean match → **STOP and reuse the existing component**
    (creating it anyway is the exact failure this skill prevents).
 2. **Create (conditional).** *Scaffold mode* → DELEGATE `ui-expert` (Task tool):

package/package.json

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