baldart 4.93.0 → 4.95.0

package/framework/.claude/skills/context-primer/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: cont
 effort: medium
-version: 1.0.0
+version: 1.1.0
 description: >
   Load codebase context silently before starting work, optimized for LLM
   comprehension using research-backed structured formatting.
@@ -56,72 +56,38 @@ precedence caveats: `framework/agents/effort-protocol.md`.
 
    Default to `query` if ambiguous.
 
+2b. **Map the task type to an analysis profile** (the mapping SSOT is
+   `framework/agents/analysis-profiles.md` § 3 — do not restate search strategy here):
+
+   | Task type | PROFILE |
+   |-----------|---------|
+   | `bug-fix` | `bug` |
+   | `refactor` | `impact` |
+   | `new-feature`, `query`, `doc-update` | `discovery` (pass the task type through — the profile has per-task-type deltas) |
+   | any type + UI/component/token keywords when `features.has_design_system: true` | `ui` |
+
 3. Launch `codebase-architect` agent with this prompt template:
 
 ```
 Load context about: {keywords}
 Task type: {task_type}
 
+PROFILE={profile} — resolve your analysis profile per `agents/analysis-profiles.md`
+(Grep `### PROFILE: {profile}`, Read ONLY that section + the shared blocks it cites).
+It defines your retrieval plan, what to skip, and your output blocks. Your system
+prompt's Investigation Protocol is the engine; the profile scopes it.
+
 OUTPUT=terse — you are a silent loader's machine consumer, not a human Q&A. Return the
-structured contract (reuse table + canonical evidence + `path:line — symbol` rows + `totals:`)
-with no narrative prose; the loader condenses this into the XML context block.
-
-TOKEN BUDGET: stay under 15K tokens total. Prefer the canonical router + targeted reads over broad file scans.
-
-SEARCH STRATEGY — canonical-router-first, verify-only-if-needed:
-
-1. Resolve the topic to its canonical source. Read `${paths.references_dir}/ssot-registry.md`
-   to route `{keywords}` to the owning reference doc / ADR, then read only the matched
-   section(s). If the topic is documentation-heavy and `features.has_wiki_overlay: true`,
-   also consult `${paths.wiki_dir}/index.md` and any must-include docs listed in
-   `.baldart/overlays/context-primer.md` (verify wiki claims against canonical docs).
-
-2. Targeted searches:
-   a. Agent memory: grep MEMORY.md index for topic match, read ONLY
-      matching files (skip files >20KB unless filename matches keywords).
-   b. Backlog (when `features.has_backlog: true`): grep `${paths.backlog_dir}/*.yml` for card titles matching keywords.
-      Read only the matching cards, not all cards.
-   c. Git: `git log --oneline -10 --grep="{keywords}"` (10 results max).
-
-3. Broader search (when steps 1-2 are thin):
-   a. Search for 2-3 specific identifiers from steps 1-2, routing by query shape
-      per `framework/agents/code-search-protocol.md` (symbols → LSP when
-      `has_lsp_layer`) and `framework/agents/code-graph-protocol.md` (structural /
-      relational → Graphify when `has_code_graph`); grep is the fallback for textual
-      patterns. Follow those modules' tier order, budgets, and anti-flail rule —
-      don't restate them here.
-   a-bis. **UI / component keywords when `has_design_system: true`**: route via the
-      design-system layer, NOT source scans — read `${paths.design_system}/INDEX.md`
-      (thin router) then the **frontmatter HEAD** of the matched
-      `components/<Name>.md` (props/variants/token_bindings; schema
-      `framework/agents/component-manifest-schema.md`). Read a spec's prose / the
-      source only to verify a runtime-sensitive claim. This is the cheap on-demand
-      path that replaces reading a monolithic INDEX or component sources.
-   b. Read key file headers (first 50 lines) to identify structure.
-   DO NOT read `${paths.prd_dir}/` or `${paths.references_dir}/` files in full —
-   route via the registry and read only the specific section you need.
-
-4. Targeted verification (ALL cases):
-   - Verify ONLY runtime-sensitive claims (auth patterns, API contracts,
-     current schema) against actual code.
-   - Files <200 lines: read in full.
-   - Files 200-500 lines: read first 50 lines + specific section.
-   - Files >500 lines: grep for key exports/functions, read only those.
-   - NEVER read agent memory files >20KB in full.
-
-TASK-ADAPTIVE RULES:
-- "query": canonical docs + memory only. Skip source code unless code-specific.
-- "bug-fix": canonical docs + recent git changes + error-related code. Skip arch docs.
-- "new-feature": canonical docs + patterns in same domain + ADRs. Skip unrelated areas.
-- "refactor": canonical docs + affected files + dependency refs. Skip design rationale.
-- "doc-update": SSOT registry. Skip source code.
-
-WIKI OVERLAY ROUTING:
-- If the topic is about synthesized knowledge, dashboards, reading guides, or
-  recurring documentation questions, prefer the derived wiki overlay as a
-  compression layer.
-- Always verify wiki claims against canonical repo docs before using them as
-  working truth.
+structured contract (the profile's blocks + canonical evidence + `path:line — symbol`
+rows + `totals:`) with no narrative prose; the loader condenses this into the XML
+context block.
+
+TOKEN BUDGET: stay under 15K tokens total (this caps the profile default).
+
+SKILL-SPECIFIC INPUTS (on top of the profile plan):
+- Must-include canonical docs listed in `.baldart/overlays/context-primer.md` (if the
+  overlay is present) — read their matched sections.
+- Recency signal: `git log --oneline -10 --grep="{keywords}"` (10 results max).
 
 Return output in this EXACT XML format (30-50 lines max):
 

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

