baldart 5.5.0 → 5.7.0

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

@@ -52,6 +52,19 @@ Mark task 5 as `in_progress`.
         surface / ISA file owned by NO card is a BLOCKER (this is the gap that otherwise surfaces only
         at `/new`'s expensive final review). Message: `"ISA touchpoint <path> (<category>) is owned by
         no card — assign it to a card's files_likely_touched."`
+      - **Universal-quantifier epic AC gate (v5.6.0 — FEAT-0068):** for every EPIC acceptance
+        criterion carrying a universal quantifier over a UI/route surface ("ogni schermata",
+        "tutte le route", "every screen", "all pages", "nessun <difetto> su <superficie>"),
+        derive the surface's OWNER components from the **fresh registry/ISA census** (the
+        UI ROLE FAMILY touchpoints of discovery Dimension 9 — NOT the raw mechanism-consumer
+        touchpoints, or you inherit an incomplete inventory) and verify each owner appears in
+        the union of the child cards' `files_likely_touched`/scope. An owner covered by NO
+        child is a BLOCKER: `"Epic AC-<n> quantifies over <surface> but owner <component>
+        (<N> files) belongs to no card."` Persist the resolved owner list as
+        `invariant_owners:` in the epic YAML so the `/new` epic-closure gate can re-verify
+        it. (FEAT-0068: the epic promised "no seam on every screen" while DrilldownHeader/
+        SectionHeader — ~90% of screens — belonged to no card; the ISA→card gate passed
+        44/44 vacuously because the inventory itself was wrong.)
       Both are SEMANTIC (path extraction from prose / ISA needs interpretation) — bias toward flagging.
 
    **Gate**: the 0-i validator exits 0 on every card (enums, conditional `requirements`, zero
@@ -59,6 +72,22 @@ Mark task 5 as `in_progress`.
    checks (b)/(c) are noted in the audit log; user may accept them after review. The 0-i and (e)
    BLOCKERs must be fixed before commit.
 
+0-ii. **Phase-evidence audit (v5.6.0 — executed, not recited; FEAT-0068 shipped TWO phantom
+   gates).** Deterministic checks on the STATE FILE before the audit protocol runs:
+   - **`module_read` stamps**: each executed phase section must carry its `module_read:
+     <reference file> (full)` stamp (SKILL.md § phase-module loading). A phase that ran with
+     its module unread is a protocol violation to surface — on FEAT-0068, `research-phase.md`,
+     `prd-writing-phase.md` and `backlog-phase.md` were never read and the improvised Step 5
+     contract produced the EARS rework round.
+   - **Gate stamps carry evidence**: any gate recorded as run/passed/`N/A` (API Performance
+     Gate, holistic audit, Codex Discovery Cross-Check) must name its evidence — an agent
+     spawn/report path for agent gates, the concrete reason for an `N/A`. A gate stamp with no
+     evidence is treated as NOT RUN (the FEAT-0068 session stamped `pass # N/A` on the API
+     gate without ever spawning the auditor, and the holistic stamp landed with zero audit
+     spawns).
+   - **`step_3_mode` ∈ {full, hybrid, mockup-only, skipped, pending_external_handoff}**: any
+     other value (the session fabricated `design-spec`) is a BLOCKER — fix the state file and
+     re-run the branch it should have taken.
 1. **Field Name Audit (runs after item 0 — only when item 0 passes for a given card; skipped for cards blocked in item 0)** — for each generated card:
 
    a. Verify every `data_fields` entry has `ts_verified: true` OR `status: new` with `schema_ref`.
@@ -142,9 +171,15 @@ created by Step 1 (HARD RULE 17). `$WORKTREE_PATH` is set in the state file.
    HOLISTIC_AUDITED_AT="$(date -u +%Y-%m-%dT%H:%M:%SZ)"
    HOLISTIC_AUDITED_COMMIT="$(git -C "$WORKTREE_PATH" merge-base HEAD "${git.trunk_branch}" 2>/dev/null || git -C "$WORKTREE_PATH" rev-parse "${git.trunk_branch}" 2>/dev/null || echo "")"
    # --set = the sorted Step-5 child card IDs (the joint cross-card scope), comma-separated.
+   # --audit-report (v5.6.0, REQUIRED for a full stamp) = the audit-phase report artifact
+   #   (e.g. /tmp/prd-audit-<slug>.md, written by audit-phase Step 6.9 with its `agents_run:`
+   #   line). NO artifact on disk = the audit team never ran (the FEAT-0068 phantom stamp) →
+   #   run WITHOUT the flag and the script writes `status: skipped` + NO agents_run, which
+   #   /new's P1 treats as ABSENT (plan-auditor runs — fail-safe, exactly right).
    node .framework/framework/scripts/stamp-holistic-audit.js \
      --at "$HOLISTIC_AUDITED_AT" --commit "$HOLISTIC_AUDITED_COMMIT" \
-     --set "<ID1,ID2,...>" "$WORKTREE_PATH/${paths.backlog_dir}"/FEAT-XXXX-*.yml
+     --set "<ID1,ID2,...>" --audit-report "/tmp/prd-audit-<slug>.md" \
+     "$WORKTREE_PATH/${paths.backlog_dir}"/FEAT-XXXX-*.yml
    ```
    The script is **idempotent** (a card already stamped by Step 6.9.4 is untouched),
    **additive** (never overwrites other `metadata` keys), skips EPIC cards (they carry
@@ -223,6 +258,15 @@ created by Step 1 (HARD RULE 17). `$WORKTREE_PATH` is set in the state file.
    Input: { "worktreePath": "$WORKTREE_PATH" }
    ```
 
+   **HARD RULE (v5.6.0 — FEAT-0068 N1): `mw-docs`, NEVER generic `/mw`, for a docs worktree.**
+   The registry entry for this worktree says `kind: "docs"` — a generic `/mw` on it runs the
+   forbidden unbounded `npm run build` (a docs worktree has no node_modules → guaranteed false
+   BUILD_FAIL, manual recovery, classifier-blocked push; ~4M wasted on the real session). If
+   you find yourself about to call `/mw`, or to invent invocation args (`checksAlreadyPassed`
+   is NOT an input of this contract), STOP — the invocation above is the whole contract.
+   `/mw` itself refuses a `kind: "docs"` worktree since v5.6.0 (worktree-manager pre-flight),
+   but do not rely on the belt: use the right mode.
+
    The skill executes:
    - Safety commit (idempotent — likely no-op after step 8; if any file was
      missed by item 6's explicit list, the safety commit picks it up, but the

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.1 — 2026-07-06
+
+- **Feature-gate**: added `requires_feature: has_prd_workflow` frontmatter — this skill is now linked into a consumer only when `features.has_prd_workflow` is enabled (it already refused at runtime otherwise). Trims Codex's ~2% skill-description budget on projects without the feature. Install-time gate, portable across Claude + Codex.
+
 ## 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`).

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

@@ -1,7 +1,8 @@
 ---
 name: prd-add
 effort: medium
-version: 1.1.0
+version: 1.1.1
+requires_feature: has_prd_workflow
 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."
 ---
 

package/framework/.claude/skills/skill-creator/references/skill-structure.md

@@ -27,13 +27,42 @@ when the skill needs them** — no empty placeholder dirs (that was upstream
 name: <kebab-case>            # matches the directory name
 effort: medium               # low | medium | high | xhigh | max  (effort-protocol.md)
 version: 1.0.0               # the skill's OWN SemVer
+requires_feature: has_x      # OPTIONAL — install-time feature-gate (see below)
 description: >               # triggers + what/when; NO angle brackets
   ...
 ---
 ```
 
-Order: `name` → `effort` → `version` → `description`. `license` / `metadata` are
-tolerated only on imported third-party skills; do not add other keys.
+Order: `name` → `effort` → `version` → (`requires_feature`) → `description`.
+`license` / `metadata` are tolerated only on imported third-party skills; do not
+add other keys.
+
+### `requires_feature` — install-time feature-gate (OPTIONAL)
+
+A skill that is only meaningful when a `baldart.config.yml` `features.*` flag is
+on (and already REFUSES at runtime otherwise) declares that dependency here, so
+the installer links it into a consumer ONLY when the feature is enabled. This
+trims Codex's ~2% skill-description budget on projects that don't use the feature.
+
+```yaml
+requires_feature: has_design_system                 # string  → link iff true
+requires_feature: [has_design_system, has_e2e_review] # list = AND (ALL true)
+```
+
+- **Omit it** for any skill that should always be linked (the default). The five
+  bootstrap skills that ENABLE a feature (`design-system-init`, `i18n-adopt`,
+  `graphify-bootstrap`, `lsp-bootstrap`, `toolchain-bootstrap`) MUST stay ungated
+  — otherwise the feature could never be turned on.
+- The gate is **install-time only** and **portable**: both Claude (`.claude/skills/`)
+  and Codex (`.agents/skills/`) simply see fewer directories. Neither runtime reads
+  the field — it is ignored exactly like `version`/`effort`. Resolution lives in
+  `src/utils/skill-gate.js`; it reads `features.*` directly and **fails open** (a
+  missing config, or a malformed frontmatter, links the skill rather than hiding it).
+- **NOT a `baldart.config.yml` key** — it consumes existing `features.*`, so the
+  schema-change propagation rule does NOT apply. It is skill-frontmatter metadata.
+- **Invariant** (latent, for future Codex `agents/openai.yaml` metadata): a gated
+  skill MUST NOT be declared as a `dependencies:` target of an always-linked skill's
+  `openai.yaml` — pruning the gated skill would leave a dangling dependency.
 
 ## Body headers (in order, when applicable)
 

package/framework/.claude/skills/skill-creator/scripts/quick_validate.py

@@ -39,10 +39,22 @@ def validate_skill(skill_path):
         return False, f"Invalid YAML in frontmatter: {e}"
 
     # Define allowed properties
-    # BALDART additions: `effort` (per-skill reasoning baseline — effort-protocol.md)
-    # and `version` (per-skill SemVer — canonical structure, see references/skill-structure.md).
+    # BALDART additions: `effort` (per-skill reasoning baseline — effort-protocol.md),
+    # `version` (per-skill SemVer — canonical structure, see references/skill-structure.md)
+    # and `requires_feature` (install-time feature-gate — a skill is linked into a
+    # consumer only when this `features.*` flag is on; see references/skill-structure.md
+    # and src/utils/skill-gate.js). All three are OPTIONAL frontmatter metadata,
+    # ignored by the Claude/Codex skill loaders (they only read name+description).
     ALLOWED_PROPERTIES = {'name', 'description', 'license', 'allowed-tools', 'metadata',
-                          'effort', 'version'}
+                          'effort', 'version', 'requires_feature'}
+
+    # Known feature flags a `requires_feature` value may reference (mirrors the
+    # features.* block of baldart.config.template.yml). Used for a SOFT warning
+    # only — an unknown value is not fatal (fail-open: the gate links the skill).
+    KNOWN_FEATURES = {'has_design_system', 'multi_tenant_theming', 'has_api_docs',
+                      'has_backlog', 'has_adrs', 'has_prd_workflow', 'has_wiki_overlay',
+                      'has_lsp_layer', 'has_code_graph', 'has_e2e_review',
+                      'has_toolchain', 'has_i18n'}
 
     # Check for unexpected properties (excluding nested keys under metadata)
     unexpected_keys = set(frontmatter.keys()) - ALLOWED_PROPERTIES
@@ -90,6 +102,16 @@ def validate_skill(skill_path):
     # `version` + a per-skill CHANGELOG.md are REQUIRED for new skills but WARNED (not
     # hard-failed) here for backwards-compat with skills authored before the convention.
     warnings = []
+    # Soft-validate requires_feature values against the known features.* set.
+    if 'requires_feature' in frontmatter:
+        req = frontmatter['requires_feature']
+        req_list = req if isinstance(req, list) else [req]
+        unknown = [str(f) for f in req_list if str(f) not in KNOWN_FEATURES]
+        if unknown:
+            warnings.append(
+                f"`requires_feature` references unknown flag(s): {', '.join(sorted(unknown))}. "
+                f"The gate fails open (skill still linked). Known: {', '.join(sorted(KNOWN_FEATURES))}"
+            )
     if 'version' not in frontmatter:
         warnings.append("missing `version:` in frontmatter (add `version: 1.0.0`)")
     if 'effort' not in frontmatter:

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

@@ -2,6 +2,10 @@
 
 Formato: [Keep a Changelog](https://keepachangelog.com/) · [SemVer](https://semver.org/).
 
+## 2.0.1 — 2026-07-06
+
+- **Feature-gate**: added `requires_feature: has_design_system` frontmatter — this skill is now linked into a consumer only when `features.has_design_system` is enabled (it already refused at runtime otherwise). Trims Codex's ~2% skill-description budget on projects without the feature. Install-time gate, portable across Claude + Codex.
+
 ## 2.0.0 — 2026-07-03
 
 **The local design studio.** Root-level refactor (framework v5.2.0): the

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

@@ -1,7 +1,8 @@
 ---
 name: ui-design
 effort: medium
-version: 2.0.0
+version: 2.0.1
+requires_feature: has_design_system
 description: "The local design studio — THE framework skill for designing, prototyping and restyling UI directly in the repo (the internal twin of the Claude Design handoff). Produces context-aware, token-compliant HTML mockups in 3 distinct directions, with a locked Design Read, a deterministic anti-slop craft gate and separated generator/evaluator verification. Use when: (1) designing new pages, screens or components, (2) the /prd skill reaches its UI design phase (Step 3), (3) redesigning/restyling existing pages ('rifai la UI', 'migliora il design', 'restyle'), (4) exploring design options ('3 opzioni', 'opzioni di design', 'direzioni estetiche'), (5) prototyping a page/landing/dashboard locally ('prototipo', 'mockup', 'progetta interfaccia', 'design UI'). SUPERSEDES frontend-design (now a router) and ui-ux-pro-max for ALL design/prototyping work. Not for: implementing an already-approved mockup (→ /ui-implement), in-code UI fixes with no design decision (→ ui-expert agent), motion specs (→ /motion-design)."
 ---
 

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

@@ -2,6 +2,10 @@
 
 Formato: [Keep a Changelog](https://keepachangelog.com/) · [SemVer](https://semver.org/).
 
+## 1.1.2 — 2026-07-06
+
+- **Feature-gate**: added `requires_feature: has_design_system` frontmatter — this skill is now linked into a consumer only when `features.has_design_system` is enabled (it already refused at runtime otherwise). Trims Codex's ~2% skill-description budget on projects without the feature. Install-time gate, portable across Claude + Codex.
+
 ## 1.1.1 — 2026-07-02
 
 - Return Contract (SKILL.md): documentati i campi `bindings` + `lane_coverage`/`lanes`

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

@@ -1,7 +1,8 @@
 ---
 name: ui-implement
 effort: medium
-version: 1.1.1
+version: 1.1.2
+requires_feature: has_design_system
 description: >
   Implement an ALREADY-APPROVED mockup into the codebase end-to-end and
   self-verify its fidelity. Takes a mockup in any channel — a Claude Design

package/framework/.claude/skills/worktree-manager/CHANGELOG.md

@@ -2,6 +2,19 @@
 
 Formato: [Keep a Changelog](https://keepachangelog.com/) · [SemVer](https://semver.org/).
 
+## 1.2.0 — 2026-07-04 (FEAT-0068 post-mortem)
+
+- **`merge-worktree.sh --safety-sweep <all|allowlist:globs>`**: in modalità allowlist il
+  safety commit pre-rebase stagia SOLO i file che matchano (bookkeeping del batch), con
+  messaggio onesto che li enumera; le modifiche TRACKED fuori allowlist vengono messe in
+  quarantena byte-per-byte (`quarantined:` nel manifest) e ripristinate a HEAD, gli
+  untracked restano su disco (`uncommitted_left:`). Default `all` invariato per `/mw`
+  interattivo. Chiude lo split-brain col F-030 del chiamante ("[safety] Auto-commit" da
+  751 righe opaco su develop, ricorrente FEAT-0067/FEAT-0068).
+- **Guardia docs-worktree in `/mw`** (BLOCKING, step 1): registry `kind: "docs"` ⇒ rifiuto
+  con puntatore a `mw-docs` (un `/mw` generico su un docs worktree = build unbounded senza
+  node_modules ⇒ BUILD_FAIL falso garantito, ~4M su un run `/prd` reale).
+
 ## 1.1.0 — 2026-07-03
 
 ### Fixed — local-trunk sync robustness (step 4c "Common", both strategies)

package/framework/.claude/skills/worktree-manager/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: worktree-manager
 effort: medium
-version: 1.1.0
+version: 1.2.0
 description: >
   Manage fully independent git worktrees for parallel coding agents.
   Commands: /nw (new worktree) creates an isolated workspace with its own
@@ -685,6 +685,16 @@ Supports two modes:
 
 Read `.worktrees/registry.json`. If multiple entries exist or user didn't specify, list them and ask which to merge.
 
+**Docs-worktree guard (v5.6.0 — BLOCKING, before anything else).** If the resolved registry
+entry carries `kind: "docs"`, this is the WRONG mode: REFUSE and route to `mw-docs`
+(programmatic: `Mode: programmatic, mw-docs`). A generic `/mw` on a docs worktree runs the
+build/check pipeline against a tree with no node_modules → a guaranteed false BUILD_FAIL,
+manual recovery, and a blocked push (observed on a real `/prd` session: ~4M tokens + a human
+unblock). Message: `"WRONG MODE: worktree '<slug>' is kind:docs — use mw-docs (docs merge:
+no build, additive-registry resolution). Refusing generic /mw."` Also ignore any invented
+invocation args (`checksAlreadyPassed` is a `/new`-orchestrator flag, not a user contract) —
+the registry entry is the SSOT for what kind of merge this is.
+
 Fallback: `git worktree list` if registry is missing.
 
 Determine, reading them from the worktree's registry entry (R6):

package/framework/.claude/skills/worktree-manager/scripts/merge-worktree.sh

@@ -48,6 +48,21 @@
 #   --tc-build <cmd>       toolchain build cmd     (default: config / npm run build)
 #   --log <path>           build/merge log sink    (default: /tmp/wt-merge-<slug>.log)
 #   --build-timeout <s>    hard build timeout sec  (default: 600)
+#   --safety-sweep <mode>  what the pre-rebase safety commit may stage (v5.6.0):
+#                            all               — every changed+untracked file (default;
+#                                                the historical /mw interactive behavior)
+#                            allowlist:<globs> — comma-separated shell globs (e.g.
+#                                                "backlog/*.yml,docs/metrics/*,.baldart/*").
+#                              Matching files → committed with an honest message that
+#                              ENUMERATES them. Non-matching TRACKED changes → preserved
+#                              byte-for-byte into a labeled quarantine dir, then restored
+#                              to HEAD (so the rebase can start). Non-matching UNTRACKED
+#                              files → left in place. Both reported in the manifest.
+#                              Rationale (FEAT-0068 5f618347d / FEAT-0067 5a5f1c135): an
+#                              unconditional sweep contradicts the caller's F-030 "never
+#                              commit ungated code" by construction — dirty code at merge
+#                              time did NOT pass the per-card gates and must never ride an
+#                              opaque "[safety]" commit onto the trunk.
 #
 # Status file written (parsed by callers — STABLE contract):
 #   status: success | code_conflict | build_fail | sync_needs_decision | error
@@ -63,6 +78,8 @@
 #   sync_marker: <none | SYNC-DEFERRED | SYNC-NEEDS-DECISION>
 #   sync_detail: <message | ->
 #   build_log: <path | ->
+#   uncommitted_left: <csv | ->        (allowlist mode — untracked files left in place, NOT committed)
+#   quarantined: <dir | ->             (allowlist mode — tracked changes preserved here, then reset to HEAD)
 #
 # Exit: 0 ONLY on status:success. Non-zero otherwise (the exit code mirrors the
 # status: 10=code_conflict, 11=build_fail, 12=sync_needs_decision, 1/2=error). The
@@ -75,7 +92,7 @@ err() { printf '%s\n' "$*" >&2; }
 
 # --- args ------------------------------------------------------------------
 WORKTREE= MANIFEST= CONTINUE=0 BRANCH= TRUNK= MAIN= STRATEGY= SKIP_CHECKS=0
-METRICS_DIR= TC_TC= TC_LINT= TC_BUILD= LOG= BUILD_TIMEOUT=600
+METRICS_DIR= TC_TC= TC_LINT= TC_BUILD= LOG= BUILD_TIMEOUT=600 SAFETY_SWEEP=all
 while [ $# -gt 0 ]; do
   case "$1" in
     --worktree) WORKTREE="${2:-}"; shift 2 ;;
@@ -92,6 +109,7 @@ while [ $# -gt 0 ]; do
     --tc-build) TC_BUILD="${2:-}"; shift 2 ;;
     --log) LOG="${2:-}"; shift 2 ;;
     --build-timeout) BUILD_TIMEOUT="${2:-}"; shift 2 ;;
