baldart 3.33.1 → 3.35.0

package/CHANGELOG.md

@@ -5,6 +5,37 @@ 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).
 
+## [3.35.0] - 2026-05-30
+
+De-duplicates the review chain in `/new` and adds a **Review Profile Selector** so the per-card pre-merge gate scales its *depth* by risk instead of running the full multi-agent `/codexreview` on every card — including trivial ones. The per-card gate stays **unconditional** (it always runs); only its breadth varies, and the safety-critical Codex adversarial pass + false-positive gate run on every card regardless of profile. Copertura invariata: every line is still code-reviewed once, every doc doc-reviewed once. **No new `baldart.config.yml` keys** — the profile is computed at runtime from signals already present (the Phase 3.7 high-risk-trigger detector + the QA profile), and lean mode is an internal caller→skill file contract, so the schema-propagation rule does not apply.
+
+### Changed — `/new` review chain (de-dup, coverage-invariant)
+
+- **[framework/.claude/skills/new/SKILL.md](framework/.claude/skills/new/SKILL.md)** + **[framework/.claude/commands/codexreview.md](framework/.claude/commands/codexreview.md)**: per-card Phase 3.7 (and Team Mode D.4b) now hand `/codexreview` a lean contract file (`/tmp/codexreview-lean-<CARD-ID>.json`) so it **reuses the Phase-1 architecture baseline** (`/tmp/arch-baseline-<CARD-ID>.md`) instead of re-spawning `codebase-architect`, and **skips the duplicate `doc-reviewer`** (Phase 3 already audits the same diff). `/codexreview` gains a backward-compatible **Step -0.5 (lean-mode detection)** with consume-once semantics; standalone `/codexreview <CARD-ID>` (no contract file) behaves exactly as before.
+- **doc-reviewer lens-merge**: Phase 3's `doc-reviewer` mandate now also carries the *spec/docs-drift → bug* lens that was previously exclusive to `/codexreview` agent #4 — so dropping the duplicate loses no coverage.
+- **Final review de-dup**: single-card batches short-circuit F.1–F.4 (the lone card already passed Phase 3.7 unchanged) while still running the F.5 final build; multi-card batches scope the cross-card review to a **computed** surface (files touched by ≥2 cards ∪ `depends_on`-linked pairs), never a model-decided skip.
+- **Team Mode doc-reviewer collapse**: `doc-reviewer` went from ~3× per card (D.2 + D.4a + D.4b) to ~1× per group — D.2 attributes findings per-card, D.4a consumes them (no re-spawn), D.4b skips its copy via the lean contract.
+
+### Added — Review Profile Selector (data-gated)
+
+- **[framework/.claude/skills/new/SKILL.md](framework/.claude/skills/new/SKILL.md)**: Phase 3.7 Step C selects `light` ⟺ (0 high-risk triggers AND QA profile ∈ {skip, light}), else `full`. `light` drops the breadth agents (qa-sentinel, api-perf-cost-auditor, doc-reviewer) + Step 3.5 CoVe but ALWAYS keeps `code-reviewer` + Codex adversarial + the false-positive gate (BUG-0530 invariant preserved — `light` ≠ skip). Mirrors the existing QA Profile Selector pattern. Ships behind a **data gate**: the mapping stays hard-coded to `full` until consumer telemetry (`docs/metrics/` Fix Application Log) confirms `light`-eligible cards have not historically produced verified BLOCKER/HIGH at full depth.
+
+## [3.34.0] - 2026-05-30
+
+Adds an **assert-active git-hooks health check** to `baldart doctor` and the `worktree-manager` verify step. A consumer had `core.hooksPath` pointing at `.git/hooks` (empty) while the repo's versioned hooks lived in `scripts/git-hooks/` — the pre-commit schema guard and pre-push were **silently inactive for days**. The existing worktree-manager verify (`git config core.hooksPath || true`) only *read* the value without asserting anything, so it never caught the drift. Same class as the LSP bug: the framework "verifies" by reading a proxy instead of asserting the real state. This moves it from read-only to assert-active. **WARN-only** — the check never mutates `core.hooksPath` (a wrong heuristic + auto-fix would be worse than the original bug); it surfaces the exact remediation command and lets the user apply it. **No new `baldart.config.yml` keys** — it's a universal, always-on, filesystem-autodetected check, so the schema-propagation rule does not apply.
+
+### Added — git-hooks health check (assert-active)
+
+- **[src/utils/githooks.js](src/utils/githooks.js)**: new, self-contained, fail-safe utility (distinct from `src/utils/hooks.js`, which manages `.claude/settings.json` hooks). `getStatus(cwd)` detects the repo's versioned-hooks directory (`.husky`, `.githooks`, `scripts/git-hooks`, `githooks` — first that exists and contains a standard-named hook), resolves the **active** hooks dir explicitly (`core.hooksPath` → relative resolved against `git rev-parse --show-toplevel`, absolute verbatim; unset → `<git-dir>/hooks`, handling the worktree `.git`-is-a-file case), and asserts the active dir serves the versioned hooks. **`git rev-parse --git-path hooks` is deliberately NOT used** — empirically it returns the configured value relative/unresolved and historically some git versions ignored `core.hooksPath` for it. Returns `checked:false` (silent, `ok:true`) when no managed hooks exist or on any error, so the check never produces a false WARN.
+- **[src/utils/githooks.js](src/utils/githooks.js)**: pure exported `isActiveServing(activeAbs, expectedAbs)` — identical-or-nested decision (covers husky v9, which sets `core.hooksPath=.husky/_` with user hooks in `.husky/`). Paths are canonicalized (symlink-resolved, handling non-existent leaves) before comparison so a symlinked ancestor (macOS `/var`→`/private/var`, symlinked repo/home) never yields a false INACTIVE. Executability (`-x`) is asserted only for raw dirs git execs directly; husky user hooks (not required `+x` in v9) skip the assert.
+- **[src/commands/doctor.js](src/commands/doctor.js)**: probe wired into `detectState` (`state.gitHooks`), a `Git hooks` line in `renderDiagnostic` (silent when `checked:false`), and an **advisory print-only** action in `planActions` (`githooks-health`) whose `run()` prints the WARN + fix command and **never mutates** `core.hooksPath` (safe under `--auto`).
+- **[framework/.claude/skills/worktree-manager/SKILL.md](framework/.claude/skills/worktree-manager/SKILL.md)**: step 4 (isolation setup) replaces the silent `git config core.hooksPath || true` read with a lean **assert** — detects the versioned-hooks dir, resolves the active dir, and echoes a loud `⚠️ WARNING` + the `git config core.hooksPath <dir>` fix on mismatch (matches husky v9 `.husky/_` and `<dir>/*` as active). The worktree shares `core.hooksPath` via `.git/commondir`, so the same resolution applies.
+
+### Tests
+
+- **[src/utils/__tests__/githooks-active.test.js](src/utils/__tests__/githooks-active.test.js)**: new — 8 pure fixtures for `isActiveServing` (the mayo bug, husky v9 nesting, identical dirs, prefix-not-a-boundary, trailing-sep normalization).
+- **[scripts/test-githooks.sh](scripts/test-githooks.sh)**: new — drives **real** git repos: misconfig (`hooksPath=.git/hooks`, hooks in `scripts/git-hooks`) → inactive + fix; correctly wired → ok; non-executable raw hook → ok=false + chmod fix; husky v9 → active, `-x` assert skipped; no managed hooks → `checked:false` (silent).
+
 ## [3.33.1] - 2026-05-30
 
 Fixes a **false-positive in the LSP layer's verify step** that let `/lsp-bootstrap` (and `baldart configure` / `doctor`) report a language server as `verified` while every real LSP call failed with `Executable not found in $PATH` — a dead layer masked by `codebase-architect`'s silent Grep fallback. Root cause was a **resolution mismatch**: verify used `npx --no-install typescript-language-server --version` (resolves from `node_modules/.bin`), but the consumer — Claude Code's LSP tool — spawns the server **by name from `$PATH`**. The npm-dev install (`npm install --save-dev`) put the binary in `node_modules/.bin`, which is *not* on `$PATH`, so verify passed and spawn failed. The npm-managed adapters now install **globally** so the binary lands on `$PATH`, and verify checks `$PATH` reachability the *same way the consumer spawns it*. **No new `baldart.config.yml` keys** — reachability is computed, not configured, so the schema-propagation rule does not apply.