@@ -2,6 +2,10 @@
 
 Formato: [Keep a Changelog](https://keepachangelog.com/) · [SemVer](https://semver.org/).
 
+## 1.2.0 — 2026-07-02
+
+- **Analysis-profile contract (framework v4.94.0)**: the standalone screen-resolution probe passes `PROFILE=ui` to `codebase-architect` per `framework/agents/analysis-profiles.md`. The Step 3 field-extraction retrieval order is unchanged.
+
 ## 1.1.0 — 2026-07-01
 
 - **Decision & preference pass (Step 5.5)** — nuovo `references/decision-pass.md`.

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

@@ -1,7 +1,7 @@
 ---
 name: ds-handoff
 effort: medium
-version: 1.1.0
+version: 1.2.0
 description: >
   Produce a FIELD-LEVEL, 1:1, interaction-complete handoff brief for Claude Design
   — every screen's real fields (label, control type, required, validation, default,
@@ -89,7 +89,8 @@ Each step is a delegation. Read the cited SSOT; do not paraphrase it.
    `mockup_analysis` from the `/prd` state file `## UI Design` (reuse the caller's
    collection — do NOT re-derive). *Standalone* → derive screens from the arg;
    on ambiguity, ONE `AskUserQuestion` listing route/page candidates from a
-   `codebase-architect` probe. Never proceed on silence.
+   `codebase-architect` probe (pass `PROFILE=ui` — `agents/analysis-profiles.md`).
+   Never proceed on silence.
 
 2. **Identify backing entities per screen.** Name the entity/entities each screen
    reads or writes. A screen may legitimately have **zero** entities (pure

package/framework/.claude/skills/e2e-review/CHANGELOG.md

@@ -2,6 +2,10 @@
 
 Formato: [Keep a Changelog](https://keepachangelog.com/) · [SemVer](https://semver.org/).
 
+## 1.3.0 — 2026-07-02
+
+- **Analysis-profile contract (framework v4.94.0)**: the two `codebase-architect` reverse-dependency lookups (routes importing a changed component; primitives used by a route in compliance-only mode) pass `PROFILE=impact` per `framework/agents/analysis-profiles.md`.
+
 ## 1.2.1 — 2026-07-02
 
 - Phase 3.8: la lane visual del route non renderizzabile con mockup code-form viene

package/framework/.claude/skills/e2e-review/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: e2e-review
 effort: medium
-version: 1.2.1
+version: 1.3.0
 description: >
   Deterministic, BLOCKING end-to-end review run after a feature is implemented.
   Combines functional E2E (Playwright spec written by `coder`, executed via
@@ -140,8 +140,9 @@ system constraints into a machine-readable verification plan.
      route, SvelteKit `routes/...` → route). If the framework is unknown,
      ask the user.
    - For each changed component under `${paths.components_primitives}`,
-     identify the routes that import it via the `codebase-architect` agent
-     (fallback to grep when LSP is unavailable).
+     identify the routes that import it via the `codebase-architect` agent —
+     pass `PROFILE=impact` (reverse-dependency lookup per
+     `agents/analysis-profiles.md`; fallback to grep when LSP is unavailable).
 3. **Synthesize verification plan** as Gherkin scenarios. Format:
 
    ```gherkin
@@ -260,7 +261,8 @@ If no mockup image is available BUT `features.has_design_system: true`:
   specs (cascade detailed in
   [`framework/agents/design-system-protocol.md`](../../../agents/design-system-protocol.md)).
 - Identify which primitives the route uses via the `codebase-architect`
-  agent (or grep on imports under `${paths.components_primitives}`).
+  agent with `PROFILE=impact` (or grep on imports under
+  `${paths.components_primitives}`).
 - Record `mockup_source.level = "compliance-only"` and the list of components
   in scope.
 

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

@@ -2,6 +2,10 @@
 
 Formato: [Keep a Changelog](https://keepachangelog.com/) · [SemVer](https://semver.org/).
 
+## 1.4.0 — 2026-07-02
+
+- **Analysis-profile contract (framework v4.94.0)**: `implement.md` Phase 1 step 3 now passes a deterministic `PROFILE=` token to the `codebase-architect` spawn — `ui` when the card has a non-empty `links.design`/`links.design_src` (the same mockup bit as step 6a), else `feature`. Contract SSOT: `framework/agents/analysis-profiles.md`; guarded by the `check-new-parity.mjs` tripwire.
+
 ## 1.3.0 — 2026-07-02
 
 - **Hot-file economy (T2.A)**: il briefing "Codebase Context" passa il baseline

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

@@ -1,7 +1,7 @@
 ---
 name: new
 effort: medium
-version: 1.3.0
+version: 1.4.0
 description: >
   Orchestrate a team of specialized agents to implement one or more backlog cards
   end-to-end inside a dedicated worktree, with code review, doc review, QA, and

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

@@ -54,6 +54,15 @@ Before triggering any review, you MUST verify that the coder agent implemented *
    index of WHERE to look; you still verify independently (do NOT trust its `status` alone), just
    without pulling entire files inline.
 
+   **4b. Per-AC executable oracles (`ac_verification` — EXECUTE, don't judge).** When the card
+   carries an `ac_verification` map (card-schema.md § "Acceptance-criteria grammar (EARS) +
+   per-AC oracles"), an AC whose oracle is NOT `manual:` is verified by **running the command**
+   — the exit status is the PRIMARY evidence for that row (`Done` on expected exit, `Missing/
+   Partial` otherwise, with the command + exit code in the Evidence column). Reading-based
+   judgment then covers only `manual:` oracles, oracle-less ACs, and the non-AC requirement
+   rows. A failing oracle is never argued around: either the implementation is incomplete
+   (gap-fixer path) or the oracle itself is stale — surface which, never silently reclassify.
+
    **Verification depth per requirement type:**
    - **"Create endpoint/route"** → verify: route file exists, handler has correct HTTP method,
      request validation present, response shape matches requirement, auth middleware applied.

package/framework/.claude/skills/new/references/final-review.md

@@ -211,7 +211,8 @@ that is a **gate violation**: log it as
      Log `f.2-arch: reused N per-card baselines (no re-spawn)` in the tracker. This avoids the N+1
      architect invocations the per-card persistence was designed to prevent.
    - **Any missing** (a card was added late, or a baseline was purged) → invoke **codebase-architect**
-     ONCE over the batch scope to map existing architecture, critical patterns, and high-risk code
+     ONCE over the batch scope — pass `PROFILE=baseline OUTPUT=terse` (`agents/analysis-profiles.md`) —
+     to map existing architecture, critical patterns, and high-risk code
      paths for regression. Persist its output to `/tmp/arch-baseline-batch-<FIRST-CARD-ID>.md` and set
      `${ARCH_BASELINE_PATHS}` to that single path. Log `f.2-arch: re-spawned (missing baselines: <list>)`. Do NOT spawn
      the architect more than once for the batch — it is the single grounding context for all

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

@@ -10,7 +10,7 @@
    - If `DONE` (or the user chose "proceed anyway") → continue.
 2b. **Claim** — only now set the card status to `IN_PROGRESS` (in the backlog YAML / tracker) and assign yourself. This is a state write, not a visibility emission — do not also spend a TaskUpdate / Progress-Bar turn (§ "State surface — the tracker only").
 2c. **Trivial-card classification (BLOCKING gate for steps 3–4)** — evaluate `IS_TRIVIAL(card)` per § "Trivial-card fast-lane". Note: condition 3 (non-source diff) cannot be fully evaluated until the coder has produced the diff, so at this point compute the **provisional** trivial flag from conditions 1+2 only (`review_profile == skip` AND no Step-A trigger sourced from the card YAML text + `files_likely_touched` extensions — if EVERY path in `files_likely_touched` is non-source, condition 3 is provisionally satisfied). If provisionally trivial → **SKIP steps 3, 3a, and 4** (architecture grounding); log `trivial: architecture grounding skipped (review_profile=skip + non-source files_likely_touched + 0 triggers)` and jump to Phase 2. Re-confirm `IS_TRIVIAL` on the ACTUAL committed diff at the review gates (Phase 2.55/3.5/3.7); if the coder unexpectedly touched a source file, the guard flips the card back onto the normal review path there. If NOT provisionally trivial → run steps 3, 3a, 4 as normal.
-3. **(skip when provisionally trivial — see 2c)** Invoke the **codebase-architect** agent (MUST per AGENTS.md) to understand the relevant codebase area, existing patterns, and architecture before any implementation. When `features.has_lsp_layer: true`, the architect uses LSP find-references for identifier-shaped lookups — this needs NO handoff from the orchestrator: the architect reads `features.has_lsp_layer` from `baldart.config.yml` directly (the flag is ambient) per `agents/code-search-protocol.md`. Likewise, when `features.has_code_graph: true`, the architect uses the Graphify code graph for structural/relational lookups (ambient flag) per `agents/code-graph-protocol.md`. The orchestrator does NOT propagate either flag. (Earlier doc versions numbered this step 4; the step that read project-status BEFORE the architect was removed because it persisted pre-analysis context — see step 3a.) **Pass `OUTPUT=terse` in the architect prompt (since v4.49.0)** — this is grounding for the coder/reviewer, not an explanation, so the architect returns its structured contract (reuse table + canonical evidence + `path:line — symbol` rows + `totals:`) without narrative prose. The verbatim baseline persisted at step 5b keeps all the substance a lean `/codexreview` needs (paths, signatures, patterns, high-risk paths) while staying small in the orchestrator's context and on disk. **Baseline content contract (MANDATORY — since v4.56.0):** the architect prompt is grounding INPUT only — pass the card scope, `files_likely_touched`, and the question to map. NEVER put line-level fix directives ("remove lines 90-91", "Fix: use X"), the words "implement/fix/apply", or acceptance-criteria framed as a task into the architect prompt. The architect produces a read-only MAP (file/symbol locations, patterns, type signatures, integration points, high-risk paths); it does NOT implement and has no `Task`/Agent tool to delegate (see `codebase-architect.md` § Role boundary). The coder is a separate spawn the orchestrator owns.
+3. **(skip when provisionally trivial — see 2c)** Invoke the **codebase-architect** agent (MUST per AGENTS.md) to understand the relevant codebase area, existing patterns, and architecture before any implementation. When `features.has_lsp_layer: true`, the architect uses LSP find-references for identifier-shaped lookups — this needs NO handoff from the orchestrator: the architect reads `features.has_lsp_layer` from `baldart.config.yml` directly (the flag is ambient) per `agents/code-search-protocol.md`. Likewise, when `features.has_code_graph: true`, the architect uses the Graphify code graph for structural/relational lookups (ambient flag) per `agents/code-graph-protocol.md`. The orchestrator does NOT propagate either flag. (Earlier doc versions numbered this step 4; the step that read project-status BEFORE the architect was removed because it persisted pre-analysis context — see step 3a.) **Pass `OUTPUT=terse` in the architect prompt (since v4.49.0)** — this is grounding for the coder/reviewer, not an explanation, so the architect returns its structured contract (reuse table + canonical evidence + `path:line — symbol` rows + `totals:`) without narrative prose. **Pass the analysis profile too (since v4.94.0)**: `PROFILE=ui` when the card has a non-empty `links.design` OR `links.design_src` (the same mockup bit that drives step 6a), else `PROFILE=feature` — contract and per-profile scoping in `agents/analysis-profiles.md` (its § 3 caller routing table is normative). The profile is deterministic from the card YAML; never leave the architect to infer it. The verbatim baseline persisted at step 5b keeps all the substance a lean `/codexreview` needs (paths, signatures, patterns, high-risk paths) while staying small in the orchestrator's context and on disk. **Baseline content contract (MANDATORY — since v4.56.0):** the architect prompt is grounding INPUT only — pass the card scope, `files_likely_touched`, and the question to map. NEVER put line-level fix directives ("remove lines 90-91", "Fix: use X"), the words "implement/fix/apply", or acceptance-criteria framed as a task into the architect prompt. The architect produces a read-only MAP (file/symbol locations, patterns, type signatures, integration points, high-risk paths); it does NOT implement and has no `Task`/Agent tool to delegate (see `codebase-architect.md` § Role boundary). The coder is a separate spawn the orchestrator owns.
 3a. Update `${paths.references_dir}/project-status.md` Active Code Context (skip when the file does not exist in the project) — do this AFTER the codebase-architect run (step 3) so the "Active Code Context" reflects the architect's findings (which files are actually in scope), not just the card YAML's `files_likely_touched`. Writing it before the architect run would persist pre-analysis claims that downstream agents (e.g. a parallel card) would then read as truth.
 4. **Plan-auditor grounding check** — but first, a **provenance skip (since v4.7.0 — mirror of Step 3d)**: the `/prd` Step 6.6 holistic audit already ran a per-card grounding pass when the card was authored. Re-grounding here is only worth a plan-auditor spawn if something changed since. **This skip is the NORMAL path for a card implemented right after `/prd`, not an occasional optimization** — `/prd` now guarantees the `metadata.holistic_audit` stamp lands on every audited card (deterministic backstop at `validation-phase.md` Step 7 item 5b, since the v4.88.2 provenance-reliability fix), so P1 below holds whenever the batch is freshly authored. Skip the plan-auditor when **BOTH** hold:
    - **P1 — provenance present**: the card has `metadata.holistic_audit` with non-empty `audited_at`, `audited_commit`, `audited_set`.

package/framework/.claude/skills/new2/CHANGELOG.md

@@ -2,6 +2,10 @@
 
 Formato: [Keep a Changelog](https://keepachangelog.com/) · [SemVer](https://semver.org/).
 
+## 1.3.0 — 2026-07-02
+
+- **Analysis-profile contract (framework v4.94.0)**: the B7 per-card architect spawn in `new2.js` passes `PROFILE=${hasMockup ? 'ui' : 'feature'}` (deterministic from the pre-flight cardGraph bit) mirroring `/new` implement.md step 3; the SSOT is `framework/agents/analysis-profiles.md`. Tripwire rule added to `check-new-parity.mjs`.
+
 ## 1.2.1 — 2026-07-02
 
 Review avversariale post-release (3 lenti indipendenti, finding verificati):

package/framework/.claude/skills/new2/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: new2
 effort: high
-version: 1.2.1
+version: 1.3.0
 description: >
   Workflow-hosted batch engine for /new. Implements one or
   more backlog cards end-to-end by delegating the WHOLE batch to a background

package/framework/.claude/skills/prd/CHANGELOG.md

@@ -2,6 +2,21 @@
 
 Formato: [Keep a Changelog](https://keepachangelog.com/) · [SemVer](https://semver.org/).
 
+## 1.3.0 — 2026-07-02
+
+- **Analysis-profile contract (framework v4.94.0)**: the discovery-loop targeted architect question now passes `PROFILE=discovery`, and the Step 2 ISA scan passes `PROFILE=impact` (structural tier primary) — per `framework/agents/analysis-profiles.md`. Prompt semantics otherwise unchanged.
+
+## 1.3.0 — 2026-07-02
+
+**Applier economico + pacchetto EARS+verify** — i due interventi strutturali dal forensics (48% del costo nelle fasi meccaniche; gate-prosa aggirabili):
+
+- **`MODE: apply-findings` su `prd-card-writer`** (un agente + token, pattern analysis-profiles — mai un twin): l'apply dei finding di audit esce dall'orchestratore (che non edita più YAML). L'applier riceve tutto BY PATH, applica solo campi `[Target:]`, grounding obbligatorio (path/comandi verificati, mai inventati), marca `[MANUAL]` senza decidere, ESEGUE validator `--prd` + stamper, ritorna compact. `audit-phase.md` Step 6.9 = delega thin + drift guard `git diff --stat` + fallback inline visibile. Field-mapping/severity/audit-trail SPOSTATE nel corpo agente. Testato con spawn reale su fixture.
+- **Grammatica EARS sugli AC child/standalone** (SSOT: `card-schema.md` § "Acceptance-criteria grammar"): 5 pattern (`THE SYSTEM SHALL` / `WHEN` / `WHILE` / `WHERE` / `IF…THEN`) + `SHALL CONTINUE TO`; keyword inglesi, corpo nella lingua del progetto; ban-list verbi vaghi. BLOCKER nel validator `--prd` — le card legacy non sono mai retro-bloccate (il baseline check di `/new` non applica EARS). AC-EPIC esenti.
+- **`ac_verification`** (mappa opzionale `AC-N → oracolo eseguibile` o `manual:`): authoring groundato (comando scritto solo se verificato esistente — classe Field Grounding Rule), consumo in `/new` Phase 2.5 che ESEGUE gli oracoli non-manual (exit status = evidenza primaria; `qa-sentinel` deliberatamente NON è il consumer — AC verification fuori dal suo contratto). Enforcement WARN-first (hard-gate solo dopo telemetria). Cross-check drift con `validation_commands`.
+- Validator: canale warnings separato (mai exit 1 da un WARN); fixtures EARS nel self-test CI (`check-card-baseline.js` Check D).
+
+Codex parity: portable (token in prosa agente → transpile TOML; script zero-dep; prosa condivisa).
+
 ## 1.2.0 — 2026-07-02
 
 **Gate-hygiene wave** — dai driver misurati sul forensics di una sessione /prd reale (61.6M token; 48% del costo in fasi meccaniche a piena finestra; una famiglia di card spedita con zero audit-trail; ~20 righe di progress bar × 30+ messaggi):

package/framework/.claude/skills/prd/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: prd
 effort: high
-version: 1.2.0
+version: 1.3.0
 description: "Structured PRD creation skill. Use when the user says /prd, 'crea un prd', 'nuova funzionalita', 'pianifica feature', or wants to plan a new feature end-to-end. Also handles /prd-add, 'aggiungi requisito', 'serve anche', 'manca un endpoint' for change requests on active PRD sessions — runs ICIAS impact analysis to determine which phases need SKIP/PATCH/REDO. Produces PRD + UI design + backlog cards, all validated and committed. Multi-turn conversation: asks questions, waits for answers, iterates through discovery, design, spec writing, card creation, and validation phases."
 ---
 

package/framework/.claude/skills/prd/assets/card-template.yml

@@ -85,8 +85,12 @@ existing_patterns:
 anti_patterns:
   - "DO NOT {{specific prohibited action — be concrete, not generic}}"
 
+# EARS grammar (card-schema.md § "Acceptance-criteria grammar"): the clause matches one of
+# THE SYSTEM SHALL … / WHEN … THE SYSTEM SHALL … / WHILE … / WHERE … / IF … THEN THE SYSTEM SHALL …
+# Body in the project language, EARS keywords in English. No vague verbs (banned by the validator).
 acceptance_criteria:
-  - "[ ] [AC-1] {{Testable criterion}}"
+  - "[ ] [AC-1] WHEN {{trigger}} THE SYSTEM SHALL {{observable behavior}}"
+  - "[ ] [AC-2] IF {{error condition}} THEN THE SYSTEM SHALL {{recovery behavior}}"
 
 # --- Validation Commands (OPTIONAL — include for cards with testable outputs) ---
 # Executable commands the agent runs for self-verification after implementation.
@@ -98,6 +102,14 @@ validation_commands:
     expect: "exit 0"
   - cmd: "{{verification command, e.g. grep -c 'pattern' src/file.tsx}}"
     expect: "{{expected: 'exit 0', '>= N', 'contains X', '== N'}}"
+
+# --- Per-AC oracles (OPTIONAL map — card-schema.md § ac_verification) ---
+# One entry per AC: an EXECUTABLE command verified to exist (npm script / toolchain command /
+# existing test file) — never invented — or an explicit "manual: <what a human checks>".
+# /new Phase 2.5 EXECUTES non-manual oracles; exit status is the primary AC evidence.
+ac_verification:
+  AC-1: "{{command verified to exist, e.g. npm run test -- --grep '{{feature}}'}}"
+  AC-2: "manual: {{what a human checks}}"
     note: "{{what this verifies — maps to AC-N}}"
 
 definition_of_done:

package/framework/.claude/skills/prd/references/audit-phase.md

@@ -165,7 +165,7 @@ INVEST criteria violations:
 - Valuable: card does not deliver user-visible or system-critical value
 - Estimable: scope unclear, cannot estimate effort
 - Small: card too large for one dev session
-- Testable: acceptance criteria not binary pass/fail
+- Testable: acceptance criteria not binary pass/fail (the EARS grammar in card-schema.md § "Acceptance-criteria grammar" is the norm — a clause outside the 5 EARS patterns is a finding)
 
 Requirements smell detection:
 - Ambiguous pronouns without clear antecedent
@@ -199,7 +199,7 @@ Card structure:
   files_likely_touched — flag any unowned consumer (the "hidden-still-shown-in-the-other-mode" class).
 - areas field incomplete
 - git_strategy set to TBD
-- acceptance_criteria not binary testable
+- acceptance_criteria not EARS-conformant (5 patterns, card-schema.md) or not binary testable
 - definition_of_done missing items
 - existing_patterns with stale line_range or missing anchor_text
 - validation_commands missing for cards with testable outputs
@@ -337,48 +337,42 @@ Present the consolidated report to the user.
 
 Use `SendMessage` with `type: "shutdown_request"` to shut down all teammates, then `TeamDelete`.
 
-## Step 6.9 — Apply Findings to Cards
-
-**Goal**: Transform each card from "audited" to "implementation-ready" by editing YAML fields directly.
-
-**Read findings from the persisted report file** (path stored in the session tracker as `$REPORT_FILE`; pattern: `/tmp/check-audit-report-<CARD-ID-SLUG>-<SESSION-ID>.md`).
-
-### Field mapping rules
-
-| Target tag | Card field | Action |
-|---|---|---|
-| `[Target: requirements]` | `requirements` | Append missing requirement or rewrite existing one |
-| `[Target: acceptance_criteria]` | `acceptance_criteria` | Append new `"[ ] [AC-N] ..."` item or rewrite vague AC |
-| `[Target: definition_of_done]` | `definition_of_done` | Append new `"[ ] ..."` item |
-| `[Target: files_likely_touched]` | `files_likely_touched` | Append missing path (no duplicates) |
-| `[Target: depends_on]` | `depends_on` | Append missing card ID |
-| `[Target: areas]` | `areas` | Add missing area key/value |
-| `[Target: git_strategy]` | `git_strategy` | Replace `TBD` with `feat/<CARD-ID>-<slug> from ${git.trunk_branch}` |
-| `[Target: unknowns]` | `unknowns` | Append new `[U-N] UNKNOWN: ...` entry |
-| `[Target: existing_patterns]` | `existing_patterns` | Append missing pattern reference or fix stale line_range/anchor_text |
-| `[Target: validation_commands]` | `validation_commands` | Append missing verification command |
-| `[Target: anti_patterns]` | `anti_patterns` | Append missing DO NOT constraint |
-| `[Target: scope_boundaries]` | `scope_boundaries` | Add missing in_scope or out_of_scope item |
-| `[Target: input_output_examples]` | `input_output_examples` | Append missing scenario or fix incorrect example |
-| `[Target: error_handling]` | `error_handling` | Append missing failure mode or fix incorrect action |
-| `[Target: reuse_analysis]` | `reuse_analysis` | Add missing reuse opportunity or correct file path |
-| `[Target: notes]` | `notes` | Audit trail only (Step 6.9c) |
-
-### Severity policy
-
-- **HIGH**: MUST apply. Card cannot be safely implemented without these.
-- **MEDIUM**: SHOULD apply. Skip only if human judgment needed (mark `[MANUAL]`).
-- **LOW**: Do NOT edit structured fields. Audit trail note only.
-
-### Audit trail in `notes`
-
-After applying all edits, append to `notes`:
-
-```yaml
-## Applied by quality audit — YYYY-MM-DD
-Applied N findings to structured fields (H high, M medium).
-Manual review needed: [list [MANUAL] items, or "none"].
-```
+## Step 6.9 — Apply Findings to Cards (DELEGATED — the orchestrator does not edit YAML)
+
+**Goal**: transform each card from "audited" to "implementation-ready". The mechanical apply
+is DELEGATED to `prd-card-writer` in **MODE: apply-findings** — its § "MODE: apply-findings"
+is the SSOT for the field mapping, severity policy, audit trail, self-validation and stamp
+execution; do NOT restate or re-execute them here. (Measured driver: the inline apply ran
+~48 Edits at full context window — the mechanical phases were 48% of a real run's cost.)
+
+1. Capture the three run-level stamp values ONCE (snippet in § "Holistic-audit provenance
+   stamp" below) and read `$REPORT_FILE` **as a path only** from the session tracker
+   (pattern: `/tmp/check-audit-report-<CARD-ID-SLUG>-<SESSION-ID>.md`) — do not load it.
+2. Spawn ONE `prd-card-writer` subagent — Claude: Task tool, `subagent_type: prd-card-writer`,
+   `model: sonnet` override, `mode: "bypassPermissions"`; Codex: spawn by name from
+   `.codex/agents/` (inherits the session model). THIN prompt, paths only:
+
+   ```
+   MODE: apply-findings
+   REPORT_FILE: <path>
+   CARD_PATHS: <newline-separated card paths>
+   AUDITED_AT: <ts>   AUDITED_COMMIT: <sha-or-empty>   AUDITED_SET: <ID1,ID2,...>
+   VALIDATOR: .framework/framework/scripts/validate-card-baseline.js
+   STAMPER: .framework/framework/scripts/stamp-holistic-audit.js
+   ```
+   (Resolve the two script paths for this install — same base as the validation-phase 0-i
+   gate.)
+3. Consume the COMPACT return (`APPLY-FINDINGS DONE` block):
+   - any card `validator: FAIL` → HALT and surface the validator output verbatim;
+   - route each `[MANUAL]` item to `AskUserQuestion` (they legally survive to
+     validation-phase Step 7 item 1);
+   - **drift guard (zero-cost)**: run `git diff --stat -- "${paths.backlog_dir}"` — the
+     touched files MUST be ⊆ CARD_PATHS; anything else → HALT (the applier edited outside
+     its mandate). Never re-read the card bodies to "double-check" — the validator already
+     did.
+4. **Fallback (delegate-or-else-inline, visible never silent)**: if the spawn is impossible
+   in this install, apply inline following the agent's § "MODE: apply-findings" and log
+   "apply-findings: INLINE FALLBACK (<reason>)" in the audit log.
 
 ### Holistic-audit provenance stamp (since v4.3.0) — consumed by `/new` Step 3d
 
@@ -420,13 +414,10 @@ Hand-edit the YAML only when the script is genuinely unreachable in this install
 
 ### Per-card workflow
 
-For each card:
-1. Read persisted report → collect all findings for this card ID.
-2. Read current card YAML.
-3. Apply HIGH findings first, then MEDIUM, then write audit trail.
-4. Write the `metadata.holistic_audit` provenance block (see "Holistic-audit provenance stamp" above) — **by EXECUTING `stamp-holistic-audit.js` once for the whole card set** (after the last card's field edits), not by hand-editing YAML. **MANDATORY when the audit ran** (see the Fail-safe contract above) — this is what lets `/new`/`new2` skip the per-card plan-auditor when the card is implemented right after `/prd`; `validation-phase.md` Step 7 item 5b deterministically backstops it, but do not rely on the backstop.
-5. Write updated card YAML.
-6. Re-read to verify edits landed correctly.
+The per-card loop (read findings → edit targeted fields → audit trail → validate → stamp)
+is OWNED by `prd-card-writer` § "MODE: apply-findings" (Step 6.9). The stamper runs ONCE for
+the whole card set inside the applier; `validation-phase.md` Step 7 item 5b remains the
+deterministic backstop.
 
 **Note**: No separate commit here — the validation-phase.md Step 7 handles committing all PRD artifacts together.
 

package/framework/.claude/skills/prd/references/discovery-phase.md

@@ -698,7 +698,9 @@ section of the state file. Mark dimension as covered.
    If more specific detail is needed beyond what context-primer provided,
    invoke `codebase-architect` agent (foreground) with a targeted question:
    ```
-   OUTPUT=terse — machine consumer (discovery dimension resolution), not human Q&A.
+   PROFILE=discovery OUTPUT=terse — machine consumer (discovery dimension resolution),
+   not human Q&A. Resolve your analysis profile per `agents/analysis-profiles.md`
+   (Grep "### PROFILE: discovery", read only that section).
    For feature `<slug>`: regarding the dimension `<dimension>`, does the codebase
    already answer this? Specifically check: existing collections, routes, components,
    permissions, and patterns. Report what you find with file references — structured
@@ -780,8 +782,10 @@ Instead, run the ISA scan and present findings for validation.
 1. Invoke `codebase-architect` agent with this specific prompt:
 
    ```
-   OUTPUT=terse — machine consumer (ISA table builder), not human Q&A: per-touchpoint
-   rows only, no narrative overview.
+   PROFILE=impact OUTPUT=terse — machine consumer (ISA table builder), not human Q&A:
+   per-touchpoint rows only, no narrative overview. Resolve your analysis profile per
+   `agents/analysis-profiles.md` (Grep "### PROFILE: impact", read only that section —
+   the structural tier is your primary source when its flag is on).
    For feature `<slug>`: perform an Integration Surface Analysis (ISA).
    Find ALL existing code that should reference, link to, or interact with this
    new feature. Scan these categories systematically:

package/framework/.claude/skills/prd/references/validation-phase.md

@@ -21,6 +21,7 @@ Mark task 5 as `in_progress`.
    - **`review_profile` enum + epic `skip`** — `skip|light|balanced|deep`; missing/empty = blocker (the card-writer must compute it via `prd-card-writer.md § Rule C`); epics MUST be `skip`;
    - **conditional `requirements` presence (PO1)** — a child/standalone card with non-empty `acceptance_criteria` + `scope` MUST carry `requirements` (a fresh `/prd` card without them shifts a measured ~3–4M-token back-fill into `/new`'s orchestrator — see `card-schema.md` § "Authoring completeness invariants");
    - **unresolved `[NEEDS CLARIFICATION: …]` markers** — a card carrying a planning ambiguity is NOT implementable. Resolve each marker (with the user via `AskUserQuestion` when it needs a human answer, or from Discovery/PRD material when it does not), edit the card, re-run;
+   - **EARS grammar on child/standalone AC** (5 patterns + vague-verb ban-list — `card-schema.md` § "Acceptance-criteria grammar") = BLOCKER; `ac_verification` coverage = WARN-only;
    - the universal field-state matrix + remaining enums (`card-schema.md`).
 
    **Why executed and not recited:** the prose version of this gate has already failed silently on a real run (a whole card family shipped with zero audit trail). A recited check degrades under context pressure; an executed one cannot.
@@ -77,7 +78,7 @@ Mark task 5 as `in_progress`.
    Then execute the audit protocol described within, using the card IDs from Step 5.
    The protocol auto-detects which agents to include (security and performance
    are signal-triggered, no manual profile selection needed).
-   **I/O contract:** `audit-phase.md` may edit card YAML files (e.g. its Step 6.9 normalisation pass). The list of all card paths modified by the audit (including those edited in Step 6.9) is the complete set that Step 7 item 6 must stage. The glob `FEAT-XXXX-*.yml (all cards from Step 5)` in item 6 covers this; note it explicitly so that context compaction does not cause a model to stage only the pre-audit originals.
+   **I/O contract:** `audit-phase.md` may edit card YAML files (its Step 6.9 apply runs via the `prd-card-writer` MODE: apply-findings subagent). The list of all card paths modified by the audit (including those edited in Step 6.9) is the complete set that Step 7 item 6 must stage. The glob `FEAT-XXXX-*.yml (all cards from Step 5)` in item 6 covers this; note it explicitly so that context compaction does not cause a model to stage only the pre-audit originals.
 3. Wait for audit report and card edits.
 
 **Gate:** all HIGH/MEDIUM findings resolved, no open `[MANUAL]` items that require external human input beyond this orchestrator. (Items that the orchestrator can resolve autonomously are resolved before this gate; items that need a human decision were already routed to `AskUserQuestion` inside `audit-phase.md`. Items that survive to Step 7 item 1 are those that received a human answer but required card re-edits — these are explicitly handled there.)

package/framework/.claude/skills/prd-add/CHANGELOG.md

@@ -2,6 +2,10 @@
 
 Formato: [Keep a Changelog](https://keepachangelog.com/) · [SemVer](https://semver.org/).
 
+## 1.1.0 — 2026-07-02
+
+- **Analysis-profile contract (framework v4.94.0)**: PATCH-mode re-discovery passes `PROFILE=impact` to `codebase-architect` (blast-radius scoping per `framework/agents/analysis-profiles.md`).
+
 ## 1.0.0 — 2026-07-01
 
 - Baseline: versioning per-skill introdotto al framework v4.82.0.

package/framework/.claude/skills/prd-add/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: prd-add
 effort: medium
-version: 1.0.0
+version: 1.1.0
 description: "Change Request skill for active PRD sessions. Use when the user says /prd-add, 'aggiungi requisito', 'serve anche', 'manca un endpoint', or describes a new requirement that impacts an existing PRD. Also auto-triggered by /prd during discovery when the user's answer reveals a new sub-feature not covered by the original scope. Runs ICIAS impact analysis (semantic scan + structural propagation + scoring) to determine which PRD phases need SKIP/PATCH/REDO, then executes only affected phases."
 ---
 
@@ -241,7 +241,8 @@ Execute ONLY phases with PATCH or REDO verdict, in original phase order.
 
 ### For Discovery dimensions (PATCH/REDO)
 
-- **PATCH**: Run `codebase-architect` on affected dimensions only.
+- **PATCH**: Run `codebase-architect` on affected dimensions only — pass
+  `PROFILE=impact` (blast-radius scoping per `agents/analysis-profiles.md`).
   Update state file checklist entries. No user questions unless ambiguous.
 - **REDO**: Full re-discovery for that dimension (same as /prd Step 2 loop
   but scoped to affected dimensions only). May require user questions.

package/framework/.claude/skills/ui-design/CHANGELOG.md

@@ -2,6 +2,10 @@
 
 Formato: [Keep a Changelog](https://keepachangelog.com/) · [SemVer](https://semver.org/).
 
+## 1.1.0 — 2026-07-02
+
+- **Analysis-profile contract (framework v4.94.0)**: Step B adjacent-UI analysis passes `PROFILE=ui OUTPUT=terse` to `codebase-architect` (registry-cascade-first per `framework/agents/analysis-profiles.md`).
+
 ## 1.0.0 — 2026-07-01
 
 - Baseline: versioning per-skill introdotto al framework v4.82.0.

package/framework/.claude/skills/ui-design/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: ui-design
 effort: medium
-version: 1.0.0
+version: 1.1.0
 description: "UI design workflow. Generates context-aware mockups with GAN-inspired generator/evaluator separation, visual verification via Playwright, and structured sprint contracts. Use when: (1) designing new pages or components, (2) the /prd skill reaches its UI design phase (Step 3), (3) redesigning existing pages, (4) creating design options for user review, (5) any task involving 'design UI', 'mockup', 'opzioni di design', 'progetta interfaccia', '3 opzioni', 'design page', 'UI design'. Not for: bug fixes, small tweaks, copy-only changes, or implementing an already-chosen design."
 ---
 
@@ -120,7 +120,7 @@ Read [references/generation.md](references/generation.md) § Context Capture.
    render harness over full-page Playwright — `baldart render build && /ds-render`
    gives per-primitive PNGs of the REAL registry components (Storybook-backed). Use
    full-page Playwright for page-level context. No Storybook → fall back to Playwright.
-3. Invoke `codebase-architect` to analyze adjacent UI components, layout patterns, and design tokens. Report file paths and rendered structure.
+3. Invoke `codebase-architect` with `PROFILE=ui OUTPUT=terse` (profile contract: `agents/analysis-profiles.md` — registry-cascade-first, component reuse table, token findings) to analyze adjacent UI components, layout patterns, and design tokens. Report file paths and structure.
 
 ### Step C — Generate 3 Options (GENERATOR)
 

package/framework/.claude/workflows/new-card-review.js

@@ -274,7 +274,7 @@ if (baselinePaths.length) {
   log(`Baseline: reusing ${baselinePaths.length} per-card baseline file(s).`)
 } else {
   const arch = await agent(
-    `You are grounding a post-implementation code review. Map the EXISTING architecture, critical patterns, and high-risk code paths relevant to this wave's changed files, so downstream reviewers can spot regressions.\n\n${waveBrief}\n\nReturn a concise baseline (key modules, their contracts, the regression-prone seams touched by this diff). Do not review the changes yet.`,
+    `PROFILE=baseline — resolve your analysis profile per agents/analysis-profiles.md (Grep "### PROFILE: baseline", Read only that section; v4.94.0). You are grounding a post-implementation code review. Map the EXISTING architecture, critical patterns, and high-risk code paths relevant to this wave's changed files, so downstream reviewers can spot regressions.\n\n${waveBrief}\n\nReturn a concise baseline (key modules, their contracts, the regression-prone seams touched by this diff). Do not review the changes yet.`,
     { label: 'arch-baseline', phase: 'Baseline', agentType: 'codebase-architect',
       schema: { type: 'object', required: ['baseline'], additionalProperties: false, properties: { baseline: { type: 'string' } } } }
   )

package/framework/.claude/workflows/new-final-review.js

@@ -265,7 +265,7 @@ if (baselinePaths.length) {
   log(`Baseline: reusing ${baselinePaths.length} per-card baseline file(s).`)
 } else {
   const arch = await agent(
-    `You are grounding a post-implementation code review. Map the EXISTING architecture, critical patterns, and high-risk code paths relevant to this batch's changed files, so downstream reviewers can spot regressions.\n\n${scopeBrief}\n\nReturn a concise baseline (the key modules, their contracts, and the regression-prone seams touched by this diff). Do not review the changes yet.`,
+    `PROFILE=baseline — resolve your analysis profile per agents/analysis-profiles.md (Grep "### PROFILE: baseline", Read only that section; v4.94.0). You are grounding a post-implementation code review. Map the EXISTING architecture, critical patterns, and high-risk code paths relevant to this batch's changed files, so downstream reviewers can spot regressions.\n\n${scopeBrief}\n\nReturn a concise baseline (the key modules, their contracts, and the regression-prone seams touched by this diff). Do not review the changes yet.`,
     { label: 'arch-baseline', phase: 'Baseline', agentType: 'codebase-architect',
       schema: { type: 'object', required: ['baseline'], additionalProperties: false, properties: { baseline: { type: 'string' } } } }
   )