+    --safety-sweep) SAFETY_SWEEP="${2:-all}"; shift 2 ;;
     *) err "ERROR: unknown arg: $1"; exit 2 ;;
   esac
 done
@@ -99,6 +117,7 @@ done
 # --- status writer (called on EVERY exit path) -----------------------------
 M_STATUS="error" M_PHASE="identify" M_ERROR="-" M_MERGE="-" M_MERGETS="-"
 M_CONFLICTS="-" M_SYNCMARK="none" M_SYNCDETAIL="-" M_BLOG="-"
+M_UNCOMMITTED="-" M_QUARANTINE="-"
 write_status() {
   [ -n "$MANIFEST" ] || return 0
   {
@@ -115,6 +134,8 @@ write_status() {
     printf 'sync_marker: %s\n' "$M_SYNCMARK"
     printf 'sync_detail: %s\n' "$M_SYNCDETAIL"
     printf 'build_log: %s\n' "$M_BLOG"
+    printf 'uncommitted_left: %s\n' "$M_UNCOMMITTED"
+    printf 'quarantined: %s\n' "$M_QUARANTINE"
   } > "$MANIFEST" 2>/dev/null || true
 }
 fail()          { M_STATUS="error";         M_ERROR="$1"; write_status; err "ERROR: $1"; exit "${2:-1}"; }
@@ -362,19 +383,74 @@ else
   # -------------------------------------------------------------------------
   # FRESH path: safety commit → (checks) → rebase
   # -------------------------------------------------------------------------
-  # 1. Safety commit (ALWAYS — never skippable; files lost after rebase are unrecoverable)
+  # 1. Safety commit. Mode `all` (default, /mw interactive): every changed+untracked file —
+  #    files lost after rebase are unrecoverable. Mode `allowlist:<globs>` (v5.6.0, passed by
+  #    orchestrated callers like new2): only batch bookkeeping is committed (with an honest,
+  #    enumerating message); non-matching TRACKED changes are quarantined byte-for-byte then
+  #    reset to HEAD (a dirty tracked file would block the rebase), non-matching UNTRACKED
+  #    files stay in place. Nothing is silently lost, nothing ungated rides to the trunk.
   M_PHASE="safety"
   CHANGED="$(git -C "$WORKTREE" diff --name-only HEAD 2>/dev/null)"
   UNTRACKED="$(git -C "$WORKTREE" ls-files --others --exclude-standard 2>/dev/null)"
   if [ -n "$CHANGED" ] || [ -n "$UNTRACKED" ]; then
-    for f in $CHANGED $UNTRACKED; do git -C "$WORKTREE" add "$f" 2>>"$LOG"; done
-    git -C "$WORKTREE" commit -m "[safety] Auto-commit uncommitted files before merge
+    case "$SAFETY_SWEEP" in
+      allowlist:*)
+        SWEEP_GLOBS="${SAFETY_SWEEP#allowlist:}"
+        sweep_match() { # POSIX case-glob match of $1 against any comma-separated pattern
+          _f="$1"; _rest="$SWEEP_GLOBS"
+          while [ -n "$_rest" ]; do
+            _pat="${_rest%%,*}"
+            [ "$_pat" = "$_rest" ] && _rest= || _rest="${_rest#*,}"
+            # shellcheck disable=SC2254 — unquoted on purpose: $_pat is a glob
+            case "$_f" in $_pat) return 0 ;; esac
+          done
+          return 1
+        }
+        SWEPT= LEFT_UNTRACKED= QUAR_TRACKED=
+        for f in $CHANGED; do
+          if sweep_match "$f"; then git -C "$WORKTREE" add "$f" 2>>"$LOG"; SWEPT="$SWEPT $f"
+          else QUAR_TRACKED="$QUAR_TRACKED $f"; fi
+        done
+        for f in $UNTRACKED; do
+          if sweep_match "$f"; then git -C "$WORKTREE" add "$f" 2>>"$LOG"; SWEPT="$SWEPT $f"
+          else LEFT_UNTRACKED="${LEFT_UNTRACKED:+$LEFT_UNTRACKED,}$f"; fi
+        done
+        if [ -n "$QUAR_TRACKED" ]; then
+          QDIR="/tmp/wt-merge-quarantine-$(basename "$WORKTREE")-$(date +%s)"
+          for f in $QUAR_TRACKED; do
+            mkdir -p "$QDIR/$(dirname "$f")" 2>>"$LOG"
+            cp -p "$WORKTREE/$f" "$QDIR/$f" 2>>"$LOG" || err "WARN: quarantine copy failed for $f"
+          done
+          # restore ONLY after the byte-for-byte copy — the rebase needs a clean tracked tree
+          for f in $QUAR_TRACKED; do git -C "$WORKTREE" checkout -- "$f" 2>>"$LOG"; done
+          M_QUARANTINE="$QDIR"
+          err "WARN: $(echo "$QUAR_TRACKED" | wc -w | tr -d ' ') tracked change(s) OUTSIDE the sweep allowlist quarantined to $QDIR + reset to HEAD (ungated code never rides a safety commit — F-030)"
+        fi
+        [ -z "$LEFT_UNTRACKED" ] || M_UNCOMMITTED="$LEFT_UNTRACKED"
+        write_status
+        if [ -n "$SWEPT" ]; then
+          git -C "$WORKTREE" commit -m "[safety] Materialize batch bookkeeping before merge (sweep allowlist)
+
+Allowlist-matched files that were uncommitted when merge-worktree.sh started:
+$(for f in $SWEPT; do printf '  - %s\n' "$f"; done)
+
+Non-matching files were NOT committed (quarantined/left + reported in the manifest).
+
+Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>" --quiet >>"$LOG" 2>&1 \
+            || err "WARN: allowlist safety commit produced no commit (nothing staged?)"
+        fi
+        ;;
+      *)
+        for f in $CHANGED $UNTRACKED; do git -C "$WORKTREE" add "$f" 2>>"$LOG"; done
+        git -C "$WORKTREE" commit -m "[safety] Auto-commit uncommitted files before merge
 
 Files were uncommitted when merge-worktree.sh started. This safety commit
 prevents file loss during rebase.
 
-Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>" --quiet >>"$LOG" 2>&1 \
-      || err "WARN: safety commit produced no commit (nothing staged?)"
+Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>" --quiet >>"$LOG" 2>&1 \
+          || err "WARN: safety commit produced no commit (nothing staged?)"
+        ;;
+    esac
   fi
 
   # 2. Pre-merge checks (skipped when --skip-checks / checksAlreadyPassed)

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

@@ -340,13 +340,15 @@ const codexPrompt =
   `The companion script is ALREADY CONFIRMED PRESENT at:\n  ${codexScriptPath}\n\n` +
   `Run EXACTLY these steps and nothing else:\n` +
   `  1. Write the task text (everything after "TASK PROMPT:" at the end of this message) to ${codexTaskFile} using the Write tool — do NOT inline it into the shell command (avoids quote breakage).\n` +
-  `  2. Launch Codex in the BACKGROUND (run_in_background:true — a sync run hits the Bash timeout):\n` +
-  `       node "${codexScriptPath}" task "$(cat ${codexTaskFile})" --cwd "${a.worktreePath || '.'}" > ${codexReviewFile} 2>&1\n` +
-  `  3. POLL ${codexReviewFile} (BashOutput / repeated reads) until ONE of these appears — whichever is FIRST ends the poll (do NOT keep waiting once one is present). Set \`marker\` accordingly:\n` +
-  `       • "<<<END_FINDINGS_JSON>>>"  → marker = "END_JSON"\n` +
-  `       • "Turn completed."          → marker = "TURN_COMPLETED" (Codex finished; it may have written prose instead of the JSON block)\n` +
-  `       • "CODEX_NOT_FOUND"          → marker = "CODEX_NOT_FOUND" (companion missing)\n` +
-  `       • the full 10-minute window elapses with none of the above → marker = "TIMEOUT" (NEVER pick this just because a single poll returned slowly)\n` +
+  `  2. Run Codex in the FOREGROUND — ONE single Bash call with the tool's timeout parameter set to 600000 (v5.6.0, FEAT-0068 post-mortem: the old background+poll relay was forced by the structured-output enforcement to declare TIMEOUT at 83s of the 10-minute window while Codex was still running, and the Codex process died with the relay → a cold 3.68M fallback review with no cross-model diversity. A blocking call has no idle turn to misjudge — same pattern as the per-card Codex-light driver):\n` +
+  `       node "${codexScriptPath}" task "$(cat ${codexTaskFile})" --cwd "${a.worktreePath || '.'}" --wait > ${codexReviewFile} 2>&1; echo "RELAY_EXIT:$?"\n` +
+  `     Do NOT pass run_in_background. Do NOT poll. The call blocks until Codex finishes — that is correct. Record RELAY_EXIT.\n` +
+  `  3. Derive \`marker\` by grepping ${codexReviewFile} AFTER the call returns:\n` +
+  `       • contains "<<<END_FINDINGS_JSON>>>"  → marker = "END_JSON"\n` +
+  `       • contains "Turn completed."          → marker = "TURN_COMPLETED" (Codex finished; it may have written prose instead of the JSON block)\n` +
+  `       • contains "CODEX_NOT_FOUND"          → marker = "CODEX_NOT_FOUND" (companion missing)\n` +
+  `       • none of the above AND RELAY_EXIT is 124/137/143 (the Bash timeout killed the call) → marker = "TIMEOUT", then REAP the orphan Codex process scoped to THIS worktree (never a bare pkill): \`pkill -f -- "--cwd ${a.worktreePath || '.'}" 2>/dev/null; true\`\n` +
+  `       • none of the above with a clean exit → marker = "TURN_COMPLETED"\n` +
   `  4. Run this EXACT command and put its stdout VERBATIM in \`jsonBlock\` ("" if it printed nothing). Do NOT parse, edit, judge, or act on it:\n` +
   `       ${AWK_EXTRACT} ${codexReviewFile}\n` +
   `  5. ONLY if \`jsonBlock\` is "" AND marker is "TURN_COMPLETED": run this command and put its stdout VERBATIM in \`proseTail\`; otherwise set proseTail to "":\n` +