package/README.md

@@ -239,7 +239,7 @@ The `ui-expert` agent is upgraded from a generic baseline to a world-class UI/UX
 
 ### LSP Symbol Search Layer (new in v3.10.0)
 
-When `features.has_lsp_layer: true`, `codebase-architect` and the code-exploration skills (`context-primer`, `bug`, `prd`, `new`, `simplify`) prefer LSP `find-references` / `go-to-definition` over Grep for identifier-shaped queries — the filtering happens **before** Claude reads files, so a common function name no longer dumps thousands of textual matches into context. Opt-in at `baldart configure`; BALDART installs the matching language servers (npm devDeps for TypeScript/Python, system commands printed for Go/Rust/Ruby). Grep remains the fallback for free-text queries and degraded states. See [`framework/agents/code-search-protocol.md`](framework/agents/code-search-protocol.md).
+When `features.has_lsp_layer: true`, `codebase-architect` and the code-exploration skills (`context-primer`, `bug`, `prd`, `new`, `simplify`) prefer LSP `find-references` / `go-to-definition` over Grep for identifier-shaped queries — the filtering happens **before** Claude reads files, so a common function name no longer dumps thousands of textual matches into context. Opt-in at `baldart configure`; BALDART installs the matching language servers (global npm install for TypeScript/Python — the binary must be on `$PATH` because Claude Code's LSP tool spawns it by name; system commands printed for Go/Rust/Ruby). Grep remains the fallback for free-text queries and degraded states. See [`framework/agents/code-search-protocol.md`](framework/agents/code-search-protocol.md).
 
 ### Commands
 

package/VERSION

@@ -1 +1 @@
-3.33.1
+3.35.0

package/framework/.claude/commands/codexreview.md

@@ -27,6 +27,48 @@ Deduplicate, then:
 
 ---
 
+## Step -0.5 — Lean Mode Detection (caller-supplied contract)
+
+`/new` invokes this skill per-card as a pre-merge gate (Phase 3.7 / Team D.4b) and passes an
+out-of-band **contract file** so it can reuse work already done in earlier phases and scale review
+depth. Detection is deterministic and applies to THIS run only.
+
+For the (single) card in scope, check for `/tmp/codexreview-lean-<CARD-ID>.json`.
+
+- **Absent** → **full mode**. This is the default for standalone `/codexreview <CARD-ID>`
+  invocations — nothing below is skipped; behave exactly as documented in Steps 0–4.
+- **Present** → parse it:
+
+  ```json
+  {
+    "profile": "light" | "full",
+    "arch_baseline_path": "/tmp/arch-baseline-<CARD-ID>.md",
+    "diff_summary_path": "<completion-report or git-diff path>",
+    "skip_doc_reviewer": true
+  }
+  ```
+
+  Apply:
+  - `arch_baseline_path` readable → **skip Step 1** (do NOT re-spawn `codebase-architect`); load the
+    baseline from that file and ALSO attach the `diff_summary_path` contents to every review agent so
+    they see what changed against the existing-architecture map. *(A1)*
+  - `skip_doc_reviewer: true` → **omit agent #4 (`doc-reviewer`)** in Step 2. Doc concerns are covered
+    by `/new` Phase 3, which runs `doc-reviewer` (with the spec/docs-drift lens) on the same diff
+    immediately before this gate. *(A2)*
+  - `profile: "light"` → ALSO omit agent #2 (`qa-sentinel`) and agent #3 (`api-perf-cost-auditor`),
+    and **skip Step 3.5 (CoVe)**. Agent #1 (`code-reviewer`), agent #5 (**Codex adversarial**), and
+    the Step 3 false-positive gate ALWAYS run. *(B1)*
+  - `profile: "full"` (or missing) → full agent set, minus #4 if `skip_doc_reviewer`.
+
+**Invariant**: lean mode NEVER suppresses the run itself — at minimum `code-reviewer` + Codex
+adversarial + Step 3 FP-gate execute on every card. If the contract file is malformed/unreadable,
+fall back to **full mode** and note it. **Consume-once**: delete `/tmp/codexreview-lean-<CARD-ID>.json`
+immediately after parsing it, so a later standalone `/codexreview <CARD-ID>` on the same card never
+inherits a stale lean contract from a prior `/new` run. Record the resolved mode in the Step 4 report
+`Method` section, e.g. `lean: profile=light, architect=reused, doc-reviewer=skipped(Phase 3), cove=skipped`.
+
+---
+
 ## Step 0 — Resolve Scope
 
 For each provided card ID:
@@ -49,6 +91,11 @@ If a card cannot be found, mark it as `UNKNOWN` and ask the user before continui
 
 ## Step 1 — Architecture Baseline (MUST)
 
+> **Lean skip (Step -0.5)**: if a contract file resolved `arch_baseline_path`, SKIP this step
+> entirely — read the baseline from that file instead of invoking `codebase-architect`, carry it
+> (plus the attached `diff_summary_path`) as the mandatory context for downstream agents, and go to
+> Step 2. In full mode (no contract file), run this step as written.
+
 Before running any review agents, invoke `codebase-architect` (via Task tool) for each card scope to map:
 
 - Existing architecture and critical patterns
@@ -96,6 +143,10 @@ Launch these agents in parallel for each card:
 4. `doc-reviewer` — spec/docs drift that can cause incorrect behavior
 5. **Codex (GPT-5.5)** — adversarial review via `codex-companion.mjs`
 
+> **Lean agent set (Step -0.5)**: when a contract file is active, launch only the agents the resolved
+> mode permits — `skip_doc_reviewer` omits #4; `profile: light` additionally omits #2 and #3. Agents
+> #1 (`code-reviewer`) and #5 (Codex) ALWAYS launch. In full mode (no contract file), launch all five.
+
 **Codex invocation rules (agent #5):**
 
 Codex is NOT invoked via the `Agent` tool (the `codex:codex-rescue` subagent_type is not registered in the harness). Instead, invoke it directly with Bash:
@@ -152,6 +203,10 @@ Only `VERIFIED` findings can be reported as bugs.
 
 ## Step 3.5 — Cross-Agent CoVe Pass (MUST — anti-echo, anti-ripple)
 
+> **Lean skip (Step -0.5)**: when the contract file resolved `profile: light`, SKIP this CoVe pass.
+> Light profile is only ever selected for 0-trigger + QA-light cards (small, non-refactor diffs)
+> where the ripple surface is minimal. Full profile (and all standalone runs) execute it as written.
+
 After Step 3 false-positive gating, the orchestrator runs ONE additional Chain-of-Verification pass on the consolidated VERIFIED pool. This catches two failure modes the per-agent CoVe doesn't:
 
 1. **Cross-agent echo allucination**: 2+ agents independently produce the same hallucinated finding (e.g. wrong file path that "looks plausible") and reinforce each other through Step 3 cross-validation.
@@ -183,7 +238,7 @@ Write one consolidated report per run to `/tmp/codexreview-report-<TIMESTAMP>.md
 Report structure:
 
 1. `Scope Reviewed`
-2. `Method` (agents used + validation flow; note whether Codex was available or `CODEX_UNAVAILABLE`; note whether Step 3.5 CoVe ran fully or hit budget cap)
+2. `Method` (agents used + validation flow; note whether Codex was available or `CODEX_UNAVAILABLE`; note whether Step 3.5 CoVe ran fully or hit budget cap; in lean mode, record the resolved contract — `lean: profile=<light|full>, architect=<reused|spawned>, doc-reviewer=<skipped(Phase 3)|run>, cove=<skipped|run>`)
 3. `Verified Bugs` (ordered: BLOCKER -> HIGH -> MEDIUM -> LOW; tag findings with `[codex]` if originating from Codex; tag `[ripple-expanded]` if Step 3.5 added `ripple_files`; tag `[cove_unverified]` if Step 3.5 budget exhausted before reaching it)
 4. `Needs Manual Confirmation`
 5. `False Positives Discarded` (with reason)

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

@@ -374,6 +374,7 @@ For each card, execute these phases in order:
    - If **FIXES NEEDED**: apply corrections to the tracker notes for this card (do NOT modify the backlog YAML). Carry the corrected requirements into the Phase 2 briefing.
    - If **PASS**: proceed.
 5. **Update tracker**: phase = "1-claim DONE", log codebase-architect key findings (1-2 lines) and plan-auditor result (PASS or corrections applied).
+5b. **Persist the architecture baseline for reuse (since v3.35.0)** — write the FULL codebase-architect findings (file paths, type signatures, patterns, high-risk paths) to `/tmp/arch-baseline-<CARD-ID>.md`. Phase 3.7's per-card `/codexreview` reuses this file instead of re-spawning `codebase-architect` (lean mode), so capture enough detail to ground a reviewer — not just the 1-2 tracker lines.
 
 ### Phase 2 — Implement (self-healing, up to 3 retries)
 6. **Update tracker**: phase = "2-implement".
@@ -1151,6 +1152,12 @@ skill's Phase 1 falls back to deriving Gherkin scenarios from
     - Check each invariant in the checklist above and flag any that are unmet
     - Flag any doc in "Related docs to check" that should be stale but isn't marked yet
     - Run your standard doc audit on all changed files
+    - **Spec/docs-drift → bug lens (MANDATORY since v3.35.0)**: flag any place where the
+      implementation contradicts a documented contract/spec in a way that can cause incorrect
+      behavior (response shape diverging from `api/<module>.md`, field semantics diverging from
+      `data-model.md`, etc.). This lens was previously exclusive to `/codexreview` agent #4; the
+      per-card Phase 3.7 gate now skips that duplicate (lean mode), so THIS pass MUST carry it.
+      Report as a doc finding with the conflicting code location + the doc it violates.
     ```
     Doc-reviewer collects findings WITHOUT making changes.
 14. **Obsidian Corpus Dispatch**: Parse section H from doc-reviewer findings. If `Trigger: YES`, dispatch the `obsidian-sync` agent (`.claude/agents/obsidian-sync.md`) with the listed paths after all fixes are applied (step 16). If `Trigger: NO`, skip. This is non-blocking -- do not wait for obsidian-sync to complete before proceeding.
@@ -1265,15 +1272,46 @@ Log the detector output in the tracker for traceability. **This step never short
 
 #### Step C — Invoke per-card `/codexreview` (ALWAYS)
 
-For EVERY card (no conditional skip):
+For EVERY card (no conditional skip — the gate ALWAYS runs; only its DEPTH varies):
+
+0. **Select the review profile (deterministic — Review Profile Selector, since v3.35.0)** from
+   signals ALREADY computed (no new thresholds):
+   - **`light`** ⟺ Step A matched **zero** high-risk triggers **AND** this card's QA profile
+     (Phase 3.5) ∈ {`skip`, `light`}.
+   - **`full`** ⟺ otherwise (any trigger matched, OR QA ∈ {`balanced`, `deep`}).
+
+   `light` is **NOT** a skip: `/codexreview` still runs `code-reviewer` + Codex adversarial + the
+   Step 3 false-positive gate. It drops only the breadth agents (qa-sentinel, api-perf-cost-auditor,
+   doc-reviewer) and Step 3.5 CoVe — exactly the passes that yield ~nothing on a 0-trigger, QA-light
+   diff. The BUG-0530 invariant ("never miss a blocker on a low-risk path") holds because the Codex
+   adversarial pass — the one that catches those — always runs.
+   **DATA GATE (BLOCKING for `light`)**: until the consumer's telemetry (`docs/metrics/` Fix
+   Application Log) confirms that `light`-eligible cards have NOT historically produced verified
+   BLOCKER/HIGH at FULL depth, hard-code `profile = full` here. Flip to the selector only after the
+   data passes (no config key — change the line).
+
+   Then dump the card diff (reviewer grounding) and write the lean contract `/codexreview` consumes:
+   ```bash
+   cd <worktree-path>
+   git diff develop...HEAD -- <card files from ownership map> > /tmp/diff-<CARD-ID>.txt 2>/dev/null \
+     || git diff HEAD~1 > /tmp/diff-<CARD-ID>.txt
+   ```
+   Write `/tmp/codexreview-lean-<CARD-ID>.json`:
+   ```json
+   { "profile": "light|full", "arch_baseline_path": "/tmp/arch-baseline-<CARD-ID>.md",
+     "diff_summary_path": "/tmp/diff-<CARD-ID>.txt", "skip_doc_reviewer": true }
+   ```
+   `skip_doc_reviewer` is ALWAYS true: Phase 3 already ran `doc-reviewer` on this diff (with the
+   spec/docs-drift→bug lens since v3.35.0), so `/codexreview` agent #4 would be a duplicate.
 
 1. **Log gate invocation** in the tracker under `## Pre-Merge Codex Review`:
 
    ```
    ## Pre-Merge Codex Review
    - Triggered: unconditional (mandatory pre-merge gate)
+   - Profile: light | full — reason: <triggers=0, qa=light | trigger #N matched | qa=deep>
    - Matched high-risk triggers: <list from detector, or "none">
-   - Action: invoking /codexreview <CARD-ID> (per-card, pre-merge gate)
+   - Action: invoking /codexreview <CARD-ID> (per-card, pre-merge gate; lean contract written)
    ```
 
 2. **Invoke `/codexreview`** for the single card via the Skill tool:
@@ -1283,7 +1321,10 @@ For EVERY card (no conditional skip):
    args: <CARD-ID>
    ```
 
-   The orchestrator's `/codexreview` skill runs all 5 review agents (incl. adversarial Codex) + Step 3 false-positive gate + Step 3.5 cross-agent CoVe + Step 4 consolidated report. This is the same pipeline used post-batch in Phase 7 — here it runs per-card and BEFORE commit.
+   `/codexreview` Step -0.5 consumes `/tmp/codexreview-lean-<CARD-ID>.json`: reuses the Phase-1
+   architecture baseline (no re-spawn), drops the duplicate doc-reviewer, and for `profile: light`
+   also drops qa-sentinel + api-perf-cost-auditor + Step 3.5 CoVe. Codex adversarial + Step 3
+   FP-gate + Step 4 report ALWAYS run. (`full` = standard pipeline minus the duplicate doc-reviewer.)
 
 3. **Read the consolidated report** from `/tmp/codexreview-report-<TIMESTAMP>.md`. Extract:
    - Verified BLOCKER count
@@ -1359,6 +1400,21 @@ Never block the pipeline indefinitely — recover and continue per the rules abo
 
 Once ALL cards are committed in the worktree:
 
+> **Final-review scope gate (deterministic, since v3.35.0)** — the per-card Phase 3.7 `/codexreview`
+> gate has ALREADY reviewed every card individually before its commit. The final review exists to
+> catch what a per-card pass structurally cannot: **cross-card interactions**. Branch on batch size:
+>
+> - **Single card (N=1)**: SKIP Steps F.1–F.4 (the lone card is byte-identical to what Phase 3.7
+>   already passed — re-review adds nothing). Log:
+>   `"Final review (F.1–F.4) skipped — single card already passed /codexreview at Phase 3.7 (PASS), code unchanged since commit"`.
+>   Then jump to **Step F.5 and RUN the final build** (`npm run lint && npx tsc --noEmit && npm run build`)
+>   — that gate is NOT skipped.
+> - **Multiple cards (N>1)**: run F.1–F.5 but **scope the review to the cross-card surface only**
+>   (computed, not discretionary) — see F.1 step 4. If that surface is empty, log
+>   `"cross-card review: no shared surface (intersection=∅, depends_on=∅) — F.3 limited to integration sanity"`
+>   and run a minimal integration pass (build + type-check across the union) instead of a full
+>   per-line re-review. This is a computed scope reduction, NEVER a model-decided skip.
+
 ### Step F.1 — Resolve scope
 
 1. **Read the tracker file** to get the full picture: card IDs, files changed, commit hashes.
@@ -1368,7 +1424,11 @@ Once ALL cards are committed in the worktree:
    git diff --name-only <base-branch>...HEAD
    ```
 3. Read each card's backlog YAML to collect `acceptance_criteria`, `files_likely_touched`.
-4. Build `review_scope_files` as union of card-indicated files + git-touched files.
+4. Build `review_scope_files` as union of card-indicated files + git-touched files. **For N>1 (per
+   the Final-review scope gate above), then REDUCE `review_scope_files` to the cross-card subset**:
+   files appearing in ≥2 cards' File Ownership Map entries ∪ files of any `depends_on`-linked card
+   pair. Record both the full union and the reduced set in the tracker; downstream F.3 reviews the
+   reduced set.
 
 ### Step F.2 — Architecture baseline
 
@@ -2020,6 +2080,11 @@ Return: file paths, type signatures, existing patterns. Max 30 lines.
 
 This is the ONLY context the orchestrator accumulates per group. After passing it to the coders, it can be purged.
 
+**Persist for review reuse (since v3.35.0)** — also write these findings to
+`/tmp/arch-baseline-group-<FIRST-CARD-ID>.md`. D.4b's per-card `/codexreview` lean contract points
+its `arch_baseline_path` at this file, so the review reuses the group baseline instead of re-spawning
+`codebase-architect`.
+
 #### Step B: Spawn parallel coder agents
 
 For each card in the current group, spawn a coder agent using the Agent tool. ALL agents for the group MUST be spawned in a **SINGLE message** (multiple Agent tool calls) to run truly in parallel.
@@ -2112,7 +2177,7 @@ After ALL agents in the group complete successfully:
 
 1. **D.1 — Build verification (group)** — Run `npm run build` in the worktree to verify combined changes compile. If build fails, identify which card's changes broke it (from `git diff` per card), spawn a targeted fix-coder for those files only.
 
-2. **D.2 — Combined static review (group)** — Invoke **code-reviewer** + **doc-reviewer** IN PARALLEL (read-only, same as Phase 3) across ALL changes in the group. This is ONE combined review, not per-card — efficient and catches cross-card issues. Per-card doc-review still runs in D.4a.
+2. **D.2 — Combined static review (group)** — Invoke **code-reviewer** + **doc-reviewer** IN PARALLEL (read-only) across ALL changes in the group. ONE combined pass — catches cross-card issues. The doc-reviewer MUST **attribute every finding to a specific card** (by file → ownership map) and apply the full Phase 3 mandate INCLUDING the spec/docs-drift→bug lens (since v3.35.0), so this single pass satisfies each card's doc gate. D.4a consumes these per-card findings (no second doc-reviewer spawn).
 
 3. **D.3 — Apply fixes (group)** — If D.2 findings exist, spawn ONE fix-coder to apply all fixes in a single pass. Run build + lint after.
 
@@ -2124,9 +2189,9 @@ After ALL agents in the group complete successfully:
 
 4. **D.4 — QA gate (group)** — Select the HIGHEST QA profile across all cards in the group (e.g., if one card is BALANCED and another is DEEP, use DEEP). Invoke **qa-sentinel** once for the group.
 
-4a. **D.4a — Phase 3 Doc Review per-card** — For EACH card in the group, invoke `doc-reviewer` scoped to that card's File Ownership Map + card YAML (mirrors Phase 3 of the sequential path). If findings exist, spawn a targeted fix-coder for that card only. This is in addition to the combined D.2 doc-reviewer pass — D.2 catches cross-card issues, D.4a verifies each card meets its own doc gate before commit.
+4a. **D.4a — Per-card doc gate (consumes D.2, since v3.35.0)** — Do NOT re-spawn `doc-reviewer`. For EACH card in the group, take that card's doc findings from D.2's per-card-attributed output; if any exist, spawn a targeted fix-coder for that card only. (Previously D.4a re-ran doc-reviewer per card — a duplicate of D.2; collapsed to a single attributed D.2 pass. D.4b's per-card `/codexreview` also skips its doc-reviewer via the lean contract, so doc-review now runs once per group instead of ~3× per card.)
 
-4b. **D.4b — Pre-Merge Codex Review Gate (per-card, MANDATORY — UNCONDITIONAL)** — Invoke `/codexreview` for EACH card in the group, one at a time, BEFORE any commit. This mirrors Phase 3.7 of the sequential path and is non-skippable regardless of file paths or perceived risk. Apply the same fix sub-loop: if the consolidated report shows verified BLOCKER/HIGH findings, spawn a fix-coder and re-run `/codexreview <CARD-ID>` (max 2 retries per card). If still BLOCKER/HIGH after retries, ask the user before proceeding to D.5. The D.5 commits MUST NOT happen until every card in the group has a PASS verdict (or explicit user override via `AskUserQuestion`). Log results in the tracker under `## Pre-Merge Codex Review` per card.
+4b. **D.4b — Pre-Merge Codex Review Gate (per-card, MANDATORY — UNCONDITIONAL)** — Invoke `/codexreview` for EACH card in the group, one at a time, BEFORE any commit. This mirrors Phase 3.7 of the sequential path and is non-skippable regardless of file paths or perceived risk. Apply the same fix sub-loop: if the consolidated report shows verified BLOCKER/HIGH findings, spawn a fix-coder and re-run `/codexreview <CARD-ID>` (max 2 retries per card). If still BLOCKER/HIGH after retries, ask the user before proceeding to D.5. The D.5 commits MUST NOT happen until every card in the group has a PASS verdict (or explicit user override via `AskUserQuestion`). Log results in the tracker under `## Pre-Merge Codex Review` per card. **Lean + profile (since v3.35.0)**: before each card's `/codexreview`, apply the same Review Profile Selector and write the same `/tmp/codexreview-lean-<CARD-ID>.json` contract as sequential Phase 3.7 Step C — `arch_baseline_path` pointing at `/tmp/arch-baseline-group-<FIRST-CARD-ID>.md`, `skip_doc_reviewer: true`, and `profile: light|full` from (0 triggers + QA ∈ {skip,light}). LIGHT still runs Codex adversarial + code-reviewer + FP-gate (subject to the same DATA GATE: keep `full` until telemetry confirms).
 
 5. **D.5 — Commit** — One commit per card using explicit staging from the ownership map. **NO stash in worktrees** (stashes are globally shared via `refs/stash` — see Phase 4 WORKTREE COMMIT RULE):
    ```bash
@@ -2178,7 +2243,7 @@ Before starting group N, verify ALL cards in groups 0..N-1 are status: done. If
 
 ### Post-batch (same as sequential mode)
 
-After all groups are complete, run the same Final Review, Phase 6 (merge), and Phase 7 (production readiness) as documented above. No changes needed for these phases.
+After all groups are complete, run the same Final Review, Phase 6 (merge), and Phase 7 (production readiness) as documented above. Team mode is always N>1, so the Final Review applies its deterministic **cross-card-only scope** (per the Final-review scope gate) — not a full per-line re-review.
 
 ---
 

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

@@ -411,8 +411,32 @@ else
   echo "PORT=$PORT" >> .env.local
 fi
 
-# 5. Verify husky hooks work (they share via .git/commondir)
-git config core.hooksPath || true
+# 5. ASSERT git hooks are ACTIVE — not just readable.
+#    The worktree shares core.hooksPath via .git/commondir, so the same
+#    resolution applies here as in the main checkout. Reading the value
+#    (the old `git config core.hooksPath || true`) is NOT enough: it never
+#    catches the failure mode where core.hooksPath points at an empty dir
+#    while the repo's versioned hooks live elsewhere (pre-commit / pre-push
+#    silently inactive). Detect the versioned-hooks dir and assert it is served.
+HOOK_SRC=""
+for d in .husky .githooks scripts/git-hooks githooks; do
+  if [ -d "$d" ] && ls "$d" 2>/dev/null | grep -qE '^(pre-commit|pre-push|commit-msg)$'; then
+    HOOK_SRC="$d"; break
+  fi
+done
+if [ -n "$HOOK_SRC" ]; then
+  ACTIVE="$(git config --get core.hooksPath || echo .git/hooks)"
+  # Lean literal-string match (HOOK_SRC is relative). Full path resolution +
+  # canonicalization lives in `baldart doctor` (src/utils/githooks.js); an
+  # absolute core.hooksPath here would warn spuriously — rare, run doctor to confirm.
+  case "$ACTIVE" in
+    "$HOOK_SRC"|"$HOOK_SRC"/*|.husky/_) : ;;  # active dir serves the versioned hooks (incl. husky v9 .husky/_)
+    *)
+      echo "⚠️  WARNING: git hooks INATTIVI — gli hook versionati sono in '$HOOK_SRC' ma core.hooksPath = '$ACTIVE'." >&2
+      echo "    Esegui per riattivarli:  git config core.hooksPath $HOOK_SRC" >&2
+      ;;
+  esac
+fi
 ```
 
 ### 5. Verify baseline

package/package.json

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

package/src/commands/doctor.js

@@ -30,6 +30,7 @@ const GitUtils = require('../utils/git');
 const UI = require('../utils/ui');
 const State = require('../utils/state');
 const Hooks = require('../utils/hooks');
+const GitHooks = require('../utils/githooks');
 const LspInstaller = require('../utils/lsp-installer');
 const UpdateNotifier = require('../utils/update-notifier');
 const cliPackageJson = require('../../package.json');
@@ -234,6 +235,16 @@ async function detectState(cwd, opts = {}) {
       }
     } catch (_) {}
 
+    // ---- Git-hooks health (since v3.34.0) ------------------------------
+    // Assert that the repo's versioned git hooks (pre-commit/pre-push/…) are
+    // actually being run — i.e. `core.hooksPath` resolves to the directory
+    // that holds them. A drift here (e.g. core.hooksPath=.git/hooks while the
+    // hooks live in scripts/git-hooks/) silently disables every hook. Distinct
+    // from the BALDART `.claude/settings.json` hooks probed above. Fully
+    // fail-safe: `checked:false` when no managed hooks exist or on any error.
+    state.gitHooks = { checked: false, ok: true };
+    try { state.gitHooks = GitHooks.getStatus(cwd); } catch (_) {}
+
     // ---- Agent symlink integrity (since v3.20.0) -----------------------
     // Source of truth for the BALDART agent list is the framework filesystem
     // directory itself (`.framework/framework/.claude/agents/*.md`). For each
@@ -503,6 +514,28 @@ function planActions(state) {
     });
   }
 