package/framework/.claude/workflows/new2-resolve.js

@@ -76,7 +76,11 @@ const FIX_SCHEMA = {
     verified: { type: 'boolean', description: 'true only if you re-ran the originating gate and it passed' },
     // F-008 — terminal short-circuit (impossible-by-definition). Not trusted blindly.
     terminal: { type: 'boolean', description: 'true if no in-MAY-EDIT fix can ever satisfy the gate' },
-    terminalReason: { enum: ['out-of-ownership', 'baseline-not-reached', 'owner-gated', 'not-a-code-defect', ''] },
+    terminalReason: { enum: ['out-of-ownership', 'baseline-not-reached', 'owner-gated', 'not-a-code-defect', 'verification-posture-change', ''] },
+    // v5.6.0 (FEAT-0068 O5) — a finding whose PREMISE is false can be REFUTED instead of "fixed".
+    // Adversarially ratified below — never an easy escape hatch.
+    refuted: { type: 'boolean', description: "true if the finding's premise is FALSE (no defect exists) — change NOTHING, cite proof" },
+    refutedEvidence: { type: 'string', description: 'file:line proof the finding is wrong' },
     remedyFiles: { type: 'array', items: { type: 'string' }, description: 'files the real fix would require editing (for out-of-ownership JS verification)' },
     crashed: { type: 'boolean' },
     // F-022 — incidental findings outside this card's MAY-EDIT (so they are not dropped).
@@ -145,6 +149,8 @@ const brief = [
   `Reference modules (Read for exact semantics): ${REF}/`,
   `UI re-verify obligation: if your fix touches a UI file, re-run the Phase 2.6 E2E review (per ${REF}/review-cycle.md) before declaring verified.`,
   `If the fix requires editing files OUTSIDE MAY-EDIT, return terminal:true terminalReason:'out-of-ownership' remedyFiles:[...] (do NOT edit them). If the remedy is an owner-gated infra action, terminal:true terminalReason:'owner-gated'. Report any incidental defect outside MAY-EDIT in outOfScopeFindings.`,
+  `VALIDATE THE PREMISE FIRST (v5.6.0): before touching any file, check the finding against the actual code. If its premise is FALSE (misread code, condition already satisfied, documented-by-design), return refuted:true + refutedEvidence:'<file:line proof>' and change NOTHING — NEVER edit code to appease a wrong finding.`,
+  `VERIFICATION-POSTURE RULE (v5.6.0): a "fix" that disables, skips, or opt-in-gates a test/check/suite that an acceptance criterion of this batch mandates is FORBIDDEN — it erodes the DoD (FEAT-0068: a repair flag-gated the epic's visual-regression suite to silence a blocker). If that looks like the only available fix, return terminal:true terminalReason:'verification-posture-change' instead.`,
 ].filter(Boolean).join('\n')
 
 // JS-deterministic ownership check (F-008 anti-escape-hatch): are remedy files ⊆ MAY-EDIT?
@@ -213,6 +219,28 @@ try {
   )
 } catch (e) { if (e && e.transientExhausted) return { status: 'followup', reason: 'outage during tier-1', deferralClass: 'outage', outOfScopeFindings: [] }; throw e }
 