+  // Git-hooks health (since v3.34.0). ADVISORY ONLY — the action's run() never
+  // mutates `core.hooksPath` (a wrong heuristic + auto-fix is worse than the
+  // original silent-inactive bug). It surfaces the WARN + the exact remediation
+  // command so the user applies it deliberately. Present as an action (rather
+  // than a bare table WARN) so `doctor` doesn't contradict it with "Nothing to
+  // do". Safe to run in --auto since it only prints.
+  if (state.gitHooks && state.gitHooks.checked && !state.gitHooks.ok) {
+    actions.push({
+      key: 'githooks-health',
+      label: state.gitHooks.inactive
+        ? `Git hooks INACTIVE — ${state.gitHooks.source} hooks in ${state.gitHooks.expectedDir} are not being run`
+        : `Git hooks not executable — ${state.gitHooks.nonExecutable.join(', ')}`,
+      why: `${state.gitHooks.detail}. Fix: ${state.gitHooks.fixCommand}`,
+      autoOk: true, // advisory print-only; run() does NOT mutate config
+      run: () => {
+        UI.warning(state.gitHooks.detail);
+        UI.info('Run to re-activate the repo\'s versioned git hooks:');
+        console.log(`    ${state.gitHooks.fixCommand}`);
+      },
+    });
+  }
+
   // Agent symlink integrity (since v3.20.0). Re-runs the agent merge loop to
   // recreate any missing per-agent symlink. Calls `SymlinkUtils.mergeAgents`
   // directly rather than dispatching to `update` — we want only the symlink