+// v5.6.0 (FEAT-0068 O5 — false-positive BLOCKER): refuted short-circuit, adversarially ratified.
+// The FEAT-0068 CR-001 blocker had a false premise ("baselines missing" = the documented bootstrap
+// state) and was "resolved" by flag-gating the epic's mandated visual-regression suite — 4.73M
+// spent eroding the DoD to appease a wrong finding. A ratified refutation resolves with ZERO edits.
+if (attempt && attempt.refuted && !attempt.terminal) {
+  let refConfirmed = selfJudges // reviewer-writer specialists self-verify (same trust model as terminal)
+  if (!selfJudges) {
+    try {
+      const rj = await agentSafe(
+        `A repair agent claims this finding's PREMISE IS FALSE (refuted) — no defect exists, nothing was changed. Claimed proof: ${attempt.refutedEvidence || attempt.note || '(none)'}\n\n${brief}\n\nIndependently verify the refutation against the actual files (grep/read them yourself; do NOT trust the claim). Return confirmed:true ONLY if the finding is genuinely wrong.`,
+        { label: `resolve:refute-judge:${card}`, phase: 'Verify', agentType: judgeAgent, schema: TERMINAL_JUDGE_SCHEMA }
+      )
+      refConfirmed = !!(rj && rj.confirmed)
+    } catch (_) { refConfirmed = false }
+  }
+  if (refConfirmed) {
+    log(`${kind} REFUTED (false premise${selfJudges ? '' : ', judge-ratified'}) — resolved with zero edits.`)
+    return { status: 'resolved', reason: `refuted: ${attempt.refutedEvidence || attempt.note || 'false premise'}`, outOfScopeFindings: collectOOS(attempt) }
+  }
+  log('refutation NOT ratified — treating as a real finding.')
+}
+
 // F-008 — terminal short-circuit, verified not trusted.
 if (attempt && attempt.terminal) {
   const tr = attempt.terminalReason || ''