@@ -787,6 +820,29 @@ function renderDiagnostic(state) {
       console.log(`   • pre-v3.18: ${state.hooksLegacy.join(', ')}`);
   }
 
+  // Git-hooks health (v3.34.0+). Silent when no versioned-hooks dir exists
+  // (`checked:false`) — most consumers have no managed git hooks and must see
+  // zero noise here.
+  if (state.gitHooks && state.gitHooks.checked) {
+    if (state.gitHooks.ok) {
+      console.log(statusLine(
+        'Git hooks',
+        `${state.gitHooks.source} active (${state.gitHooks.expectedHooks.join(', ')})`,
+        'ok'
+      ));
+    } else if (state.gitHooks.inactive) {
+      console.log(statusLine(
+        'Git hooks',
+        `INACTIVE — ${state.gitHooks.source} hooks in ${state.gitHooks.expectedDir} not run by core.hooksPath`,
+        'warn'
+      ));
+      console.log(`   • fix: ${state.gitHooks.fixCommand}`);
+    } else {
+      console.log(statusLine('Git hooks', state.gitHooks.detail, 'warn'));
+      console.log(`   • fix: ${state.gitHooks.fixCommand}`);
+    }
+  }
+
   if (state.frameworkIgnored && state.frameworkIgnored.ignored) {
     console.log(statusLine(
       '.gitignore',

package/src/utils/__tests__/githooks-active.test.js

@@ -0,0 +1,63 @@
+#!/usr/bin/env node
+/**
+ * Fixture-driven test for the git-hooks active-vs-expected decision.
+ *
+ * Run: node src/utils/__tests__/githooks-active.test.js
+ * Exits 0 on success, 1 on any mismatch (CI-friendly).
+ *
+ * `isActiveServing` is the one decision that, if wrong, silently invalidates
+ * the entire git-hooks health check (src/utils/githooks.js). It is pure (path
+ * logic only) so it is fully unit-testable without a live repo — covering the
+ * husky-version branches that fs/git probing can't easily exercise.
+ */
+const path = require('path');
+const { isActiveServing } = require('../githooks');
+
+// Absolute roots so the fixtures don't depend on cwd. Normalize through
+// path.resolve the same way the implementation does.
+const ROOT = path.resolve('/repo');
+const j = (...p) => path.join(ROOT, ...p);
+
+const FIXTURES = [
+  // ─── the mayo bug: core.hooksPath=.git/hooks, hooks in scripts/git-hooks ──
+  { active: j('.git', 'hooks'), expected: j('scripts', 'git-hooks'), want: false, note: 'mayo: inactive' },
+
+  // ─── husky v9: active=.husky/_ wrappers, user hooks in .husky ─────────────
+  { active: j('.husky', '_'),   expected: j('.husky'),               want: true,  note: 'husky v9 nested' },
+  // ─── husky v5-v8: core.hooksPath=.husky, hooks in .husky ──────────────────
+  { active: j('.husky'),        expected: j('.husky'),               want: true,  note: 'husky v8 identical' },
+
+  // ─── scripts convention, correctly wired ─────────────────────────────────
+  { active: j('scripts', 'git-hooks'), expected: j('scripts', 'git-hooks'), want: true, note: 'scripts identical' },
+
+  // ─── .githooks convention, wired to default .git/hooks (inactive) ─────────
+  { active: j('.git', 'hooks'), expected: j('.githooks'),            want: false, note: '.githooks inactive' },
+
+  // ─── reverse nesting (expected within active) also counts as serving ──────
+  { active: j('.husky'),        expected: j('.husky', '_'),          want: true,  note: 'reverse nesting' },
+
+  // ─── sibling dirs sharing a prefix must NOT match (prefix-not-boundary) ───
+  { active: j('hooks'),         expected: j('hooks-extra'),          want: false, note: 'prefix not a path boundary' },
+
+  // ─── trailing-slash / non-normalized inputs normalize equal ──────────────
+  { active: j('.husky') + path.sep, expected: j('.husky'),           want: true,  note: 'trailing sep normalized' },
+];
+
+let failures = 0;
+for (const f of FIXTURES) {
+  const got = isActiveServing(f.active, f.expected);
+  const ok = got === f.want;
+  if (!ok) {
+    failures++;
+    console.error(`✗ ${f.note}: isActiveServing(${f.active}, ${f.expected}) = ${got}, expected ${f.want}`);
+  } else {
+    console.log(`✓ ${f.note}`);
+  }
+}
+
+if (failures) {
+  console.error(`\n${failures} failure(s).`);
+  process.exit(1);
+}
+console.log(`\nAll ${FIXTURES.length} fixtures passed.`);
+process.exit(0);

package/src/utils/githooks.js

@@ -0,0 +1,233 @@
+/**
+ * Git-hooks health check — **assert-active**, not read-only.
+ *
+ * NOT to be confused with `src/utils/hooks.js`: that module manages the Claude
+ * Code hooks registered in `.claude/settings.json`. THIS module inspects the
+ * repo's own *git* hooks (pre-commit, pre-push, …) and asserts they are
+ * actually being executed by git — i.e. that `core.hooksPath` resolves to the
+ * directory where the repo's versioned hooks live.
+ *
+ * **Why it exists** (since v3.34.0)
+ *
+ * A consumer had `core.hooksPath` pointing at `.git/hooks` (empty) while the
+ * repo's real, versioned hooks lived in `scripts/git-hooks/`. Result: the
+ * pre-commit schema guard and pre-push were silently inactive for days, and
+ * the worktree-manager verify step (`git config core.hooksPath || true`) only
+ * *read* the value without asserting anything — so it never caught the drift.
+ * Same class as the LSP bug: the framework "verifies" by reading a proxy
+ * instead of asserting the real state. This moves it from read-only to
+ * assert-active.
+ *
+ * **Resolution of the active hooks dir** (the crux)
+ *
+ * `git rev-parse --git-path hooks` is NOT used: empirically it returns the
+ * configured value *relative and unresolved*, and historically some git
+ * versions ignored `core.hooksPath` for `--git-path` entirely. Instead we
+ * resolve explicitly:
+ *   - `core.hooksPath` set      → relative resolves against the working-tree
+ *                                 top (`git rev-parse --show-toplevel`),
+ *                                 absolute is used verbatim.
+ *   - `core.hooksPath` unset    → `<git rev-parse --git-dir>/hooks` (handles
+ *                                 the worktree case where `.git` is a file).
+ *
+ * **Design invariants**
+ *
+ *   - Fail-safe: every probe is wrapped; any internal error yields
+ *     `{ checked: false, ok: true }` so the check NEVER blocks legitimate work
+ *     and never produces a false WARN.
+ *   - Silent when nothing to assert: a repo with no versioned-hooks directory
+ *     returns `checked: false` (most consumers have no managed hooks).
+ *   - No config flag: this is a universal, always-on health check auto-detected
+ *     from the filesystem, so the schema-change-propagation rule does not apply.
+ *   - WARN only: this module never mutates `core.hooksPath`. It reports a
+ *     `fixCommand` string; applying it is the caller's (user's) decision.
+ */
+
+const fs = require('fs');
+const path = require('path');
+const { execFileSync } = require('child_process');
+
+// Standard git hook filenames. A managed-hooks directory is recognized by
+// containing at least one of these (husky places them at `.husky/<name>`,
+// raw dirs at `<dir>/<name>`).
+const STANDARD_HOOKS = [
+  'pre-commit', 'pre-push', 'commit-msg', 'prepare-commit-msg',
+  'pre-rebase', 'pre-merge-commit', 'post-checkout', 'post-commit',
+  'post-merge', 'post-rewrite', 'pre-applypatch', 'applypatch-msg',
+];
+
+// Candidate versioned-hooks directories, in priority order. The first that
+// exists AND contains a standard-named hook wins. `scripts/git-hooks` and
+// `githooks` are conventions (not universal) — we enumerate a small known set
+// rather than guess.
+const MANAGED_DIRS = [
+  { dir: '.husky',            source: 'husky' },
+  { dir: '.githooks',         source: 'githooks' },
+  { dir: 'scripts/git-hooks', source: 'scripts' },
+  { dir: 'githooks',          source: 'githooks' },
+];
+
+function git(cwd, args) {
+  return execFileSync('git', args, {
+    cwd,
+    encoding: 'utf8',
+    stdio: ['ignore', 'pipe', 'ignore'],
+  }).trim();
+}
+
+/**
+ * Find the repo's versioned-hooks directory, or null when none is managed.
+ * @returns {{ dir: string, abs: string, source: string, hooks: string[] } | null}
+ */
+function detectExpected(cwd) {
+  for (const cand of MANAGED_DIRS) {
+    const abs = path.join(cwd, cand.dir);
+    let names = [];
+    try {
+      if (!fs.statSync(abs).isDirectory()) continue;
+      names = fs.readdirSync(abs).filter((f) => STANDARD_HOOKS.includes(f));
+    } catch (_) { continue; }
+    if (names.length) return { dir: cand.dir, abs, source: cand.source, hooks: names };
+  }
+  return null;
+}
+
+/**
+ * Resolve the directory git will actually look in for hooks.
+ * @returns {{ configured: string | null, abs: string }}
+ */
+function resolveActiveDir(cwd) {
+  let configured = null;
+  try { configured = git(cwd, ['config', '--get', 'core.hooksPath']) || null; } catch (_) {}
+
+  if (configured) {
+    if (path.isAbsolute(configured)) return { configured, abs: configured };
+    // Relative core.hooksPath resolves against the working-tree top, not cwd.
+    let top = cwd;
+    try { top = git(cwd, ['rev-parse', '--show-toplevel']); } catch (_) {}
+    return { configured, abs: path.resolve(top, configured) };
+  }
+
+  // Unset → <git-dir>/hooks. git-dir may be relative or a worktree gitdir.
+  let gitDir;
+  try { gitDir = git(cwd, ['rev-parse', '--git-dir']); } catch (_) { gitDir = path.join(cwd, '.git'); }
+  if (!path.isAbsolute(gitDir)) gitDir = path.resolve(cwd, gitDir);
+  return { configured: null, abs: path.join(gitDir, 'hooks') };
+}
+
+/**
+ * Resolve a path to its canonical (symlink-free) form so two paths computed
+ * from different bases compare correctly. The active dir (from git's
+ * realpath-resolved toplevel/git-dir) and the expected dir (from cwd) can
+ * otherwise differ purely by a symlinked ancestor — e.g. macOS `/var` →
+ * `/private/var`, or a symlinked repo/home path — yielding a false INACTIVE.
+ *
+ * Handles non-existent leaves (the active `.git/hooks` may not exist on a
+ * misconfigured repo): realpath the deepest existing ancestor, re-append the
+ * rest. Falls back to a plain resolve if nothing along the path is realpath-able.
+ */
+function canonicalize(p) {
+  let dir = path.resolve(p);
+  const tail = [];
+  for (;;) {
+    try {
+      const real = fs.realpathSync(dir);
+      return tail.length ? path.join(real, ...tail) : real;
+    } catch (_) {
+      const parent = path.dirname(dir);
+      if (parent === dir) return path.resolve(p); // reached fs root
+      tail.unshift(path.basename(dir));
+      dir = parent;
+    }
+  }
+}
+
+/**
+ * PURE decision: is the active hooks dir serving the versioned hooks?
+ *
+ * True when the two dirs are identical OR one is nested within the other.
+ * The nesting case covers husky v9, which sets `core.hooksPath=.husky/_`
+ * (wrappers) while the user hooks live in `.husky/`. Exported for unit tests —
+ * this is the one decision that, if wrong, silently invalidates the whole check.
+ */
+function isActiveServing(activeAbs, expectedAbs) {
+  const a = path.resolve(activeAbs);
+  const e = path.resolve(expectedAbs);
+  if (a === e) return true;
+  return a.startsWith(e + path.sep) || e.startsWith(a + path.sep);
+}
+
+/**
+ * Inspect the repo's git-hooks health. Fail-safe.
+ * @returns {{
+ *   checked: boolean, ok: boolean, source: string|null, configured: string|null,
+ *   activeDir: string|null, expectedDir: string|null, expectedHooks: string[],
+ *   inactive: boolean, nonExecutable: string[], detail: string, fixCommand: string|null
+ * }}
+ */
+function getStatus(cwd = process.cwd()) {
+  const result = {
+    checked: false,
+    ok: true,
+    source: null,
+    configured: null,
+    activeDir: null,
+    expectedDir: null,
+    expectedHooks: [],
+    inactive: false,
+    nonExecutable: [],
+    detail: '',
+    fixCommand: null,
+  };
+
+  try {
+    const expected = detectExpected(cwd);
+    if (!expected) return result; // no managed hooks → silent, ok
+
+    const active = resolveActiveDir(cwd);
+    result.checked = true;
+    result.source = expected.source;
+    result.configured = active.configured;
+    result.activeDir = active.abs;
+    result.expectedDir = expected.dir;
+    result.expectedHooks = expected.hooks;
+
+    // Canonicalize both ends before comparing — they're computed from different
+    // bases (git realpath vs cwd) and a symlinked ancestor would otherwise
+    // produce a false INACTIVE.
+    if (!isActiveServing(canonicalize(active.abs), canonicalize(expected.abs))) {
+      result.inactive = true;
+      result.ok = false;
+      result.fixCommand = `git config core.hooksPath ${expected.dir}`;
+      result.detail = `core.hooksPath risolve a ${active.abs} ma gli hook versionati sono in ${expected.dir}`;
+      return result;
+    }
+
+    // Executability assert — only for raw dirs git execs directly. Husky sources
+    // user hooks via its `_` wrappers and v9 does NOT require them to be +x, so
+    // asserting -x there would manufacture false positives.
+    if (expected.source !== 'husky') {
+      for (const h of expected.hooks) {
+        try { fs.accessSync(path.join(expected.abs, h), fs.constants.X_OK); }
+        catch (_) { result.nonExecutable.push(h); }
+      }
+      if (result.nonExecutable.length) {
+        result.ok = false;
+        result.detail = `hook non eseguibili (manca il bit -x): ${result.nonExecutable.join(', ')}`;
+        result.fixCommand = `chmod +x ${result.nonExecutable.map((h) => path.join(expected.dir, h)).join(' ')}`;
+      }
+    }
+
+    return result;
+  } catch (_) {
+    // Never block doctor / worktree verify on a probe failure.
+    return { ...result, checked: false, ok: true };
+  }
+}
+
+module.exports = { getStatus, isActiveServing };
+// Exposed for completeness / advanced callers and unit tests.
+module.exports.detectExpected = detectExpected;
+module.exports.resolveActiveDir = resolveActiveDir;
+module.exports.STANDARD_HOOKS = STANDARD_HOOKS;
+module.exports.MANAGED_DIRS = MANAGED_DIRS;