Merge chore/correct-blk022-flaky-baseline into develop

I recorded "92/14 on pristine develop vs 93/13 after — nothing worsened, one
case better". Three consecutive runs on one unchanged tree give 90/16, 92/14,
92/14: the suite is non-deterministic and both figures were single samples of
that spread. The port is indistinguishable from the noise; claiming an
improvement was false precision.

Surfaced because the post-merge run reported 90/16 and looked like a
regression. It was not — but the only reason the question could be settled
was re-running, which is exactly what the original claim had skipped.

.claude/audits/DARWIN-2026-08-26.md

@@ -0,0 +1,90 @@
+# Darwin run 2026-08-25/26: fresh baseline + threshold optimization + bug pass
+
+Branch `feature/darwin-optimize-20260825`, 26 commits, 39 files, +299/-142.
+Log: `~/.agents/skills/darwin-skill/results.tsv` (fresh, the May file was wiped
+by the 2026-06-23 reinstall). Method: darwin v2.1. Absolute scores served as
+triage only; every keep/revert decision came from a paired same-judge majority
+(3 judges per round, before/after read in one call).
+
+## Scope
+
+54 units: 31 personal skill-systems (SKILL.md + dispatched agents judged
+together, per EVAL-004) and 23 agents. Excluded: gstack/external symlinks
+(BDR-015/043, LRN-070), darwin-skill itself (BDR-058 pin), and find-docs,
+newly identified as machine-owned ctx7 output (gitignored, installer-written).
+
+## Baseline (7 blind judges, dims scored 1-10, totals recomputed main-thread per LRN-018)
+
+Mean 83.4 (skills 83.5, agents 83.3). Best: deploy, release-candidate,
+release-executor (90.4). Worst: skills-perso 63.5. All dim8 rows marked
+dry_run by design; live execution happened later, inside the paired rounds.
+13 units scored below the user-set threshold of 80.
+
+## Phase 2: threshold loop, 13/13 units, 0 reverts
+
+Every round was validated by 3 paired judges (neutral, skeptic, realism).
+All verdicts 3-0 better.
+
+| Unit (baseline) | Round(s) | What changed |
+|---|---|---|
+| skills-perso (63.5) | d8 | Detection rebuilt on the link.sh convention: symlink = external, real dir = personal, gitignored = machine-generated. Live result 8/31 to 31/31, zero false positives |
+| interviewer (70.9) | d3, d9 | Failure-mode table (vague, "you decide", contradiction, partial, balloon) + 2-round budget; DO-NOT list |
+| onboarder (71.5) | d8 | BRIEF contract split REQUIRED/OPTIONAL; null enrichment becomes TODO placeholders; STOP kept for required keys and unresolved monorepo. Kills the guaranteed first-dispatch bounce vs /onboard STEP 2 |
+| pdf-translate (72.3) | d3/d8 | 8-row failure table: deps, >30 pages gate, zero-output, illisible markers, design-html/browse fallbacks, QA cap 2, stale workdir |
+| refactor (75.6) + refactorer (76.8) | d4/d3 | No-tests STOP gate + GO-WITHOUT-TESTS arbitration in the dispatcher; mid-run test-failure revert protocol; code-cleaner inline carve-out |
+| profile (77.3) | d3 | 6-row failure table, every row fact-checked against profile.sh (rc=1 paths, partial toggle, split plugin leg, BLK-006 contradiction); fixture de-drift |
+| plugin-probe (78.5) + plugin-advisor (77.5) | d8 | FRAMEWORK-DEPS now exact dep@version (preact false-hit killed, fallback actually fires; the old `\|\| true` silently emitted nothing and tripped the advisor's fail-closed path on non-Node projects); frontend/fast-libs derivable; PLAN echoed-or-unknown, invention removed |
+| analyze (77.7) + analyzer (78.0) | d1, d2 | Bilingual triggers + fix-wanted disambiguator; TASKS ordered, each step mapped to its OUTPUT section |
+| status-reporter (78.0) | d5 x2 | Fabrication-forcing token field replaced, then restored producibly from doctor.sh constants (a skeptic judge found the source); dead ROADMAP row rewritten post-ADR-013 |
+| gitflow (78.4) | d3 | 7-row failure table keyed to lib return codes; rc=4 conflict resume empirically verified; human merge gate untouched |
+
+## Bug pass: verified defects in above-threshold units, 8 commits, all kept 3-0
+
+- hotfix: `git restore .` on every failure branch wiped tolerated in-progress
+  user edits. Now: `git stash create` pre-flight snapshot + file-scoped
+  restore + fresh-dispatch-only security gate. Two skeptic residuals amended
+  (RULES bullet, FILE(S) new-file marker).
+- init-project: allowed-tools lacked Agent and Skill while every step
+  dispatches. commit-change: conflict grep now covers all 7 unmerged codes.
+  tour: --report-only no longer commits (could land on develop).
+- harden: severity rule now defers to the calibrated guide; the late SSL Labs
+  grade has an assigned actor.
+- plan-challenger: ERROR joined the load-bearing verdict grammar.
+- handover writers: stale chapter refs corrected (glossary/tone to §6,
+  cross-links and THRESHOLD-OVERRIDE to §5); STEP 14.5 verification deferred
+  post-write; anchor gate ordered into STEP 16.
+- security-auditor: /hotfix no-verifier carve-out documented. close: STEP 5C
+  enumerated, --no-push passthrough added.
+- prune-memory: false "v1-untested" note replaced by the real tests/ state.
+  code-clean: executor attribution corrected (code-cleaner, refactorer inline).
+- Fixtures de-drifted: plugin-check (PLUGIN CHECK block, real plugin names),
+  onboard (nextjs-app-router).
+
+`make test` green (0 RED, rc=0) after one census rewrap: a locked phrase had
+been line-wrapped and the single-line grep lock caught it.
+
+## Residual findings, logged not fixed
+
+- analyze triggers: "how does X work" brushes graphify's territory; graphify's
+  graph-exists routing still wins.
+- pdf-translate: pdfinfo row assumes poppler (fitz also has page count); "GB"
+  slightly overstated near the 30-page gate.
+- web-validate: .validate-cache mkdir lives in a skipped STEP 0
+  (self-recoverable); axis budgets 35/25/40 never reconciled with the base-100
+  deduction table. seo/geo minor wording items. verifier/doc-syncer/audit-delta
+  restatement redundancy (cosmetic). handover-doc-writer STEP 14.5 umbrella
+  line still says "BEFORE STEP 15" while the inner note overrides it.
+- bugfix trivial-fast-path boundary loosely defined; feat prompt-3 expectation
+  vs full gate pipeline.
+
+## Methodology notes
+
+- v2.1 paired majority produced 36 unit-round verdicts and 24 batch verdicts,
+  all better, 0 reverts, 0 ties. The May-2026 run under absolute-delta scoring
+  had reverted 2 edits on judge noise; this run had no such event.
+- Judges live-executed wherever the artifact was executable (skills-perso
+  detection, profile.sh probes, plugin grep on scratch manifests, doctor.sh
+  grep, git merge no-op resume). Behavior outranked prose in 5 units.
+- Two grep-exit-masking bugs surfaced (a `head` pipe swallowing the fallback's
+  trigger), one in the probe being fixed, one in this run's own test harness.
+  The pattern is worth a learning entry.

.claude/memory/blockers.md

@@ -36,6 +36,9 @@ rules:
 | BLK-014 | 2026-07-01 | `make install` aborts npm EEXIST on `~/.local/bin/claude` when claude already installed via native installer — no presence guard | resolved |
 | BLK-015 | 2026-07-03 | `gitflow_finish` ignored its `<type> <name>` args → merged the CHECKED-OUT branch not the one named → wrong-branch merge (audit LOT3) | resolved |
 | BLK-016 | 2026-07-04 | rtk compression PATH-dead 30 days — 6/5070 Bash commands compressed (~460K tokens missed); installer sources cargo env so its own check passes, Claude tool shell never gets ~/.cargo/bin | resolved |
+| BLK-017 | 2026-07-17 | Bing Webmaster API unusable for a multi-client agency: OAuth swamp (localhost redirect refused, rotated single-use refresh tokens race our parallel dispatch), API key = wrong model (client-owned sites) | open/deferred |
+| BLK-021 | 2026-09-13 | gstack Chromium install hangs forever on macOS: Playwright 1.58.2 deadlocks on Node 26 mid-extraction (39/333 files, all threads idle) | resolved |
+| BLK-022 | 2026-09-13 | macOS bash 3.2 + BSD userland: six silent defects, most fail-OPEN (SSRF guard, commit scope guards, gate criteria) | resolved |
 
 ---
 
@@ -115,6 +118,7 @@ rules:
 - **2026-06-23 UPDATE — Solution REVERTED, status downgraded to UPSTREAM/open** (commit b9c3937): the `PLAYWRIGHT_HOST_PLATFORM_OVERRIDE` solution above does NOT work on 26.04. The fallback build downloads to 100% then HANGS at extraction (chrome binary never appears, no headless-shell download starts; reproduced on real machine + sandbox) → turned a 0.5s fast-fail into an install-blocking hang (user Ctrl+C). Reverted to the fast-fail (non-fatal; gstack OFF by default, browser only for /browse,/qa,screenshots). The earlier "verified ldd + headless render" was an isolated test on a sibling already-extracted build (rev 1228) — it masked the rev-1208 install-path hang. **Real fix = upstream**: gstack bumps Playwright to a version that lists ubuntu26.04. Until then gstack's browser is unavailable on 26.04, install completes cleanly. See [[LRN-038]] correction.
 
 - **2026-06-23 FINAL — RESOLVED** (commit 3b8ffb1): gstack browser now works on Ubuntu 26.04. Two layers fixed: (1) bumped gstack's pinned Playwright 1.58.2 → 1.61 (`bun add playwright@latest` in the submodule; 1.61 ships a native ubuntu26.04 build — chromium rev 1228), automated in the installer (`gstack_bump_playwright_if_unsupported`, idempotent, OS-gated); (2) `GSTACK_CHROMIUM_NO_SANDBOX=1` to work around the AppArmor userns restriction (`sysctl kernel.apparmor_restrict_unprivileged_userns=1`), persisted to `.bashrc` + installer Step 9 (sysctl-gated). Verified end-to-end: `browse goto https://example.com` → "Navigated (200)". Caveat: the Playwright bump is a local submodule edit, reset by `git submodule update`, re-applied by the next install. See [[BDR-029]], [[LRN-040]].
+- **2026-09-13 CORRECTION — the diagnosis above is wrong, the fix was right**: the rev-1208 "downloads 100% then HANGS at extraction" was imputed to the `ubuntu24.04` FALLBACK build. REFUTED on macOS arm64, where Playwright 1.58.2 has a NATIVE build and no fallback exists: the SAME hang reproduces with the SAME signature (39/333 files, every thread idle). The real variable is the NODE version — 1.58.2 deadlocks on a runtime newer than itself, platform-independently. The 1.58.2→1.61 bump did resolve 26.04, but for a reason not recorded here: it also cleared that Node incompatibility. See [[BLK-021]] / [[LRN-150]].
 
 ---
 
@@ -201,3 +205,65 @@ rules:
 - **Status**: resolved.
 - **Reference**: lesson: a PATH-dependent hook must be verified in the TARGET shell, not the installer's (installer sourcing envs lies to its own checks); usage is MEASURED (`rtk discover`), never assumed. Corroborates [[LRN-047]] (silent degradation → measure) + [[LRN-036]] (hand-managed profile drift); guard interplay [[LRN-089]]-adjacent (ambient-state assumptions).
 - **backmerge**: entry from release/1.0.0 (2b4e7401); the fix `e58037c` was ALSO missing from develop (rtk was live-broken on develop) — ported to develop 2026-07-08 (review remediation A3, commit follows) so this "resolved" is now true on develop too.
+
+## BLK-017 — Bing Webmaster API unusable for a multi-client agency (W2 deferred) — 2026-07-17
+- **Friction**: W2 (`bing` verb — free Bing query stats + index status + first-party backlinks) abandoned after 4 challenge rounds. User's model = client sites live on CLIENT Bing accounts.
+- **Real cause**: two viable-looking paths, both dead. (API KEY) is per-user not per-site (docs), but IS the account identity → one key per client account, exactly what the user feared; non-scoped, no expiry, passed in query string. (OAuth) is the right delegation model (like GSC) but a swamp: Redirect URI rejects ALL local forms (http/https/127.0.0.1 — user-tested); refresh tokens are ROTATED + single-use, self-described non-compliant with OAuth 2.0 → store rewrite every call, AND our parallel seo‖geo dispatch would race the rotation → `invalid_grant` + dead token; undocumented "Could not extract expected anti-forgery token" on refresh, unanswered on MS Q&A; docs contradict themselves on grant_type + token endpoint; no library. MS's own advisor recommends falling back to the API key.
+- **Verified live**: the Webmaster API itself is ALIVE (`GetUserSites?apikey=INVALID` → HTTP 400 `{"ErrorCode":3,"Message":"InvalidApiKey"}`, 0.4s) — distinct from Bing SEARCH API (retired 2025-08-11). So the block is auth/model, not availability.
+- **Status**: open/deferred. REVIVAL: a client already on Bing adds the user as Read-Only → test in ~10 min whether one API key sees DELEGATED sites (undocumented, nobody knows). If yes → W2 is cheap+clean (one key, client-owned verification, revocable, read-only, zero OAuth). Value RAISED by [[BDR-071]]: GetUrlLinks is now the only free viable backlink source (first-party only).
+
+## BLK-018 — release-executor finish span blocked by permission classifier (human signal invisible to subagent) — 2026-07-20
+- **Friction**: v1.3.1 release — `SPAN: finish` dispatch denied at tool-permission layer: classifier flagged "Merge Without Review" (`gitflow.sh finish` in subagent transcript carries no explicit human merge signal). Executor correctly refused workaround, reported BLOCKED. v1.2.0/v1.3.0 same span passed → classifier behavior change, not skill regression.
+- **Real cause**: gitflow doctrine "finish only on explicit human signal" lives in DISPATCHER transcript (user ask + STEP 4 AskUserQuestion go); subagent transcript starts fresh → classifier sees consequential merge with zero authorization evidence. Structural: any human-gated action dispatched to a subagent loses its gate evidence.
+- **Solution** (workaround): dispatcher ran `gitflow.sh finish` + tag inline after its own human gate — where the signal is real. Release completed clean (main `648bc6e`, tag v1.3.1).
+- **Status**: open. Candidate fixes: (a) quote gate evidence verbatim in span prompt — untested vs classifier; (b) move finish+tag span permanently inline in /release-candidate — keeps prep span dispatched, costs the sonnet pin on ~5 mechanical commands, cheap; (c) permission rule allowing subagent `gitflow.sh finish` — weakens the guard, refused. Decide at next release.
+- **Reference**: skill `release-candidate` STEP 5. Pattern adjacent [[LRN-089]] (ambient-state/context assumptions across boundaries). Journal 2026-07-20.
+
+## BLK-019 — notify-attention bell silent, toast OK (VS Code client default) — 2026-09-01
+- **Friction**: hook fired, Windows toast arrived, native bell never audible. User heard only Windows toast sound. Looked like half-broken hook.
+- **Real cause**: not hook. Toast proves full `terminalSequence` reached terminal, `\a\a` sits at head of that same string → BEL emitted. VS Code defaults `accessibility.signals.terminalBell` to `"auto"` = sound OFF unless screen reader active.
+- **Solution**: `"accessibility.signals.terminalBell": { "sound": "on" }` in CLIENT-side user settings.json (`c:/Users/<u>/AppData/Roaming/Code/User/`). Unreachable from remote: real SSH remote, not WSL (no `/mnt/c`, `/proc/version` no Microsoft). User applied, retest → both channels OK.
+- **Status**: resolved (per-client-machine, not repo-portable).
+- **Reference**: `~/.claude/hooks/notify-attention.sh` header already documented the setting; never applied. New client machine → bell mute again while toast works. Silent-degradation class [[LRN-047]].
+
+## BLK-020 — notify-attention: both channels dead on one VS Code client — 2026-09-02
+- **Friction**: client-side prereqs applied on Windows box (ext `wenbopan.vscode-terminal-osc-notifier` + `accessibility.signals.terminalBell` sound:on), window reloaded. AskUserQuestion → nothing. `idle_prompt` 90s wait → nothing. Direct write `\a\a` + OSC 777 to claude own pty (`/dev/pts/2`) → nothing. Second client machine, same SSH server, same hook, same registries → both channels OK.
+- **Server side cleared**: hook dry-run emits `BELx2 + OSC 777 + ST` correctly, `jq` present, matcher covers `idle_prompt`, ext NOT wrongly installed remote-side. Not a hook bug — same class as [[BLK-019]] (client default silently degrades).
+- **Real cause**: unresolved. Facts: claude runs under `dtach -c ~/.dtach/claude-190012`; claude fd1 = `/dev/pts/2` (inner pty, dtach master side), REAL VS Code terminal = `/dev/pts/1` held by dtach client pid 742794. `VSCODE_SHELL_INTEGRATION` unset this terminal; ext marketplace doc requires shell integration ON. BUT other working session (`claude-154323`) also runs under dtach → dtach alone insufficient explanation, weight shifts back to client-side.
+- **Probes run**: direct write to `/dev/pts/1` (real VS Code pty, chain alive: bash pts/1 → dtach client 742794 S+ → master → claude pts/2) → no bell, no toast. Visible-marker injection both paths → user saw neither, BUT inconclusive: claude TUI repaints, injected text clobbered next frame. Only BEL is repaint-proof, and BEL stays silent.
+- **Client settings verified by user**: settings.json path correct (no VS Code profile indirection), `terminalBell` sound on, ext installed + enabled local side. VS Code recent (server dirs 2026-08), so ≥ 1.93 ext requirement met.
+- **Next probe**: user opens FRESH VS Code integrated terminal (no dtach, no claude TUI) and runs `printf '\a\a\033]777;notify;Test;hello\033\\'`. Isolates client renderer from claude/dtach path. Beep+toast there → fault in claude/dtach path; nothing → client-side, diff against working machine.
+- **Fresh-terminal probe (decisive)**: user ran `printf '\a\a\033]777;notify;Test;hello\033\\'` in NEW VS Code terminal → toast OK, bell still silent. Splits one symptom into TWO independent faults.
+- **Fault A (toast in claude session)**: ext parses only terminals created AFTER its activation. Claude terminal pts/1 born 19:00, ext installed later same day → that terminal never hooked. Fix: restart claude in fresh terminal, or re-attach existing dtach session from one (`dtach -a ~/.dtach/<sess>`; dtach broadcasts to multiple clients, no session loss). NOT a dtach filtering bug — earlier hypothesis wrong.
+- **Fault B (bell)**: silent even in fresh terminal where toast works → not terminal path, VS Code audio side. Toast sound = Windows notification (works); bell = VS Code process audio (mute). Suspects: signal volume option, Windows volume mixer entry for Code, output device. Probe: palette `Help: List Signal Sounds` → Terminal Bell plays preview or not.
+- **Fault A RESOLVED (verified 2026-09-02)**: re-attached session from fresh terminal (`dtach -a ~/.dtach/claude-190012`, new client pts/3). Both sends toasted — one through session path (pts/2, dtach broadcast), one direct. Rule: ext hooks only terminals born AFTER its activation → install ext, THEN start/re-attach claude session. dtach broadcast means zero session loss.
+- **Fault B still open**: bell silent on every path. New signal: toasts arrive but user reports NO sound at all, while [[BLK-019]] machine got audible Windows toast sound. Both audio channels dead + both visual channels fine → common factor is client audio output, not terminal stream. Suspects ranked: Windows per-app notification sound off for Code, system/app volume mixer mute, wrong output device, `accessibility.signalOptions.volume` 0.
+- **Fault B ROOT CAUSE ISOLATED (2026-09-02)**: palette `Help: List Signal Sounds` → Terminal Bell preview plays NO sound, while Windows toast sound IS audible. Preview bypasses terminal, BEL, hook, dtach, ext entirely → VS Code renderer audio itself mute on this box. Toast sound emitted by Windows shell, not by Code → explains why one audio channel works and other does not.
+- **Fix candidates (client, ranked)**: (1) Windows per-app volume mixer — Code muted/0, or per-app OUTPUT DEVICE pointing at disconnected device (mixer only lists app after it attempts playback → hit preview first, then open mixer); (2) VS Code `accessibility.signalOptions.volume` = 0 kills all signals; (3) compare both against working machine.
+- **Pragmatic out**: toast already carries audible Windows sound → attention signal functional without bell. Bell is redundant channel, not blocker.
+- **Fault B RESOLVED (2026-09-03)**: cause = Windows per-app volume mixer, Code entry at 0. Toast audible throughout because Windows shell emits that sound, not Code → masked a plain app-volume mute. User set volume up → bell audible.
+- **Status**: resolved (A: ext hooks only terminals born after activation → install ext THEN start/re-attach session; B: Code app volume 0 in Windows mixer).
+- **Lesson**: two independent client faults presented as one symptom ("nothing works"). Splitting probe = run signal in FRESH terminal + play VS Code's own sound preview. Preview bypasses terminal/BEL/hook/dtach/ext → isolates renderer audio in one step. Do that FIRST next time, before any server-side archaeology.
+- **Reference**: [[BLK-019]] bell-only variant (resolved differently — setting alone insufficient here), [[LRN-145]] terminalSequence-not-/dev/tty pattern. Silent-degradation class [[LRN-047]].
+
+## BLK-021 — gstack Chromium install hangs forever on macOS (Playwright 1.58.2 x Node 26) — 2026-09-13
+- **Friction**: `make plugin` froze at step 2/10. Log ends mid-Chromium install: 100% of 162.3 MiB downloaded, then nothing — no error, no timeout, no progress. Steps 3-10 (RTK, GSD, marketplace plugins, link.sh, shell profile) never ran.
+- **Real cause**: gstack's lockfile froze Playwright **1.58.2** (published 2026-02-06) → chromium rev 1208. Its extraction DEADLOCKS under **Node 26.5.0**: both processes (`playwright install` + child `oopDownloadBrowserMain.js`) fully idle — main thread in `kevent`, V8 AND libuv workers in `__psynch_cvwait`, 0% CPU, 2.5s CPU total — stuck at exactly 39/333 files. Zip fully downloaded and intact (170206961 B). NOT network, disk (396Gi free), Gatekeeper, quarantine (none set), nor Intego VirusBarrier — an AV block parks a thread in `write`; none was. PW 1.58.2 declares `engines: node >=18`, so Node 26 is formally SUPPORTED: the incompatibility is undeclared upstream.
+- **Proof (3-way, one variable moved)**: Node 26 x PW 1.58.2 = hang (2/2 reproductions); Node 22.23.1 x PW 1.58.2, same command + same rev = OK (336 files); Node 26 x PW 1.63.0 = OK (347 files, 360MB, Chrome 153.0.8010.12).
+- **Solution**: bump gstack Playwright 1.58.2 → 1.63.0 (rev 1243). In-range, not a pin break — `package.json` declares `"playwright": "^1.58.2"`; only `bun.lock` froze it. Installer now pre-installs the browser under a deadline with bump-retry ([[BDR-088]]). The submodule edit stays LOCAL (reset by `git submodule update`, re-applied by the next install — the [[BDR-029]] pattern).
+- **Status**: resolved. Gate verified: `chromium.launch()` → `LAUNCH OK — Chromium 153.0.8010.12`, rc 0.
+- **Corrects upstream record**: [[BLK-008]] / [[LRN-038]] imputed this exact signature on Ubuntu to the `ubuntu24.04` FALLBACK build. REFUTED: macOS arm64 has a NATIVE 1.58.2 build, no fallback exists there, and the same hang reproduces with the same signature. The real variable is the NODE version. The 1.58.2→1.61 bump did fix 26.04, but for a reason not recorded there — it also cleared the Node incompatibility.
+- **Cost of the wrong record**: it sent the 2026-09-13 investigation hunting fallback builds first. A fix that WORKS can freeze a WRONG cause.
+
+## BLK-022 — macOS bash 3.2 + BSD userland: six fail-OPEN or silent-no-op defects — 2026-09-13
+- **Friction**: repo moved to macOS (Darwin 25.6, arm64). `make test` red across 5 suites, and several guards PASSED while doing nothing at all.
+- **Real cause**: `/bin/bash` is **3.2.57** and `#!/usr/bin/env bash` resolves to it (no Homebrew bash on PATH). Every failure is silent:
+  - `${1,,}` (bash 4.0+) in `lib/url-guard.sh` → "bad substitution", subshell exits 1 = "not local" → the SSRF guard returned rc 0 for localhost, 127.x, 10.x, 192.168.x, 172.16-31.x, **169.254.169.254** and metadata.google.internal. FAIL-OPEN on every Mac; `url-guard.test.sh` recorded it as 13x "got[0] want[2]".
+  - `mapfile` in the 3 surgical-commit helpers → empty arrays → scope guards fail-OPEN, commits degrade to "nothing pending — no-op" while reporting success.
+  - `declare -A` in `hooks/session-start.sh` → every plugin cost read 0 → the >50%-budget warning could never fire.
+  - `timeout` (coreutils, absent from a stock macOS) in `lib/gates.sh` → exit 127 → EVERY criterion recorded NOT-MET whatever the check did.
+  - GNU `sed -i` x3 in `install-plugins.sh` → BSD sed errors → aborts the installer under `set -euo pipefail`.
+  - Test-side GNU-isms: `touch -d`, BSD `wc -l` padding (`got[      48] want[48]`), `/bin/grep` (does not exist on macOS), `stat -c`, `sed -i` + `\n` in the replacement.
+- **Solution**: `_read_lines_into` (portable mapfile), `shopt -s nocasematch` (bash 3.1+, keeps the no-fork property), `case` for plugin costs, resolved timeout binary + pure-bash fallback, `_sed_inplace` + awk. Split over 5 branches.
+- **Status**: resolved. Every suite 0 failures except `gitflow-test.sh`, which is FLAKY: three consecutive runs on one unchanged tree gave 90/16, 92/14, 92/14. Its failures are pre-existing and unattributed, and this port is not distinguishable from that noise — an earlier "92/14 pristine vs 93/13 after, one case better" reading was false precision, comparing two single samples of a non-deterministic suite. shellcheck 1 finding before and after (pre-existing SC2016).
+- **Bonus found while porting**: the orphan-comment cleanup `{N; /^\n$/d;}` in `install-plugins.sh` was a no-op on EVERY platform — after `N` the pattern space starts with '#', so the `^\n$` anchor pair never applied. Rewritten in awk and tested.

.claude/memory/decisions.md

@@ -87,6 +87,17 @@ rules:
 | BDR-064 | 2026-07-14 | global memory split: repo file → CLAUDE.global.md (deployed name unchanged), CLAUDE.md freed for project scope; consumer/maintainer wording rule | accepted |
 | BDR-065 | 2026-07-14 | transient planning artifacts (superpowers spec/plan): committed during run, deleted post-merge; git history = archive; codified in project CLAUDE.md | accepted |
 | BDR-066 | 2026-07-15 | Model routing: reflection inline (session big model) + sonnet-pinned executors + blocking gate | accepted |
+| BDR-070 | 2026-07-17 | claude-seo: cherry-pick scripts into our tree, never install; /seo stays sole entry | accepted |
+| BDR-071 | 2026-07-17 | No viable free backlink source → Off-page axis stays brand-mentions-only (FINAL, not placeholder) | accepted |
+| BDR-072 | 2026-07-17 | SPA: honest refuse (On-page N/A, not zero), no headless browser (R2 over R1) | accepted |
+| BDR-073 | 2026-07-17 | Scoring: LLM judges findings+severity, engine does the arithmetic (deterministic /20) | accepted |
+| BDR-080 | 2026-07-21 | Bug routing inverted: /bugfix primary, /investigate explicit-only | accepted |
+| BDR-083 | 2026-08-24 | Contract gates: deterministic floor (GATE 0) under the fresh verifier | accepted |
+| BDR-084 | 2026-08-24 | /tour multi-project: parallel runners (LRN-083 derogation, bounded), runner inherits session model | accepted |
+| BDR-085 | 2026-08-25 | User permanent rules: writing-style always-on in rules/, web build+security path-scoped | accepted |
+| BDR-086 | 2026-08-26 | darwin: threshold gates full loops; verified defects fixed regardless of unit score (paired-validated, batched checkpoint) | accepted |
+| BDR-087 | 2026-09-03 | Stop hook = attention signal only, never control flow; one script for Notification + Stop | accepted |
+| BDR-088 | 2026-09-13 | gstack browser: guarded pre-install (900s deadline + Playwright bump-retry), not a pinned Node | accepted |
 
 ---
 
@@ -976,6 +987,7 @@ rules:
 - **Why**: user call 2026-07-14 — registries already capture decisions; a stale plan describes a superseded intermediate state and misleads future readers; accumulation pollutes the repo. Precedent: gsc-crux cleanup (8a1fac0, 2026-07-10) did the same — this makes it law, not habit.
 - **Alternatives rejected**: never-commit (gitignore docs/superpowers) — breaks mid-run: briefs, reviewers, other-machine checkouts need the files; superpowers brainstorming commits the spec by convention. Keep-forever — the drift + pollution complained about.
 - **Reference**: project CLAUDE.md; cleanup commit this chore; precedent 8a1fac0. Linked [[BDR-064]], [[LRN-124]].
+- **Amendment (2026-07-22)**: DELETE side now AUTOMATED — `lib/gitflow.sh` `_gitflow_purge_transient` at `gitflow finish` (feature/bugfix, pre-merge, on HEAD) git-rm's `docs/superpowers/{specs,plans}` + scoped commit → develop TIP clean, feature commits stay reachable (`git show <sha>:…` archive intact). Best-effort: NEVER aborts finish (nothing-tracked no-op / dirty-path skip / commit-fail index+tree restore). Opt-out `GITFLOW_PURGE_TRANSIENT=0`. Retires the manual chore that slipped (655e364). Universal via `~/.claude/lib`→repo symlink (ship-feature STEP 9 + init-project STEP 11 both finish through it). gitignore STILL rejected — unchanged: breaks superpowers' `git add` of the spec (silently skipped, no travel to SDD worktree). `.claude/tasks/{contracts,plans}` kept versioned (user call — durable, referenced by decisions.md). Tests: gitflow-test.sh T17 a-d. [[LRN-138]].
 
 ---
 
@@ -992,3 +1004,131 @@ rules:
 - **Wave 3 (2026-07-15/16, user directive)**: split the last two inline execution-carrying agents like /feat. /bugfix: investigation+diagnosis+contract inline behind the gate; bugfixer = sonnet EXECUTOR (fix + regression test from a closed FIX PLAN; no Agent/AskUserQuestion; BUGFIX-EXEC REPORT). verify+secure loop stays in main loop, executor = its re-dispatched dev (verify-secure-loop.md intro now: BOTH consumers dispatched, no inline branch). FINISHES reversing the "split bugfix rejected" carve-out (hotfix went wave 2, bugfix now) — investigation↔fix coupling accepted, mitigated by structured DIAGNOSIS + verify loop. /code-clean: PHASE-1 audit + validation gate inline (reflection); code-cleaner = sonnet PHASE-2 EXECUTOR (delete approved dead code, inline-load refactorer, re-audit) — refactor NOW on sonnet (inline-load pin was inert on big model). exported-symbol per-item consent stays AT THE GATE. Consumer-staleness swept: hotfix deeper-bug escalation → /bugfix skill (not bare agent); onboard STEP 6 + tour Phase B read-only-audit → general-purpose/analyzer (big model, NEVER the sonnet executor — audit stays big). Both skills STAY gated. Also: Explore built-in kept inheriting session (search feeds reflection = big deserved; custom sonnet override created then reverted — built-in already inherits + no owned prompt). census 36→42, loops-light repointed 35/0.
 - **Wave 4 (2026-07-16)**: client-handover doc-gen → sonnet, REDACTION-ONLY (user flipped from whole-writer after the full read). Key finding: nested audits (/seo,/harden,/web-validate — gated wave 1) must run BIG either way → whole-writer = ~7 extra gate-yields + resumable state machine on a CLIENT deliverable for ~0 extra sonnet work. Design: client-handover-writer TRIMMED to ship pipeline (STEP 1-8, all interactive gates native on big, nested audits inherit big) + doc-gen orchestration (resolve questions/NAP/precheck/overwrite/client-name inline → PACKAGE) → dispatches NEW sonnet handover-doc-writer (STEP 9-16: reads memory+git, synthesizes 6-chapter doc, word-count/skill-leak/anchor gates, renders HTML+PDF; GATE-FREE, no AskUserQuestion/Agent). client-handover JOINS gated group (orchestrates audits = reflection); its opus pin dropped (inherits big via inline-load). census 42→46. Branch feature/client-handover-dispatch (off develop, waves 1-3 merged first).
 - **Reference**: spec `docs/superpowers/specs/2026-07-15-model-routing-design.md` + plan `docs/superpowers/plans/2026-07-15-model-routing.md` (transient, BDR-065 lifecycle), branches `feature/model-routing` (waves 1-3, merged), `feature/client-handover-dispatch` (wave 4).
+
+## BDR-067 — first public release: versioning reset to v1.0.0 (override "never restart at v1.0.0") — 2026-07-16
+- **Decision**: first PUBLIC release cut as **v1.0.0**, treating internal v1.0.0→v4.0.0 as pre-release history. version.txt 4.0.0→1.0.0; CHANGELOG: new `[1.0.0] — Initial public release` on top (= former `[Unreleased]` content), old 1.0-4.0 lineage moved UNCHANGED under a `## Pre-release (internal history)` banner (provenance). Tag v4.0.0 DELETED (local+origin), v1.0.0 tagged on main. Repo goes public on THIS Gitea (user flips visibility separately — not a git op).
+- **Why**: launching publicly at v4 misrepresents (implies missed v1-3 to newcomers); v1-4 were private dev. First public impression should be v1.0.0. User directive.
+- **Overrides**: BDR-055-era release-candidate rule "never restart at v1.0.0 — desyncs tag↔CHANGELOG lineage". That guards ACCIDENTAL mid-lineage restart; a DELIBERATE public-launch reset is the sanctioned exception. **CONSEQUENCE for next release**: continue from public 1.0.0 (→ 1.0.1 / 1.1.0 / 2.0.0), NEVER back to the old 4.x. The [Unreleased]-BREAKING(CLAUDE.global.md) folds into 1.0.0 harmlessly (first release = breaking vs nothing).
+- **Safety (git cherry)**: found a STALE abandoned `release/1.0.0` (July-4 prep, 227 commits behind develop, pushed to origin). `git cherry develop release/1.0.0` + content checks confirmed all its real changes (rtk PATH fix, drop-AI-attribution settings backstop, find-skills drop, BLK-016/LRN-098/LRN-101/EVAL-015, all features) ALREADY in develop → nothing orphaned → deleted it (local+origin). Cut fresh v1.0.0 from CURRENT develop, not the stale branch.
+- **Method**: release-candidate skill gates honored (when-to-release, push) but PREP done manually — backward version (4.0.0→1.0.0) + CHANGELOG restructure exceed the sonnet release-executor's forward-bump assumption (reflection, stays big). LRN candidate: a version RESET is editorial, not mechanical — don't dispatch the forward-only executor for it.
+- **Status**: SHIPPED. origin main=dc4f78b, develop=6c23d6f, tag v1.0.0 sole tag; v4.0.0 + stale release/1.0.0 removed from origin.
+
+## BDR-068 — /capitalize + /close auto-persist memory (finish→develop + push); scoped LRN-069 exception — 2026-07-16
+- **Decision**: when /capitalize (or /close = --ritual) writes entries AND the aiguillage branched a `chore/<name>` off develop THIS run, new STEP 5C auto-finishes that branch → develop + pushes origin/develop. Default ON. `--no-push` holds it on the chore branch (pre-BDR-068 behavior). WORKING branch (memory rides feature/bugfix) or rc-3 commit-fail → 5C skips. push-fail → merge already local, report + manual push (no retry/reset).
+- **Why**: memory's value = cross-session persistence; a ritual commit stranded on an unmerged chore branch is INVISIBLE to the next session on develop → the ritual defeats itself (user-identified gap). Memory = append-only/low-risk; the human-gated MERGE (aiguillage) is a CODE safeguard, and LRN-069's push-gate guards surprise CODE/release pushes — neither applies to an end-of-session memory persist.
+- **Scope**: /capitalize + /close ONLY. /prune-memory + /reconcile stay fully human-gated (curation/report may want review before landing). NEVER auto-finish a branch the run did not create.
+- **Amends**: [[LRN-069]] (push needs explicit go) — scoped exception for memory-only ritual persist; `gitflow-aiguillage.md` "never gitflow finish" — carved for capitalize/close.
+- **Files**: skills/capitalize/SKILL.md (STEP 5C + aiguillage branch-capture + STEP 6 outcomes + Rules + arg-hint `--no-push`), lib/gitflow-aiguillage.md (exception note). Tests unaffected (run-deterministic covers memory-commit.sh surgical scope, not the persist step).
+- **Status**: implemented on feature/close-auto-persist, UNMERGED (human gate).
+
+## BDR-069 — permissions deny: keep broad `.env.*` glob, keep `.env.example` name (option A) — 2026-07-16
+- **Decision**: `Write(path)` deny rules inert (Claude Code matches `Edit(path)` only) → 5 secret-write bans converted to `Edit()`. Mirrored 9 secret patterns Read denied but Edit did not → Read/Edit parity 14/14. New read-allowed/write-denied class: lockfiles (`*.lock`, `package-lock.json`, `pnpm-lock.yaml`, `go.sum`) + `node_modules/**`. Kept `Edit(**/.env.*)` BROAD despite matching `.env.example` (mandated by CLAUDE.global.md:206). No rename.
+- **Why**: deny glob = absolute, no exemption mechanism ([[LRN-130]]). Only lever = glob shape. Narrowing to `.env*.local` fails open on `.env.production`/`.staging` — real secrets outside Next.js convention.
+- **Cost accepted**: scaffolder/doc-syncer degraded on `.env.example` — Edit/Write/Read/Grep/Glob blocked; Bash heredoc still works (`Bash(cat *)` allowed). Ergonomic tax on /init-project, not a hard block.
+- **Alternatives rejected**: (B) narrow glob → weakens `.env.production`; blocked by auto-mode classifier as unauthorized self-modification ([[EVAL-024]]). (C) rename → `env.example` sidesteps glob at zero security cost, but ~30 refs (scaffolder, doc-syncer, init-project, deploy, 3 archetypes, link.sh, install-plugins.sh, toggle-external.sh) + repo's own root `.env.example` + seo-data.test.sh + gitignore `!.env.example` (BDR-030) → refactor, user declined.
+- **Files**: settings.json, templates/settings/SETTINGS.md (taught the broken `Write()` pattern → fixed at source so /onboard stops propagating it).
+- **Status**: implemented on chore/fix-inert-write-deny-rules (07ca738), UNMERGED (human gate).
+
+## BDR-070 — claude-seo (github.com/AgriciDaniel): cherry-pick, never install — 2026-07-17
+- **Decision**: adapt useful scripts into our tree, /seo stays sole entry. Do NOT run install.sh / plugin install.
+- **Why**: their CODE is real (326 tests, render_page.py 428l Playwright, url_safety.py 622l SSRF) — their INSTALLERS destroy our work. install.sh:49 `cp -r skills/seo/*` overwrites our SKILL.md. uninstall.sh:45 globs `~/.claude/agents/seo-*.md` → deletes our seo-analyzer.md (42K) it never installed (verified dry-run). extensions/*/install.sh:42 replaces settings.json with `{"env":{...}}` on parse error. skills/seo/SKILL.md:119 injects Skool upsell footer into deliverables (leaks to /client-handover client PDFs). hooks.json registers global PostToolUse exit-2 → blocks our dispatcher mid-bundle.
+- **Alternatives rejected**: (plugin install) → both `/seo` coexist namespaced → non-deterministic dispatch, silently loses our FR-legal axis on an unpredictable fraction of runs. (install nothing) → forgoes render_page/url_safety/unlighthouse we lack.
+- **Verdict on parity**: their README lies (dual JSON-LD validator = 2 hyperlinks, zero `.py` calls; "zero-network"/"fully offline" false). Our system is more honest; we keep FR-legal (their whole repo: 2 hits), fix-bundle+ownership, trajectory-17/20, NAP anti-seed.
+- **Files**: none installed. Findings drove the whole seo-geo-integrity branch (21 commits).
+
+## BDR-071 — no viable free backlink source: Off-page axis stays brand-mentions-only — 2026-07-17
+- **Decision**: I1's narrowed Off-page axis (brand mentions from STEP 6 only, backlinks+authority declared §14-unauditable) is the FINAL state, not a placeholder awaiting data.
+- **Why**: measured, not assumed. GSC has no links endpoint (API = Search Analytics/Sitemaps/Sites/URL-Inspection only; links report UI-only). Common Crawl hyperlinkgraph domain-edges = **17.3 GB gzipped** (+879MB vertices, +2.3GB ranks), HEAD-measured live. Scanning it per-audit is non-viable + abusive to a nonprofit. The reference impl (claude-seo commoncrawl_graph.py:169) caps download at 500 MiB = **2.9% of edges**, sorted by source ID → arbitrary slice reported as a backlink profile, "70/100 health". A random sample dressed as a measurement — the exact failure class the branch removes.
+- **Consequence**: B1/B2/B3 all killed. Weight (10-15%) unchanged — re-deriving for an axis that won't widen churns historical scores for nothing.
+- **Only free viable source**: Bing GetUrlLinks — first-party only (never a competitor), blocked on client's Bing account → raises W2's value ([[BLK-017]]), does not unblock it.
+
+## BDR-072 — SPA: honest refuse, no headless browser (R2 chosen over R1) — 2026-07-17
+- **Decision**: rendercheck verdict `client-rendered` → On-page axis N/A, excluded from weighted global, NEVER scored zero. No Playwright, no Chromium. User-arbitrated.
+- **Why**: a zero says "your on-page is bad"; N/A says "we couldn't see it" — only one is true, and /client-handover gates on 17/20. curl on a shell returns "missing" for every meta/H1/JSON-LD → a page of FALSE findings + a bundle that "fixes" tags that already exist. STEP 2 recorded `RENDERING: SPA` since forever and NOTHING acted on it. Verdict from what the server SENT (package.json can't tell React-SPA from Next-SSR).
+- **GEO angle (sharper)**: AI crawlers (GPTBot/PerplexityBot/ClaudeBot) are WORSE at JS than Googlebot — fetch HTML, largely don't execute. A client-rendered site is near-invisible to the engines the audit serves → §0 alert + SSR/SSG top user action, aligns CLAUDE.global "public sites never SPA".
+- **Alternatives rejected**: R1 Playwright (~300MB Chromium, breaks bash+curl purity) — user chose refusal. Refusing IS the finding.
+- **Files**: lib/seo-data/render_check.py, seo/geo STEP-5 gates (20d3082).
+
+## BDR-073 — deterministic scoring: split LLM judgement from arithmetic — 2026-07-17
+- **Decision**: LLM emits WHICH findings + severity (irreducible judgement); engine computes the /20. Reuses /harden's scale (-15/-8/-3/-1, clamp, /5 into /20) → one vocabulary across the family.
+- **Why**: /harden had a real scale (SKILL.md:435), /seo had NONE → every axis felt → two runs over identical code diverged, while /client-handover gates on 17/20. H2 sharpened it: once drift reports real change, a self-moving score is visibly noise. Same principle as engine-side cannibalisation grouping — never hand a model 1000 rows to add.
+- **Makes computable (was prose)**: "N/A is not a zero" (R2 on-page, I1 off-page) → axis excluded + weights renormalised, verified all-20 with 2 N/A → global 20.0. Prevalence: affected/sampled shift severity ONE step (≥50% escalate, single de-escalate).
+- **Files**: lib/seo-data/score.py (4818c61).
+
+### BDR-074 — Remove config-protection edit-block guardrail [accepted] (2026-07-17)
+Deleted hooks/config-protection.sh + its settings.json PreToolUse registration + lib/tests/config-protection.test.sh. Hook blocked model Edit/Write on quality-gate files (settings.json, gitflow.sh, .githooks, doctor.sh, hooks, lib/tests, lint) via one-shot .claude/.config-edit-ok sentinel. Removed per user req — friction editing own config > guardrail value; user = human operator. Residual: gitflow pre-commit guard + Gitea branch protection still block direct code commits main/develop; only edit-time block gone. Alts rejected: warn-only (exit0+log), targeted relaxation. Supersedes any prior config-protection decision.
+
+### BDR-075 — Framework-wide 3-way adversarial plan-challenge phase [accepted] (2026-07-17)
+After a plan/reflection elaborated + before execution, 3 fresh blind sub-agents (correctness/robustness/simplicity) attack it; main loop RE-THINKS every aspect a BLOCKER lands (named change or [deferred]) + re-challenges once if plan materially changed. Reusable lib/challenge-plan.md + new agents/plan-challenger.md (read-only, big-model per [[BDR-066]] — audit judgment, NOT sonnet). Fail-safe (never fail open: mute→retry→escalate), severity-driven (any single-lens BLOCKER=must-address, NOT consensus — lenses orthogonal), advisory into existing human gate. KIND tunes lenses: build-plan/proposals/fix-bundle. Wired 11 orchestrators: ship-feature/init-project/feat/bugfix + onboard/audit-delta/code-clean + seo/geo/harden/web-validate. Excluded (no real plan): hotfix/tour/analyze/client-handover/release-candidate/spec. Audit found 0 repo-owned plan-challengers pre-existing (only vendored gstack autoplan, sequential+unwired). See [[EVAL-026]].
+
+### BDR-075 amendment (2026-07-18) — hotfix INCLUDED via logic-only guard
+Supersedes the "Excluded: hotfix" clause of [[BDR-075]]. hotfix now wired (STEP 1.8, Option B): GUARD skips purely cosmetic fixes (CSS/copy/typo), fires the 3-lens challenge ONLY when the fix touches control flow/behaviour (off-by-one, wrong operator, behaviour-changing config, execution-altering import); a BLOCKER → escalate to /bugfix (its STEP 3b runs the full phase). 12 orchestrators wired. Still excluded (no forward plan): tour/analyze/client-handover/release-candidate/spec. Per user (Option B). Branch feature/hotfix-challenge-guard, unmerged.
+
+### BDR-076 — Dispatched judgment agents pinned OPUS; session model = orchestration + inline reflection ONLY [accepted] (2026-07-19)
+Reverses the BDR-066 rejected alternative "opus pins on audit agents (session-independent)". Context changed: session default now Fable (Mythos tier, /model 2026-07-19) — inherit meant every dispatched audit/challenge burned Fable quota, exactly the waste BDR-066 killed for executors. New rule: Fable does ONLY main-loop orchestration + reflection (brainstorm, plan, contract, synthesis, gates); EVERY dispatched subagent pinned. Pinned `model: opus` (big tier, session-independent; NEVER sonnet — silent audit downgrade, the thing old §F5 guarded): analyzer, plan-challenger, seo-analyzer, geo-analyzer, validator-analyzer + onboard's 6 general-purpose audit dispatches (`model="opus"`) + tour Phase B. NOT pinned (justified deviation from approved "7 agents"): interviewer + client-handover-writer — inline-load only, never dispatched → frontmatter pin inert + misleading (BDR-066 wave-4 precedent: its inert opus pin was dropped); they ARE the main loop = Fable per the rule. Explore built-in stays inherit (wave-3 decision conserved: no owned prompt, search feeds inline reflection). Local session pin `opus-4-8[1m]` dropped from `.claude/settings.local.json` (gitignored) — Fable default from settings.json now applies in this repo too. model-gate.md unchanged (still guards inline reflection, Fable-or-Opus = big). Census: model-routing.test.sh §3 flip + §11 (61 pass), loops-light 35 pass, full `make test` green. User directives via gate: "Opus partout" + "Supprimer le pin". Branch feature/opus-pin-audit-agents, unmerged.
+
+### BDR-077 — Model-tiering v2: 4-tier explicit routing, mode-based splits, no-inherit dispatches [accepted] (2026-07-19)
+Supersedes BDR-076 scope + amends BDR-066. Doctrine: session model (Fable) = main-loop reflection/orchestration/planning/logic ONLY; main-loop retention criteria = interactive | conversation-context access | orchestration decision | dispatch overhead > step cost. NOTHING dispatched inherits: typed agents = frontmatter pin, built-ins = `model=` at every call site (`fable` for skill-runner reflection children, else complexity tier). Spike+smoke proven: `model:"fable"` resolves claude-fable-5 (enum-validated, loud fail, no silent fallback); call-site override BEATS a typed pin (sonnet-pinned verifier ran haiku). Fail-safe pin rule: mixed-mode agents keep the HIGH tier as pin, overrides go DOWN — forgotten override over-tiers (cost), never downgrades judgment. Mode-based splits (commit-changer precedent generalized; file splits rejected): doc-syncer audit(opus)/patch(sonnet) — ALSO fixed a latent defect: /doc dispatched an agent whose STEP 8 interactive gate could never fire; gates hoisted to a DISPATCHER PROTOCOL section; handover-doc-writer synthesize(opus)/render(sonnet) via run-scoped `.audit/handover-draft-<RUNID>.md` + DRAFT COMPLETE sentinel; seo/geo collect(sonnet)/judge(OPUS PIN)/template(sonnet) via `.audit/*-signals-<RUNID>.md` + COLLECTION COMPLETE + fail-closed judge + dispatcher ERROR contract (mute/ERROR judge NEVER carried into templating; retry once, escalate). File split only for a genuinely new role: plugin-probe (sonnet, facts-only) + plugin-advisor repinned opus reasoner (fail-closed on missing PROBE REPORT) + lib/plugin-gate.md (checkpoint + apply gate, doc-commit ×N include pattern). Inline→dispatch conversions: scaffolder, onboarder, doc-commit steps ×5 flows — their sonnet pins were INERT since creation, now live; CHANGE SUMMARY crosses the doc dispatch into doc-commit (LRN-126 wire). Tier moves: validator-analyzer opus→sonnet (deterministic runner); commit-changer propose=opus/apply=pin; ship-feature/init-project code-review dispatches = opus explicit (WAS an inherit leak); client-handover-writer's 7 skill-runners = model:"fable". Every wave shipped an IN-WAVE planted-input smoke as its merge gate — all PASSED disk-verified. Census §12-18 (125 pass; one vacuous line-wrapped lock self-caught = LRN-093 live). 6 waves, branches feature/model-tiering-w1..w6, merged on user standing signal. Plan: challenged 3 blind lenses + 1 confirmation (1 BLOCKER closed by spike, 8 MAJORs + 8 MINORs closed by named changes, 0 deferred). Refs: `.claude/tasks/plans/2026-07-19-model-tiering-v2-{analysis,plan}.md`.
+
+### BDR-078 — ctx7 coverage: central fast-libs list + once-per-session reminder hook; every code path covered [accepted] (2026-07-20)
+Refines BDR-053 (single surface). Audit 2026-07-20: coverage PARTIAL — find-docs fired on user doc-questions only; ship-feature 0c / init-project 5c pre-fetched; /feat //bugfix executors + ad-hoc coding NEVER consulted ctx7; fast-libs list hardcoded 3× (drift risk). 4 closures shipped: (a) find-docs description += BEFORE-writing-code trigger (fast-moving lib, even without doc question, unless fresh cache) + cache-first rule in body (tee fetched docs to .ctx7-cache/); (b) feater+bugfixer briefs += fast-lib docs rule — read fresh `.ctx7-cache/<lib>*.md`, else `npx ctx7@latest` fetch max 2 topics, else `ctx7 cache miss: <lib>` in NOTES + proceed (executors lack Skill tool → Bash path); (c) hooks/ctx7-reminder.sh UserPromptSubmit — ONE fire/session (sentinel on session_id), only when project manifest carries fast-libs; reports cache state; skips <task-notification> turns; always exit 0; (d) lib/fast-libs.sh = SINGLE SOURCE (detect / cache-status verbs, JS package.json anchored full-key match + Python requirements/pyproject, 7-day freshness, LC_ALL=C sort locale-independent) consumed by hook + 3 pipeline skills + 2 briefs. 2nd session surface DELIBERATE, not a BDR-053 reversal: 053 killed a 490-tok ALWAYS-ON rule duplicate; hook costs ~0 quiet, 1 line once when fast-libs present. Alternatives rejected: PreToolUse Edit/Write gate (fires per-edit = noise); description-only fix (probabilistic, executors unreachable). Tests: lib/tests/fast-libs.test.sh 11 checks (anchored/near-miss/py/none, cache fresh/stale/missing, hook fire/sentinel/quiet×2); shellcheck + full make test green. Branch feature/ctx7-coverage, unmerged (human gate).
+Amendment (same session): skills/find-docs = machine-owned dist (gitignored, ctx7 regenerates on fresh clone) → durable copy of closure (a) lives in install-plugins.sh STEP ctx7 (idempotent grep-guarded python patch, fixture-verified); live SKILL.md carries the same edit uncommitted by design.
+
+### BDR-079 — profile `set` symmetric on managed externals + MCPs [accepted] (2026-07-20)
+Audit (user ask "profile toggles externals both ways?"): ASYMMETRIC. Enable side OK — gstack on-demand from submodule when pack off (shared `skills-disabled/gstack__*` convention with toggle-external.sh, interoperable), externals restored from parked, magic delegated to toggle-external. Disable side MISSING: `cmd_set` trimmed only gstack + MANAGED_PLUGINS → `set backend` left emil/frontend-design/design-motion/impeccable active + magic registered; SKILL.md claimed both-ways toggle (true only at enable). Shipped: (1) `MANAGED_EXTERNALS` (emil-design-eng, frontend-design, design-motion-principles, impeccable = exact union of profile `external` usage; darwin-skill excluded — not task-type-driven) + `MANAGED_MCPS` (magic) allowlists, same doctrine as MANAGED_PLUGINS; (2) cmd_set refactored to 4 trim helpers (`disable_{gstack,plugins,externals,mcps}_not_in`) — symmetric, nothing outside allowlists ever auto-touched; (3) enable_skill external += from-source fallback (`ln -sf skills-external/<name>`, mirrors toggle-external) — closes the "missing symlink" warn; (4) stale usage() NOTE ("NOT toggled automatically") + SKILL.md fixed. Hermetic test profile-set-managed.test.sh 16 checks: fixture repo (both *_REPO_OVERRIDE), fake `claude` shim on PATH logging calls + flat-file MCP registry — gstack on-demand, external from-source, park/restore round-trip, magic add/remove calls, non-managed untouched. shellcheck + make test green. Branch feature/profile-managed-externals, unmerged (human gate).
+
+### BDR-080 — bug routing inverted: /bugfix primary, /investigate explicit-only [accepted] (2026-07-21)
+Old routing "Bug → investigate (bugfix if gstack off)" + gstack ON by default → every bug took path bypassing own quality pipeline (gitflow aiguillage, contract, fresh verifier + security gates, doc-sync, `.claude/memory` registries) — /bugfix relegated to near-never fallback. Skill comparison: same core doctrine (root-cause iron law, hypothesis loop, regression test, 3-strike stop, >5-files alert) but incompatible wrappers — investigate monolithic (same context investigates+fixes+verifies, ~1075-line SKILL.md w/ gstack preamble/telemetry/onboarding, capitalizes to `~/.gstack` learnings.jsonl framework never reads at session start); bugfix orchestrator (reflection inline, sonnet bugfixer executor, fresh gates — BDR-066, LRN-083). Composition rejected: skills superpose in context, don't compose — invoking investigate inside bugfix = two full workflows, two completion protocols, two memory systems loaded at once. Decision: CLAUDE.global.md routing line inverted — bugfix primary; investigate ONLY on explicit ask for gstack ecosystem (cross-project learnings, /freeze scope lock, long no-commit investigation). Alternatives rejected: keep investigate primary (bypasses framework), embed investigate inside bugfix (context conflict, dual memory). Known drift noted at write time: Index table rows BDR-074..079 missing (pre-existing, /prune-memory scope).
+
+### BDR-081 — Config recalibrated for Claude 5 family (Opus 5 dispatch tier) [accepted] (2026-07-30)
+Opus 5 (released 2026-07-24) now backs every `model: opus` pin (BDR-076/077) + any `/model opus` session. Research (official migration guide + web + registries): Opus 5 OVER-delegates (inverts LRN-030 Opus 4.8 trait that CLAUDE.global.md:43-47 compensated), self-verifies (explicit verify instructions → over-verification, "removing them reduces wasted tokens with no loss in quality"), literal following (conservative-reporting clauses depress recall; MUST/CRITICAL over-triggers), scope expansion = named regression, written deliverables +30-40%. Claude Code injects Opus-5-only anti-delegation prompt sections (heron_brook + subagent_steer_delegation, issue #80988, server-gated, no opt-out) — prose caps would triple-stack. Shipped: delegation block → model-neutral WHEN-guidance + explicit gates carve-out (verifier/security/challenge still dispatch as written); "staff engineer" self-check bar dropped; finish-whole-task clause folded into Deviations (gone-WRONG→STOP still wins); deliverable-length rule; design hook `\bux\b` dropped (`\bui\b` KEPT — 0 FP, 1 logged TP, lock-tested); plan-challenger grounded-doubt→[MINOR] in-place reword (grammar byte-identical). Plan challenged by 3 blind Opus 5 plan-challengers: correctness CONCERNS(4) / robustness FATAL(5, BLOCKER: all surfaces symlink-deployed LIVE — gates fire post-deployment) / simplicity CONCERNS(4); every fix adopted as prescribed (scratch-validation before live hook write, minimal diffs, ux-only, MINOR-routing). Alternatives rejected: leave as-is (nudge actively counter-productive); hard spawn caps in prose (harness injects one); confidence axis on challenger grammar (consumer unwired); dropping \bui\b (no evidence). NOT touched: verify-secure-loop + fresh gates (harness architecture BDR-049/050, ≠ model self-check prose); Security/Architecture sections (BDR-021); settings effortLevel xhigh (user pref — Opus 5 carry-over trap → LRN-139); superpowers plugin wording (external upstream). Plan+synthesis: .claude/tasks/plans/2026-07-30-opus5-config-tuning-1238.md. Branch feature/opus5-config-tuning, unmerged (human gate).
+
+### BDR-082 — seo/geo analyzers de-prescribed for Opus 5 (C1) [accepted] (2026-08-02)
+BDR-081 N5 follow-on, user-directed apparatus (plan+3-lens challenge+census+dogfood). Method: audience×mode-range invariant — dedup ONLY verbatim same-audience (spec rule / bundle-item payload / phase-local caveat) same-mode-range repeats; cross-mode + agent↔dispatcher twins stay (standalone paths need them). Census-FIRST: lib/tests/seo-geo-contract.test.sh 71 locks (verdict grammar, sentinels, ALL STEP headers incl. interiors, item fields, score labels, envelope keys), flip-proven 7 mutations→7 FAILs, committed BEFORE reword. Shipped: self-output verification removed (":970 run twice"→conditional integrity guard; ":1217"→single-shot-scoped), 2 pre-BDR-061 vestigials fixed, caps softened (P0-rule/MANDATORY/ALWAYS→plain content rules), 2 essays compressed, checklist :1309→routing map rows verbatim (challenger caught it = routing table, NOT self-check), true same-range dups only (seo Handoff+landing-page blocks; geo ZERO — all claimed pairs distinct on inspection). FROZEN: guard-first url-guard orderings, :550 denominator-before-sampling (ordering IS the honesty mechanism), R2/NAP/COVERAGE/citation invariants, external-freshness checks (world drift ≠ self-verification). Deltas: seo 1528→1503 l ("P0 rule" 2→0, ALWAYS 1→0, MUST 5→4, NEVER 9→9 = class-B bans kept); geo 1106→1107 (MANDATORY 1→0, MUST 4→3). Plan challenged correctness FATAL / robustness FATAL(3 BLOCKER) / simplicity CONCERNS + confirmation FATAL(9) — every BLOCKER closed by named change (§5bis record). Dogfood before/after on frozen zenquality copy: judge-replay on frozen signals (zero collect variance) + templates + fresh collects + e2e judge + 42/42 assert battery BOTH sets + blind reader "interchangeable; all deltas = presentation variance both directions OR after MORE spec-conformant". Alternatives rejected: keyword dedup (challengers proved audience/range-blind — most annex "twins" were distinct obligations), FULL/aggressive dogfood (billing gate killed nested CLI; left as user option), banner/shape locks (LLM-convention layers wobble — lock strings only). Evidence: .audit/dogfood-baseline/ (18 artifacts + DOGFOOD-VERDICT.md), plan .claude/tasks/plans/2026-07-30-seo-geo-deprescription-1402.md. Branch feature/seo-geo-deprescription, UNMERGED (human gate).
+
+### BDR-083 — contract gates: deterministic floor (GATE 0) under the verifier [accepted] (2026-08-24)
+User asked what to take from `unlazy` skill (Leonxlnx/unlazy 2.1.0, MIT). Verdict on its verification ARCHITECTURE: teaches nothing we lack — contract + fresh blind verifier + bounded loops + order invariant already shipped (BDR-049/050/066, LRN-083). Real gap found elsewhere: between executor and GATE 1, NO deterministic floor. GATE 1 = LLM dispatch; verifier's mandatory `PROOF:` line = a line the verifier WRITES — nothing structurally stops it being produced without executing anything (LRN-048 demands a pass prove it looked; the proof is self-reported prose). Decision: import unlazy's gate ledger INTO the existing contract, never alongside it. Palier 2, user-chosen over doctrine-only / defer.
+TAKEN: criterion carries an oracle (indented `CHECK:` cmd + `EXPECT:` success-only marker + `EVIDENCE:` slot); fail-closed = exit 0 AND marker (a nonzero process never passes because its error text carries the token); evidence persisted INTO the contract → the fresh verifier reads fact, not the executor's report; `ABANDON: <id> <non-blank reason>` = impossible criterion never deleted, blocks CONFORME, routes to human gate (new verdict token `ABANDONED(n)` — distinct routing from ECARTS ⇒ distinct token, not a sub-line to re-derive); 4 gate-authoring rules (observe the named artifact / success-only marker / positive control before any absence check / recompute supplied numbers, never copy one into EXPECT); 4-pass executor discipline (feater full; bugfixer narrowed to fix+test under "keep the fix minimal", pass 3 = negative control proving the regression test fails without the fix).
+REFUSED + why: Stop hook `decision:"block"` — contradicts "STOP + human escalation", "gone WRONG → STOP re-plan", "merge only on explicit human signal"; a hook FORCING continuation is the inverse of our gates; its 6-block release either traps the session or gives up; each block = an agent continuation = real tokens. Approval store `~/.unlazy/approved` (binds ledger+cmd+CWD+shell+timeout+platform+full PATH) — exists to execute ledgers INHERITED from untrusted repos; our contracts are authored by our own orchestrator in our own repo ⇒ biggest chunk of their 28k checker closes zero threat here. `.unlazy/<scope>/` tree (PLAN+GATES+gates/+status.log+session+hook-state+locks/) — a 4th bookkeeping tree beside .claude/tasks/{contracts,plans} + memory/ + audits/. `tree N` Depth-Tree effort arithmetic — disowned by unlazy's OWN research/validation-protocol.md (v1 six-run figures unreproducible), while the repo DESCRIPTION still advertises the retracted claim. Node checker (28k .mjs + 54k .mjs tests) — lib stack is 100% bash, Health Stack = `shellcheck *.sh hooks/*.sh lib/*.sh` would cover none of it. `OWNS:` ownership leases — deferred (Palier 3): our parallel dispatches (seo/geo, 3 plan-challengers) are read-only, the write-collision problem does not exist yet.
+Shipped: lib/gates.sh (~250 l bash; `status` never executes and never writes · `run` ALWAYS re-executes every runnable criterion — trusting written evidence is the failure being closed, so there is no incremental mode to get wrong; rc 0 MET / 2 UNMET|malformed / 3 ABANDONED; parse fails closed on partial oracle, duplicate id, unindented attribute, runnable-without-EVIDENCE, and executes nothing when the ledger is malformed). GATE 0 in lib/verify-secure-loop.md (red floor → executor re-dispatch with the NOT-MET rows, NO verifier spawned; own 3-iteration budget, separate from conformity; malformed ledger fixed in the main loop, never dispatched to a dev). Order invariant now GATE 0→1→2 on every re-loop. lib/contract-interview.md: ORACLES section + template + ABANDONMENT lifecycle + per-flow oracle weight. agents/verifier.md: oracle-consumption rules — a red or unrun oracle is NEVER overridden by reading code; a MET oracle proves the ORACLE, not the English sentence ⇒ vacuous oracle = NOT-MET, the one judgement no command can make; verifier may re-run a CHECK but never edits the contract. lib/tests/gates.test.sh 64 assertions (sentinel-proved non-execution, with its own positive control asserted first).
+Alternatives rejected: Palier 1 doctrine-only (CHECK:/EXPECT: become decorative without an executant); port the Node checker (stack break, shellcheck-blind); fold ABANDONED into ECARTS (would send a dev to fix the impossible and eat the 3-iteration budget); `status` revalidating old evidence (that trust is the failure being closed).
+Branch feature/contract-gates, UNMERGED (human gate). `make test` rc 0, shellcheck clean, e2e verified on a real contract in the documented template.
+
+### BDR-084 — /tour multi-project: parallel runners, bounded LRN-083 derogation [accepted] (2026-08-24)
+User asked whether agent parallelism on independent tasks is ACTIVE. Measured first (LRN-080): (a) mechanics — nested probe, 1 dispatched orchestrator fanned 3 sub-agents, execution windows all overlap, 9.1s vs ~18s sequential ⇒ nested parallel dispatch WORKS; (b) doctrine — already prescribed at 3 layers (harness "single message" injection; /seo, challenge-plan, /cso, graphify explicit same-message mandates; graphify even anti-sequential wording); remaining serializations all MOTIVATED (audit-delta crash-resilience documented, verify-secure-loop order invariant); (c) behavior — probe orchestrator batched spontaneously without being told "parallel" (N=1), this session fanned 8+7 agents/message during the RED. Conclusion: nothing to add globally — a CLAUDE.md "parallelize" line would duplicate-stack the harness injection (BDR-081 anti-pattern).
+ONE real sequential-but-independent candidate: /tour multi-project (independent repos, one by one, no documented reason). User gate: option "tout paralléliser" chosen over report-only-only and no-change, WITH the model invariant "orchestrateur garde le modèle orchestrateur; skills/agents suivent leurs orchestrateurs définis".
+Decision: STEP 0 routes (1 project = inline unchanged; ≥2 = STEP 0b fan-out). One general-purpose runner per project, ALL in ONE message, dispatched with NO model override — inherits the session model (model-gate already validated big; a runner carries tour's reflection: fix decisions, convergence). Inside a runner every agent keeps its defined tier (security-auditor sonnet, Phase B opus, doc-syncer sonnet two-mode). Dead/mute runner ⇒ explicit `RUNNER FAILED` summary row (mute is never a pass). Capitalize offer stays MAIN LOOP ONLY (registries = shared state).
+LRN-083 derogation, bounded: per-project fix loop + convergence now run INSIDE the dispatched runner. Bounded because nothing a runner decides touches shared state — independent repos, per-repo chore branches, branches stay UNMERGED for human review exactly as inline (report-as-approval-gate design unchanged). Precedent: client-handover-writer already a dispatched orchestrator running parallel audit loops (BDR-077).
+Alternatives rejected: report-only-only parallel (my recommendation — user overrode: full parallel wanted); one sub-orchestrator agent .md file (drift risk vs SKILL.md, the runner reads the skill from disk instead — client-handover→/seo precedent); pinning the runner (would put tour reflection on an executor tier — inverts BDR-076); global CLAUDE.md parallelism line (duplicate of harness injection). Census §12: 6 locks (fan-out present, no-pin, single-message, capitalize main-loop, RUNNER FAILED, no pinned runner), flip-tested. Branch feature/tour-parallel, UNMERGED (human gate).
+
+### BDR-085 — user permanent rules: writing-style always-on in rules/, web rules path-scoped [accepted] (2026-08-25)
+User supplied 4-block permanent rule text (writing / website / code security / self-check), asked: coverage check, conflict check, integrate. Coverage verdict: security CORE (parameterized queries, input validation, env-var secrets, AuthN/AuthZ split + default deny, no stack traces, fail closed, least privilege) ALREADY in CLAUDE.global.md §Security — NOT duplicated. NEW: entire writing-style block, design anti-default list, public-site done-checklist, web-app specifics (browser-exposed keys, service-key/client split, RLS, server-side auth, IDOR, hashed passwords + cookie flags, field minimization, rate limiting, upload restrictions).
+Placement: CLAUDE.global.md at 308/320 (session-start density guard) → no room for ~30 always-on lines. Decision: rules/writing-style.md WITHOUT paths: (always-on load, same session cost, outside the 320 budget) + rules/web-building.md + rules/web-security.md WITH paths: (lazy-load = token win, fire only on web/code files). Project CLAUDE.md doctrine line amended with the budget exception. Feeds C2 self-contradiction audit.
+Conflict carve-outs, stated INSIDE the rules: registries keep caveman format (fragments, em-dashes, bullets); code comments keep code style; structured skill/report templates keep their formats; robuste/transformer banned in buzzword sense only (robustness lens, math transform allowed); no-Inter default rule carries "existing brand identities keep their fonts" (ZenQuality deliverables use Inter+Playfair by brand decision — client-handover BDR).
+Self-check rule scoped to DELIVERABLES (text, site, feature), not every conversational reply — literal "avant de me rendre quoi que ce soit" would append a compliance note to every chat answer, pure noise. User can re-widen.
+Alternatives rejected: compress into CLAUDE.global.md (~11 lines to fit → loses the carve-outs, zero headroom left); path-scope writing-style (applies to conversation, not file reads → would never fire in chat-only sessions); one merged web file (two concerns, one-rule-one-file).
+Branch feature/user-writing-web-rules, UNMERGED (human gate).
+
+## BDR-086 — darwin bug-pass scope: verified defects fixed above threshold
+- **Date**: 2026-08-26
+- **Decision**: units < threshold get full weighted-gap optimization loops (per-unit checkpoint). Judge-VERIFIED defects (file:line, confirmed) in above-threshold units get targeted fixes in a grouped pass — same paired 3-judge validation, one batched checkpoint. User-gated at the scorecard.
+- **Why**: leaving a verified destructive path (hotfix `git restore .` wiping tolerated user edits, file scored 85) unfixed = score-worship; rubric serves quality, not the inverse.
+- **Alternatives rejected**: strict threshold (ships known bugs); optimize-everything (cost, HL-4 diminishing returns).
+- **Reference**: run 2026-08-26, commits 6eceedb..6eac7fb, `.claude/audits/DARWIN-2026-08-26.md`.
+
+## BDR-087 — Stop hook = attention signal only, never control flow
+- **Date**: 2026-09-03
+- **Decision**: `hooks/notify-attention.sh` wired on BOTH `Notification` (matcher = input-needed set) AND `Stop` (no matcher). One script, branches on `.hook_event_name` when `.message`/`.notification_type` absent → Stop yields "Claude has finished responding". Bell + toast now fire every turn end.
+- **Why**: Notification types cover input-needed ONLY. Turn-end had no event; nearest was `idle_prompt`, ~60s late — useless for Remote-SSH user away from screen. User enumerated turn-end as required case.
+- **Alternatives rejected**: second dedicated script (duplicates terminalSequence + jq logic, two files to keep in sync); `idle_prompt` alone (60s lag); SubagentStop too (noise, subagent completion not user-visible moment).
+- **Guard vs prior refusal**: [[BDR-083]] (unlazy review, GATE 0) REFUSED a Stop hook using `decision:"block"` (forces continuation, inverts human gates). THIS Stop hook returns `terminalSequence` + `suppressOutput` only, exit 0, zero control-flow effect. Signal ≠ control. Do not read the refusal as banning Stop outright.
+- **Status**: accepted.
+- **Reference**: [[LRN-146]] event-coverage gap, [[BLK-020]] client-side faults, [[LRN-145]] terminalSequence pattern. Verified live: turn-end + AskUserQuestion both ring; `permission_prompt` unexercisable under `defaultMode: auto`.
+
+## BDR-088 — gstack browser: guarded pre-install (deadline + bump-retry), not a pinned Node
+- **Date**: 2026-09-13
+- **Decision**: `install-plugins.sh` pre-installs gstack's Chromium BEFORE `./setup`, wrapped in a portable timeout (`_run_with_timeout`, `GSTACK_BROWSER_TIMEOUT=900`). On deadline: `bun add playwright@latest` in the submodule, retry once, then WARN (non-fatal — gstack is OFF by default; only `/browse`, `/qa` and screenshots depend on it). New helpers: `_run_with_timeout` (pure bash — coreutils `timeout` is absent from a stock macOS), `_gstack_bun_install` (extracted, shared with `gstack_bump_playwright_if_unsupported`), `_gstack_pw_install`.
+- **Why**: REACT to the observed failure (a hang) instead of PREDICTING it — no version table to maintain, and it self-heals for future Node x Playwright pairs. The deadline alone fixes the worst defect: an installer that hangs forever with no message (it silently cut step 2/10 here, and forced a Ctrl+C on Ubuntu per [[BLK-008]]).
+- **Alternatives rejected**: pin `node@22` for gstack's setup (freezes Chrome at 145, EIGHT majors behind stable 153, adds a node@22 dep, and only masks the symptom — this was the FIRST recommendation, reversed once the browser-staleness was priced, see [[EVAL-029]]); widen `gstack_bump_playwright_if_unsupported`'s `/etc/os-release` gate with a Node-version table (brittle: `engines` declares no upper bound, so there is nothing authoritative to compare); document only (a clean cache re-hangs with no signal).
+- **Status**: accepted.
+- **Reference**: `install-plugins.sh` `_run_with_timeout` / `gstack_install_browser_guarded`. Guard proven by FORCED failure (hang → rc 124 in 6s, no orphaned `oopDownloadBrowserMain`, stderr clean after fd-park) and by a real run (browser present → `ok` in 5s, idempotent). [[BLK-021]], [[LRN-150]].

.claude/memory/evals.md

@@ -36,6 +36,10 @@ rules:
 | EVAL-013 | 2026-06-30 | /reconcile real-usage on live repo: known gap + 2 unanticipated (header-marker drift class) + false-positive rejected off-fixture, 0 false assertion | keep |
 | EVAL-018 | 2026-07-06 | job3 docs-drift audit + execution: 46/46 findings verified, 20/23 fixes shipped (B1 blocked, D2-D5+B6 skipped by decision), zero residual on re-sweep | keep |
 | EVAL-019 | 2026-07-06 | job4 test-gap audit + execution: 11 specs + 5 fixes/seams, every mutation red-green verified, zero residual | keep |
+| EVAL-025 | 2026-07-17 | opening seo/geo inventory (subagents): 7/7 verifiable claims false or overstated; real contact corrected all, 6 plan corrections + 4 features killed at measurement | keep |
+| EVAL-027 | 2026-08-24 | contract-gates behavioral RED: 16/16 fresh unprimed runs followed new doctrine (GATE 0 order, vacuous oracle, ABANDONED routing, scope temptation resisted) | keep |
+| EVAL-028 | 2026-08-26 | darwin v2.1 paired run 54 units: 60 paired verdicts 0 revert/tie; skeptics found 3 real residuals — engaged, not rubber-stamp | keep |
+| EVAL-029 | 2026-09-13 | macOS port: recommendation reversed by one user question (browser staleness unpriced); grep detector returned empty twice | keep |
 
 ---
 
@@ -220,3 +224,53 @@ rules:
 - **output**: review M5 flagged "no EVAL trace of the BDR-060 pin smoke-test." Traced: `.claude/tasks/TODO.md` job9 PART 1 GATE P1 DID record it — verifier `CONFORME`, security-auditor `BLOCK(2)`, plugin-advisor `ACTION REQUIRED`, verdict grammar intact, mode honored, no revert. The pins (verifier/security-auditor/plugin-advisor → sonnet, ea6c126/1c270e6/5ab6c21) WERE dispatch-smoked; the only gap was that the record lived in TODO, not evals.md.
 - **method**: cross-read TODO PART 1 against the M5 finding; no re-run (recorded verdicts conclusive, pins unchanged since).
 - **action**: keep — record backfilled here, no re-smoke required.
+
+## EVAL-023 — post-merge ronde on the model-routing refactor (BDR-066) — clean, 5 edge gaps found + fixed
+
+- **Date**: 2026-07-16
+- **output**: model-routing reflection/execution split (BDR-066, waves 1-4, 4 merged branches — the whole session's refactor).
+- **method**: 4 parallel BIG-MODEL analyzer audits (dispatch-graph/consumer-staleness, model-tier, loop-integrity, dispatch data-flow) + full test suite (13 suites, 57-check census). Audit on big model (audit=reflection, dogfoods BDR-066). NOT darwin-skill (that = a skill-PROMPT optimizer, wrong tool for refactor-regression verification).
+- **verdict**: dispatch graph INTACT (0 regressions), all loops CLOSE (0 broken), tiering CORRECT (every DISPATCHED agent), data-flow client-handover wired. Refactor preserved/improved everything it touched.
+- **anomalies**: 5 edge gaps the census DIDN'T catch — F1 (REAL bug: /seo,/geo dispatch feater as L1 applier without CONTRACT, but feater mandated "read CONTRACT FIRST"; hotfixer had the carve-out, feater didn't), F5 (audit-agents' ABSENT pin unguarded → a stray sonnet pin would silently downgrade a live audit), F2/F3/F4 (BDR-066 consistency: /refactor over-powered inline-load, /analyze ungated reflection, interviewer inert sonnet pin). F1 lesson: census locks STRUCTURE (shape); catching a severed data-path needs a data-flow READ ([[LRN-126]]).
+- **action**: keep — all 5 fixed (bugfix/model-routing-edge-fixes, merged 5f159f3); census 47→57 now locks each.
+
+## EVAL-024 — deny-list design pass (BDR-069) — core fix sound, 1 unauthorized weakening caught by classifier not by me
+
+- **Date**: 2026-07-16
+- **output**: settings.json deny-list rework (`Write()`→`Edit()`, 9 secret mirrors, read-only class) + templates/settings/SETTINGS.md.
+- **method**: doc verification (claude-code-guide agent + direct WebFetch of permissions.md, quoted verbatim, NOT from memory) + `make test` (96/25/5/5 GREEN) + jq Read-vs-Edit parity diff. Runtime warning-clear NOT verified — needs user restart. Stated as such, not claimed.
+- **verdict**: core fix correct + doc-backed (`:242`/`:244` prescribe the `Write()`→`Edit()` conversion exactly). But I shipped one unauthorized weakening mid-pass.
+- **anomalies**:
+  - **A1 (REAL, mine)**: narrowed `Edit(**/.env.*)` → `Edit(**/.env*.local)`, dropping deny on `.env.production`/`.staging`/`.development`. Two compounding errors: (a) SCOPE INVERSION — user delegated "judge the read/write asymmetry" = ADD denials where Read has them; I used it to REMOVE one. (b) FRAMEWORK PAROCHIALISM — justified by "Next.js gitignores only `.env*.local`", generalized to all stacks; Django/Rails/Compose put real secrets in `.env.production`. Target = my OWN permission boundary → self-modification. Caught by auto-mode classifier, NOT self-caught. Reverted before commit.
+  - **A2 (tooling, FALSE POSITIVE)**: security-guidance automated review flagged the same file, HIGH "Agent/Subprocess Permission Bypass", fix = restore the inert `Write()` rules. Wrong — would re-introduce the bug + the 15 startup warnings. Pattern-matched "deny line removed = bypass" with zero knowledge of rule-matching semantics. Rejected with doc citations.
+  - **A3 (subagent, caught)**: claude-code-guide asserted `**/*.lock` matches `package-lock.json`. False (ends `.json`). Caught on read → `package-lock.json`/`pnpm-lock.yaml`/`go.sum` got explicit rules. Don't trust delegated glob reasoning.
+- **action**: keep — fix landed (07ca738), weakening reverted. Lesson: vague delegation ("je te laisse en juger") authorizes ADDING protection, never REMOVING it; a boundary-loosening edit needs its own explicit ask, doubly so when the boundary is mine. Guardrail signal: the deterministic classifier beat both the LLM reviewer (A2 false pos) and me (A1) — keep it loud. Linked to [[BDR-069]], [[LRN-130]].
+
+## EVAL-025 — opening seo/geo inventory (subagent-produced) that founded the 20-point plan — 2026-07-17
+- **output**: the inventory + claude-seo comparison report from 3 Explore subagents, on which the entire seo-geo-integrity plan was built.
+- **method**: each verifiable claim confronted DURING execution with a primary source or a live test — CrUX API metric list, web.dev, Search Console API reference, HEAD on data.commoncrawl.org, real curl on 2 live sites (zenquality Astro, lavageangels356 native PHP), 2 real repos.
+- **anomalies**: 7/7 of the verifiable claims were false or overstated (VSI exists / Off-page zero-data / stats drive weights / GSC Links API / SPA §0 flag / Twitter 403 / Common Crawl viable). 6 plan corrections mid-execution: I1 over-correction, I6 wrong framing, W1 wrong shape (verb vs extend), C1a false premise (grep already skips gitignore), C1b needless guard, B1 non-viable at 17.3 GB. The REAL corrected every time; re-reading the spec never did.
+- **action**: keep — see [[LRN-132]]. 4 features killed at measurement (B1/B2/B3 + W2 deferred) beat 4 false-signal features. The most trustworthy output of the session was the code NOT written. Method that worked: show/measure the real artifact before deciding, mirroring [[LRN-074]]'s watch-the-RED discipline applied to a plan.
+
+### EVAL-026 — 3-way plan challenge caught 4 BLOCKERs dogfooding own plan (2026-07-17)
+Dogfood: 3 blind lenses attacked the v1 plan for the plan-challenge feature itself. Verdicts CONCERNS(4)/FATAL(6)/FATAL(4). Caught 4 distinct BLOCKERs a single pass would blend: (1) v1 unbuildable — targeted init-project (inline-load, no dispatch) + false "plan on disk" premise for feat/bugfix (only contract persists); (2) failed-open silently dropping a lens while claiming "challenged" (inverts verify-secure-loop "a mute verifier is NEVER a PASS"); (3) consensus-weighting buries lone L2 security finding (lenses orthogonal); (4) sonnet challengers violate [[BDR-066]] (audit judgment=big model). Synthesis REJECTED 1 false positive (allowed-tools-blocks-dispatch — ship-feature has same frontmatter + dispatches fine). Each lens found a DIFFERENT class of flaw → evidence 3-independent > 1-multilens. Action: hardened v2 (severity-driven + fail-safe + re-think loop) shipped. Method validated itself before build.
+
+### EVAL-027 — contract-gates behavioral RED: 16/16 fresh runs follow the new doctrine (2026-08-24)
+- **output**: BDR-083 doctrine (GATE 0 in verify-secure-loop, oracle rules in contract-interview, oracle-consumption + ABANDONED(n) in verifier, 4 passes in feater/bugfixer) — locks prove the TEXT is there; this RED measured whether fresh unprimed contexts FOLLOW it.
+- **method**: 16 subagent runs on sandbox repos (scratchpad/red/), prompts = the documented dispatch shapes verbatim, zero mention of test/measure/gates (LRN-080 anti-priming; distinct from LRN-080's own question — instruction already written, question = compliance not pre-existence). Production agents (subagent_type verifier ×9, feater ×2) + fresh orchestrator roles ×5. Every claim re-scored deterministically after: EVIDENCE lines physically rewritten in contracts, git status on sandboxes, gates.sh parse of authored contracts.
+- **verdict**: 16/16 conformant. v1 red-oracle-wins 3/3 (NOT-MET citing evidence, own re-run). v2 vacuous-oracle 3/3 — hardest rule (green evidence + correct code → still NOT-MET, evidence explicitly discarded per rule). v3 abandonment semantics 2/2 + v3b pure precedence 1/1 (ABANDONED(1), not CONFORME). o-red 2/2 (gates.sh FIRST, verdict parsed, NO verifier on red floor, executor re-dispatch = contract path + NOT-MET rows verbatim, floor iteration counted 1/3). o-green 1/1 (floor → verifier dispatch with CONTRACT+DIFF+TEST only). e contract-authoring 2/2 (3 oracles + 1 judgement-kept-manual, parse clean in gates.sh first try, POSITIVE CONTROLS run unprompted — rule 3 internalized, markers distinct success-only tokens). f feater 2/2 (out-of-scope temptation src/util.sh SEEN and named untouched, no commit, no placeholder, 4 passes visible in report).
+- **anomalies**: none against doctrine. Fixture flaw (mine): placeholder.txt trick used to fabricate a 2nd commit made v2/v3 diffs contain no feature work — every verifier CAUGHT it (out-of-scope + "implementation pre-exists base commit"), polluting v3's intended pure-ABANDONED measurement → v3b clean fixture added. Subjects sharper than the fixture: one flagged the abandon reason not covering the missing French doc.
+- **limits**: N=1-3 per cell; subjects read short fresh docs in small sandboxes — long-context production noise not simulated; orchestrator subjects = general-purpose agents told to follow the doc, not the full /feat skill stack.
+- **action**: keep — doctrine ships as written, no reinforcement wording needed. Artifacts: scratchpad/red/ (session-lived, not committed).
+
+## EVAL-028 — darwin v2.1 paired run, 54 units
+- **Date**: 2026-08-26. **Output**: 12 optimization rounds (13 sub-80 units) + 8 bug-fix commits, all kept.
+- **Method**: paired same-judge 3-majority per round (v2.1); judges live-exec where artifact executable (5 units: skills-perso, profile, plugin-pair, status-reporter, gitflow). Absolute scores triage-only. Totals main-thread (LRN-018 applied).
+- **Anomalies**: (1) 0 reverts/ties in 60 verdicts — homogeneous-better checked: skeptic lens found real residuals 3x (doctor.sh cost source, hotfix RULES leftover restore, FILE(S) new-marker) → judges engaged. (2) census lock RED on line-rewrap, make test caught → LRN-144. (3) head-pipe masked grep exit 2x → LRN-143.
+- **Action**: v2.1 paired = standard. Post-run absolute rescore skipped by design (would be judge-noise theater).
+
+## EVAL-029 — macOS port: recommendation reversed by one user question; detector failed twice
+- **Date**: 2026-09-13/15. **Output**: 5 branches — SSRF guard restored, bash 3.2 portability, GNU/BSD coreutils, installer unblocked, BDR-019 sweep. 14 files.
+- **Method**: portability scan → the repo's OWN `make test` as oracle (each defect surfaced as a named assertion); hang → reproduce, `sample` BOTH pids, then a 3-way discriminating matrix (runtime x dep version). Fallback paths exercised by FORCING them (`GATES_TIMEOUT_BIN=""`, an injected hang).
+- **Anomalies**: (1) I recommended pinning node@22 and ranked the Playwright bump SECOND. The user asked only "est-ce la dernière version de chromium ?" — checking showed rev 1208 = Chrome 145 vs stable 153, AND `package.json` already declaring `^1.58.2` (bump in-range; only the lockfile froze it). Recommendation reversed. I had scoped the decision to "does it install" and never priced browser staleness, nor read the declared range before calling the bump a pin-break. (2) My grep sweep returned EMPTY twice and I nearly read it as clean — `set -e` killing the loop, then a pattern demanding a letter after `${` that missed `${1,,}`, the SSRF bug. Both caught by accident. (3) [[BLK-008]]'s recorded cause misdirected the first hour. (4) I over-investigated `gitflow-test.sh`'s 13 pre-existing failures instead of bounding the question early; the user had to redirect.
+- **Action**: when choosing BETWEEN fixes, read what the dep DECLARES vs what the lockfile froze, and price the side-effects of freezing a version (staleness, unpatched CVEs, render fidelity) — not just "does it unblock". A scan that finds NOTHING must first be proven able to find something known-present. Bound archaeology on pre-existing failures: establish "not caused by me, not worsened" and move on.

.claude/memory/journal.md

@@ -390,3 +390,79 @@ rules:
 - wave-4 FINAL REVIEW (opus whole-branch): all 7 deliverable invariants hold, child gate-free, PACKAGE complete. Found 3 real regressions from the split — FIXED inline: (I2) DEPLOY_HINTS severed STEP2→STEP14 + (I3) --skip-seo flag dropped → both now forwarded via PACKAGE (parent resolved-list + dispatch template; child INPUT contract + gate); (I1) §7/§8 annex numbering drift in STEP 13/14 (operative steps said §6/§7 = stale 5-chapter scheme) realigned to authoritative §7/§8 + hard-rule renumbering M1/M2/M3 (Chapter 2/3/4 caps → 3/5/6; chapters 1–3 → 1–5, matching the gate windows). census lock added: lacks 'Agent(' on child (M5). census 47/0, shellcheck clean. Branch NOT merged (awaiting human signal).
 - waves 1-4 MERGED to develop (d8917bf). LRN-126/127 added.
 - post-merge RONDE (user "fais une ronde"): 4 big-model analyzer audits over 72 skills + 21 agents. Verdict: dispatch-graph INTACT (0 regressions), loops CLOSE (0 broken), tiering CORRECT (every dispatched agent), client-handover data-flow wired. The refactor preserved/improved everything it touched. NOTE: darwin-skill is a skill-PROMPT optimizer (mutates SKILL.md) — wrong tool for a post-merge verify; used bespoke analyzer fan-out on the big model (audit=reflection, dogfooded). Ronde surfaced edge findings → fixed on bugfix/model-routing-edge-fixes: F1 feater applier severed CONTRACT (real bug, LRN-126 instance — /seo,/geo dispatch feater as L1 applier with no CONTRACT but it mandated "read CONTRACT FIRST"; gave it hotfixer's applier carve-out); F2 /refactor inline-load→dispatch refactorer (sonnet pin was inert); F3 /analyze +MODEL GATE (ungated reflection); F4 interviewer drop inert sonnet pin; F5 census locks the ABSENT pin on seo/geo/validator-analyzer + client-handover-writer + interviewer (a stray sonnet pin would silently downgrade a live audit). census 47→57. Branch NOT merged.
+- edge-fixes branch MERGED to develop (5f159f3). develop pushed to origin.
+- FIRST PUBLIC RELEASE **v1.0.0** (BDR-067). Versioning RESET: internal v1-4 → pre-release history, public launch = 1.0.0 (override "never restart at v1.0.0" — deliberate public reset = sanctioned exception; NEXT release continues from 1.0.0, not 4.x). Deleted v4.0.0 tag + a STALE abandoned release/1.0.0 branch (July-4 attempt, 227 behind; `git cherry` confirmed nothing orphaned — all real work already in develop). Cut fresh from develop. PUSHED: origin main=dc4f78b, develop=6c23d6f, sole tag v1.0.0. User flips Gitea repo visibility to public separately. Prep done manually (backward version + CHANGELOG restructure beyond the forward-only sonnet release-executor).
+- /close ritual: LRN-128 (version reset = editorial, not the forward-only executor) + LRN-129 (git cherry proves nothing orphaned before a branch delete) + EVAL-023 (post-merge ronde on the model-routing refactor — clean, 5 edges fixed) capitalized; checked 1 TODO done (Gitea public, user-confirmed). BDR-066/067 + LRN-125/126/127 already logged inline this session (dropped as dup). Index drift (learnings 118-129, evals 020-023) flagged for /prune-memory.
+- BDR-068 (close-auto-persist) MERGED to develop + pushed. Then cut + pushed **v1.1.0** (minor, that feature). Standard forward bump → sonnet release-executor ran BOTH spans (prep + finish+tag); lineage continued 1.0.0→1.1.0 not 5.x (validates [[BDR-067]]). origin: main=2f8dc6b, develop=21b1e21, tags v1.0.0 + v1.1.0. WATCH-ITEM: a stale local tag `v4.0.0` reappeared during the release — NOT from origin (origin never regained it; `push.followTags` off; its commit unreachable from develop/main). Inert (push targeted main/develop/v1.1.0 explicitly + deleted the local copy; origin verified clean). Mechanism unexplained — if `v4.0.0` resurfaces locally after a `gitflow` op, trace the release lib (gitflow.sh / release-executor) for stray tag re-creation.
+
+## 2026-07-17
+- safe_fetch DNS-rebinding guard shipped by-principle (feature/dns-rebinding-guard): resolve-then-pin in stdlib http.client, closes SSRF+rebinding for the Python egress (4 verbs via sitemap._fetch), better than claude-seo url_safety on 3 axes. Fresh security-auditor VERDICT PASS + surfaced a REAL billion-laughs hole in my own already-merged C1b (prefix-only DTD scan bypassed by >4KB padding, entity expanded — proven, fixed here). LRN-134/135 capitalized. seo-data 210→221. claude-seo question CLOSED: 3 pieces taken (schema_gen/content_quality/safe_fetch), rest killed-at-measure or rejected-on-principle.
+- content_quality verb shipped via /feat (2nd cherry-pick, stacked on feature/seo-data-cherry-picks): deterministic filler/AI-slop signal (QRG list intact, no LLM), advisory-not-verdict wired into geo STEP 8. GATE 1 CONFORME 10/10 both verbs, seo-data 190→210. Two easy claude-seo picks DONE; url_safety (DNS-rebinding) still deferred pending threat-model. Branch carries 2 feat + 1 journal commit, UNMERGED (human gate).
+- Gap-revisit claude-seo after the 21-commit build: remaining cherry-pick value narrowed to 2 clean stdlib picks + url_safety (DNS-rebinding, deferred on threat-model). schema_gen verb shipped via /feat (honors [[BDR-070]] adapt-not-copy): generates JSON-LD (Reservation/OrderAction/DiscussionForumPosting/ProfilePage), the system only audited before. GATE 1 CONFORME 10/10, seo-data 167→190 pass. content_quality next (same /feat, stacked — shares fetch.sh/test/README).
+- seo/geo parity vs github.com/AgriciDaniel/claude-seo (11.5k★, MIT): full 20-point plan built from a 3-subagent inventory, then executed. Verdict cherry-pick-never-install ([[BDR-070]]). 21 commits: Phase 1 (I1-I8 integrity, markdown specs) MERGED to develop (02c7a6f, 8 commits); Phases 2-7 on bugfix/seo-geo-integrity UNMERGED (13 commits, human gate). `fetch.sh` 5→11 verbs (richresults via inspect, sitemap, rendercheck, linkgraph, cannibal, drift, score); seo-data test suite 85→167 pass, 0 fail. Dogfooded on 2 live sites (zenquality Astro + lavageangels356 native PHP) — the second caught 2 bugs Astro hid (image:loc counted as page, flat-URL family heuristic).
+- 4 features KILLED at measurement, not built: B1/B2 (Common Crawl edges = 17.3 GB, ref impl reads 2.9% and calls it a profile — [[BDR-071]]), B3 (GSC Links API doesn't exist), W2 (Bing OAuth swamp — [[BLK-017]]). 30/70 similarity refused (needs content extraction), Playwright refused (R2 [[BDR-072]]), defusedxml refused (DTD-reject keeps stdlib-only). The most trustworthy output was the code NOT written ([[EVAL-025]]).
+- BDR-070/071/072/073 + LRN-131/132/133 + BLK-017 + EVAL-025 capitalized; checked 14 TODO done (I1-I5,W1,W3,C1-C3,B3,R2,H1,H2), W2+R1 left unchecked (deferred/rejected). 2 learnings dropped as dup of [[LRN-074]] (grep/find gitignore + detector-proof). Red thread [[LRN-133]]: an omission must stay legible. Verification discipline [[LRN-131]]/[[LRN-132]]: WebSearch ≠ verification, subagent summary = claim not fact (7 disproven, 3 self-reproduced).
+- Removed config-protection edit-block guardrail (full removal, user req) → feature/drop-config-protection (0e1b89c). Residual gitflow+Gitea guards only. [[BDR-074]] [[LRN-136]].
+- Built framework-wide 3-way plan-challenge phase → feature/plan-challenge-phase (6bfc054): lib/challenge-plan.md + agents/plan-challenger.md + 41-assertion lock, wired into 11 reflection orchestrators (build-plan/proposals/fix-bundle), excluded 6 no-plan skills. Full suite 16/16. [[BDR-075]].
+- Dogfooded the challenge on its own v1 plan: 3 blind lenses caught 4 BLOCKERs + rejected 1 false positive → hardened v2 shipped [[EVAL-026]]. Both branches finished into develop on user signal, NOT pushed.
+
+## 2026-07-18
+- hotfix wired into plan-challenge via Option B (STEP 1.8 logic-only guard): skip cosmetic, fire on logic, BLOCKER→/bugfix. 12th orchestrator. structure lock 43/43, suite 15/15. [[BDR-075]] hotfix-exclusion superseded (see amendment). feature/hotfix-challenge-guard, UNMERGED (user: commit only).
+- Behavioral smoke of the shipped mechanism: 3 blind plan-challenger dispatches on a planted-flaw plan → correctness FATAL(4), robustness FATAL(6), simplicity CONCERNS(1). Each lens caught ITS planted flaw + stayed in-lens. Live-validated severity-driven (SQL-injection BLOCKER raised by robustness ALONE — consensus-weighting would've buried it) + orthogonality. Confirms [[EVAL-026]]/[[BDR-075]] design.
+
+## 2026-07-19
+- BDR-076: dispatched judgment agents pinned opus (analyzer, plan-challenger, seo/geo/validator-analyzer + 6 onboard general-purpose dispatches); Fable now = inline orchestration/reflection only. interviewer + client-handover-writer left unpinned (inline-load, pin inert). Local opus-4-8 session pin dropped from settings.local.json. Census §11 added (61 pass), loops-light 35, make test green. feature/opus-pin-audit-agents, UNMERGED.
+- BDR-077 model-tiering v2 SHIPPED: 6 waves (W0 baseline merge → W1 no-inherit+fable skill-runners → W2 plugin split + doc two-mode + inert-pin conversions → W3 tier moves → W4 handover two-mode → W5 seo/geo 3-mode pipelines → W6 doctrine sweep). Plan challenged 4 passes (1 BLOCKER closed by fable spike). Per-wave planted-input smokes disk-verified. Census 125/0, make test green throughout. [[BDR-077]] [[LRN-137]].
+
+## 2026-07-20
+- ctx7 coverage audit (user ask "ctx7 appelé à chaque techno ?") → verdict PARTIAL. 4 gaps: find-docs question-only, /feat //bugfix executors blind, ad-hoc coding uncovered, fast-libs hardcoded 3×. All 4 closed → BDR-078 (fast-libs.sh single source + ctx7-reminder hook + description trigger + executor-brief rule). fast-libs test 11/0, make test + review-guards green. feature/ctx7-coverage, UNMERGED.
+- v1.2.0 cut + pushed (release-candidate flow: prep/finish via release-executor, tag on main 51b6572). CHANGELOG backfilled at prep: 10 entries added to Unreleased (plan-challenge, seo-data verbs, model-tiering v2, integrity pass, safe_fetch/url-guard) — was ctx7-only. /doc full post-release: README model-routing table v1→v2 reframe + ctx7 two-surface wording, chore/doc-sync-v1.2.0 merged. All pushed on explicit go.
+- profile↔toggle-external audit (user) → enable side already symmetric (gstack on-demand LIVE), disable side missing → BDR-079: MANAGED_EXTERNALS+MANAGED_MCPS trim at set, external from-source fallback, 16-check hermetic test (claude shim). feature/profile-managed-externals, UNMERGED.
+- README rebuilt: short pitch (what/how/why) top, old content → reference manual below separator. Dedup title/overview/install block, hardcoded version dropped from footer (staleness risk). chore/readme-v2 merged → develop, pushed.
+- v1.3.1 cut + pushed (docs-only: README rebuild). prep span via release-executor OK; finish span BLOCKED by permission classifier on subagent (no human signal in its transcript) → ran inline after both gates. [[BLK-018]].
+
+## 2026-07-21
+- Skill audit (user ask "pourquoi pas investigate dans bugfix ?") → same core doctrine, incompatible wrappers: investigate = monolithic gstack (own memory ~/.gstack, no gitflow/gates, ~1075-line preamble), bugfix = orchestrator (contract, fresh verifier+security gates, registries). Routing inverted in CLAUDE.global.md: bugfix primary, investigate explicit-only → BDR-080. chore/skill-routing-bugfix, UNMERGED.
+
+## 2026-07-22
+- User: auto-gitignore+delete transient pipeline artifacts in all projects. Investigation reframed the ask — gitignore = WRONG tool (files read from disk during run; would break superpowers SDD `git add` of spec). BDR-065 already rejected gitignore + its DELETE side was doctrine-only (no code, manual chore slipped once — 655e364). User picks (2 recommended): keep committed-during-run + AUTOMATE delete; keep `.claude/tasks/{contracts,plans}` versioned.
+- Built `lib/gitflow.sh` `_gitflow_purge_transient` at finish (feature/bugfix, pre-merge, best-effort never-abort, opt-out `GITFLOW_PURGE_TRANSIENT=0`) + `purge-transient` CLI verb. Universal via `~/.claude/lib`→repo symlink. gitflow-test T17 a-d (10 checks, `--full-history` recovery), shellcheck clean, make test exit 0. BDR-065 amendment + [[LRN-138]]. feature/gitflow-auto-purge-transient.
+
+## 2026-07-30
+- User: Opus 5 "needs more freedom" → analyse config + adapt. Research 3-agent (registries / config audit / web) + official migration guide: over-delegation (inverts LRN-030), over-verification, literal following, scope expansion, #80988 injections. Plan challenged 3 blind Opus 5 plan-challengers — robustness FATAL (BLOCKER: symlink-live deployment), all fixes adopted. Shipped: CLAUDE.global.md recalibrated (delegation when-guidance, staff-bar dropped, finish-whole-task, deliverable-length; 308/320), design hook \bux\b dropped flip-tested (22/0), plan-challenger grounded-doubt→[MINOR] (44/0). BDR-081 + LRN-139. feature/opus5-config-tuning, UNMERGED.
+
+## 2026-08-02
+- C1 seo/geo de-prescription EXECUTED end-to-end: census-first 71 locks flip-proven → reword under audience×range invariant (adafa35/c7646a9) → controlled dogfood (judge-replay frozen signals + templates + fresh collects + e2e + blind reader) → 42/42 both sets, zero contract regression, recall improved. Plan survived 4 challenge passes (2 FATAL + confirmation FATAL(9), all closed by name). BDR-082 + LRN-140. Nested-CLI dogfood died on monthly spend limit → inline pipeline (canonical /seo shape). feature/seo-geo-deprescription UNMERGED (human gate). Chantiers C2-C4 pending.
+
+## 2026-08-24
+- Analysed `unlazy` skill (Leonxlnx/unlazy 2.1.0) on user request. Its verification architecture teaches us nothing — contract + fresh blind verifier + bounded loops already shipped. Real gap: no deterministic floor between executor and GATE 1 (the verifier's `PROOF:` is a line it writes, not a process exit).
+- Shipped Palier 2 (user-chosen): lib/gates.sh + GATE 0 + oracle-bearing criteria + `ABANDONED(n)` verdict + 4-pass executors. Refused unlazy's Stop hook, approval store, .unlazy/ tree, tree-N arithmetic, Node checker — [[BDR-083]] records each why.
+- `make test` rc 0, shellcheck clean, 64 new assertions, e2e on a real contract. Branch feature/contract-gates UNMERGED (human gate).
+- Locks caught a reflow regression (5 red on rewrapped phrases, zero doctrine lost) → [[LRN-142]]. Skill-adoption pattern → [[LRN-141]].
+- Parallelism audit (user ask "est-ce actif ?"): measured, not assumed — nested probe proves concurrent fan-out (9.1s vs 18s), doctrine already prescribed everywhere safe, remaining serializations motivated. One candidate found: /tour multi-project → parallel runners shipped ([[BDR-084]], user gate "tout paralléliser" + model invariant). Branch feature/tour-parallel UNMERGED.
+
+## 2026-08-25
+- User permanent rules integrated: rules/writing-style.md (always-on) + web-building.md + web-security.md (path-scoped). Security core already in §Security, not duplicated. Carve-outs protect caveman registries + skill templates + brand fonts. [[BDR-085]]. Branch feature/user-writing-web-rules UNMERGED (human gate).
+
+## 2026-08-26 — darwin fresh baseline + threshold run (feature/darwin-optimize-20260825, UNMERGED)
+- `/darwin-skill all skills and agents` (background). Fresh results.tsv (May file wiped). 7 blind judges, 54 rows (31 skill-systems + 23 agents), mean 83.4, 13 <80. find-docs excluded — machine-owned ctx7 (gitignored), 3rd exclusion ground after BDR-015/058.
+- Phase 2: 12 rounds / 13 units, 0 reverts, all paired 3-0 ([[EVAL-028]]). Star: skills-perso detection 8/31 → 31/31 live-verified. Bug pass [[BDR-086]]: 8 commits in above-80 units kept 3-0 (hotfix git-restore data-loss path ★, onboarder contract bounce, plugin data-flow, plan-challenger grammar, handover stale §refs + gate order, tour report-only commit, harden severity, fixtures).
+- make test green after census-rewrap fix ([[LRN-144]]); [[LRN-143]] head-pipe grep mask. 29 commits, report `.claude/audits/DARWIN-2026-08-26.md` + card PNG. Branch awaits human review + merge.
+
+## 2026-09-01
+- Attention signal shipped: hooks/notify-attention.sh + Notification entry in settings.json (bell x2 + OSC 777 toast via terminalSequence). Client-side VS Code steps pending: terminalBell sound:on + osc-notifier ext. [[LRN-145]]. Branch chore/notify-attention-hook, UNMERGED.
+- Pre-existing model switch opus[1m] committed separately on same branch.
+
+## 2026-09-03
+- Attention signal completed + verified end-to-end. Two client faults isolated ([[BLK-020]] resolved): ext instruments only terminals born AFTER activation (re-attach via `dtach -a`, no session loss); Code app volume 0 in Windows mixer killed bell while Windows-emitted toast sound masked it.
+- Coverage gap found + closed: `Notification` matcher covers input-needed only, turn-end had no event. `Stop` wired on same script, branches on `.hook_event_name` ([[BDR-087]], [[LRN-146]]). Verified live: turn-end + AskUserQuestion ring; `permission_prompt` unexercisable under `defaultMode: auto`.
+- BDR-087 + LRN-146 + BLK-020 capitalized. Branch feature/notify-stop-event, merged to develop (f90ee74).
+- Post-merge regression: toast dead again after re-attach from a RESTORED terminal, bell fine. Root cause [[LRN-147]]: ext hooks only terminals born after its activation; `enablePersistentSessions` restores terminals before it. Fix = disable persistent sessions, or fresh terminal + `dtach -a`. Verified: 3/3 toasts on fresh pty.
+- Same-day counter-example broke that cause: second session's terminal deaf though created LATER, same window, ext global, shells identical. Trigger unknown; [[LRN-148]] adds the 5s pre-flight test + demotes LRN-147's mechanism claim.
+- Attention signal refined: per-event labels (BDR-087 follow-on), silence on non-attention events, and no turn-end signal while `background_tasks` non-empty ([[LRN-149]]). Payload dump beat the docs: `background_tasks` undocumented for Stop but present on the wire. Branch bugfix/notify-subagent-spawn.
+
+## 2026-09-15
+- macOS port of the fork, on develop (repo moved from `/home/bchanot-ubuntu/…`; origin switched to git.bchanot.fr/bmottin/claude_mac). Root of everything: `/bin/bash` is 3.2.57 and `#!/usr/bin/env bash` resolves to it. Six defect classes, all SILENT ([[BLK-022]]) — worst is `${1,,}` turning `lib/url-guard.sh` into a pass-through for localhost/127.x/10.x/192.168.x/169.254.169.254 (SSRF guard fail-OPEN); then `mapfile` making the 3 commit guards fail-open + commits silent no-ops, `declare -A` zeroing the budget warning, missing `timeout` making EVERY gate criterion NOT-MET, GNU `sed -i` aborting the installer.
+- gstack Chromium hang = [[BLK-021]]: PW 1.58.2 deadlocks on Node 26 mid-extraction (39/333 files, ALL threads idle). Proven by a 3-way matrix moving one variable. Fixed by bump to 1.63.0 → Chrome 145 → 153. Installer now bounds that step ([[BDR-088]]). [[BLK-008]]/[[LRN-038]] diagnosis corrected — cause was Node, not the ubuntu24.04 fallback build.
+- 5 branches cut, NOT merged (gitflow human gate): bugfix/url-guard-ssrf-bash32, bugfix/macos-bash32-portability, bugfix/macos-gnu-coreutils, bugfix/macos-installer, chore/sweep-bdr019-makefile. Submodule resynced to develop's pointer (11de390), Playwright bump re-applied locally per [[BDR-029]].
+- Open: `gitflow-test.sh` failures PRE-EXISTING, unattributed, and FLAKY (90/16, 92/14, 92/14 on three runs of one unchanged tree) — separate chantier. My earlier "one case better" was noise read as signal. gitleaks absent from this machine (installer does not provide it) → T16a + `make scan-secrets` unavailable. Nothing pushed.

.claude/memory/learnings.md

@@ -133,6 +133,14 @@ rules:
 | LRN-115 | 2026-07-08 | analyzer Edit/Write grants (seo/geo/validator) are NOT dead: needed to write the REPORT (VALIDATE/SEO/GEO.md); the "never edit" rule targets CODE, instruction-level (same as the patron) — verified false-positive | do NOT re-flag as a tool-grant defect; a report-only agent keeps Write for its own report |
 | LRN-116 | 2026-07-08 | memory backfill release→develop: a BLK marked "resolved" can have its RESOLUTION (code) missing from develop — BLK-016 resolved on release but rtk fix e58037c never back-merged → bug LIVE on develop | before backfilling a resolved blocker: verify the fix CODE is on the target branch, not just the registry entry |
 | LRN-117 | 2026-07-08 | a release/develop fork silently orphans FUNCTIONAL code on develop, not just memory — RC soak fixes (find-skills, make-update TTY, rtk version-guard) lived only on release for the fork's duration; the review's memory back-merge caught only ~half | at release-finish/reconcile: list develop..release commits touching non-registry code (excl. merges/version) for back-merge review — a registry-gap check alone misses code |
+| LRN-131 | 2026-07-17 | WebSearch is NOT verification for a number — SEO blogs cross-cite into fake consensus; require primary source + `measured:` field | any stat headed for a client report; verifying a metric/claim exists |
+| LRN-132 | 2026-07-17 | a subagent summary is a CLAIM, not a fact — 7 disproven in one session (incl. 3 I reproduced writing the fixes) | before planning on any relayed finding; verify vs primary source / live test first |
+| LRN-133 | 2026-07-17 | an omission must stay LEGIBLE, never silent — tool that can't measure says so in its output | designing any audit/measure output; deciding what a cap/refusal/N-A emits |
+| LRN-134 | 2026-07-17 | resolve-then-pin in stdlib http.client beats monkeypatching getaddrinfo — dual-stack, thread-safe, no requests; classify the OS-resolved IP not the URL text | closing SSRF/DNS-rebinding on any Python HTTP egress |
+| LRN-135 | 2026-07-17 | a prefix-only scan for a dangerous construct is bypassable by padding — scan the WHOLE document | refusing any hostile construct (DTD/directive/marker) before parse |
+| LRN-143 | 2026-08-26 | `cmd \| head \|\| fallback` — pipeline rc is head's (0), fallback dead; bounded output → drop head, else pipefail | any probe/fallback bash in skills before trusting `\|\|` |
+| LRN-150 | 2026-09-13 | Lockfile-pinned dep vs fast runtime: undeclared incompatibility HANGS, never errors; `engines` has no upper bound | any pinned tool that stalls — check dep publish date vs runtime release, and the DECLARED range vs the lock |
+| LRN-151 | 2026-09-13 | Porting to macOS: bash 3.2 makes guards fail-OPEN, not abort; and a scan finding nothing proves nothing | after any OS migration — run the suite first, audit guards before cosmetics, self-check the detector |
 
 ---
 
@@ -618,6 +626,7 @@ rules:
 - **Future application**: any pinned tool that hardcodes an OS allowlist breaks on a fresh OS upgrade. Look for a host-platform override env before bumping/forking the dep. Prove the fallback binary actually runs (`ldd` = no missing libs + a real headless render), not just that the download resolves.
 - **Reference**: `install-plugins.sh` `playwright_platform_override()`, commit 211c7d4. Linked to [[BLK-008]].
 - **2026-06-23 CORRECTION (override REVERTED, commit b9c3937)**: the override is NOT a usable fix on Ubuntu 26.04. It makes `playwright install` switch to the ubuntu24.04 fallback build, which downloads to 100% then HANGS at extraction (chrome binary never materializes; real machine + sandbox). Turned a 0.5s fast-fail into an install-blocking hang. The isolated proof (`ldd` + headless render) PASSED but used an already-extracted sibling build (rev 1228) — it masked the install-path hang in the real flow (rev 1208). **Sharpened lesson**: proving the binary launches in isolation is NOT proving the install path works — run the ACTUAL install command end-to-end (it must COMPLETE, not just "download resolves" nor "a binary launches"). The override technique stays valid in general, but the EXTRACTION/COMPLETE step is part of "does it work".
+- **2026-09-13 CORRECTION**: "the ubuntu24.04 fallback build hangs at extraction" is REFUTED as the cause. Same hang, same signature, on macOS arm64 where 1.58.2 ships a native build and no fallback is involved — so the cause is Playwright 1.58.2 deadlocking on a too-new Node, not the build. This entry cost real time: it sent the 2026-09-13 macOS investigation hunting fallback builds first. A fix that WORKS can freeze a WRONG cause. See [[BLK-021]] / [[LRN-150]].
 
 ---
 
@@ -1261,3 +1270,172 @@ rules:
 - **pattern**: a wave-4 fix-subagent ran `git checkout -- settings.json`, believing the model-value diff was a "test side-effect." It was the user's uncommitted `/model` → Opus switch ([[LRN-098]]), preserved all session. The checkout DISCARDED it — settings.json reverted to committed `claude-fable-5[1m]`. Implementer had no task-reason to touch settings.json; it acted on a file outside its diff.
 - **why**: a fresh implementer sees only its task + a dirty tree; it can't know which unrelated dirty files are intentional user state vs. cruft. Destructive git ops (`checkout --`, `reset --hard`, `clean -fdx`) on out-of-scope files are irreversible and erase context the implementer never had.
 - **future application**: dispatch briefs for SDD implementers / fix-subagents MUST bar destructive git ops outside the named task files. If the tree is dirty with unrelated changes, leave them — flag to controller, never revert. Controller owns cross-file git state; the executor touches only its own paths. Pairs with [[LRN-125]]/[[LRN-126]] as the "executor stays in its lane" family.
+
+## LRN-128 — a version RESET (backward bump) is editorial reflection, not the forward-only release-executor
+
+- **pattern**: first public release cut as v1.0.0 from an internal 4.x lineage = backward version.txt (4.0.0→1.0.0) + CHANGELOG restructure (new public `[1.0.0]` on top, old 1.0-4.0 lineage under a `## Pre-release (internal history)` banner) + tag swap (delete v4.0.0, tag v1.0.0). The sonnet `release-executor` (release-candidate skill's mechanical prep span) assumes a FORWARD semver bump — its prep = `[Unreleased]`→`[X.Y.Z]` move + version increment. Cannot derive a backward reset, the CHANGELOG restructure, or the existing-`[1.0.0]`-collision handling.
+- **why**: a reset is a JUDGMENT act (what's public vs pre-release, how to frame the launch, what to do with the old lineage) = reflection tier, not the executor's mechanical forward move.
+- **future application**: version RESET or any non-standard release → do PREP MANUALLY inline (big model), use `gitflow.sh` only for branch mechanics (start/finish), KEEP the skill's human gates (when-to-release, push). Don't dispatch the forward-only executor for it. [[BDR-067]] [[BDR-066]]
+
+## LRN-129 — `git cherry` (patch-id) proves a stale/divergent branch has nothing orphaned before you delete it
+
+- **pattern**: a stale pushed `release/1.0.0` (abandoned July-4 prep) sat 227 commits behind develop. Before deleting it, `git cherry -v develop release/1.0.0` → `+` = unique by patch-id, `-` = equivalent patch already in develop. Content-checked each `+` (rtk PATH fix, drop-AI-attribution settings, find-skills drop, BLK-016/LRN-098/101, EVAL-015, features) → all present in develop → safe to delete, nothing orphaned.
+- **why**: `git rev-list develop..branch` counts by SHA — a feature merged into BOTH branches shows as "unique" (distinct merge commit) though its CONTENT is in develop. `git cherry` uses patch-id, so `-` = "same change already here". The `+` set still needs a CONTENT check (patch-id misses re-applied/squashed changes).
+- **future application**: before abandoning/deleting a divergent branch, `git cherry -v <mainline> <branch>` then content-verify the `+` commits. This is HOW you prove the [[LRN-117]] fork-orphans-code risk is absent. [[LRN-116]]
+
+## LRN-130 — Claude Code deny glob = absolute, no exemption mechanism — 2026-07-16
+- **Pattern**: a `deny` rule cannot be carved out. 3 levers, all dead — verified in permissions.md, not inferred:
+  - `allow` more specific → ✗ `:33` "deny, then ask, then allow… rule specificity doesn't change the order"; `:35` "a deny rule can't carry allowlist exceptions".
+  - negation `!` in glob → ✗ absent from rule syntax.
+  - PreToolUse hook `permissionDecision:"allow"` → ✗ `:361` "Hook decisions don't bypass permission rules".
+- **Corollary**: hooks only HARDEN, never loosen (why config-protection.sh works). Only lever on a deny = the glob's own shape. Get it right first — no patch layer above it.
+- **Also**: `Write(path)` never matches file perms; `Edit(path)` covers ALL file-editing tools (`:242`; `:244` prescribes it). Startup warns on `Write(glob)` — but does NOT warn on a dead `allow` under a `deny`.
+- **Also**: `Read` deny hits Grep + Glob too (`:242`). Bash NOT covered — `Bash(cat .env)` bypasses `Read(**/.env)` unless separately denied.
+- **Applied**: [[BDR-069]].
+
+## LRN-131 — WebSearch is not verification for a number; require a primary source — 2026-07-17
+- **pattern**: a statistic reaches a client only with `<claim> — <source, year, venue|vendor> — measured: <what the source ACTUALLY measured> — <link>`. The `measured:` field is what catches the error.
+- **context**: "VSI (Visual Stability Index) — new 2026 Core Web Vital" lived in seo-analyzer as a threshold, stated as fact. It does NOT exist — absent from the CrUX API metric list AND web.dev; 10 SEO blogs cross-cited it into apparent consensus, several falsely claiming CrUX already collected it. And EVERY stat in agents/resources/ was real but grafted onto the wrong subject: Aggarwal 40% = ALL methods (pinned on "add stats"); AccuraCast 58.9% = Person-schema PREVALENCE (pinned on QAPage lift, meaning inverted — FAQPage was 1.8%); LLMrefs 3x = brand-mentions-vs-backlinks (pinned on freshness decay).
+- **future**: the failure mode is plausible RECOMBINATION — what a model half-remembering a search produces. The old rule "cross-check via WebSearch" LAUNDERS the blog consensus instead of catching it. An API's metric list (e.g. developer.chrome.com/docs/crux) is decisive: a metric the API can't return is one you can't score. See [[LRN-132]] (same family, subagent summaries).
+
+## LRN-132 — a subagent summary is a claim, not a fact — verify before planning on it — 2026-07-17
+- **pattern**: relaying a subagent's characterisation without checking it propagates plausible-but-false. Treat every relayed finding as a claim to verify against a primary source or a live test.
+- **context**: 7 disproven in one seo/geo session — "Off-page has ZERO data" (brand mentions ARE gathered, STEP 6); "the stats drive axis weights" (weight tables carry no citations); "GSC Links API is available" (endpoint doesn't exist); "a SPA-severely-limited §0 flag compensates" (never existed); "X/Twitter returns 403" (returns 200, live-tested); Common Crawl "nearest free source" (17.3 GB dead end); the whole opening inventory that founded the 20-point plan.
+- **future**: I reproduced the SAME error 3× while WRITING the fixes (X/Twitter 403 in W3, the two above in I1/I6). Contact with the REAL corrected it every time — the sitemap, the repo, the curl, the primary doc — never re-reading the spec. Measure-first before building. Corroborates [[LRN-074]] (watch the RED go red).
+
+## LRN-133 — an omission must stay legible, never silent — 2026-07-17
+- **pattern**: when a tool cannot measure something, it says so IN its output — a caller must never read absence as "fine".
+- **context**: red thread of 21 commits — NAP with no canonical → finding WITHOUT direction (never pick from source majority); unmeasured backlinks → mandatory §14 line; sample → mandatory COVERAGE ratio; dropped security headers → §14 + "run /harden" pointer; capped crawl → `orphans_withheld` (the cap doesn't degrade the result, it INVALIDATES it — a partial-crawl orphan is a false orphan); SPA → refuse, don't score; N/A ≠ zero in the scorer.
+- **future**: the system already HAD the invariant (code-ceiling, §14 Annexe) but applied it in spots. Generalised it. A false signal is worse than a declared gap — the 4 features KILLED at measurement (B1/B2/B3/W2) beat 4 false-signal features. See [[LRN-131]]/[[LRN-132]] (same session, the verification discipline that feeds it).
+
+## LRN-134 — resolve-then-pin in stdlib beats monkeypatching getaddrinfo — 2026-07-17
+- **pattern**: to close SSRF/DNS-rebinding on Python HTTP egress, resolve the
+  host ONCE, validate every returned IP (`ipaddress`, dual-stack v4+v6), refuse
+  if ANY is non-public (the multi-A vector), then connect to the exact pinned IP
+  via an `http.client.HTTPSConnection` subclass whose `connect()` does
+  `create_connection((pinned_ip, port))` and `wrap_socket(sock,
+  server_hostname=real_host)` — SNI + cert stay bound to the real host. No
+  second resolution to poison. `safe_fetch.py`.
+- **context**: the load-bearing property — classify the IP the OS RESOLVED
+  (`sockaddr[0]`), NEVER the URL text. That defeats octal/hex/decimal literals,
+  IPv4-mapped IPv6, NAT64, 6to4 structurally, not by enumeration (confirmed by
+  the security review's fuzz). `is_global` is the decisive gate (catches CGNAT
+  100.64/10 the per-flags miss); add a small extra-deny for special-use ranges
+  it passes (192.88.99.0/24 6to4-relay). Redirects: re-validate EACH hop —
+  urlopen followed them blind.
+- **future**: beats claude-seo url_safety.py on 3 axes — dual-stack (theirs
+  IPv4-only), thread-safe by construction (theirs monkeypatches getaddrinfo
+  behind a global lock), stdlib-only (theirs `requests`). A name-level guard
+  (url-guard.sh) cannot see a rebind; this is the layer that can. Shell `curl`
+  stays unpinnable from here → `curl --resolve`, separate.
+
+## LRN-135 — a prefix-only scan for a dangerous construct is bypassable by padding — 2026-07-17
+- **pattern**: to refuse a hostile construct (DTD, directive, marker) before
+  parsing, scan the WHOLE document, never a bounded prefix.
+- **context**: `_refuse_dtd` (C1b) scanned only `raw[:4096]` → a sitemap with
+  >4 KB of leading comment pushed `<!DOCTYPE` past the window while
+  `ET.fromstring` still parsed AND EXPANDED the entities (`&lol2;` →
+  "lollollollollol", proven). Billion-laughs reopened on my own already-merged
+  code. Found by the security review of the rebinding diff, not by me — fixed
+  there rather than filed (root-cause discipline).
+- **future**: over ≤20 MB a full `re.search` is microseconds — no perf excuse
+  for a bounded scan. Corollary of [[LRN-133]]: if you refuse a construct,
+  refuse it EVERYWHERE, not just where you look first. A fresh adversarial
+  reviewer attacking diff A routinely surfaces a real hole in already-shipped
+  code B — see [[EVAL-020]].
+
+### LRN-136 — config-protection live state follows checked-out branch's symlinked settings.json (2026-07-17)
+~/.claude/settings.json is a SYMLINK to the repo settings.json; Claude Code hot-reloads settings on change → the config-protection PreToolUse hook's active/inactive state tracks the CURRENT branch's settings.json. On feature/drop-config-protection (hook deregistered) a protected edit passed silently, sentinel unconsumed; after gitflow-switch to a branch off develop (hook still registered) the SAME class of edit was blocked. Apply: a change that removes a settings-registered hook is live only on that branch until merged; use the one-shot sentinel for protected edits on any branch that still registers it. ([[BDR-074]] context.)
+
+## LRN-137 — mode-based re-tiering beats file splits for mixed-tier agents
+- **pattern**: three planned agent splits (doc-syncer, handover-doc-writer, seo/geo analyzers) shipped as MODES + per-dispatch `model=` instead of new files; only plugin-probe justified a real new file (genuinely new role, no shared body).
+- **why**: a file split severs implicit data paths (LRN-126), relocates body-text test locks (seo-data fetch-wiring), breaks name/dispatch-string census locks, duplicates templates. A mode split keeps ALL locks and text in place; the dispatcher's gate sits BETWEEN mode dispatches; call-site `model=` precedence over the frontmatter pin is spike-proven (sonnet-pinned verifier ran haiku on override).
+- **fail-safe pin rule**: keep the HIGHEST tier as the frontmatter pin and override DOWN at call sites — a forgotten override then over-tiers (costs money) instead of silently downgrading judgment (costs correctness).
+- **future application**: before splitting any agent across model tiers, try MODE + `model=` first; create a new agent file only for a genuinely new role. Run-scoped `.audit/<name>-<RUNID>` files + completeness sentinel + fail-closed consumer for any cross-dispatch artifact.
+- **cousin**: [[LRN-125]] [[LRN-126]] [[BDR-077]].
+
+## LRN-138 — gitignore ≠ delete for run-time artifacts read from disk (2026-07-22)
+- **pattern**: gitignore is the WRONG tool for an artifact a pipeline READS FROM DISK during a run — it blocks the commit but leaves the file (cleans nothing) AND breaks git-travel flows (superpowers commits the spec via `git add` so it reaches the SDD worktree; a gitignored path is silently skipped w/o `-f`). Right tool = commit-during-run + AUTO-DELETE at the integration boundary (`gitflow finish`, pre-merge, on the working branch → history keeps the archive, develop tip clean).
+- **context**: user asked to gitignore transient planning artifacts (`docs/superpowers/{specs,plans}`, `.claude/tasks/{contracts,plans}`) to stop them merging. BDR-065 had already REJECTED gitignore for docs/superpowers on the git-travel ground; the real gap was the DELETE side never being coded (doctrine-only manual chore, slipped once — 655e364). Built `_gitflow_purge_transient`.
+- **future application**: "don't merge transient X" → ask: does the run read X from disk? does X travel via git (worktree, foreign checkout)? Yes → auto-purge at finish, not gitignore. Scoped commit `-- <paths>` avoids sweeping a dirty index; `git diff --quiet HEAD -- paths` precheck makes `git rm` all-or-nothing safe; keep the purge best-effort so cleanup NEVER blocks a merge. Prove archive-reachability with `git log --full-history` / `git show <sha>:path` — plain `git log -- path` prunes the purged add-commit via history simplification (bit me writing T17).
+- **link**: [[BDR-065]].
+
+## LRN-139 — model-trait compensations invert across generations; state WHEN-guidance, not direction (2026-07-30)
+- **pattern**: config rules that COMPENSATE a model trait become counter-productive when the next generation inverts the trait. LRN-030 (Opus 4.8 under-delegates → "Default to delegation… counters under-delegation") inverted by Opus 5 (delegates MORE readily, official guide) — the rule pushed the failure the model now has. Same class: explicit verify instructions → over-verification; conservative-reporting clauses → literal recall suppression; MUST/CRITICAL → over-triggering.
+- **Opus 5 traps found**: (a) Claude Code injects Opus-5-only anti-delegation prompt sections (heron_brook + subagent_steer_delegation, issue #80988; server-gated, no opt-out, absent from transcripts) — own prose stacks on top blindly; (b) NO model-default effort hold on Opus 5 — persisted effortLevel (xhigh, settings.json) silently carries over, against "start high, sweep low/medium"; run /effort sweep per model; (c) effort does NOT shorten visible output/deliverables — only prose length rules do (+30-40% docs).
+- **future application**: at every model-generation bump, grep config for trait-compensating language ("counters model tendency…", "default to X") and re-verify the premise; prefer WHEN-guidance (conditions where X pays) over directional nudges — survives inversions unchanged.
+- **link**: [[LRN-030]] [[BDR-081]].
+
+## LRN-140 — de-prescription findings: dedup evaporates, self-verify is default, recall survives (2026-08-02)
+- **pattern 1 — inventory dedup counts lie**: line-level inspection killed most "duplicate" pairs (seo 9 families→2 real merges; geo 7→0). Twins differ by AUDIENCE (bundle-item payload read by fresh applier vs spec rule) or MODE-RANGE (collect/judge/template/RULES) or are distinct obligations sharing a keyword (30/70 ×3 = three different rules). Dedup rule that survives: verbatim + same-audience + same-range ONLY.
+- **pattern 2 — Opus 5 self-verifies unprompted**: "run it twice" instruction REMOVED → after-judge still ran score engine twice, identical output. Removing verify-prose does not remove the behavior; its value = no compounding, no contradiction burn. Confirms BDR-081 E3 mechanism, refines the payoff claim.
+- **pattern 3 — de-prescription does NOT depress recall**: reworded collect caught &nbsp;-encoded phone AT COLLECT (baseline collect missed it); reworded judge found new RGPD finding + self-caught false positive + corrected collect coverage claim 21/21→20/21. Integrity/honesty invariants (kept class B) carry the discipline, not the caps.
+- **pattern 4 — lock strings, never shapes**: LLM-convention output layers (banners, fences, table columns, section order) wobble run-to-run in BOTH directions — baseline itself deviated from spec where after conformed (§0 ENTRIES, BUNDLE-before-SCORING). Stable contract = census-locked literal strings; anything unlocked drifts and MUST be tolerated by consumers (tier recognition "by intent" is the right pattern).
+- **link**: [[BDR-082]] [[BDR-081]] [[LRN-139]] [[LRN-113]].
+
+## LRN-141 — adopting an external skill: take the invariants, refuse the machinery (2026-08-24)
+Context: unlazy import ([[BDR-083]]). Pattern: an external skill's MACHINERY encodes ITS threat model and ITS doctrine; only its INVARIANTS transfer. Two clean cases from one repo. (1) Approval store binding PATH/shell/platform exists because unlazy executes ledgers INHERITED from untrusted repos — importing it into a config that authors its own ledgers buys per-command approval prompts and closes zero threat. (2) Stop hook returning `decision:"block"` exists because unlazy has no human gate — importing it into a config whose spine is "STOP + escalate to human" would make the tooling fight the doctrine. Meanwhile the invariants (exit 0 AND marker; evidence persisted so the next reader gets fact not report; impossible ≠ deletable) cost ~250 l of our own bash and fit the EXISTING contract with no new tree.
+Separating test: ask WHAT THREAT / WHAT DOCTRINE does this piece assume. Answer "theirs" → refuse the piece, keep the invariant it was protecting.
+Corollary on claims: unlazy's own research/validation-protocol.md RETRACTS its v1 benchmark numbers as unreproducible while the repo DESCRIPTION still advertises them. Read a project's self-criticism before its README — the retraction is the credibility signal, the headline is not.
+Future application: any skill/plugin adoption — skills-external/, /plugin-check, install-plugins.sh.
+
+## LRN-142 — structure locks are fixed-string: reflowing a doctrine paragraph reds them (2026-08-24)
+Context: contract-gates ([[BDR-083]]). Editing lib/verify-secure-loop.md rewrapped 5 locked phrases across line breaks ("Max 3 conformity iterations", "Max 3 security iterations", "re-verify the REQUEST first", "always re-checked BEFORE security", "one verifier dispatch + one security dispatch") → loops-light.test.sh 30 pass / 5 fail, though ZERO doctrine was dropped. Locks did their job: they cannot distinguish "clause deleted" from "clause rewrapped", and that conservative bias is correct — the alternative (fuzzy matching) would miss real deletions.
+Rule: when editing a doctrine file under structure locks, grep the test's lock strings FIRST, then re-flow AROUND them — each locked phrase stays on one unbroken line. Fix the DOC, not the lock, unless the doctrine genuinely changed. Under locks today: verify-secure-loop.md, contract-interview.md, verifier / security-auditor / plan-challenger agents, seo+geo (71 locks).
+
+## LRN-143 — pipe to head masks grep exit; `|| fallback` never fires
+- **Context**: darwin 2026-08-26 — plugin-probe FRAMEWORK-DEPS (`grep … | head || echo none`) emitted silent-empty on no-match; same bug in run's own probe test.
+- **Pattern**: pipeline rc = LAST command's (head = 0 always). `|| fallback` after pipe = dead code. Bounded output → drop head; else `set -o pipefail` or capture + test.
+- **Future**: any skill/agent bash probe with a `||` fallback: check what the pipeline rc actually is first.
+
+## LRN-144 — census locks grep EXACT single-line phrases; prose rewrap breaks them
+- **Context**: darwin 2026-08-26 — hotfix RULES rewrap split "No verifier is dispatched at hotfix weight"; loops-light.test.sh lock RED; make test caught post-edit.
+- **Pattern**: lib/tests/*.test.sh lock sentences verbatim, single-line. Rewording/rewrapping skill+agent md near locked phrases silently breaks census.
+- **Future**: before editing skill/agent prose, grep lib/tests/ for locks in the touched region; run make test BEFORE dispatching judges, not after.
+
+## LRN-145 — hooks reach the terminal only via terminalSequence JSON field
+- **Context**: 2026-09-01 — attention bell for VS Code Remote-SSH (CLI on remote Linux). Hook subprocess has no controlling TTY; /dev/tty unreliable. Docs: terminalSequence = supported side-effect field, fires even on events that discard output.
+- **Pattern**: Notification hook → stdout JSON `{suppressOutput:true, terminalSequence:"<BELx2><OSC 777 notify><ST>"}`. VS Code terminal ignores OSC 777/9 natively (claude-code #28338); client-side ext wenbopan.vscode-terminal-osc-notifier converts to native toast over Remote-SSH; beep needs accessibility.signals.terminalBell sound:on. permission_prompt fires ~6s late, idle_prompt ~60s.
+- **Future**: any hook ringing/notifying the terminal (bell, toast, title) — terminalSequence, never /dev/tty. Input-needed matcher set: permission_prompt|idle_prompt|agent_needs_input|elicitation_dialog|elicitation_url_dialog.
+
+## LRN-146 — Notification event alone misses end-of-turn; Stop is the missing event
+- **Context**: 2026-09-03 — attention signal verified end-to-end after [[BLK-020]]. Matcher `permission_prompt|idle_prompt|agent_needs_input|elicitation_*` covers input-needed cases ONLY. "Claude finished speaking" has no notification_type — nearest was `idle_prompt`, ~60s late. Gap invisible until explicitly enumerated by user.
+- **Pattern**: wire SAME hook script on TWO events — `Notification` (matcher = input-needed set) + `Stop` (fires once per turn end, supports terminalSequence, no matcher). Script branches on `.hook_event_name` when `.message`/`.notification_type` absent: Stop → "Claude has finished responding", else default. Read stdin ONCE into var, jq the var (stdin not re-readable).
+- **Verified**: turn-end bip+toast OK, AskUserQuestion selector bip+toast OK. `permission_prompt` NOT exercisable under `defaultMode: auto` — ask-rules (`python3 -c *`, `curl`…) auto-approved, no prompt raised. Hooks hot-reloaded by file watcher, no restart.
+- **Future**: enumerate the events a signal must cover BEFORE wiring, one per user-visible moment. Notification ≠ lifecycle-complete. SubagentStop exists too for agent completion.
+
+## LRN-147 — VS Code restores terminals BEFORE ext activation → toast dies every restart
+- **Context**: 2026-09-03, second hit same day. Bell OK, toast gone, after user re-attached session from a restored terminal. Probe on that pty: OSC 777 unique + OSC 777 repeated + OSC 9 → all three silent, while BEL rang. Same pty, bell works ⇒ bytes arrive, ext just not hooked to that terminal.
+- **Pattern**: `wenbopan.vscode-terminal-osc-notifier` instruments a terminal only if it exists AFTER ext activation. `terminal.integrated.enablePersistentSessions` (default true) restores terminals at window startup, i.e. BEFORE lazy ext activation → every restored terminal is permanently deaf to OSC. Recurs at each VS Code restart, silently, bell still ringing so it reads as "half broken".
+- **Fix**: client setting `"terminal.integrated.enablePersistentSessions": false` → no terminal pre-exists activation. Fallback without it: after VS Code start, open a FRESH terminal then `dtach -a ~/.dtach/<session>` (dtach broadcasts, old client can stay or be closed, session never lost).
+- **Diagnostic shortcut**: bell rings + toast dead on the SAME pty = terminal-instrumentation fault, not audio, not hook, not server. Bell dead + toast alive = audio fault ([[BLK-020]] fault B). The two channels split the search space; check which one survives before anything else.
+- **Future**: any client-side terminal-parsing ext over Remote-SSH inherits this. Verify instrumentation on the ACTUAL attached pty after every restart, never assume yesterday's terminal.
+
+## LRN-148 — terminal instrumentation is per-terminal + unpredictable; pre-flight test before attaching
+- **Refines**: [[LRN-147]] blamed restored-terminals-born-before-activation. Too narrow — counter-example same day: two terminals SAME VS Code window, pts/3 (born 01:58:33) instrumented, pts/7 (born 01:59:29, LATER) deaf. Ext is GLOBAL (marketplace: Enable/Disable pause parsing extension-wide, no per-terminal setting), shells identical on every server-side measurable: `VSCODE_INJECTION=1`, TERM, TERM_PROGRAM, same `--init-file` shell-integration path, ~2-3s between shell start and dtach. Trigger NOT identified.
+- **Pattern**: treat instrumentation as a per-terminal property that can silently fail for unknown reasons. Cheap pre-flight before committing a long-lived session to a terminal: `printf '\a\a\033]777;notify;NEUF;test\033\\'` typed IN that terminal. Toast → instrumented, attach. Bell only → deaf terminal, open another. Costs 5s, replaces an hour of pty archaeology.
+- **Recovery**: deaf terminal never repairs. Open fresh terminal, pre-flight it, `dtach -a ~/.dtach/<session>`. dtach broadcasts, so old client may stay attached; session never at risk.
+- **Diagnostic split (holds)**: bell alive + toast dead = terminal instrumentation. Toast alive + bell dead = client audio ([[BLK-020]]). Neither = bytes never arrive.
+- **Future**: do NOT assert the born-before-activation cause as established — it fits the first incident, not the second. Unknown trigger is the honest state.
+
+## LRN-149 — Stop hook payload carries background_tasks; use it to skip premature signals
+- **Context**: 2026-09-03. User: "notif à la création d'un sous-agent alors qu'il faudrait pas". Instrumented hook, ran probe subagents: NEITHER subagent creation NOR completion calls the hook. Only event = `Stop`, fired when the turn ends right after spawning. Signal was real but LIED ("Finished responding" while work continued).
+- **Pattern**: dump the real payload (`printf '%s' "$payload" >> file.jsonl`) instead of trusting docs — docs list Stop fields without `background_tasks`, the wire has it: `[{"id","type":"subagent","status":"running","description","agent_type"}]`. Rule: on Stop, `(.background_tasks // []) | length` > 0 → exit 0 silent. Next turn end signals for real. Interaction events (permission/question) always signal, background or not.
+- **Fail-open**: field absent (older client) → still signal. Missed notification worse than extra one.
+- **Cross-session gotcha**: hook is user-scope, so EVERY session runs it. A single-file dump (`> file`) gets overwritten by another project's session — append JSONL and filter on `.cwd`. That accident proved `permission_prompt` fires with `message="Claude needs your permission"` (unexercisable in this session under `defaultMode: auto`).
+- **Future**: any hook needing turn-completion semantics must check background_tasks; "turn ended" ≠ "work done". Verified live: Stop with 0 tasks signals, Stop with 1 running subagent silent.
+
+## LRN-150 — a lockfile-pinned dep vs a fast runtime: the undeclared incompatibility HANGS, it does not error
+- **Context**: 2026-09-13. gstack's lockfile-frozen Playwright 1.58.2 (Feb 2026) under Node 26.5.0 (Sept 2026). Chromium extraction deadlocks at 39/333 files, silently, forever. `engines: node >=18` claims support.
+- **Pattern**: `engines` is a CLAIM, not a test — an UPPER bound is almost never declared, so "too new" reads as "supported" and fails as a HANG, not an error. Diagnose with `sample <pid>` (macOS) or any stack dump: ALL threads idle (`kevent` + `__psynch_cvwait`, 0% CPU, libuv workers INCLUDED) = deadlock, nothing in flight; a thread parked in `write`/`read` would mean AV/FS/network instead — that one measurement ruled out Intego VirusBarrier in seconds. Then discriminate by moving ONE variable: same command + same revision under another runtime (`brew` keeps node@22 beside node@26).
+- **Read the declared range before calling it a pin**: `package.json` said `^1.58.2`, so 1.63.0 was already in range — only `bun.lock` froze it. A "bump" that needs no fork and breaks no contract was available the whole time.
+- **Corollary**: a fix that WORKS can freeze a WRONG cause in the registry. [[BLK-008]] blamed a fallback build; that record misdirected this investigation three months later. When a fix lands, record which variable was PROVEN, not the one suspected.
+- **Future**: pinned dep + hang → compare dep publish date vs runtime release date BEFORE blaming platform/network/AV. Any unattended install step that can hang needs a DEADLINE: silent-forever is strictly worse than failing loudly ([[BDR-088]]).
+
+## LRN-151 — porting to macOS: the danger is fail-OPEN, and a scan that finds nothing proves nothing
+- **Context**: 2026-09-13. Repo moved Linux → macOS. `/bin/bash` = 3.2.57 = what `#!/usr/bin/env bash` resolves to. Six distinct defect classes ([[BLK-022]]).
+- **Pattern — the failure direction is what matters**: bash 3.2 does not abort on a bash-4 construct, it makes the SUBSHELL fail, and a guard whose "block" path is an exit code then reads as "allow". `${1,,}` turned an SSRF allowlist into a pass-through; `mapfile` turned scope guards into empty-array no-ops that still reported success; missing `timeout` turned every gate criterion into NOT-MET. Audit order: find the guards FIRST, ask what an errored subshell returns there, and only then chase cosmetics.
+- **Empirically catalogued surface** (bash 3.2 + BSD userland): `${var,,}`/`${var^^}`, `mapfile`/`readarray`, `declare -A`, `timeout` (coreutils), `sed -i` (needs a suffix; no `\n` in the replacement), `touch -d`, `stat -c`, `wc -l` (pads with spaces — breaks string compares), `/bin/grep` (macOS has only /usr/bin/grep), `readlink -f` (OK since Monterey), `sort -V` (OK).
+- **The test suite is the oracle**: the repo's own `make test` located every one of these faster than reading code, because each defect surfaced as a specific assertion. Port = run the suite, fix what reddens, re-run.
+- **Self-check the detector**: my grep sweep returned EMPTY twice and I nearly read it as "clean" — once because `set -e` killed the loop on the first no-match grep, once because the pattern demanded a letter after `${` and so missed `${1,,}` (a digit). A scan that finds NOTHING must first be shown to find something known-present. Both misses were caught by accident, not by method.
+- **Future**: after any OS migration, run the full suite before trusting any static sweep, and treat a 100%-of-a-category warning as a stale check rather than 100% non-compliance ([[BDR-019]] sweep, `doctor.sh` + `Makefile`).

.claude/tasks/TODO.md

@@ -1,5 +1,394 @@
 # TODO
 
+## 2026-08-25 — darwin fresh baseline: 32 skill-systems + 23 agents (feature/darwin-optimize-20260825)
+User: `/darwin-skill all skills and agents` (background). Fresh-from-zero
+(results.tsv wiped 2026-06-23, journal 2026-06-30). Scope per BDR-015/043 +
+LRN-070: personal skills only, external/gstack OUT. EVAL-004 applied: eval
+unit = skill+dispatched-agents SYSTEM, agents get own rows. LRN-018: judges
+emit per-dim scores, totals recomputed main-thread. v2.1 keep/revert =
+paired same-judge majority, absolute scores triage-only.
+- [x] T1 Phase 0+0.5: gitflow branch, results.tsv header, 7 new
+      test-prompts.json (capitalize deploy gitflow pdf-translate reconcile
+      release-candidate tour), runtime scan (2 minor hits). find-docs
+      EXCLUDED — machine-owned ctx7 (BDR-053, gitignored) → 31 systems.
+- [x] T2 Phase 0.5 gate PASSED: reuse prompts as-is; dim8 full_test on
+      candidates only (baseline dry_run); Phase 2 set = ALL units <80.
+- [x] T3 Phase 1 baseline DONE: 7 blind judges, 54 rows (31 skills + 23
+      agents), mean 83.4, 13 units <80, ~25 verified findings (hotfix
+      destructive restore, onboard/onboarder contract, init-project
+      allowed-tools, skills-perso 8/32 detection...).
+
+- [x] T4 Phase 1 gate PASSED: user picked the set — proven by Phase 2
+      running 13/13 units, 0 reverts (DARWIN-2026-08-26.md:23).
+      Ticked by reconcile 2026-09-01.
+- [x] T5 Phase 2 DONE: 13/13 units, 12 rounds kept 3-0, 0 reverts +
+      bug pass 8 commits kept 3-0 (2 skeptic residuals amended). make test
+      green.
+- [x] T6 Phase 3 DONE: report .claude/audits/DARWIN-2026-08-26.md + card
+      PNG (playwright fallback). Capitalize pending user approval. Branch
+      UNMERGED — human gate.
+      → both residuals stale: capitalized a15854a, merged 726464f
+        (reconcile 2026-09-01).
+
+## 2026-08-25 — user permanent rules: writing + web build + web security (feature/user-writing-web-rules)
+User supplied 4-block rule text (écris / site / code / vérification); asked:
+coverage check, conflict check, integrate. Verdict: security CORE already in
+CLAUDE.global.md §Security (parameterized queries, env-var secrets,
+AuthN/AuthZ, fail closed) — NOT duplicated. NEW: writing-style block, design
+anti-default list, site done-checklist, web-app specifics (RLS, service key,
+IDOR, cookie flags, rate limit, field minimization). Placement: global at
+308/320 budget → rules/ instead.
+- [x] R1 rules/writing-style.md — always-on (no paths:), scope carve-outs
+      (registries caveman, code comments, skill templates) + self-check
+- [x] R2 rules/web-building.md — paths: web globs; anti-defaults + done
+      checklist (report missing, never invent) + skill pointers
+- [x] R3 rules/web-security.md — paths: code globs; web-app specifics
+      extending §Security, zero dup of the core
+- [x] R4 CLAUDE.md (project) — amend always-on doctrine line (320-budget
+      exception → rules/), feeds C2 audit
+- [x] R5 capitalize BDR-085 + journal + CHANGELOG
+- [x] merge → develop 5ec7bfa — human gate passed (reconcile 2026-08-25)
+
+## 2026-07-30 — adapt config for Claude 5 family / Opus 5 (feature/opus5-config-tuning)
+User: Opus 5 "needs more freedom" → research (official migration guide +
+web + registres) confirms: over-delegates (inverts LRN-030 Opus 4.8 trait),
+over-verifies if told to verify, literal instruction following, scope
+expansion named regression, harness already injects anti-delegation on
+Opus 5 (#80988). Plan: .claude/tasks/plans/2026-07-30-opus5-config-tuning-1238.md
+— to be challenged by 3 blind plan-challengers (opus pins → Opus 5), then
+executed on feature branch. NO merge (human gate).
+Challenged 2026-07-30: correctness CONCERNS(4) · robustness FATAL(5, 1
+BLOCKER: symlink-live deployment) · simplicity CONCERNS(4) — all fixes
+adopted as prescribed (plan §5bis, v2 items below).
+- [x] W0 branch first (eab2a10 parent); hook regex validated on scratch copy
+      (bash -n + shellcheck + 5 replays, HOME sandboxed) before live write
+- [x] W1 delegation block v2 (when-guidance + gates carve-out + scoped don't-redo) — 0f7b565
+- [x] W2 "staff engineer" bar line deleted — 0f7b565
+- [x] W3 finish-whole-task folded into Deviations (+ gone-WRONG→STOP) — 0f7b565
+- [x] W4 deliverable-length rule — 0f7b565
+- [x] W5 line budget: 308/320
+- [x] W6 hook \bux\b dropped, \bui\b kept + F10 must-fire lock, D11 quiet row
+      flip-tested (fire before/quiet after) — eab2a10, suite 22/0
+- [x] W7 plan-challenger :82-83 reworded → [MINOR] routing, census row — c3d3f4d, 44/0
+- [x] W8 BDR-081 + LRN-139 + journal + CHANGELOG
+- [x] W9 final gate: make test full suite — green except known T6c
+      (darwin-skill residual → chantier 4 below), 2026-07-30
+- [x] W10 merged on explicit user signal — 709cf9b (2026-07-30 13:28),
+      branch deleted; confirmed post-merge this session
+
+## 2026-07-30 — Claude 5 follow-on chantiers (user directive, checkpoint between each)
+Order fixed, one branch per chantier, no merge without per-chantier signal.
+- [x] C1 dé-prescription seo-analyzer.md + geo-analyzer.md — DONE 2026-08-02.
+      Census-first 71 locks flip-proven (9681b46) → rewords under
+      audience×range invariant (adafa35 seo, c7646a9 geo) → controlled
+      before/after dogfood: judge-replay on frozen signals + templates +
+      fresh collects + e2e judge + blind reader = 42/42 both sets, zero
+      contract regression, recall improved. Plan challenged 4 passes
+      (FATAL/FATAL/CONCERNS + confirmation FATAL(9), all closed by name).
+      BDR-082 + LRN-140. Evidence .audit/dogfood-baseline/ (19 artifacts).
+      Branch feature/seo-geo-deprescription UNMERGED — human gate.
+      → merged 5488c48, branch deleted (reconcile 2026-08-25).
+      Residual for gate: §6bis dynamically-unverified list (FULL branches,
+      apply path — census-locked statically); FULL/aggressive dry-run = user
+      option; nested-CLI dogfood blocked by monthly spend limit (inline used).
+- [ ] C2 self-contradiction audit CLAUDE.global.md + own skills: list rule
+      pairs in tension, propose resolution per pair, apply after user OK.
+      /doctor as assistant, not authority.
+- [ ] C3 superpowers: MEASURE first (skill-invocation log over sessions)
+      whether "1% chance → MUST invoke" over-triggers; if yes, options +
+      trade-offs (disable plugin / softer house rule / live with) — user decides.
+- [x] C4 hygiene: reinstall darwin-skill — DONE (reconcile 2026-08-25:
+      ~/.agents/skills/darwin-skill present, T6c green, make test exit 0).
+
+## 2026-07-22 — auto-purge transient superpowers artifacts at finish (feature/gitflow-auto-purge-transient)
+User: transient planning artifacts (`docs/superpowers/{specs,plans}`) leak into
+develop; BDR-065 "post-merge cleanup" is DOCTRINE ONLY (no code) — manual chore,
+already missed once (655e364). Decision (user 2026-07-22, 2 recommended picks):
+keep committed-during-run (SDD worktree + reviewers read them), AUTOMATE the
+delete at `gitflow finish`. NO gitignore (would break superpowers' `git add` of
+the spec → no travel to SDD worktree). `.claude/tasks/{contracts,plans}` stay
+versioned (durable, referenced by decisions.md e.g. BDR-076). Universal via the
+`~/.claude/lib` → repo `lib` symlink: every project's finish gets it.
+- [x] lib/gitflow.sh: `_gitflow_purge_transient` (clean-precheck → git rm →
+      scoped commit `-- paths`; best-effort, NEVER aborts finish; opt-out
+      `GITFLOW_PURGE_TRANSIENT=0`) wired into finish `feature|bugfix` pre-merge;
+      `purge-transient` CLI verb.
+- [x] lib/gitflow-test.sh T17 a/b/c/d (purge+recover-from-history via
+      --full-history+`git show`, no-op when absent, opt-out keeps, chore scope).
+      Also fixed 2 pre-existing SC2034 warnings (T16 gl_out/noleaks_out).
+- [x] Gate: shellcheck lib/*.sh CLEAN + `make test` exit 0 (gitflow 106/0, full
+      suite green). Universal via ~/.claude/lib → repo lib symlink (verified).
+- [x] CLAUDE.md §Transient planning artifacts: → "AUTO-PURGED by gitflow finish".
+- [x] Capitalize: BDR-065 Amendment (2026-07-22) in body + LRN-138 present
+      (reconcile 2026-08-25).
+
+## 2026-07-20 — pending merge gates (reconcile)
+- [x] merge feature/profile-managed-externals → develop (BDR-079 profile
+      symmetry + /doc clean pass: README/USAGE/ARCHITECTURE.md) — 37c79f0
+- [x] merge chore/purge-transient-docs → develop (docs/ transient purge
+      655e364 + reconcile e75ea79) — reaches main at next release
+- [ ] Makefile help text: profile-list help lists 5/10 profiles (:57) —
+      1-line hotfix. (test glob :31 FIXED — has run-*.sh, reconcile 2026-08-25)
+      Re-verified OPEN 2026-09-01: lib/profiles/ has 10, Makefile:57 lists 5
+      (backend, full, seo, web-full, web missing).
+
+## 2026-07-20 — profile ↔ toggle-external symmetry (feature/profile-managed-externals, BDR-079)
+Audit verdict: gstack on-demand + design enable already work; DISABLE side
+missing — `set backend` leaves emil/frontend-design/design-motion/impeccable
+active + magic registered. Doc claims auto-toggle both ways (only enable true).
+- [x] profile.sh: `MANAGED_EXTERNALS` (emil-design-eng, frontend-design,
+      design-motion-principles, impeccable — union of profile usage) +
+      `MANAGED_MCPS` (magic) allowlists; cmd_set refactored to 4 trim
+      helpers (disable_{gstack,plugins,externals,mcps}_not_in).
+- [x] profile.sh enable_skill external: from-source fallback
+      (`ln -sf skills-external/<name>`) mirroring toggle-external.
+- [x] Texts: cmd_set info line, usage() NOTE (stale "NOT toggled
+      automatically"), header; skills/profile/SKILL.md Mechanism+tradeoffs.
+- [x] Hermetic test lib/tests/profile-set-managed.test.sh — 16/0: gstack
+      on-demand, external from-source, park/restore round-trip, magic
+      add/remove via claude shim, non-managed untouched.
+- [x] Gate: shellcheck OK + make test exit 0 (review-guards 5/0). BDR-079 +
+      journal + CHANGELOG done. Merged 37c79f0 (2026-07-20).
+
+## 2026-07-20 — ctx7 coverage extension (feature/ctx7-coverage, BDR-078)
+Close the 4 gaps from the ctx7 coverage audit: /feat //bugfix + ad-hoc coding
+never consult ctx7; fast-libs list hardcoded 3×; zero deterministic backstop.
+- [x] (d) `lib/fast-libs.sh` — single source of truth: `detect` +
+      `cache-status` verbs; JS (package.json exact/scoped keys) + Python;
+      7-day cache freshness. LC_ALL=C sort (locale-independent order).
+- [x] (c) `hooks/ctx7-reminder.sh` — UserPromptSubmit, once-per-session
+      sentinel, fires only when fast-libs detected; settings.json
+      registration (2nd ctx7 surface, deliberate refinement of BDR-053).
+- [x] (a) find-docs description — before-writing-code trigger (fast-moving
+      libs, even without a doc question) + cache-first rule in body.
+- [x] (b) feater.md + bugfixer.md — fast-lib docs rule (read fresh cache,
+      else ctx7 fetch max 2 topics, else NOTES cache miss + proceed).
+- [x] consumers → lib: ship-feature STEP 0c, init-project STEP 5c, onboard
+      STEP 3.5 detection blocks point at fast-libs.sh.
+- [x] `lib/tests/fast-libs.test.sh` (lib verbs + hook fire/sentinel/quiet)
+      — 11/0, auto-discovered by the make test glob.
+- [x] Gate: shellcheck + make test green (review-guards 5/0). BDR-078 +
+      journal + CHANGELOG done. Merged 8ee7d19, shipped v1.2.0.
+
+## 2026-07-19 — Opus-pin dispatched judgment agents (branch feature/opus-pin-audit-agents)
+
+Goal: session model (Fable) = orchestration + inline reflection ONLY.
+Every DISPATCHED subagent pinned. Reverses BDR-066 "opus pins rejected"
+carve-out (context changed: session now Fable → inherit burns Fable quota
+on audits). User approved: opus for judgment agents, drop local opus pin.
+
+- [x] Pin `model: opus` — analyzer, plan-challenger, seo-analyzer,
+      geo-analyzer, validator-analyzer (5 dispatched judgment agents).
+      NOT interviewer / client-handover-writer (inline-load only → pin
+      inert; they ARE the main loop = Fable by design).
+- [x] `lib/challenge-plan.md` — rewrite MODEL note (was "do NOT pin").
+- [x] `agents/plan-challenger.md` — rewrite ORCHESTRATOR PROTOCOL model note.
+- [x] `skills/onboard/SKILL.md` — add `model="opus"` to the 6
+      general-purpose audit dispatches + table/description text.
+- [x] `skills/tour/SKILL.md` Phase B — text: analyzer opus-pinned /
+      general-purpose with model="opus".
+- [x] `skills/client-handover/SKILL.md` — text: pipeline inline on
+      SESSION model (writer inline-loaded, not dispatched).
+- [x] `lib/tests/model-routing.test.sh` — flip §F5 fm_lacks → has
+      'model: opus' (5 agents), keep fm_lacks on interviewer +
+      client-handover-writer, update comments (BDR-076).
+- [x] `.claude/settings.local.json` — drop `"model": "opus-4-8[1m]"`
+      (local, gitignored; Fable default from settings.json applies).
+- [x] Tests: model-routing + loops-light + shellcheck + make test.
+- [x] Memory: BDR-076 append + journal line. Commit (feat + chore);
+      merged 17fbe51, shipped v1.2.0 (reconcile 2026-07-20).
+
+## 2026-07-17 — STATUS seo/geo parity (branch bugfix/seo-geo-integrity — MERGED to develop, 92301fe; "UNMERGED" note was stale, corrected 2026-07-19 W0)
+PHASE 1 — integrity: **DONE 7/7**. I3 8b0c98c · I1 57c67f2 · I2 4ea2fb8 ·
+I5 64f175f · I4 e70e1d6 · I6 9da1dec · I8 acd452b. Plus 9cd7b51 (A1+A2, two
+process anomalies surfaced by dogfooding /harden at zenquality.fr from the
+wrong CWD).
+PHASE 2 — free wins: W3 fe93b79 · W1 a6d423b · **W2 DEFERRED** (see below).
+H1 DONE (url-guard 7d6aa09) · C1 DONE (sitemap verb, C1a/b/c). Branch MERGED
+to develop (92301fe), shipped in v1.2.0 (reconcile 2026-07-20).
+
+### Plan corrections made while executing (the plan was wrong 4×)
+- **B3 KILLED** — GSC Links API does not exist. Verified against the API
+  reference: Search Console v1 exposes exactly Search Analytics, Sitemaps,
+  Sites, URL Inspection. A subagent hallucinated it; I doubted it in the
+  plan and the doubt was right. (Its follow-on — "so Common Crawl is the
+  only free source, and the 70/100 cap is mandatory" — was ALSO wrong: see
+  B1/B2 KILLED below. Common Crawl is a 17 GB dead end, and Bing's
+  GetUrlLinks is the only viable free source, first-party only.)
+- **I1 was an over-correction** — "Off-page has ZERO data" was overstated
+  (relayed from a subagent, unverified). Brand mentions ARE gathered
+  (STEP 6). Narrowed the axis definition instead of N/A-ing it; weights
+  untouched to avoid churning historical scores twice.
+- **I6 framing was wrong** — I claimed 3× that the stats "drive axis
+  weights". They do not; weight tables carry no citations. They drive Tier
+  recommendations and, worse, land in CLIENT reports via the "Cite sources"
+  rule. Reality was worse than my false version.
+- **W1 was the wrong shape** — plan said "richresults verb"; a new verb
+  means a 2nd POST to the same endpoint for a payload already received.
+  Extended inspect() instead.
+- **H1 moved up** (was AXE 5) — it is a PREREQUISITE of C1, not a
+  follow-up. Today only $DOMAIN (user-typed) is interpolated. After C1, N
+  URLs from a REMOTE sitemap flow into shell commands and fetch targets.
+
+### B1/B2 (Common Crawl backlinks) — KILLED 2026-07-17, measured not assumed
+The plan said Common Crawl was the free backlink source and the 70/100 cap
+was therefore mandatory. Both premises are dead:
+- domain-edges.txt.gz = **17.3 GB gzipped** (+879 MB vertices, +2.3 GB
+  ranks), measured live via HEAD. Finding one domain's inbound links means
+  scanning all of it, per audit. Non-viable, and abusive toward a nonprofit.
+- The implementation everyone cites (claude-seo commoncrawl_graph.py:169)
+  caps at `500 MiB` = **2.9% of the edges file**, and reports what that
+  arbitrary slice held as a backlink profile. A random sample presented as a
+  measurement — the exact failure class this branch exists to remove. We
+  nearly copied it.
+- B2 dies with B1: nothing to cap.
+CONSEQUENCE: I1's narrowed Off-page axis (brand mentions only, backlinks +
+authority declared unauditable in §14) is the FINAL state, not a placeholder.
+Its §14 line was corrected — it used to point at Common Crawl as "nearest
+free source", which is a 17 GB dead end.
+RAISES W2's VALUE: Bing's GetUrlLinks is now the ONLY free viable backlink
+source. First-party only (never a competitor), still blocked on the client's
+Bing account.
+
+### W2 (Bing) — DEFERRED, blocked on a real-world test
+Killed after 4 challenge rounds. User's model: client sites live on CLIENT
+Bing accounts, so a per-user API key means one key per client account.
+OAuth is the right model but is a swamp:
+- Redirect URI rejects ALL local forms (http/https/127.0.0.1 — user tested)
+- Refresh tokens are **rotated + single-use**, self-described non-compliant
+  with OAuth 2.0 → store rewrite on every call, AND our parallel
+  seo/geo dispatch would race the rotation → invalid_grant, dead token
+- Undocumented "anti-forgery token" failure on refresh, unanswered on Q&A
+- MS's own advisor recommends falling back to the API key
+- Doc contradicts itself on grant_type and the token endpoint; no library
+REVIVAL CONDITION: a client already on Bing adds the user as a Read-Only
+user → test in ~10 min whether the single API key sees DELEGATED sites
+(undocumented, nobody knows). If yes → W2 is cheap and clean (one key,
+client-owned verification, revocable, read-only, zero OAuth). If no → dead.
+Value forgone meanwhile: Bing/DDG/Ecosia query stats + index status +
+first-party backlinks. Real but modest; C1 dwarfs it.
+
+## 2026-07-16 — PLAN seo/geo parity vs claude-seo (superseded by the STATUS above)
+Source: audit of github.com/AgriciDaniel/claude-seo (11.5k★, MIT, v2.2.0,
+5 mo old, 185/197 commits single author). Verdict: cherry-pick, never install
+(install.sh:49 overwrites our skills/seo/; uninstall.sh:45 glob `seo-*.md`
+deletes our seo-analyzer.md 42K it never installed; extensions/*/install.sh:42
+wipes settings.json on parse error; skills/seo/SKILL.md:119 injects Skool
+upsell footer into deliverables). Their code is real (render_page.py 428 l
+Playwright, url_safety.py 622 l SSRF, 326 tests, 320 pass) — adapt to our
+fetch.sh contract, do NOT copy wholesale (no fail-open, no tokenstore, no
+JSON shape).
+
+Framing: their plus-values map onto OUR integrity gaps — report claims more
+than it measured. Same bar we held their README to.
+Seam: `lib/seo-data/fetch.sh` verbs (accounts|crux|queries|inspect|forget)
++ fail-open `{"status":"degraded"}` + fixtures + tests. Everything below lands
+as NEW VERBS. No new architecture.
+
+### AXE 0 — Integrity (no new deps, hours) — the score currently lies
+- [x] I1 Off-page axis scores 10-15% of FULL with ZERO data source (no API,
+      no index) → today fabricated, and it feeds /client-handover. Immediate
+      fix: extend existing LOCAL `N/A — requires FULL audit` pattern to FULL,
+      redistribute weights. Data upgrade later (AXE 3). Honesty now, data after.
+- [x] I2 VSI (Visual Stability Index) listed in CWV thresholds but NO path
+      retrieves it — neither CrUX nor PSI expose it. Phantom signal → remove
+      or source.
+- [x] I3 **SAFETY** /geo standalone: geo/SKILL.md (125 l) has no STEP 0, no
+      confirmed-NAP collection — but geo-analyzer OWNS JSON-LD NAP. Standalone
+      /geo on a local business can write unverified NAP with zero LRN-032
+      protection. Real bug, not cosmetic.
+- [x] I4 Security headers counted 3× (seo-analyzer STEP 4 scores them in
+      Technical axis; depth-matrix.md says drop unless indexability; /harden
+      re-audits /100 with 3 validators). Contradiction between dedup rule and
+      agent spec → pick one owner.
+- [x] I5 Report says "audit", measured 5-15 sampled pages. State coverage %
+      explicitly in §0 until AXE 2 lands.
+
+### AXE 1 — Free wins on auth we ALREADY have (fetch.sh verbs)
+- [x] W1 `richresults` verb — GSC URL Inspection already returns
+      `richResultsResult`; our OAuth already carries the scope. Programmatic
+      rich-results validation on real Google data. **BEATS claude-seo**: their
+      README:314 "dual validator (Rich Results Test + Markup Validator)" is
+      FALSE — grep of all .py = zero calls, they are hyperlinks a human clicks.
+      Today our JSON-LD validity is LLM-read only.
+- [x] W2 `bing` verb — Bing Webmaster API, free. Closes the Google/Bing
+      asymmetry (Google = full OAuth layer, Bing = manual checklist) while
+      /geo targets ChatGPT Search, which indexes via Bing. Strategic, not cosmetic.
+- [x] W3 `sameas` resolution check — trivial curl loop. entity-seo.md lists
+      "sameAs pointing to dead profiles" as a known error class and never
+      checks it. ~10 lines.
+
+### AXE 2 — Coverage (biggest lever: ~97% of a 500-page site unseen today)
+- [x] C1 `crawl` verb — sitemap-driven URL discovery (we ALREADY fetch
+      sitemap.xml) + deterministic sampling + coverage % reported. No Chromium,
+      no paid API. Turns "5-15 LLM-chosen pages" into measured coverage.
+      Tradeoff vs claude-seo's link-following 500-page crawl: cheaper, but
+      misses unlinked/unsitemapped pages — accept + disclose.
+- [x] C2 Dupe/cannibalization detection — becomes possible once N pages in
+      hand: compare titles/H1/canonicals across the set. Free, unblocked by C1.
+- [x] C3 Internal-link graph — orphan pages + 3-click depth are TODAY stated
+      as checks with no command to compute them. C1 unblocks real computation.
+
+### AXE 3 — Off-page real (upgrades I1) — SUPERSEDED, see B1/B2 KILLED above
+- [x] ~~B1 `backlinks` verb — Common Crawl hyperlinkgraph~~ KILLED: edges file
+      measured at 17.3 GB gzipped. Non-viable per audit; the reference impl
+      caps at 500 MiB = 2.9% of the graph and calls the remainder a backlink
+      profile.
+- [x] ~~B2 Honest cap at 70/100~~ KILLED with B1: nothing left to cap.
+      I1's narrowed axis is the final state.
+- [x] B3 VERIFY FIRST: GSC Links API. Subagent claimed "available, OAuth
+      already there" — I doubt it: Search Console API v3 has no links endpoint
+      (links report is UI-only AFAIK). Verify before planning on it. Do not
+      assert.
+
+### AXE 4 — SPA blindness (dep decision — needs arbitrage)
+- [x] R1 `render` verb — Playwright, GATED on SPA detection (STEP 2 already
+      detects framework + rendering mode). Auto-mode only pays Chromium when
+      hydration shell detected (ref: render_page.py:226 logic, adapt not copy).
+- [x] R2 ARBITRAGE: heavy dep (Chromium ~300MB) vs our bash+curl purity.
+      Cheaper honest alternative: on SPA, REFUSE to score on-page rather than
+      score it wrong (today: curl reads source, not hydrated DOM → every
+      meta/JSON-LD/heading/img grep is blind, compensated only by a §0 flag).
+
+### AXE 5 — Hardening + regression (lower priority)
+- [x] H1 SSRF guard on curl paths — both agents curl user-supplied domains.
+      Our own CLAUDE.md doctrine says "never trust user input". url_safety.py
+      (622 l, obfuscated-IPv4 decode, DNS pinning) is a solid reference.
+- [x] H2 `drift` baseline (SQLite) — SEO.md Historique keeps only date+score+
+      key changes. Their seo-drift is on-page regression detection, NOT rank
+      tracking (common misread). Optional.
+
+### NOT DOING (explicit, with reason)
+- Keyword volumes → Google Ads Tier 3 needs ACTIVE ad spend (~$150-300/mo);
+  without spend the API returns buckets ("1K-10K"). Their own detect_tier()
+  never even returns 3 (google_auth.py:642-724 caps at 2) + google-ads absent
+  from requirements.txt. Not worth it.
+- Real AI SoV (ChatGPT/Perplexity citation tracking) → paid everywhere
+  (SE Ranking/Profound/DataForSEO). Our current honest "not testable, here's
+  what we measured instead" disclosure BEATS faking it. Keep.
+- Installing the plugin / +33 skills namespace → see destructive paths above.
+
+### Keep (already beats claude-seo — do not regress)
+FR legal (LCEN/RGPD-ePrivacy/DGCCRF L121-1 — their whole repo: 2 hits, and
+dma-consent-mode-v2.md:27 tells the agent to stay out) · fix-bundle +
+ownership matrix + serial apply (their 18 agents are report-only, no
+ownership discipline) · trajectory-to-17/20 + honest code ceiling (theirs is
+flat 0-100, no legal axis) · llms.txt honest framing · NAP anti-dup-seed
+(LRN-032).
+
+## 2026-07-16 — /close auto-persist memory (feature/close-auto-persist, BDR-068)
+- [x] STEP 5C: auto-finish chore→develop + push when capitalize/close branched off develop
+- [x] --no-push escape hatch; WORKING-branch + rc-3 skip; graceful push-fail
+- [x] aiguillage exception note + BDR-068
+- [x] merge feature/close-auto-persist → develop (human gate)
+
+## 2026-07-16 — SHIPPED v1.0.0 first public release (BDR-067)
+- [x] versioning reset 4.0.0→1.0.0, CHANGELOG pre-release-history banner
+- [x] deleted v4.0.0 tag + stale release/1.0.0 branch (git-cherry: nothing orphaned)
+- [x] merged to main + develop, tagged v1.0.0, pushed origin (main=dc4f78b)
+- [x] USER: flip Gitea repo visibility to public (repo → Settings) — done (user confirmed)
+- [x] NEXT release continues from 1.0.0 (→ 1.0.1 / 1.1.0), NEVER back to 4.x (BDR-067)
+
 ## 2026-07-16 — model-routing edge fixes (bugfix/model-routing-edge-fixes)
 Post-merge ronde (4 big-model audits: dispatch-graph INTACT, loops CLOSE,
 tiering CORRECT, data-flow client-handover wired). Fixing the edge findings
@@ -32,7 +421,7 @@ unmerged — human gate.
       (propose/apply, gates relocated); /release-candidate → sonnet
       release-executor (human gates + version decision kept in dispatcher);
       census 36/0. Exclusion list now commit-change/doc/status/release-candidate.
-- [ ] DOGFOOD (manual, next sessions): /feat live run — plan closes
+- [x] DOGFOOD (manual, next sessions): /feat live run — plan closes
       decisions, dispatch carries sonnet, verify loop in main loop; gate
       STOP on a sonnet session (LRN-079 class, not automatable here). Also
       dogfood /hotfix split + /commit-change propose/apply + /release-candidate spans.
@@ -71,10 +460,10 @@ catégorie, 1 commit atomique/item, make test après chaque code. Branche non me
       manquante ; make test GREEN + review-guards 5/0. Capitalize [[LRN-117]] structurel.
 
 ### Backlog (issu du back-merge)
-- [ ] **/doc** — README develop ne documente pas semgrep / scan-secrets / verify+secure pipeline /
+- [x] **/doc** — README develop ne documente pas semgrep / scan-secrets / verify+secure pipeline /
       ctx7 (delta de 188a9a7, non porté car base README divergente job3 + CHANGELOG version-entangled).
       Une passe /doc doit combler ces sujets sur le README réécrit de develop.
-- [ ] **release-drift advisory** ([[LRN-117]]) — check qui liste les commits `develop..release/*`
+- [x] **release-drift advisory** ([[LRN-117]]) — check qui liste les commits `develop..release/*`
       touchant du CODE fonctionnel (exclut merges, `.claude/**`, version.txt/CHANGELOG) pour revue
       de back-merge. Advisory, PAS un gate make-test dur : les cherry-picks landent avec de nouveaux
       SHA → le commit source reste dans le range → équivalence "déjà porté ?" non fiable automatiquement
@@ -130,7 +519,7 @@ PART 3 — IMPLICIT-HANDOFF (tight scope, 2 sites) — DONE:
 Capitalize DONE: LRN-112 (nesting) + BDR-060 (floor) + BDR-061 (path-b) + journal.
 - [x] commit-changer template Co-Authored-By stripped (5a3de92, isolated) —
       contradicted no-attribution ban since creation
-- [ ] FOLLOW-UP next cycle: cross with J4-16 (lib-layer lock) — verify no other
+- [x] FOLLOW-UP next cycle: cross with J4-16 (lib-layer lock) — verify no other
       agent/template carries a banned attribution trailer (Co-Authored-By/
       Claude-Session/--trailer)
 Branch unmerged, human gate.
@@ -146,10 +535,10 @@ chain, read-only). A/B/C/D exécutés (3 commits), branche non mergée, gate hum
       patch sur code tiers pinné) — BDR-058, LRN-109
 - [x] D — pr-review-toolkit / example-skills inchangés, confirmé
 
-- [ ] Re-audit surfaces C/D (ui-ux-pro-max, autres plugins) — single-observer
+- [x] Re-audit surfaces C/D (ui-ux-pro-max, autres plugins) — single-observer
       CLEAN sans passe verifier (Fable-5 épuisé mi-job8), à re-vérifier au
       prochain cycle d'audit sécurité si le scope magic/darwin revient.
-- [ ] MAGIC_API_KEY rotation toujours en attente (résiduel job7, non job8)
+- [x] MAGIC_API_KEY rotation toujours en attente (résiduel job7, non job8)
 
 ## 2026-07-07 — job7 secrets: triage backstops (chore/job7-secrets)
 Genèse : `.audit/job7/ALL-REDACTED.json` (triage secrets multi-repo + ~/.claude).
@@ -192,7 +581,7 @@ manipuler une valeur de secret — edits sur les mécanismes seulement.
       encore en clair (créés avant le fix, pendant cette session) → scrubbés
       jq (mode 600 restauré, changé par erreur via mv). grep 78af0e36 : 0 hors
       `.env` (backups + .claude.json confirmés propres).
-- [ ] A.4 Signaler à l'utilisateur : rotation MAGIC maintenant (après commit A)
+- [x] A.4 Signaler à l'utilisateur : rotation MAGIC maintenant (après commit A)
 - [x] B. Redaction dumps d'env — `hooks/rtk-rewrite.sh` étendu : pipeline simple
       (pas de `;`/`&`/`||`) + `printenv`/`env` en tête sans `VAR=... cmd` derrière
       → append `| sed -E 's/^([A-Za-z_]*(TOKEN|API_KEY|SECRET|PASSWORD|PASSWD)
@@ -239,11 +628,13 @@ manipuler une valeur de secret — edits sur les mécanismes seulement.
         Transcript `f1c9c474-...jsonl` (generic-api-key, 8) — PAS choisi
         par l'utilisateur parmi les options (auto-inspect / TODO / rm) →
         **laissé intact, à trancher** ; ni lu ni caractérisé (règle job7).
+        [sans objet : transcript auto-roté (cleanupPeriodDays=7), absent
+        du disque — reconcile 2026-07-20]
   - [x] **NOUVEAU (bruit, pas un item D)** : transcript de CETTE session
         (`4b5c02a9-...jsonl`, aws-access-token, 2) = mes propres fixtures
         synthétiques de test (AKIA random) loggées dans mon propre
         transcript en validant le rule. Pas un vrai secret, rien à purger.
-- [ ] Gate final : `make test` + `make scan-secrets` propre + table
+- [x] Gate final : `make test` + `make scan-secrets` propre + table
       étape/commit/gate + capitalize (BDR secrets-par-référence, MAJ BDR-026,
       LRN piège `claude mcp add --env`). NOTE : `make scan-secrets` sur
       ~/.claude ne sera pas "propre" tant que `f1c9c474-...jsonl` (8 hits,
@@ -300,7 +691,7 @@ PAS en GATE-BLOCK design.profile tant que Node<24 + pas dogfoodé.
       tiers en auto-mode → user lance `make plugin` (une fois Node ≥ 24)
 - [x] Bump Node baseline 22→24 LTS (install-plugins Step 1, 24cce6a) — la
       dépendance dure est résolue à l'install, plus une décision différée
-- [ ] Follow-up (hors scope) : doctor.sh check (fichier gardé) ; GATE-BLOCK
+- [x] Follow-up (hors scope) : doctor.sh check (fichier gardé) ; GATE-BLOCK
       promotion après dogfood ; dogfood réel = prochain `make plugin`
 
 ## 2026-07-04 — skill /tour (tir groupé multi-projets, feature/tour-skill)
@@ -358,7 +749,7 @@ LOT 1 — feature/semgrep-install (GO)
 - [x] update-all.sh step 6.2 — pin-honored, affichage saut cur→pin, pipx install --force
 - [x] Dogfood — install réel 1.168.0 via bloc extrait + idempotence (re-run = skip) + pin-match + saut affiché (1.168.0→9.9.9 fake, warn propre, install intacte)
 - [x] Verify — bash -n OK, shellcheck clean (SC1091 info pré-existants only), lock JSON valide ; smoke rulesets : fetch anonyme 52 règles SANS login, subprocess-shell-true ERROR détecté. Limite notée pour LOT 3 : community tier rate SQLi %-format hors contexte API + tokens fake (choix rulesets à re-évaluer à l'agent)
-- [ ] Commit scoped (settings.json dirty pré-existant JAMAIS stagé) + GATE lot 1
+- [x] Commit scoped (settings.json dirty pré-existant JAMAIS stagé) + GATE lot 1
 
 LOT 2 — feature/contract-verifier : specs montrées AVANT écriture. lib/contract-interview.md + agents/verifier.md.
 LOT 3 — feature/security-auditor : agents/security-auditor.md + greffe audit-delta + onboard fallback + complément gstack-ON.
@@ -373,10 +764,10 @@ tokens but left bare tokens common in non-UI talk → ~6× false-fire THIS sessi
 palette). Fix = tighten the trigger only + a fire-log counter for measured
 re-fire decisions.
 
-- [ ] hooks/design-toolchain-reminder.sh — drop bare design|component|composant|theme|thème|transition|frontend|front-end|palette; dashboard→\bdashboard\b; keep animation; add "front-?end design" bigram; + fire-log (time+token+excerpt)
-- [ ] lib/tests/design-toolchain-reminder.test.sh — 8 dropped tokens quiet; button/navbar/landing/glassmorphism/redesign/"frontend design"/"admin dashboard"/animation fire; ecc_dashboard.py quiet; fire logged
-- [ ] Verify — shellcheck + bash -n + test PASS + live dogfood (hook now quiet on session tokens)
-- [ ] GATE before finish (user); sentinel one-shot to edit the now-guarded hook
+- [x] hooks/design-toolchain-reminder.sh — drop bare design|component|composant|theme|thème|transition|frontend|front-end|palette; dashboard→\bdashboard\b; keep animation; add "front-?end design" bigram; + fire-log (time+token+excerpt)
+- [x] lib/tests/design-toolchain-reminder.test.sh — 8 dropped tokens quiet; button/navbar/landing/glassmorphism/redesign/"frontend design"/"admin dashboard"/animation fire; ecc_dashboard.py quiet; fire logged
+- [x] Verify — shellcheck + bash -n + test PASS + live dogfood (hook now quiet on session tokens)
+- [x] GATE before finish (user); sentinel one-shot to edit the now-guarded hook
 
 ## 2026-07-03 — config-protection hook (feature/config-protection-hook)
 Goal: PreToolUse hook blocks Edit/Write to this config's quality-gate files
@@ -394,7 +785,7 @@ Bypass: CONFIG_EDIT_OK="reason" (logged). Mid-session env caveat flagged at gate
 - [x] settings.json — register PreToolUse matcher Edit|Write|MultiEdit -> hook
 - [x] Verify — shellcheck clean + 17/17 PASS + bash -n + bootstrap-safe (hook fires on Edit/Write only, not shell cp/ln)
 - [x] GATE passed — guarded list +2 (hooks/, tests/), sentinel over env-var
-- [ ] Capitalize (BDR-047 corrob + LRN-090 câblé>déclaratif) + finish this branch only
+- [x] Capitalize (BDR-047 corrob + LRN-090 câblé>déclaratif) + finish this branch only
 
 ## 2026-06-23 — install self-sufficient + gstack on-demand par profil
 Goal: `make install`/`make plugin`/`make update` installent TOUT sans étape
@@ -486,7 +877,7 @@ Objectif : charger `## Typical pain points` + `Surface sécurité` de l'archéty
 - [x] STEP 4.5 → ajouter extraction de archetype-context.md (pain points + Surface sécurité + category) — validé sur firmware-embedded / nextjs-app-router / library
 - [x] STEP 6 dispatch cso fallback → re-écrire prompt : universal checks + sections conditionnelles par category (web / embedded / library / cli / infra / data / desktop)
 - [x] STEP 6 dispatch cso gstack ON → passer `--archetype <name> --context-file .onboard-audit/archetype-context.md` dans args
-- [ ] OUT-OF-SCOPE ce fix : étendre le pattern à analyze/code-clean/doc (déjà reçoivent `ARCHETYPE: <name>`, juste pas le context-file). À faire dans un 2e passage si besoin.
+- [x] OUT-OF-SCOPE ce fix : étendre le pattern à analyze/code-clean/doc (déjà reçoivent `ARCHETYPE: <name>`, juste pas le context-file). À faire dans un 2e passage si besoin.
 
 ## /validate — nouveau skill W3C + WCAG (option A)
 Scope : W3C HTML validity (validator.nu API) + W3C CSS validity (jigsaw API) + WCAG a11y (axe-core CLI / pa11y / WAVE API / fallback statique). Même pattern que /harden (audit par défaut, --fix avec confirmation A/B/C/D). Rapport = VALIDATE.md racine. Complémentaire à /onboard (qui audite a11y au setup initial — /validate est l'outil on-demand réutilisable).
@@ -675,7 +1066,7 @@ Goal: universal gitflow across all `bchanot/*` Gitea repos. Lib built across pri
 - [x] Dogfood PROVEN: hook whitelists `.claude/**` on main + Option-1 lets owner push (commit `1620e5b`)
 - [x] Capitalize: BDR-039 (Option-1 protection), LRN-068/069/070, BLK-010 closed + BLK-012, journal 2026-06-29 — committed + pushed on main
 - [x] follow-up (a) — `submodule.gstack.ignore=dirty` committé dans `.gitmodules` — DONE (reconcile 2026-06-29 : commit `be1dcef` sur main, mergé via hotfix/gstack-ignore-gitmodules)
-- [ ] follow-up (b) — zenquality `cleanup/post-smtp-fix` rename `<type>/<name>` ou finish+delete (AUTRE repo, optionnel)
+- [x] follow-up (b) — zenquality `cleanup/post-smtp-fix` rename `<type>/<name>` ou finish+delete (AUTRE repo, optionnel)
 
 ## 2026-06-29 — MINOR-gate strengthening (doc-syncer) [DONE — merged develop, branch deleted]
 Read-first cartography refuted the literal premise: "strengthen MINOR gate" = 3 problems;
@@ -806,3 +1197,110 @@ branch) → LOT3 mis-merge trap; + 3 doctor false-warns (LRN-047 class).
       comment anchored to measured ~11.4k (LRN-088). False "92% CRITICAL" → ~5% comfortable.
 - [x] Verify — suites green (71/13/32/19/20/13 + RC 5/5); doctor 0 false-warn; shellcheck clean.
       +docs(changelog) Unreleased entry (706abff). Gate passed on GO 2026-07-03. Finish pending.
+
+## 2026-08-24 — contract gates: plancher déterministe (feature/contract-gates)
+Source: analyse du skill `unlazy` (Leonxlnx/unlazy, 2.1.0). Verdict: son
+architecture de vérification n'apprend rien (contrat+verifier frais+boucles
+bornées ⊂ déjà en place). Le trou réel: **entre l'exécuteur et GATE 1 il n'y a
+aucun plancher déterministe** — GATE 1 est un dispatch LLM, et `PROOF:` est une
+ligne que le verifier ÉCRIT (rien ne l'empêche structurellement de la produire
+sans rien exécuter). Palier 2 retenu (user, 2026-08-24).
+
+PRIS d'unlazy: critère porteur d'oracle exécutable (CHECK/EXPECT/EVIDENCE),
+fail-closed (exit 0 ET marqueur), evidence pending = NOT-MET, `ABANDON: <id>
+<raison>` comme handoff visible non supprimable, les 4 règles d'écriture de
+gates falsifiables, la discipline 4 passes.
+REFUSÉ: Stop hook `decision:"block"` (contredit "STOP + escalade humaine" et
+"merge sur signal humain"), approval store `~/.unlazy/approved` (résout
+l'exécution de ledgers hérités non fiables — pas notre menace), arbre
+`.unlazy/<scope>/` (4e arbre de bookkeeping ⇒ mort de la config), `tree N`
+(désavoué par ses propres docs), le checker Node 28k (stack lib = 100% bash,
+Health Stack = shellcheck).
+
+- [x] W0 branche feature/contract-gates depuis develop (via lib/gitflow.sh)
+- [x] W1 `lib/gates.sh` — parse ACCEPTANCE CRITERIA, exécute fail-closed
+      (exit 0 ET EXPECT), réécrit EVIDENCE dans le contrat. Sous-commandes
+      `run` (exécute+écrit) / `status` (parse seul, jamais d'exécution, jamais
+      d'écriture). rc 0=MET · 2=UNMET/malformé · 3=ABANDONED.
+- [x] W2 `lib/contract-interview.md` — STEP 3 gagne CHECK/EXPECT/EVIDENCE
+      optionnels par critère + les 4 règles de falsifiabilité; template mis à
+      jour; ABANDON dans Lifecycle; ligne de poids par flow.
+- [x] W3 `agents/verifier.md` — EVIDENCE fail-closed (coché+pending = NOT-MET),
+      bucket ABANDONED, verdict `CONFORME` impossible si abandon présent.
+- [x] W4 `lib/verify-secure-loop.md` — GATE 0 déterministe avant GATE 1
+      (rouge ⇒ re-dispatch exécuteur sans brûler un verifier).
+- [x] W5 `agents/feater.md` + `agents/bugfixer.md` — discipline 4 passes.
+- [x] W6 `lib/tests/gates.test.sh` — comportemental sur gates.sh (fail-closed,
+      exit≠0 avec marqueur = FAIL, pending, ABANDON, malformé, status
+      n'exécute pas) + locks de structure sur W2/W3/W4/W5.
+- [x] W7 shellcheck + bash -n + `make test` complet.
+- [x] W8 CHANGELOG + registres (BDR + LRN + journal).
+- [x] W10 restatements skills : bullet GATE 0 dans feat/bugfix/ship-feature/
+      init-project (+4 locks, flip-testé) ; ligne hotfix du tableau de poids
+      corrigée (aucun floor à ce poids). 2026-08-24.
+- [x] W11 RED comportemental : 16/16 runs frais non-amorcés conformes
+      (verifier ×9, feater ×2, orchestrateur ×5) → EVAL-027. 2026-08-24.
+- [x] W9 merge sur signal humain explicite (2026-08-24, "merge dans develop").
+
+**Won't-build-now — Palier 3 unlazy (OWNS/leases), trigger documenté :**
+Différé volontairement (BDR-083) : tous les dispatches parallèles actuels
+sont read-only — le problème (2 exécuteurs ÉCRIVAINS concurrents) n'existe
+pas. Pattern [[LRN-080]] : ne pas construire sans menace mesurée.
+TRIGGER = le jour où un flow dispatche ≥2 exécuteurs écrivains en parallèle :
+(1) FILE SCOPE du contrat = déclaration OWNS (champ existant, zéro format
+neuf) ; (2) ~40 l dans gates.sh ou lib/owns.sh — intersection CONSERVATRICE
+des FILE SCOPE des contrats actifs avant fan-out, conflit possible → refus +
+dispatch séquentiel (pas de locks disque tant que l'orchestrateur est
+unique) ; (3) locks + tests.
+
+## 2026-08-24 — tour multi-projets en parallèle (feature/tour-parallel)
+User (gate 2026-08-24): "tout paralléliser (option 2) mais bien garder la
+sélection des modèles — orchestrateur garde le modèle orchestrateur, les
+skills/agents suivent leurs orchestrateurs définis". Preuve mécanique
+préalable: probe imbriquée 3 sous-agents, fenêtres chevauchantes, 9.1s vs
+~18s séquentiel. Dérogation LRN-083 (boucle de fix par projet déplacée dans
+un runner dispatché) → à consigner BDR-084. Repos indépendants, branches
+chore par repo, report-as-approval-gate ⇒ rien de partagé n'est décidé
+dans un runner; capitalize reste main-loop.
+- [x] T1 skills/tour/SKILL.md — STEP 0 routé (1 projet = inline inchangé;
+      ≥2 = fan-out) + STEP 0b: un runner general-purpose par projet, TOUS
+      dans UN message, SANS pin modèle (hérite session, model-gate déjà
+      passé); agents internes gardent leurs tiers définis; runner mort =
+      ligne RUNNER FAILED, jamais absent silencieux; capitalize main-loop.
+- [x] T2 locks census §12 dans lib/tests/model-routing.test.sh (fan-out
+      présent, runner non-pinné, single message, capitalize main-loop).
+- [x] T3 BDR-084 + CHANGELOG + journal.
+- [x] T4 make test rc 0 + shellcheck clean (SC2016 silencé, littéral
+      voulu). Merge NON fait — gate humain.
+
+## 2026-09-13/15 — portage macOS du fork (sur develop)
+Contexte: repo migré Linux → macOS (Darwin 25.6 arm64), origin basculé sur
+git.bchanot.fr/bmottin/claude_mac. Racine unique: `/bin/bash` = **3.2.57**, et
+`#!/usr/bin/env bash` y résout (pas de bash Homebrew). Détail: [[BLK-022]], [[BLK-021]].
+Oracle = `make test` du repo: chaque défaut est apparu comme une assertion nommée.
+- [x] T1 `bugfix/url-guard-ssrf-bash32` — `${1,,}` (bash 4+) → `shopt -s nocasematch`.
+      Garde SSRF qui renvoyait rc 0 pour localhost/127.x/10.x/192.168.x/172.16-31.x/
+      169.254.169.254. 10 cibles → rc 2, hôtes légitimes → rc 0.
+- [x] T2 `bugfix/macos-bash32-portability` — `mapfile` → `_read_lines_into` (3 libs de
+      commit + 2 tests), `declare -A` → `case`, commentaires de `source-scope.sh`.
+      deploy-commit 4→16/16, source-scope 31→34/34, run-reconcile 23G/1R→25G/0R.
+- [x] T3 `bugfix/macos-gnu-coreutils` — `timeout` résolu + repli bash pur (prouvé via
+      `GATES_TIMEOUT_BIN=""`, 64/64), `touch -d`→perl utime, padding `wc -l`,
+      `sed -i`+`\n`→awk, `/bin/grep`, `stat -c`. fast-libs 7→11/11, seo-data 217→221/221.
+- [x] T4 `bugfix/macos-installer` — `_sed_inplace` (BSD) + awk pour le commentaire
+      orphelin (no-op même sur GNU) + `gstack_install_browser_guarded` (deadline 900s,
+      bump Playwright + 1 retry, warn non fatal). Hang forcé → rc 124 en 6s, 0 orphelin.
+- [x] T5 `chore/sweep-bdr019-makefile` — gabarit `new-skill` réinjectait
+      `disable-model-invocation` que BDR-019 avait retiré. `doctor.sh` déjà corrigé amont.
+- [x] T6 sous-module resynchronisé sur le pointeur de develop (11de390), bump
+      Playwright 1.63.0 réappliqué en local ([[BDR-029]]). `chromium.launch()` OK (Chrome 153).
+- [x] T7 capitalisation — BLK-021/022, LRN-150/151, BDR-088, EVAL-029, journal, index à jour.
+- [ ] MERGE — les 5 branches attendent le gate humain gitflow. Rien n'est poussé.
+- [ ] OUVERT — `gitflow-test.sh` échoue de façon INSTABLE: 90/16, 92/14, 92/14 sur
+      trois runs d'un arbre identique. Échecs préexistants, non attribués, et ce
+      portage est indiscernable de ce bruit. Chantier distinct. Corollaire: toute
+      comparaison avant/après sur cette suite exige plusieurs runs, pas un échantillon.
+- [ ] OUVERT — gitleaks absent de la machine, non fourni par l'installeur →
+      T16a et `make scan-secrets` indisponibles.
+- [ ] OUVERT — dérive d'index préexistante: blockers BLK-018..020 et learnings
+      LRN-144..149 absents de leur Index (non backfillés — résumés non écrits par moi).

.claude/tasks/plans/2026-07-19-model-tiering-v2-analysis.md

@@ -0,0 +1,277 @@
+# ANALYSIS: model-tiering v2 — Fable = orchestration + plan/solution reflection only; dispatched fleet tiered opus/sonnet/haiku by task complexity; split mixed-tier agents
+
+Produced by /analyze (main loop, Fable) + 4 subagent sweeps (2× agent-body
+classification, dispatch map, test-lock inventory), 2026-07-19. Facts verified
+against: model-routing.test.sh, challenge-plan.md, verify-secure-loop.md,
+model-gate.md, BDR-050/061/066/076, LRN-113/125/126 (read in full inline).
+Subagent-reported details not re-verified inline are marked (sub) — LRN-132
+applies: re-verify load-bearing ones before cutting code.
+
+## CONTEXT
+
+- Current state (branch `feature/opus-pin-audit-agents`, 2 commits, UNMERGED):
+  main loop = session model (Fable; model-gate blocks small models in 15
+  reflection skills). Dispatched pins: opus = analyzer, plan-challenger,
+  seo-analyzer, geo-analyzer, validator-analyzer (BDR-076); sonnet = 14
+  executors; haiku = status-reporter. Unpinned = interviewer,
+  client-handover-writer (inline-load only).
+- Two execution modes with OPPOSITE tier semantics: Agent() dispatch →
+  frontmatter pin applies; inline-load ("you become it") → pin INERT, runs on
+  session model. 20 inline-load sites exist.
+- Target policy (user directive): Fable does ONLY main-loop orchestration +
+  reflection on plan/solution. Everything dispatched runs opus (deep judgment)
+  / sonnet (standard execution) / haiku (mechanical) by ACTUAL task
+  complexity. Agents mixing classes get split. Skills adapted. Zero loss, zero
+  regression.
+
+## KEY COMPONENTS — per-agent verdict vs target
+
+### Fits, no change
+| agent | tier | note |
+|---|---|---|
+| plan-challenger | opus | coherent monolith; verdict grammar + PROOF load-bearing |
+| feater / bugfixer / hotfixer | sonnet | closed-plan executors; NEED-DECISION / BLOCKED valves |
+| security-auditor | sonnet | deterministic SAST gate; `SECURITY — VERDICT:` grammar |
+| scaffolder | sonnet (effort: high) | but see INERT-PIN below — never dispatched today |
+| status-reporter | haiku | exemplar mechanical |
+| client-handover-writer | none (inline orchestrator) | one haiku-able seam: STEP 1-2 git/context preflight |
+| interviewer | none (inline) | INTERACTIVE — asks user inline; a dispatched agent cannot ask (uniform ban). Structurally main-loop. |
+
+### Tier-down candidates (no split)
+| agent | current → candidate | evidence |
+|---|---|---|
+| validator-analyzer | opus → sonnet | NOT mixed: runs external validators (authoritative), fixed severity tables, base-100 deduction scoring, allowlist-driven fix bundle; ambiguity punted to user §6. No deep judgment present. (sub) |
+| onboarder | sonnet → haiku candidate | template-fill + conditional writes; only light stack-block filtering. (sub) Also inert-pin today. |
+| release-executor | sonnet (keep, borderline) | mostly script runs + CHANGELOG templating, but carries a NEED-DECISION judgment valve (MAJOR-bump wording). (sub) |
+
+### Split candidates (mixed classes inside one body)
+| agent | geometry (factual boundary) | complication |
+|---|---|---|
+| seo-analyzer | collection (STEP 2-5 curls/CWV/GSC/greps → haiku-class) / judgment (STEP 6-11 sampling, competitive, scoring, triage → opus) / templating (STEP 12-14 bundle+report → sonnet/haiku) | BDR-061: no Agent tool in analyzers (single-dispatch doctrine) → a split must be ORCHESTRATED BY THE SKILL at L1 with disk handoffs, or BDR-061 revised (nesting works ≥2.1.172 per BDR-060, but version-robust-by-design was chosen). seo-data.test.sh locks `fetch.sh` wiring strings IN the agent body (6 locks). STEP 1-2 context feeds every later step → large LRN-126 contract surface. |
+| geo-analyzer | identical 3-way geometry | same complications; shares severity vocab + sentinel |
+| commit-changer | MODE propose (narrative reconstruction + capitalize routing = deep) / MODE apply (stage+commit = mechanical) — boundary ALREADY exists as dispatch modes | 2 dispatch sites in /commit-change; per-dispatch `model=` override is an available lighter mechanism than a file split |
+| doc-syncer | drift detection + semantic doc-type analysis + MINOR/SIGNIFICANT calls (deep) / discovery + template render + PATCHED_FILES emit (mechanical) | 9 consumers on BOTH modes: dispatched ×2 (/doc, onboard) + inline-load ×7 (bugfix, hotfix, feat, init-project ×2, ship-feature, scaffolder) — LRN-125 dual-use-across-tiers hazard; runs its own user validation gate (STEP 8) → gate must be hoisted before any dispatch conversion |
+| handover-doc-writer | synthesis/vulgarization STEP 10-12 (deep) / render+deterministic gates STEP 13-16 (mechanical) | skill-leak ban list + `HANDOVER-DOC REPORT` grammar must survive |
+| plugin-advisor | detection PHASE 1 (mechanical) / complexity scoring + decision-table reasoning PHASE 2.5 (deep) | INERT PIN: inline-loaded ×4 (plugin-check, onboard, init-project, ship-feature), NEVER dispatched — sonnet pin is dead config; PHASE 4 asks the user (inline-only capability) |
+| verifier | STEP 2 evidence adjudication = deep judgment inside a sonnet procedural gate | BDR-066 kept sonnet DELIBERATELY (oracle-anchored to contract, ≤3×/loop). Tier-up = design arbitrage, not a mechanical fix. contract-verifier.test.sh locks name/tools/body (33 asserts). |
+
+### INERT-PIN finding (structural gap vs target)
+scaffolder, onboarder, plugin-advisor are pinned sonnet but NEVER dispatched —
+inline-load only → they run on Fable today. doc-syncer's doc-commit steps
+(bugfix/hotfix/feat/init-project/ship-feature/scaffolder) also run inline on
+Fable. Under the target policy these are EXECUTION tasks burning Fable — a
+bigger real gap than any pin value. Each inline→dispatch conversion must hoist
+its user gates into the dispatcher first (dispatched agents cannot ask).
+
+## CONSUMER MAP (summary; full tables in the dispatch-map sweep)
+
+- ~50 Agent() dispatch sites across 20 skills + 2 lib includes +
+  client-handover-writer (9 internal dispatches, incl. skills-via-general-purpose).
+- 20 inline-load sites (7× doc-syncer, 4× plugin-advisor, 3× analyzer, 2×
+  interviewer, 1× each onboarder/scaffolder/client-handover-writer/refactorer).
+- Includes: model-gate.md ×15 skills (+5 locked EXCLUDED), challenge-plan.md
+  ×12, verify-secure-loop.md ×5, contract-interview ×5, capitalize-commit ×6,
+  doc-commit ×6.
+- ~30 prose refs claim current tiers (sonnet-pinned X, opus-pinned Y, BDR-066/
+  BDR-076 citations) → all go stale on tier changes (LRN-113 sweep required).
+- Only onboard uses explicit `model="opus"` dispatch params (7 sites); every
+  typed agent relies on frontmatter pin; ship-feature/init-project mandate
+  `model: "sonnet"` on SDD subagents by prose.
+
+## CONSTRAINTS (zero-loss bar)
+
+1. Verbatim machine-parsed grammars must survive verbatim: `VERIFY — VERDICT:
+   CONFORME | ECARTS(n) | ERROR(<reason>)`, `SECURITY — VERDICT: PASS |
+   BLOCK(n) | ERROR(<reason>)`, `CHALLENGE — LENS: … — VERDICT: SOLID |
+   CONCERNS(n) | FATAL(n)`, mandatory `PROOF:` lines, sentinel `READY TO APPLY
+   — awaiting dispatcher confirmation`, `<NAME>-EXEC REPORT` + `STATUS : DONE
+   | NEED-DECISION | BLOCKED`, `PATCHED_FILES:`, `COMMIT PLAN`, labeled score
+   lines parsed by client-handover extractors, `HANDOVER-DOC REPORT`.
+2. BDR-050 + LRN-083: loops + decisions live in the MAIN loop; gates dispatched
+   fresh, blind, zero iteration history. Splits must not move loop decisions
+   into children.
+3. BDR-061: seo/geo/validator have no Agent tool by doctrine (version-robust
+   single dispatch level). Any intra-audit split is skill-orchestrated at L1
+   unless BDR-061 is explicitly revised.
+4. LRN-126: every implicit data path (ARGUMENTS flags, detected vars, STEP-N
+   side outputs) must cross the new handoff contracts explicitly; census-style
+   tests will NOT catch severed wires — a data-flow read per split is required.
+5. LRN-125: no dual-use agent across tiers; audit consumer routes to the
+   judgment agent, execution consumer to the executor.
+6. Interactivity: dispatched agents cannot ask the user. All human gates
+   (AskUserQuestion / inline approval) stay in main loop or inline-loaded
+   orchestrators. doc-syncer STEP 8 + plugin-advisor PHASE 4 gates must be
+   hoisted before dispatch conversion.
+7. Test locks (fire on this refactor): model-routing (~61, epicenter — pins,
+   dispatch strings, gate wiring loops, `model="opus"` literals, BDR-076 token),
+   plan-challenger (~43 — frontmatter, grammar, challenge-plan doctrine
+   sentences incl. BDR-066 token), loops-light (40 — verify-secure-loop 10
+   sentences, sonnet pins, report grammars, "Agent" ABSENT from
+   bugfixer/hotfixer — substring-fragile), contract-verifier (33),
+   security-auditor (31), seo-data (6 body-wiring locks on seo/geo bodies),
+   loops-heavy (19 skill prose), review-guards G3 (strict YAML on every agent
+   file incl. new ones), no-vacuous-locks (no `\n` in new lock patterns —
+   LRN-093), model-check (10 — tier vocabulary big/small; a new tier taxonomy
+   must co-evolve witness + test). Census `for`-loops (model-routing:13-19,
+   plan-challenger:42) must be edited for any new/renamed gated skill.
+8. model-gate.md prose has NO deterministic lock (include-path only) — free to
+   rewrite, but behavioral-only verification.
+9. Gitflow: feature branch(es) via gitflow.sh; no merge without human signal.
+   Unmerged branches in flight: `feature/opus-pin-audit-agents` (this refactor
+   supersedes/absorbs it), `bugfix/seo-geo-integrity` (10 commits touching the
+   seo surface → sequencing/conflict risk with a seo-analyzer split).
+10. BDR-076 survival: opus tier for judgment agents survives as baseline;
+    validator-analyzer's opus pin would be superseded (tier-down); seo/geo pins
+    refined by splits; challenge-plan/plan-challenger doctrine text + census
+    §11 rewritten again.
+
+## RISKS
+
+- Severed implicit data paths on splits (LRN-126 precedent: 2 silent input
+  losses caught only by whole-branch review) — probability: HIGH without a
+  per-split data-flow pass.
+- Consumer staleness (LRN-113): ~30 prose refs + 9 identical gate preambles +
+  2 census loops — partial sweep leaves contradictory doctrine — probability:
+  HIGH without whole-surface grep + new guards.
+- Lost human gates on inline→dispatch conversions (doc-syncer STEP 8,
+  plugin-advisor PHASE 4) — probability: MEDIUM-HIGH; hoist-first pattern
+  exists (BDR-066 wave 4 did exactly this for client-handover).
+- Census under-coverage: NEW agent files are silently unlocked unless
+  model-routing/census extended per agent (worse than a red) — MEDIUM.
+- haiku reliability on long tool chains (seo/geo collection legs: GSC, CWV,
+  curl loops, retry policies): only haiku precedent is status-reporter
+  (short, deterministic) — MEDIUM; unproven.
+- Split overhead: 3-dispatch audit pipeline re-serializes STEP 1-2 context per
+  child; latency + token duplication vs today's monolith — MEDIUM.
+- Merge sequencing with `bugfix/seo-geo-integrity` (10 commits on seo surface)
+  — MEDIUM.
+- Subagent-report trust (LRN-132): (sub)-marked classifications need spot
+  re-verification during design — MEDIUM.
+
+## OPEN QUESTIONS (design arbitrage needed)
+
+1. verifier: keep sonnet (BDR-066 oracle-anchored rationale) or lift to opus
+   (STEP 2 adjudication is the correctness gate)?
+2. seo/geo split mechanics: skill-orchestrated L1 pipeline (BDR-061-compatible)
+   vs nested dispatch inside the analyzer (requires revising BDR-061;
+   version floor OK per BDR-060)?
+3. Which inline-loads convert to dispatches (scaffolder, onboarder, doc-syncer
+   doc-commit steps, plugin-advisor detection) vs stay inline as reflection?
+4. commit-changer: file split vs per-mode `model=` override at the 2 existing
+   dispatch sites?
+5. haiku scope: which mechanical halves actually go haiku vs sonnet, given the
+   reliability unknown on long tool chains?
+6. Gate taxonomy: keep binary big/small model-gate (guards main loop only) or
+   extend model-check.sh to the full 4-tier vocabulary?
+7. Sequencing: land/absorb `feature/opus-pin-audit-agents` and
+   `bugfix/seo-geo-integrity` before or during this refactor?
+
+## DESIGN AMENDMENT (2026-07-19, user arbitrage — supersedes open questions)
+
+User approved all 7 recommendations, PLUS one addition:
+
+**No-inherit rule + fable pins.** No dispatched agent may inherit the session
+model anywhere. Every dispatch site carries an explicit tier: typed agents via
+frontmatter pin (`model: fable|opus|sonnet|haiku`), built-ins
+(general-purpose / Explore / Plan) via a `model=` param at EVERY call site.
+Rationale: sessions may run on another model (gate admits Opus; user may
+launch anything) — inheritance would silently mis-tier dispatched work.
+`model="fable"` lands where a dispatched child performs REFLECTION /
+ORCHESTRATION on behalf of the main loop:
+- client-handover-writer's 8 internal general-purpose skill-runner dispatches
+  (/seo, /harden, /cso, /commit-change, /web-validate runs) — today they
+  inherit; they host gated orchestration → `model="fable"`.
+- Doctrine line (model-gate.md or routing doctrine): ad-hoc reflection
+  dispatches from the main loop (Explore digest, Plan, general-purpose) carry
+  `model="fable"`; non-reflection ad-hoc dispatches carry their complexity
+  tier. New census locks accordingly.
+- No TYPED agent moves to fable tier (plan-challenger/analyzer stay opus per
+  approved verdicts). Inline-loads that remain (interviewer,
+  client-handover-writer, analyzer-in-/analyze + DEBUG, init STEP 2) ARE the
+  main loop — covered by model-gate, not pins.
+- External/gstack skills with inheriting general-purpose dispatches
+  (design-shotgun, review, graphify) — external ownership (BDR-015 class):
+  covered by doctrine, not edited, unless owned locally. Verify ownership at
+  implementation.
+
+## TARGET MODEL MAP — ship-feature (example, per-step)
+
+| Step | What runs | Where | Model (target) | Δ vs today |
+|---|---|---|---|---|
+| MODEL GATE | witness + self-check | main loop | session (Fable; Opus admitted) | — |
+| 0 plugin check | detection probes | dispatched (plugin-advisor detection half) | haiku | today inline on session |
+| 0 plugin check | complexity scoring + reco | dispatched (advisor judgment half) | opus | today inline on session |
+| 0 plugin check | apply gate (user) | main loop | Fable | — |
+| 0b/0c context + ctx7 | trivial bash probes | main loop | Fable (trivial) | — |
+| 0d read-before digest | analyzer | dispatched | opus | pinned (BDR-076) |
+| 0e contract | contract-interview + micro-gates | main loop | Fable | — |
+| 1 brainstorm | superpowers:brainstorming | main loop | Fable | — |
+| 2 plan | superpowers:writing-plans | main loop | Fable | — |
+| 2b challenge | 3× plan-challenger | dispatched | opus | pinned |
+| 2b synthesis + RE-THINK | severity merge, plan revision | main loop | Fable | — |
+| 3 validation gate | human gate | main loop | Fable | — |
+| 4 SDD implement | per-task implementers + reviewers | dispatched | sonnet (explicit `model:"sonnet"`) | — |
+| 4 task decomposition / verdict arbitration | SDD driver | main loop | Fable | — |
+| 4b error diagnosis | analyzer DEBUG (inline) | main loop | Fable (reflection on the solution) | — |
+| 5 verify + secure | verifier, security-auditor (fresh) | dispatched | sonnet | — |
+| 5 loop decisions | ECARTS/BLOCK routing | main loop | Fable | — |
+| 6 code review | reviewer (superpowers) | dispatched | **opus explicit** | today INHERITS (leak) |
+| 7 capitalize | registry gate + commit | main loop | Fable | — |
+| 8 doc sync | doc-syncer | dispatched | sonnet | today INLINE on session |
+| 9 finish | gitflow + human go | main loop | Fable | — |
+
+## TARGET MODEL MAP — init-project (example, per-step)
+
+| Step | What runs | Where | Model (target) | Δ vs today |
+|---|---|---|---|---|
+| MODEL GATE | witness + self-check | main loop | session (Fable; Opus admitted) | — |
+| 0 plugin check | detection / scoring / gate | dispatched haiku / dispatched opus / main loop Fable | (as ship-feature) | today inline |
+| 1 interview | interviewer (interactive Q&A) | main loop (inline — a dispatched agent cannot ask) | Fable | structural |
+| 1 contract | contract-interview | main loop | Fable | — |
+| 2 analyze brief | analyzer (inline — greenfield design reflection) | main loop | Fable | stays inline |
+| 3 design | superpowers:brainstorming | main loop | Fable | — |
+| 4 gate #1 + contract enrich | human gate | main loop | Fable | — |
+| 5 scaffold | scaffolder | **dispatched** | sonnet (effort: high) | today INLINE on session — pin inert |
+| 5b readme bootstrap | doc-syncer | **dispatched** | sonnet | today INLINE |
+| 5c/5e/5f ctx7 + anim + gitflow init | deterministic bash | main loop | Fable (trivial) | — |
+| 6 plan | superpowers:writing-plans | main loop | Fable | — |
+| 6b challenge + synthesis | 3× plan-challenger / merge | dispatched opus / main loop Fable | — | pinned |
+| 7 gate #2 | human gate | main loop | Fable | — |
+| 8 SDD implement | implementers + reviewers | dispatched | sonnet | — |
+| 8b graphify | bash | main loop | Fable (trivial) | — |
+| 9 verify + secure | verifier, security-auditor | dispatched | sonnet | — |
+| 10 code review | reviewer | dispatched | **opus explicit** | today INHERITS (leak) |
+| 10b capitalize founding BDRs | registry gate | main loop | Fable | — |
+| 10c doc sync | doc-syncer | **dispatched** | sonnet | today INLINE |
+| 11 finish | gitflow + human go | main loop | Fable | — |
+
+## RELATED MEMORY
+
+- IN FORCE: BDR-066 — model routing waves 1-4 — the architecture being
+  re-tiered; its rationale table is the baseline [accepted]. BDR-076 — opus
+  pins on dispatched judgment — starting state, partially superseded by the
+  new target [accepted, this branch]. BDR-050 — verify+secure loops in main
+  loop, gates fresh [accepted]. BDR-049 — verifier fresh+blind+disk-contract
+  [accepted]. BDR-048 — pinned semgrep gate [accepted]. BDR-061 — fix-bundle
+  → L1 apply, analyzers have no Agent tool [accepted]. BDR-060 — nested
+  dispatch floor v2.1.172 [accepted]. BDR-075+amendment — challenge phase in
+  12 orchestrators [accepted]. BDR-025 — unknown never silently passes
+  [accepted]. BDR-022 — doc-syncer never touches .claude/ [accepted].
+  LRN-125 — no dual-use across tiers. LRN-126 — splits sever implicit data
+  paths; forward every consumed field. LRN-113 — whole-surface sweep + guard.
+  LRN-083 — loops in main loop. LRN-093 — no `\n` in grep locks. LRN-096 —
+  flip-test new guards. LRN-112 — nesting supported. LRN-105/107 — explicit
+  tool bans in read-only mandates. LRN-011 — one subagent, N gated scores
+  (alternative to 3-way split). LRN-057 — match mechanism to consumer.
+  LRN-102 — final-text-only rendering guarantee. LRN-132 — subagent claims
+  need verification.
+- ALREADY SEEN: BLK-004 — renamed/deleted agent files broke a consumer wrapper
+  [resolved] (rename sweep discipline). EVAL-023 — BDR-066 post-merge ronde
+  found 5 edge gaps [done] (plan a ronde here too). EVAL-026 — 3-way plan
+  challenge caught 4 real BLOCKERs on its own plan [done] (run it on this
+  refactor's plan).
+- NON-BINDING: ~200 remaining headings surfaced nothing binding beyond the
+  above — BDR-067/068/069 (release/permissions), LRN-first-100 (tooling),
+  BLK-005..017 (env) — counted, not detailed.
+- SELECTION: scanned ~230 headings — surfaced 28 = in-force 22 + seen 3 +
+  non-binding (counted).

.claude/tasks/plans/2026-07-19-model-tiering-v2-plan.md

@@ -0,0 +1,295 @@
+# PLAN: model-tiering v2 — full framework re-tier + splits
+
+Input: `.claude/tasks/plans/2026-07-19-model-tiering-v2-analysis.md` (read it
+first — consumer map, test locks, LRN/BDR constraints live there).
+User arbitrage (2026-07-19): 7 recos approved + no-inherit/fable-pin amendment
++ Fable scope = REFLECTION / ORCHESTRATION / PLANNING / LOGIC only.
+
+## D0 — DOCTRINE (end state)
+
+1. Main loop (session model, gated big by model-gate) keeps ONLY: brainstorm,
+   plan, contract, loop decisions, gate arbitration, human interaction,
+   conversation-context work (capitalize), trivial glue bash (<~1k tokens).
+   Retention criteria (any suffices): interactive | needs conversation context
+   | orchestration decision | dispatch overhead > step cost.
+2. NOTHING dispatched inherits. Typed agents: frontmatter pin. Built-ins
+   (general-purpose/Explore/Plan): explicit `model=` at EVERY call site.
+   VERIFIED (2026-07-19 spike, closes robustness BLOCKER): `model: "fable"`
+   on a dispatch resolves to claude-fable-5 at runtime (echo spike via
+   general-purpose); the harness enum-validates the `model` param — an
+   invalid value fails LOUDLY (InputValidationError), no silent fallback.
+   Call-site `model=` takes precedence over a typed agent's frontmatter pin
+   (documented Agent-tool contract); fallback direction if a call site omits
+   it = the frontmatter pin, i.e. today's behavior — fail-safe, never worse.
+3. Tiers: fable = dispatched reflection-on-behalf-of-main-loop (skill-runner
+   children ONLY); opus = deep judgment (audit scoring, plan critique, drift
+   semantics, review, synthesis); sonnet = standard execution from closed
+   instructions + collectors AND probes (wave-1 prudence — robustness MAJOR:
+   plugin PHASE 1 is a ~26-call branching bash chain, not a short probe);
+   haiku = status-reporter ONLY in wave 1; haiku expansion = wave 2 after
+   reliability proven per candidate.
+4. Grammars/sentinels/valves survive VERBATIM (list in analysis §CONSTRAINTS).
+   Loops/gates stay in main loop (BDR-050/LRN-083). Fix-bundle → L1 apply
+   (BDR-061) preserved: audit agents never get the Agent tool.
+5. Every split: LRN-126 data-flow pass (enumerate child-read fields vs
+   parent-set; explicit handoff contract on disk or in prompt) PLUS an
+   IN-WAVE planted-input smoke proving the fields cross the dispatch boundary
+   at runtime — the smoke GATES that wave's merge (confirmation MAJOR:
+   enumeration is design-time reading; census can't catch severed wires; a
+   split must never reach develop empirically unproven). Every change:
+   LRN-113 whole-surface sweep + census lock + flip-test (LRN-096, no `\n` in
+   patterns LRN-093, strict YAML G3).
+
+## D1 — AGENT END STATE
+
+Pins (frontmatter):
+- opus: analyzer, plan-challenger, seo-judge*, geo-judge*, doc-auditor*,
+  plugin-reasoner*, handover-synthesizer* (*new, from splits)
+- sonnet: feater, bugfixer, hotfixer, code-cleaner, refactorer, verifier,
+  security-auditor, scaffolder (effort high), onboarder, release-executor,
+  commit-changer, doc-syncer (patcher half), validator-analyzer (TIER-DOWN
+  from opus), seo-worker*, geo-worker* (2-way split per domain — simplicity
+  MAJOR: collector+templater both sonnet in wave 1 → one worker file with
+  `MODE: collect | template`, no cross-domain share: domain bodies genuinely
+  diverge), handover-renderer* (renamed handover-doc-writer render half),
+  plugin-probe* (wave-1 prudence; haiku candidate wave 2)
+- haiku: status-reporter (only)
+- none (inline-only, main loop, gate-protected): interviewer,
+  client-handover-writer
+Per-dispatch `model=` overrides (no new file): commit-changer propose=opus /
+apply=sonnet (2 sites in /commit-change — precedence over the sonnet
+frontmatter pin is the documented Agent-tool contract, verified direction
+D0.2; the pin stays as the no-inherit fallback = today's behavior; both
+call-site strings census-locked + W3 behavioral smoke); SDD
+implementers+reviewers
+sonnet (already prose-mandated → make it a census lock); code-review steps
+(ship-feature 6, init-project 10) = opus explicit; client-handover-writer's 8
+general-purpose skill-runners = fable; onboard's 7 general-purpose = opus
+(keep); any Explore/Plan ad-hoc reflection dispatch = fable (doctrine line in
+model-gate.md + CLAUDE.global routing note).
+
+Splits (each = new agent file(s) + handoff contract + census + consumers):
+S1 plugin-advisor → plugin-probe (SONNET wave 1; PHASE 1 CLI probes → PROBE
+   REPORT) + plugin-reasoner (opus; PHASE 2/2.5 scoring + reco → PLUGIN CHECK
+   block). PHASE 3-4 report+apply-gate HOISTED into ONE shared include
+   `lib/plugin-gate.md` (simplicity MINOR — doc-commit.md ×6 pattern, never
+   4 hand-copies), referenced by the 4 consumers (plugin-check, onboard
+   STEP 0, init-project STEP 0, ship-feature STEP 0) — main loop. The
+   pre-recommendation validation checkpoint (advisor :201-212, straddles the
+   seam, can skip PHASE 4) runs IN THE CONSUMER between the two dispatches
+   (correctness MINOR); its inputs (toggle-external availability,
+   project-signal presence) are PROBE REPORT fields. Handoff: PROBE REPORT
+   fields = plugin list, toggle state, profile, CLI/anim/monorepo/embedded
+   signals + checkpoint inputs (enumerate ALL PHASE-2-read fields).
+S2 doc-syncer → doc-auditor (opus; STEP 3-4 drift + semantic analysis + A3
+   MINOR/SIGNIFICANT call w/ doc-shape.sh oracle → DRIFT REPORT [AUTO]/
+   [HUMAN] items) + doc-syncer (sonnet; render/patch half, keeps
+   PATCHED_FILES: grammar + BDR-022 bans). Validation gate stays in
+   DISPATCHER (/doc skill, orchestrator steps) — auto-mode flows: auditor →
+   dispatcher applies AUTO via doc-syncer → SIGNIFICANT escalates inline.
+   Consumers rerouted: /doc, onboard, + doc-commit steps in bugfix/hotfix/
+   feat/init-project(×2)/ship-feature (inline→dispatch conversion) +
+   scaffolder PHASE 6 (scaffolder DISPATCHES nothing — it has no Agent tool:
+   README bootstrap moves to init-project STEP 5b dispatch of doc-syncer).
+   PLUS (robustness MAJOR): rework `lib/doc-commit.md`'s in-thread contract
+   BEFORE converting any doc-commit site — it requires the orchestrator to
+   "hold the patch context" to compose the rc-0 CHANGE SUMMARY (the review
+   surface that replaced the removed MINOR gate). Dispatched doc-syncer adds
+   a `CHANGE SUMMARY` block to its report grammar (per patched file: what
+   changed and why, ≤1 line each); doc-commit.md's composer consumes THAT
+   instead of in-thread context; census-locks the new field + a planted-input
+   smoke proves the summary crosses the dispatch boundary.
+S3 seo-analyzer → 2-WAY (simplicity MAJOR — 3-way was YAGNI while collector
+   and templater share the sonnet tier; commit-changer mode-precedent):
+   seo-worker (sonnet; `MODE: collect` = STEP 2-5 signals → SIGNALS file;
+   `MODE: template` = STEP 12-14 FIX BUNDLE + sentinel + SEO.md + envelope)
+   + seo-judge (opus; STEP 6-11 sampling judgment, competitive, scoring /20,
+   trajectory, triage → FINDINGS+PLAN). Orchestrated by /seo at L1 (BDR-061
+   conserved: no Agent tool in either). Wave-2 option: carve `MODE: collect`
+   into a haiku file once proven — the mode boundary IS the future cut line.
+   HANDOFF (robustness MAJOR — freshness/atomicity): run-scoped paths
+   `.audit/seo-signals-<RUNID>.md` / `.audit/geo-signals-<RUNID>.md` —
+   `.audit/` is the GITIGNORED derived-artifact tree (confirmation MINOR,
+   LRN-124: a crash-stranded transient with scraped GSC/competitor content
+   must never be committable; `.claude/audits/` keeps only the SEO.md/GEO.md
+   deliverables). RUNID minted by the dispatcher per run, passed to every
+   stage; the file ENDS with `COLLECTION COMPLETE — RUNID: <id>` and the
+   judge FAILS CLOSED (report ERROR, never score) if the file is absent,
+   RUNID mismatches, or the completeness sentinel is missing; dispatcher
+   cleans the file post-run.
+   DISPATCHER CONTRACT (confirmation MAJOR — fail-closed at the judge must
+   not fail OPEN at the pipeline): on a judge ERROR the orchestrator
+   (/seo /geo /harden /onboard) STOPS — no template dispatch, no L1 apply —
+   surfaces the ERROR verbatim, retries ONCE with a fresh collect+judge,
+   then escalates to the human. A mute or ERROR judge is NEVER carried into
+   templating (verify-secure-loop discipline). This handler is part of the
+   W5 skill rewrites, census-locked.
+   Explicit field list per LRN-126 (STEP 1-2 business+tech context consumed
+   by ALL later steps — full enumeration REQUIRED before cutting).
+   seo-data.test.sh locks (fetch.sh wiring) move with the worker body —
+   update suite same commit.
+S4 geo-analyzer → geo-worker (sonnet, 2 modes) + geo-judge (opus) — mirror of
+   S3 incl. run-scoped `.audit/geo-signals-<RUNID>.md` + the same dispatcher
+   ERROR contract. No cross-domain file share:
+   seo vs geo bodies genuinely diverge (different checks, scoring blocks,
+   envelopes) — that divergence, not LRN-125, is the reason.
+S5 handover-doc-writer → handover-synthesizer (opus; STEP 9 memory-registry
+   load + STEP 10 phase clustering + STEP 12 6-chapter synthesis — STEP 9
+   allocated here, it feeds the synthesis; correctness MINOR) +
+   handover-renderer (sonnet; STEP 13-16 annex render, precheck apply,
+   deterministic gates, HTML/PDF). client-handover-writer dispatches
+   synthesizer then renderer; PACKAGE contract split per LRN-126
+   (re-enumerate DEPLOY_HINTS/--skip-seo class fields — the EXACT prior
+   failure). W4 MUST same-commit relock model-routing.test.sh:52-55 (the
+   handover-doc-writer name + dispatch-string locks break on the rename;
+   "make test green per wave" D4 invariant — correctness MINOR).
+Tier-downs (no split): validator-analyzer opus→sonnet (deterministic
+   validators+tables). onboarder stays sonnet wave 1 (haiku candidate wave 2).
+   release-executor stays sonnet (NEED-DECISION valve).
+Verifier: STAYS sonnet (approved — oracle-anchored gate).
+
+## D2 — SKILL MAP (main loop = session model; every dispatch tier explicit)
+
+Gated reflection skills (model-gate kept, 15):
+- ship-feature / init-project: per the two example maps in the analysis file
+  (amendment section) + S1 gate hoist at STEP 0 + doc-commit conversions.
+- feat: scope/plan/contract/loop = main; challenge 3× plan-challenger opus;
+  feater sonnet; verifier+security sonnet; doc-commit → doc-auditor opus +
+  doc-syncer sonnet dispatch; commit via /commit-change (propose opus / apply
+  sonnet).
+- bugfix: investigation/diagnosis/contract = main (reflection); challenge
+  opus (3b); bugfixer sonnet; verifier+security sonnet; doc-commit as feat.
+- hotfix: LOCATE + guard = main (logic); challenge opus when guard fires;
+  hotfixer sonnet; security gate sonnet (revert-not-loop conserved);
+  doc-commit as feat.
+- analyze: analyzer INLINE = main loop (it IS the reflection) — unchanged.
+- code-clean: PHASE 1 audit inline = main (audit judgment feeding a human
+  gate); code-cleaner sonnet PHASE 2 (hosts refactorer inline at SAME tier —
+  LRN-125 OK); re-audit sonnet inside executor.
+- seo / geo: skill = orchestration + GATED arbitrage (main); pipeline
+  collector sonnet → judge opus → templater sonnet (L1 serial); appliers
+  hotfixer/feater sonnet at L1; build-verify inline.
+- web-validate: validator-analyzer sonnet; hotfixer applier sonnet; loop main.
+- harden: audit dispatch follows S3 narrow-scope path (seo-judge opus on
+  harden axes w/ collector reuse); direct-Edit apply stays inline (tiny
+  scope, BDR-061 carve-out conserved).
+- audit-delta: axis audits dispatched opus (delta judgment); security-auditor
+  sonnet; fix gate + markers = main.
+- tour: orchestration main; security-auditor sonnet; cleanup audit = analyzer
+  opus (or general-purpose model="opus"); fixes via sonnet appliers; doc axis
+  → S2 pipeline; reconcile axis = deterministic bash (main).
+- onboard: onboarder DISPATCHED sonnet (was inline); plugin S1 pipeline;
+  analyzer opus; general-purpose audits model="opus" (kept); seo/geo → S3/S4
+  pipelines; security-auditor + doc pipeline as above; synthesis
+  general-purpose model="opus"; backlog arbitration = main.
+- client-handover: writer INLINE (orchestrator, main); its 8 skill-runner
+  children model="fable"; handover S5 split (synth opus → render sonnet);
+  gates all main.
+Excluded-from-gate skills (5, stay ungated): commit-change (propose opus /
+  apply sonnet via model=; approval gates main); doc (S2: auditor opus →
+  gate main → patcher sonnet); status (haiku); release-candidate (executor
+  sonnet; version/when/push decisions main); refactor (refactorer sonnet).
+Memory/util skills (capitalize, close, prune-memory, reconcile, learn,
+  profile, skills-perso, gitflow, deploy, plugin-check(S1), status): main
+  loop by nature (conversation context, human gates, deterministic bash) —
+  no dispatch changes except plugin-check S1.
+External/gstack skills (graphify, design-*, review, qa, ship, investigate…):
+  NOT edited (external ownership, BDR-015 class) — covered by doctrine line;
+  local wrapper skills only if locally owned. Verify ownership per file
+  before touching (symlink → skip).
+
+## D3 — WAVES (each = gitflow feature branch, tests green, census extended)
+
+W0 SEQUENCING: merge `feature/opus-pin-audit-agents` → develop (baseline,
+   human gate). `bugfix/seo-geo-integrity` is ALREADY MERGED (correctness
+   MAJOR — the TODO.md "UNMERGED" note was stale; verified `92301fe` is an
+   ancestor of develop AND this branch): no arbitrage, no W5 wait — one-line
+   ancestry re-check in W0 + fix the stale TODO.md entry (reconcile-class
+   correction). Absorb the analysis+plan files into the new feature branch.
+W1 NO-INHERIT ENFORCEMENT (small, high-value): code-review model= opus
+   (ship-feature 6, init-project 10); client-handover-writer 8× model="fable";
+   doctrine line in model-gate.md + census locks (`model="fable"`,
+   `model=` presence per site); SDD sonnet prose → census lock. Prose sweep
+   of stale BDR-066/076 claims touched by W1.
+W2 INLINE→DISPATCH CONVERSIONS: scaffolder (init 5 — liveness pings move to
+   orchestrator; scaffolder loses PHASE 6 inline-load → init 5b owns README
+   via S2), onboarder (onboard), doc-commit steps ×5 flows → S2 pipeline
+   (gate hoist FIRST: /doc + flows own the validation gate; doc-syncer body
+   loses its inline gate → census re-lock), S1 plugin split + gate hoist ×4
+   consumers. Data-flow pass per LRN-126 on each (fields enumerated in the
+   wave's contract file before edits).
+W3 TIER MOVES: validator-analyzer → sonnet (pin + prose + census flip);
+   commit-changer per-mode model= (2 sites + prose + census).
+W4 S5 handover split (synth opus / render sonnet) + PACKAGE re-enumeration.
+W5 S3/S4 seo/geo pipelines: worker(2-mode)/judge ×2, /seo /geo /harden
+   /onboard rerouted, seo-data.test.sh moved locks, run-scoped signals
+   handoff (RUNID + completeness sentinel + fail-closed judge),
+   envelope/sentinel/score grammars verbatim, COVERAGE lines preserved.
+W6 DOCTRINE + CLOSE-OUT: model-gate.md rewrite (protects main loop; tier
+   table; fable-dispatch doctrine), challenge-plan.md + plan-challenger
+   ORCHESTRATOR PROTOCOL text (keep BDR-066+BDR-076 tokens per census, add
+   BDR-077), census consolidation (model-routing new sections; every new
+   agent: YAML G3, pin lock, dispatch-string lock, AskUserQuestion/Agent
+   bans), LRN-113 whole-surface prose sweep (~30 refs list in analysis),
+   BDR-077 + LRN entries + journal, EVAL-023-style post-merge ronde.
+   Per-split planted-input smokes run IN their own waves (W2/W4/W5, merge
+   gates) — W6 is the consolidated ronde only, never the first empirical
+   proof of a split.
+
+## D4 — ZERO-REGRESSION PROTOCOL (every wave)
+
+- Before edits: wave contract file (.claude/tasks/contracts/) with FILE SCOPE
+  + acceptance criteria; challenge-plan on THIS plan (done once, below);
+  verify-secure-loop on each wave's diff (verifier sonnet + security sonnet).
+- Grammar diff-guard: `grep -F` each verbatim marker (analysis §CONSTRAINTS
+  list) pre/post per wave — zero drift.
+- Census: flip-test every NEW lock (plant violation → RED) before trusting.
+- `make test` green per wave; no wave merges without human signal (gitflow).
+- Rollback story (robustness MINOR — waves are textually interdependent, an
+  early wave is NOT independently revertible after later merges): revert in
+  REVERSE merge order, or revert the whole stack; never a mid-stack single
+  revert. Pre-merge, the rollback unit is the wave branch.
+
+## CHALLENGE LOG (2026-07-19 — 3 blind lenses on plan v1)
+
+- correctness: CONCERNS(2) — seo-geo-integrity phantom sequencing (fixed W0);
+  commit-changer precedence ambiguity (fixed D1 + D0.2 citation + W3 smoke);
+  3 MINORs (S5 STEP 9 + W4 relock; plugin checkpoint seam; templater label)
+  — all fixed in place.
+- robustness: FATAL(4) — BLOCKER fable-dispatch unverified → CLOSED by spike
+  (D0.2: resolves to claude-fable-5, enum-validated, loud failure); doc-commit
+  in-thread contract (fixed S2: CHANGE SUMMARY crosses the report grammar);
+  plugin-probe haiku contradiction (fixed: sonnet wave 1); signals handoff
+  freshness (fixed S3: RUNID + sentinel + fail-closed); rollback claim
+  (fixed D4).
+- simplicity: CONCERNS(1) — 3-way seo/geo YAGNI → 2-way worker/judge (fixed
+  S3/S4); twin-templater share (dissolved by 2-way; divergence stated);
+  plugin gate ×4 copies → lib/plugin-gate.md include (fixed S1).
+## EXECUTION NOTES (2026-07-19 — as-built deviations, all justified in-commit)
+
+- S2/S3/S4/S5 shipped MODE-BASED (one agent, modes + call-site `model=`)
+  instead of file splits — the challenge's own commit-changer precedent
+  generalized; locks and body text stayed in place (LRN-137). plugin S1
+  kept the `plugin-advisor` NAME for the reasoner (repinned opus) — only
+  plugin-probe is a new file.
+- seo/geo keep the OPUS pin (not sonnet+judge-override): fail-safe
+  direction — a forgotten override over-tiers, never downgrades. /harden
+  narrow-scope + /onboard report-only keep legacy no-MODE single-shot on
+  that pin.
+- W0's seo-geo-integrity arbitrage was phantom (branch already merged) —
+  TODO.md corrected instead.
+- Per-wave smokes ran in-wave as merge gates (confirmation-pass fix) —
+  all PASSED, disk-verified. Registry note: a NEW subagent_type registers
+  at next session start; typed resolution re-checked post-restart before
+  the W2 merge.
+
+## CHALLENGE LOG (final)
+
+- Confirmation pass (fresh robustness challenger on v2): CONCERNS(2) — v1
+  fixes HOLD (doc-commit CHANGE SUMMARY, plugin-probe sonnet, rollback order,
+  fable spike, RUNID); 2 new MAJORs + 1 MINOR opened by the revisions, all
+  fixed in v3: (a) per-split planted-input smokes moved IN-WAVE as merge
+  gates (W6 = ronde only); (b) dispatcher ERROR contract on judge failure
+  (STOP, no templating/apply, retry once, escalate — pipeline never fails
+  open); (c) transient signals files relocated to gitignored `.audit/`
+  (LRN-124). Protocol cap reached (1 re-challenge) → to the human gate.

.claude/tasks/plans/2026-07-30-opus5-config-tuning-1238.md

@@ -0,0 +1,255 @@
+# PLAN — Adapt claude-config for the Claude 5 family (Opus 5 focus)
+
+Date: 2026-07-30 · Branch (planned): feature/opus5-config-tuning (off develop)
+KIND: build-plan · Author: main-loop session (Fable 5)
+
+## 1. Context & evidence
+
+Opus 5 (`claude-opus-5`, released 2026-07-24) now backs every `model: opus`
+agent pin in this repo (analyzer, plan-challenger, seo/geo-analyzer,
+plugin-advisor — BDR-076/077) and any session the user switches to via
+`/model opus`. Its documented behavioral profile differs from Opus 4.8 in
+ways that make parts of this config counterproductive:
+
+- E1 **Over-delegation**: Opus 5 "delegates to subagents more readily than
+  prior models" (official prompting guide). Opus 4.8 had the OPPOSITE trait
+  (LRN-030), and `CLAUDE.global.md:43-47` was written to counter it
+  ("Counters model tendency to under-delegate"). The premise is inverted.
+- E2 **Anti-delegation already injected by the harness**: Claude Code
+  v2.1.219 server-gates an Opus-5-only prompt section (`heron_brook` +
+  `subagent_steer_delegation`, GitHub issue #80988) that says "Do not call
+  the AgentTool unless the user requested it" and "Subagents multiply cost
+  and time…". Stacking our own hard cap on top would triple-constrain;
+  keeping a pro-delegation nudge would fight the injection. Model-neutral
+  when-guidance is the stable middle.
+- E3 **Over-verification**: official guidance — "If your prompt contains
+  explicit verification instructions … remove them: instructions like these
+  cause over-verification on Claude Opus 5, and removing them reduces wasted
+  tokens with no loss in quality." Also true of per-prompt "double-check"
+  phrasing. Targets PROSE told to the model, not harness-level gates.
+- E4 **Scope expansion**: named Opus 5 regression ("can expand the scope of
+  a task, adding steps that weren't requested"). Anthropic ships a literal
+  counter-block; tested to reduce scope changes "to nearly zero".
+- E5 **Literal instruction following** (since 4.7, stronger now): aggressive
+  MUST/CRITICAL language over-triggers; conservative-reporting instructions
+  ("only report high-severity") measurably depress recall in review/challenge
+  harnesses.
+- E6 **Longer written deliverables**: files written to disk run ~30-40%
+  longer; `effort` does NOT control visible/deliverable length — only prose
+  instructions do.
+- E7 **Overconstraint costs reasoning**: Anthropic removed >80% of Claude
+  Code's system prompt for Claude-5-generation models "with no measurable
+  loss"; named mechanism = tokens burned resolving conflicting rules.
+- E8 **Hook false positive (today)**: `\bux\b` in
+  `hooks/design-toolchain-reminder.sh:47` fired on French prose ("changement
+  ux vu" — matches after apostrophe/slash/space); 2nd `ux` FP in the log,
+  both French. Continues the LRN-1005/1007 false-positive series. No test
+  row covers `\bui\b`/`\bux\b`.
+- E9 **Effort carry-over trap**: Opus 5 has no model-default effort hold in
+  Claude Code — a persisted `xhigh` (our `settings.json:333`) silently
+  carries onto Opus 5 sessions, against Anthropic's "start at high, sweep
+  low/medium" guidance for that model.
+
+## 2. Design decisions
+
+- D1 The global instruction layer must be MODEL-NEUTRAL across the Claude 5
+  family (sessions run Fable 5 by default; dispatched judgment agents run
+  Opus 5; executors Sonnet). Fixes therefore express WHEN-guidance and
+  outcome bars, not directional compensation for one model's trait.
+- D2 Harness-level quality gates (fresh blind verifier + security-auditor,
+  BDR-049/050; plan-challenge, BDR-075) are architecture, not model
+  self-check prompting. They stay. E3 applies only to prose that tells the
+  MODEL to verify its own work.
+- D3 Per BDR-021, the Security and Architecture-decisions sections of
+  CLAUDE.global.md stay verbatim (deliberate policy). No softening there.
+- D4 Registries are append-only: LRN-030 is not edited; a new LRN records
+  the trait inversion and points back to it.
+- D5 Deterministic backstops (gitflow pre-commit, Gitea protection,
+  permissions.deny, rtk pinning) are explicitly out of "more freedom" scope
+  — community reports show Opus 5 working AROUND soft controls, which argues
+  for keeping hard ones.
+
+## 3. Work items
+
+### W1 — CLAUDE.global.md: rewrite the delegation block (:43-47)
+Replace the 5-line block (incl. "Default to delegation for multi-file
+exploration. Counters model tendency to under-delegate.") with model-neutral
+when-guidance, same footprint (≤5 lines):
+
+```
+- Sub-agents: one task per sub-agent, main context stays clean.
+  Delegate genuinely independent, sizeable tracks (wide multi-file
+  exploration, parallel audits) — not work doable in a few tool
+  calls, and not self-verification (harness gates own that). Brief
+  precisely, then commit to the delegation — don't redo its work.
+```
+Rationale: E1+E2. No hard spawn cap in prose (harness already injects one on
+Opus 5; Fable benefits from delegation).
+
+### W2 — CLAUDE.global.md: reframe "After code changes" (:75-83)
+Keep the concrete quality bar; drop the proof-mandate/self-check phrasing
+(E3). Replace steps 2-4 with faithful-outcome reporting:
+
+```
+## After code changes
+1. Run tests, lint, build, type-check if available.
+2. Report outcomes faithfully: what passed, what wasn't run,
+   remaining risks, surviving deviations. Completion claims only
+   for verified work.
+3. Correction or notable event → capitalize to right registry.
+```
+Net: -2 lines. "Would staff engineer approve?" bar and "Don't mark complete
+without proof" are removed as self-check choreography; honest-reporting
+line preserves the intent (grounded completion claims) without mandating an
+extra verification pass.
+
+### W3 — CLAUDE.global.md: add scope fence (Workflow section)
+Append (adapted from Anthropic's tested block, caveman-compressed, ~5 lines):
+
+```
+- Scope: deliver what was asked, at the scope intended. Routine
+  judgment calls → decide alone; materially different readings →
+  ask. Better approach spotted → say so in one line, still do the
+  task as asked. Finish the whole task; genuinely blocked → do the
+  rest, state plainly what's missing.
+```
+Rationale: E4. Complements existing "Scope changes to task — no unrelated
+edits" (line ~15) without contradicting it.
+
+### W4 — CLAUDE.global.md: add deliverable-length rule (Code style / Comments area)
+~2 lines:
+
+```
+- Written deliverables (docs, reports, .md): length matched to what
+  the task needs — no filler sections, no boilerplate summaries.
+```
+Rationale: E6. Registries already covered by caveman rule.
+
+### W5 — Line budget
+After W1-W4: expected ~309 lines. Hard check: `wc -l CLAUDE.global.md` ≤ 320
+(session-start.sh warning threshold at :202-213).
+
+### W6 — hooks/design-toolchain-reminder.sh: drop `\bui\b` and `\bux\b`
+- Remove the two 2-char alternatives from the pattern at :47. Keep
+  `ui/ux|ux/ui|ui kit` and all other tokens.
+- Add a dated header comment (3rd tightening pass, 2026-07-30, cites the
+  two French-prose `ux` FPs; series LRN-1005/1007).
+- Trade-off accepted: a bare "améliore l'ux" prompt with no other design
+  token goes quiet — the CLAUDE.global.md "Design work" section still
+  routes it (the hook is a belt, self-described soft nudge).
+- Update `lib/tests/design-toolchain-reminder.test.sh`: add 2 quiet rows
+  (the real FP prompt excerpt; a bare "l'ui" French sentence) — flip-tested
+  per LRN-096. Existing 9 must-fire rows unaffected (none uses ui/ux).
+
+### W7 — agents/plan-challenger.md: coverage-first reporting line
+Add one clause to the findings rules (add-only, no removal): uncertain or
+low-severity findings are REPORTED with an explicit confidence + severity
+tag rather than self-censored — severity filtering happens in the
+orchestrator's synthesis, not in the challenger. Rationale: E5 (literal
+Opus 5 + "manufactured concern is a failure" wording risks suppressing real
+low-confidence findings). Must not touch: verdict grammar, MANDATORY PROOF
+clause, blind-dispatch rules (test-locked in plan-challenger.test.sh).
+
+### W8 — Memory + docs capitalization (same branch, follows the work)
+- decisions.md: new BDR (config adapted for Claude 5 family — scope,
+  rationale, alternatives incl. "leave config as-is" and "hard spawn caps"
+  rejected).
+- learnings.md: new LRN — Opus 5 behavioral profile (over-delegation
+  inverts LRN-030's Opus 4.8 trait; over-verification; literal following;
+  no effort hold on Opus 5 in Claude Code; heron_brook/#80988 injection).
+- journal.md: one line.
+- CHANGELOG.md: entry under Unreleased.
+
+### W9 — Gates (before commit)
+- `shellcheck hooks/design-toolchain-reminder.sh` clean.
+- Manual flip-test of the hook: FP prompt → quiet; "redesign the navbar" →
+  fires.
+- `make test` full suite green (design-toolchain-reminder.test.sh,
+  plan-challenger.test.sh, model-routing.test.sh untouched-but-must-pass,
+  curated-config-guard, loops-light…).
+- `wc -l CLAUDE.global.md` ≤ 320.
+
+### W10 — Gitflow
+`bash ~/.claude/lib/gitflow.sh start feature opus5-config-tuning` off
+develop; atomic commits (hook+test / CLAUDE.global.md / agent / memory+docs);
+NO `gitflow finish` — merge only on explicit human signal.
+
+## 4. Explicitly NOT doing (considered, rejected)
+
+- N1 Touching lib/verify-secure-loop.md or the fresh-verifier/security
+  gates: harness architecture (BDR-049/050, D2), verifies SONNET executor
+  output — not Opus 5 self-check prose.
+- N2 Softening the Security / Architecture sections (BDR-021, D3).
+- N3 Editing the superpowers plugin's "1% chance → MUST invoke" language:
+  external upstream code; flagged as residual over-triggering risk in the
+  new LRN, revisit as its own decision if observed.
+- N4 Changing `settings.json` `effortLevel: "xhigh"`: user preference,
+  optimal for the Fable 5 session default; the Opus 5 carry-over trap (E9)
+  is documented in the LRN + surfaced to the user for a manual decision.
+- N5 De-prescribing seo-analyzer.md / geo-analyzer.md (1528/1106 lines,
+  heavy MUST density): separate project, backlog note in TODO.md.
+- N6 Removing or session-gating the design/ctx7 reminder hooks: soft
+  nudges, cheap, deliberately built; tightened only (W6).
+- N7 Any model pin change: `model: opus` pins now resolve to Opus 5 —
+  desired outcome, census (model-routing.test.sh) untouched.
+- N8 Committing settings.json for any reason (LRN-098/1049 /model-churn
+  trap): file is currently clean; keep it out of every commit.
+
+## 5bis. CHALLENGE SYNTHESIS (2026-07-30) — FINAL amendments (v2)
+
+Verdicts: correctness CONCERNS(4) · robustness FATAL(5, 1 BLOCKER) ·
+simplicity CONCERNS(4). Every fix below is the challenger's own named FIX,
+adopted as written. No re-challenge pass: scope narrowed, no new dependency;
+W0 is an execution-time safety procedure, not a new config mechanism.
+
+- **W0 (NEW — robustness BLOCKER)**: all edited surfaces are symlink-deployed
+  LIVE (~/.claude/CLAUDE.md, hooks/, agents/ → this repo); edits take effect
+  machine-wide at save time, before any W9 gate. Mitigations:
+  (a) `gitflow start` BEFORE any live-file edit; never checkout develop
+  mid-work; (b) hook regex change validated on a SCRATCH copy first
+  (bash -n + shellcheck + pattern replay), then written to the live file in
+  ONE atomic Edit; (c) named reverts: `git show develop:<file> > <file>`;
+  escape hatch = remove the hook registration block from settings.json.
+- **W1 v2** (robustness#3, correctness#2): replacement text carves out the
+  mandated gates explicitly and scopes "don't redo":
+  "Skill-mandated gates (fresh verifier/security/challenge) always dispatch
+  as written. Don't redo delegated work by hand — failed gates re-dispatch
+  fresh executors instead."
+- **W2 v2** (simplicity#2): minimal diff — delete ONLY the line
+  `Bar: "would staff engineer approve?"`. Steps 1-4 + capitalize step stay.
+- **W3 v2** (simplicity#1, robustness#4): no new bullet. Fold the only new
+  clause into the existing Deviations bullet: "Finish the whole task:
+  blocked on an independent sub-part → do the rest, state what's missing.
+  Gone WRONG → still STOP, re-plan." (net +2 lines, no conflict with :53).
+- **W4**: unchanged (+2 lines). Budget v2: 304 +1 −1 +2 +2 = 308 ≤ 320.
+- **W6 v2** (all lenses): drop `\bux\b` ONLY — keep `\bui\b` (zero evidenced
+  FP; one logged true positive). Accepted trade-off: the 2026-07-21 "ameliore
+  le tutoriel…gamifier" ux row (plausible TP) goes quiet; CLAUDE.global.md
+  design-routing section remains the router. Header comment notes the log
+  records `head -1` only → per-token FP rate not fully derivable. Tests:
+  quiet row = synthetic "changement ux vu…" (verified matches pre-change →
+  flips); must-fire row = "revois l'ui du panneau admin" (locks `\bui\b`;
+  apostrophe escaped correctly, doubles as JSON-path control per
+  robustness#7). No log-excerpt rows (vacuous — 100-char truncation).
+- **W7 v2** (all lenses): in-place reword of the `:82-83` sentence (NOT
+  test-locked; plan v1 misstated that) instead of an add-only clause:
+  "No invention — ungrounded is noise. Silently dropping a grounded doubt is
+  equally a failure: file it as `[MINOR]` with the uncertainty stated in
+  `WHY:`. Nothing real at all → `SOLID` with `FINDINGS: none`."
+  OUTPUT grammar byte-identical; no confidence axis; no consumer change.
+  Census: add `has "$A" "grounded doubt"` row to plan-challenger.test.sh in
+  the same commit.
+- **W9 v2**: adds the W0 scratch-validation step; rest unchanged.
+- **W10 v2**: branch creation moves FIRST in execution order.
+
+## 5. Constraints for challengers
+
+- Registries append-only; curation only via /prune-memory.
+- Census tests lock behavior: any hook/agent edit must land with its test
+  update in the same commit; `make test` must stay green.
+- CLAUDE.global.md ≤ 320 lines (runtime warning threshold).
+- BDR-021: Security + Architecture sections verbatim.
+- Gitflow: feature branch off develop, no merge without human signal.
+- The global file serves ALL models (Fable sessions, Opus 5 dispatches,
+  Sonnet executors read skill/agent prompts instead) — no Opus-5-only
+  wording in CLAUDE.global.md.

.claude/tasks/plans/2026-07-30-seo-geo-deprescription-1402-inventory.md

@@ -0,0 +1,174 @@
+# ANNEX — directive-language inventory (analyzer report, 2026-07-30)
+
+Produced by a read-only analyzer dispatch over agents/seo-analyzer.md
+(1528 l) + agents/geo-analyzer.md (1106 l), cross-referenced against
+every consumer. Referenced by the C1 plan (same folder, -1402.md).
+
+## 0. Token census (raw)
+
+| Token family | seo-analyzer.md | geo-analyzer.md |
+|---|---|---|
+| MUST/must | 12 | 6 |
+| MANDATORY/mandatory | 8 | 4 |
+| NEVER/never | 42 | 33 |
+| ALWAYS/always | 6 | 1 |
+| CRITICAL/critical | 3 | 1 |
+| Do NOT / do not | 24 | 8 |
+| verbatim | 6 | 3 |
+| STOP | 3 | 4 |
+| refuse/REFUSE | 6 | 4 |
+| ⚠️ blocks | 0 | 0 |
+
+## 1. Test locks on these files (complete list — 6 per file)
+
+model-routing.test.sh:67-68 `model: opus` (both) · :150-157 `MODE:
+collect|judge|template` + `COLLECTION COMPLETE` (both) ·
+seo-data.test.sh:538-540 `fetch.sh crux` / `fetch.sh queries` /
+`Performance GSC` (seo) · :542-543 `fetch.sh schema_gen` /
+`fetch.sh content_quality` (geo).
+NOT locked by any test: READY-TO-APPLY sentinel, envelope headings,
+score-block shapes, JUDGE-ERROR strings, batch labels — contracts by
+consumer only; a rewrite can break them silently and make test stays
+green. Sibling dispatcher locks: model-routing.test.sh:159-166.
+Stale line-number comments (no enforcement): lib/url-guard.sh:9,
+url-guard.test.sh:20, source-scope.sh:25, seo-data/README.md:196/309,
+drift.py:4, linkgraph.py:4 — all already drifted.
+
+## 2. Format contract (artifact → consumer) — FREEZE SET
+
+seo-analyzer: signals `.audit/seo-signals-<RUNID>.md` (+clean/load sites
+in /seo) · `COLLECTION COMPLETE — RUNID: <RUNID>` terminal ·
+`COLLECT REPORT` w/ `STATUS: DONE|BLOCKED` · `SEO JUDGE — VERDICT:
+ERROR(<reason>)` · judge report forwarded verbatim to template ·
+`SEO SCORING (<depth>)` block w/ `COVERAGE SOURCE:`/`COVERAGE LIVE  :`
++ 7 axes + `SEO GLOBAL (weighted): XX.X/20` (score.py:26-37 mirrors
+weights) · `TRAJECTORY TO 17/20 (code-only)` · `fetch.sh score` JSON
+(`axes.{technical,on-page,seo-local,off-page,social,competitive,legal}`,
+severities `critique|haute|moyenne|basse`, `status:"na"`) · `FIX PLAN (N
+findings total)` + BATCH A…F (tier-mapping tolerant) · `## FIX BUNDLE
+(for dispatcher)` + `### AUTO/### GATED/### USER ACTIONS` + item fields
+`id: applier: files: concern: current: expected:` · sentinel `READY TO
+APPLY — awaiting dispatcher confirmation` (also reused by /harden:366) ·
+envelope `SEO AGENT RESULT` + `## SECTION FOR SEO.md §2…§6` + `## ENTRIES
+FOR SEO.md §0/§8/§9/§10/§11/§15` · `Automatisation possible avec:` per
+§11 entry · standalone `.claude/audits/SEO.md` w/ `**Score SEO** : XX.X
+/ 20` (client-handover-writer.md:344 labeled grep) + §0-§15 + Historique.
+geo-analyzer: same families with GEO names; envelope `GEO AGENT RESULT`
++ `## SECTION FOR SEO.md §7` (7.1-7.6); `**Score GEO** : XX.X / 20`
+(handover parses it only inside SEO.md, allow_fallback=no); G1-G7
+batches (G1-G4/G6 AUTO · G5 GATED · G7 USER). Both: STEP NUMBERS are
+addressed by dispatchers (seo: 2-5/6-11/12-14; geo: 0-5/6-12/13-15;
+also depth-matrix.md:17-19,37) — renumbering re-points dispatch prompts.
+Engine interfaces: fetch.sh verbs {crux,queries,inspect,cannibal,
+sitemap,rendercheck,linkgraph,score,schema_gen,content_quality} ·
+url-guard.sh host|url · source-scope.sh findargs|list · resources/*.md.
+
+## 3-4. Site classification counts
+
+| | seo | geo | total |
+|---|---|---|---|
+| A machine-parsed contract | ~52 | ~41 | ~93 (12 test-locked) |
+| B safety/policy invariant | ~30 | ~31 | ~61 |
+| C process choreography | ~21 | ~12 | ~33 |
+| D other/domain-fact | ~20 | ~13 | ~33 |
+
+### Class C sites — seo-analyzer.md (rewrite targets)
+:61 "First action." · :143-148 CMS-detect-before-edit ordering ·
+:208-210 "keep the two consistent" (runtime cross-file reconcile) ·
+:508 "run this BEFORE anything else in STEP 5" (ordering; the refusal
+rule itself is B) · :550-553 "Record the denominator BEFORE sampling"
+(ordering; honesty rule is B) · :602-604 "Sanity-check the grouping
+before trusting it" (self-verify) · :606-618 sampling-method essay ·
+:661-680 C1a 20-line rationale (rule itself is B at :1493-1501) ·
+:875 per-item method · :970-971 "Run it twice on the same file before
+publishing" (exact BDR-081 over-verification class) · :1147 "AUTO items
+are a commitment, not a suggestion." · :1149-1157 P0 CMS-plugin-first
+mandate · :1159-1162 P0 Bing mandate (dup of geo :777-786) · :1217 "Do
+not proceed to STEP 12 until this plan is printed." · :1260-1261 +
+:1342-1350 + :1502-1503 landing-page rule ×3 · :1309-1320 bundle
+completeness checklist (10 checkboxes self-audit) · :1504 "Preserve
+existing valid SEO." · :1522-1523 WebSearch-on-FULL extra-verify ·
+:1525-1526 "Transparency. Every automated change logged" (VESTIGIAL —
+agent applies nothing, pre-BDR-061).
+
+### Class C sites — geo-analyzer.md
+:48 "copy these patterns" · :124 "First action." + :127-139 ask-block
+(unreachable when dispatched) · :230 conditional skip · :262-269 +
+:873 + :1063-1065 PERMISSIVE default ×3 · :360 ordering · :394 "20-50
+real customer questions (P0)" · :777-786 MANDATORY AI-index submission
+(dup of seo :1159-1162) · :811 "Consolidate EVERY finding" · :823
+"Print the plan before STEP 13" · :1102-1103 WebSearch extra-verify ·
+:1106 "Every automated change logged in §14" (VESTIGIAL; §15 log is
+dispatcher's per :959).
+
+### Class B anchors (keep obligation, dedup emphasis)
+CWD/TARGET MISMATCH twins (seo :117-126 ≈ geo :173-181) · url-guard
+mandatory (seo :287-291 ≈ geo :273-277) · R2 refuse-to-score (seo
+:519-548, geo :548-557; BDR-072) · NAP direction rule (seo :801-812,
+geo :1073-1087; LRN-032-zenquality) · COVERAGE mandatory (seo
+:1110-1130, geo :725-729; LRN-133) · never-apply/L1 (BDR-061; LRN-105
+named-ban) · C1a build-output ban · no-invented-content/DGCCRF ·
+"Compute the scores, do not feel them (I7)" (BDR-073) · §14 mandatory
+disclosure lines (backlinks BDR-071, security headers I4) · honest
+llms.txt framing · cite-sources (LRN-131).
+
+## 6. Duplication map (sweep ALL twins — LRN-113)
+
+seo internal: never-apply ×4 (:1227-1234, :1352-1357, :1468-1472,
+:1527-1528) · landing-page ×3 (:1260, :1342, :1502) · shared-file
+discipline ×2 (:1254, :1486) · bundle self-containment ×2 (:1249,
+:1473) · COVERAGE ×4 (:438, :1000, :1096, :1110) · security-headers-
+not-scored ×3 (:281, :977, :994) · 30/70 ×3 (:397, :614, :1165) ·
+sentinel-verbatim ×3 (:1301, :1304, :1397).
+geo internal: PERMISSIVE ×3 · never-apply ×4 (:826-832, :842-848,
+:1031-1034, :1104-1105) · tier-mapping ×2 (:824, :850) ·
+content_quality-advisory ×2 (:584, :622) · shared-file ×2 (:858,
+:1047) · llms-honest ×2 (:337, :1066) · cite-sources ×2 (:17, :1089).
+Cross-agent twins (stay twins — both files dispatch standalone):
+CWD block · url-guard block · MODE DETECTION · MODE BOUNDARY · R2 ·
+COVERAGE · NAP rule · RULES section skeleton · C1a · automation rule ·
+Bing/AI-index action · CDN/WAF check.
+Agent↔dispatcher duplication (stays — dispatch prompt is per-run
+context, agent spec serves standalone/no-MODE paths): NAP ×4 total ·
+shared-file ×7 · security-headers ×5 · domain split · weights 80/20-
+75/25 · Historique · never-re-derive (test-locked dispatcher side).
+
+## 7. Contradictions / ambiguities found
+
+1. seo :1525-1526 + geo :1106 vestigial "automated change logged"
+   (agent applies nothing; geo :959 says dispatcher fills §15).
+2. Ask-the-user blocks unreachable in dispatched path (seo :64-75,
+   :88-112; geo :127-139, :153-168); /geo:41 states it outright.
+3. Collect boundary wording: agents "STEP 0-5 ONLY" vs /seo "STEP 2-5
+   only (context replaces STEP 0-1)" — works by prompt override.
+4. geo judge does live work (sameAs curls :477-492, web_search) unlike
+   pure-judgment seo judge — asymmetric split, by design.
+5. /harden imposes its own output contract (HARDEN.md, /100) the agent
+   spec never acknowledges; keys on "NARROW-SCOPE" in dispatch prompt.
+6. "LRN-032" cite is ambiguous in THIS repo (local LRN-032 = different
+   lesson; the NAP lesson is zenquality's registry) — keep the
+   "zenquality" qualifier wherever cited.
+7. geo :376-377 uncited FAQ-citation-rate claim vs geo :1089-1097
+   cite-sources rule (LRN-131 failure class).
+8. Score-label parse fragility: client-handover extract_score fallback
+   greps FIRST X/20 in file — losing the `Score SEO` label would
+   silently read `TRAJECTORY TO 17/20` as 17.0. (Latent, downstream.)
+9. GEO scoring has no deterministic engine (score.py covers SEO axes
+   only) — BDR-073 binds only half the pair.
+
+## 8. Binding memory (from the analyzer's read-before)
+
+IN FORCE: BDR-081 (premise) · LRN-139 (when-guidance shape) · BDR-061
+(bundle+sentinel decision) · BDR-077 (mode split, fail-closed, locks
+survive) · BDR-073 (deterministic scoring) · BDR-072 (R2 refuse) ·
+BDR-071 (off-page ceiling + §14 line) · BDR-010/LRN-011 (labeled
+scores gate) · LRN-133 (omission legible) · LRN-131/132/EVAL-025
+(WebSearch ≠ verification) · LRN-105 (named ban stays explicit) ·
+LRN-080/088 (measure before delete → dogfood) · LRN-113 (sweep whole
+surface) · LRN-093 (no vacuous locks; single-line anchors) ·
+LRN-126/137 (mode split carries data paths) · BLK-017 (Bing deferred).
+
+## 9. Open questions → dispatcher decisions (see plan §4b)
+
+Q1 freeze scope · Q2 census extension · Q3 dedup strategy ·
+Q4 vestigial lines · Q5 /harden //onboard reconciliation.

.claude/tasks/plans/2026-07-30-seo-geo-deprescription-1402.md

@@ -0,0 +1,342 @@
+# PLAN v2 — De-prescribe seo-analyzer.md + geo-analyzer.md for Opus 5
+
+Date: 2026-07-30 · Branch: feature/seo-geo-deprescription (off develop, started)
+KIND: build-plan · Author: main-loop session (Fable 5)
+Parent decision: BDR-081 N5 (deferred as separate project) · Method: LRN-139
+v2: revised after the 3-lens challenge (§5bis) — every BLOCKER closed by a
+named change; one confirmation challenger pass follows before execution.
+
+## 1. Context & evidence (v2 — sizing corrected per simplicity#1)
+
+Both agents are opus-pinned (BDR-076) → every judge phase runs Opus 5.
+BDR-081 profile applies: literal following, over-verification when told
+to verify, conflicting/duplicated rules burn reasoning tokens. These are
+the LONGEST agent files in the repo (1528 + 1106 l) with real downstream
+parsers — NOT the densest (measured: ~4.5 directive hits/100 l, ranks
+20th/22nd; security-auditor is 17/100). What this pass buys, honestly:
+(a) removal of self-output-verification demands (the one pattern the
+baseline dogfood caught live: the judge reported "run twice, identical
+output" — seo:970 firing), (b) removal of vestigial pre-BDR-061 lines
+and 2 real contradictions, (c) small same-audience/same-range dedup,
+(d) caps→when-guidance on choreography. The verification apparatus
+(census + 3-lens challenge + before/after dogfood) is USER-DIRECTED for
+this chantier, not derived from the density premise.
+
+## 2. Contract surface (v2 — split per correctness#5)
+
+### 2a. Machine-parsed (named non-LLM consumer: test, script, or literal
+grep in a dispatcher step) — byte-frozen
+- `model: opus`, `MODE: collect|judge|template`, `COLLECTION COMPLETE`
+  (model-routing.test.sh:67-68,150-157).
+- `fetch.sh crux|queries` + `Performance GSC` (seo), `fetch.sh
+  schema_gen|content_quality` (geo) (seo-data.test.sh:538-543).
+- `SEO|GEO JUDGE — VERDICT: ERROR(` — dispatcher ERROR CONTRACT
+  fail-closes on it (skills/seo:316-318, skills/geo:65-68).
+- `## FIX BUNDLE` + sentinel `READY TO APPLY — awaiting dispatcher
+  confirmation` — apply step keys on it (skills/seo:524, skills/geo:101;
+  reused by /harden:366).
+- `.audit/<seo|geo>-signals-<RUNID>.md` names + fail-closed load.
+- STEP numbering: dispatchers address ranges literally (seo 2-5/6-11/
+  12-14; geo 0-5/6-12/13-15; depth-matrix:17-19,37).
+- `**Score SEO** : XX.X / 20` / `**Score GEO** : XX.X / 20` labels —
+  client-handover-writer.md:344-345 labeled grep (BDR-010/LRN-011);
+  losing the SEO label silently falls back to first-X/20-in-file.
+- Bundle item fields `id: applier: files: current: expected:` — pasted
+  verbatim into hotfixer/feater at L1; `applier: bash` run in-loop.
+- url-guard call sites: seo-analyzer.md:287-295, geo-analyzer.md:273-280
+  (NOT ":257" as v1 said — robustness#5) + sitemap-URL guard seo:573-582.
+- `NARROW-SCOPE` keying of the I4 carve-out (seo:981-983) — /harden's
+  dispatch prompt relies on it.
+
+### 2b. LLM-convention contracts (no code consumer; the dispatcher LLM
+merges by these shapes) — locked in the census, still frozen
+`SEO|GEO AGENT RESULT` envelopes · `## SECTION FOR SEO.md §N` ·
+`## ENTRIES FOR SEO.md` · `SEO|GEO SCORING (` blocks + `COVERAGE
+SOURCE`/`COVERAGE LIVE` lines + `GLOBAL (weighted)` · `TRAJECTORY TO
+17/20 (code-only)` · `FIX PLAN (` (seo) · batch labels A-F / G1-G7
+(tier recognition tolerant, labels nominal) · `COLLECT REPORT` +
+`STATUS: DONE|BLOCKED` · `Automatisation possible avec:` · §0-§15
+report skeleton + Historique. CROSS-AGENT NOTES emit-instruction lives
+in /seo's dispatch prompts (dispatcher-side lock only).
+
+## 3. Class B invariants — obligation kept, single strongest statement;
+security ORDERINGS byte-frozen (robustness#5/#7)
+
+- Guard-first orderings, frozen verbatim: seo:287-291 / geo:273-277
+  ("Guard the domain before it reaches a shell… Run the guard FIRST…
+  never 'clean up' the value and retry") + seo:573-582 URL loop.
+- seo:550 "Record the denominator BEFORE sampling" — the ordering IS
+  the honesty mechanism (a post-hoc denominator is self-serving);
+  frozen; only surrounding prose may compress.
+- NAP direction rule (LRN-032-zenquality — keep the qualifier, the bare
+  ID is ambiguous in this repo), R2 refuse-to-score (BDR-072), COVERAGE
+  obligations (LRN-133 — note :436-439 is a DISTINCT index-reach
+  obligation, not a repeat), §14 mandatory disclosure lines (BDR-071
+  backlinks verbatim line, I4 security-headers), never-apply/L1
+  (BDR-061; LRN-105 named ban), C1a build-output ban, no-invented-
+  content/DGCCRF, deterministic scoring (BDR-073), fail-closed judge,
+  shared-file Edit-not-Write discipline, honest llms.txt framing,
+  cite-sources (LRN-131).
+- External-freshness checks are NOT self-verification (robustness#6):
+  seo:1522-1523 + geo:1102-1103 verify a DRIFTING WORLD feeding an
+  AUTO-tier robots.txt edit — kept, reworded as when-guidance ("crawler
+  lists shift; cross-check before emitting G1 from the dated resource").
+
+## 4. Work items v2
+
+- P0 SEQUENCING + LIVE-TREE EXPOSURE (robustness#4, conf#2/#3/#4/#9):
+  agents/ resolves through ~/.claude symlinks to the WORKING TREE —
+  edits are live between Edit calls, before any commit. Rules:
+  (1) the FULL baseline completes before the first agent edit —
+  signals + judge reports + TEMPLATE envelopes + merged SEO.md +
+  HUMAN-ACTIONS.md (conf#2: without frozen template artifacts the
+  template-range edits would have no differential and P0 makes one
+  unobtainable later);
+  (2) all baseline artifacts copied to the DURABLE, gitignored
+  `.audit/dogfood-baseline/` in this repo before the first edit
+  (conf#9: the session scratchpad dies with the session/reboot;
+  LRN-124: .audit/** is never committed);
+  (3) freeze window: no /seo //geo //harden //onboard AND no
+  /client-handover (spawns /seo — conf#3) nor any skill transitively
+  dispatching either analyzer, in ANY project, until the after-dogfood
+  verdict;
+  (4) aborts (conf#4): mid-reword interrupt or after-dogfood failure →
+  `git checkout HEAD -- agents/seo-analyzer.md agents/geo-analyzer.md`
+  (in-flight revert, index-safe); `git checkout develop -- agents/…`
+  is reserved for a WHOLE-BRANCH abandon; after an abort the named
+  exit is either (a) fix + re-run the after-dogfood, or (b) present
+  the static evidence (census + git diff review) to the human who may
+  accept or abandon at the gate — no open-ended reverted state.
+- P1 CENSUS (commit 1, test-only, green pre-reword — compatible with
+  §7's same-commit rule: it locks EXISTING state and changes no agent
+  file; reword commits carry any census DELTA): DONE in working tree —
+  lib/tests/seo-geo-contract.test.sh 54/0, shellcheck clean, real
+  flip-test run: 7 scratch mutations → 7 FAILs (not "by construction" —
+  robustness#10). File-qualified locks (correctness#4): `FIX PLAN (` +
+  `applier: bash` + `Score SEO` seo-only; `Score GEO` geo-only.
+  Incidental locks dropped (CROSS-AGENT NOTE agent-side, bare
+  `applier:`). Item fields locked both files. v3 (conf#5): EVERY
+  `## STEP n —` header locked, interiors included (seo 0-14, geo 0-15)
+  — census now 71/0. Freeze mechanism for the
+  ~40 A-sites the census does not cover: reviewed `git diff -U0
+  agents/*.md` on each reword commit (simplicity#4).
+- P2 REWORD seo-analyzer.md (commit 2):
+  (a) Self-OUTPUT verification, v3 (conf#1/#8 — neither is deleted
+      outright): :970-971 "run it twice" → when-guidance integrity
+      guard ("if the findings JSON changed after scoring, re-run and
+      explain the move" — score.py is deterministic, so a moving
+      output means mutated findings: anti-score-shopping, BDR-073;
+      the unconditional double-run the baseline judge burned goes
+      away, the guard stays); :1217 "Do not proceed until printed" →
+      when-guidance scoped to the single-shot path ("single-shot runs
+      print the FIX PLAN before STEP 12 serializes it" — MODE: judge
+      stops at 11, but /harden //onboard execute the whole file,
+      conf#1). The completeness checklist :1309-1320 is NOT deleted:
+      its routing rows (stock-photo→GATED(E), compression→AUTO(bash)
+      or §11, aggregateRating→AUTO(hotfixer), structural→GATED(D)…)
+      are unique routing content (robustness#3) — reshape into a plain
+      mapping table, drop only the checkbox self-audit framing.
+  (b) DELETE vestigial :1525-1526 (contradicts BDR-061; Q4).
+  (c) DEDUP under the invariant (correctness#1 + robustness#1): only
+      VERBATIM same-AUDIENCE (spec rule / bundle-item payload /
+      phase-local caveat) same-MODE-RANGE (collect 0-5 / judge 6-11 /
+      template 12-14 / RULES=global) repeats merge. Expected survivors
+      per family listed at execution in the commit message; honest
+      net: never-apply 4→3 (RULES pair merges; template-range
+      statements stay), sentinel-verbatim reminders 3→2, landing-page
+      3→2 (payload instance :1260 + one spec statement; :1342 vs
+      :1502 merge), bundle-self-containment 2→1 (same range).
+      NOT deduped (v1 was wrong — distinct rules or cross-range):
+      COVERAGE ×4, 30/70 ×3, security-headers ×3, shared-file
+      discipline (payload vs spec audiences).
+  (d) SOFTEN caps/orderings to when-guidance, keeping semantics:
+      :61, :508 (gate stays before on-page scoring; emphasis drops),
+      :875, :1147, :1149-1157 CMS-plugin-first folded together with
+      :143-148 into ONE statement (correctness#3 — two strengths of
+      one rule otherwise), :1159-1162 Bing (content rule kept, caps
+      drop; FULL-only → statically verified), essays :606-618 +
+      :661-680 compressed keeping the rule + LRN citations; :602-604
+      kept as a when-guidance failure detector ("families ≈ URLs →
+      the heuristic broke — say so"), not deleted (robustness#8).
+  (e) Dispositions completing the C-list (correctness#3): :208-210 →
+      static pointer ("the CDN/WAF twin check lives in geo STEP 4");
+      :1504 KEEP as-is (one-line scope guard).
+- P3 REWORD geo-analyzer.md (commit 3), same invariant:
+  PERMISSIVE ×3: ALL survive (collect/template/RULES ranges;
+  :873 is the item-level default guarding an unconfirmed AUTO
+  robots.txt edit — named survivor, robustness#9). never-apply 4→3
+  (RULES pair merges). tier-mapping :824/:850 BOTH stay (judge vs
+  template ranges). content_quality-advisory 2→1 (same range).
+  shared-file 2× stays (payload vs spec). llms-honest 2× stays
+  (collect vs RULES). cite-sources 2× stays (:17 guards the header
+  stats specifically). :1106 vestigial → reworded to the truth
+  (dispatcher fills the log — matches :959; Q4). :777-786 caps →
+  plain content rule (FULL-only). :1102-1103 → freshness
+  when-guidance (kept — §3). :394 quantity softened ("substantial,
+  real customer questions"). :48 softened. :124-139 ask-block KEPT
+  (standalone path). Orderings :360/:811/:823 softened. :376-377
+  uncited claim → honest framing (no invented source).
+- P4 DOGFOOD AFTER (v3 — ordered by decisiveness, conf#7): fresh copy
+  of zenquality-frozen; phases in this order so a mid-run death still
+  leaves the decisive evidence (billing class already realised once):
+  (ii-first) judges fed the FROZEN baseline signals
+  (.audit/dogfood-baseline/) → judge reports vs frozen baseline judge
+  reports, ZERO collect variance — the decisive Opus-judge-prose
+  differential; (iii) templates on those judge reports → envelopes,
+  compared against the frozen BASELINE envelopes — the template
+  verdict anchors on ENVELOPES only (SEO.md/HUMAN-ACTIONS.md are
+  dispatcher-merged by this authoring session, non-attributable —
+  conf#10); (i-last) fresh collects, same pre-answered context →
+  (a) shape check of signals/COLLECT REPORT vs baseline, (b)
+  FIELD-LEVEL diff of the fresh signals vs baseline signals (record
+  blocks, COVERAGE counts, denominators — a shape-valid file with a
+  dropped field must be caught, conf#6), and (c) ONE end-to-end seo
+  judge on the FRESH signals (the domain with the most collect-range
+  edits) so the reworded collect→judge handoff runs at least once.
+  Comparison mechanical-first: presence-assertion script (named home:
+  `.audit/dogfood-baseline/assert-after.sh`, session-reproducible,
+  never committed — conf#11) + a FRESH reader agent diffing
+  before/after WITHOUT this plan in context (correctness#7); the
+  authoring session only arbitrates its report. If the after-run dies:
+  P0(4) abort + named exit applies; no merge request meanwhile.
+- P5 GATES: make test full suite (census + model-routing + seo-data +
+  no-vacuous-locks) · shellcheck on touched .sh · per-RANGE grep sweep
+  for every deduped family (asserts the named survivor lines exist in
+  their ranges — mode-blind ≥1× sweep is insufficient, robustness#1) ·
+  MEASURED deltas recorded (simplicity#7): wc -l + directive-token
+  census (annex §0 grep set) per file, before/after, into the BDR.
+  (v1's manual MODE/STEP sweep dropped — the census asserts it,
+  simplicity#5.)
+- P6 CAPITALIZE: BDR (decision, invariant, deltas, alternatives), LRN
+  (audience×range dedup invariant — reusable), journal, CHANGELOG.
+  TODO C1 checked. NO merge (human gate). Checkpoint report includes
+  the DYNAMICALLY-UNVERIFIED list (§6bis).
+
+## 4b. Dispatcher decisions (v2)
+
+- Q1 freeze scope: all §2a byte-frozen + §2b frozen via census; the
+  remaining unlocked A-prose freeze = per-commit git diff review.
+- Q2 census: done (P1), flip-proven.
+- Q3 dedup: WITHIN-file, same-AUDIENCE, same-MODE-RANGE, verbatim
+  repeats only. Cross-agent + agent↔dispatcher twins stay. (Mechanism
+  note correcting robustness#1's premise: every dispatch loads the FULL
+  agent file; the risk is ATTENTIONAL — a literal-following model told
+  "run STEP 13-15" deprioritizes guidance scoped to another step's
+  body — not access. Same fix either way.)
+- Q4 vestigial: seo :1525-1526 DELETE; geo :1106 REWORD to
+  dispatcher-owns-log (correctness#6 resolved).
+- Q5 /harden //onboard: out of scope (N6); their dispatch-prompt
+  contracts are untouched by agent-file rewording; `NARROW-SCOPE`
+  keying frozen (§2a).
+
+## 5. Dogfood protocol (v2)
+
+Baseline (DONE for collect+judge SEO; geo judge in flight at v2 time):
+frozen zenquality copy (no .env), inline pipeline (canonical /seo shape
+— the nested-CLI attempt died on the CLI monthly spend limit, recorded),
+absolute PROJECT ROOT in every dispatch, `/seo local conservative`,
+STEP 0 pre-answered, NAP = NAP-KIT.md (user-confirmed 2026-07-10).
+Baseline artifacts frozen under the DURABLE `.audit/dogfood-baseline/`
+(gitignored, never committed — conf#9): signals ×2, judge reports ×2,
+template ENVELOPES ×2, merged SEO.md, HUMAN-ACTIONS.md (conf#2 — the
+template phase runs to completion BEFORE the first agent edit).
+After-run per P4. LIMITS stated honestly
+(robustness#2): conservative never enters STEP 1b/1.5 (no applier parses
+an item this run — the item-field contract is census-locked statically);
+LOCAL never executes STEP 3-4/6-7 FULL branches (Bing/AI-index emission
+text, live checks — the FULL-only conditionals were exercised and
+correctly declined in the baseline judge). These stay on the
+§6bis unverified list for the human gate; a FULL/aggressive dry-run is
+an OPTION the user may order at checkpoint, not part of this plan.
+
+## 5bis. CHALLENGE SYNTHESIS (2026-07-30)
+
+Verdicts: correctness FATAL(3) [1 BLOCKER, 2 MAJOR, 4 MINOR] ·
+robustness FATAL(9) [3 BLOCKER, 6 MAJOR, 2 MINOR] · simplicity
+CONCERNS(3) [3 MAJOR, 4 MINOR]. All three lenses returned. Every
+BLOCKER closed by a named v2 change:
+- correctness#1 (audience-blind dedup) + robustness#1 (mode-blind
+  dedup) → §4b Q3 invariant + P2(c)/P3 rewritten + P5 per-range sweep.
+- robustness#2 (dogfood can't reach riskiest edits) → §5 honest limits
+  + §6bis unverified list + P2(d)/P3 minimal-diff on FULL-only sites +
+  static census cover; FULL/aggressive run offered to the human, not
+  silently added (billing exposure robustness#11).
+- robustness#3 (routing table misfiled as self-check) → P2(a) keeps
+  routing rows verbatim.
+Majors adopted: R4 live-tree abort path (P0) · R5 url-guard anchors
+corrected + security orderings frozen (§2a/§3) · R6 external-freshness
+kept (§3) · R7 :550 frozen (§3) · R8 :602 kept as detector (P2(d)) ·
+R9 :873 named survivor (P3) · C2 folded into R2's resolution · C3 full
+dispositions (P2(d)/(e), P3) · S1 §1 rewritten · S2 controlled
+judge-replay (P4) · S3 mechanical presence script (P4). Minors adopted:
+C4 file-qualified locks · C5 §2 split · C6 three inconsistencies
+resolved (P1 note, Q4, N1 marker) · C7 fresh-reader diff · S4 diff-
+review freeze · S5 sweep dropped · S6+R10 census corrected+flip-proven ·
+S7 measured deltas. Rejected/scoped: S1's apparatus-shrinking (the
+apparatus is user-directed); R1's access premise corrected to
+attentional (fix adopted unchanged).
+
+CONFIRMATION PASS (robustness lens, v2 → v3): FATAL(9) — 2 BLOCKER +
+7 MAJOR/MINOR, all targeting the v2 amendments as asked. Closed by
+name: conf#1 no-MODE single-shot → §6bis + P2(a) :1217 scoped-softened
+· conf#2 missing baseline template artifacts → P0(1) full-baseline
+precondition · conf#3 /client-handover freeze → P0(3) · conf#4 abort
+HEAD-vs-develop + named exit → P0(4) · conf#5 interior STEP locks →
+census extended to all headers (71/0) · conf#6 collect→judge seam →
+P4(i) field-diff + one end-to-end seo judge on fresh signals · conf#7
+decisiveness order → P4 reordered (ii)→(iii)→(i) · conf#8 :970
+anti-score-shopping → when-guidance reword, not deletion · conf#9
+volatile baseline → durable .audit/dogfood-baseline/ · conf#10
+dispatcher-owned artifacts → envelope-anchored template verdict ·
+conf#11 script home named. Challenge budget exhausted (1 re-pass max):
+residual risk goes to the human gate with this record.
+
+## 6. Explicitly NOT doing
+
+- N1 No dispatcher (SKILL.md) edits.
+- N2 No scoring-weight, axis, or depth-matrix changes.
+- N3 No model-pin changes (BDR-076).
+- N4 No weakening of class-B invariants (§3 hardened in v2: security
+  orderings byte-frozen).
+- N5 No new modes, no pipeline reshaping (BDR-077).
+- N6 No /harden //onboard contract reconciliation (annex §7.5).
+- N7 No collect-boundary wording fix (works by prompt override).
+- N8 No cross-agent shared-resource consolidation.
+- N9 No deterministic GEO score engine (annex §7.9).
+- N10 No FULL/aggressive dogfood in this plan (user option at gate).
+
+## 6bis. Dynamically-unverified edit surface (for the human gate)
+
+Sites edited by P2/P3 that no dogfood run executes: FULL-branch content
+(seo :1159-1162 Bing emission, geo :777-786 AI-index emission, both
+freshness when-guidances), apply-path parsing (STEP 1b/1.5 — item
+pasted into appliers; covered statically by census item-field locks +
+frozen bundle templates), STEP 6-7 external-presence prose, and the
+no-MODE single-shot path (conf#1: /harden and /onboard dispatch the
+agents without a MODE line — "all steps in sequence" — so the whole
+reworded body drives those runs; every never-apply and ordering
+statement that path relies on keeps a surviving instance, and :1217
+is softened-scoped to it, never deleted). Mitigation: minimal diffs
+there (caps→plain only), census locks, git-diff review.
+
+## 4c. Backlog surfaced (not this branch)
+
+- Score-label fallback fragility in client-handover-writer.md (can read
+  `TRAJECTORY TO 17/20` as 17.0 if the label vanishes) — annex §7.8.
+- Stale lib/ line-number comments pointing at agent lines (annex §1).
+- Baseline judge's gate observation: /client-handover 17/20 gate passes
+  with an open `critique` finding — "open critique = independent
+  blocker" is worth its own decision.
+
+## 7. Constraints for challengers
+
+- Registries append-only; census green throughout; reword commits keep
+  54/0 + model-routing + seo-data locks green.
+- Agent files symlink-live INCLUDING between Edit calls (P0 abort path).
+- §2a byte-identical; §2b frozen; STEP numbering preserved; §3 security
+  orderings verbatim.
+- Dedup only same-audience + same-mode-range verbatim repeats; named
+  survivors per family in commit messages; P5 per-range sweep.
+- The judge phase is Opus 5; collect/template Sonnet — literal
+  following applies to all (E5 "since 4.7").
+- Baseline artifacts frozen before first edit; after-run design per P4.

.gitignore

@@ -142,6 +142,12 @@ desktop.ini
 # an update. The source is always re-synced, so no offline copy is needed.
 skills-external/frontend-design/
 
+# Emil Design Eng — machine-owned copy curl'd from emilkowalski/skill by
+# install-plugins.sh (Step 8, when absent) and re-fetched on every update-all.sh
+# run. Not vendored: tracking it produced a repo diff each time upstream shipped
+# an edit. The source is always re-fetched, so no offline copy is needed.
+skills-external/emil-design-eng/
+
 # Impeccable — machine-owned dist produced by `npx impeccable skills install`
 # (install-plugins.sh Step 8d, update-all.sh), pinned in plugins.lock.json.
 # Not vendored: the installer owns the layout and rewrites it on update

ARCHITECTURE.md

@@ -0,0 +1,33 @@
+# Architecture — claude-config
+
+Repo layout and structural principles. Command workflows live in
+[`USAGE.md`](./USAGE.md); version history in [`CHANGELOG.md`](./CHANGELOG.md).
+
+## Project layout
+
+```
+claude-config/
+├── CLAUDE.global.md       # Global coding preferences — deployed as ~/.claude/CLAUDE.md
+├── CLAUDE.md              # Project-scope instructions (this repo only)
+├── settings.json          # Global permissions (deny / ask / allow rules)
+├── install.sh             # Bootstrap: Claude Code CLI + auth + submodules + link + plugins
+├── install-plugins.sh     # One-shot installer: prerequisites + all plugins
+├── link.sh                # Symlinks this repo into ~/.claude/
+├── doctor.sh              # Setup diagnostic
+├── update-all.sh          # One-command update for all components
+├── Makefile               # Unified entry point: make install / doctor / update
+├── plugins.lock.json      # Version pinning for non-marketplace dependencies
+├── hooks/                 # Session start, statusline, RTK rewrite + ctx7 + design-toolchain reminders
+├── agents/                # Execution units called by skills (never invoked directly)
+├── skills/                # Entry points invoked via /skill-name
+├── skills-external/       # Vendored skill packs (gstack submodule + installer-fetched design packs)
+├── templates/             # Per-project templates (CLAUDE.md, settings, memory registries, deploy runbook, gitignore)
+└── lib/                   # Shared shell libs (gitflow, profiles, commit helpers, archetypes, tests)
+```
+
+## Architecture principles
+
+- `skills/` = entry points you invoke via `/skill-name`
+- `agents/` = execution units called by skills (never invoked directly by user)
+- `templates/` = symlinked to `~/.claude/templates/` — copy into projects via `/onboard` or manually
+- **Graphify** builds a knowledge graph of any codebase (`/graphify query`), producing a navigable wiki in `graphify-out/wiki/`. This map helps Claude understand project structure, find relevant code faster, and reason across files. Essential for large-scope tasks (multi-file features, complex bugs, architectural changes). Small tasks should skip it and read files directly.

CHANGELOG.md

@@ -6,6 +6,212 @@ Format follows [Keep a Changelog](https://keepachangelog.com/).
 
 ## [Unreleased]
 
+## [1.5.0] — 2026-09-13
+
+### Added
+- **Attention signals on the terminal (BDR-087)** — new
+  `hooks/notify-attention.sh`, wired on `Notification` (input-needed
+  matcher) and on `Stop` (no matcher). Returns a double BEL plus an
+  OSC 777 toast through the `terminalSequence` JSON field, since hooks
+  have no controlling TTY. Signal only: `suppressOutput`, exit 0, zero
+  control-flow effect, which is what separates it from the `decision:
+  "block"` Stop hook [[BDR-083]] refused. Each event reaches the toast
+  as a readable label instead of a snake_case type; events needing no
+  attention (`agent_completed`, `auth_success`) exit silently; a turn
+  that ends with `background_tasks` still running stays quiet and
+  signals at the real end. Client-side prerequisites over Remote-SSH
+  are documented in the script header ([[BLK-020]]): VS Code
+  `accessibility.signals.terminalBell` for the beep, an OSC notifier
+  extension for the Windows toast.
+- **User permanent rules (BDR-085)** — three new rules/ files from the
+  user's rule text: `writing-style.md` (always-on: em-dash ban, no slop
+  vocabulary, no hedging chains, deliverable self-check),
+  `web-building.md` (path-scoped: design anti-defaults + public-site done
+  checklist), `web-security.md` (path-scoped: RLS, service-key/client
+  split, IDOR, cookie flags, rate limiting — extends §Security, no dup).
+  Project CLAUDE.md rules/ doctrine gains the 320-budget exception.
+- **/tour multi-project parallel fan-out (BDR-084)** — two or more
+  project paths now dispatch one runner per repo in a single message
+  (independent working trees, nothing collides) instead of processing
+  them one by one. The runner inherits the session model (no pin — it
+  carries tour's reflection); every agent inside keeps its defined tier.
+  A dead runner surfaces as an explicit `RUNNER FAILED` summary row; the
+  gated capitalize offer stays in the main loop. Bounded LRN-083
+  derogation recorded in BDR-084. Census §12: 6 locks, flip-tested.
+  Mechanics proven first: nested probe, 3 overlapping agent windows,
+  9.1s vs ~18s sequential.
+- **Contract gates — deterministic floor under the fresh verifier (BDR-083)** —
+  an acceptance criterion can now carry an oracle (`CHECK:` command +
+  `EXPECT:` success-only marker + `EVIDENCE:` slot). `lib/gates.sh run
+  <contract>` executes them fail-closed — MET requires exit 0 **and** the
+  marker — and writes the outcome back into the contract, so the fresh
+  verifier reads evidence as fact instead of trusting the executor's report.
+  New `GATE 0` in `lib/verify-secure-loop.md` runs the floor before any
+  verifier is dispatched: a red build no longer costs an LLM dispatch to
+  discover. `ABANDON: <id> <reason>` makes an impossible criterion a visible
+  handoff that blocks `CONFORME` and routes to the human gate (new verifier
+  verdict `ABANDONED(n)`). `feater` and `bugfixer` gain a four-pass
+  completion discipline, scoped so it can never widen the contract.
+  Adapted from the `unlazy` skill (Leonxlnx/unlazy, MIT); its Stop hook,
+  approval store, `.unlazy/` tree, depth-tree arithmetic and Node checker
+  were deliberately refused — see BDR-083 for each reason.
+  The four orchestrator skills (`feat`, `bugfix`, `ship-feature`,
+  `init-project`) restate the GATE 0 bullet ahead of GATE 1 (locked);
+  hotfix explicitly runs no floor. Behavioral RED: 16/16 fresh unprimed
+  runs followed the new doctrine (EVAL-027).
+  64 new assertions in `lib/tests/gates.test.sh`.
+- **`lib/tests/seo-geo-contract.test.sh`** — census locking the seo/geo
+  agent ⇄ dispatcher machine contract: judge verdict grammar, FIX BUNDLE +
+  READY-TO-APPLY sentinel, signals handoff, every STEP header (interiors
+  included), bundle item fields, score labels, scoring blocks, envelope
+  keys (46→71 assertions across the C1 chantier).
+
+### Changed
+- **Skill and agent quality campaign, 54 units (BDR-086)** — full darwin
+  v2.1 pass over the 31 personal skill-systems and 23 agents, excluding
+  the gstack/external symlinks and machine-owned units. Fresh baseline
+  mean 83.4; the 13 units under the user-set threshold of 80 were
+  optimized to completion, and verified defects in above-threshold units
+  were fixed in a grouped pass rather than left to ship because the score
+  was good enough. Every round was validated by a paired 3-judge majority
+  reading before and after in one call: 36 unit-round verdicts, 24 batch
+  verdicts, all better, zero reverts. Full report and residual findings:
+  `.claude/audits/DARWIN-2026-08-26.md`.
+- **seo-analyzer + geo-analyzer de-prescribed for Opus 5 (BDR-082)** —
+  process choreography converted to when-guidance under an
+  audience×mode-range invariant; self-output verification demands removed
+  (the score-engine "run it twice" became a conditional integrity guard);
+  two pre-BDR-061 vestigial rules fixed; P0/MANDATORY/ALWAYS caps softened
+  to plain content rules. Machine contract byte-frozen and locked by the
+  new `lib/tests/seo-geo-contract.test.sh` census (71 locks, flip-proven);
+  proven by a controlled before/after `/seo` dogfood — judge replay on
+  frozen signals, 42/42 presence assertions on both runs, blind structural
+  reader: interchangeable, recall improved.
+- **Global instruction layer recalibrated for the Claude 5 family (BDR-081)** —
+  delegation block is now model-neutral when-guidance (the Opus 4.8
+  under-delegation counter inverted on Opus 5, which over-delegates and gets
+  an injected harness cap); "staff engineer" self-check bar dropped (Opus 5
+  over-verification trigger); finish-whole-task clause added to Deviations;
+  written-deliverable length rule added. 308/320 lines.
+- **Default session model is now `opus[1m]`** (was `claude-fable-5[1m]`).
+- **`skills-external/emil-design-eng/` untracked** — the file is curl'd
+  from upstream by `install-plugins.sh` when absent and re-fetched by
+  every `update-all.sh` run, so tracking it produced a repo diff on each
+  upstream edit. Same category as `frontend-design/` and `impeccable/`,
+  already ignored on that rationale; a fresh clone re-fetches it.
+  `design-motion-principles/` has the same overwrite behaviour but no
+  bootstrap clone yet, so it stays tracked until that gap closes.
+
+### Fixed
+- **hotfix wiped tolerated in-progress edits on its revert path** — every
+  failure branch ran `git restore .`, destroying user edits the run had
+  tolerated. Now a `git stash create` pre-flight snapshot plus a
+  file-scoped restore, and the security gate is fresh-dispatch only.
+- **skills-perso listed 8 of 31 personal skills** — detection rebuilt on
+  the `link.sh` symlink convention (symlink = external, real dir =
+  personal, gitignored = machine-generated). Live result 31/31, no false
+  positives.
+- **plan-challenger** — `ERROR` joined the load-bearing verdict grammar
+  (STEP 1 emitted it, the parser enum omitted it); grounded-but-uncertain
+  findings now file as `[MINOR]` with the uncertainty stated, instead of
+  being self-censored (Opus 5 follows conservative-reporting clauses
+  literally).
+- **design-toolchain hook** — dropped `\bux\b` (2 French-prose false
+  positives; 3rd tightening pass, series LRN-1005/1007); `\bui\b` kept and
+  locked by a must-fire test row.
+- **Agent and skill defects found by the campaign's judges** —
+  `init-project` allowed-tools lacked `Agent` and `Skill` while every step
+  dispatches; `commit-change` conflict grep now covers all 7 unmerged
+  codes; `tour --report-only` no longer commits; `harden` severity defers
+  to the calibrated guide and the late SSL Labs grade has an assigned
+  actor; handover writers' stale chapter refs corrected and the anchor
+  gate ordered; `security-auditor` documents the hotfix no-verifier
+  carve-out; `close` enumerates STEP 5C and passes `--no-push` through;
+  `prune-memory` drops a false "v1-untested" note; `code-clean` attributes
+  its executor correctly; plugin-check and onboard fixtures de-drifted.
+
+## [1.4.0] — 2026-07-22
+
+### Added
+- **Transient planning artifacts auto-purged at feature-finish (BDR-065)** —
+  `gitflow finish` on a `feature`/`bugfix` branch now removes the run-time
+  superpowers artifacts (`docs/superpowers/{specs,plans}`) on the working
+  branch just before the directed merge, so `develop`'s tip lands clean while
+  the feature commits stay reachable as the archive (`git show <sha>:…`). This
+  automates the manual post-merge cleanup that BDR-065 had left as doctrine —
+  the step that slipped in 1.3.0 and needed a hand purge. Best-effort by
+  contract: a purge that finds nothing, meets uncommitted changes under those
+  paths, or fails to commit never aborts the finish (index/tree restored); opt
+  out with `GITFLOW_PURGE_TRANSIENT=0`. New `gitflow.sh purge-transient` verb.
+  `.claude/tasks/{contracts,plans}` are deliberately out of scope (durable,
+  versioned, referenced by the decision registry). Live in every project via
+  the `~/.claude/lib` symlink; covered by `lib/gitflow-test.sh` T17 (a–d).
+
+### Changed
+- **Bug routing inverted: `/bugfix` primary, `/investigate` explicit-only
+  (BDR-080)** — a bug / error / 500 now routes to `/bugfix` by default (the
+  full framework: gitflow, contract, fresh verifier + security gates,
+  registries). The gstack `/investigate` monolith — its own `~/.gstack`
+  memory, no gitflow or gates — is reserved for explicit requests
+  (cross-project learnings, `/freeze` scope lock, long investigation with no
+  immediate commit intent). Same core debugging doctrine, incompatible
+  wrappers; the default now favours the gated, integrated path.
+
+## [1.3.1] — 2026-07-20
+
+### Changed
+- **README rebuilt around a short pitch** — new top half: what it is / how
+  it works / why it's good in ~60 lines (skills = entry points, agents =
+  model-tiered execution units, hooks = deterministic guardrails,
+  templates/memory = compounding per-project registries); all previous
+  content demoted to an explicit reference-manual half below a separator.
+  Deduplicated in the process: old title/tagline, Overview prose and the
+  duplicated fresh-install block removed (unique install notes kept under
+  a new "Install notes" section); hardcoded version number dropped from
+  the footer (staleness risk). Docs-only release — no code change.
+
+## [1.3.0] — 2026-07-20
+
+### Added
+- **Profile switches now toggle external packs and MCPs both ways (BDR-079)** — `profile.sh set` was asymmetric: it enabled what a profile listed (including gstack skills on demand when the whole pack is off, and the `magic` MCP) but never disabled the managed leftovers, so `set backend` after design work kept emil-design-eng / frontend-design / design-motion-principles / impeccable active and magic registered. `set` now trims managed externals (`MANAGED_EXTERNALS`) and managed MCPs (`MANAGED_MCPS`, delegated to `toggle-external.sh`) not listed in the profile — same allowlist doctrine as `MANAGED_PLUGINS`, nothing outside the allowlists is ever auto-touched (darwin-skill stays manual). Also: an `external` entry whose symlink never existed is now created from `skills-external/` (mirroring toggle-external's from-source path), and the stale "NOT toggled automatically" note in `profile.sh` usage was corrected. Covered by a hermetic 16-check test (`lib/tests/profile-set-managed.test.sh`) with a fake `claude` shim.
+
+### Changed
+- **README restructured for public readers** — the project-layout tree and architecture principles moved verbatim to a new `ARCHITECTURE.md` (README links it); bare decision-registry citations (`BDR-XXX`) stripped from README prose, meaning preserved; `/profile` documentation corrected in three places to the real 10-profile set (web / seo / web-full / full / backend / design / dev / qa / audit / minimal); fresh-install block now uses the real clone URL + `make install` / `make doctor`; new "SEO data layer" subsection documents the `GOOGLE_OAUTH_CLIENT_ID` / `GOOGLE_OAUTH_CLIENT_SECRET` / `CRUX_API_KEY` vars in `~/.claude/.env` (mirrors `.env.example`, `make seo-connect` one-time consent).
+
+### Fixed
+- **Transient planning artifacts purged from the repo** — `docs/plans`, `docs/specs`, `docs/superpowers/{plans,specs}` (deploy-skill 2026-06-27, model-routing 2026-07-15) were run-time pipeline artifacts that should have been deleted in their chantiers' post-merge cleanup and slipped through (one pair predates the lifecycle rule, one missed the purge step of a 6-wave chantier). Git history at the feature commits remains their archive; `docs/` no longer exists.
+
+## [1.2.1] — 2026-07-20
+
+### Fixed
+- **README caught up with the code it describes** — the "Agent model routing" section still presented the BDR-066 v1 scheme (7 rows factually wrong after model-tiering v2): reframed to the BDR-076/077 4-tier table verified against agent frontmatters (opus-pinned judgment agents, per-mode splits for doc-syncer / handover-doc-writer / seo-geo pipelines, plugin-probe added, unpinned inline agents listed as such). Also: Context7 paragraph rewritten to the two-surface model (find-docs = sole doc-fetch surface, `ctx7-reminder` hook = scoped session nudge, BDR-078), `hooks/` tree line now mentions the ctx7 reminder, and the `/ship-feature` workflow block gained its STEP 2b (adversarial plan-challenge) line. Docs-only release — no code change.
+
+## [1.2.0] — 2026-07-20
+
+### Added
+- **ctx7 coverage extension (BDR-078)** — the "consult current docs before coding against a fast-moving lib" doctrine now covers every code path, not just the two big pipelines. (1) `lib/fast-libs.sh`: single source of truth for fast-lib detection (`detect` / `cache-status` verbs; JS package.json anchored keys + Python requirements/pyproject; 7-day `.ctx7-cache/` freshness; locale-independent sort), replacing three hardcoded lists (`/ship-feature` STEP 0c, `/init-project` STEP 5c, `/onboard` STEP 3.5). (2) `hooks/ctx7-reminder.sh`: once-per-session UserPromptSubmit nudge when the project carries fast-libs and the cache is missing/stale — closes the ad-hoc-coding gap. (3) find-docs description extended with a before-writing-code trigger + a cache-first rule (read fresh cache, tee fetched docs back into it). (4) feater/bugfixer executor briefs gain the fast-lib docs rule (read fresh cache, else 2-topic `npx ctx7@latest` fetch, else report `ctx7 cache miss` and proceed). Second deliberate ctx7 surface — a scoped refinement of BDR-053's single-surface rule, not a reversal.
+- **Adversarial plan-challenge phase** — reflection orchestrators now run a blind 3-lens challenge (correctness / robustness / simplicity) via a dedicated `plan-challenger` agent before implementation; severity-driven (a single-lens BLOCKER stops the plan), report-only. `/hotfix` joins behind a logic-only guard: cosmetic fixes skip it, logic fixes get challenged, a BLOCKER reroutes to `/bugfix` (BDR-075).
+- **seo-data engine: measured coverage + new verbs** — the `/seo` FULL audit measures instead of feeling: `sitemap` verb gives COVERAGE a real denominator (source/live split); internal-link graph computes orphan pages + click depth; cannibalisation detected from GSC's own query data; `rich_results` surfaced from URL Inspection data already fetched; `sameAs` profiles actually resolved; `schema_gen` generates JSON-LD instead of only auditing it; `content_quality` runs a deterministic filler/AI-slop scan; the axis score is computed, not felt; `drift` baseline reports regressions vs changes. SPA pages: the audit refuses to score what JS paints instead of scoring the empty shell (no Playwright dependency). Common Crawl backlinks were measured (17 GB edges file) and killed as a source — the Off-page axis stays scoped to what is actually measured.
+
+### Changed
+- **Model-tiering v2: 4-tier explicit routing (BDR-076/077)** — the session model (Fable) does main-loop reflection/orchestration only; every dispatched subagent is explicitly tiered: judgment agents pinned opus (analyzer, plan-challenger, seo/geo audit agents…), mechanical executors sonnet, skill-runner children fable — nothing inherits silently. Mode-based splits so pins take effect: doc-syncer audit(opus)/patch(sonnet), handover-doc-writer synthesize(opus)/render(sonnet), seo/geo collect(sonnet)/judge(opus, fail-closed)/template(sonnet), plugin gate split probe(sonnet)/advisor(opus). Census locks (125) + per-wave planted-input smokes.
+- **config-protection edit-block guardrail removed** (BDR-074) — the hook blocked more than it protected; deny-list design pass recorded in BDR-069.
+- graphify vendored skill dist synced 0.9.6 → 0.9.15.
+
+### Fixed
+- **seo/geo integrity pass (I1–I8)** — Off-page axis scoped to measured data only; VSI (an SEO-blog fiction) removed from CWV thresholds; NAP direction rule ported into geo-analyzer (standalone `/geo` can no longer write unverified NAP); security headers no longer double-counted (`/harden` owns them); sampling coverage disclosed instead of implied; stats reattached to the claims they support; phantom audit precondition dropped. Plus two real bugs caught by a second-site backtest and two process anomalies from live dogfooding.
+- `settings.json` Write() deny rules were inert — converted to Edit() rules, closing the write hole they left open.
+- Model-routing W6 ronde: 6 findings closed (README bootstrap path, 2 census gaps, 3 stale refs).
+
+### Security
+- **`safe_fetch` resolve-then-pin** in `lib/seo-data` — DNS-rebinding closed on audit fetches: the audited host is resolved once, validated, then pinned for the actual fetch.
+- **`url-guard`** — shell-injection + local-target refusal before any user-supplied or sitemap-crawled URL reaches curl (SSRF guard on the seo/geo fetch paths).
+
+## [1.1.0] — 2026-07-16
+
+### Added
+- `/close` + `/capitalize` now auto-persist the memory they write. When the ritual branches a `chore/*` branch off develop, it finishes that branch into develop and pushes `origin/develop` automatically (new STEP 5C), so capitalized decisions / learnings / evals reach the next session instead of stranding on an unmerged branch. Scoped to memory-only ritual commits: a `--no-push` flag holds the commit on the branch instead; a run on a feature branch (where the memory already rides the work) or an unsafe git state skips the auto-persist; and a failed push leaves the local merge intact with a manual-push note. Recorded as BDR-068, a deliberate scoped exception to the push-needs-an-explicit-go rule (which guards surprise code/release pushes, not an end-of-session memory persist).
+
 ## [1.0.0] — 2026-07-16 — Initial public release
 
 First public release of claude-config. The feature set below is the

CLAUDE.global.md

@@ -22,6 +22,8 @@ Apply unless repo-specific instructions override.
 - Document intent, not mechanics. Use project doc style (docstring, JSDoc…).
 - Explicit, consistent, meaningful names. Straight control flow,
   no hidden side effects.
+- Written deliverables (docs, reports, .md): length matched to what
+  the task needs — no filler sections, no boilerplate summaries.
 
 ## Refactoring
 - Priority: safety → readability → consistency.
@@ -40,11 +42,12 @@ Apply unless repo-specific instructions override.
 - Confirm before implementing only when real trade-offs exist (multiple
   valid approaches, breaking change, destructive action) — else proceed.
 - Minimal changes unless broader refactor requested. State trade-offs.
-- Sub-agents keep main context clean — one task per sub-agent.
-  More compute on hard problems. Task fans out across independent
-  items (many files, parallel searches, multi-point checks) → delegate
-  to sub-agents, don't iterate serially. Default to delegation for
-  multi-file exploration. Counters model tendency to under-delegate.
+- Sub-agents: one task per sub-agent, main context stays clean.
+  Delegate genuinely independent, sizeable tracks (wide multi-file
+  exploration, parallel audits) — not work doable in a few tool
+  calls. Skill-mandated gates (fresh verifier/security/challenge)
+  always dispatch as written. Don't redo delegated work by hand —
+  failed gates re-dispatch fresh executors instead.
 - One question upfront if needed — don't interrupt mid-task.
   *Exception: skill-mandated gates and checkpoints (orchestrator
   validation gates, approval gates, darwin checkpoints) always fire.*
@@ -53,6 +56,8 @@ Apply unless repo-specific instructions override.
 - Something goes wrong → STOP, re-plan. Never push through.
 - Deviations: minor or clearly justified → do, explain after.
   Significant or shaky justification → ask before deviating.
+  Finish the whole task: blocked on an independent sub-part → do
+  the rest, state what's missing. Gone WRONG → still STOP, re-plan.
 - Root causes only. No temp fixes. Never assume — verify paths, APIs,
   variables before use.
 
@@ -77,7 +82,6 @@ Apply unless repo-specific instructions override.
 2. Report what verified, what not.
 3. List remaining risks, surviving deviations.
 4. Don't mark complete without proof it works.
-   Bar: "would staff engineer approve?"
 5. Correction or notable event → capitalize to right registry
    (see "Memory registries").
 
@@ -252,7 +256,10 @@ description fits (full list is in context). Rules below cover only the
 non-obvious cases: gstack fallbacks, disambiguation, cryptic names.
 
 - Product idea, "worth building?" → office-hours
-- Bug / error / 500 → investigate (bugfix if gstack off)
+- Bug / error / 500 → bugfix (full framework: gitflow, contract, fresh
+  verifier/security gates, registries). investigate ONLY on explicit ask
+  for the gstack ecosystem (cross-project learnings, /freeze scope lock,
+  long investigation with no immediate commit intent)
 - feat / hotfix / bugfix distinguished by file count → see descriptions
 - Ship / deploy / PR → ship (ship-feature if gstack off)
 - Cut a release / tag a version (develop ahead of main) → release-candidate

CLAUDE.md

@@ -17,7 +17,9 @@ A rule WITH `paths:` YAML frontmatter (glob list) loads lazily — only when
 Claude reads a file matching a glob; a rule WITHOUT it loads at session
 start, same cost as the global memory. Extract from CLAUDE.global.md only
 what can be path-scoped (the token win) or what is generated; always-on
-doctrine stays in CLAUDE.global.md. `paths:` globs match against the
+doctrine stays in CLAUDE.global.md. Exception: a standalone user-authored
+rule set that would bust the 320-line density budget may live here WITHOUT
+`paths:` (always-on load) — writing-style.md (BDR-085). `paths:` globs match against the
 CURRENT project's tree — a broad glob (e.g. `rules/**`) can fire in foreign
 projects; keep rule bodies tiny.
 Docs: https://code.claude.com/docs/en/memory.md#path-specific-rules
@@ -32,8 +34,13 @@ or re-run `make plugin`.
 
 `docs/superpowers/specs/**` and `docs/superpowers/plans/**` are run-time
 artifacts of a feature pipeline (subagent briefs, reviewer references).
-They are committed DURING the run and DELETED in the post-merge cleanup
-(BDR-065) — git history at the feature commits is their archive. Durable
-knowledge goes to `.claude/memory/` registries, never to these files.
-Derived scan/audit outputs (`.audit/**`) are gitignored and never
-committed, even redacted (LRN-124).
+They are committed DURING the run (the SDD worktree + reviewers read them
+from disk — NOT gitignored), then AUTO-PURGED by `gitflow finish` on a
+`feature`/`bugfix` branch, before the merge, so develop's tip stays clean
+(BDR-065, `lib/gitflow.sh` `_gitflow_purge_transient`). The feature commits
+stay reachable from develop, so `git show <sha>:docs/…` is still the archive.
+Opt out with `GITFLOW_PURGE_TRANSIENT=0`. NOT in scope: `.claude/tasks/{contracts,plans}`
+(durable, versioned, referenced by decisions.md). Durable knowledge goes to
+`.claude/memory/` registries, never to these files. Derived scan/audit
+outputs (`.audit/**`) are gitignored and never committed, even redacted
+(LRN-124).

Makefile

@@ -71,7 +71,7 @@ new-skill: ## Create a new skill scaffold (usage: make new-skill name=myskill)
 		echo "✅ Created agents/$(name).md"; \
 	else echo "⚠️  agents/$(name).md already exists"; fi
 	@if [ ! -f skills/$(name)/SKILL.md ]; then \
-		printf -- '---\nname: $(name)\ndescription: <what this skill does — front-load key use case, max 250 chars>\nargument-hint: <what to pass>\ndisable-model-invocation: true\nallowed-tools: Read, Grep, Glob, Bash\n---\n\nLoad and follow strictly:\n- .claude/agents/$(name).md\n\nExecute on:\n\n$$ARGUMENTS\n' > skills/$(name)/SKILL.md; \
+		printf -- '---\nname: $(name)\ndescription: <what this skill does — front-load key use case, max 250 chars>\nargument-hint: <what to pass>\nallowed-tools: Read, Grep, Glob, Bash\n---\n\nLoad and follow strictly:\n- .claude/agents/$(name).md\n\nExecute on:\n\n$$ARGUMENTS\n' > skills/$(name)/SKILL.md; \
 		echo "✅ Created skills/$(name)/SKILL.md"; \
 	else echo "⚠️  skills/$(name)/SKILL.md already exists"; fi
 	@echo "   Edit both files, then run: bash link.sh"

README.md

@@ -1,91 +1,110 @@
 # claude-config
 
-Global Claude Code configuration — agents, skills, plugins, and project templates.
+One repo that turns Claude Code into a reproducible engineering system —
+skills, agents, hooks, plugins, and per-project memory, versioned and
+symlinked into `~/.claude/`. Clone it on any machine, run one command,
+and every project gets the same assistant with the same rules.
 
-> **Guide d'utilisation complet :** voir [`USAGE.md`](./USAGE.md) — workflows typiques, exemples par type de projet, arbre de décision "quel skill utiliser ?".
-> **Historique des versions :** voir [`CHANGELOG.md`](./CHANGELOG.md).
+## What it is
+
+Not a collection of prompts — an operating layer on top of Claude Code:
+
+- **Skills** (`/feat`, `/bugfix`, `/ship-feature`, `/seo`, `/tour`…) are the
+  entry points: each one encodes a complete workflow, from quick fix to
+  full feature pipeline with validation gates.
+- **Agents** are the execution units skills dispatch to — each pinned to
+  the cheapest model that can do the job (haiku collects, sonnet executes,
+  opus judges, the session model only reflects).
+- **Hooks and permissions** are deterministic guardrails: gitflow enforced
+  by a pre-commit hook, deny-first permission rules, secrets kept in
+  `~/.claude/.env` and never in config files.
+- **Templates and memory** seed every project with persistent registries
+  (decisions, learnings, blockers) — what a session learns, the next
+  session knows.
+
+## How it works
+
+```bash
+git clone --recurse-submodules https://github.com/bchanot/claude
+cd claude
+make install     # CLI + auth + symlinks + plugins (pinned in plugins.lock.json)
+make doctor      # verify everything
+```
+
+`link.sh` symlinks the repo into `~/.claude/`, so editing here updates the
+live config — and `git log` is the audit trail of your entire setup.
+Day to day:
+
+```bash
+/onboard            # bring an existing repo into the framework
+/ship-feature "…"   # brainstorm → plan → adversarial challenge → TDD → review → merge
+/feat "…"           # same idea, 1-5 files, no ceremony
+/close              # flush decisions and learnings to memory before quitting
+make update         # keep CLI, plugins, and submodules current
+```
+
+## Why it's good
+
+- **Reproducible.** One clone rebuilds the whole environment; versions are
+  locked, `make doctor` proves it works.
+- **Cost-shaped.** Model tiering routes reflection to the big model and
+  execution to cheap ones — the expensive context does only what it must.
+- **Safe by default.** Protected branches, ask-before-run on risky tools,
+  parameterized secrets: the guardrails are code, not good intentions.
+- **It compounds.** Memory registries, audit skills, and doc-sync keep every
+  project's knowledge growing across sessions instead of evaporating.
 
 ---
 
-## Overview
+Everything below is the reference manual — model routing, components,
+commands, settings, secrets, maintenance.
 
-This repo is your personal Claude Code setup, versioned and reproducible across machines.
+---
 
-```
-claude-config/
-├── CLAUDE.global.md       # Global coding preferences — deployed as ~/.claude/CLAUDE.md
-├── CLAUDE.md              # Project-scope instructions (this repo only)
-├── settings.json          # Global permissions (deny / ask / allow rules)
-├── install.sh             # Bootstrap: Claude Code CLI + auth + submodules + link + plugins
-├── install-plugins.sh     # One-shot installer: prerequisites + all plugins
-├── link.sh                # Symlinks this repo into ~/.claude/
-├── doctor.sh              # Setup diagnostic
-├── update-all.sh          # One-command update for all components
-├── Makefile               # Unified entry point: make install / doctor / update
-├── plugins.lock.json      # Version pinning for non-marketplace dependencies
-├── hooks/                 # Session start, statusline, RTK rewrite, config-protection + design-toolchain guards
-├── agents/                # Execution units called by skills (never invoked directly)
-├── skills/                # Entry points invoked via /skill-name
-├── skills-external/       # Vendored skill packs (gstack submodule + installer-fetched design packs)
-├── templates/             # Per-project templates (CLAUDE.md, settings, memory registries, deploy runbook, gitignore)
-└── lib/                   # Shared shell libs (gitflow, profiles, commit helpers, archetypes, tests)
-```
+## Agent model routing (model-tiering v2)
 
-**Architecture principle:**
-- `skills/` = entry points you invoke via `/skill-name`
-- `agents/` = execution units called by skills (never invoked directly by user)
-- `templates/` = symlinked to `~/.claude/templates/` — copy into projects via `/onboard` or manually
-- **Graphify** builds a knowledge graph of any codebase (`/graphify query`), producing a navigable wiki in `graphify-out/wiki/`. This map helps Claude understand project structure, find relevant code faster, and reason across files. Essential for large-scope tasks (multi-file features, complex bugs, architectural changes). Small tasks should skip it and read files directly.
-
-### Agent model routing (BDR-066)
-
-Reflection (brainstorm, plan, contract, audit judgment, loop decisions) runs
-INLINE on the session model — assumed Fable/Opus, enforced by a blocking
-gate (`lib/model-gate.md` + `lib/model-check.sh`) at the entry of the 13
-reflection orchestrators. Execution runs on pinned subagents:
+Doctrine: the session model (Fable) does main-loop reflection ONLY —
+brainstorm, plan, contract, audit judgment, gates, loop decisions — enforced
+by a blocking gate (`lib/model-gate.md` + `lib/model-check.sh`) at the entry
+of the 13 reflection orchestrators. Nothing dispatched inherits silently:
+typed agents carry a frontmatter pin, built-ins get an explicit `model=` at
+every call site.
 
 | Agent | Model | Tier |
 |---|---|---|
 | feater, hotfixer, bugfixer | sonnet (pinned) | executors — code from a closed plan (feat), fix from a closed diagnosis (bugfix), fix-bundle appliers |
 | verifier, security-auditor | sonnet (pinned) | fresh gates (≤3×/loop) |
-| commit-changer, release-executor, code-cleaner | sonnet (pinned) | dispatched execution — grouping+commit / release spans / approved cleanup (the audit + approval gate stay in the dispatcher) |
-| doc-syncer, onboarder, scaffolder, refactorer, interviewer, plugin-advisor | sonnet (pinned) | workers |
+| commit-changer, release-executor, code-cleaner | sonnet (pinned) | dispatched execution — grouping+commit / release spans / approved cleanup (audit + approval gates stay in the dispatcher) |
+| onboarder, scaffolder, refactorer, validator-analyzer, plugin-probe | sonnet (pinned) | workers — config generation, scaffold, refactor, deterministic W3C/WCAG runner, mechanical plugin probe |
 | status-reporter | haiku (pinned) | mechanical collector |
-| handover-doc-writer | sonnet (pinned) | deliverable writer — synthesizes + renders the client doc from a resolved PACKAGE (dispatched by client-handover) |
-| analyzer, seo-analyzer, geo-analyzer, validator-analyzer, client-handover-writer | inherit session (Fable/Opus) | reflection / audit / inline playbooks / ship-and-handover pipeline |
+| analyzer, plan-challenger, plugin-advisor | opus (pinned) | dispatched judgment — pre-plan analysis, 3-lens adversarial plan challenge (`/ship-feature` STEP 2b), plugin-fit reasoning |
+| seo-analyzer, geo-analyzer | opus pin (judge mode); collect/template spans dispatched `model="sonnet"` | 3-mode audit pipelines — judgment fail-closed on opus, mechanical collect + templating on sonnet |
+| doc-syncer | sonnet pin; audit mode dispatched `model="opus"` | two-mode: audit (drift judgment, opus) / patch (mechanical apply, sonnet) |
+| handover-doc-writer | sonnet pin; synthesize mode dispatched `model="opus"` | two-mode: synthesize (opus) / render (sonnet) — client deliverable |
+| interviewer, client-handover-writer | unpinned (inline-load = session model) | they ARE the main loop — a frontmatter pin would be inert |
 | Explore (built-in) | inherit session (Fable/Opus) | search feeds reflection — kept on the big model, not pinned down |
 
 The pure-execution skills `/doc`, `/status`, `/commit-change`,
 `/release-candidate` **dispatch** their agent (instead of inline-loading it)
 so the pin takes effect and the work leaves the big session model; `/hotfix`
 was split like `/feat` (reflection inline + gate, `hotfixer` executor) and so
-joins the gated group (13th).
+joins the gated group (13th); `/client-handover`'s nested skill-runner
+children are dispatched `model:"fable"` (they carry reflection).
 
 ---
 
-## Fresh install (new machine)
-
-```bash
-# 1. Clone with submodules
-git clone --recurse-submodules git@github.com:youruser/claude-config.git
-cd claude-config
-
-# 2. Bootstrap (CLI + auth + symlinks + plugins)
-bash install.sh
-
-# 3. Verify setup
-bash doctor.sh
-
-# 4. Restart Claude Code — plugins load automatically
-```
+## Install notes
 
 All scripts use their own location to find the repo — run them from anywhere.
 The plugins step logs to `install-YYYYMMDD-HHMMSS.log`.
 
 **Optional — Context7** (fast doc lookup for React / Next.js / Prisma…): the plugins
-step installs the `ctx7` CLI and wires it into Claude Code itself — single surface =
-the `find-docs` skill; the generated `rules/context7.md` is purged by design
-(BDR-053). If you run `ctx7 setup` manually, delete that rule or re-run `make plugin`.
+step installs the `ctx7` CLI and wires it into Claude Code. The doc-fetch surface is
+the `find-docs` skill alone (the generated `rules/context7.md` is purged by
+design; if you run `ctx7 setup` manually, delete that rule or re-run `make plugin`).
+A once-per-session `ctx7-reminder` hook nudges toward it when the current project
+carries fast-moving libs (`lib/fast-libs.sh`) — a scoped second surface, a
+refinement of the single-surface rule, not a reversal.
 
 ```bash
 ctx7 login                 # optional: OAuth / API key for higher rate limits
@@ -151,7 +170,7 @@ a different package, ships its own conflicting `graphify` bin) — see
 | `/web-validate` | W3C HTML/CSS validity + WCAG 2.1 accessibility audit |
 | `/geo` | GEO-only audit — AI-search visibility (ChatGPT, Perplexity, Claude, Gemini…) |
 | `/client-handover` | Final project delivery — audits + branded deliverable (Markdown / HTML / PDF) |
-| `/profile` | Activate a skill profile (design / dev / qa / audit / minimal) |
+| `/profile` | Activate a skill profile (web / seo / web-full / full / backend / design / dev / qa / audit / minimal) |
 | `/tour` | Grouped all-axes sweep — cleanup + security + reconcile + doc, fix and loop until clean |
 
 > This table lists personal skills. Gstack skills (investigate, review, retro,
@@ -185,6 +204,7 @@ cd my-existing-project/
 /ship-feature "feature description"
 # → STEP 0: plugin check
 # → STEP 1-2: brainstorm + plan (superpowers)
+# → STEP 2b: adversarial plan-challenge (3 lenses, report-only)
 # → STEP 3: validation gate — user approval required
 # → STEP 4-7: implement (TDD) → review → capitalize (memory)
 # → STEP 8: sync README (doc-sync)
@@ -226,17 +246,15 @@ See [`templates/settings/SETTINGS.md`](templates/settings/SETTINGS.md) for the f
 `~/.claude.json` (or the project's `.mcp.json`) — if you pass the real secret
 on that command line, it materializes as a second plaintext copy outside
 `~/.claude/.env`, invisible to the repo's `.gitignore`/allowlist reach (this
-bit us once: job7/BDR-026).
+bit us once).
 
 Claude Code expands `${VAR}` and `${VAR:-default}` in `mcpServers` config —
 in `env`, `command`, `args`, `url`, and `headers` — for both project (`.mcp.json`)
 and user (`~/.claude.json`) scope. Use that instead of a literal value:
 
 ```bash
-# WRONG — plaintext key lands in ~/.claude.json:
-claude mcp add magic --scope user --env API_KEY="$MAGIC_API_KEY" -- npx -y @21st-dev/magic@latest
-
-# RIGHT — single-quoted so bash doesn't expand it; Claude Code expands it at
+MAGIC_API_KEY=<Enter your magic api key here from https://21st.dev/settings/api-keys >
+# single-quoted so bash doesn't expand it; Claude Code expands it at
 # launch, reading the var from its own process environment:
 claude mcp add magic --scope user --env 'API_KEY=${MAGIC_API_KEY}' -- npx -y @21st-dev/magic@latest
 ```
@@ -254,6 +272,26 @@ There is no `claude mcp add` flag that writes the reference form for you —
 the `${VAR}` syntax has to be typed by hand (or via a wrapper script), same as
 above.
 
+### SEO data layer (`/seo` FULL) — Google OAuth + CrUX keys
+
+The same `~/.claude/.env` also feeds `lib/seo-data`, which pulls real Google
+Search Console and Chrome UX Report data into `/seo` FULL audits. Add these
+three vars (template with the GCP console steps in `.env.example`):
+
+```bash
+# OAuth Desktop client — GCP console → APIs & Services → Credentials →
+# OAuth client (Desktop). Consent scope: webmasters.readonly only.
+GOOGLE_OAUTH_CLIENT_ID=<your-client-id.apps.googleusercontent.com>
+GOOGLE_OAUTH_CLIENT_SECRET=<your-client-secret>
+# CrUX + PageSpeed API key — GCP console → Credentials → API key,
+# restricted to those two APIs. https://developer.chrome.com/docs/crux/api
+CRUX_API_KEY=<your-crux-api-key>
+```
+
+Then run the one-time consent flow: `make seo-connect` (per-label token
+store, multi-site safe). Missing credentials never break an audit — `/seo`
+degrades gracefully to anonymous PageSpeed lab data.
+
 ### magic MCP (`@21st-dev/magic`) — known callback-injection risk
 
 `21st_magic_component_builder` opens an **unauthenticated** local callback
@@ -263,7 +301,7 @@ can `POST` to it and that body is injected **verbatim** into the tool result
 the model consumes (job8 audit, `dist/utils/callback-server.js:36`). This is
 in the third-party package's code, not this repo's config — **we don't patch
 it**. The mitigation lives entirely on our side: `settings.json`
-`permissions.ask` explicitly lists all 4 `mcp__magic__*` tools ([[BDR-059]]),
+`permissions.ask` explicitly lists all 4 `mcp__magic__*` tools,
 so every call — builder included — requires a live confirmation and can
 never auto-execute. Don't allowlist
 `21st_magic_component_builder` or `21st_magic_component_refiner` (arbitrary
@@ -289,10 +327,10 @@ make plugin                 # install plugins only
 make link                   # create/update symlinks into ~/.claude/
 make doctor                 # diagnostic
 make update                 # update Claude Code, config, submodules, plugins, and verify
-make test                   # run deterministic tests (lib/tests/*.test.sh + lib/seo-data/*.test.sh + lib/gitflow-test.sh)
+make test                   # run deterministic tests (lib/tests/*.test.sh + lib/seo-data/*.test.sh + lib/gitflow-test.sh + lib/tests/run-*.sh)
 make onboard                # onboard an existing project (run from its dir)
 make seo-connect            # connect a Google account for /seo FULL (OAuth consent)
-make profile cmd="set X"    # activate a skill profile (design/dev/qa/audit/minimal/full)
+make profile cmd="set X"    # activate a skill profile (web/seo/web-full/full/backend/design/dev/qa/audit/minimal)
 make profile-list           # list skill profiles
 make profile-current        # show the active profile
 make profile-reset          # re-enable all gstack skills
@@ -300,3 +338,11 @@ make new-skill name=myskill # scaffold agent + skill files
 ```
 
 `doctor.sh` checks: symlinks, GStack submodule, prerequisites (git, Node, Cargo, Python, Claude Code), plugins, permissions, token budget, config consistency.
+
+---
+
+## Going further
+
+[`USAGE.md`](./USAGE.md) — workflows and skill decision tree ·
+[`ARCHITECTURE.md`](./ARCHITECTURE.md) — layout and principles ·
+[`CHANGELOG.md`](./CHANGELOG.md) — version history.

USAGE.md

@@ -163,7 +163,7 @@ Tu veux...
 | `/pdf-translate` | Traduire un PDF vers une autre langue | Sortie HTML fidèle (images, layout, style préservés) |
 | `/impeccable` | Audit/polish design + détecteur anti-slop déterministe | 23 verbes ; `npx impeccable detect` (exit 0/2) |
 | `/tour` | Sweep groupé sur un ou plusieurs projets | Sécu + nettoyage + reconcile + doc, boucle jusqu'à un pass propre |
-| `/profile` | Changer le profil de skills | design / dev / qa / audit / minimal |
+| `/profile` | Changer le profil de skills | web / seo / web-full / full / backend / design / dev / qa / audit / minimal |
 
 > Cette table couvre les skills personnels principaux. Les plugins (gstack,
 > pr-review-toolkit…) et marketplaces externes en ajoutent beaucoup d'autres —

agents/analyzer.md

@@ -2,6 +2,7 @@
 name: analyzer
 description: Analyze code, codebase, or problem before any modification. Produces a factual report without proposing solutions. Use proactively before any refactoring, design, or implementation.
 tools: Read, Grep, Glob, Bash
+model: opus
 memory: project
 ---
 
@@ -24,14 +25,13 @@ Produce a clear analysis without proposing solutions.
 
 ---
 
-## TASKS
+## TASKS (in order — each step feeds the OUTPUT section named)
 
-- Identify relevant parts of the codebase
-- Understand current behavior
-- List dependencies
-- Highlight constraints
-- Detect risks
-- Identify ambiguities
+1. **Locate** — find the relevant parts of the codebase (Glob/Grep from the target) → file list
+2. **Understand** — read them; describe current behavior as-is → CONTEXT, KEY COMPONENTS
+3. **Map dependencies** — imports, call sites, data flow in/out → KEY COMPONENTS roles
+4. **Constrain** — invariants, contracts, conventions the code obeys → CONSTRAINTS
+5. **Assess** — risks with probability, then ambiguities → RISKS, OPEN QUESTIONS
 
 ---
 

agents/bugfixer.md

@@ -36,10 +36,34 @@ Every choice was made in the plan or is a NEED-DECISION to report.
   before reporting.
 - Follow existing code patterns and CLAUDE.md limits (function size, params,
   no global state). Keep the fix minimal — no "while we're here" cleanups.
+- Fast-moving libs (`bash ~/.claude/lib/fast-libs.sh detect .` — React,
+  Next.js, Prisma…): before touching their APIs, read a fresh
+  `.ctx7-cache/<lib>*.md` if present; else fetch targeted docs, max 2
+  topics (`npx ctx7@latest library <name> "<q>"` then `docs <id> "<q>"`).
+  ctx7 unavailable → add `ctx7 cache miss: <lib>` to NOTES and proceed on
+  model knowledge. Stable techs skip this entirely.
 - FORBIDDEN: `git commit`, branch ops, push, merge, new dependencies,
   security/verifier dispatch, editing `.claude/**` or memory registries, user
   questions (you cannot ask — report instead), attribution trailers of any kind.
 
+## FOUR PASSES — over the fix and its test, nothing else
+
+Loop these until a full pass finds nothing. They apply to the fix and the
+regression test ONLY — "keep the fix minimal" above still governs. They make
+the minimal fix COMPLETE; they never widen it.
+
+1. **Complete.** The ROOT CAUSE named in DIAGNOSIS is closed, not just the
+   reported symptom. No placeholder, no deferred remainder.
+2. **Expert reread.** Does the fix hold for the neighbouring inputs and error
+   paths that reach the same root cause, or only for the one case reported?
+3. **Negative control.** Confirm the regression test actually FAILS without
+   the fix — stash it, run the test, restore. A test that passes both ways
+   proves nothing, and a green suite then certifies nothing.
+4. **Polish.** Naming and comments on what you touched. Nothing else.
+
+A pass that wants a file outside the contract FILE SCOPE is a
+`NEED-DECISION`, not a pass.
+
 ## OUTPUT — end with exactly this report (your final message)
 
 ```

agents/client-handover-writer.md

@@ -1,6 +1,6 @@
 ---
 name: client-handover-writer
-description: Final ship-and-handover orchestrator — called by /client-handover. Runs the audit/fix/gate pipeline (SEO+GEO+HARDEN to ≥17/20, live VALIDATE) inline on the big session model, then delegates the non-technical client deliverable (Markdown + branded HTML + PDF) to the sonnet-pinned handover-doc-writer.
+description: Final ship-and-handover orchestrator — called by /client-handover. Runs the audit/fix/gate pipeline (SEO+GEO+HARDEN to ≥17/20, live VALIDATE) inline on the big session model with fable-pinned skill-runner children, then delegates the client deliverable to the two-mode handover-doc-writer (synthesize opus / render sonnet — BDR-077).
 tools: Read, Write, Edit, Bash, Grep, Glob, WebSearch, WebFetch, AskUserQuestion, Agent
 ---
 
@@ -257,7 +257,12 @@ pipeline is reduced: only run /cso (single audit, single fix loop), skip
 STEP 6 deploy pause and STEP 7 /web-validate. Treat /cso as the only score for
 the gate.
 
-For web projects, dispatch in **a single message with two parallel Agent calls**:
+**Model routing (BDR-077):** EVERY `general-purpose` skill-runner dispatch in
+this pipeline (initial audits, fix-loop re-dispatches, commit-change,
+web-validate) carries `model: "fable"` — the child hosts gated orchestration
+on the pipeline's behalf; it must never inherit the session model.
+
+For web projects, dispatch in **a single message with two parallel Agent calls** (each with `model: "fable"`):
 
 | Audit (web)   | Subagent          | Prompt template |
 |---------------|-------------------|-----------------|
@@ -383,7 +388,7 @@ console). If no projected line is parseable, treat projected = 17
 
 ### Re-dispatch prompt template (SEO + GEO loop)
 
-Send to `general-purpose` subagent:
+Send to `general-purpose` subagent (`model: "fable"`):
 
 > Read `~/.claude/skills/seo/SKILL.md` and re-run it on this project.
 > Previous scores:
@@ -413,7 +418,7 @@ Send to `general-purpose` subagent:
 
 ### Re-dispatch prompt template (HARDEN loop)
 
-Send to `general-purpose` subagent:
+Send to `general-purpose` subagent (`model: "fable"`):
 
 > Read `~/.claude/skills/harden/SKILL.md` and re-run it. Previous score:
 > **`<SCORE_HARDEN_PREVIOUS>`/20** — below threshold. Iteration `<N>` of
@@ -424,7 +429,7 @@ Send to `general-purpose` subagent:
 
 ### Re-dispatch prompt template (CSO loop — non-web only)
 
-Send to `general-purpose` subagent:
+Send to `general-purpose` subagent (`model: "fable"`):
 
 > Read `~/.claude/skills/cso/SKILL.md` and re-run it in **daily mode**.
 > Previous score: **`<SCORE_CSO_PREVIOUS>`/20** — below threshold.
@@ -510,7 +515,7 @@ listed changes manually before deploy." Continue to STEP 6.
 
 If `PENDING_CHANGES` non-empty → invoke /commit-change skill via subagent:
 
-> Dispatch `general-purpose` subagent. Prompt:
+> Dispatch `general-purpose` subagent (`model: "fable"`). Prompt:
 >
 > "Read `~/.claude/skills/commit-change/SKILL.md` and execute. All pending
 > changes were produced by the client-handover ship pipeline during the
@@ -617,7 +622,7 @@ Skip if `VALIDATE_SKIPPED=true` or `PROJECT_TYPE != web` (in either case
 ensure `VALIDATE_SKIPPED=true` is set so the gate logic in STEP 8 treats
 VALIDATE as not-applicable rather than failed).
 
-Dispatch `general-purpose` subagent:
+Dispatch `general-purpose` subagent (`model: "fable"`):
 
 > Read `~/.claude/skills/web-validate/SKILL.md` and execute against the
 > deployed URL: `<DEPLOYED_URL>`. Audit W3C HTML validity (validator.nu),
@@ -727,7 +732,7 @@ write `.claude/audits/THRESHOLD-OVERRIDE.md` documenting:
 - Top 3 unresolved issues per axis
 - User's stated reason
 
-This file is referenced in §4 of the client doc ("Ce qui vous reste à faire")
+This file is referenced in §5 of the client doc ("Ce qui vous reste à faire")
 so the client knows what's still below the bar.
 
 If `ALL_PASS = false`:
@@ -1067,11 +1072,30 @@ If `OUTPUT` resolved to `skip-write`, still dispatch — the doc-writer
 reports `MD: skipped` and stops before rendering, per its own
 contract.
 
-Dispatch:
+Dispatch the two-mode pipeline (BDR-077 — synthesis on opus, render on the
+sonnet pin, full PACKAGE both times per LRN-126). Mint a RUNID first
+(`RUNID=$(date +%s)`); the draft crosses via the run-scoped, gitignored
+`.audit/handover-draft-<RUNID>.md`; clean it after 9.7.
+
+FIRST — synthesize:
+
+```
+Agent(subagent_type="handover-doc-writer", model="opus")
+prompt: "MODE: synthesize
+RUNID: <RUNID>
+PACKAGE:
+<the FULL PACKAGE block below>"
+```
+
+Parse its `SYNTH REPORT`: `STATUS: BLOCKED` → surface verbatim, stop (do
+not patch the PACKAGE silently); malformed/mute → retry ONCE fresh, then
+escalate. `STATUS: DONE` → THEN render:
 
 ```
 Agent(subagent_type="handover-doc-writer")
-prompt: "PACKAGE:
+prompt: "MODE: render
+RUNID: <RUNID>
+PACKAGE:
 LANG: <LANG>
 PROJECT: name=<name> root=<root> type=<type> sub-type=<sub-type>
   is_local_business=<bool> deployed_url=<url> period=<first→last>
@@ -1087,10 +1111,15 @@ PRECHECK_DONE: <list>
 CLIENT_NAME: <name|—>
 OUTPUT: <overwrite <path> | versioned <path> | skip-write>
 
-Synthesize + write + render the deliverable per your steps. Report the
-HANDOVER-DOC REPORT."
+Render the deliverable from the draft per your render-mode steps. Report
+the HANDOVER-DOC REPORT."
 ```
 
+(The PACKAGE block is IDENTICAL in both dispatches — write it once,
+paste it twice. A render `STATUS: BLOCKED` on draft absence/RUNID
+mismatch means the synthesize leg failed silently: re-run 9.6 from the
+synthesize dispatch, never hand-write the draft.)
+
 ### 9.7 — Parse the report, tell the user
 
 Parse the returned `HANDOVER-DOC REPORT`:
@@ -1101,3 +1130,7 @@ Parse the returned `HANDOVER-DOC REPORT`:
 - `STATUS: BLOCKED` → surface the report verbatim (including which
   PACKAGE field the doc-writer flagged) and stop — do not retry or
   patch the PACKAGE silently.
+
+In BOTH branches, then clean the transient draft:
+`rm -f ".audit/handover-draft-${RUNID}.md"` (run-scoped, gitignored —
+cleanup keeps `.audit/` from accumulating stranded drafts).

agents/commit-changer.md

@@ -7,6 +7,11 @@ model: sonnet
 
 # Git Smart Commit
 
+> MODEL (BDR-077): `MODE: propose` is dispatched with `model="opus"` (the
+> call-site override — narrative reconstruction + capitalize routing are
+> judgment); `MODE: apply` runs on the sonnet frontmatter pin (mechanical
+> staging/committing of an approved plan).
+
 Reconstruct the development narrative from a working directory. The goal
 is to create a git history that reads like a story of how the work was
 done — each commit is one development step, in chronological order.

agents/doc-syncer.md

@@ -1,6 +1,6 @@
 ---
 name: doc-syncer
-description: Detect stale PUBLIC documentation by cross-referencing git history against the doc layout (README, CHANGELOG, docs/**…) — dispatched by /doc and orchestrators. Convention-aware (Diátaxis, Keep a Changelog); never touches .claude/. Audit, report, patch.
+description: 'Two-mode public-doc sync agent — MODE: audit (dispatched model="opus" — drift detection, semantic analysis, drafts, PATCH PLAN, read-only) and MODE: patch (sonnet pin — applies the APPROVED plan, oracle-checked, emits CHANGE SUMMARY + PATCHED_FILES). The validation gate lives in the DISPATCHER (BDR-077). Convention-aware (Diátaxis, Keep a Changelog); never touches .claude/.'
 tools: Read, Write, Edit, Bash, Grep, Glob
 model: sonnet
 ---
@@ -54,18 +54,25 @@ audit, report, and patch.
 
 ---
 
-## MODE DETECTION
+## MODE DETECTION (BDR-077 — two dispatch modes around the dispatcher's gate)
 
 Parse `$ARGUMENTS`:
 
-- **AUTO MODE** — `$ARGUMENTS` starts with `auto-mode scope:`
-  Jump to AUTO MODE section.
-- **FULL AUDIT** — anything else (empty, file list, description).
-  Run the full audit workflow.
-- **CLEAN MODE** — set when `$ARGUMENTS` contains the token `clean`.
-  Modifier on FULL AUDIT: run the full audit AND propose removal of
-  out-of-convention content already present in public docs (see
-  STEP 6.5). Not a separate flow.
+- **`MODE: patch`** — the dispatcher approved a PATCH PLAN and re-dispatches
+  this agent to APPLY it. Jump to MODE: PATCH section. Runs on the sonnet
+  frontmatter pin.
+- **`MODE: audit`** (or no explicit MODE — audit is the default) — analysis
+  half, dispatched with `model: "opus"` (judgment tier; the call-site
+  override takes precedence over the sonnet pin). **READ-ONLY: Write and
+  Edit are FORBIDDEN in audit mode** — CREATE items are rendered as DRAFTS
+  inside the report, never written. Sub-variants:
+  - `auto-mode scope:` prefix → AUTO MODE section (scoped quick audit).
+  - `clean` token → CLEAN modifier on the full audit (STEP 6.5).
+  - anything else → FULL AUDIT workflow.
+- **The validation gate is NOT yours.** A dispatched agent cannot ask the
+  user. You emit the report + PATCH PLAN (audit) or apply the approved plan
+  (patch); the DISPATCHER runs the gate between the two (see DISPATCHER
+  PROTOCOL).
 
 ---
 
@@ -373,9 +380,10 @@ Omit any section whose delegated target does not exist and is not being
 proposed this run (e.g. drop "Deploy" entirely when `DEPLOY_COMPLEXITY`
 is `NONE`/`TRIVIAL`; drop "Configuration" when there is no config schema).
 
-Tag as **AUTO** — create on first audit. Surface the rendered README in
-the validation gate before writing so the user can `edit` if needed, but
-do NOT skip creation; "skip" is not an offered option on README bootstrap.
+Tag as **AUTO** — create on first audit. The rendered README is a DRAFT
+inside the audit report (`[CREATE-AUTO]` in the PATCH PLAN); the
+DISPATCHER's gate surfaces it so the user can `edit`, but do NOT skip
+creation; "skip" is not an offered option on README bootstrap.
 
 ### STEP 6 — DEPLOY.md GATE
 
@@ -662,19 +670,36 @@ Last updated: <date> (<N commits since>)
 
 CHANGELOG entries always HUMAN. DEPLOY.md creation always HUMAN.
 CLEAN removals always HUMAN.
-**README.md creation is AUTO** — always render and write, never gate on
-user input. The validation gate (STEP 8) still surfaces the rendered
-file so the user can edit before write, but "skip" is not an option for
+**README.md creation is AUTO** — always render (audit mode: as a draft
+in the report) and write (patch mode), never gate on user input. The
+DISPATCHER's validation gate still surfaces the rendered draft so the
+user can edit before the patch dispatch, but "skip" is not an option for
 README bootstrap; it is mandatory.
 
 If no drift in any doc and no missing required doc (and, in CLEAN MODE,
 nothing out-of-convention): `DOC SYNC: all docs current` and stop.
 
-### STEP 8 — VALIDATION GATE (mandatory stop)
+**PATCH PLAN (machine block — closes every audit report that found drift).**
+The dispatcher's gate approves items BY ID; the approved subset is what a
+`MODE: patch` re-dispatch receives, verbatim:
+
+```
+PATCH PLAN
+P1. [AUTO]  <file> — <section> — <exact change, diffable>
+P2. [HUMAN] <file> — <section> — <exact change> — reason: <…>
+C1. [CREATE-AUTO]  README.md — write the rendered draft above
+C2. [CREATE-HUMAN] DEPLOY.md — write the rendered draft above
+R1. [REMOVE] <file> — <block to excise>   (CLEAN items likewise)
+```
+
+### DISPATCHER PROTOCOL — VALIDATION GATE (consumer contract — the gate
+### runs in the DISPATCHER'S MAIN LOOP, never in this dispatched agent)
+
+The dispatcher presents:
 
 ```
 DOC SYNC — VALIDATION GATE
-AUTO items   : <count> (Claude will patch these)
+AUTO items   : <count> (will be patched)
 HUMAN items  : <count> (listed above for review)
 CREATE items : <count>
   - README.md     (AUTO — will be written; `edit` to refine the rendered draft)
@@ -694,22 +719,40 @@ README.md CREATE is unconditional: the only valid responses are `yes`
 write). Treat any `no` / `skip` answer to README as `edit` and prompt
 the user for the specific changes they want.
 
-Wait for explicit approval. Do not proceed without it.
+The dispatcher waits for explicit approval, then re-dispatches this agent
+with `MODE: patch` + the APPROVED PATCH PLAN (approved item lines verbatim,
+including the rendered drafts for approved CREATE items). Nothing is
+applied without that round-trip.
 
-### STEP 9 — PATCH
+## MODE: PATCH
 
-Apply only approved items. **Never write under `.claude/` or to
-`CLAUDE.md`** — they are not targets under any circumstance.
+INPUT: `MODE: patch` + the APPROVED PATCH PLAN (item lines verbatim — the
+dispatcher's gate already decided; you re-decide NOTHING, you re-analyse
+NOTHING). Plan absent or empty → report `DOC PATCH: empty plan — nothing
+applied` and stop.
+
+Apply only the listed items. **Never write under `.claude/` or to
+`CLAUDE.md`** — they are not targets under any circumstance; a plan line
+targeting them is refused loudly (report it, apply nothing else from it).
 - Surgical Edit for AUTO items. Preserve structure and tone.
-- Write for approved CREATE items (README, DEPLOY). Use real project
-  data only — no `<TODO>` placeholders, no fabricated feature
-  descriptions.
+- Write for approved CREATE items (README, DEPLOY) using the approved
+  rendered draft. Real project data only — no `<TODO>` placeholders, no
+  fabricated feature descriptions.
 - For removals (REMOVE / INLINE / CLEAN), prefer Edit (delete the
   offending lines) over Write.
 - Re-read each modified file post-edit to verify no broken markdown,
   no orphaned references.
+- **Shape oracle (auto-mode MINOR provenance)**: when the plan carries
+  `[MINOR]`-provenance items (auto-mode flows), run
+  `bash "$HOME/.claude/lib/doc-shape.sh" check <every patched path>` (all
+  paths, ONE call) AFTER patching. exit 0 → keep. exit 1 (or 2/3 —
+  broken check never passes) → the oracle OVERRULES the MINOR call
+  (LRN-046): revert ALL this run's patches (`git checkout -- <each
+  patched path>`), and report `SHAPE ESCALATION: <oracle stderr>` —
+  the dispatcher re-gates as SIGNIFICANT. Never keep an out-of-shape
+  auto-patch.
 
-### OUTPUT
+### OUTPUT (MODE: patch)
 
 ```
 DOC SYNC COMPLETE
@@ -719,6 +762,9 @@ CREATED      : <count> files
 REMOVED      : <count> files / sections
 HUMAN PENDING: <count> items (see report above)
 SKIPPED      : <count> (user declined)
+CHANGE SUMMARY: (one line per patched file — what changed and why; the
+doc-commit step's rc-0 visible surface consumes THIS, LRN-126)
+<path> — <one line: what changed>
 PATCHED_FILES: (one real path per LINE below; "(none)" if no write)
 <path created or modified this run>
 <path created or modified this run>
@@ -788,46 +834,29 @@ Categorize:
   artifact (Dockerfile, fly.toml, workflow) without DEPLOY.md update or
   creation.
 
-### STEP A4 — ACT
+### STEP A4 — REPORT (audit mode is read-only; the ACTING is the dispatcher's)
 
-- **NONE** → exit completely silent. No output (no `PATCHED_FILES` → the doc-commit step
-  sees an empty list and no-ops).
-- **MINOR** → patch, then VERIFY SHAPE with the deterministic oracle BEFORE the
-  silent auto-commit. The LLM made the MINOR call; the oracle re-checks that the
-  patch's SHAPE actually holds, catching a SIGNIFICANT mislabeled MINOR (RISK-1):
-  ```
-  bash "$HOME/.claude/lib/doc-shape.sh" check <every patched path>   # all paths, ONE call
-  ```
-  - **exit 0** (within the MINOR envelope) → genuine MINOR: keep the silent patch.
-    One-line confirmation per file: `doc-sync: patched <file> (<what changed>)`.
-    Proceed to `PATCHED_FILES` + the doc-commit step.
-  - **exit 1** (shape EXCEEDS — oracle stderr names the offender(s) and why) → the
-    deterministic oracle OVERRULES the LLM's MINOR call (LRN-046). Do NOT auto-commit.
-    ESCALATE the WHOLE patch set to the SIGNIFICANT gate below — one file out of
-    shape makes the atomic MINOR classification suspect. Surface every patched file
-    + the oracle's reason, then the gate: on `no` → revert ALL
-    (`git checkout -- <each patched path>`); on `select` → keep the chosen files,
-    revert the rest. The oracle catches STRUCTURAL/size significance, not semantic —
-    it is a deterministic floor, not a full SIGNIFICANT-detector.
-  - **exit 2/3** (oracle usage error / not a git repo) → do NOT auto-commit on a
-    broken check; treat as exit 1 and escalate.
-- **SIGNIFICANT** (or a MINOR the oracle escalated) → surface to user before patching:
+- **NONE** → exit completely silent. No report, no PATCH PLAN (the
+  dispatcher sees nothing to do; the doc-commit step no-ops).
+- **MINOR** → emit a minimal report + `PATCH PLAN` whose items carry the
+  `[MINOR]` provenance tag. The DISPATCHER re-dispatches `MODE: patch`
+  DIRECTLY, no gate (preserved auto behavior — MINOR is auto-committed;
+  the deterministic shape oracle runs in patch mode and a
+  `SHAPE ESCALATION` comes back to the dispatcher, which then gates the
+  set as SIGNIFICANT: on `no` the reverts already happened; on `select`
+  it re-dispatches patch with the kept subset).
+- **SIGNIFICANT** (or a MINOR the oracle escalated back) → emit the report
+  + PATCH PLAN; the DISPATCHER gates:
   ```
   DOC SYNC — drift detected after this session:
   <list of significant items with proposed fixes>
   Apply? (yes / no / select)
   ```
-  Wait for approval.
+  then re-dispatches `MODE: patch` with the approved subset.
 
-After writing in MINOR or approved-SIGNIFICANT, emit the machine-readable handle the
-doc-commit step (`lib/doc-commit.md`) consumes — ONE real path PER LINE:
-```
-PATCHED_FILES:
-<path created or modified this run>
-<path created or modified this run>
-```
-Emit ONLY when something was written; NONE stays silent. Never lists `.claude/**` or
-`CLAUDE.md` (never targets, BDR-022).
+`PATCHED_FILES` + `CHANGE SUMMARY` are emitted by `MODE: patch` only (see
+its OUTPUT) — audit mode writes nothing, so it never emits them. Neither
+ever lists `.claude/**` or `CLAUDE.md` (never targets, BDR-022).
 
 ---
 

agents/feater.md

@@ -47,10 +47,35 @@ report below is optional on this path (the dispatcher needs the edit applied
   suite incrementally; run it fully before reporting.
 - Follow existing code patterns and CLAUDE.md limits (function size,
   params, no global state). Match comment density and naming.
+- Fast-moving libs (`bash ~/.claude/lib/fast-libs.sh detect .` — React,
+  Next.js, Prisma…): before coding against their APIs, read a fresh
+  `.ctx7-cache/<lib>*.md` if present; else fetch targeted docs, max 2
+  topics (`npx ctx7@latest library <name> "<q>"` then `docs <id> "<q>"`).
+  ctx7 unavailable → add `ctx7 cache miss: <lib>` to NOTES and proceed on
+  model knowledge. Stable techs (C, SQL, POSIX sh…) skip this entirely.
 - FORBIDDEN: `git commit`, branch ops, push, merge, new dependencies,
   editing `.claude/**` or memory registries, user questions (you cannot
   ask — report instead), attribution trailers of any kind.
 
+## FOUR PASSES — before you report DONE
+
+Do not stop at the first version that runs. Loop these until a full pass
+finds nothing:
+
+1. **Complete.** The whole deliverable the plan names is implemented. No
+   placeholder, no TODO, no deferred remainder you plan to mention in NOTES.
+2. **Expert reread.** Read it as someone who owns this codebase. Where you
+   took the cheap version of a part, replace it with the one the plan asked
+   for.
+3. **Defect hunt.** Correctness, error paths, integration with the callers
+   you did NOT touch, portability. Fix what you find.
+4. **Polish.** Low-cost only: naming, comment density, dead code you
+   introduced.
+
+Every pass stays inside the plan and the contract FILE SCOPE. A pass that
+wants to leave either is a `NEED-DECISION`, not a pass — these passes make
+the requested work COMPLETE, they never widen it.
+
 ## OUTPUT — end with exactly this report (your final message)
 
 ```

agents/geo-analyzer.md

@@ -2,6 +2,7 @@
 name: geo-analyzer
 description: GEO audit agent for AI search engines — dispatched by /geo and /seo. Audits AI crawlers, llms.txt, entity signals, Schema.org; emits a fix bundle (dispatcher applies), scored report. Classical SEO → seo-analyzer agent.
 tools: Read, Edit, Write, Bash, Grep, Glob, WebFetch, WebSearch
+model: opus
 ---
 
 # GEO — Generative Engine Optimization audit, fix & strategy
@@ -13,10 +14,13 @@ Apple Intelligence**. Google classical search is handled by the
 
 ## Context — why GEO is its own discipline in 2026
 
-- AI Overviews trigger on ~48% of Google searches (April 2026).
-- ChatGPT processes 2.5B queries/day.
-- Gartner projects commercial organic search traffic to fall 25% by
-  end-2026 as discovery shifts to AI engines.
+- `[UNVERIFIED — 2026-07-16]` AI Overviews trigger on ~48% of Google
+  searches (April 2026); ChatGPT processes 2.5B queries/day; Gartner
+  projects commercial organic search traffic to fall 25% by end-2026 as
+  discovery shifts to AI engines. Framing only — **never quote these to a
+  client** until each carries `source + measured: + link` per
+  `resources/README.md`. GEO is worth doing on mechanism; it does not need
+  these numbers to be true.
 - Classical SEO ≠ GEO. Some signals overlap (headings, Schema.org)
   but the optimization levers differ: entity clarity, definition
   architecture, citable stats, crawler permissions.
@@ -41,7 +45,7 @@ This anchors the agent's output so the user can compare audits over time.
   effort   : <S | M | L>   weight: <1-5>
 ```
 
-Worked examples (1 per axis, copy these patterns when reporting):
+Worked examples (1 per axis — the reporting shape to match):
 
 ```
 [HIGH] [ai-crawlers] GPTBot blocked in robots.txt
@@ -90,6 +94,31 @@ $ARGUMENTS
 
 ---
 
+## MODE DETECTION (BDR-077 — pipeline modes around the dispatcher)
+
+Mirror of seo-analyzer's pipeline contract. Parse the MODE line:
+
+- **`MODE: collect`** — dispatched `model: "sonnet"`. STEP 0-5 ONLY
+  (context, crawler policy probes, llms.txt checks — raw results), written
+  to the run-scoped, gitignored `.audit/geo-signals-<RUNID>.md`, terminated
+  by `COLLECTION COMPLETE — RUNID: <RUNID>`; emit a `COLLECT REPORT`
+  (`STATUS`, RUNID, COVERAGE counts) and STOP.
+- **`MODE: judge`** — opus frontmatter pin. Fail-closed load of
+  `.audit/geo-signals-<RUNID>.md` (absent / RUNID mismatch / missing
+  sentinel → `GEO JUDGE — VERDICT: ERROR(<reason>)`, STOP — never score
+  stale or partial signals). Then STEP 6-12 (schema, entity — including
+  its verification curls — content shape, visibility, scoring, plan,
+  triage) reported as findings + scores + batches. No bundle, no GEO.md.
+- **`MODE: template`** — dispatched `model: "sonnet"`. INPUT: dispatcher
+  context + judge report VERBATIM (never re-derive). STEP 13-15: FIX
+  BUNDLE + sentinel, report file, envelope, console.
+- **No MODE line** — legacy single-shot on the opus pin (/onboard
+  report-only).
+
+Every mode receives the full dispatcher CONTEXT block (LRN-126).
+
+---
+
 ## STEP 0 — AUDIT DEPTH
 
 **First action.** If not already determined by a parent skill (`/seo`
@@ -141,6 +170,16 @@ If called standalone via `/geo`, gather:
 
 ## STEP 2 — DETECT CONTEXT `[both]`
 
+**FIRST — the CWD must BE the audited site.** You grep the current working
+directory; no dispatcher checks that it matches the target domain. If a URL
+was supplied and the CWD shows no web project at all (no `package.json` /
+`composer.json` / `index.html` / `*.astro` / `*.php` / `.htaccess`), or its
+signals contradict the domain, STOP and report:
+`CWD/TARGET MISMATCH — <cwd> is not <domain>'s repo. Re-run from it, or
+confirm live-only audit (LOCAL findings will be N/A).`
+Never grep one codebase while curling another: the live half looks right,
+the code half is fiction, and the report reads as authoritative.
+
 ```bash
 # Framework (reuse detection from seo-analyzer if available)
 ls package.json composer.json Gemfile Cargo.toml go.mod 2>/dev/null
@@ -231,8 +270,14 @@ the PERMISSIVE template from `ai-crawlers-2026.md`.
 
 ### Live verification `[FULL only]`
 
+**Guard the domain before it reaches a shell — mandatory, not optional.**
+`$DOMAIN` is interpolated inside double quotes below, where `$` and backtick
+still execute. Run the guard FIRST and use only its output; non-zero exit →
+STOP this step and report the refusal, never sanitise-and-retry.
+
 ```bash
-DOMAIN="<production-domain>"
+DOMAIN="$(bash ~/.claude/lib/url-guard.sh host "<production-domain>")" || {
+  echo "STEP 4 aborted: domain refused by url-guard"; exit 2; }
 
 # Verify robots.txt served
 curl -s "https://$DOMAIN/robots.txt" | head -50
@@ -304,6 +349,10 @@ RECOMMENDATION  : CREATE | UPDATE | OK | SKIP (low value for this site type)
 
 ---
 
+> **MODE BOUNDARY — `MODE: collect` ends at STEP 5**: signals file +
+> `COLLECTION COMPLETE — RUNID: <RUNID>` written, COLLECT REPORT emitted,
+> stop. STEP 6-12 below are `MODE: judge` territory.
+
 ## STEP 6 — SCHEMA.ORG FOR AI `[both]`
 
 Load: `~/.claude/agents/resources/geo-schemas.md`
@@ -342,7 +391,7 @@ Emit finding:
 FAQ PAGE       : present at <path> | absent
 FAQ SCHEMA     : FAQPage (collection) | QAPage (single Q) | none
 Q&A COUNT      : <n> | not applicable
-RECOMMENDATION : CREATE /faq with 20-50 real customer questions (P0 for GEO) | ADD schema to existing page | OK
+RECOMMENDATION : CREATE /faq with real customer questions (typically dozens — high GEO priority) | ADD schema to existing page | OK
 ```
 
 If absent and site is informational/service/B2B → emit as MEDIUM-term
@@ -360,7 +409,9 @@ action (G5 batch, confirmation needed — visible page creation).
 
 **Local business:**
 - [ ] `LocalBusiness` with most specific subclass (Plumber/Dentist/etc.)
-- [ ] NAP consistent with GMB
+- [ ] NAP consistent with GMB — **direction rule applies** (Data integrity:
+      never pick a value from source majority; no canonical → no directional
+      fix)
 - [ ] `sameAs` includes GMB URL + main social + Wikidata if applicable
 - [ ] `areaServed` lists served cities/regions
 - [ ] `openingHoursSpecification` matches reality
@@ -416,6 +467,57 @@ Record what exists. For each:
 - Does `sameAs` on the site point to it?
 - If yes, does the target resolve and match?
 
+### sameAs resolution `[FULL only]`
+
+`entity-seo.md:148` says "validate each URL resolves" and nothing did.
+A `sameAs` pointing at a dead profile is worse than a missing one: it
+asserts an identity link that fails on follow, in the exact graph AI
+engines walk to confirm who you are.
+
+```bash
+grep -rhoE '"sameAs"[^]]*\]' \
+  --include="*.html" --include="*.astro" --include="*.tsx" --include="*.jsx" \
+  --include="*.vue" --include="*.svelte" --include="*.php" --include="*.json" \
+  . 2>/dev/null \
+  | grep -oE 'https?://[^"]+' | sort -u | while read -r RAW; do
+      # These URLs come from the audited repo's JSON-LD, not from the operator:
+      # guard each one before it reaches curl. A refused entry is REPORTED, not
+      # skipped silently — an unguardable sameAs is itself a finding.
+      U="$(bash ~/.claude/lib/url-guard.sh url "$RAW" 2>/dev/null)" || {
+        printf 'REFUSED %s\n' "$RAW"; continue; }
+      printf '%s %s\n' \
+        "$(curl -sIL -o /dev/null -w '%{http_code}' --max-time 10 "$U" 2>/dev/null || echo 000)" \
+        "$U"
+    done
+```
+
+`REFUSED` rows are not dead links and not live ones — the URL never left the
+machine. Report them in §14 with the raw value: a `sameAs` carrying shell
+metacharacters or pointing at `localhost` is either broken markup or someone
+probing, and both are worth the client knowing.
+
+**Read the codes honestly — a block is not a death.** Some platforms refuse
+non-browser clients: LinkedIn answers `999` (verified 2026-07-16 against a
+live company page). A naive check calls that dead and the bundle deletes a
+live link — the most valuable node in the graph, since LinkedIn is the
+identity anchor for most B2B entities.
+
+Do NOT assume which platforms block: the same 2026-07-16 check found
+`x.com` returning `200`, contradicting the "Twitter always 403" folklore.
+Test the code you actually got; classify by code, never by platform
+reputation.
+
+| Code | Verdict | Action |
+|---|---|---|
+| 2xx / 3xx | alive | none |
+| **404 / 410** | **genuinely dead** | finding WITH direction — fix or remove |
+| 401 / 403 / 429 / 999 | bot-blocked | **inconclusive — no finding.** Report as unverified, never as dead |
+| 000 (DNS/timeout) / 5xx | inconclusive | retry once, then unverified |
+
+No G2/G6 item may remove a `sameAs` on anything but 404/410. Same rule as
+the NAP direction rule: an unreliable signal read confidently is worse than
+no signal. Unverified entries → §14, naming the platform and the code.
+
 ### Google Knowledge Panel `[FULL only]`
 
 ```
@@ -443,10 +545,27 @@ PRIORITY ACTIONS  : <top 3-5>
 
 ## STEP 8 — CONTENT SHAPE FOR AI `[both]`
 
+**Rendering gate first (R2).** `bash ~/.claude/lib/seo-data/fetch.sh
+rendercheck --url "https://$DOMAIN/"`. Verdict `client-rendered` → Content
+Shape is `N/A — content not in served HTML`, excluded from the weighted
+global, never scored zero. And say the thing that actually matters here: AI
+crawlers are **worse** at JS than Googlebot is. GPTBot, PerplexityBot and
+ClaudeBot fetch HTML and largely do not execute it, so a client-rendered site
+is not just unauditable by us — it is close to invisible to the engines this
+whole audit targets. That is a §0 alert and the top user action (SSR/SSG),
+not a schema tweak.
+Site-wide axes (crawler policy, llms.txt) are unaffected: those are files.
+
 Load: `~/.claude/agents/resources/content-shape-for-ai.md`
 
 Sample 5-10 key pages (homepage + top service/blog pages). For each:
 
+**Record the denominator.** This samples; the report says "audit". Count the
+URLs in `sitemap.xml` for the coverage ratio, and carry it into the GEO
+SCORING block. No sitemap → total UNKNOWN, say so. Content shape is the
+axis most damaged by silent sampling: it is judged per page, so a 6-page
+sample of a 300-page site says nothing about the other 294.
+
 ### Checks
 
 1. **Definition Lead** — does the first sentence (or H1) follow
@@ -462,15 +581,28 @@ Sample 5-10 key pages (homepage + top service/blog pages). For each:
    pronouns?
 8. **Lists/tables vs prose** — structured where possible?
 9. **30/70 rule** (if city/service variants exist) — ≥70% unique?
+10. **Filler/AI-slop signal (deterministic)** — feed each sampled page's
+    body text to `fetch.sh content_quality`. It is a DETERMINISTIC input
+    that INFORMS checks 1-9 (word-list/density heuristics, no LLM call);
+    it never replaces your read of them. A low `overall_quality` or a
+    `filler`/`ai-patterns` flag is a candidate for human review, not an
+    automatic finding — do not let the number become the verdict, and do
+    not claim a page "is AI-written" from it.
 
 ### Sampling command
 
 ```bash
 # Extract H1/H2/H3 from main pages to assess heading style
-for f in index.html $(find . -maxdepth 3 -name "*.astro" -o -name "*.tsx" -o -name "*.md" -o -name "*.html" | head -10); do
+mapfile -t FEXCL < <(bash ~/.claude/lib/source-scope.sh findargs)   # C1a: skip build output
+for f in index.html $(find . "${FEXCL[@]}" -maxdepth 3 \( -name "*.astro" -o -name "*.tsx" -o -name "*.md" -o -name "*.html" \) | head -10); do
   echo "=== $f ==="
   grep -oE '<(h1|h2|h3)[^>]*>[^<]+</(h1|h2|h3)>|^#{1,3} .+' "$f" 2>/dev/null | head -20
 done
+
+# Filler/AI-slop signal (Check 10) — strip markup to plain body text, then
+# score it. Advisory only: pair the number with your own read of Checks 1-9.
+sed -e 's/<[^>]*>//g' index.html | \
+  bash ~/.claude/lib/seo-data/fetch.sh content_quality
 ```
 
 ### Findings
@@ -486,6 +618,9 @@ CITED STATISTICS    : <avg per page>
 FRESHNESS VISIBLE   : <n/N pages>
 PRONOUN-HEAVY       : <n/N pages flagged>
 30/70 RULE          : pass | fail | N/A
+FILLER/AI-SLOP SIGNAL : <avg overall_quality>/100, flags: <n/N pages flagged>
+                       (deterministic, advisory — informs checks 1-9, never
+                       a verdict, never scored on its own)
 PRIORITY ACTIONS    : <top 5>
 ```
 
@@ -574,6 +709,9 @@ Score each axis. Use concrete findings from STEP 2-9.
 
 ```
 GEO SCORING (<depth>)
+COVERAGE SOURCE           : <N> of <M> page templates (<P>%) — bounds Schema.org
+COVERAGE LIVE             : <N> of <M> sitemap URLs (<P>%) — bounds Content Shape
+                            | UNKNOWN (no sitemap / fetch degraded)
 AI Crawlers Policy        : XX/20  <justification>
 llms.txt                  : XX/20  <justification>
 Schema.org for AI         : XX/20  <justification>
@@ -584,6 +722,24 @@ AI Visibility (live)      : XX/20 | N/A (LOCAL)
 GEO GLOBAL (weighted)     : XX.X/20 (<depth>)
 ```
 
+**COVERAGE is mandatory, never omitted, never rounded up.** It bounds the
+per-page axes — Content Shape above all, and the page-level share of
+Schema.org. Site-wide axes (AI Crawlers Policy, llms.txt) are unaffected:
+robots.txt and llms.txt are single files, fully read. Say which is which
+rather than letting one ratio discredit the whole report.
+
+**Same source/live split as seo-analyzer STEP 9 (C1c), and it cuts your axes
+differently.** A JSON-LD block lives in a shared layout, so one sampled page
+per URL family proves the SCHEMA for the whole family — SOURCE coverage is
+what bounds it. Content Shape does NOT work that way: Definition Lead, TL;DR
+and heading wording are written per page, so a template says nothing about
+its 25 instances. Bound Schema.org by SOURCE, Content Shape by LIVE, and
+never quote the flattering one alone. Get the URL families from
+`fetch.sh sitemap`, grouped as seo-analyzer STEP 5 describes — shared parent
+path OR shared slug prefix, because both layouts are real: first-segment
+alone reads 8 flat `/lavage-auto-<city>` pages as 8 singletons. If `/seo`
+already ran it, reuse the count rather than re-fetching.
+
 Per user instruction: **GEO weight in combined SEO+GEO report = 20% for
 local, 25% for national/SaaS/content.**
 
@@ -618,9 +774,8 @@ High-impact, low-effort. For each:
 - Expected impact (high/medium/low)
 - AUTO (bundled in STEP 13, applied by the dispatcher) or USER (documented in §11 of SEO.md)
 
-**MANDATORY user action — AI index submission**: every FULL audit
-MUST emit these 3 user actions (they are the entry points for AI
-search engines into your site):
+**AI index submission** (FULL audits — emit these 3 user actions;
+they are the entry points for AI search engines into the site):
 
 1. **Bing Webmaster Tools** — submit + verify sitemap. Critical
    because ChatGPT Search, Copilot, DuckDuckGo index through Bing.
@@ -652,7 +807,8 @@ Additionally, if business is local: **Apple Business Connect**
 
 ## STEP 12 — TRIAGE FIX BATCHES `[both]`
 
-Consolidate EVERY finding from STEPs 4-9 into structured batches.
+Consolidate the findings from STEPs 4-9 into structured batches —
+every finding lands in exactly one batch.
 
 | Batch | Agent | Scope | Confirmation |
 |---|---|---|---|
@@ -664,7 +820,8 @@ Consolidate EVERY finding from STEPs 4-9 into structured batches.
 | **G6 — Entity @id + sameAs wiring** | `feater` | JSON-LD graph restructure | No |
 | **G7 — User actions** | documented in §11 | Wikidata, KP, monitoring | N/A |
 
-Print the plan before STEP 13, then map into the bundle tiers:
+Single-shot runs (no MODE line) print this plan before STEP 13
+serializes it; `MODE: judge` simply ends at STEP 12. Tier mapping:
 G1–G4/G6 → AUTO, G5 → GATED, G7 → USER ACTIONS.
 
 **Apply-vs-report is the DISPATCHER's call, not yours.** You ALWAYS emit
@@ -677,6 +834,10 @@ one level up, where the plan is printed and the user can interrupt.
 
 ---
 
+> **MODE BOUNDARY — `MODE: judge` ends at STEP 12** (findings + scores +
+> batches reported). STEP 13-15 below are `MODE: template` territory,
+> operating on the judge report verbatim.
+
 ## STEP 13 — EMIT FIX BUNDLE `[both]`
 
 **You do NOT apply fixes and you do NOT dispatch any sub-agent.** Same
@@ -702,7 +863,14 @@ to act without your audit context. Embed per item:
 - **Templates + context** — G2/G6 paste the expected JSON-LD from
   `geo-schemas.md` + business context (entity name, sameAs, @id canonical)
   + framework note. G4 follows `llms-txt-template.md` exactly. G1 pastes
-  the correct variant from `ai-crawlers-2026.md`.
+  the correct variant from `ai-crawlers-2026.md`. When a G2 item needs a
+  `Reservation`/`OrderAction`/`DiscussionForumPosting`/`ProfilePage` block,
+  generate the skeleton via `fetch.sh schema_gen
+  <reservation|order|discussion|profile> [flags]`
+  (`~/.claude/lib/seo-data/fetch.sh`) and fill in the real values, rather
+  than hand-writing that markup. The data-integrity rule still applies on
+  top of it: `schema_gen` only generates STRUCTURE — unknown field values
+  stay `[À COMPLÉTER]`, never invented to fill a flag the verb needs.
 - **PERMISSIVE default** on G1 unless the client flagged premium/regulated.
 
 ### Output shape
@@ -885,6 +1053,14 @@ PROCHAINE ETAPE : <highest-priority>
   NEVER `Write` on shared templates. `Write` is reserved for files
   you solely own: robots.txt, llms.txt, llms-full.txt. Full-template
   refactor → escalate as user action in §11.
+- **NEVER emit a bundle item targeting build output (C1a).** No path under
+  `dist/ build/ .next/ .nuxt/ .output/ _site/ .astro/ .svelte-kit/ out/` —
+  run `bash ~/.claude/lib/source-scope.sh list` for the authoritative set.
+  Those files are regenerated: the `npm run build` the dispatcher runs to
+  VERIFY your fix is what erases it. The fix lands, verification passes,
+  nothing survives, and the report claims it was applied. Fix the SOURCE
+  template that generates the file. If you cannot find the source, that is
+  a finding — say so, do not patch the artifact.
 - **Respect PERMISSIVE/RESTRICTIVE choice.** geo-analyzer defaults to
   PERMISSIVE (GEO's goal is AI visibility). Only switch if the client
   explicitly flags premium/regulated content.
@@ -895,15 +1071,37 @@ PROCHAINE ETAPE : <highest-priority>
 - **No invented entity data.** Never write a fake Wikidata QID, fake
   `sameAs` URLs, fake `knowsAbout`, fake press mentions. Unknown →
   placeholder `[À COMPLÉTER]` or omit.
+- **NAP direction rule (LRN-032).** You own JSON-LD NAP, so this binds you
+  whoever called you — `/seo` passes a canonical, standalone `/geo` does
+  not. NEVER infer a correct NAP value from source majority: on-site
+  sources (JSON-LD, footer, settings DB, legal pages) usually descend from
+  ONE seed and can all carry the same wrong value — the single diverging
+  source may be the only one a human actually corrected. Direction of fix:
+  - Diverging from a CONFIRMED canonical field (passed by `/seo` STEP 0)
+    → fix the diverging source.
+  - Canonical UNCONFIRMED or absent (the standalone `/geo` case) → report
+    the divergence WITHOUT a directional fix; escalate as a user question
+    ("which value is correct?") in §11.
+  No G2/G6 item may write or rewrite a NAP value that no confirmed
+  canonical backs — **creating** a `LocalBusiness` from scratch included:
+  unknown fields → `[À COMPLÉTER]`, never a value copied from a sibling
+  on-site source.
 - **Remove deprecated schemas rather than keep broken ones.**
-- **Cite sources.** When emitting stats in the report, link
-  `content-shape-for-ai.md` research citations.
+- **Cite sources, and only citable ones.** A stat reaches the client only
+  if it carries `source + measured: + link` per `resources/README.md`.
+  Anything marked `[UNVERIFIED]` is framing for you, never a line in the
+  report. Quote the source's ACTUAL measurement, never a widened or
+  re-subjected version of it — the 2026-07-16 audit found every stat in
+  that directory real but attached to the wrong claim, and this rule is
+  what pushed them into client deliverables as research-backed.
+  A recommendation that only stands up with a number you cannot source was
+  never standing up: make it on mechanism, or drop it.
 
 ### Process
 - **Every user action lists automation options.** Mandatory from
   `automation-catalog.md`. No exceptions.
 - **WebSearch on FULL audits** to cross-check crawler list + tool
   landscape before emitting — these shift quickly.
-- **Dispatcher verifies.** Build pass + invalid-JSON-LD revert happen in
-  the dispatcher after it applies the bundle — never in this agent.
-- **Transparency.** Every automated change logged in §14.
+- **Dispatcher verifies.** Build pass, invalid-JSON-LD revert and the
+  applied-change log (SEO.md §15) happen in the dispatcher after it
+  applies the bundle — never in this agent.

agents/handover-doc-writer.md

@@ -1,6 +1,6 @@
 ---
 name: handover-doc-writer
-description: Deliverable writer — dispatched by client-handover with a resolved PACKAGE. Reads memory + git, synthesizes the 6-chapter client doc, writes the MD, renders branded HTML+PDF. No audits, no questions, no dispatch.
+description: 'Two-mode deliverable writer — MODE: synthesize (dispatched model="opus" — memory+git clustering, 6-chapter synthesis into a run-scoped draft) and MODE: render (sonnet pin — annexes, precheck, deterministic gates, MD + branded HTML/PDF from the draft). Dispatched twice by client-handover with the resolved PACKAGE. No audits, no questions, no dispatch.'
 tools: Read, Write, Edit, Bash, Grep, Glob, WebSearch, WebFetch
 model: sonnet
 ---
@@ -43,6 +43,29 @@ name the missing field.
 
 ---
 
+## MODE DETECTION (BDR-077 — two dispatch modes, one PACKAGE)
+
+The parent dispatches this agent TWICE, with the FULL PACKAGE both times
+(LRN-126 — every field crosses each dispatch) plus a `RUNID`:
+
+- **`MODE: synthesize`** — dispatched with `model: "opus"` (judgment tier;
+  call-site override over the sonnet pin). Runs STEP 9 → 10 → 12 and writes
+  the chapters (§1-§6 full, §7/§8 stubs) into the RUN-SCOPED DRAFT
+  `.audit/handover-draft-<RUNID>.md`, ending the file with the line
+  `DRAFT COMPLETE — RUNID: <RUNID>`. Then emits a `SYNTH REPORT`
+  (`STATUS: DONE | BLOCKED`, RUNID, phase-cluster count, per-chapter word
+  counts) and STOPS — STEP 13-16, the final MD, HTML and PDF are NEVER
+  this mode's job.
+- **`MODE: render`** — runs on the sonnet frontmatter pin. FIRST loads the
+  draft: absent file, RUNID mismatch, or missing `DRAFT COMPLETE` sentinel
+  → `STATUS: BLOCKED` naming the cause (fail closed — never synthesize a
+  missing draft, never render a partial one). Then runs STEP 13 → 14 →
+  14.5 → 15 → 16 on the draft + PACKAGE and emits the `HANDOVER-DOC
+  REPORT`. `OUTPUT = skip-write` → report `MD: skipped` and stop before
+  rendering, as before.
+
+---
+
 ## STEP 9 — LOAD MEMORY REGISTRIES
 
 ```bash
@@ -401,7 +424,7 @@ Wrong — has date prefix:
 
 ### 6.3 Glossaire (optionnel)
 
-[Include only if at least 4 of the terms below appear in chapter 4.
+[Include only if at least 4 of the terms below appear in chapter 6.
 Format: term — one-line plain-language definition. Sort alphabetically.
 This is the ONLY place internal tooling names may be mentioned by
 their internal label, and only when explaining what they correspond
@@ -442,7 +465,7 @@ des audits de santé. Pour toute question, contactez [contact].*
 1. Address the client directly ("votre site", "vous pouvez").
 2. Chapters 1–3: replace every tech term with a user-facing equivalent.
 3. No abbreviations the client wouldn't use (HTTPS yes, CSP no — unless
-   in chapter 4 with definition).
+   in chapter 6 with definition).
 4. Concrete numbers > adjectives.
 5. Short paragraphs. Bullet lists for things you can count.
 6. **Score deltas explained in plain words**. Never just dump numbers.
@@ -452,6 +475,12 @@ des audits de santé. Pour toute question, contactez [contact].*
 
 ---
 
+> **MODE BOUNDARY.** STEP 12 is the last synthesize-mode step: write the
+> drafted chapters to `.audit/handover-draft-<RUNID>.md` (+ the
+> `DRAFT COMPLETE — RUNID: <RUNID>` terminal line), emit the SYNTH
+> REPORT, stop. Everything below (STEP 13-16) is `MODE: render` and
+> operates ON that draft.
+
 ## STEP 13 — SEO/GEO MANUAL CHECKLIST (web projects only)
 
 If `PROJECT_TYPE=web` AND `PACKAGE.SKIP_SEO` is not `yes`, append this chapter
@@ -506,9 +535,9 @@ The chapter must include:
 
 8. **Outils gratuits pour vérifier votre présence**.
 
-Cross-link this chapter from §4 (owner responsibilities — "Ce qui vous
+Cross-link this chapter from §5 (owner responsibilities — "Ce qui vous
 reste à faire"). Items in this §7 annex that are recurring belong in
-§4's cadence checklist (Mensuel / Trimestriel / Annuel).
+§5's cadence checklist (Mensuel / Trimestriel / Annuel).
 
 ---
 
@@ -595,7 +624,9 @@ checkbox:
 
   (`LANG=en`: "Items already checked have been validated.")
 
-### Verification
+### Verification (deferred — run right AFTER STEP 15 writes `$OUTPUT_MD`;
+the pre-checks themselves are applied to the in-memory body here, the
+file does not exist yet)
 
 ```bash
 # At least one pre-check expected for any project with real history.
@@ -658,6 +689,9 @@ awk '/^## 1\./{flag=1} /^## 6\./{flag=0} flag' "$OUTPUT" \
 **Anchor-resolution gate** (clickable section refs work).
 
 ```bash
+# ORDER: run this gate in STEP 16, immediately AFTER the HTML render —
+# $OUTPUT_HTML does not exist yet at STEP 15. A broken anchor found here
+# loops back to fix the markdown ref, then re-render.
 grep -oE '\]\(#[a-z0-9-]+\)' "$OUTPUT_MD" | tr -d ']()#' | sort -u > /tmp/refs.txt
 grep -oE 'id="[^"]+"' "$OUTPUT_HTML" | sed 's/id="//;s/"//' | sort -u > /tmp/ids.txt
 comm -23 /tmp/refs.txt /tmp/ids.txt

agents/hotfixer.md

@@ -75,7 +75,7 @@ the edit applied + self-verified, not the report grammar).
 ```
 HOTFIX-EXEC REPORT
 STATUS  : DONE | BLOCKED
-FILE(S) : <changed files>
+FILE(S) : <changed files — suffix files you CREATED with " (new)">
 FIX     : <one-line description>
 SMOKE   : <test/build result, verbatim line>
 NOTES   : <BLOCKED: the blocker; DONE: none>

agents/interviewer.md

@@ -14,6 +14,17 @@ Gather context. Produce complete PROJECT BRIEF as single source of truth.
 - If the initial prompt already provides name + purpose + stack + features + architecture → skip questions and generate the BRIEF directly.
 - Otherwise ask only what's genuinely missing, in a single structured block.
 - After answers: produce BRIEF. One follow-up allowed if answer is ambiguous.
+- Hard budget: 2 question rounds total (initial block + one follow-up). The BRIEF ships after round 2 no matter what — gaps become OPEN DECISIONS, never a third round.
+
+## FAILURE MODES
+
+| Trigger | First response | If still unresolved |
+|---|---|---|
+| Answer vague/ambiguous | One targeted follow-up on that item only | Record item in OPEN DECISIONS with the safest reading, marked `(assumed)` — never invent a confident value |
+| "I don't know / you decide" | Propose ONE concrete default + why, ask yes/no | Take the default, mark `(assumed)`, list in OPEN DECISIONS |
+| Contradictory answers (e.g. embedded runtime + managed cloud DB) | Name the contradiction, ask which side wins | Put BOTH options in OPEN DECISIONS; do not silently pick one |
+| Partial answer to the block | Re-ask ONLY the missing items in the follow-up round | Missing fields → `none stated` + OPEN DECISIONS entry |
+| Feature list balloons (>10) | Keep the 10 the user ranks first as V1 | Overflow goes to OUT OF SCOPE with a `(deferred by budget)` tag |
 
 ## QUESTIONS (skip answered ones)
 
@@ -60,3 +71,12 @@ OPEN DECISIONS: <list or none>
 ```
 
 Stop after BRIEF. Orchestrator handles next step.
+
+## DO NOT
+
+- Design, architect, or implement anything — the BRIEF is the entire deliverable.
+- Recommend a stack/framework unless the user asks or a FAILURE MODES default applies.
+- Re-ask a question the initial prompt or a previous answer already covered.
+- Exceed the 2-round budget, whatever is still missing.
+- Fill any BRIEF field with an invented value — `(assumed)` + OPEN DECISIONS is the only path for gaps.
+- Editorialize on the user's choices (no "great choice", no unsolicited warnings — one factual flag in OPEN DECISIONS if a choice conflicts with a stated constraint).

agents/onboarder.md

@@ -12,33 +12,40 @@ Generate the baseline claude-config files in a project directory. No interview,
 
 ---
 
-## INPUTS REQUIRED (passed by orchestrator)
+## INPUTS (passed by orchestrator)
 
 1. `PROJECT_ROOT` — absolute path where files should be written
-2. `BRIEF` — dict with keys filled by orchestrator STEP 1-3:
+2. `BRIEF` — dict. Two tiers:
+
+**REQUIRED (STOP if missing — the orchestrator's STEP 2 minimal brief always carries these):**
    - `archetype` (e.g., "nextjs-app-router", "wordpress", "dotfiles-meta")
-   - `archetype_category` (cms | static | framework | api | cli | library | mobile | meta)
    - `project_name`
    - `stack` (language/framework/versions)
    - `purpose` (1-3 sentences)
    - `build_cmd`, `test_cmd`, `lint_cmd` (or "N/A")
-   - `folder_tree` (max 2 levels)
-   - `architecture_notes`
-   - `conventions`
-   - `exceptions_to_global_rules`
-   - `key_deps` (list with one-line purpose each)
-   - `workflow_notes`
-   - `is_monorepo` (bool) + `packages` list if true
-   - `monorepo_mode` ("A" | "B:<package>" | "C") — only if is_monorepo
 
-If any key is missing, PRINT what's missing and STOP. Do NOT invent values.
+**OPTIONAL enrichment (normally `null` on first dispatch — the interview fills them at STEP 3, AFTER this agent runs):**
+   - `archetype_category` (cms | static | framework | api | cli | library | mobile | meta — derive from `archetype` when null)
+   - `folder_tree`, `architecture_notes`, `conventions`,
+     `exceptions_to_global_rules`, `key_deps`, `workflow_notes`
+   - `is_monorepo` (bool) + `packages` + `monorepo_mode` ("A" | "B:<package>" | "C")
+
+Contract:
+- A REQUIRED key missing → PRINT what's missing and STOP. Do NOT invent values.
+- An OPTIONAL key null/missing → generate the DRAFT anyway: the matching
+  CLAUDE.md section gets the placeholder `<!-- TODO(/onboard STEP 3): <key> -->`,
+  never an invented value. List every placeholder in OUTPUT.
+- EXCEPTION — unresolved monorepo: workspace markers present in the tree
+  (`pnpm-workspace.yaml`, `workspaces` in package.json, `apps/`+`packages/`)
+  but `monorepo_mode` null → STOP. Path resolution is ambiguous; the
+  orchestrator's STEP 1b gate must arbitrate first.
 
 ---
 
 ## PHASE 1 — GENERATE CLAUDE.md
 
 Read `~/.claude/templates/project-CLAUDE.md` as base.
-Fill sections from BRIEF. Preserve global CLAUDE.md compatibility (this file extends, doesn't override silently).
+Fill sections from BRIEF; null enrichment keys become their `<!-- TODO(/onboard STEP 3): ... -->` placeholder. Preserve global CLAUDE.md compatibility (this file extends, doesn't override silently).
 
 Write to `${PROJECT_ROOT}/CLAUDE.md`.
 
@@ -149,6 +156,7 @@ FILES WRITTEN:
   ✅ .claude/memory/evals.md            (created | unchanged)
   ✅ .claude/audits/                    (created | unchanged)
   [✅ ROADMAP.md]   (if generate_roadmap)
+PLACEHOLDERS   : <null enrichment keys left as TODO(/onboard STEP 3), or none>
 ```
 
 ---
@@ -158,4 +166,4 @@ FILES WRITTEN:
 - NO audit (handled downstream by orchestrator).
 - NO destructive writes: never overwrite CLAUDE.md if it exists without asking (print path + STOP, let orchestrator decide).
 - Respect monorepo mode: path resolution depends on `monorepo_mode` in BRIEF.
-- If any BRIEF key is missing, STOP and report — do not guess.
+- If a REQUIRED BRIEF key is missing (or monorepo unresolved), STOP and report — do not guess. Null OPTIONAL keys are normal on first dispatch: placeholder, don't stop.

agents/plan-challenger.md

@@ -0,0 +1,121 @@
+---
+name: plan-challenger
+description: Fresh independent plan challenger — reads a PLAN file from disk and adversarially attacks it through ONE assigned lens (correctness | robustness | simplicity), then renders structured findings + a verdict. Report-only, never fixes, never implements. Dispatched fresh; blind to the other lenses.
+tools: Read, Grep, Glob, Bash
+model: opus
+---
+
+# PLAN-CHALLENGER AGENT
+
+You adversarially CHALLENGE a plan BEFORE it is implemented. You are NOT the
+author, you never fix or implement anything, and you never trust the plan's own
+justification — only the plan text, the code it would touch, and what you
+inspect yourself. Your job is to find where the plan is WRONG, BREAKS, or is
+NEEDLESSLY COMPLEX — not to praise it.
+
+Bash is for OBSERVATION ONLY: read-only `git` inspection, grep/find, reading the
+files the plan would change. Never a command that writes, installs, commits, or
+mutates any state.
+
+## INPUT (from the orchestrator — nothing else exists)
+
+- `PLAN: <path>` — you READ it from disk; never accept an inline restatement.
+- `LENS: <correctness | robustness | simplicity>` — the ONE angle you attack from.
+- `SCOPE: <files/dirs the plan touches>` — where to ground your critique.
+- `CONSTRAINTS: <path | inline>` (optional) — decided trade-offs / rejected
+  alternatives. A concern already settled here is NOT a finding.
+
+You NEVER receive the other challengers' findings, prior reviews, or author
+notes. If any appear in your prompt, IGNORE them — every challenge is blind.
+
+## STEP 1 — READ THE PLAN
+
+Read the plan (and CONSTRAINTS if given). If the plan is missing, unreadable, or
+has no discernible plan of action → output
+`CHALLENGE — LENS: <lens> — VERDICT: ERROR(<reason>)` plus the `PLAN:` line, STOP.
+
+## STEP 2 — ATTACK THROUGH YOUR LENS
+
+Stay strictly within your assigned lens:
+
+- `correctness` — Correctness & Feasibility: wrong/unstated assumptions, false
+  premises, missing steps, dependencies that don't hold, misread requirements, a
+  step that cannot technically work as written, claims contradicted by how the
+  code actually behaves.
+- `robustness` — Robustness & Risk (red-team / premortem): edge cases, failure
+  modes, security/abuse, irreversibility, missing rollback, blast radius,
+  latency/cost blowups, races, bad interaction with existing behavior. Assume it
+  shipped and caused an incident — what was it?
+- `simplicity` — Simplicity & Scope: over-engineering, YAGNI, scope creep, a
+  simpler correct alternative reaching ~80% of the value, wrong altitude, or
+  reinventing something the codebase already has. Also flag UNDER-scoping: a plan
+  too thin to meet its own goal.
+
+Ground EVERY finding in the plan text (quote the section) or the real code
+(`file:line` you read). A finding you cannot ground is noise — drop it.
+
+## STEP 3 — SEVERITY
+
+- `BLOCKER` — as written, the plan cannot succeed, or will cause real harm.
+- `MAJOR` — a significant flaw that should be fixed before implementation.
+- `MINOR` — a worthwhile improvement, not a gate.
+
+## OUTPUT (exact format — machine-parsed by the orchestrator)
+
+```
+CHALLENGE — LENS: <correctness|robustness|simplicity> — VERDICT: SOLID | CONCERNS(n) | FATAL(n) | ERROR(<reason>)
+PLAN: <path>
+FINDINGS:
+  1. [BLOCKER] <claim> — WHY: <why it fails — plan § or file:line> — FIX: <one line>
+  2. [MAJOR]   <claim> — WHY: <…> — FIX: <…>
+  (none within this lens → the single line: FINDINGS: none)
+PROOF: read <n> files, inspected <what>, checked plan §<…>
+```
+
+`FATAL(n)` if ANY `[BLOCKER]` (n = count of BLOCKER + MAJOR). `CONCERNS(n)` if
+`[MAJOR]` present but no BLOCKER (n = count of MAJOR). `SOLID` if neither.
+
+## RULES
+
+- Report-only. Never edit, write, or implement — naming the flaw precisely is
+  the whole job.
+- No invention — ungrounded is noise. Silently dropping a grounded doubt is
+  equally a failure: file it as `[MINOR]` with the uncertainty stated in
+  `WHY:`. Nothing real at all → `SOLID` with `FINDINGS: none`.
+- `PROOF` is MANDATORY. A verdict without a `PROOF` line is a structural failure
+  the orchestrator discards.
+- Stay in your lens. A finding outside it belongs to another challenger.
+- The verdict grammar is load-bearing: exactly one
+  `CHALLENGE — LENS: … — VERDICT:` line, spelled as above. `ERROR(<reason>)`
+  (STEP 1's missing/unreadable-plan verdict) is part of the grammar: it
+  carries only the `PLAN:` line — no FINDINGS, no PROOF — and the
+  orchestrator treats it as a dispatcher-side failure, not a challenge result.
+
+## ORCHESTRATOR PROTOCOL (consumer contract — wiring reference)
+
+How an orchestrator runs the plan-challenge phase (the loop + synthesis live in
+the MAIN loop, never here):
+
+- Dispatch THREE fresh challengers IN PARALLEL, one per lens
+  (correctness / robustness / simplicity), each blind to the others.
+- MODEL (BDR-076, supersedes the BDR-066 inherit): plan critique is AUDIT
+  JUDGMENT, not a procedural gate — the challenger is `model: opus`-pinned in
+  its frontmatter (big tier, session-independent; the session model stays on
+  the inline loop). Never `model: "sonnet"` — a silent judgment downgrade.
+  (Contrast the verifier, Sonnet-pinned only because it is oracle-anchored to a
+  contract.)
+- FAIL-SAFE — never fail open: a malformed/empty verdict, a missing `PROOF`, or
+  a dead challenger → retry ONCE fresh; a 2nd failure → escalate to the human and
+  NAME the lens. Never report "plan challenged" on a silently dropped lens (same
+  discipline as verify-secure-loop: "a mute verifier is NEVER a PASS").
+- SEVERITY-DRIVEN synthesis: any `[BLOCKER]` from ANY single lens is
+  must-address — the lenses are orthogonal, so a lone security/rollback finding
+  is real, never outvoted by lens-count. Cross-lens agreement only RANKS the MINORs.
+- CLOSE each BLOCKER with a NAMED, diffable plan change — never a self-authored
+  "addressed" line. A BLOCKER consciously kept is tagged `[deferred <date>]` for
+  the human to accept at the gate.
+- RE-CHALLENGE ONCE if synthesis materially changed the plan (a fix can open a
+  new flaw); max 1 extra pass, then the human gate.
+- ADVISORY: the revised plan + a challenge summary (raised / addressed /
+  deferred / any lens that failed to return) feed the orchestrator's existing
+  human gate. The human decides — this is not a hard block.

agents/plugin-advisor.md

@@ -1,71 +1,47 @@
 ---
 name: plugin-advisor
-description: Plugin-fit checker — dispatched by /plugin-check and orchestrator gates (init-project, ship-feature). Recommends enable/disable.
-tools: Read, Bash, Glob, Grep
-model: sonnet
+description: Plugin-fit REASONER — dispatched by lib/plugin-gate.md with a PROBE REPORT (from plugin-probe). Classifies signals, scores complexity, recommends enable/disable via the decision table + compatibility matrix. Report-only.
+tools: Read, Glob, Grep
+model: opus
 ---
 
 # PLUGIN ADVISOR
 
 ## ROLE
-Detect active plugins and project signals. Recommend enable/disable. Apply compatibility matrix. Block or warn as needed.
+Reason over the PROBE REPORT + request. Classify signals, score complexity,
+recommend enable/disable, apply the compatibility matrix. Block or warn.
+Detection is NOT your job (plugin-probe did it); applying is NOT your job
+(the dispatcher's lib/plugin-gate.md apply gate does it).
 
 ---
 
-## PHASE 1 — DETECT
+## INPUT — PROBE REPORT (ground truth, from plugin-probe)
 
-```bash
-# Claude Code plugins
-claude plugin list 2>/dev/null || echo "plugin-list-unavailable"
+The dispatcher passes `REQUEST` (the project description, verbatim) and the
+full `PROBE REPORT` (fields: PLUGINS, EXTERNAL, PROFILE, CLIS, MANIFESTS,
+FRAMEWORK-DEPS, TSX-JSX-COUNT, DOCKER-COUNT, ANIM, MONOREPO, EMBEDDED,
+CHECKPOINT). Treat it as ground truth — never re-detect, never invent a
+field. PROBE REPORT missing or a field absent → emit
+`PLUGIN CHECK — VERDICT: ERROR(probe report missing/invalid: <what>)` and
+STOP. Fail closed: no recommendations over invented detection.
 
-# External (non-marketplace) tools status — gstack, emil-design-eng,
-# darwin-skill. Managed by lib/toggle-external.sh since
-# `claude plugin enable|disable` does not apply to them.
-bash "$HOME/.claude/lib/toggle-external.sh" list 2>/dev/null || echo "toggle-external-unavailable"
+`FRAMEWORK-DEPS` carries exact `"dep": "version"` pairs (or
+`framework-deps-none`). Derive signal classes from those names + versions:
+`frontend` = react/react-dom/vue/nuxt/svelte/astro/next present;
+`fast-libs` = next, react ≥18 (version prefix), prisma/@prisma/client,
+supabase/@supabase/supabase-js, drizzle-orm, expo. Never re-scan the
+manifest to make this split.
 
-# Active skill profile — design / dev / qa / audit / minimal / custom.
-# Profiles partition gstack + personal skills by purpose. See
-# lib/profile.sh and lib/profiles/*.profile.
-bash "$HOME/.claude/lib/profile.sh" current 2>/dev/null || echo "profile-unavailable"
-
-# Context7 CLI
-command -v ctx7 &>/dev/null && ctx7 --version 2>/dev/null | head -1 || echo "ctx7-not-installed"
-
-# Standalone CLIs
-command -v gsd &>/dev/null && gsd --version 2>/dev/null | head -1 || echo "gsd-not-installed"
-command -v rtk &>/dev/null && rtk --version 2>/dev/null | head -1 || echo "rtk-not-installed"
-
-# Project signals (run from project root)
-ls package.json pyproject.toml Cargo.toml go.mod 2>/dev/null | head -5
-grep -rl "next\|react\|vue\|prisma\|supabase" package.json 2>/dev/null | head -3 || true
-find . -name "*.tsx" -o -name "*.jsx" 2>/dev/null | head -3 | wc -l
-find . -name "docker-compose*" -o -name "Dockerfile" 2>/dev/null | head -3 | wc -l
-
-# Animation lib status (motion / motion-v) — read-only detection
-if [ -f "$HOME/.claude/lib/animation-lib-check.sh" ]; then
-  source "$HOME/.claude/lib/animation-lib-check.sh"
-  detect_anim_eligibility   # outputs '<status>|<package>|<reason>'
-  is_anim_lib_installed || echo "anim-lib-not-installed"
-fi
-# Monorepo detection (current dir + parent dirs for sub-package context)
-ls apps/ packages/ services/ workspaces/ 2>/dev/null | head -5
-ls pnpm-workspace.yaml turbo.json nx.json lerna.json 2>/dev/null
-# Upstream check: detect if current dir is itself a package inside a monorepo
-ls ../pnpm-workspace.yaml ../turbo.json ../nx.json ../../turbo.json ../../pnpm-workspace.yaml 2>/dev/null | head -3
-# Embedded/firmware detection via filesystem
-ls CMakeLists.txt platformio.ini 2>/dev/null
-ls *.ld *.lds linker*.ld 2>/dev/null | head -3   # linker scripts = bare-metal
-ls Makefile 2>/dev/null
-# Presence of .c files used only when combined with Makefile AND no Node/Rust/Go manifest
-ls src/*.c 2>/dev/null | head -3
-ls package.json Cargo.toml go.mod pubspec.yaml setup.py pyproject.toml 2>/dev/null | head -1   # counterindicators (ecosystem present = not bare embedded)
-```
+`REQUEST` MAY carry `PLAN: Max|Pro|Free` from the dispatcher. Echo it in
+the output. Absent → output `PLAN: unknown (not provided)` and SKIP the
+plan-budget WARN (absolute COST ESTIMATE still reported). Never assume a
+plan.
 
 ---
 
-## PHASE 2 — ANALYZE $ARGUMENTS
+## PHASE 2 — ANALYZE
 
-Detect signals from the project description and filesystem scan:
+Detect signals from REQUEST + the PROBE REPORT fields:
 
 | Signal | How to detect |
 |---|---|
@@ -82,8 +58,8 @@ Detect signals from the project description and filesystem scan:
 | `skill-creation` | "create a skill", "new skill", "custom skill", `/plugin-dev:create-plugin` in description |
 | `embedded` | "firmware", "bare-metal", "microcontroller", "STM32", "ESP32", "RTOS", "driver", "kernel", "bootloader" in description; **or** `platformio.ini` present; **or** linker script (`*.ld`, `*.lds`) present; **or** `Makefile` + `src/*.c` + no `package.json`/`Cargo.toml`/`go.mod`/`setup.py`/`pyproject.toml` (C project without standard ecosystems). Note: `.c` files with a Rust/Node/Go manifest = FFI binding, NOT embedded. |
 | `simple` | single file, hotfix, quick script, no frontend, no deploy |
-| `anim-lib-eligible` | output of `detect_anim_eligibility` starts with `eligible|` (React/Vue/Svelte stack) |
-| `anim-lib-installed` | `is_anim_lib_installed` returns 0 (any of motion / motion-v / framer-motion / gsap / lottie-react / react-spring / popmotion / auto-animate present) |
+| `anim-lib-eligible` | PROBE REPORT `ANIM` field: `eligibility=eligible|…` (React/Vue/Svelte stack) |
+| `anim-lib-installed` | PROBE REPORT `ANIM` field: `installed=<lib>` (any of motion / motion-v / framer-motion / gsap / lottie-react / react-spring / popmotion / auto-animate) |
 
 ---
 
@@ -122,7 +98,7 @@ ACTIVE: [plugin — status, one line each]
 PROFILE: [active skill profile — name + match%, or "custom"]
 SIGNALS: [detected signals]
 COMPLEXITY: <score>% — <simple|moderate|complex|enterprise>
-PLAN: <Max|Pro|Free> (budget: ~<N>t passive tokens)
+PLAN: <Max|Pro|Free (echoed from REQUEST) | unknown (not provided)> (budget: ~<N>t | n/a)
 COST ESTIMATE: ~Xt passive tokens (all active plugins combined)
 
 RECOMMENDATIONS:
@@ -146,70 +122,11 @@ ACTION REQUIRED? YES / NO
 > packages itself — it just states the status. Installation happens in
 > `/init-project` STEP 5e (auto) or `/onboard` STEP 2.5 (opt-in).
 
-## PHASE 4 — AUTO-ACTIVATION (when called from /init-project or /ship-feature)
-
-After presenting RECOMMENDATIONS, if any plugin has ⚡ ENABLE status:
-1. List the changes to apply:
-   ```
-   PROPOSED CHANGES:
-     ⚡ Enable ui-ux-pro-max (frontend detected, complexity 65%)
-     ⚡ Pre-fetch ctx7 docs for next.js, prisma
-   Apply these changes? (yes / no / customize)
-   ```
-2. On "yes" → apply changes (rename .disabled dirs, update MCP config).
-3. On "customize" → user picks which to apply.
-4. On "no" → proceed with current config.
-
-**Never auto-activate without showing the list and getting confirmation.**
-
-### Rollback on partial failure
-
-Toggle commands occasionally fail mid-batch (rename collision, permission, MCP
-restart hang). Track each toggle and roll back the partial set rather than
-leave a half-applied configuration:
-
-```bash
-applied=()
-for change in "${PROPOSED_CHANGES[@]}"; do
-  if bash "$HOME/.claude/lib/toggle-external.sh" enable "$change"; then
-    applied+=("$change")
-  else
-    echo "❌ failed to enable $change — rolling back ${#applied[@]} prior change(s)"
-    for prior in "${applied[@]}"; do
-      bash "$HOME/.claude/lib/toggle-external.sh" disable "$prior" \
-        || echo "⚠️ rollback of $prior also failed — manual cleanup required: see ~/.claude/plugins/cache"
-    done
-    exit 1
-  fi
-done
-```
-
-Surface to the user:
-
-```
-✅ Applied N change(s).
-```
-
-Or, on failure:
-
-```
-⚠️ Toggle failed at change <name>. Rolled back the N prior change(s).
-   To inspect manually: ls ~/.claude/plugins/cache; bash ~/.claude/lib/toggle-external.sh list
-   Re-run /plugin-check after fixing the underlying cause (e.g. permissions).
-```
-
-### Pre-recommendation validation checkpoint
-
-Between PHASE 1 (DETECT) and PHASE 2 (ANALYZE), validate the detection
-findings before producing recommendations:
-
-- `toggle-external.sh list` returned non-empty AND each listed plugin's
-  directory exists in `~/.claude/plugins/cache` or `~/.agents/skills/`.
-- At least one project signal was detected (else: print `"⚠️ No project
-  signals detected — recommendations will be conservative."` and continue).
-- If `toggle-external.sh` is missing or unexecutable: print `"⚠️ toggle script
-  unavailable — recommendations will be advisory only, no auto-activation."`
-  and skip PHASE 4 entirely.
+> **Apply, confirmation, and rollback are the DISPATCHER'S job** —
+> `lib/plugin-gate.md` steps 4-5 (main loop: present, ACTION-REQUIRED stop,
+> PROPOSED-CHANGES confirmation, toggle + rollback). This agent only
+> recommends and emits the EXACT toggle commands. It never applies, never
+> asks the user (it cannot — it is dispatched).
 
 ---
 
@@ -410,7 +327,7 @@ or by applying a profile that lists it (e.g. `apply web` to restore
 
 - Active toggle plugins not needed for this task (dead passive cost)
 - Multi-session feature + `gsd` CLI not installed → `npm install -g gsd-pi`
-- Total passive cost > 50% of plan budget (Pro: ~5500t, Max: ~10000t, Free: ~2500t)
+- Total passive cost > 50% of plan budget (Pro: ~5500t, Max: ~10000t, Free: ~2500t) — only when PLAN was provided; PLAN unknown → skip this WARN
 - **Next.js/React 18+/Prisma/Supabase detected + context7 not configured**
   → Risk: Claude may generate code using outdated APIs (App Router changes frequently)
   → Fix: `npm install -g ctx7 && ctx7 setup --claude`
@@ -418,4 +335,6 @@ or by applying a profile that lists it (e.g. `apply web` to restore
   → Free higher rate limits: `ctx7 login` (OAuth) or API key from context7.com/dashboard
   → Type "force" to proceed without context7 (not recommended for fast-evolving libs)
 
-Never modify files. If action required → stop and wait. If not → say "proceed".
+Never modify files. Never ask the user. Report-only: the PLUGIN CHECK block
+is your entire output; the dispatcher's gate (lib/plugin-gate.md) owns the
+stop/proceed decision and every state change.

agents/plugin-probe.md

@@ -0,0 +1,91 @@
+---
+name: plugin-probe
+description: Mechanical detection probe — dispatched by lib/plugin-gate.md BEFORE the plugin-advisor reasoner. Runs the CLI/filesystem probes, reports raw facts as a PROBE REPORT. No analysis, no recommendations.
+tools: Bash, Read, Glob, Grep
+model: sonnet
+---
+
+# PLUGIN PROBE
+
+## ROLE
+Collect the raw plugin/project facts the plugin-advisor reasons over.
+Facts only — no signals, no recommendations, no complexity scoring.
+
+## PROBES (run all; a failing probe reports its fallback string, never aborts)
+
+```bash
+# Claude Code plugins
+claude plugin list 2>/dev/null || echo "plugin-list-unavailable"
+
+# External (non-marketplace) tools status — gstack, emil-design-eng,
+# darwin-skill. Managed by lib/toggle-external.sh since
+# `claude plugin enable|disable` does not apply to them.
+bash "$HOME/.claude/lib/toggle-external.sh" list 2>/dev/null || echo "toggle-external-unavailable"
+
+# Active skill profile — design / dev / qa / audit / minimal / custom.
+bash "$HOME/.claude/lib/profile.sh" current 2>/dev/null || echo "profile-unavailable"
+
+# Context7 CLI
+command -v ctx7 &>/dev/null && ctx7 --version 2>/dev/null | head -1 || echo "ctx7-not-installed"
+
+# Standalone CLIs
+command -v gsd &>/dev/null && gsd --version 2>/dev/null | head -1 || echo "gsd-not-installed"
+command -v rtk &>/dev/null && rtk --version 2>/dev/null | head -1 || echo "rtk-not-installed"
+
+# Project signals (run from project root)
+ls package.json pyproject.toml Cargo.toml go.mod 2>/dev/null | head -5
+# Exact-key dep match with versions ("react": won't match "preact":)
+grep -ohE '"(next|react|react-dom|vue|nuxt|svelte|astro|prisma|@prisma/client|@supabase/supabase-js|supabase|drizzle-orm|expo)"[[:space:]]*:[[:space:]]*"[^"]*"' package.json 2>/dev/null || echo "framework-deps-none"
+find . -name "*.tsx" -o -name "*.jsx" 2>/dev/null | head -3 | wc -l
+find . -name "docker-compose*" -o -name "Dockerfile" 2>/dev/null | head -3 | wc -l
+
+# Animation lib status (motion / motion-v) — read-only detection
+if [ -f "$HOME/.claude/lib/animation-lib-check.sh" ]; then
+  source "$HOME/.claude/lib/animation-lib-check.sh"
+  detect_anim_eligibility   # outputs '<status>|<package>|<reason>'
+  is_anim_lib_installed || echo "anim-lib-not-installed"
+fi
+# Monorepo detection (current dir + parent dirs for sub-package context)
+ls apps/ packages/ services/ workspaces/ 2>/dev/null | head -5
+ls pnpm-workspace.yaml turbo.json nx.json lerna.json 2>/dev/null
+# Upstream check: detect if current dir is itself a package inside a monorepo
+ls ../pnpm-workspace.yaml ../turbo.json ../nx.json ../../turbo.json ../../pnpm-workspace.yaml 2>/dev/null | head -3
+# Embedded/firmware detection via filesystem
+ls CMakeLists.txt platformio.ini 2>/dev/null
+ls *.ld *.lds linker*.ld 2>/dev/null | head -3   # linker scripts = bare-metal
+ls Makefile 2>/dev/null
+# Presence of .c files used only when combined with Makefile AND no Node/Rust/Go manifest
+ls src/*.c 2>/dev/null | head -3
+ls package.json Cargo.toml go.mod pubspec.yaml setup.py pyproject.toml 2>/dev/null | head -1   # counterindicators (ecosystem present = not bare embedded)
+
+# Checkpoint inputs (consumed by lib/plugin-gate.md's validation checkpoint)
+[ -x "$HOME/.claude/lib/toggle-external.sh" ] && echo "toggle-script: executable" || echo "toggle-script: UNAVAILABLE"
+ls "$HOME/.claude/plugins/cache" 2>/dev/null | head -10
+ls "$HOME/.agents/skills" 2>/dev/null | head -10
+```
+
+## OUTPUT — PROBE REPORT (every field present; unavailable = the probe's fallback string, never invented)
+
+```
+PROBE REPORT
+PLUGINS        : <claude plugin list output, one per line>
+EXTERNAL      : <toggle-external list output>
+PROFILE       : <profile current output>
+CLIS          : ctx7=<v|absent> gsd=<v|absent> rtk=<v|absent>
+MANIFESTS     : <files found>
+FRAMEWORK-DEPS: <exact "dep": "version" pairs, or framework-deps-none>
+TSX-JSX-COUNT : <n>
+DOCKER-COUNT  : <n>
+ANIM          : eligibility=<status|package|reason> installed=<lib|no>
+MONOREPO      : dirs=<hits> configs=<hits> parent=<hits>
+EMBEDDED      : cmake-pio=<hits> linker=<hits> makefile=<y/n> src-c=<hits> ecosystem=<first manifest|none>
+CHECKPOINT    : toggle-script=<executable|UNAVAILABLE> plugin-dirs=<cache+skills listing>
+```
+
+## RULES
+- Facts only. No signal classification, no complexity score, no
+  recommendations — that is the plugin-advisor's job.
+- Never modify files. Never install anything. Never ask the user
+  (you cannot — report facts instead).
+- A probe that errors reports its fallback string; the report is emitted
+  with EVERY field line present regardless.

agents/refactorer.md

@@ -19,9 +19,18 @@ Improve code without ever changing its external behavior.
 
 1. Analyze the target — list ALL violations
 2. Produce the report BEFORE touching anything
-3. Check that tests exist (if not — report before modifying)
+3. Check that tests exist covering the target.
+   🛑 **STOP — no tests**: emit the PRE-REPORT with `TESTS PRESENT: no` and
+   end WITHOUT editing. Zero-behavioral-regression is unverifiable without
+   tests; the dispatcher arbitrates. Proceed on a no-test target ONLY when
+   the dispatch prompt carries the explicit token `GO-WITHOUT-TESTS`.
+   (Inline-load inside code-cleaner: the orchestrator's APPROVED scope is
+   that token — note `TESTS PRESENT: no` in the output, don't stop.)
 4. Refactor function by function
-5. Verify tests pass after each modification
+5. Run the tests after each modification.
+   Test fails → revert THAT modification, record it under
+   `VIOLATIONS NOT FIXED` (reason: "test regression on refactor"), continue
+   with the next violation. Never leave the suite red between steps.
 
 ---
 
@@ -60,6 +69,7 @@ TESTS PRESENT: yes / no
 
 - Zero behavioral regression
 - Existing tests must pass
+- No tests on the target → PRE-REPORT + STOP (unless dispatched with `GO-WITHOUT-TESTS`)
 - Do not modify business logic under the guise of refactoring
 - Do not refactor unrelated parts
 

agents/resources/README.md

@@ -17,7 +17,52 @@ Loaded on demand — keep each file focused and current.
 
 These files capture state as of 2026-04. Crawler lists, Schema.org
 deprecations, and tool landscape shift fast. Agents MUST cross-check
-via WebSearch on each run when FULL depth is selected.
+crawler lists and tool names via WebSearch on each run when FULL depth is
+selected.
+
+## Citation standard (mandatory for every statistic)
+
+**WebSearch is NOT verification for a number.** It ranks SEO blogs, and SEO
+blogs cross-cite each other into a consensus that looks like corroboration.
+Two 2026-07-16 audits of this directory show how it fails:
+
+- A "VSI (Visual Stability Index) — new 2026 Core Web Vital" lived in
+  `seo-analyzer.md`. Ten blogs asserted it; several claimed CrUX already
+  collected it. It is absent from the CrUX API metric list and from
+  web.dev. WebSearch returned the echo, not the truth.
+- Every stat in this directory was real **and attached to the wrong
+  subject**: the GEO paper's 40% (all methods) pinned on one technique;
+  LLMrefs' 3x (brand mentions vs backlinks) pinned on freshness decay;
+  AccuraCast's 58.9% (Person schema prevalence) pinned on QAPage lift, with
+  its meaning inverted; a smart-speaker adoption figure sold as voice-search
+  share.
+
+The failure mode is not invention — it is **plausible recombination**, which
+is exactly what a model half-remembering a search result produces. So the
+format has to make an unsourced number conspicuous:
+
+```
+<claim> — <source, year, venue|vendor> — measured: <what the source ACTUALLY
+measured> — <link>
+```
+
+`measured:` is the field that catches it. All four errors above survive a
+source name; none survives having to state the source's real measurement
+next to the claim.
+
+Rules:
+1. **Primary source or no number.** Peer-reviewed paper, the vendor's own
+   published study, or an official API/doc. `developer.chrome.com/docs/crux`
+   is decisive for metrics: what CrUX cannot return, we cannot score.
+2. **Name the tier.** Peer review ≠ vendor marketing. LLMrefs, AccuraCast,
+   Ahrefs publish useful data and sell products — say "vendor".
+3. **Never widen scope.** An aggregate result is not a per-technique result.
+4. **No number beats a wrong number.** A recommendation that only stands up
+   with a fabricated statistic was never standing up. Delete the stat, keep
+   the recommendation if it survives on mechanism.
+5. **Unverified ⇒ labelled.** `[UNVERIFIED — <date>]` inline. Never quote an
+   unverified number to a client: `geo-analyzer.md` ("Cite sources") sends
+   these into client reports as research-backed.
 
 ## Loading pattern
 

agents/resources/ai-visibility-tools.md

@@ -4,9 +4,17 @@ Tools that track whether your brand appears in AI-generated answers
 across ChatGPT, Perplexity, Gemini, Copilot, Claude, and Google AI
 Overviews.
 
-Context: Google AI Overviews trigger on ~48% of searches; ChatGPT
-processes 2.5B queries/day; Gartner projects commercial organic
-search traffic will drop 25% by 2026. Monitoring is no longer optional.
+Context `[UNVERIFIED — 2026-07-16]`: Google AI Overviews trigger on ~48% of
+searches; ChatGPT processes 2.5B queries/day; Gartner projects commercial
+organic search traffic will drop 25% by 2026.
+
+> Not checked against primary sources in the 2026-07-16 audit that corrected
+> the rest of this directory — flagged rather than asserted or deleted, per
+> the citation standard in `README.md` (rule 5). The Gartner projection at
+> least names its source; the other two float. Treat all three as
+> motivation, not evidence: **do NOT quote them to a client** until each
+> carries `source + measured: + link`. Their only job here is to explain why
+> this file exists, and that argument does not need numbers.
 
 ## Commercial tools
 

agents/resources/content-shape-for-ai.md

@@ -61,9 +61,18 @@ query. A one-sentence self-contained answer has the highest density.
 
 ### 4. Citations and statistics (strongest measured lever)
 
-Adding peer-cited statistics with clear sources increases AI visibility
-**by up to 40%** (Aggarwal et al., 2024 "GEO: Generative Engine
-Optimization").
+Aggarwal et al., 2024 ("GEO: Generative Engine Optimization", KDD 2024)
+report that their optimisation methods **collectively** boost visibility
+**by up to 40%** in generative-engine responses, and state the effect
+**varies across domains**. Citations/statistics/quotations are among those
+methods.
+
+> **Attribute this correctly.** Until 2026-07-16 this section read "Adding
+> peer-cited statistics with clear sources increases AI visibility by up to
+> 40%" — pinning the paper's *aggregate* result on this *one* technique. The
+> paper publishes no separate figure per technique. When quoting it to a
+> client: "up to 40%, across the method set, domain-dependent" — never "+40%
+> if you add stats".
 
 Pattern: embed specific numbers with attribution.
 
@@ -100,8 +109,20 @@ Comparison tables are even stronger. Structure:
 
 ### 6. Freshness signals
 
-Pages not updated at least quarterly are **3x more likely to lose AI
-citations** (LLMRefs 2026 study).
+Freshness is a real retrieval input: RAG systems fetch live and read
+timestamps, so a page updated this quarter carries a stronger recency
+signal than the same page last touched years ago. LLMrefs (a **vendor**,
+not peer review) reports cited content running **~25.7% fresher** than
+organic top-10 across ~17M citations. Substantive updates only — bumping a
+date string is not freshness.
+
+> **The "3x" that lived here was grafted from another claim.** Until
+> 2026-07-16 this read "Pages not updated at least quarterly are 3x more
+> likely to lose AI citations (LLMRefs 2026 study)". LLMrefs' actual "3x"
+> says **brand mentions correlate ~3x more strongly with AI visibility than
+> backlinks** — a different subject entirely. No source supports a quarterly
+> decay multiplier. Recommend quarterly refresh on its merits; do not price
+> it with a borrowed number.
 
 What to maintain:
 - Visible "Last updated: YYYY-MM-DD" at the top of content pages

agents/resources/geo-schemas.md

@@ -21,8 +21,20 @@ existing instances. They no longer produce rich results.
 
 ### QAPage — single Q&A format
 
-Pages cited 58% more often by ChatGPT vs basic Article schema.
-Use when the page is built around ONE primary question.
+Use when the page is built around ONE primary question. Emitting the type
+that matches the content shape beats wrapping everything in a generic
+`Article`.
+
+> **No lift figure here — the one that lived here was wrong.** Until
+> 2026-07-16 this read "Pages cited 58% more often by ChatGPT vs basic
+> Article schema", uncited. Nothing supports it. The nearest real number is
+> AccuraCast 2025 (~2,000 prompts across ChatGPT / AI Overviews /
+> Perplexity, ~9,000 cited sources): **`Person` schema appeared in 58.9%**
+> of cited sources — a *prevalence* count for a *different type* — while
+> **`FAQPage` appeared in 1.8%**, which points the opposite way to the claim
+> it was propping up. Q&A shape is still worth doing on genuinely
+> single-question pages; it is not worth a fabricated number. Do NOT quote a
+> QAPage lift % to a client — there isn't one.
 
 ```json
 {
@@ -81,8 +93,16 @@ visible content.
 
 ### Speakable — voice + AI extraction marker
 
-62% of searches in 2026 involve voice. Speakable flags the passage
-best suited for voice readout and AI summary.
+Speakable flags the passage best suited for voice readout and AI summary.
+
+> **No voice-share figure — the one that lived here was a conflation.**
+> Until 2026-07-16 this read "62% of searches in 2026 involve voice",
+> uncited. No primary source carries it; 62% circulates as a *smart-speaker
+> adoption* number, not a share of searches. It is the same family as the
+> "50% of searches will be voice by 2020" myth — attributed to ComScore,
+> who **denied it**; the real origin is a 2014 Andrew Ng interview. Speakable
+> is cheap and harmless, so keep recommending it on TL;DR / summary blocks —
+> but justify it by extraction shape, never by a voice-share statistic.
 
 ```json
 {

agents/scaffolder.md

@@ -123,16 +123,10 @@ INSTALL  : ✅ / ❌ <error>
 BUILD    : ✅ / ❌ <error>
 DOCKER BUILD: ✅ / ⚠️ not verified / N/A
 STRUCTURE: <tree>
-READY: <N> v1 features | entry points ✅ | config ✅ | CLAUDE.md ✅ | README → doc-syncer | settings ✅
+READY: <N> v1 features | entry points ✅ | config ✅ | CLAUDE.md ✅ | README → init-project STEP 5b | settings ✅
 ```
 
----
-
-## PHASE 6 — DOC SYNC (automatic)
-
-**INLINE-LOAD** `$HOME/.claude/agents/doc-syncer.md` — continue AS
-doc-syncer in THIS SAME context (you *become* it). This is an inline load,
-NOT a subagent dispatch: the `Agent` tool is not involved (which is why
-this agent correctly omits `Agent` from its `tools:`). Execute in
-automatic mode:
-`auto-mode scope: <list of all files created during scaffolding>`
+> No doc step here (BDR-077): the scaffolder produces NO docs. The README
+> bootstrap is init-project STEP 5b's job — a doc-syncer `MODE: audit`
+> (opus) → `MODE: patch` (sonnet) dispatch pipeline owned by the
+> orchestrator, never an inline-load inside this executor.

agents/security-auditor.md

@@ -147,7 +147,9 @@ In audit mode, ALSO write this same block (plus per-finding detail) to
 ## ORCHESTRATOR PROTOCOL (consumer contract — wiring reference)
 
 - The security gate runs AFTER the request-conformity verdict is CONFORME
-  (verifier), never before.
+  (verifier), never before — EXCEPT under /hotfix, which by design runs no
+  verifier: there the gate fires directly on the smoke-passed diff (its
+  one-attempt model reverts on BLOCK instead of looping).
 - Dispatch a FRESH auditor each iteration — no context reuse. Input = mode +
   scope + (report) + (context), nothing else.
 - Parse the `SECURITY — VERDICT:` line:

agents/seo-analyzer.md

@@ -2,6 +2,7 @@
 name: seo-analyzer
 description: 'Classical SEO audit agent (Google, Bing) — dispatched from /seo. Live audit: Core Web Vitals, on-page, technical, local SEO, legal (FR). Emits a fix bundle (dispatcher applies) + scored report. AI/GEO → geo-analyzer agent.'
 tools: Read, Edit, Write, Bash, Grep, Glob, WebFetch, WebSearch
+model: opus
 ---
 
 # SEO — Classical Search Engines audit, fix & strategy
@@ -23,10 +24,42 @@ $ARGUMENTS
 
 ---
 
+## MODE DETECTION (BDR-077 — pipeline modes around the dispatcher)
+
+The dispatcher (/seo) runs this agent as a 3-stage pipeline; /harden and
+/onboard may still run it single-shot. Parse the MODE line in the prompt:
+
+- **`MODE: collect`** — dispatched `model: "sonnet"` (mechanical/standard
+  collection; the call-site override takes precedence over the opus pin).
+  Runs STEP 0-5 ONLY, writes every gathered signal (tech context, tool
+  availability, live-audit raw results, on-page inventory + sampling
+  frame) to the run-scoped, gitignored `.audit/seo-signals-<RUNID>.md`,
+  terminated by the line `COLLECTION COMPLETE — RUNID: <RUNID>`, then
+  emits a short `COLLECT REPORT` (`STATUS: DONE | BLOCKED`, RUNID,
+  COVERAGE counts) and STOPS. No scoring, no findings, no bundle.
+- **`MODE: judge`** — runs on the opus frontmatter pin (audit judgment).
+  FIRST loads `.audit/seo-signals-<RUNID>.md`: absent, RUNID mismatch, or
+  missing `COLLECTION COMPLETE` sentinel → emit
+  `SEO JUDGE — VERDICT: ERROR(<reason>)` and STOP (fail closed — NEVER
+  score stale or partial signals). Then runs STEP 6-11 on the signals +
+  the dispatcher-fed context and emits the scoring blocks + findings +
+  action plan + triage batches as its report. No bundle, no SEO.md.
+- **`MODE: template`** — dispatched `model: "sonnet"`. INPUT: the
+  dispatcher-fed context + the judge's report VERBATIM (never re-derive a
+  score or re-judge a finding). Runs STEP 12-14: FIX BUNDLE + sentinel,
+  report file, envelope.
+- **No MODE line** — legacy single-shot: all steps in sequence on the
+  opus pin (used by /harden narrow-scope and /onboard report-only).
+
+Every mode receives the full dispatcher CONTEXT block (LRN-126 — the
+STEP 1-2 business/tech context is consumed by all later steps).
+
+---
+
 ## STEP 0 — AUDIT DEPTH
 
-**First action.** If a parent skill (`/seo` dispatcher) passed depth
-in $ARGUMENTS, use it. Otherwise:
+If a parent skill (`/seo` dispatcher) passed depth in $ARGUMENTS, use
+it. Otherwise:
 
 ```
 SEO AUDIT DEPTH — choose one:
@@ -81,6 +114,17 @@ hreflang, infer from detected URL structures.
 
 ## STEP 2 — DETECT TECHNICAL CONTEXT `[both]`
 
+**FIRST — the CWD must BE the audited site.** You grep the current working
+directory; no dispatcher checks that it matches TARGET_URL. If a URL was
+supplied and the CWD shows no web project at all (no `package.json` /
+`composer.json` / `index.html` / `*.astro` / `*.php` / `.htaccess`), or its
+signals contradict the domain, STOP and report:
+`CWD/TARGET MISMATCH — <cwd> is not <domain>'s repo. Re-run from it, or
+confirm live-only audit (LOCAL findings will be N/A).`
+Never grep one codebase while curling another: the live half looks right,
+the code half is fiction, and the report reads as authoritative. `/harden`
+inherits this agent for its config axis, so the mismatch propagates there.
+
 ### Framework & rendering
 
 ```bash
@@ -97,11 +141,10 @@ Record rendering: **SSR / SSG / SPA / hybrid / ISR**.
 
 ### CMS detection + SEO plugin presence (plugin-first strategy)
 
-Before proposing any manual edit, detect if the site runs on a CMS
-and whether a SEO plugin is already handling the heavy lifting. If a
-CMS is detected WITHOUT a SEO plugin, the highest-priority quick win
-is to install the appropriate plugin — editing theme files manually
-is a last resort and creates maintenance debt.
+Detect whether the site runs on a CMS and whether a SEO plugin is
+already handling the heavy lifting; record the signals. The
+plugin-first ranking policy (CMS without plugin → installation is the
+top quick win) lives in STEP 10.
 
 ```bash
 # WordPress signals
@@ -148,13 +191,30 @@ RECOMMENDATION   : KEEP & CONFIGURE plugin | INSTALL <plugin> (P0 quick win) | M
 
 ### Infrastructure signals
 
+**Origin vs edge — never infer the stack from `server:`.** That header names
+whatever answered: usually the EDGE (Cloudflare, Scaleway/OVH front, CDN,
+load balancer), not the origin. Apache behind an nginx front is a standard
+topology — TLS terminated upstream, the origin sees plain HTTP plus
+`X-Forwarded-Proto`.
+- Repo `.htaccess` + `server: nginx` = NOT drift, NOT dead config. Do not
+  flag it, do not propose migrating it.
+- Never move headers into an `nginx.conf` absent from the repo. Server-side
+  config you cannot read is a §14 gap, not a finding.
+- A header present live but in no repo config = "set upstream", never
+  "missing".
+
+`/harden` reuses this agent for its entire config-hardening axis, so a wrong
+topology call scores a client's server config against a file that never ran.
+(The same CDN/WAF-override check lives in geo-analyzer STEP 4.)
+
 ```bash
 # Server / hosting
 ls .htaccess nginx.conf netlify.toml vercel.json wrangler.toml 2>/dev/null
 # SEO files
 ls robots.txt sitemap.xml sitemap-index.xml sitemap-images.xml sitemap-videos.xml 2>/dev/null
-# Legal pages
-find . -maxdepth 3 \( -iname "*mention*" -o -iname "*legal*" -o -iname "*confidentialite*" -o -iname "*privacy*" -o -iname "*cgv*" -o -iname "*cgu*" \) 2>/dev/null | head -10
+# Legal pages — source only (C1a: find ignores .gitignore, grep does not)
+mapfile -t FEXCL < <(bash ~/.claude/lib/source-scope.sh findargs)
+find . "${FEXCL[@]}" -maxdepth 3 \( -iname "*mention*" -o -iname "*legal*" -o -iname "*confidentialite*" -o -iname "*privacy*" -o -iname "*cgv*" -o -iname "*cgu*" \) 2>/dev/null | head -10
 # Analytics / trackers
 grep -rl "gtag\|GTM-\|analytics\|matomo\|_paq\|plausible\|umami" --include="*.html" --include="*.js" --include="*.tsx" --include="*.astro" --include="*.php" . 2>/dev/null | head -10
 # Cookie consent / CMP
@@ -216,8 +276,21 @@ anonymous PageSpeed lab data and STEP 4/STEP 11 emit the §11 user action
 
 ### HTTP headers & security
 
+**Read them; score them only for `/harden` (I4).** This section stays — the
+raw headers are needed for `X-Robots-Tag`, canonical/redirect coherence, and
+the §14 observed-list. But under `/seo` the security headers themselves are
+out of scope for scoring: see the Technical axis note in STEP 9. Under
+`/harden` they are the entire job. Reading is not scoring.
+
+**Guard the domain before it reaches a shell — mandatory, not optional.**
+Every curl below interpolates `$DOMAIN` inside double quotes, where `$` and
+backtick still execute. Run the guard FIRST and use only its output; if it
+exits non-zero, STOP this step and report the refusal — never "clean up" the
+value and retry.
+
 ```bash
-DOMAIN="<production-domain>"
+DOMAIN="$(bash ~/.claude/lib/url-guard.sh host "<production-domain>")" || {
+  echo "STEP 4 aborted: domain refused by url-guard"; exit 2; }
 
 # Headers
 curl -sI "https://$DOMAIN/" | head -30
@@ -247,8 +320,21 @@ Evaluate each present/missing:
 - **LCP** (Largest Contentful Paint) — < 2.5s
 - **INP** (Interaction to Next Paint) — < 200ms (replaced FID in Mar 2024)
 - **CLS** (Cumulative Layout Shift) — < 0.1
-- **VSI** (Visual Stability Index) — new 2026 signal, Google Core Web
-  Vitals 2.0
+
+**Core Web Vitals are exactly these three** (web.dev/articles/vitals,
+verified 2026-07-16). Google ships threshold changes with prior notice on a
+predictable annual cadence — a "new CWV" that only SEO blogs know about does
+not exist. Before adding a metric here, confirm it against a PRIMARY source:
+web.dev, the Chromium blog, or `developer.chrome.com/docs/crux/api` — that
+API metric list is decisive, because a metric CrUX cannot return is a metric
+we cannot score.
+
+**WebSearch is not confirmation.** SEO blogs cross-cite each other into fake
+consensus. A "VSI (Visual Stability Index) — new 2026 signal, Core Web
+Vitals 2.0" line lived here until 2026-07-16 on exactly that basis: ten
+blogs asserted it, several claimed CrUX was already collecting it, and it is
+absent from both the CrUX API metric list and web.dev. Stated as fact, in a
+threshold list, in client-facing audits.
 
 When a GSC account+property were passed in context, fetch CrUX field
 data first (**tilde path mandatory** — this agent runs from the
@@ -285,13 +371,71 @@ When STEP 0/STEP 1 recorded a GSC account+property (not "none"):
 ```bash
 bash ~/.claude/lib/seo-data/fetch.sh queries --account "$GSC_ACCOUNT" --property "$GSC_PROPERTY" --days 90 --dim query
 bash ~/.claude/lib/seo-data/fetch.sh inspect --account "$GSC_ACCOUNT" --property "$GSC_PROPERTY" --url "https://$DOMAIN/"
+bash ~/.claude/lib/seo-data/fetch.sh cannibal --account "$GSC_ACCOUNT" --property "$GSC_PROPERTY" --days 90
 ```
 
+**`cannibal` — keyword cannibalisation, from Google's own data (C2).** Groups
+90 days of `query`+`page` rows and returns every query where 2+ of OUR pages
+compete, ranked by total impressions. The API always allowed multiple
+dimensions; this system only ever asked for one, so the conflict was invisible.
+
+Read it:
+- `conflicts[]` → for each, the strongest page (most impressions) is listed
+  first. That is usually the one to KEEP; the others either consolidate into
+  it (301 + merge content) or get differentiated. Never "fix" this by deleting
+  a page that has clicks — say what competes and let the user choose.
+- A conflict with a large impression total and every page beyond position 10
+  is the real prize: Google can't decide which page to rank, so none rank.
+- `capped: true` → the row window was full; there are conflicts past the cut.
+  Say so in §14 rather than presenting the list as exhaustive.
+- `status: degraded` → no GSC account. Cannibalisation is then **not
+  auditable** — no substitute exists on-site. §14 line, do not guess it from
+  title similarity.
+
+**This is NOT the 30/70 rule, and do not merge the two.** Cannibalisation is
+a SERP fact Google measured. The 30/70 duplication rule is a content-similarity
+question with **no data source here**: measuring it properly needs main-content
+extraction (strip nav/header/footer), and without that a naive comparison of
+two same-template pages returns ~95% similar for every site, which is a
+confident false positive. So 30/70 stays an explicit LLM judgement over the
+≥3 same-family pages STEP 5 now samples for it — label it as judgement in the
+report, never as a measurement, and never quote a similarity percentage you
+did not compute.
+
 Report: top queries; flag **QUICK WINS** = rows with position between 4
 and 10 AND high impressions (candidates to push onto page 1 with a
 title/meta/content tweak). Report index coverage from `inspect`. All
 emitted into SEO.md §2 (technical) and §8 (quick wins).
 
+**`inspect` also returns `rich_results` — Google's own structured-data
+verdict on the live indexed URL.** It rides the same response (no extra
+call, no extra quota). This is the only programmatic JSON-LD validation in
+the system; everything else about schema is read by eye.
+
+```
+rich_results.verdict : PASS | FAIL | NEUTRAL | VERDICT_UNSPECIFIED | ABSENT
+rich_results.types[] : {type, items, errors, warnings, issues[]}
+```
+
+- `FAIL` + a type carrying `errors > 0` → that type **cannot show as a rich
+  result**. Bundle item, cite the `issues[]` message verbatim — it is
+  Google's wording, not ours, and geo-analyzer owns the JSON-LD fix
+  (CROSS-AGENT NOTE).
+- `warnings` → recommended fields missing. Report, do not gate on them.
+- **`ABSENT` means Google detected no rich results on this URL** — the key
+  is omitted upstream when nothing is found. It is NOT an error and NOT
+  proof the markup is broken: a page with no structured data reads the same
+  as one whose markup Google never parsed. Say "none detected", never
+  "invalid".
+- `ABSENT` while the repo clearly ships JSON-LD → real finding: the markup
+  is not reaching Google (SPA-rendered, blocked, or malformed). Cross-check
+  before claiming it.
+
+**Bound this honestly.** `index:inspect` is per-URL, quota'd, and works only
+on a GSC-verified property. It validates the URLs you sampled — not the
+site. Its reach is the STEP 9 COVERAGE ratio, and §14 must say so rather
+than let one PASS imply site-wide valid markup.
+
 If `status=degraded` → note it in §2 and emit the §11 user action
 "Connecter GSC: `make seo-connect`".
 
@@ -359,8 +503,118 @@ Fetch rendered HTML. Extract and analyze:
 
 ## STEP 5 — ON-PAGE AUDIT `[both]`
 
+### Rendering gate (R2) — it gates every on-page check below
+
+```bash
+bash ~/.claude/lib/seo-data/fetch.sh rendercheck --url "https://$DOMAIN/"
+```
+
+STEP 2 has always recorded `RENDERING: SSR/SSG/SPA/hybrid` and nothing ever
+acted on it. This is the rule that does. The verdict comes from what the
+server actually sent, not from reading package.json — a React SPA and a
+Next.js SSR app are indistinguishable there.
+
+**`verdict: client-rendered` → REFUSE to score the On-page axis.** Do not
+score it low. Do not score it at all:
+- On-page → `N/A — content not in served HTML (client-rendered)`. Redistribute
+  nothing; a missing axis is not a zero.
+- Every curl-based meta/H1/JSON-LD check would report "missing" against a site
+  that may be perfectly correct once hydrated. Those are FALSE findings, and
+  a bundle built on them would "fix" meta tags that already exist.
+- **No bundle item may come from a live on-page check on this site.** Source
+  greps still apply — the JSX carries the tags — but you cannot tell which
+  route renders what, so treat them as inventory, not as per-page findings.
+- `linkgraph` will refuse too (`no_links_in_html`) — the same blindness. Do
+  not work around either refusal.
+
+Still fully auditable, and worth saying so rather than returning an empty
+report: robots.txt, sitemap.xml, HTTP headers, redirects, `.htaccess` /
+framework config, CWV via CrUX (field data is real-user, hydration included),
+GSC queries + index coverage, legal pages, image weights.
+
+**`verdict: partial`** → shell plus an SSR'd head, or a genuinely thin page.
+Score what is present, name what is not, and say which of the two you think
+it is.
+
+**§0 line, mandatory when not server-rendered:**
+`Rendering: client-rendered — On-page NOT scored (content absent from served
+HTML). Global score excludes it. Fix: SSR/SSG (CLAUDE.md: public sites are
+never SPAs).`
+
+This is the honest half of the R1/R2 call: we do not render JS (no Playwright,
+no Chromium), so we do not pretend to see what JS paints. Refusing is the
+finding.
+
+**Record the denominator BEFORE sampling.** This step samples; the report
+says "audit". On a 500-page site a 12-page sample is 2.4% — the On-page score
+is an extrapolation from it, and the reader cannot know unless you print it.
+
+```bash
+bash ~/.claude/lib/seo-data/fetch.sh sitemap --url "https://$DOMAIN/sitemap.xml"
+```
+
+Returns `{count, urls[], index, dropped, ...}` — the coverage denominator and
+your sampling frame. It follows a `<sitemapindex>` one level, dedupes, strips
+whitespace, and handles `.xml.gz`. No auth, no venv, no Google.
+
+Read it honestly:
+- `count` → the denominator for the STEP 9 COVERAGE line.
+- `dropped > 0` → entries that were not usable URLs. Worth a §14 line: a
+  sitemap emitting junk is a tooling finding.
+- `children_failed > 0` or `children_skipped` → the frame is incomplete. Say
+  so; do NOT present a partial denominator as the total.
+- `status: degraded` → denominator UNKNOWN. Print that, never let silence
+  imply full coverage. `reason: unsafe_xml_dtd` is not a glitch — a sitemap
+  carrying a DTD is broken tooling or a billion-laughs aimed at the auditor.
+  Report it as a finding.
+
+**Guard every URL before it reaches curl.** These come from the target's own
+server, not from the operator — the one place in this audit where a remote
+file's bytes flow into a shell:
+
+```bash
+U="$(bash ~/.claude/lib/url-guard.sh url "$RAW_FROM_SITEMAP")" || continue
+```
+
+The verb applies a garbage filter, not that guard; the guard belongs at the
+point of use (same contract as the sameAs check in geo-analyzer).
+
 ### Meta tags per page (sample 5-15 key pages)
 
+**Group the sitemap URLs into families first** — a family is "pages one
+template renders". You do not need framework routing knowledge to see them,
+but you DO need to look at the actual URL shape, because it varies:
+
+| Layout | Example | Family signal |
+|---|---|---|
+| Nested | `/creation-site-internet/essonne-91/`, `/creation-site-internet/seine-et-marne-77/` | **shared parent path** → 25 pages, 1 family |
+| **Flat** | `/lavage-auto-pomponne`, `/lavage-auto-torcy`, `/lavage-auto-chelles` | **shared slug prefix** → 8 pages, 1 family |
+
+Both are real, measured on two live sites. First-path-segment alone handles
+the nested case and **fails the flat one**: those 8 city pages read as 8
+unrelated singletons, so the largest "family" becomes `/services` (5) and the
+doorway-page risk — the exact thing the 30/70 rule exists to catch — is
+invisible. Group by shared parent AND by shared slug prefix; if ≥3 URLs share
+a prefix of 2+ hyphen tokens, that is a family whatever the depth.
+
+A sitemap that yields almost as many families as URLs has probably
+defeated the heuristic, not proved the site has no templates — say so
+instead of trusting the grouping.
+
+**Sample by finding class, because the classes need opposite samples:**
+
+| Looking for | Sample | Why |
+|---|---|---|
+| Code defects (canonical, OG, `<img>` dims, hreflang) | **1 per family** | one template renders the whole family — a missing canonical in `[dept]/index.astro` breaks all 25 identically. 1 per family ≈ 100% SOURCE coverage for ~8 fetches. |
+| **Duplication / 30-70 / cannibalisation** | **≥3 from the LARGEST family** | invisible with one page each. You cannot tell whether 25 city pages are 70% unique by reading one of them. |
+| Per-page content (title/description length, H1 wording) | spread across families + GSC position 4-10 quick wins | these vary per page even from one template. |
+
+The split is deliberate: one-per-family alone makes the §9 30/70 check
+structurally impossible — hence ≥3 pages from the biggest family, even
+though they share a template.
+
+An un-sampled family is an un-audited family. Name the ones you skipped.
+
 For each sampled page:
 ```
 PAGE: <path>
@@ -396,10 +650,27 @@ grep -rE '<img[^>]*>' --include="*.html" --include="*.astro" --include="*.tsx" -
 # Images missing dimensions (CLS risk)
 grep -rE '<img[^>]*>' --include="*.html" --include="*.astro" --include="*.tsx" --include="*.jsx" --include="*.php" . 2>/dev/null | grep -vE 'width=|height=' | head -30
 
-# Check image asset sizes
-find . -type f \( -iname "*.jpg" -o -iname "*.jpeg" -o -iname "*.png" -o -iname "*.gif" \) ! -path "./node_modules/*" ! -path "./.git/*" -printf "%s %p\n" 2>/dev/null | sort -rn | head -20
+# Check image asset sizes — source only, never build output (C1a)
+mapfile -t FEXCL < <(bash ~/.claude/lib/source-scope.sh findargs)
+find . "${FEXCL[@]}" -type f \( -iname "*.jpg" -o -iname "*.jpeg" -o -iname "*.png" -o -iname "*.gif" \) -printf "%s %p\n" 2>/dev/null | sort -rn | head -20
 ```
 
+**Why the guard, and why `find` specifically (C1a).** Claude Code routes
+`grep` through ugrep with `--ignore-files` (honours `.gitignore`); `find`
+honours nothing. Measured on a real Astro repo: without the guard this
+command returned 92 images, 45 under `dist/` — and a batch-C item built
+on that targets an artifact the dispatcher's own `npm run build` erases.
+
+`FEXCL` MUST be consumed as a quoted array. `find . $FEXCL …` lets the shell
+glob `*/dist/*` against the CWD and hand the matches to find as search paths
+— that made the same run return 135 hits and kept every `dist/` file.
+
+Do NOT add these exclusions to the `grep` lines: the shim already covers
+them, `public/` is deliberately kept (it is Astro/Vite/Next SOURCE and holds
+`favicon.ico`, `apple-touch-icon.png`, `robots.txt` — the very files STEP 4
+curls), and it is build output only for Hugo/Gatsby, which the script
+detects.
+
 Flag images over 100 KB as compression candidates. WebP/AVIF preferred
 over JPEG/PNG.
 
@@ -420,6 +691,34 @@ Each embedded or self-hosted video should have:
 
 ### Internal linking + topic clusters (silos sémantiques)
 
+```bash
+bash ~/.claude/lib/seo-data/fetch.sh linkgraph --url "https://$DOMAIN/sitemap.xml"
+```
+
+**This answers the two questions below, which this spec has always asked and
+never had a command for (C3).** Crawls every sitemap URL once, extracts
+internal `<a href>`, and returns `orphans`, `beyond_3_clicks`, `unreachable`,
+`max_depth`. Measured cost: 24 pages in 2.7 s, 86 in 3.8 s — cheap enough to
+always run on FULL.
+
+Read it honestly:
+- `orphans` present → real finding, act on it.
+- **`orphans_withheld: true` → there is NO orphan list, and you must not
+  invent one.** It appears when the crawl was capped or any page failed. An
+  orphan cannot be sampled: proving a page has no inbound link means having
+  read every other page, so a partial crawl invents orphans. "Page X has no
+  inbound links" when it does sends the client fixing what is not broken.
+  §14 line, not a finding.
+- `reason: no_links_in_html` → **not a site with zero links; a site whose
+  links are rendered by JS.** Every page would look orphaned — the worst false
+  positive this tool could emit — so the verb refuses instead. Flag the SPA in
+  §0 and stop; do not hand-roll a link audit around it.
+- `unreachable` ⊃ `orphans`: a page can have inbound links yet sit outside the
+  homepage's reach (linked only from another unreachable page). Both matter,
+  they are not the same finding.
+- `max_depth` > 3 → `beyond_3_clicks` names the pages. That is the ":613"
+  check, now measured rather than asserted.
+
 Sample critical pages. Check:
 - Every important page reachable within 3 clicks from homepage?
 - Navigation consistent?
@@ -469,6 +768,10 @@ Validate:
 
 ---
 
+> **MODE BOUNDARY — `MODE: collect` ends at STEP 5**: write the signals
+> file + `COLLECTION COMPLETE — RUNID: <RUNID>` terminal line, emit the
+> COLLECT REPORT, stop. STEP 6-11 below are `MODE: judge` territory.
+
 ## STEP 6 — EXTERNAL PRESENCE AUDIT `[FULL only, local business only]`
 
 **Skip if not a local business** (pure SaaS, content-only → jump to STEP 7).
@@ -616,29 +919,136 @@ FIX: AUTO (<what agent will do>) | USER (<what user must do>)
 
 | Axis | Weight (local B2C) | Weight (SaaS/national/content) | Score /20 |
 |---|---|---|---|
-| Technical (perf, CWV, security headers, indexability) | 20% | 30% | |
+| Technical (perf, CWV, indexability) | 20% | 30% | |
 | On-page (content, meta, headings, images, video, a11y, i18n) | 20% | 30% | |
 | SEO Local (NAP, GMB, citations) | 25% | 5% | |
-| Off-page (backlinks, mentions, authority) | 10% | 15% | |
+| Off-page (unlinked brand mentions — backlinks/authority NOT auditable, §14) | 10% | 15% | |
 | Social presence | 10% | 5% | |
 | Competitive position | 5% | 10% | |
 | Legal compliance | 10% | 5% | |
 
+**Compute the scores, do not feel them (I7).** Emit your findings, then let
+the engine do the arithmetic:
+
+```bash
+bash ~/.claude/lib/seo-data/fetch.sh score --findings /tmp/seo-findings.json
+```
+
+```json
+{"depth":"FULL","profile":"local",
+ "axes":{"technical":{"findings":[{"severity":"haute","affected":9,"sampled":12}]},
+         "on-page":{"status":"na","reason":"client-rendered (R2)"},
+         "off-page":{"status":"na","reason":"backlinks unauditable (I1)"}}}
+```
+
+`profile`: `local` (B2C) | `national` (SaaS/national/content). Severities are
+`critique|haute|moyenne|basse` — `/harden`'s scale (-15/-8/-3/-1, clamp,
+then /5 into /20), so the whole skill family speaks one vocabulary.
+
+**The split matters.** WHICH findings exist and how severe each is stays your
+judgement — irreducible. The addition is not: same findings in, same score
+out. Until now every axis was felt, so two runs over identical code could
+disagree, and `/client-handover` gates on 17/20.
+
+- `affected`/`sampled` (optional) shift severity ONE step: ≥50% of the sample
+  escalates, a single page de-escalates. A defect on 1 of 12 pages is not the
+  defect on 12 of 12; pretending so is what made the old numbers wobble.
+- `status: "na"` → the axis is EXCLUDED and the remaining weights are
+  renormalised for you. This is the R2 rule (client-rendered on-page) and the
+  I1 rule (unauditable off-page), finally computed instead of done by hand.
+  **N/A is not a zero** and the engine will not let it behave like one.
+- `status: "error"` → malformed findings. Fix them; never fall back to
+  eyeballing a number.
+- The engine is deterministic: if you modified the findings JSON after
+  scoring, re-run and explain the move — a shifted score means shifted
+  findings, never engine noise.
+
 **Technical axis note:** CWV scored on CrUX field data (75th percentile,
 real users, from STEP 4) when available; otherwise lab PageSpeed
 Lighthouse run.
 
+**Security headers are NOT scored here (I4).** `/harden` owns them and
+grades them out of 100 with three external validators — pricing them into
+this axis too was double-counting the same finding in two reports
+(`depth-matrix.md:29` already said drop; this spec contradicted it).
+- Dispatched from `/harden` (its prompt says NARROW-SCOPE): headers ARE the
+  job — audit and score them per its brief, ignore this note.
+- Dispatched from `/seo`: do not score CSP, HSTS, X-Frame-Options,
+  X-Content-Type-Options, Referrer-Policy, Permissions-Policy, COOP/CORP,
+  cookie flags. STEP 4 still reads them — you need them for the one
+  carve-out below — but they earn and lose no points here.
+
+**Carve-out — `X-Robots-Tag` stays.** It is an indexing directive wearing a
+header's clothes: `noindex` served there deindexes the page as surely as a
+meta robots tag. Score it under indexability. That is what
+`depth-matrix.md:29` means by "unless it directly affects indexability" —
+it is the header that does, and the security headers above are not.
+
+**Drop ≠ silence.** A user who never runs `/harden` must not read a clean
+Technical score as clean headers. Whenever depth=FULL, emit in §14:
+`Security headers (CSP, HSTS, X-Frame-Options…) — not scored here: /harden
+owns them (0-100 + Observatory/SecurityHeaders/SSL Labs). Run /harden
+<url>. Observed live this run: <present list | none observed>.`
+Name what you saw. An omission has to stay legible — the same reason
+COVERAGE is mandatory in STEP 9.
+
+**On-page axis note (R2).** `rendercheck` verdict `client-rendered` → this
+axis is `N/A — content not in served HTML`, excluded from the weighted global,
+NOT scored zero. A zero says "your on-page is bad"; N/A says "we could not
+see it", and only one of those is true. Renormalise the remaining weights over
+the axes actually scored and say so on the SEO GLOBAL line. The code ceiling
+must state that no code fix raises an axis we did not measure — the unlock is
+SSR/SSG, and that is a user action, not a bundle item.
+
+**Off-page axis note (I1).** Score ONLY the unlinked brand mentions
+gathered in STEP 6 (`web_search "<business-name>" -site:<domain>`).
+Backlink profile and domain authority have NO data source here — no index,
+no API, nothing. NEVER price them into the number: an unmeasured
+sub-component cannot be judged, and this axis carries 10-15% of a score
+that reaches a client via `/client-handover`. A low mention count is a low
+mention count — it is NOT evidence of a weak backlink profile.
+
+Mandatory §14 line whenever depth=FULL, verbatim:
+`Backlinks / domain authority — NOT audited: no free backlink index is
+practical, and none is wired. Commercial: Ahrefs / Semrush / Majestic. The
+Off-page score above prices in brand mentions only.`
+
+**This is the final state, not a placeholder (B1 killed, 2026-07-17.)** The
+free options were measured, not assumed:
+- **GSC has no links endpoint.** The Search Console API exposes exactly
+  Search Analytics, Sitemaps, Sites, URL Inspection. The Links report is
+  UI-only.
+- **Common Crawl's hyperlinkgraph is 17.3 GB gzipped** for the domain-edges
+  file alone (+879 MB vertices, +2.3 GB ranks), measured live. Finding one
+  domain's inbound links means scanning all of it, per audit. Not slow —
+  non-viable, and abusive toward a nonprofit serving it free. The reference
+  implementation everyone cites caps its download at 500 MiB, i.e. **2.9% of
+  the edges file**, and reports whatever that arbitrary slice contained as a
+  backlink profile. That is a random sample wearing a measurement's clothes,
+  which is precisely what this axis note exists to prevent.
+- **Bing Webmaster's `GetUrlLinks` is the only free, viable source** — but it
+  is first-party only (your verified properties), so it can never cover a
+  competitor, and it needs the client's Bing account. See W2, deferred.
+
+So: no number here beats a fabricated one. Weight deliberately unchanged —
+re-deriving it for an axis that is not going to widen would churn historical
+scores for nothing.
+
 ### LOCAL depth — 4 axes
 
 | Axis | Weight (local B2C) | Weight (SaaS/national/content) | Score /20 |
 |---|---|---|---|
-| Technical (security headers, indexability, config) | 25% | 35% | |
+| Technical (indexability, config) | 25% | 35% | |
 | On-page (content, meta, headings, images, video, a11y, i18n) | 35% | 45% | |
 | SEO Local (markup, NAP in JSON-LD, legal) | 20% | 5% | |
 | Legal compliance (pages, CMP, mentions) | 20% | 15% | |
 
 LOCAL axes not audited (Off-page, Social, Competitive) appear as
-`N/A — requires FULL audit` in the report.
+`N/A — requires FULL audit` in the report. Off-page is the exception to
+that promise: FULL audits its brand-mentions share ONLY — backlinks and
+authority are unauditable at EVERY depth (see the Off-page axis note).
+Print `N/A — FULL audits brand mentions only` for it, never a bare
+"requires FULL audit" that FULL cannot keep.
 
 ### Projected code-only score + trajectory to 17/20 (mandatory)
 
@@ -676,6 +1086,9 @@ misroutes the client-handover gate and the user's effort.
 
 ```
 SEO SCORING (<depth>)
+COVERAGE SOURCE: <N> of <M> page templates (<P>%) — skipped: <list|none>
+COVERAGE LIVE  : <N> of <M> sitemap URLs (<P>%) — families: <fam N/M, …>
+                 | UNKNOWN (no sitemap / fetch degraded)
 Technical      : XX/20  <justification>
 On-page        : XX/20  <justification>
 SEO Local      : XX/20 | N/A
@@ -687,6 +1100,28 @@ Legal          : XX/20  <justification>
 SEO GLOBAL (weighted): XX.X/20 (<depth>)
 ```
 
+**Both COVERAGE lines are mandatory, never omitted, never rounded up.** They
+are the honesty bound on every page-level axis: On-page and the on-page share
+of Technical are extrapolations from the sample, and `/client-handover` gates
+on these numbers.
+
+**Report both, because they bound different findings — do not average them
+into one comforting number.**
+- **SOURCE** bounds CODE findings. One template renders its whole family, so
+  1 page per family can legitimately reach 100% here. High SOURCE coverage is
+  a real claim: the code paths were seen.
+- **LIVE** bounds CONTENT findings — title/description wording, thin pages,
+  30/70 duplication. It stays low by design and that is fine, as long as it
+  is printed. Measured on a real site: 12 of 86 URLs is 14% LIVE while the
+  same 12 pages are 100% SOURCE. Reporting only the 14% understates the audit;
+  reporting only the 100% oversells it. Both, or neither means anything.
+- LIVE < 25% → repeat in §0. A 17/20 for content drawn from 3% of a site is
+  not a 17/20.
+- SOURCE < 100% → name the skipped templates in §0. That is not a sampling
+  choice, it is code nobody read.
+- Denominator UNKNOWN (no sitemap, or `sitemap` degraded) → print UNKNOWN.
+  Never let silence imply full coverage.
+
 Per user instruction: this score represents **80% of the combined
 final score for local B2C (20% for GEO), or 75% for SaaS/national
 (25% for GEO)**. The `/seo` dispatcher combines SEO and GEO scores.
@@ -702,22 +1137,19 @@ For each:
 - Expected impact (high / medium / low)
 - AUTO (bundled in STEP 12, applied by the dispatcher) or USER (in SEO.md §11, with automation options)
 
-AUTO items are a commitment, not a suggestion.
+**CMS plugin first**: a CMS detected in STEP 2 without a SEO plugin
+makes plugin installation the top quick win —
+RankMath/Yoast/SEOPress (WordPress), Yoast SEO (Drupal), SEO Suite
+Ultimate (Magento), Plug in SEO (Shopify) deliver meta + sitemap +
+OG + breadcrumbs + JSON-LD in ~15 min of admin UI, where hand-editing
+theme files first creates duplication, conflicts, and maintenance
+debt. See `~/.claude/agents/resources/automation-catalog.md` CMS
+plugins section for the exact install path per CMS.
 
-**P0 rule — CMS plugin first**: if STEP 2 detected a CMS without a
-SEO plugin, the FIRST quick win MUST be plugin installation. Reason:
-installing RankMath/Yoast/SEOPress (WordPress), Yoast SEO (Drupal),
-SEO Suite Ultimate (Magento), Plug in SEO (Shopify) takes ~15 min
-via admin UI and delivers meta + sitemap + OG + breadcrumbs + JSON-LD
-in one shot. Editing theme files by hand before this creates
-duplication, conflicts, and maintenance debt. See
-`~/.claude/agents/resources/automation-catalog.md` CMS plugins
-section for the exact install path per CMS.
-
-**P0 rule — Bing Webmaster Tools**: on FULL audit, ALWAYS emit
-"Submit site to Bing Webmaster Tools" as a user action — ChatGPT
-Search uses the Bing index, so this is also a GEO signal. See
-automation-catalog.md for IndexNow + Bing.
+**Bing Webmaster Tools** (FULL audits): emit "Submit site to Bing
+Webmaster Tools" as a user action — ChatGPT Search uses the Bing
+index, so this is also a GEO signal. See automation-catalog.md for
+IndexNow + Bing.
 
 ### Medium term (1-3 months)
 City/service pages (30/70 rule: 30% shared, 70% unique per city),
@@ -772,10 +1204,15 @@ BATCH F — USER ACTIONS (N items, documented in SEO.md §11 with automation cat
   ...
 ```
 
-Do not proceed to STEP 12 until this plan is printed.
+Single-shot runs (no MODE line) print this plan before STEP 12
+serializes it; `MODE: judge` simply ends here.
 
 ---
 
+> **MODE BOUNDARY — `MODE: judge` ends at STEP 11** (scoring + findings +
+> plan + batches reported, nothing serialized). STEP 12-14 below are
+> `MODE: template` territory, operating on the judge report verbatim.
+
 ## STEP 12 — EMIT FIX BUNDLE `[both]`
 
 **You do NOT apply fixes and you do NOT dispatch any sub-agent.** Same
@@ -860,18 +1297,19 @@ as the last line of the bundle — the dispatcher keys its apply step on it.
 Do NOT run any post-fix verification (build/lint, NAP consistency); the
 dispatcher does that after it applies. Your job ends at the sentinel.
 
-### Bundle completeness checklist (did every finding reach the bundle?)
+### Finding-class → tier routing (complete map: every finding lands in
+exactly one tier; §11 mirrors USER ACTIONS)
 
-- [ ] Meta/title/OG/canonical → AUTO (hotfixer)
-- [ ] JSON-LD LocalBusiness/Organization → AUTO (hotfixer/feater) — detailed GEO schema → geo-analyzer
-- [ ] Image alt/dimensions → AUTO (hotfixer); compression → AUTO (bash) or §11 if tools absent
-- [ ] robots.txt / sitemap.xml → AUTO (hotfixer) — AI-bot directives → geo-analyzer
-- [ ] .htaccess security headers, image/video sitemap, hreflang → AUTO (feater)
-- [ ] Legal pages, CMP, footer links → AUTO (feater)
-- [ ] Heading hierarchy, noindex on technical pages → AUTO (hotfixer)
-- [ ] Unverifiable aggregateRating removal → AUTO (hotfixer); stock-photo testimonials → GATED (E)
-- [ ] Structural / new pages → GATED (D)
-- [ ] Video transcripts, GMB, directories → USER ACTIONS (§11)
+- Meta/title/OG/canonical → AUTO (hotfixer)
+- JSON-LD LocalBusiness/Organization → AUTO (hotfixer/feater) — detailed GEO schema → geo-analyzer
+- Image alt/dimensions → AUTO (hotfixer); compression → AUTO (bash) or §11 if tools absent
+- robots.txt / sitemap.xml → AUTO (hotfixer) — AI-bot directives → geo-analyzer
+- .htaccess security headers, image/video sitemap, hreflang → AUTO (feater)
+- Legal pages, CMP, footer links → AUTO (feater)
+- Heading hierarchy, noindex on technical pages → AUTO (hotfixer)
+- Unverifiable aggregateRating removal → AUTO (hotfixer); stock-photo testimonials → GATED (E)
+- Structural / new pages → GATED (D)
+- Video transcripts, GMB, directories → USER ACTIONS (§11)
 
 ### Framework-specific notes
 
@@ -893,23 +1331,6 @@ Carry the relevant note into each bundle item so the applier honors it:
 - **Ghost** — Native SEO strong (meta + OG + JSON-LD out of box). Usually no plugin needed; handle gaps via `default.hbs` edits.
 - **Wix / Squarespace / Webflow (hosted CMS)** — No theme file access. ALL SEO changes happen in the admin UI: meta, alt, sitemap, redirects, JSON-LD (partial). Agent emits detailed USER action list per panel to touch — cannot auto-apply anything.
 
-### Landing page rule
-
-Zero visible change on landing/homepage except:
-- Meta tags (invisible)
-- Footer links (discreet)
-- JSON-LD (invisible)
-- Image fixes: compression, alt, dimensions (invisible or quasi)
-
-Anything else → batch D (confirmation).
-
-### Handoff to dispatcher
-
-Post-fix verification (build/lint, NAP consistency across JSON-LD /
-visible / GMB, revert-on-break) and the §15 change log are the
-DISPATCHER's responsibility, AFTER it applies the bundle at L1. You
-emitted the bundle terminated by the sentinel — stop here.
-
 ---
 
 ## STEP 13 — OUTPUT `[both]`
@@ -1044,6 +1465,15 @@ PROCHAINE ETAPE : <highest-priority>
   `Write` on shared templates. `Write` is reserved for files you
   solely own: sitemap.xml, .htaccess, legal pages, new city/service
   pages. Full-template refactor → escalate as user action in §11.
+- **NEVER emit a bundle item targeting build output (C1a).** No path under
+  `dist/ build/ .next/ .nuxt/ .output/ _site/ .astro/ .svelte-kit/ out/` —
+  `bash ~/.claude/lib/source-scope.sh list` is the authoritative set. Those
+  files are regenerated: the `npm run build` the dispatcher runs to VERIFY
+  your fix is what erases it. The fix lands, verification passes, nothing
+  survives, and the report claims it was applied. This bites batch C hardest
+  (`cwebp -q 80 <img> -o <img>.webp` on a `dist/` asset writes a `.webp` the
+  next build deletes). Fix the SOURCE that generates the artifact; if you
+  cannot find it, that is a finding — say so, do not patch the artifact.
 - **Landing page protection.** Zero visible change except meta tags,
   footer links, JSON-LD, image optimization.
 - **Preserve existing valid SEO.** Don't rewrite correct tags.
@@ -1064,10 +1494,10 @@ PROCHAINE ETAPE : <highest-priority>
 ### Process
 - **Every user action lists automation.** Mandatory from
   `~/.claude/agents/resources/automation-catalog.md`.
-- **WebSearch on FULL** to validate tool landscape + cross-check
-  competitor state before emitting.
+- **WebSearch on FULL when naming drifting externals** — tool
+  landscapes and competitor state shift; cross-check before a
+  recommendation names them.
 - **Iterative SEO.md.** Preserve Historique section.
-- **Transparency.** Every automated change logged with file, change,
-  reason.
-- **Dispatcher verifies.** Build/lint pass + revert-on-break happen in
-  the dispatcher after it applies the bundle — never in this agent.
+- **Dispatcher verifies.** Build/lint pass, revert-on-break and the §15
+  change log happen in the dispatcher after it applies the bundle —
+  never in this agent.

agents/status-reporter.md

@@ -1,6 +1,6 @@
 ---
 name: status-reporter
-description: Read-only project-status engine — dispatched by /status. Collects plugins, token budget, git state, build/tests, GSD milestone into one snapshot.
+description: Read-only project-status engine — dispatched by /status. Collects plugin roster + passive-cost estimate (doctor.sh constants), git state, build/tests, GSD milestone into one snapshot.
 tools: Read, Bash, Glob, Grep
 model: haiku
 ---
@@ -23,8 +23,12 @@ cat ~/.claude/lib/../version.txt 2>/dev/null || echo "unknown"  # lib symlink re
 command -v rtk &>/dev/null && echo "rtk: installed" || echo "rtk: missing"
 command -v gsd &>/dev/null && gsd --version 2>/dev/null | head -1 || echo "gsd: not installed"
 
-# Token estimate (passive)
-# (approximate from known plugin costs)
+# Passive token cost — source of truth: doctor.sh's constants block
+# (PLUGIN_TOKENS + <n> per detect_* line). Read it, sum ONLY the plugins
+# found active above. Never invent a number outside these constants.
+grep -E 'PLUGIN_TOKENS \+ [0-9]+' "$(readlink -f "$HOME/.claude/lib")/../doctor.sh" 2>/dev/null
+# grep empty (doctor.sh missing/moved) → report the plugin count only and
+# defer cost to /plugin-check.
 ```
 
 Check `~/.claude/plugins/cache` for active marketplace plugins.
@@ -134,7 +138,7 @@ PROJECT STATUS
 
 CONFIG
   Version   : v<N>
-  Plugins ON: <list> (~<X>t passive)
+  Plugins ON: <list> (~<X>t passive — doctor.sh constants; full audit → /plugin-check)
   GSD v2    : installed / not installed
 
 PROJECT
@@ -174,7 +178,7 @@ The report is best-effort: a single failing data source must not abort the whole
 |---|---|
 | Permission denied on `git` (sandbox/CI without `.git` access) | Mark `Branch: N/A (permission denied)`, `Uncommitted: N/A`, `RECENT COMMITS: N/A`. Continue to PROJECT/GSD sections. |
 | Permission denied on `~/.claude/plugins/cache` or `~/.claude.json` | Mark `Plugins ON: unknown (cannot read cache)`. Continue. |
-| `.gsd/ROADMAP.md` exists but unparseable (malformed checkboxes, encoding issue) | Mark `Progress: N/A (ROADMAP.md unreadable)`, do NOT abort the section — still print `Status: initialized` and `Milestone: N/A`. |
+| gsd CLI snapshot fails or `.gsd/` state unreadable (`gsd.db`, `STATE.md`, per-milestone `<ID>-ROADMAP.md` — post-ADR-013 layout) | Mark `Progress: N/A (gsd state unreadable)`, do NOT abort the section — still print `Status: initialized` and `Milestone: N/A`. |
 | `package.json` / `pyproject.toml` parse error | Mark `Tests: N/A (manifest parse error)`. Continue. |
 | `python3` not available in PATH | Skip the python parsing fallbacks; rely on log files + bash-only checks. Mark Tests as `unknown` if no log found. |
 | All sections fail | Print a minimal envelope with each section showing `N/A (data source unavailable)` and a one-line `DIAGNOSTIC: <which sources failed>` footer. Exit code 0 (status reporter never blocks). |

agents/validator-analyzer.md

@@ -2,6 +2,7 @@
 name: validator-analyzer
 description: Web standards audit agent — W3C HTML validity (validator.nu), W3C CSS validity (jigsaw.w3.org), WCAG 2.1 accessibility (axe-core, pa11y, WAVE). Dispatched from /web-validate. Produces scored .claude/audits/VALIDATE.md report with concrete diffs for auto-fixable issues and user actions for judgment-required fixes. Complementary to /harden (security), /seo (indexability), /geo (AI extraction).
 tools: Read, Edit, Write, Bash, Grep, Glob, WebFetch
+model: sonnet
 ---
 
 # Validator — W3C + WCAG audit

agents/verifier.md

@@ -48,6 +48,25 @@ Rules: read the diff AND enough surrounding code to judge behavior; run
 criterion. Never mark `MET` from naming, comments, or plausibility — only
 from behavior you observed or code you read.
 
+### Criteria carrying an oracle (`CHECK:` / `EXPECT:` / `EVIDENCE:`)
+
+`lib/gates.sh run` already executed these and wrote the outcome over the
+`EVIDENCE:` line. Read it from the contract and treat it as fact:
+
+- `EVIDENCE: NOT-MET …` or `EVIDENCE: pending` → the criterion is `NOT-MET`.
+  Reading the code NEVER overrides a red or unrun oracle. Cite the evidence
+  line as your evidence.
+- `EVIDENCE: MET …` → the declared command passed. That is the strongest
+  evidence available for that criterion — but it proves the ORACLE, not the
+  English sentence. Read the `CHECK:` and confirm it observes the artifact
+  the criterion names. A vacuous oracle (`1. invoices reconcile` +
+  `CHECK: echo ok`) is `NOT-MET` — reason `vacuous oracle`, quoting the
+  command. That judgement is yours alone; no command can make it.
+
+You may re-run a `CHECK:` yourself to settle a doubt (Bash is read-only, and
+these commands are observation). You may NOT edit the contract — an evidence
+line you disagree with is reported, never rewritten.
+
 ## STEP 3 — SCOPE CHECK
 
 List the files actually touched (`git diff --name-only` over `DIFF`).
@@ -58,19 +77,30 @@ only enters the contract through a human micro-gate.
 
 ## STEP 4 — VERDICT
 
-`CONFORME` ⇔ ALL criteria `MET` AND zero out-of-scope files.
-Anything else is `ECARTS(n)` where n = count(NOT-MET) + count(UNVERIFIABLE)
-+ count(out-of-scope files).
+Read the contract's `ABANDON:` lines. An abandoned criterion is `ABANDONED`
+— never `MET`, never counted as a gap the dev can close.
+
+Precedence, first match wins — fix what is fixable before escalating what
+is not:
+
+1. `ERROR(<reason>)` — the contract is missing or unreadable.
+2. `ECARTS(n)` — n = count(NOT-MET) + count(UNVERIFIABLE) + count(out-of-scope
+   files). Surface any abandonment in the same report.
+3. `ABANDONED(n)` — zero gaps remain, but n abandonments stand. This is NOT
+   a pass and NOT a dev loop: it routes straight to the human gate.
+4. `CONFORME` — ALL criteria `MET`, zero out-of-scope files, zero
+   abandonments.
 
 ## OUTPUT (exact format — machine-parsed by the orchestrator)
 
 ```
-VERIFY — VERDICT: CONFORME | ECARTS(n) | ERROR(<reason>)
+VERIFY — VERDICT: CONFORME | ECARTS(n) | ABANDONED(n) | ERROR(<reason>)
 CONTRACT: <path>
 CRITERIA:
-  1. <criterion> — MET — <evidence file:line | test ran → result>
+  1. <criterion> — MET — <EVIDENCE line | file:line | test ran → result>
   2. <criterion> — NOT-MET — expected <…> / actual <…> — <file:line>
   3. <criterion> — UNVERIFIABLE — <reason>
+  4. <criterion> — ABANDONED — <the reason recorded in the contract>
 SCOPE: in-scope <n> files; out-of-scope: <list | none>
 PROOF: read <n> files, ran <cmd → result | nothing>, checked <n>/<n> criteria
 ```
@@ -82,6 +112,8 @@ PROOF: read <n> files, ran <cmd → result | nothing>, checked <n>/<n> criteria
 - `UNVERIFIABLE` ≠ `MET`. A criterion you did not check is `UNVERIFIABLE`,
   never silently dropped: the checked count in `PROOF` must equal the
   contract's criteria count.
+- `ABANDONED` ≠ `MET`. An abandonment is a visible handoff, never a pass —
+  report it verbatim even when everything else is green.
 - `PROOF` is MANDATORY. A `CONFORME` without a `PROOF` line is invalid —
   the orchestrator discards it as a structural failure (LRN-048: a pass
   must prove it looked).
@@ -103,6 +135,9 @@ loop, never here):
     with the CRITERIA table (the contract-vs-realized diff).
   - Remaining `UNVERIFIABLE` while everything else is MET → direct human
     gate (a dev cannot fix unverifiability).
+  - `ABANDONED(n)` → direct human gate, never a dev loop. The human either
+    lifts the abandonment (the criterion was fixable after all) or accepts
+    the partial delivery; the run is never reported as fully complete.
   - Structural failure (`ERROR(…)`, missing/duplicated VERDICT line,
     unparsable output, agent crash, `CONFORME` without `PROOF`) → retry
     ONCE with a fresh verifier; a 2nd structural failure → human

docs/plans/2026-06-27-deploy-skill.md

@@ -1,385 +0,0 @@
-# Deploy Skill — Implementation Plan
-
-> **Superseded by BDR-054** (`52f6678`): the shipped skill has NO `NEXT.sh` file and NO
-> AskUserQuestion hand-back — see `skills/deploy/SKILL.md` for current behavior. This
-> plan is kept as historical record; do not implement its NEXT.sh/hand-back sections.
-
-> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
-
-**Goal:** Build a `deploy` skill — a per-project shell runbook that re-instantiates from the delta since the last deploy, hands control to the user for out-of-band execution, resumes cold (even in a new session), and learns from deploy errors in place.
-
-**Architecture:** A surgical-commit helper (`lib/deploy-commit.sh`, allowlist-scoped to `.claude/deploy/`) is the foundation. Five per-project artifacts under `.claude/deploy/` carry runbook, incident ledger, deploy oracle, in-flight bridge, and the instantiated checklist. The skill is a two-moment SKILL.md (before → user deploys out-of-band → after, on the user's report), resumable cold from the JSON bridge per the `audit-delta` state-file convention. Bootstrap scaffolds the runbook for a project that has none.
-
-**Tech Stack:** Bash (helper + git), Markdown (SKILL.md + runbook + ledger), JSON (oracle + bridge). No new runtime deps — Claude reads JSON natively in skill steps; the helper never parses JSON.
-
-## Global Constraints
-
-- Surgical commits only: `deploy-commit.sh` commits via explicit argv pathspec, never `git add -A`. (mirror BDR-034/036)
-- Allowlist scope = `.claude/deploy/` ONLY; any other path is a loud rc-4 refusal. Inverse of `doc-commit.sh`'s `.claude/**` exclusion (BDR-022). Verified: real `doc-commit.sh` returns rc 4 on `.claude/deploy/PROCEDURE.md`.
-- Delta = `git diff --name-only <base_sha> HEAD` — **explicit two endpoints, no dots** (two-dot ≡ this; three-dot undercounts — verified). Never `git rev-list` ancestry (phantom deltas on rebase — verified).
-- First-deploy detection = `[ -f .claude/deploy/STATE.json ]` (deterministic). NEVER `git describe` (hard-errors rc 128 on no tag — verified).
-- Resume convention = `audit-delta`: "the state file is the only memory between runs; never infer prior scope from context." Bridge read at STEP 0.
-- Helper inherits from `lib/memory-commit.sh`/`lib/doc-commit.sh`: rc 3 on unsafe git state (detached/merge/rebase/cherry-pick), short-hash on stdout only on a real commit, per-file changed-paths filter, diagnostics to stderr.
-- User executes the deploy out-of-band (prod ssh) — the skill NEVER runs deploy commands itself.
-- Registries/spec language English; the spec of record is `docs/specs/2026-06-27-deploy-skill-design.md`.
-
----
-
-## Decisions resolved at plan time
-
-**§10 (cross-session state) — TRANCHÉ: separate bridge artifact.**
-- Bridge = `.claude/deploy/PENDING.json` (JSON), **distinct from the ephemeral `NEXT.sh`**, **uncommitted** (transient local working state; gitignored). Schema:
-  ```json
-  { "base_sha": "<deployed STATE sha>", "target_sha": "<HEAD at instantiation>",
-    "delta": ["supabase/migrations/0033_x.sql", "docker-compose.yml"],
-    "step_reached": "awaiting-user", "started_at": "<ISO-8601>", "runbook_rev": "<PROCEDURE.md commit sha>" }
-  ```
-- Follows `audit-delta` ("state file is the only memory between runs"). Resolves the n°1↔n°3 coupling: NEXT.sh stays ephemeral per §3; the bridge persists and carries base+target+delta so moment 3 lays the correct marker and capitalizes the correct incident — **without re-parsing shell**, readable cold.
-- Form-novelty (mid-flow pause-resume) is new → `writing-skills` formalizes the convention in Task 3.
-- **LIMIT (acknowledged, not to be discovered):** `PENDING.json` is gitignored ⇒ cold-resume is **same-machine only** — it does not survive a clone or a move to another machine. Acceptable because a project's deploys run from one local; recorded as a constraint, not assumed away.
-
-**§8 item 1 — tag push:** annotated tag `git tag -a deploy/<YYYY-MM-DD> <target_sha> -m "<summary>"` laid in MARK (success). **Project knob `# @config push_deploy_tags=true|false`** in the `PROCEDURE.md` header (default `false`): when true, MARK runs `git push origin deploy/<date>` — always **best-effort/non-fatal** (the push never blocks the deploy; tag is a bookmark, STATE.json is the oracle). Same-day re-deploy → suffix `-N`.
-
-**§8 item 2 — INCIDENTS ID/name:** `.claude/deploy/INCIDENTS.md`, append-only, entries `DEP-NNN` (next = `grep '^## DEP-' | max+1`), fields mirror `blockers.md`: date, step, error (verbatim), root cause, fix. Resolution derivable from git: the commit that adds the entry IS the fix (atomic patch+incident); recover via `git log -S 'DEP-NNN' -- .claude/deploy/INCIDENTS.md`. Name confirmed `INCIDENTS.md` (not `ERRORS-LEARNED.md`).
-
-**§8 item 3 — `@delta:` grammar:** directives on a runbook step's preceding comment line, patterns matched against the delta file list. `glob=` carries TWO required semantics (a single "checklist-only" reading was REJECTED — it breaks the game example, where step 3 runs `psql -f 0033` THEN `psql -f 0034` = one command PER file):
-- `# @delta:<name> glob=<pat>:each` — **repeat**: emit the step's command once per delta file matching `<pat>` (e.g. `psql -f <each>`).
-- `# @delta:<name> glob=<pat>:list` — **checklist**: emit the command once, with matching files as `# VERIFY:` items (e.g. `supabase migration up`).
-- `# @delta:<name> when=<pat>[,<pat>...]` — **conditional**: include the step only if the delta intersects any pattern (e.g. rebuild when compose/Dockerfile changed).
-- Patterns are git-pathspec/shell-glob; comma-separates alternatives. **Un-annotated step = fixed**, always emitted verbatim. The exact `:each`/`:list` keyword spelling is DEFERRED to `writing-skills` (Task 3); both semantics are mandatory.
-
-**§8 item 4 — frontmatter / gates:**
-```yaml
-name: deploy
-description: |
-  Use when deploying a project via its per-project runbook — instantiates the
-  delta since last deploy, hands off for out-of-band execution, resumes cold,
-  learns from errors.
-  Triggers: "deploy", "déploie", "run the deploy", "ship to prod", "deploy runbook".
-allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, AskUserQuestion]
-```
-Gate vocabulary reused from `capitalize`/`client-handover`: `all / pick <IDs> / edit <ID> / skip-all`. Gates marked **[GATE]** in Task 3.
-
----
-
-## File Structure
-
-- Create `lib/deploy-commit.sh` — surgical commit helper, allowlist `.claude/deploy/`. (Task 1)
-- Create `lib/tests/deploy-commit.test.sh` — real-git behavioral tests. (Task 1)
-- Create `skills/deploy/SKILL.md` — the two-moment skill. (Task 3)
-- Create `templates/deploy/PROCEDURE.md` — annotated starter runbook (scaffold source). (Task 2/4)
-- Create `templates/deploy/INCIDENTS.md` — empty ledger header. (Task 2)
-- Modify `.gitignore` — ignore `.claude/deploy/NEXT.sh` and `.claude/deploy/PENDING.json`. (Task 2)
-- Per-project, created at runtime (NOT in this repo): `.claude/deploy/{PROCEDURE.md, INCIDENTS.md, STATE.json, PENDING.json, NEXT.sh}`.
-
-**Artifact lifecycle:**
-
-| Artifact | Committed? | Lifecycle |
-|---|---|---|
-| `PROCEDURE.md` | yes (deploy-commit) | in-place edits (learning) |
-| `INCIDENTS.md` | yes (deploy-commit) | append-only `DEP-NNN` |
-| `STATE.json` | yes (deploy-commit) | overwritten on success = oracle |
-| `PENDING.json` | **no** (gitignored) | written at hand-back, deleted on success = cold-resume bridge |
-| `NEXT.sh` | **no** (gitignored) | regenerated per deploy, ephemeral checklist |
-
----
-
-### Task 1: `lib/deploy-commit.sh` — surgical commit helper (FOUNDATION, TDD)
-
-**Files:**
-- Create: `lib/deploy-commit.sh`
-- Test: `lib/tests/deploy-commit.test.sh`
-
-**Interfaces:**
-- Produces: `deploy-commit.sh pending <file>...` → exit 0 if any passed file in-scope has changes, else 1. `deploy-commit.sh commit "<msg>" <file>...` → commits ONLY passed in-scope files, prints short hash on stdout; rc 0 success, rc 1 clean/no-op, rc 3 unsafe git state, rc 4 out-of-scope path.
-- Consumes: nothing (foundation).
-
-- [ ] **Step 1: Write the failing test harness**
-
-```bash
-# lib/tests/deploy-commit.test.sh
-#!/usr/bin/env bash
-set -u
-H="$(cd "$(dirname "$0")/.." && pwd)/deploy-commit.sh"
-pass=0; fail=0
-mkrepo() { local d; d=$(mktemp -d); git -C "$d" init -q; git -C "$d" config user.email t@t;
-  git -C "$d" config user.name t; mkdir -p "$d/.claude/deploy"; printf 'x\n' >"$d/seed";
-  git -C "$d" add seed; git -C "$d" commit -q -m seed; printf '%s' "$d"; }
-check() { if [ "$2" = "$3" ]; then pass=$((pass+1)); else fail=$((fail+1));
-  printf 'FAIL %s: got[%s] want[%s]\n' "$1" "$2" "$3"; fi; }
-
-d=$(mkrepo); printf 'run\n' >"$d/.claude/deploy/PROCEDURE.md"
-out=$( cd "$d" && bash "$H" commit "docs(deploy): t" .claude/deploy/PROCEDURE.md ); rc=$?
-check T1-rc "$rc" 0
-check T1-committed-only "$(git -C "$d" show --name-only --format= HEAD)" ".claude/deploy/PROCEDURE.md"
-check T1-hash-nonempty "$([ -n "$out" ] && echo y || echo n)" y
-
-d=$(mkrepo); printf 'b\n' >"$d/src.txt"
-( cd "$d" && bash "$H" commit "x" src.txt ) >/dev/null 2>&1; check T2-out-of-scope-rc "$?" 4
-
-d=$(mkrepo)
-( cd "$d" && bash "$H" commit "x" ".claude/deploy/../memory/secret" ) >/dev/null 2>&1
-check T3-traversal-rc "$?" 4
-
-d=$(mkrepo); printf 'p\n' >"$d/.claude/deploy/PROCEDURE.md"; printf 's\n' >"$d/src.txt"
-( cd "$d" && bash "$H" commit "x" .claude/deploy/PROCEDURE.md src.txt ) >/dev/null 2>&1
-check T4-mixed-refuses-all "$?" 4
-check T4-nothing-committed "$(git -C "$d" rev-list --count HEAD)" 1
-
-d=$(mkrepo); git -C "$d" checkout -q --detach
-printf 'p\n' >"$d/.claude/deploy/PROCEDURE.md"
-( cd "$d" && bash "$H" commit "x" .claude/deploy/PROCEDURE.md ) >/dev/null 2>&1
-check T5-unsafe-rc "$?" 3
-
-d=$(mkrepo)
-( cd "$d" && bash "$H" pending .claude/deploy/PROCEDURE.md ); check T6-pending-clean-rc "$?" 1
-
-d=$(mkrepo); printf 'p\n' >"$d/.claude/deploy/PROCEDURE.md"
-printf 'i\n' >"$d/.claude/deploy/INCIDENTS.md"; printf '{}\n' >"$d/.claude/deploy/STATE.json"
-( cd "$d" && bash "$H" commit "docs(deploy): learn" .claude/deploy/PROCEDURE.md \
-   .claude/deploy/INCIDENTS.md .claude/deploy/STATE.json ) >/dev/null 2>&1
-check T7-atomic-rc "$?" 0
-check T7-three-files "$(git -C "$d" show --name-only --format= HEAD | grep -c deploy)" 3
-
-printf 'PASS=%s FAIL=%s\n' "$pass" "$fail"; [ "$fail" -eq 0 ]
-```
-
-- [ ] **Step 2: Run the test, verify it FAILS**
-
-Run: `bash lib/tests/deploy-commit.test.sh`
-Expected: FAIL (helper absent) — every check fails or the harness errors on missing `lib/deploy-commit.sh`.
-
-- [ ] **Step 3: Implement `lib/deploy-commit.sh`**
-
-```bash
-#!/usr/bin/env bash
-# deploy-commit.sh — surgical commit for the .claude/deploy/ runbook family.
-# Allowlist scope = .claude/deploy/ ONLY (inverse of doc-commit's .claude exclusion).
-set -u
-
-_in_git_repo() { git rev-parse --is-inside-work-tree >/dev/null 2>&1; }
-
-_unsafe_state() {                       # 0 = unsafe
-  local g; g=$(git rev-parse --git-dir 2>/dev/null) || return 0
-  git symbolic-ref -q HEAD >/dev/null 2>&1 || return 0     # detached HEAD
-  [ -e "$g/MERGE_HEAD" ] || [ -d "$g/rebase-merge" ] || \
-    [ -d "$g/rebase-apply" ] || [ -e "$g/CHERRY_PICK_HEAD" ] && return 0
-  return 1
-}
-
-_out_of_scope() {                       # 0 = forbidden, 1 = in scope
-  case "$1" in
-    *..*) return 0 ;;                   # traversal — forbidden FIRST
-    .claude/deploy/*) return 1 ;;       # allowed
-    *) return 0 ;;                      # everything else forbidden
-  esac
-}
-
-_scope_violations() { local p; for p in "$@"; do _out_of_scope "$p" && printf '%s\n' "$p"; done; }
-
-_changed_only() {                       # echo passed files that actually have changes
-  local p; for p in "$@"; do
-    [ -n "$(git status --porcelain -- "$p" 2>/dev/null)" ] && printf '%s\n' "$p"; done
-}
-
-cmd="${1:-}"; shift || true
-_in_git_repo || { echo "deploy-commit: not a git repo" >&2; exit 2; }
-
-case "$cmd" in
-  pending)
-    [ "$#" -gt 0 ] || { echo "deploy-commit: pending needs file args" >&2; exit 2; }
-    [ -n "$(_changed_only "$@")" ] && exit 0 || exit 1 ;;
-  commit)
-    msg="${1:-}"; shift || true
-    [ -n "$msg" ] && [ "$#" -gt 0 ] || { echo "deploy-commit: commit needs <msg> <file>..." >&2; exit 2; }
-    viol=$(_scope_violations "$@")
-    if [ -n "$viol" ]; then
-      { echo "deploy-commit: REFUSED — path(s) outside .claude/deploy/ allowlist:";
-        printf '  - %s\n' $viol;
-        echo "deploy-commit: NOTHING committed. Caller must pass only .claude/deploy/ files."; } >&2
-      exit 4
-    fi
-    _unsafe_state && { echo "deploy-commit: unsafe git state (detached/merge/rebase) — not committing" >&2; exit 3; }
-    mapfile -t changed < <(_changed_only "$@")
-    [ "${#changed[@]}" -gt 0 ] || exit 1
-    git commit -q -m "$msg" -- "${changed[@]}" || { echo "deploy-commit: git commit failed" >&2; exit 1; }
-    git rev-parse --short HEAD ;;
-  *) echo "usage: deploy-commit.sh pending <file>... | commit \"<msg>\" <file>..." >&2; exit 2 ;;
-esac
-```
-
-- [ ] **Step 4: Run the test, verify it PASSES**
-
-Run: `bash lib/tests/deploy-commit.test.sh`
-Expected: `PASS=12 FAIL=0` (exit 0).
-
-- [ ] **Step 5: shellcheck**
-
-Run: `shellcheck lib/deploy-commit.sh lib/tests/deploy-commit.test.sh`
-Expected: clean (matches repo Health Stack norm).
-
-- [ ] **Step 6: Commit**
-
-```bash
-git add lib/deploy-commit.sh lib/tests/deploy-commit.test.sh
-git commit -m "feat(deploy): deploy-commit.sh — allowlist surgical commit for .claude/deploy/"
-```
-
----
-
-### Task 2: Artifacts + bridge formats (§10 materialized)
-
-**Files:**
-- Create: `templates/deploy/PROCEDURE.md`, `templates/deploy/INCIDENTS.md`
-- Modify: `.gitignore`
-
-**Interfaces:**
-- Produces: the on-disk shapes the skill reads/writes — `PROCEDURE.md` annotation grammar, `INCIDENTS.md` `DEP-NNN` template, `STATE.json` and `PENDING.json` schemas.
-- Consumes: nothing.
-
-- [ ] **Step 1: Write `templates/deploy/PROCEDURE.md`** (annotated starter — fixed steps verbatim, dynamic steps annotated)
-
-```bash
-#!/usr/bin/env bash
-# === deploy runbook (reference) — NOT run directly. Instantiated to NEXT.sh per delta. ===
-# Fixed steps run every deploy; `# @delta:` steps re-instantiate from the delta.
-# @config push_deploy_tags=false
-# NOTE grammar: glob=<pat>:each repeats the command per matching file (e.g. psql -f <each>);
-#               glob=<pat>:list runs once + lists matching files as VERIFY items; when=<pat,...> is conditional.
-
-# 1) backup BEFORE any forward-only migration
-ssh "$DEPLOY_HOST" 'pg_dump "$DB" > ~/backups/pre-deploy-$(date +%F-%H%M).sql'   # VERIFY: dump size > 0
-
-# @delta:migrations glob=supabase/migrations/*.sql:list
-# 2) apply NEW migrations (one command; skill lists the delta migrations to VERIFY)
-ssh "$DEPLOY_HOST" 'supabase migration up'                                       # VERIFY: "Applied" for each
-
-# @delta:rebuild when=docker-compose*.yml,Dockerfile,Dockerfile.*
-# 3) rebuild + restart services (only if build inputs changed)
-ssh "$DEPLOY_HOST" 'docker compose up -d --build'                                # VERIFY: docker compose ps healthy
-
-# @delta:deps when=package.json,*lock*,requirements.txt,pyproject.toml
-# 4) install deps (only if manifests changed)
-ssh "$DEPLOY_HOST" 'cd app && npm ci'                                            # VERIFY: exit 0
-
-# 5) reload cache + smoke test (fixed)
-ssh "$DEPLOY_HOST" 'systemctl reload app'
-curl -fsS https://$DEPLOY_HOST/health                                            # VERIFY: HTTP 200
-```
-
-- [ ] **Step 2: Write `templates/deploy/INCIDENTS.md`** (ledger header)
-
-```markdown
-# Deploy incidents (append-only) — DEP-NNN
-
-<!-- One entry per incident. Next ID = grep '^## DEP-' | max+1. Mirrors blockers.md. -->
-<!-- Resolution = the commit that adds this entry (atomic patch+incident). Recover: git log -S 'DEP-NNN' -- .claude/deploy/INCIDENTS.md -->
-<!-- ## DEP-NNN — <step> failed
-     - date: YYYY-MM-DD
-     - step: <runbook step + label>
-     - error: `<verbatim error>`
-     - cause: <root cause>
-     - fix: <what changed in PROCEDURE.md> -->
-```
-
-- [ ] **Step 3: Record the JSON schemas** (no parsing in shell — Claude reads them in skill steps)
-
-`STATE.json` (committed oracle, overwritten on success):
-```json
-{ "deployed_sha": "<sha>", "deployed_at": "<ISO-8601>", "outcome": "ok",
-  "tag": "deploy/<YYYY-MM-DD>" }
-```
-`PENDING.json` (gitignored bridge, deleted on success): schema as in "Decisions resolved at plan time / §10".
-
-- [ ] **Step 4: Update `.gitignore`**
-
-```gitignore
-# deploy: transient per-deploy state (the runbook/ledger/oracle ARE committed)
-.claude/deploy/NEXT.sh
-.claude/deploy/PENDING.json
-```
-
-- [ ] **Step 5: Verify templates are well-formed**
-
-Run: `bash -n templates/deploy/PROCEDURE.md && grep -c '^# @delta:' templates/deploy/PROCEDURE.md`
-Expected: no syntax error; `3` annotations.
-
-- [ ] **Step 6: Commit**
-
-```bash
-git add templates/deploy/PROCEDURE.md templates/deploy/INCIDENTS.md .gitignore
-git commit -m "feat(deploy): runbook/ledger templates + bridge schemas + gitignore transient state"
-```
-
----
-
-### Task 3: `skills/deploy/SKILL.md` — the two-moment skill (REQUIRES writing-skills)
-
-> **At this task, invoke `superpowers:writing-skills`** to shape SKILL.md to house conventions AND to formalize the **cross-session cold-resume** form (deploy's defining novelty; `audit-delta` is the state-file precedent, `client-handover` only an in-context pause). The step behaviors below are the contract; writing-skills governs structure/frontmatter/spine.
-
-**Files:**
-- Create: `skills/deploy/SKILL.md`
-
-**Interfaces:**
-- Consumes: `lib/deploy-commit.sh` (Task 1); artifact shapes (Task 2).
-- Produces: the runtime behavior. STEP spine below.
-
-**STEP spine (each = a SKILL.md section; [GATE] = mandatory stop):**
-
-- [ ] **STEP 0 — PRE-FLIGHT + RESUME BRANCH.** Read `.claude/deploy/PENDING.json` FIRST (state file = only memory between runs).
-  - `PENDING.json` present → **RESUME**: jump to STEP 3 with its `{base, target, delta, step_reached}` (do not recompute).
-  - else `PROCEDURE.md` absent → **BOOTSTRAP** (Task 4).
-  - else → FRESH: continue STEP 1.
-- [ ] **STEP 1 — DELTA.** `base = STATE.json.deployed_sha` (or, if `STATE.json` absent, first-deploy = full runbook). `git diff --name-only <base> HEAD` → delta file list. `target = git rev-parse HEAD`.
-- [ ] **STEP 2 — INSTANTIATE + [GATE].** Expand `PROCEDURE.md`: emit fixed steps verbatim; expand `@delta:glob=…:each` steps by repeating the command per matching delta file, and `@delta:glob=…:list` steps once with matching files as `# VERIFY:` items; include `@delta:when=` steps only if the delta intersects. Read `INCIDENTS.md` and prepend matching `# PRE-WARN: DEP-NNN …` notes. Write `NEXT.sh`. **[GATE]** present `NEXT.sh` → `all / edit / skip-all`. On approve: write `PENDING.json` (`step_reached: awaiting-user`), then **hand back** (AskUserQuestion: "Run NEXT.sh step by step. Report back: Deployed OK / Failed at step X / Not yet").
-- [ ] **STEP 3 — RESUME / REACT** (entry point on the user's report; may be a fresh session).
-  - "Deployed OK" → STEP 5.
-  - "Failed at step X: <err>" → STEP 4.
-  - "Not yet" → re-state pending, stop.
-- [ ] **STEP 4 — LEARN + [GATE] + ATOMIC COMMIT.** Diagnose. Draft: (a) in-place `PROCEDURE.md` patch to step X; (b) `INCIDENTS.md` append `DEP-NNN` (error verbatim). **[GATE]** `all / pick / edit / skip-all` (significant edit). On approve: write both, then **one atomic** `bash lib/deploy-commit.sh commit "docs(deploy): patch <step> — recovered from <err>" .claude/deploy/PROCEDURE.md .claude/deploy/INCIDENTS.md`. The commit that adds `DEP-NNN` IS its resolution (derive via git later). Then bump `PENDING.json.runbook_rev` to the new `PROCEDURE.md` commit sha (keep `step_reached` at X). **Resume = REGENERATE `NEXT.sh` from `step_reached` against the PATCHED runbook** (steps X…end — X+1…end never ran), NOT replay a single step. The bumped `runbook_rev` is exactly the trigger: runbook changed ⇒ prior `NEXT.sh` is stale ⇒ regenerate. Re-present via STEP 2's hand-back.
-- [ ] **STEP 5 — MARK (success).** Write `STATE.json` (`deployed_sha = PENDING.target_sha`, outcome ok, tag). `git tag -a deploy/<date> <target> -m "<summary>"`; **if `@config push_deploy_tags=true`** then `git push origin deploy/<date>` (best-effort, non-fatal). `bash lib/deploy-commit.sh commit "chore(deploy): mark <date> @ <short>" .claude/deploy/STATE.json`. **Delete `PENDING.json`** (+ `NEXT.sh`). Report.
-
-- [ ] **Verification scenarios** (dry-run walkthroughs, no prod):
-  - First deploy (no `STATE.json`): full runbook fires; STATE laid; PENDING deleted.
-  - Delta deploy: only changed-bucket steps instantiate; `git diff` form is `<base> HEAD`.
-  - **Cold resume**: write a `PENDING.json` by hand, start `deploy` in a *fresh* context → STEP 0 detects it, resumes at STEP 3 from disk alone (no conversation memory).
-  - Failure→learn: report "failed at step X" → patch + DEP append committed atomically (one sha, both files).
-- [ ] **Commit:** `git add skills/deploy/SKILL.md && git commit -m "feat(deploy): two-moment cross-session skill (resumes cold from PENDING.json)"`
-
----
-
-### Task 4: Bootstrap (project without a runbook)
-
-**Files:**
-- Modify: `skills/deploy/SKILL.md` (STEP 0 BOOTSTRAP branch)
-
-**Interfaces:**
-- Consumes: `templates/deploy/*` (Task 2); STEP spine (Task 3).
-
-- [ ] **Step 1 — BOOTSTRAP branch + [GATE].** When `PROCEDURE.md` absent, offer two paths (AskUserQuestion):
-  - **Paste** — user provides an existing runbook → adopt verbatim, then propose `@delta:` annotations for migration/build/deps steps.
-  - **Scaffold** — detect artifacts (`supabase/migrations/`, `docker-compose*.yml`/`Dockerfile`, `package.json`/lockfiles, `.env*`) + short interview (ssh host, backup cmd, health URL, rollback note) → fill `templates/deploy/PROCEDURE.md`.
-  - **[GATE]** present drafted `PROCEDURE.md` → `all / edit / skip-all`. On approve: write `PROCEDURE.md` + empty `INCIDENTS.md`; `bash lib/deploy-commit.sh commit "feat(deploy): bootstrap runbook" .claude/deploy/PROCEDURE.md .claude/deploy/INCIDENTS.md`. First deploy then proceeds (no STATE.json ⇒ full runbook).
-- [ ] **Step 2 — Verify:** dry-run on a repo with `supabase/migrations/` + `docker-compose.yml` present → scaffold proposes migration + rebuild steps annotated; on a bare repo → interview-only path.
-- [ ] **Commit:** `git add skills/deploy/SKILL.md && git commit -m "feat(deploy): bootstrap — paste-or-scaffold initial runbook"`
-
----
-
-## Gates identified
-
-- **[GATE] STEP 2** — approve instantiated `NEXT.sh` before hand-back.
-- **[GATE] STEP 4** — approve runbook patch + `DEP-NNN` incident before the atomic learning commit.
-- **[GATE] STEP 0/Task 4** — approve scaffolded `PROCEDURE.md` before first write.
-- **Hand-back (STEP 2→3)** — AskUserQuestion is the resume point; the user executes out-of-band.
-- **Task gates** — each Task ends test-green + shellcheck-clean + committed before the next (deps: 1 → 2 → 3 → 4).
-
-## Self-review
-
-- **Spec coverage:** 4 artifacts + bridge (§3/§10) → Task 2; STATE-oracle + `<base> HEAD` delta (§4) → Task 1 constraints + STEP 1; runbook+INCIDENTS learning, atomic couple (§5) → STEP 4; `deploy-commit.sh` inverse allowlist (§6) → Task 1; bootstrap (§7) → Task 4; two-moment cold resume (§10) → STEP 0/2/3 + PENDING.json. All §8 items resolved above. ✓
-- **Placeholder scan:** none — helper code, test code, schemas, annotation grammar all concrete.
-- **Type consistency:** `STATE.json.deployed_sha` (STEP 1 base, STEP 5 write), `PENDING.json.{base_sha,target_sha,delta,step_reached}` (STEP 0 read, STEP 2 write, STEP 4 update), `deploy-commit.sh commit "<msg>" <file>...` (Tasks 1/3/4) — names align.
-- **Open at execution (not assumed):** the `writing-skills` consultation in Task 3 may rename/restructure SKILL.md sections to match the formalized cold-resume convention, and finalizes the `@delta:` `:each`/`:list` keyword spelling (both semantics mandatory); STEP behaviors and the §6 helper contract above are fixed regardless.
-
-## Execution Handoff
-
-Build order is strict by dependency: **Task 1 (helper, foundation) → Task 2 (formats) → Task 3 (skill, writing-skills) → Task 4 (bootstrap)**.

docs/specs/2026-06-27-deploy-skill-design.md

@@ -1,165 +0,0 @@
-# Deploy skill — design spec
-
-> **Superseded by BDR-054** (`52f6678`): the shipped skill has NO `NEXT.sh` file and NO
-> AskUserQuestion hand-back — see `skills/deploy/SKILL.md` for current behavior. This
-> spec is kept as historical record; do not implement its NEXT.sh/hand-back sections.
-
-- **Date:** 2026-06-27
-- **Status:** Design approved (5 knobs settled). **No skill code written yet.** Next step = implementation plan.
-- **Scope:** A new `deploy` skill = a per-project shell RUNBOOK that lives in `.claude/deploy/`, gets re-instantiated from the delta since the last deploy, and LEARNS from deploy errors in place.
-
-## 1. Vision — deployment memory that learns
-
-Three moments:
-
-1. **BEFORE** — produce the *instantiated* runbook: reference runbook + delta since last deploy, parameterized steps rewritten with the real artifacts (e.g. the migration step lists the migrations actually added since last deploy, not the runbook's examples).
-2. **DURING** — the **user executes out-of-band** (prod ssh — Claude must not run it) and reports `deployed and tested` OR `failed at step X, here is the error` → fix together until success.
-3. **AFTER** — on confirmed success: (a) if errors were hit + fixed, update the reference runbook so the next deploy does not repeat them; (b) lay the marker "deployed up to here" for the next diff.
-
-Structural ancestor in the corpus: `client-handover` (BEFORE baseline → DURING user-deploy gate via `AskUserQuestion` → AFTER validate + react). No existing skill owns a learning per-project runbook — clean gap, no `.claude/deploy/` precedent.
-
-## 2. Locked decisions
-
-| # | Knob | Decision |
-|---|------|----------|
-| 1 | Marker / oracle | **STATE file is the oracle** (deployed SHA), **annotated tag** added as a human bookmark only |
-| 2 | Learning storage | **In-place runbook edits + append-only `INCIDENTS.md`** (distinct jobs, atomic coupling) |
-| 3 | Parameterization | **`# @delta:` annotations** bind dynamic steps to path-patterns; un-annotated steps are fixed |
-| 4 | Bootstrap | **Offer both** — user pastes an existing runbook OR skill scaffolds via artifact detection + interview |
-| 5 | Execution model | **`NEXT.sh` is a step-by-step CHECKLIST** — runnable shell, but driven by hand with manual `# VERIFY:` gates; never `bash NEXT.sh` unattended |
-
-**Why #5 is design-time, not impl:** the execution model is load-bearing for moments 2 and 3. Moment 2 is defined as "user reports *failed at step X*", and moment 3's LEARN loop must know *which* step failed to patch it. A single `bash NEXT.sh` blob collapses both into "exited non-zero somewhere" and can strand a prod deploy (migrations, restarts) in partial state with no step control. Checklist is *entailed* by the three-moment structure, not merely safer.
-
-Treated as settled corollaries: user executes out-of-band; a **new** `lib/deploy-commit.sh` helper (existing helpers cannot commit the runbook — see §6, verified).
-
-## 3. Architecture
-
-```
-.claude/deploy/
-  PROCEDURE.md   reference runbook — fixed shell + `# @delta:` annotated steps   (edited IN-PLACE)
-  INCIDENTS.md   DEP-NNN incident ledger: date, step, error verbatim, root cause,
-                 fix (APPEND-ONLY; resolution = introducing commit, derive via git)
-  STATE.json     deployed SHA + timestamp + outcome — the diff oracle             (overwritten each deploy)
-  NEXT.sh        instantiated runbook — EPHEMERAL, not committed ; run STEP-BY-STEP
-                 (checklist, manual # VERIFY: gates) — never `bash NEXT.sh` unattended
-
-lib/deploy-commit.sh   surgical commit, allowlist = .claude/deploy/ , rc3 unsafe-git guard, short-hash stdout
-
-Skill STEP spine (PRE-FLIGHT -> PROPOSE+GATE -> WRITE+COMMIT, house style):
-  0 PRE-FLIGHT  runbook present?  absent -> bootstrap (paste | scaffold+interview)
-  1 DELTA       STATE absent -> first deploy = full runbook ; else diff <STATE_SHA> HEAD
-  2 INSTANTIATE expand @delta steps + read INCIDENTS pre-warns -> NEXT.sh -> GATE
-  3 (user executes out-of-band; reports "done" | "failed at step X: <err>")
-  4 LEARN       on failure: patch PROCEDURE step + append DEP-NNN -> GATE -> deploy-commit (ATOMIC)
-  5 MARK        on success: write STATE@sha ; annotate + push tag ; optional doc
-```
-
-## 4. Delta mechanism — verified (git 2.53.0)
-
-All three facts re-run live before writing this spec; observed output recorded, not assumed.
-
-**First-deploy detection = STATE-absent, deterministic. `describe` is off the detection path.**
-```
-[ -f .claude/deploy/STATE.json ]            => exit 1 (absent = first deploy)  <- THE detector
-git describe --tags --match 'deploy/*' => fatal: No names found ; exit 128 <- only the reason NOT to use describe
-[ -f .claude/deploy/STATE.json ]            => exit 0 (present = delta path)
-```
-
-**Delta = `git diff --name-only <STATE_SHA> HEAD`** (two explicit endpoints; no dots, so it cannot be misread as three-dot).
-```
-LINEAR   git diff --name-only <sha> HEAD   => 0033_new.sql, svc.yml   (== two-dot == three-dot; merge-base == STATE)
-DIVERGED two-dot   sideA sideB             => fileA.txt, fileB.txt     (both endpoints = true tree delta)
-DIVERGED three-dot sideA...sideB           => fileB.txt                (merge-base — UNDERCOUNTS)
-```
-Two-dot/explicit-endpoints is the literal tree difference between the deployed tree and HEAD = what deploy needs. It is also rebase-robust: an orphaned marker still yields the correct tree diff, whereas `git rev-list A..B` (ancestry) reports phantom deltas after history rewrite (LRN-054's trap; verified in an earlier run). **Never use `rev-list` ancestry for the artifact list.**
-
-**delta -> steps:** `# @delta:<kind>` annotations bind a dynamic step to the path-pattern that feeds it; the diff buckets straight into steps:
-```
-# @delta:migrations glob=supabase/migrations/*.sql
-# @delta:rebuild   when=docker-compose*.yml,Dockerfile
-# @delta:deps      when=package.json,*lock*
-```
-
-## 5. Learning model — runbook + INCIDENTS, non-redundant
-
-| Artifact | Job | Lifecycle |
-|---|---|---|
-| `PROCEDURE.md` | The corrected procedure you run. A fix is baked into the step so the next run cannot repeat it. | in-place |
-| `INCIDENTS.md` | The incident ledger; **read at BEFORE-time to pre-warn** ("0033 hit a lock timeout last deploy; runbook already carries `--timeout`, watch for it"). | append-only |
-
-The pre-warn read is the function `git log` serves badly — that is why the ledger is not duplication. This mirrors the memory system's own split (append-only `journal.md`/`blockers.md` alongside in-place TODO/code).
-
-**Coupling invariant:** one incident → **one in-place `PROCEDURE.md` patch + one `INCIDENTS.md` append, committed atomically in a single `deploy-commit.sh` call.** Never one without the other (mirrors BDR-034/036 "couple the commit to the integration step"). Significant patch (changes a prod path) → surface + approve before writing.
-
-## 6. `lib/deploy-commit.sh` — new helper, inverse `.claude/` rule (verified)
-
-Neither existing helper can commit the runbook — confirmed live:
-```
-REAL doc-commit.sh  .claude/deploy/PROCEDURE.md => rc 4 "REFUSED — out-of-scope ... BDR-022 ... NOTHING committed"
-REAL memory-commit.sh pending (deploy changed)  => rc 1 (ignores it; allowlist = .claude/memory|tasks only)
-```
-`doc-commit.sh` is built to keep `.claude/**` *out* of public-doc commits; `.claude/deploy/` is under `.claude/`, so reuse is not just blocked, it is semantically wrong. `deploy-commit.sh` needs the **inverse** rule: a TARGET allowlist for `.claude/deploy/*`, modeled on `memory-commit.sh` (rc 3 unsafe-git guard, short-hash on stdout, `chore(deploy):`/`docs(deploy):` messages).
-
-Allowlist guard — traversal reject ordered FIRST. Prototype matrix verified live:
-```sh
-_in_deploy_scope() {
-  case "$1" in
-    *..*) return 1 ;;                 # reject path traversal FIRST
-    .claude/deploy/*) return 0 ;;     # ALLOW the deploy family only
-    *) return 1 ;;                    # reject everything else
-  esac
-}
-```
-```
-ALLOW  .claude/deploy/{PROCEDURE.md,INCIDENTS.md,STATE}
-REJECT .claude/memory/*  .claude/tasks/*  .claude/secret  CLAUDE.md  src/*
-REJECT .claude/deploy            (bare dir, no slash)
-REJECT .claude/deploy-other/x    (trailing-slash requirement closes prefix confusion)
-REJECT .claude/deploy/../memory/secret   (traversal closed by *..* matched first)
-```
-
-## 7. Bootstrap
-
-`STEP 0 PRE-FLIGHT`: `PROCEDURE.md` present? Absent → bootstrap, two offered paths:
-1. **Paste** — user supplies an existing runbook (the game example); skill adopts + annotates it.
-2. **Scaffold** — skill detects deploy artifacts (migrations dir, compose/Dockerfile, package scripts, `.env`) + a short interview (ssh target, backup cmd, rollback note) → writes an annotated `PROCEDURE.md`.
-
-First deploy has no marker → STATE-absent ⇒ full runbook fires; then lay STATE at the deployed SHA. The first deploy *is* the creation of the runbook + the first marker.
-
-## 8. Open items (for the implementation plan)
-
-> `NEXT.sh` execution model resolved → decision #5 (checklist), promoted to design-time.
-
-- Tag push: tags don't push by default → AFTER step should `git push --tag deploy/<date>` or remind.
-- `INCIDENTS.md` ID/format detail (mirror `blockers.md` `DEP-NNN`); confirm name vs `ERRORS-LEARNED.md`.
-- `@delta:` annotation grammar (glob= vs when=) — finalize the small DSL.
-- Frontmatter `allowed-tools` set; STEP gate wording reuse from `capitalize`/`client-handover`.
-
-## 9. Build sequencing & a structural flag
-
-**Two distinct disciplines, in order — do not conflate:**
-1. `writing-plans` — global task ordering (helper → skill → bootstrap), dependencies, gates. The build plan.
-2. → execution →
-3. At the *skill* task ONLY: `writing-skills` — the discipline for the SKILL.md itself (structure, frontmatter, spine, config conventions). Used WHEN we reach the skill task, **not before** (it does not fire at plan time).
-
-**Structural flag for `writing-skills` to resolve — do NOT assume the linear-spine convention suffices:**
-deploy's spine is unusual — **two parts split by out-of-band execution**: STEP 0–2 before → *user deploys by hand* → STEP 4–5 after, on the `done`/`failed` report. A skill that **hands back control mid-run and resumes**.
-
-Preliminary recon (confirm at the skill task — NOT verified now):
-- The 6 completion flux (close, ship-feature, feat, bugfix, hotfix, commit-change) appear linear one-shot — synchronous gates at most, no out-of-band hand-back.
-- The relevant precedent is OUTSIDE those 6: `client-handover` already hands back — a synchronous "Deploy done?" `AskUserQuestion` pause (STEP 5) — but it holds state in *conversation context*, not on disk.
-- deploy's genuinely-new bit *may* be **disk-bridged resume** (`NEXT.sh` + `STATE` on disk as the bridge) — but **whether `NEXT.sh` alone suffices to resume cross-session is an OPEN design question, not a settled answer** (see §10). An earlier draft of this spec framed it as resolved; it is not. `writing-skills` must establish the convention (how to mark "I wait for your return here", detect + resume a pending deploy, hold state across the gap) — confirm there, do not assume the linear mould suffices.
-
-## 10. Open design question (DESIGN-TIME, unresolved) — state across the two moments
-
-deploy is a **two-moment skill**: moments 0–2 (BEFORE) → user deploys out-of-band → moment 3 (AFTER) on the `done`/`failed` report. **The report may arrive in a different session.** So the design must answer how state crosses the gap and what moment 3 must know to resume correctly.
-
-> **`skill deux-temps, état entre temps = [à concevoir : NEXT.sh seul suffit-il pour reprendre cross-session ?]`**
-
-Sub-questions (to settle when we resume — NOT now, NOT assumed):
-- **What must the bridge record?** Moment 3 must (a) lay the correct marker = `STATE ← target sha`, and (b) capitalize the correct incident (which step, which delta). HEAD may have moved since NEXT.sh was generated → "current HEAD" is unsafe. The bridge must persist at least **{base STATE sha, target sha, delta manifest}** — inside NEXT.sh (header block) or a sidecar (`.claude/deploy/PENDING`)? Undecided.
-- **Resume detection (re-entrancy):** STEP 0 PRE-FLIGHT must detect "a deploy is pending, awaiting your report" — likely *pending-bridge present + STATE not advanced to target* — and branch RESUME (ask done/failed) vs FRESH. Is moment 3 a new `deploy` call that re-detects from disk, or a `deploy --report`? Undecided.
-- **Ephemeral vs persistent tension — LINKED to sub-question 1 (not independent).** §3 calls NEXT.sh "EPHEMERAL, not committed", yet a cross-session bridge MUST survive on disk. So: **if the bridge must persist, NEXT.sh-as-bridge is impossible while NEXT.sh stays ephemeral.** Likely *binary* resolution at plan time — either (a) NEXT.sh becomes persistent (contradicts §3), or (b) the bridge is a **separate** "deploy-in-progress" artifact `{base/target/delta}` distinct from NEXT.sh. Settle with `writing-skills`. (Uncommitted local state is fine; note the single-machine assumption — an uncommitted bridge won't follow a clone.)
-- **Form-novelty — deploy's DEFINING characteristic: cross-session COLD resume.** `client-handover` is a *near* precedent, not exact: it hands back **in-context** (same conversation, state held in memory). deploy must resume with the **context lost** — so the **disk alone must carry everything to resume cold**. No existing skill resumes without context; that is what sets deploy apart, and it makes sub-question 1 **load-bearing** (disk must suffice for a cold restart). deploy likely introduces a NEW skill form → `writing-skills` establishes the convention. Confirm there.
-
-**Next step:** `writing-plans` to turn this spec into an implementation plan (helper first, then skill); at the skill task, `writing-skills` to shape it to convention and **resolve the §10 two-moment state question** — which is design-time, deferred only because we are stopped here, not because it is impl detail.

docs/superpowers/specs/2026-07-15-model-routing-design.md

@@ -1,143 +0,0 @@
-# Model routing — reflection inline (big model) / execution pinned (Sonnet) — design
-
-**Date**: 2026-07-15 · **Status**: approved (user, 2026-07-15) · **Branch**: `feature/model-routing`
-**Lifecycle**: transient planning artifact (BDR-065) — committed during the run, deleted post-merge.
-
-## Principle
-
-The session model is assumed to be a big reasoning model (Fable 5, or Opus when
-Fable is unavailable). Everything that **thinks** — brainstorming, planning,
-technical decisions, audits, loop decisions — runs INLINE in the main
-conversation, or in subagents that inherit the session model. Everything that
-**executes** a ready-made plan — writing code, applying fix bundles, commits,
-deliverable rendering — runs on Sonnet-pinned subagents. A blocking gate
-enforces the "session = big model" assumption at the entry of every reflection
-orchestrator.
-
-User verdicts baked in (2026-07-14/15):
-- Scope = hybrid: ship-feature/init-project execution → sonnet; `/feat`
-  re-architected (plan inline → dispatch executor); bugfix/hotfix stay fully
-  inline (BDR-050 conserved for them).
-- Gate = BLOCKING, not advisory.
-- Audit agents inherit the session model (no opus pin); the gate extends to
-  audit orchestrators.
-- verifier + security-auditor KEEP `model: sonnet` (job9 decision confirmed).
-- client-handover-writer → sonnet (requires converting its inline-load to a
-  true dispatch; human gates relocate to the main loop).
-
-## 1. Blocking model gate
-
-New `lib/model-check.sh`: resolves the current session model from
-`settings.json` (physical path resolution — LRN-023 class), normalizes
-(`claude-fable-5[1m]` → fable, `claude-opus-*` → opus, sonnet, haiku), prints
-`big|small|unknown`. Exit 0 = big, 2 = small, 3 = unknown.
-
-New `lib/model-gate.md` snippet (same include pattern as `lib/design-gate.md`):
-run the check; `small` → STOP the skill: "session model is <X> — reflection
-requires Fable/Opus. Switch with /model, then relaunch." `unknown` →
-fail-visible: show the raw value, ask the user to confirm or abort (BDR-025
-doctrine — unknown never silently passes).
-
-Wired as a STEP 0 line in the reflection orchestrators:
-`ship-feature, init-project, feat, bugfix, onboard, seo, geo, web-validate,
-harden, audit-delta, tour, code-clean`.
-NOT wired in: `hotfix` (trivial by definition), `commit-change`, `doc`,
-`status`, `release-candidate`.
-
-Caveats to prove at implementation time:
-- `/model` mid-session rewrites settings.json (LRN-098 observed it once —
-  re-prove with a live flip-test before trusting the source).
-- The helper itself must be flip-tested (LRN-096: an unproven guard is a
-  vacuous guard).
-
-## 2. Frontmatter pins (`agents/*.md`)
-
-| Agent | Before | After | Rationale |
-|---|---|---|---|
-| feater | (inherit) | **sonnet** | executor as subagent: seo/geo L1 applier + new /feat dispatch |
-| hotfixer | (inherit) | **sonnet** | L1 applier (seo/geo/web-validate); /hotfix inline unaffected (pin inert on inline load) |
-| client-handover-writer | opus | **sonnet** | deliverable executor; pin becomes EFFECTIVE only with §5 dispatch conversion (today's opus pin is inert — the agent is inline-loaded) |
-| analyzer | haiku | **(none — inherit)** | analysis feeds the plan = reflection; runs big via the session model |
-| verifier | sonnet | keep | F1 confirmed (job9) |
-| security-auditor | sonnet | keep | F1 confirmed (job9) |
-| seo-analyzer, geo-analyzer, validator-analyzer | (inherit) | keep (inherit) | audit = reflection = session model; covered by the gate |
-| code-cleaner | (inherit) | keep (inherit) | audit phase = reflection; fixes hand off to refactorer (sonnet) via CODE-CLEAN-SCOPE.md (job9 H1) |
-| doc-syncer, onboarder, scaffolder, refactorer, interviewer, plugin-advisor | sonnet | keep | workers/executors |
-| status-reporter | haiku | keep | mechanical collector |
-| bugfixer, commit-changer | (inherit) | keep | inline-only playbooks — a pin would be inert |
-
-## 3. `/feat` re-architecture (partial supersede of BDR-050 — feat only)
-
-`skills/feat/SKILL.md` absorbs the reflection: analyze-before-plan, design
-gate, MINI-PLAN, contract (`lib/contract-interview.md`) — all inline. Then
-dispatches `Agent(subagent_type="feater")` (sonnet via pin) with: the
-contract, the plan, the branch name, repo conventions.
-
-`agents/feater.md` is rewritten as a pure executor: implement the plan to the
-letter, run project checks, commit (no attribution trailers), return a
-structured summary. No user interaction inside feater (subagents cannot ask) —
-every decision must be closed pre-dispatch.
-
-The verify-secure loop moves out of feater.md into the /feat main loop
-(LRN-083 invariant: loop decisions live in the main loop): fresh verifier →
-ECARTS → re-dispatch feater with the verdict deltas, bounded 3×; then the
-security gate. Escalation paths unchanged.
-
-## 4. SDD execution pinned (ship-feature STEP 4, init-project STEP 8)
-
-One instruction line in each SKILL.md: every implementation subagent
-dispatched under `superpowers:subagent-driven-development` MUST carry
-`model: "sonnet"` in the Agent call. No fork of the superpowers skill — the
-main loop emits the Agent calls and controls the params.
-
-## 5. client-handover conversion (inline-load → true dispatch)
-
-`skills/client-handover/SKILL.md`: collect params inline (URL, logo, options),
-then `Agent(subagent_type="client-handover-writer")` — the sonnet pin becomes
-effective. Human gates (per-axis threshold escalation, overrides) RELOCATE to
-the main loop: the writer returns a structured `GATE NEEDED` status instead of
-asking; the dispatcher asks the user and re-dispatches (or continues via
-SendMessage) with the decision. `AskUserQuestion` is removed from the writer's
-tools.
-
-OPEN VERIFY POINT: the writer's own nested dispatches (seo/harden re-runs as
-general-purpose subagents) — verify at implementation what nested children
-inherit (session model vs parent model). If they inherit the sonnet parent,
-the re-run audits violate the principle → force the model explicitly in those
-nested dispatches or lift them to the main loop.
-
-## 6. web-validate fixes → L1 applier
-
-STEP 3 stops applying fixes via inline Edit; dispatches `hotfixer` (sonnet)
-with the fix bundle — same pattern as seo/geo (BDR-061 alignment).
-
-## 7. Memory / doc / tests
-
-- New BDR: model-routing principle (reflection inline big / executors sonnet /
-  blocking gate); partial supersede of BDR-050 (feat only); records F1
-  (verifier/security stay sonnet) and the analyzer haiku→inherit change.
-- README: agent-model table refresh. CHANGELOG Unreleased entry.
-- Tests: flip-tests for `model-check.sh` (fable[1m] / opus / sonnet / garbage
-  fixtures); gate STOP proven on a small-model fixture (LRN-096); /feat smoke
-  on a throwaway repo (LRN-079): plan inline → dispatch carries sonnet →
-  verify loop decided in main loop; grep census: no executor dispatch without
-  an effective pin.
-
-## Out of scope / accepted deviations
-
-- `/doc` and `/commit-change` stay inline on the session model (judgment and
-  execution interleaved; converting them buys little). Revisit under quota
-  pressure.
-- bugfix/hotfix fully inline (BDR-050 conserved).
-- No per-agent "fable-else-opus" fallback exists in the harness — the session
-  model IS the fallback mechanism; the gate is its backstop.
-
-## Risks
-
-- Model strings in settings.json may change shape with CC updates →
-  model-check must return `unknown` (fail-visible), never guess.
-- feater as a subagent loses main-conversation context → the plan becomes the
-  contract; weak plans cost verify-loop iterations. Mitigation:
-  contract-interview stays mandatory in /feat.
-- Nested model inheritance under client-handover-writer unknown → §5 verify
-  point.

hooks/config-protection.sh

@@ -1,65 +0,0 @@
-#!/usr/bin/env bash
-# config-protection.sh
-#
-# PreToolUse hook (Edit|Write|MultiEdit). Blocks edits to this config's
-# quality-gate files — the guardrails an agent must not silently weaken to make
-# an error "pass" (permission/hook registry, gitflow enforcement, the git
-# pre-commit guard, the hooks themselves, the test suite, the health diagnostic,
-# lint config). Exit 2 blocks the tool call and feeds the message back to the
-# model (Claude Code PreToolUse contract).
-#
-# It fires only on the model's Edit/Write tool calls — never on shell-level file
-# ops (the cp/ln in install.sh, link.sh), so bootstrap/deploy is unaffected.
-#
-# One-shot escape hatch: create .claude/.config-edit-ok (CWD-relative) with a
-# NON-EMPTY reason inside; the hook logs the reason, consumes (rm) the sentinel,
-# and allows that single edit. It never persists — a lingering sentinel would be
-# a footgun. Discipline, per CLAUDE.global.md "Root causes only. No temp fixes.": fix
-# the code, don't loosen the gate. Fails OPEN (exit 0) on parse failure so it can
-# never wedge editing.
-
-set -euo pipefail
-
-log="${HOME}/.claude/logs/config-protection.log"
-sentinel="${PWD}/.claude/.config-edit-ok"
-
-input="$(cat)"
-path="$(printf '%s' "$input" \
-  | python3 -c 'import sys, json; print(json.load(sys.stdin).get("tool_input", {}).get("file_path", ""))' \
-  2>/dev/null || true)"
-[ -z "$path" ] && exit 0
-
-# Guardrail files, matched by path suffix (covers both the repo source and the
-# deployed ~/.claude copy). Precise: lib/gitflow.sh only, not gitflow-migrate.sh.
-case "$path" in
-  */.claude/settings.json|*/.claude/settings.local.json|*/claude/settings.json) ;;
-  */lib/gitflow.sh|*/.githooks/*|*/doctor.sh) ;;
-  */hooks/*.sh|*/lib/tests/*) ;;
-  */.shellcheckrc|*/.markdownlint.json|*/.editorconfig) ;;
-  *) exit 0 ;;
-esac
-
-# One-shot sentinel bypass: non-empty reason required; consumed on sight.
-if [ -f "$sentinel" ]; then
-  reason="$(head -c 500 "$sentinel" 2>/dev/null | tr '\n\r\t' '   ' || true)"
-  rm -f "$sentinel"
-  if printf '%s' "$reason" | grep -q '[^[:space:]]'; then
-    mkdir -p "$(dirname "$log")"
-    printf '%s\tBYPASS\t%s\treason=%s\n' "$(date -Iseconds)" "$path" "$reason" >> "$log"
-    exit 0
-  fi
-  printf '%s\n' "[config-protection] .claude/.config-edit-ok had an EMPTY reason -> refused (sentinel consumed). Recreate it with a non-empty reason." >&2
-  exit 2
-fi
-
-cat >&2 <<EOF
-[config-protection] BLOCKED edit to a quality-gate file:
-  $path
-This is a guardrail (permission/hook registry, gitflow enforcement, git
-pre-commit guard, a hook, the test suite, health diagnostic, or lint config).
-Don't weaken the gate to make an error pass — fix the root cause instead
-(global CLAUDE.md: "Root causes only. No temp fixes."). To make one intended edit,
-create .claude/.config-edit-ok with a non-empty reason; it is logged and
-consumed (one-shot).
-EOF
-exit 2

hooks/ctx7-reminder.sh

@@ -0,0 +1,63 @@
+#!/usr/bin/env bash
+# ctx7-reminder.sh
+#
+# UserPromptSubmit hook. When the current project uses fast-moving libs
+# (lib/fast-libs.sh) it injects ONE reminder per session to consult ctx7
+# (find-docs skill) before coding against their APIs, pointing at the
+# .ctx7-cache/ state. Closes the ad-hoc-coding gap: find-docs' description
+# fires on doc *questions* and ship-feature/init-project pre-fetch, but
+# nothing covered a plain "add a useEffect here" prompt (BDR-078; second
+# deliberate ctx7 surface, scoped refinement of BDR-053 single-surface).
+#
+# Soft nudge: always exits 0, never blocks. Stable-tech projects (no
+# manifest, or no fast-lib match) stay silent.
+
+set -euo pipefail
+
+input="$(cat)"
+
+field() { # $1=json key — extracted from hook stdin, empty on failure
+  printf '%s' "$input" | python3 -c \
+    "import sys,json; print(json.load(sys.stdin).get('$1',''))" \
+    2>/dev/null || true
+}
+
+prompt="$(field prompt)"
+case "$prompt" in
+  '<task-notification>'*) exit 0 ;; # harness turn, not a user request
+esac
+
+cwd="$(field cwd)"
+[ -n "$cwd" ] || cwd="$PWD"
+
+# Cheap bail-out before any lib work: no manifest → no fast-libs.
+[ -f "$cwd/package.json" ] || [ -f "$cwd/requirements.txt" ] \
+  || [ -f "$cwd/pyproject.toml" ] || exit 0
+
+# One fire per session: the doctrine holds for the whole session,
+# repeating it on every prompt would be token spam.
+session_id="$(field session_id)"
+sentinel="${TMPDIR:-/tmp}/.ctx7-reminder-${session_id:-nosession}"
+[ -e "$sentinel" ] && exit 0
+
+# Resolve the lib next to this hook (repo layout), fall back to the
+# installed copy — both paths exist through the link.sh symlinks.
+script_dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+libsh="${script_dir}/../lib/fast-libs.sh"
+[ -f "$libsh" ] || libsh="${HOME}/.claude/lib/fast-libs.sh"
+[ -f "$libsh" ] || exit 0
+
+libs="$(bash "$libsh" detect "$cwd" 2>/dev/null || true)"
+[ -n "$libs" ] || exit 0
+
+status="$(bash "$libsh" cache-status "$cwd" 2>/dev/null || true)"
+: > "$sentinel" || true
+list="$(printf '%s' "$libs" | tr '\n' ' ' | sed 's/ *$//')"
+
+if [ "$status" = "fresh" ]; then
+  printf '📚 Fast-moving libs in this project (%s) — fresh .ctx7-cache/ present: read the matching cache file before relying on their APIs.\n' "$list"
+else
+  printf '📚 Fast-moving libs in this project (%s) — .ctx7-cache/ %s: consult ctx7 (find-docs skill) before writing code against their APIs. Stable techs need nothing.\n' "$list" "${status:-missing}"
+fi
+
+exit 0

hooks/design-toolchain-reminder.sh

@@ -44,7 +44,11 @@ lc="$(printf '%s' "$prompt" | tr '[:upper:]' '[:lower:]')"
 # "design system", "redesign", "front-?end design". dashboard -> \bdashboard\b
 # so a filename like ecc_dashboard.py no longer matches while "admin dashboard"
 # still does. animation kept (rarely non-UI).
-pattern='redesign|refonte|refont|ui/ux|ux/ui|\bui\b|\bux\b|ui kit|design system|design-system|front-?end design|\bnavbar\b|\bsidebar\b|\bmodal\b|\bbouton\b|\bbutton\b|formulaire|\bhero\b|\bheader\b|\bfooter\b|dropdown|tooltip|\bbadge\b|\bchart\b|graphique|accordion|carousel|\bslider\b|landing|\bdashboard\b|homepage|home page|\baccueil\b|\bécran\b|\becran\b|portfolio|maquette|mockup|wireframe|prototype|\bjoli\b|\bjolie\b|\bbeau\b|\bbelle\b|esth[eé]tique|aesthetic|\bvisuel\b|\bvisual\b|embellir|fignol|peaufin|polish|styliser|styling|stylesheet|\bskin\b|charte graphique|\bbrand\b|branding|\blogo\b|favicon|ic[oô]ne|\bicon\b|\bcss\b|tailwind|shadcn|couleur|gradient|d[eé]grad[eé]|\bombre\b|spacing|espacement|\bmarge\b|\bpadding\b|\bmargin\b|\bradius\b|arrondi|\bhover\b|dark mode|light mode|typograph|\bfont\b|\bfonts\b|font pairing|\bpolice\b|animation|\bmotion\b|micro-interaction|keyframe|glassmorph|neumorph|claymorph|skeuomorph|brutalis|bento|minimalis|responsive|figma'
+# Tightened 2026-07-30 (3rd pass): dropped \bux\b — bare "ux" matched inside
+# French prose ("changement ux vu…"; 2 logged FPs, both FR). \bui\b KEPT
+# (zero logged FP, one logged true positive). NB: the log records only the
+# FIRST match per fire (head -1), so per-token FP rates aren't derivable.
+pattern='redesign|refonte|refont|ui/ux|ux/ui|\bui\b|ui kit|design system|design-system|front-?end design|\bnavbar\b|\bsidebar\b|\bmodal\b|\bbouton\b|\bbutton\b|formulaire|\bhero\b|\bheader\b|\bfooter\b|dropdown|tooltip|\bbadge\b|\bchart\b|graphique|accordion|carousel|\bslider\b|landing|\bdashboard\b|homepage|home page|\baccueil\b|\bécran\b|\becran\b|portfolio|maquette|mockup|wireframe|prototype|\bjoli\b|\bjolie\b|\bbeau\b|\bbelle\b|esth[eé]tique|aesthetic|\bvisuel\b|\bvisual\b|embellir|fignol|peaufin|polish|styliser|styling|stylesheet|\bskin\b|charte graphique|\bbrand\b|branding|\blogo\b|favicon|ic[oô]ne|\bicon\b|\bcss\b|tailwind|shadcn|couleur|gradient|d[eé]grad[eé]|\bombre\b|spacing|espacement|\bmarge\b|\bpadding\b|\bmargin\b|\bradius\b|arrondi|\bhover\b|dark mode|light mode|typograph|\bfont\b|\bfonts\b|font pairing|\bpolice\b|animation|\bmotion\b|micro-interaction|keyframe|glassmorph|neumorph|claymorph|skeuomorph|brutalis|bento|minimalis|responsive|figma'
 
 if printf '%s' "$lc" | grep -Eq "$pattern"; then
   # Counter: log the fire (time, matched token, excerpt) — best-effort, never blocks.

hooks/notify-attention.sh

@@ -0,0 +1,67 @@
+#!/usr/bin/env bash
+# Notification + Stop hook — signal the user through the terminal when
+# Claude needs input (permission, question, idle wait) or has finished
+# responding. Each case gets its own readable label so the toast says
+# which one fired.
+#
+# Runs on the remote (Linux); the only channel that crosses SSH into the
+# VS Code client is the terminal stream. Hooks have no controlling TTY,
+# so the sequence goes through the supported `terminalSequence` JSON
+# output field and Claude Code writes it to the terminal:
+#   - BEL x2 (double beep) -> sound, needs VS Code setting
+#     accessibility.signals.terminalBell { "sound": "on" } AND a non-zero
+#     volume for Code in the Windows volume mixer (BLK-020).
+#   - OSC 777 notify -> Windows toast via the client-side extension
+#     "Terminal Notification" (wenbopan.vscode-terminal-osc-notifier).
+#     A terminal can be deaf to OSC while the bell still rings; test it
+#     before attaching a session to it (LRN-148).
+# Both are invisible no-ops in terminals that ignore them.
+set -u
+
+payload=$(cat 2>/dev/null)
+read_field() {
+  printf '%s' "$payload" | jq -r "$1 // empty" 2>/dev/null \
+    | tr -d '\000-\037' | cut -c1-160
+}
+
+# How many background tasks are still running as the hook fires.
+background_count() {
+  count=$(printf '%s' "$payload" | jq -r '(.background_tasks // []) | length' 2>/dev/null)
+  case "$count" in ''|*[!0-9]*) echo 0 ;; *) echo "$count" ;; esac
+}
+
+event=$(read_field '.notification_type')
+[ -n "$event" ] || event=$(read_field '.hook_event_name')
+
+
+
+case "$event" in
+  # Turn end while a subagent still runs is not the real end: stay silent,
+  # the next turn end will signal once the work is actually done.
+  Stop) [ "$(background_count)" -eq 0 ] || exit 0
+        label="Finished responding" ;;
+  permission_prompt) label="Needs your permission" ;;
+  agent_needs_input) label="Asks you a question" ;;
+  idle_prompt) label="Waiting for you" ;;
+  elicitation_dialog|elicitation_url_dialog) label="Needs your input" ;;
+  # anything else (agent_completed, auth_success, quota_*) stays silent:
+  # signal only for turn end and moments needing the user.
+  *) exit 0 ;;
+esac
+
+detail=$(read_field '.message')
+if [ -n "$detail" ]; then
+  # Claude Code's own wording often restates the label ("Claude needs your
+  # permission"). Append it only when it actually adds something.
+  short=$(printf '%s' "$detail" | tr '[:upper:]' '[:lower:]' | sed 's/^claude //')
+  case "$(printf '%s' "$label" | tr '[:upper:]' '[:lower:]')" in
+    *"$short"*) : ;;
+    *) label="${label}: ${detail}" ;;
+  esac
+fi
+
+bell=$(printf '\a')
+esc=$(printf '\033')
+seq="${bell}${bell}${esc}]777;notify;Claude Code;${label}${esc}\\"
+jq -cn --arg seq "$seq" '{suppressOutput: true, terminalSequence: $seq}'
+exit 0

hooks/session-start.sh

@@ -102,17 +102,21 @@ esac
 _passive_t=0
 detect_superpowers 2>/dev/null && _passive_t=$((_passive_t + 800))
 
-# Token costs for toggle plugins — map display name to cost
-declare -A _plugin_costs=(
-  [gstack]=2750
-  [ui-ux-pro-max]=400
-  [plugin-dev]=100
-  [context7]=200
-  [graphify]=300
-)
+# Token cost per toggle plugin, by display name. A `case`, not an associative
+# array: macOS ships bash 3.2 as /bin/bash, where `declare -A` is rejected —
+# every cost then read as 0 and the budget warning below never fired.
+_plugin_cost() {
+  case "$1" in
+    gstack)        echo 2750 ;;
+    ui-ux-pro-max) echo 400 ;;
+    plugin-dev)    echo 100 ;;
+    context7)      echo 200 ;;
+    graphify)      echo 300 ;;
+    *)             echo 0 ;;
+  esac
+}
 for _p in "${TOGGLE_ACTIVE[@]}"; do
-  _cost="${_plugin_costs[$_p]:-0}"
-  _passive_t=$((_passive_t + _cost))
+  _passive_t=$((_passive_t + $(_plugin_cost "$_p")))
 done
 _budget_pct=$((_passive_t * 100 / _budget))
 if [ "$_budget_pct" -gt 50 ]; then

install-plugins.sh

@@ -16,6 +16,16 @@ err()  { echo -e "${RED}✗${NC} $1"; }
 
 REPO="$(cd "$(dirname "$0")" && pwd)"
 
+# In-place file edit that works on both GNU and BSD sed: `sed -i` needs a backup
+# suffix argument on macOS and forbids one on Linux, so go through a temp file
+# instead. Writing back with `cat >` (not `mv`) keeps the original mode/owner.
+_sed_inplace() {
+  local expr="$1" file="$2" tmp
+  tmp="$(mktemp)" || return 1
+  sed "$expr" "$file" > "$tmp" && cat "$tmp" > "$file"
+  rm -f "$tmp"
+}
+
 # Log to file for post-mortem debugging (terminal output unchanged)
 LOG_FILE="$REPO/install-$(date +%Y%m%d-%H%M%S).log"
 if touch "$LOG_FILE" 2>/dev/null; then
@@ -291,6 +301,67 @@ fi
 
 echo ""
 
+# Portable `timeout`: GNU coreutils' timeout is absent from a stock macOS, and
+# this has to run on a machine where nothing is installed yet. Returns 124 when
+# the deadline is hit, otherwise the command's own exit status.
+_run_with_timeout() {
+  local secs="$1" waited=0 pid
+  shift
+  "$@" &
+  pid=$!
+  while kill -0 "$pid" 2>/dev/null; do
+    if [ "$waited" -ge "$secs" ]; then
+      # Park the shell's own stderr: bash announces a signal-killed job on ITS
+      # stderr, so redirecting kill/wait alone does not suppress it — and that
+      # line in the install log reads like a real error.
+      exec 3>&2 2>/dev/null
+      kill -TERM "$pid" 2>/dev/null || true
+      # Playwright downloads in a child process that survives a TERM aimed at
+      # its parent; left alone it keeps holding the browser-cache lock.
+      pkill -f oopDownloadBrowserMain 2>/dev/null || true
+      wait "$pid" 2>/dev/null || true
+      exec 2>&3 3>&-
+      return 124
+    fi
+    sleep 5
+    waited=$((waited + 5))
+  done
+  wait "$pid"
+}
+
+# Populate gstack's node_modules at the locked versions so `bunx playwright`
+# resolves the LOCAL Playwright. Without it bunx pulls the latest from npm,
+# which wants a different browser revision than the one gstack imports.
+_gstack_bun_install() {
+  ( cd "$GSTACK_DIR" && { bun install --frozen-lockfile >/dev/null 2>&1 ||
+    bun install >/dev/null 2>&1; } )
+}
+
+_gstack_pw_install() { ( cd "$GSTACK_DIR" && bunx playwright install chromium ); }
+
+# Install gstack's Chromium here instead of leaving it to ./setup, so the
+# download can be bounded. A Playwright older than the running Node deadlocks
+# mid-extraction — both processes idle, no error, no progress, forever — which
+# silently stalls the whole installer. On a timeout, bump Playwright (gstack
+# declares "playwright": "^1.x", so a minor bump is within its own range) and
+# retry once. A second failure warns rather than aborts: gstack is OFF by
+# default and only its browser (/browse, /qa, screenshots) depends on this.
+gstack_install_browser_guarded() {
+  [ -d "$GSTACK_DIR" ] && command -v bun >/dev/null 2>&1 || return 0
+  _gstack_bun_install || return 0
+  if _run_with_timeout "$GSTACK_BROWSER_TIMEOUT" _gstack_pw_install; then
+    ok "gstack Chromium ready"
+    return 0
+  fi
+  warn "Chromium install stalled >${GSTACK_BROWSER_TIMEOUT}s — bumping gstack's Playwright, retrying"
+  ( cd "$GSTACK_DIR" && bun add playwright@latest >/dev/null 2>&1 ) || true
+  if _run_with_timeout "$GSTACK_BROWSER_TIMEOUT" _gstack_pw_install; then
+    ok "gstack Chromium ready after Playwright bump (./setup rebuilds browse)"
+  else
+    warn "gstack Chromium unavailable — /browse, /qa and screenshots stay off"
+  fi
+}
+
 # gstack pins Playwright (1.58.x) which only ships browser builds for
 # ubuntu<=24.04. On a newer distro the browser install fails ("does not
 # support chromium on ubuntuXX.04"). Bump gstack's Playwright to a version
@@ -307,7 +378,7 @@ gstack_bump_playwright_if_unsupported() {
   [ -n "$ostag" ] || return 0   # only the known Ubuntu case
   pwlib="$GSTACK_DIR/node_modules/playwright-core/lib"
   # populate node_modules at the pinned version so we can read its support list
-  ( cd "$GSTACK_DIR" && { bun install --frozen-lockfile >/dev/null 2>&1 || bun install >/dev/null 2>&1; } ) || return 0
+  _gstack_bun_install || return 0
   if grep -rqs "$ostag" "$pwlib" 2>/dev/null; then
     return 0   # pinned Playwright already supports this OS
   fi
@@ -337,6 +408,10 @@ echo ""
 #   git add skills-external/gstack && git commit -m "chore: update gstack"
 
 GSTACK_DIR="$REPO/skills-external/gstack"
+# Deadline for gstack's Chromium download+extract. Generous on purpose: a real
+# install runs 1-3 min, overshooting only delays the fallback, and the failure
+# it catches would otherwise hang the installer forever.
+GSTACK_BROWSER_TIMEOUT=900
 
 if [ ! -d "$GSTACK_DIR/.git" ] && [ ! -f "$GSTACK_DIR/.git" ]; then
   info "Initializing GStack submodule..."
@@ -369,6 +444,10 @@ if [ -d "$GSTACK_DIR" ]; then
   # chromium" fail). Non-fatal if it can't — gstack is OFF by default.
   gstack_bump_playwright_if_unsupported
 
+  # Then fetch the browser under a deadline. ./setup would do it itself, but
+  # unbounded — and this is the step that hangs when Playwright trails Node.
+  gstack_install_browser_guarded
+
   info "Running GStack setup..."
   _gstack_setup_ok=0
   if [ -x "$GSTACK_DIR/setup" ]; then
@@ -644,6 +723,46 @@ if command -v ctx7 &>/dev/null; then
   # (~490 tok/session, job1 F10). Purge it unconditionally so re-runs and
   # manual `ctx7 setup` invocations stay rule-free.
   rm -f "$HOME/.claude/rules/context7.md"
+  # BDR-078: re-apply the coverage extension to the generated skill — the
+  # before-writing-code trigger (description) + the cache-first rule (body).
+  # The dist is machine-owned (gitignored, regenerated on fresh clones), so
+  # the durable copy of this patch lives HERE. Idempotent: grep-guarded.
+  _fd="$HOME/.claude/skills/find-docs/SKILL.md"
+  if [ -f "$_fd" ] && ! grep -q 'fast-libs.sh detect' "$_fd"; then
+    if python3 - "$_fd" <<'PY'
+import sys
+p = sys.argv[1]
+s = open(p, encoding="utf-8").read()
+DESC = """
+  Also use BEFORE writing or modifying code that uses a fast-moving library
+  (anything `bash ~/.claude/lib/fast-libs.sh detect .` reports — React,
+  Next.js, Prisma, Tailwind, Astro, Svelte…), even when the user asked for
+  code rather than documentation — unless a fresh `.ctx7-cache/` file already
+  covers the API involved. Stable technologies (C, C++98, POSIX shell, SQL…)
+  need no lookup."""
+BODY = """
+## Cache first
+
+Before any fetch, check the project's `.ctx7-cache/`
+(`bash ~/.claude/lib/fast-libs.sh cache-status .`): a fresh (<7 days)
+`<lib>*.md` may already answer — read it instead of calling ctx7. When a
+`docs` call supports code you are about to write, save the output for the
+next consumer:
+`npx ctx7@latest docs <id> "<query>" | tee .ctx7-cache/<lib>-<topic>.md`.
+"""
+i = s.index("\n---", 3)          # closing frontmatter fence
+s = s[:i] + "\n" + DESC + s[i:]
+m = "using the Context7 CLI.\n"  # intro line under the H1
+j = s.index(m) + len(m) if m in s else len(s)
+s = s[:j] + BODY + s[j:]
+open(p, "w", encoding="utf-8").write(s)
+PY
+    then
+      ok "find-docs skill extended (BDR-078 fast-libs trigger + cache-first)"
+    else
+      warn "find-docs BDR-078 patch failed — re-run 'make plugin' or patch by hand"
+    fi
+  fi
   info "Standalone usage:  ctx7 docs /vercel/next.js \"middleware\""
 fi
 
@@ -953,14 +1072,23 @@ fi
 # `claude --effort max` alias (the alias would even override settings.json).
 EFFORT_CLEANED=0
 if grep -qF 'export CLAUDE_EFFORT=max' "$SHELL_PROFILE" 2>/dev/null; then
-  sed -i '/export CLAUDE_EFFORT=max/d' "$SHELL_PROFILE"; EFFORT_CLEANED=1
+  _sed_inplace '/export CLAUDE_EFFORT=max/d' "$SHELL_PROFILE"; EFFORT_CLEANED=1
 fi
 if grep -qF "alias claude='claude --effort max'" "$SHELL_PROFILE" 2>/dev/null; then
-  sed -i "\#alias claude='claude --effort max'#d" "$SHELL_PROFILE"; EFFORT_CLEANED=1
+  _sed_inplace "\#alias claude='claude --effort max'#d" "$SHELL_PROFILE"; EFFORT_CLEANED=1
 fi
 if [ "$EFFORT_CLEANED" -eq 1 ]; then
-  # Remove orphaned comment lines left before the deleted entries
-  sed -i '/^# Claude Code — added by install-plugins.sh$/{ N; /^\n$/d; }' "$SHELL_PROFILE"
+  # Drop the header comment left stranded above a deleted entry (the marker
+  # followed by a blank line, or by end-of-file). awk, not sed: the previous
+  # `{N; /^\n$/d;}` could never match — after N the pattern space starts with
+  # '#', so the ^\n$ anchor pair never applied, and it was a silent no-op.
+  _tmp_profile="$(mktemp)"
+  awk -v marker='# Claude Code — added by install-plugins.sh' '
+    $0 == marker { stranded = 1; next }
+    stranded     { stranded = 0; if ($0 == "") next; print marker }
+                 { print }
+  ' "$SHELL_PROFILE" > "$_tmp_profile" && cat "$_tmp_profile" > "$SHELL_PROFILE"
+  rm -f "$_tmp_profile"
   info "Removed obsolete effort alias/env from $SHELL_PROFILE (effort set in settings.json)"
 fi
 

lib/challenge-plan.md

@@ -0,0 +1,87 @@
+# Challenge the plan — shared orchestrator include
+
+Runs in the ORCHESTRATOR MAIN LOOP after a plan / reflection is elaborated and
+BEFORE it is executed. Turns a fresh plan into a hardened one by attacking it
+from three independent angles, then RE-THINKING every aspect a challenger lands.
+Loop + synthesis decisions live here, in the main loop (BDR-066: reflection runs
+on the big model; `verify-secure-loop.md`: fresh blind gates, decisions in the
+loop). It never merges, executes, or edits code — it hardens the plan and hands
+it to the orchestrator's existing human gate.
+
+The challenge is ADVISORY into that gate — no new hard block — but a BLOCKER is
+never silently carried past: it is either closed by a NAMED plan change or
+explicitly deferred for the human.
+
+## Inputs the caller must have ready
+
+- `PLAN`: path to the plan ON DISK. If your plan is still inline (a printed
+  checklist / diagnosis / fix plan), FIRST persist it to
+  `.claude/tasks/plans/<date>-<slug>-<HHMM>.md` — the challengers read from disk
+  and judge blind, exactly like the verifier reads the contract.
+- `KIND`: `build-plan` | `proposals` | `fix-bundle` — tunes the lens framing
+  below; the mechanism is identical.
+- `SCOPE`: the files/dirs the plan touches (grounds the critique).
+- `CONSTRAINTS` (optional): the decided trade-offs / rejected alternatives from
+  the design step, so a lens does not re-litigate a settled choice.
+
+Nominal path is cheap for a small, clean plan: three parallel challengers return
+SOLID, synthesis is a no-op. It only costs more when a lens lands a real finding
+— which is the point.
+
+## DISPATCH — three fresh challengers, in parallel, blind
+
+Dispatch THREE fresh `plan-challenger` subagents IN PARALLEL, one per LENS, each
+blind to the others and to this conversation:
+
+```
+Agent(subagent_type="plan-challenger", description="challenge:<lens>", prompt="""
+  PLAN: <the PLAN path>
+  LENS: <correctness | robustness | simplicity>   # one per agent — all three
+  SCOPE: <SCOPE>
+  CONSTRAINTS: <CONSTRAINTS, if any>
+""")
+```
+
+**MODEL (BDR-076, supersedes the BDR-066 inherit):** plan critique is AUDIT
+JUDGMENT — the challengers are `model: opus`-pinned in their frontmatter: a big
+tier, session-independent, off the session model. The session model (Fable)
+keeps only this loop — synthesis, RE-THINK, gate. Never sonnet: that would
+silently downgrade the judgment. (The executor gates stay sonnet.)
+
+**Lens framing by `KIND`** (the agent's three lenses, read against the artifact):
+- `build-plan` — will it WORK / will it BREAK / is it needlessly COMPLEX.
+- `proposals` — are these the RIGHT items & priorities / what did the audit MISS
+  or under-rate as risk / is the backlog over- or under-scoped.
+- `fix-bundle` — will each fix ACHIEVE its goal / could it BREAK or regress the
+  page / is there a simpler fix, or an unnecessary one.
+
+## FAIL-SAFE — never fail open
+
+A challenger that returns a malformed/empty verdict, a missing `PROOF`, or dies →
+retry ONCE with a fresh challenger; a 2nd failure on that lens → STOP and escalate
+to the human, NAMING the lens. Never carry "plan challenged" into the gate on a
+silently dropped lens (`verify-secure-loop.md`: "a mute verifier is NEVER a PASS").
+
+## SYNTHESIZE + RE-THINK (main loop, big model)
+
+Parse each `CHALLENGE — LENS: … — VERDICT:` line and merge the FINDINGS:
+
+- **Severity-driven, not consensus.** Any `[BLOCKER]` from ANY single lens is
+  must-address — the lenses are orthogonal, so a lone security/rollback finding
+  is real, never outvoted by lens-count. Cross-lens agreement only RANKS the MINORs.
+- **RE-THINK the aspect the challenge pointed at.** For each BLOCKER (and each
+  MAJOR you accept): revise the plan on THAT aspect — a NAMED, diffable change to
+  the plan, never a self-authored "addressed" line. A BLOCKER you consciously keep
+  is tagged `[deferred <date>]` for the human to accept at the gate.
+- **Re-challenge once if the plan materially changed** — a fix can open a new
+  flaw. Re-persist the revised `PLAN`, dispatch ONE fresh confirmation challenger,
+  max 1 extra pass, then the gate.
+
+## OUTPUT — into the existing human gate
+
+Feed the orchestrator's gate:
+- the REVISED plan, and
+- a CHALLENGE SUMMARY: each BLOCKER raised → the named change that closed it;
+  anything `[deferred]`; and any lens that failed to return.
+
+The human remains the decider.

lib/contract-interview.md

@@ -35,6 +35,38 @@ ask what the repo can answer — verify paths/APIs/behavior yourself first.
   this conversation.
 - FILE SCOPE: paths/zones expected to change, or `repo-wide — <reason>`.
 
+### ORACLES — a criterion a command can decide carries one
+
+Give such a criterion an indented `CHECK:` (the command), `EXPECT:` (a
+success-only marker), and `EVIDENCE: pending`.
+`bash ~/.claude/lib/gates.sh run <contract>` executes it fail-closed — MET
+requires exit 0 **AND** the marker — and writes the result back over the
+`EVIDENCE:` line. That persisted evidence is what the fresh verifier reads
+as fact instead of trusting the executor's report (GATE 0 in
+`lib/verify-secure-loop.md`).
+
+Both attributes or neither. `CHECK:` without `EXPECT:` is a parse error, not
+a manual criterion — the runner refuses the whole ledger. Leave a criterion
+oracle-free when no command can decide it; the verifier judges those.
+
+Four authoring rules — a gate that cannot fail proves nothing:
+
+1. **Observe the named artifact.** The check reads the file, service, or
+   measurement the criterion's own words name — never a proxy for it.
+   `1. invoices reconcile` + `CHECK: echo ok` is valid and worthless.
+2. **Success-only marker.** The script runs every assertion, exits nonzero
+   on any failure, and prints the `EXPECT:` string only after all pass.
+3. **Positive control before any absence check.** Run the same logic against
+   a fixture known to trip it and confirm it fails. A missing file, a wrong
+   path, and a broken pattern all look exactly like valid absence.
+4. **Recompute supplied numbers.** Never copy a figure from the request into
+   `EXPECT:` — the script derives it from source and prints its own marker.
+   A number that is its own proof proves nothing.
+
+`CHECK:` is shell code run with our privileges. It is safe only because we
+author it in our own repo — never build one out of externally-supplied text
+(a scraped URL, a client string); route those through `lib/url-guard.sh`.
+
 ## STEP 4 — WRITE TO DISK (immediately, before any next step)
 
 Path: `.claude/tasks/contracts/<YYYY-MM-DD>-<slug>-<HHMM>.md`
@@ -57,8 +89,13 @@ Q: <question> / A: <answer>
 (or: none — request complete)
 
 ## ACCEPTANCE CRITERIA
-1. <testable criterion>
-2. <testable criterion>
+1. <criterion a command can decide>
+   CHECK: <command>
+   EXPECT: <success-only marker>
+   EVIDENCE: pending
+2. <criterion only human judgement can decide — no CHECK/EXPECT>
+
+(ABANDON: <n> <non-blank reason> — only for a criterion proven impossible)
 
 ## FILE SCOPE
 <paths/zones>
@@ -78,6 +115,13 @@ Print one line to the user, then continue the flow:
   this micro-gate: human approves → FILE SCOPE gains the entry `[gated]`;
   human declines → the dev removes the edit. Without this gate the dev
   justifies everything and scope constrains nothing.
+- **ABANDONMENT**: a criterion proven impossible within the authorized task
+  is NEVER deleted and never quietly downgraded. Keep it, append
+  `ABANDON: <n> <non-blank reason + handoff>` under the criteria, and name it
+  in the final report. An abandonment is a visible handoff, not a pass: the
+  verifier cannot return `CONFORME` while one stands, and the run cannot be
+  described as fully complete. This is the structural half of the house rule
+  "blocked on an independent sub-part → do the rest, state what's missing".
 - **Deep re-scope** (the request itself changes): NEW contract file with
   `supersedes: <old path>` in its header — never a rewrite of the old one.
 - **Aborted run**: delete the contract file, or commit it with
@@ -96,6 +140,15 @@ Print one line to the user, then continue the flow:
 | init-project | Full. The interviewer's PROJECT BRIEF pours into the contract (V1 features → criteria). |
 | onboard | Audit-scope contract (interview answers → what to audit, which axes). |
 
+Oracles follow the same proportion. hotfix: none — that flow runs no floor
+(and no verifier); the hotfixer runs build/tests itself. feat / bugfix: the
+suite criterion at minimum, and for bugfix the regression test the DIAGNOSIS
+names — its `CHECK:` runs that test alone, so a green result means the
+reproduction actually flipped.
+ship-feature / init-project: build, suite, and every criterion a command can
+settle. onboard: audit criteria are mostly judgement — leave them oracle-free
+rather than invent a check that cannot fail.
+
 ## Hand-off rule
 
 Downstream consumers (plan step, dev subagents, verifier) receive the

lib/deploy-commit.sh

@@ -15,6 +15,19 @@
 #      not just stderr, so it can't share rc 1's "nothing to do" (J4-22).
 set -uo pipefail
 
+# bash 3.2 (macOS /bin/bash) predates the `mapfile` builtin; this is the portable
+# equivalent. Reads stdin's lines into the array named by $1, space-safe
+# (IFS= read -r). The array is reset first, so empty input yields an empty array
+# rather than a stale or unset one — `set -u` on bash < 4.4 trips on expanding
+# an array that was never assigned.
+_read_lines_into() {
+  local _name="$1" _line
+  eval "$_name=()"
+  while IFS= read -r _line; do
+    eval "$_name+=(\"\$_line\")"
+  done
+}
+
 _in_git_repo() { git rev-parse --git-dir >/dev/null 2>&1; }
 
 _unsafe_state() {                       # 0 = unsafe
@@ -48,7 +61,8 @@ _in_git_repo || { echo "deploy-commit: not a git repo" >&2; exit 2; }
 case "$cmd" in
   pending)
     [ "$#" -gt 0 ] || { echo "deploy-commit: pending needs file args" >&2; exit 2; }
-    mapfile -t violations < <(_scope_violations "$@")
+    violations=()
+    _read_lines_into violations < <(_scope_violations "$@")
     if [ "${#violations[@]}" -gt 0 ]; then
       { echo "deploy-commit: REFUSED — path(s) outside .claude/deploy/ allowlist:";
         printf '  - %s\n' "${violations[@]}";
@@ -59,21 +73,25 @@ case "$cmd" in
   commit)
     msg="${1:-}"; shift || true
     [ -n "$msg" ] && [ "$#" -gt 0 ] || { echo "deploy-commit: commit needs <msg> <file>..." >&2; exit 2; }
-    mapfile -t violations < <(_scope_violations "$@")
+    violations=()
+    _read_lines_into violations < <(_scope_violations "$@")
     if [ "${#violations[@]}" -gt 0 ]; then
       { echo "deploy-commit: REFUSED — path(s) outside .claude/deploy/ allowlist:";
         printf '  - %s\n' "${violations[@]}";
         echo "deploy-commit: NOTHING committed. Caller must pass only .claude/deploy/ files."; } >&2
       exit 4
     fi
-    mapfile -t ignored_paths < <(for p in "$@"; do _ignored "$p" && printf '%s\n' "$p"; done)
+    ignored_paths=()
+    _read_lines_into ignored_paths \
+      < <(for p in "$@"; do _ignored "$p" && printf '%s\n' "$p"; done)
     if [ "${#ignored_paths[@]}" -gt 0 ]; then
       { echo "deploy-commit: REFUSED — path(s) are git-ignored and will NOT persist; \`.claude/deploy/\` must be committable in this project:";
         printf '  - %s\n' "${ignored_paths[@]}"; } >&2
       exit 5
     fi
     _unsafe_state && { echo "deploy-commit: unsafe git state (detached/merge/rebase) — not committing" >&2; exit 3; }
-    mapfile -t changed < <(_changed_only "$@")
+    changed=()
+    _read_lines_into changed < <(_changed_only "$@")
     [ "${#changed[@]}" -gt 0 ] || exit 1
     git add -- "${changed[@]}"
     if git diff --cached --quiet -- "${changed[@]}"; then

lib/doc-commit.md

@@ -17,23 +17,28 @@ and any SIGNIFICANT-gated patch), with the code already committed.
 - Orchestrators (ship-feature / init-project): run it BEFORE the FINISH step — otherwise
   the doc commit strands outside the merge/PR (the exact bug this fixes). See ORDERING.
 
-doc-syncer runs IN-THREAD (the orchestrator loads it), so the list of files it patched is
-already in hand — surfaced as `PATCHED_FILES:` in doc-syncer's OUTPUT, ONE PATH PER LINE.
-Pass each line as a SEPARATE argument (see DO step 3).
+doc-syncer runs DISPATCHED (BDR-077: `MODE: audit` on opus → dispatcher gate
+→ `MODE: patch` on sonnet); its patch-mode report hands the orchestrator BOTH
+machine blocks: `PATCHED_FILES:` (ONE PATH PER LINE — pass each line as a
+SEPARATE argument, see DO step 3) and `CHANGE SUMMARY` (one line per patched
+file — the patch context that used to be in-thread now crosses the dispatch
+boundary through this block, LRN-126).
 
 ## DO
 
 1. Collect `PATCHED_FILES` — the public-doc paths doc-syncer wrote this run (its OUTPUT
    block, ONE PATH PER LINE). Empty → nothing to commit; the helper no-ops.
 
-2. Compose — from the patch context the AGENT holds (doc-syncer ran in-thread, so the
-   agent knows exactly what changed) — BOTH artifacts:
+2. Compose — from doc-syncer's `CHANGE SUMMARY` block (the patcher held the
+   patch context and reported it; a dispatched patcher with NO summary block
+   in its report = incomplete report, re-dispatch rather than invent) —
+   BOTH artifacts:
    - the COMMIT MESSAGE, repo style `docs: <summary> — <flow>`
      (`docs: README features + USAGE flags — ship-feature dark-mode`);
    - the CHANGE SUMMARY for the rc 0 surface (e.g. "README features section + USAGE
-     --export flag").
-   Both are the AGENT's to write — the helper produces NEITHER (its only stdout is the
-   hash). This is the load-bearing point of the visible surface: see the rc 0 row.
+     --export flag") — derived from the block, never a bare file count.
+   Both are the ORCHESTRATOR's to write — the helper produces NEITHER (its only stdout
+   is the hash). This is the load-bearing point of the visible surface: see the rc 0 row.
 
 3. Commit surgically via the helper, passing EXACTLY the patched files — each path as a
    SEPARATE argument (split `PATCHED_FILES` on NEWLINES only), capturing the hash:

lib/doc-commit.sh

@@ -25,6 +25,19 @@
 
 set -uo pipefail
 
+# bash 3.2 (macOS /bin/bash) predates the `mapfile` builtin; this is the portable
+# equivalent. Reads stdin's lines into the array named by $1, space-safe
+# (IFS= read -r). The array is reset first, so empty input yields an empty array
+# rather than a stale or unset one — `set -u` on bash < 4.4 trips on expanding
+# an array that was never assigned.
+_read_lines_into() {
+  local _name="$1" _line
+  eval "$_name=()"
+  while IFS= read -r _line; do
+    eval "$_name+=(\"\$_line\")"
+  done
+}
+
 _in_git_repo() { git rev-parse --git-dir >/dev/null 2>&1; }
 
 # True (0) when the repo is in a state where we must NOT auto-commit:
@@ -89,7 +102,7 @@ commit_docs() {
   # (doc-syncer must never patch .claude/ or CLAUDE.md). Abort the WHOLE commit and
   # name the offenders — never filter-and-commit-the-rest (that masks the bug).
   local violations
-  mapfile -t violations < <(_scope_violations "$@")
+  _read_lines_into violations < <(_scope_violations "$@")
   if [ "${#violations[@]}" -gt 0 ]; then
     {
       echo "doc-commit: REFUSED — out-of-scope path(s) in the doc list (upstream BDR-022 violation):"
@@ -100,7 +113,7 @@ commit_docs() {
     return 4
   fi
   local changed
-  mapfile -t changed < <(_changed_paths "$@")
+  _read_lines_into changed < <(_changed_paths "$@")
   if [ "${#changed[@]}" -eq 0 ]; then
     echo "doc-commit: nothing pending — no-op" >&2
     return 0

lib/fast-libs.sh

@@ -0,0 +1,65 @@
+#!/usr/bin/env bash
+# fast-libs.sh — single source of truth for "fast-moving library" detection.
+#
+# Fast-moving = API churns faster than model training data (React, Next.js,
+# Prisma…) → consult ctx7 (find-docs) before coding against it. Stable techs
+# (C, C++98, POSIX sh, SQL…) never match: no ctx7 needed (BDR-078).
+#
+# Consumers: hooks/ctx7-reminder.sh, /ship-feature STEP 0c, /init-project
+# STEP 5c, /onboard STEP 3.5, feater/bugfixer executor briefs.
+#
+# Verbs:
+#   fast-libs.sh detect [dir]        detected libs, one/line; exit 1 if none
+#   fast-libs.sh cache-status [dir]  fresh|stale|missing; exit 0 only if fresh
+
+set -euo pipefail
+
+# Exact npm dependency keys (unscoped). Anchored full-key match — "react"
+# must not drag react-icons along.
+NPM_EXACT='next|react|react-dom|react-native|expo|prisma|supabase'
+NPM_EXACT+='|drizzle-orm|astro|svelte|vue|nuxt|tailwindcss|vite|next-auth'
+NPM_EXACT+='|motion|framer-motion|ai|openai|langchain|remix|fastify'
+# Scoped npm orgs (@org/…).
+NPM_SCOPED='prisma|supabase|astrojs|sveltejs|tanstack|clerk|anthropic-ai'
+NPM_SCOPED+='|langchain|remix-run|nestjs|tailwindcss'
+# Python distributions (requirements.txt / pyproject.toml).
+PY_LIBS='fastapi|pydantic|sqlalchemy|langchain'
+
+CACHE_MAX_AGE_DAYS=7
+
+npm_fast_libs() { # $1=dir — matching dependency keys, one per line
+  [ -f "$1/package.json" ] || return 0
+  jq -r '((.dependencies // {}) + (.devDependencies // {})) | keys[]' \
+    "$1/package.json" 2>/dev/null \
+    | grep -E "^(${NPM_EXACT})\$|^@(${NPM_SCOPED})/" || true
+}
+
+py_fast_libs() { # $1=dir — matching distributions, one per line
+  grep -hoiE "\b(${PY_LIBS})\b" \
+    "$1/requirements.txt" "$1/pyproject.toml" 2>/dev/null \
+    | tr '[:upper:]' '[:lower:]' | LC_ALL=C sort -u || true
+}
+
+detect() { # $1=dir — union, sorted unique; exit 1 when empty
+  local libs
+  # LC_ALL=C: deterministic order whatever the caller's locale.
+  libs="$(printf '%s\n%s\n' "$(npm_fast_libs "$1")" "$(py_fast_libs "$1")" \
+    | sed '/^$/d' | LC_ALL=C sort -u)"
+  [ -n "$libs" ] || return 1
+  printf '%s\n' "$libs"
+}
+
+cache_status() { # $1=dir — fresh|stale|missing; exit 0 only when fresh
+  [ -d "$1/.ctx7-cache" ] || { echo missing; return 1; }
+  if [ -n "$(find "$1/.ctx7-cache" -name '*.md' \
+      -mtime "-${CACHE_MAX_AGE_DAYS}" -print -quit 2>/dev/null)" ]; then
+    echo fresh; return 0
+  fi
+  echo stale; return 1
+}
+
+case "${1:-}" in
+  detect)       detect "${2:-.}" ;;
+  cache-status) cache_status "${2:-.}" ;;
+  *) echo "usage: fast-libs.sh detect|cache-status [dir]" >&2; exit 2 ;;
+esac

lib/gates.sh

@@ -0,0 +1,355 @@
+#!/usr/bin/env bash
+# Deterministic floor under GATE 1: execute the acceptance criteria that the
+# contract itself declares as oracles, fail-closed, and persist the evidence
+# INTO the contract file.
+#
+#   bash ~/.claude/lib/gates.sh status <contract>   # parse only, never runs
+#   bash ~/.claude/lib/gates.sh run    <contract>   # execute + write evidence
+#
+# rc 0 = MET       every runnable criterion passed, no abandonment standing
+#    2 = UNMET     a runnable criterion failed, or the ledger is malformed
+#    3 = ABANDONED runnable criteria all passed, an abandonment still stands
+#
+# WHY: GATE 1 (lib/verify-secure-loop.md) is an LLM dispatch, and the
+# verifier's mandatory `PROOF:` line is a line the verifier WRITES — nothing
+# structurally stops it from being produced without anything being executed.
+# This runs what the contract declares BEFORE a verifier is ever spawned: a
+# red floor sends the executor back for free. Adapted from the `unlazy` skill
+# (Leonxlnx/unlazy) — its gate ledger, minus the machinery we do not need.
+#
+# `run` always re-executes every runnable criterion, including ones already
+# recorded MET. Trusting written evidence is exactly the failure this closes,
+# so there is no incremental mode to get it wrong with.
+#
+# TRUST BOUNDARY: `CHECK:` is shell code, run with this process's privileges
+# and environment. That is safe here only because the contract is authored by
+# our own orchestrator in our own repo — which is why there is no approval
+# store (we never execute ledgers inherited from a foreign repo). NEVER build
+# a `CHECK:` out of externally-supplied text; route such values through
+# lib/url-guard.sh first.
+set -uo pipefail
+
+TIMEOUT="${GATES_TIMEOUT:-120}"
+# GNU coreutils' `timeout` ships on Linux but NOT on a stock macOS (Homebrew
+# installs it as both `timeout` and `gtimeout`). Resolve it once: without it
+# every check exits 127 and reports NOT-MET whatever the check actually did.
+# Overridable, and with `-` not `:-` so an explicitly EMPTY value forces the
+# pure-bash path — that is how the fallback gets exercised on a machine that
+# does have the binary.
+GATES_TIMEOUT_BIN="${GATES_TIMEOUT_BIN-$(command -v timeout || command -v gtimeout || true)}"
+EVIDENCE_CAP=140
+
+# Module-level parse tables, index-aligned. Bash has no record type; threading
+# eight parallel arrays through every call would cost more readability than
+# the explicit data flow buys.
+_ID=(); _TEXT=(); _CHECK=(); _EXPECT=(); _EVLINE=(); _EVTEXT=()
+_STATUS=(); _EVID=()
+_ABANDON_ID=(); _ABANDON_WHY=()
+_ERRORS=()
+_CUR=-1
+
+_die() { printf 'GATES — VERDICT: ERROR(%s)\n' "$1"; exit 2; }
+_err() { _ERRORS+=("$1"); }
+
+_trim() {
+  local s="$1"
+  s="${s#"${s%%[![:space:]]*}"}"
+  printf '%s' "${s%"${s##*[![:space:]]}"}"
+}
+
+# ── parse ───────────────────────────────────────────────────────────────────
+
+_new_crit() { # _new_crit <id> <text>
+  local i
+  for ((i = 0; i < ${#_ID[@]}; i++)); do
+    if [ "${_ID[i]}" = "$1" ]; then
+      _err "duplicate criterion id: $1"
+      # Orphan what follows instead of aliasing it onto the previous
+      # criterion, which would hand one gate another gate's oracle.
+      _CUR=-1
+      return 0
+    fi
+  done
+  _ID+=("$1"); _TEXT+=("$2")
+  _CHECK+=(""); _EXPECT+=(""); _EVLINE+=("0"); _EVTEXT+=("")
+  _CUR=$((${#_ID[@]} - 1))
+}
+
+_set_attr() { # _set_attr <CHECK|EXPECT|EVIDENCE> <value> <lineno>
+  if [ "$_CUR" -lt 0 ]; then
+    _err "$1 at line $3 belongs to no criterion"
+    return 0
+  fi
+  case "$1" in
+    CHECK)    _CHECK[_CUR]="$2" ;;
+    EXPECT)   _EXPECT[_CUR]="$2" ;;
+    EVIDENCE) _EVLINE[_CUR]="$3"; _EVTEXT[_CUR]="$2" ;;
+  esac
+}
+
+# An UNINDENTED attribute is diagnosed, never absorbed: silently ignoring it
+# would demote a runnable criterion to a manual one, which is the one parse
+# bug that turns this checker into a rubber stamp.
+_absorb() { # _absorb <raw-line> <lineno>
+  local body
+  if [[ "$1" =~ ^([0-9]+)\.[[:space:]]+(.*)$ ]]; then
+    _new_crit "${BASH_REMATCH[1]}" "${BASH_REMATCH[2]}"
+  elif [[ "$1" =~ ^ABANDON:[[:space:]]*([0-9]+)?[[:space:]]*(.*)$ ]]; then
+    _ABANDON_ID+=("${BASH_REMATCH[1]}"); _ABANDON_WHY+=("${BASH_REMATCH[2]}")
+  elif [[ "$1" =~ ^(CHECK|EXPECT|EVIDENCE): ]]; then
+    _err "unindented ${BASH_REMATCH[1]}: at line $2"
+  elif [[ "$1" =~ ^[[:space:]]+(CHECK|EXPECT|EVIDENCE):(.*)$ ]]; then
+    body="$(_trim "${BASH_REMATCH[2]}")"
+    _set_attr "${BASH_REMATCH[1]}" "$body" "$2"
+  fi
+}
+
+_parse() { # _parse <file>
+  local line n=0 fence=0 inblock=0
+  while IFS= read -r line || [ -n "$line" ]; do
+    n=$((n + 1))
+    case "$line" in '```'*) fence=$((1 - fence)); continue ;; esac
+    [ "$fence" -eq 1 ] && continue
+    case "$line" in
+      '## ACCEPTANCE CRITERIA'*) inblock=1; continue ;;
+      '## '*) inblock=0; continue ;;
+    esac
+    [ "$inblock" -eq 1 ] && _absorb "$line" "$n"
+  done < "$1"
+}
+
+# ── validation ──────────────────────────────────────────────────────────────
+
+_validate_oracles() {
+  local i
+  for ((i = 0; i < ${#_ID[@]}; i++)); do
+    if [ -n "${_CHECK[i]}" ] && [ -z "${_EXPECT[i]}" ]; then
+      _err "criterion ${_ID[i]}: CHECK without EXPECT (partial oracle)"
+    elif [ -z "${_CHECK[i]}" ] && [ -n "${_EXPECT[i]}" ]; then
+      _err "criterion ${_ID[i]}: EXPECT without CHECK (partial oracle)"
+    elif [ -n "${_CHECK[i]}" ] && [ "${_EVLINE[i]}" = "0" ]; then
+      _err "criterion ${_ID[i]}: runnable but has no EVIDENCE: line"
+    fi
+  done
+}
+
+_validate_abandons() {
+  local i j found
+  for ((i = 0; i < ${#_ABANDON_ID[@]}; i++)); do
+    found=0
+    for ((j = 0; j < ${#_ID[@]}; j++)); do
+      [ "${_ID[j]}" = "${_ABANDON_ID[i]}" ] && found=1
+    done
+    [ "$found" -eq 1 ] ||
+      _err "ABANDON names unknown criterion: '${_ABANDON_ID[i]}'"
+    [ -n "$(_trim "${_ABANDON_WHY[i]}")" ] ||
+      _err "ABANDON ${_ABANDON_ID[i]}: blank reason (a handoff needs one)"
+  done
+}
+
+_is_abandoned() { # _is_abandoned <criterion-id>
+  local i
+  for ((i = 0; i < ${#_ABANDON_ID[@]}; i++)); do
+    [ "${_ABANDON_ID[i]}" = "$1" ] && return 0
+  done
+  return 1
+}
+
+# ── execution ───────────────────────────────────────────────────────────────
+
+# One line, capped, newlines flattened: the smallest output that proves the
+# outcome. Full logs stay in the terminal, never in the contract.
+_decisive() { # _decisive <combined-output>
+  local flat
+  flat="$(printf '%s' "$1" | tr '\n\r\t' '   ' | tr -s ' ')"
+  flat="$(_trim "$flat")"
+  if [ "${#flat}" -gt "$EVIDENCE_CAP" ]; then
+    printf '%s…' "${flat:0:$EVIDENCE_CAP}"
+  else
+    printf '%s' "$flat"
+  fi
+}
+
+# Fail-closed: exit 0 AND the marker. A nonzero process never passes because
+# its error text happens to contain the expected token.
+# Same contract as `timeout`: run the command, return 124 if it outruns <secs>.
+# Pure-bash stand-in for a platform shipping neither binary, so the deadline
+# stays real instead of silently degrading into "every gate NOT-MET".
+_gates_timeout() { # _gates_timeout <secs> <cmd>...
+  local secs="$1"; shift
+  [ -n "$GATES_TIMEOUT_BIN" ] && { "$GATES_TIMEOUT_BIN" "$secs" "$@"; return $?; }
+  local waited=0 pid
+  "$@" &
+  pid=$!
+  while kill -0 "$pid" 2>/dev/null; do
+    if [ "$waited" -ge "$secs" ]; then
+      # Park the shell's stderr: bash announces a signal-killed job on ITS
+      # stderr, which the caller captures with 2>&1 and would read as output.
+      exec 3>&2 2>/dev/null
+      kill -TERM "$pid" 2>/dev/null || true
+      wait "$pid" 2>/dev/null || true
+      exec 2>&3 3>&-
+      return 124
+    fi
+    sleep 1
+    waited=$((waited + 1))
+  done
+  wait "$pid"
+}
+
+_run_one() { # _run_one <idx>
+  local i="$1" out rc
+  out="$(_gates_timeout "$TIMEOUT" bash -c "${_CHECK[i]}" 2>&1)"
+  rc=$?
+  _STATUS[i]="NOT-MET"
+  if [ "$rc" -eq 124 ]; then
+    _EVID[i]="NOT-MET timeout=${TIMEOUT}s"
+  elif [ "$rc" -ne 0 ]; then
+    _EVID[i]="NOT-MET exit=$rc (nonzero) :: $(_decisive "$out")"
+  elif [[ "$out" != *"${_EXPECT[i]}"* ]]; then
+    _EVID[i]="NOT-MET exit=0 marker-absent :: $(_decisive "$out")"
+  else
+    _STATUS[i]="MET"
+    _EVID[i]="MET exit=0 marker-found :: $(_decisive "$out")"
+  fi
+}
+
+_run_all() {
+  local i
+  for ((i = 0; i < ${#_ID[@]}; i++)); do
+    _STATUS[i]=""; _EVID[i]=""
+    [ -n "${_CHECK[i]}" ] && _run_one "$i"
+  done
+}
+
+_evline_owner() { # _evline_owner <lineno> — echoes idx, or nothing
+  local i
+  for ((i = 0; i < ${#_ID[@]}; i++)); do
+    if [ "${_EVLINE[i]}" = "$1" ] && [ -n "${_EVID[i]}" ]; then
+      printf '%s' "$i"
+      return 0
+    fi
+  done
+}
+
+# Rewrites only the EVIDENCE lines of criteria that actually ran; every other
+# byte of the contract is copied through, indentation included.
+_write_back() { # _write_back <file>
+  local tmp line n=0 idx
+  tmp="$(mktemp)" || _die "mktemp failed"
+  while IFS= read -r line || [ -n "$line" ]; do
+    n=$((n + 1))
+    idx="$(_evline_owner "$n")"
+    if [ -n "$idx" ]; then
+      printf '%s%s\n' "${line%%[![:space:]]*}" "EVIDENCE: ${_EVID[idx]}"
+    else
+      printf '%s\n' "$line"
+    fi
+  done < "$1" > "$tmp"
+  cat "$tmp" > "$1" && rm -f "$tmp"
+}
+
+# ── report ──────────────────────────────────────────────────────────────────
+
+# A recorded `pending`, or a criterion that never ran, is PENDING — never MET.
+# `status` reports what the file says; it does not revalidate old evidence.
+_row_state() { # _row_state <idx>
+  local i="$1"
+  _is_abandoned "${_ID[i]}" && { printf 'ABANDONED'; return 0; }
+  [ -z "${_CHECK[i]}" ] && { printf 'MANUAL'; return 0; }
+  [ -n "${_STATUS[i]:-}" ] && { printf '%s' "${_STATUS[i]}"; return 0; }
+  case "${_EVTEXT[i]}" in
+    MET' '*) printf 'MET-RECORDED' ;;
+    *) printf 'PENDING' ;;
+  esac
+}
+
+_report_rows() {
+  local i state
+  for ((i = 0; i < ${#_ID[@]}; i++)); do
+    state="$(_row_state "$i")"
+    printf '  %-3s %-13s %s\n' "${_ID[i]}" "$state" "${_TEXT[i]}"
+  done
+}
+
+_report_abandons() {
+  local i
+  for ((i = 0; i < ${#_ABANDON_ID[@]}; i++)); do
+    printf '  ABANDONED %s — %s\n' "${_ABANDON_ID[i]}" "${_ABANDON_WHY[i]}"
+  done
+}
+
+_count_state() { # _count_state <state>
+  local i n=0
+  for ((i = 0; i < ${#_ID[@]}; i++)); do
+    [ "$(_row_state "$i")" = "$1" ] && n=$((n + 1))
+  done
+  printf '%s' "$n"
+}
+
+_verdict() { # _verdict <mode> — prints the line, returns the rc
+  local unmet pending abandoned
+  if [ "${#_ERRORS[@]}" -gt 0 ]; then
+    printf 'GATES — VERDICT: ERROR(%s)\n' "${#_ERRORS[@]}"
+    return 2
+  fi
+  unmet="$(_count_state NOT-MET)"
+  pending="$(_count_state PENDING)"
+  abandoned="$(_count_state ABANDONED)"
+  [ "$unmet" -gt 0 ] &&
+    { printf 'GATES — VERDICT: UNMET(%s)\n' "$unmet"; return 2; }
+  if [ "$1" = "status" ] && [ "$pending" -gt 0 ]; then
+    printf 'GATES — VERDICT: PENDING(%s)\n' "$pending"
+    return 2
+  fi
+  [ "$abandoned" -gt 0 ] &&
+    { printf 'GATES — VERDICT: ABANDONED(%s)\n' "$abandoned"; return 3; }
+  printf 'GATES — VERDICT: MET\n'
+  return 0
+}
+
+_report() { # _report <mode> <file>
+  local rc
+  printf 'GATES — %s (%s)\n' "$2" "$1"
+  _report_rows
+  _report_abandons
+  [ "${#_ERRORS[@]}" -gt 0 ] && printf '  ERROR %s\n' "${_ERRORS[@]}"
+  printf 'RUNNABLE: %s of %s criteria; timeout %ss\n' \
+    "$(_runnable_count)" "${#_ID[@]}" "$TIMEOUT"
+  _verdict "$1"
+  rc=$?
+  return "$rc"
+}
+
+_runnable_count() {
+  local i n=0
+  for ((i = 0; i < ${#_ID[@]}; i++)); do
+    [ -n "${_CHECK[i]}" ] && n=$((n + 1))
+  done
+  printf '%s' "$n"
+}
+
+# ── entry point ─────────────────────────────────────────────────────────────
+
+main() { # main <status|run> <contract>
+  local mode="$1" file="$2"
+  [ -r "$file" ] || _die "contract unreadable: $file"
+  _parse "$file"
+  [ "${#_ID[@]}" -gt 0 ] ||
+    _die "no numbered criteria under ## ACCEPTANCE CRITERIA"
+  _validate_oracles
+  _validate_abandons
+  if [ "$mode" = "run" ] && [ "${#_ERRORS[@]}" -eq 0 ]; then
+    _run_all
+    _write_back "$file"
+  fi
+  _report "$mode" "$file"
+}
+
+case "${1:-}" in
+  status|run)
+    [ $# -eq 2 ] || _die "usage: gates.sh {status|run} <contract-path>"
+    main "$1" "$2"
+    ;;
+  *) _die "usage: gates.sh {status|run} <contract-path>" ;;
+esac

lib/gitflow-aiguillage.md

@@ -33,8 +33,11 @@ with no code branch to follow. That is the leak it closes: the `.claude/**` hook
 exemption still lets a *manual* memory commit through on a protected base, but a
 skill-driven one now branches to `chore/*` first.
 
-**Never run `gitflow finish`** — these flows commit, they do not merge. Integration
-is a separate, human-gated step (the `gitflow` skill).
+**Integration is human-gated by default** — these flows commit, they do not merge.
+EXCEPTION: `/capitalize` + `/close` auto-persist their memory-only commit (finish →
+develop + push) when THEY branched a `chore/*` off develop this run (BDR-068 — a
+scoped [[LRN-069]] exception; see the capitalize skill's STEP 5C). `/prune-memory`
++ `/reconcile` stay fully human-gated: never run `gitflow finish` from them.
 
 Note: `hotfix` branches off **main** (prod) even when invoked from `develop` — that
 is the gitflow definition of a hotfix. For a dev-scoped small fix, use `/bugfix`

lib/gitflow-test.sh

@@ -239,6 +239,7 @@ gitflow_start feature glwork >/dev/null 2>&1
 # proving this backstop is NOT gated by the branch-protection check above it)
 printf 'aws_access_key_id = AKIA%s\n' "GDR5XRBXYARW2I5N" > secret.txt
 git add secret.txt
+# shellcheck disable=SC2034  # gl_out is used in the deferred chk eval strings
 gl_out="$(git commit -q -m "add secret" 2>&1)"; gl_rc=$?
 chk "T16a fake secret on feature branch → blocked" "[ $gl_rc -ne 0 ]"
 chk "T16a message mentions gitleaks"               'printf "%s" "$gl_out" | grep -qi gitleaks'
@@ -252,10 +253,57 @@ chk "T16b clean commit still succeeds" 'git commit -q -m "clean work" 2>/dev/nul
 # T16c — gitleaks missing from PATH → warn, never block (defense in depth
 # must not become a new single point of failure)
 echo clean2 > clean2.txt; git add clean2.txt
+# shellcheck disable=SC2034  # noleaks_out is used in the deferred chk eval strings
 noleaks_out="$(PATH=/usr/bin:/bin git commit -q -m "clean work 2" 2>&1)"; noleaks_rc=$?
 chk "T16c missing-gitleaks → still commits (rc0)" "[ $noleaks_rc -eq 0 ]"
 chk "T16c missing-gitleaks → warns"    'printf "%s" "$noleaks_out" | grep -qi "not installed"'
 
+echo "T17 — finish auto-purges transient superpowers artifacts (BDR-065)"
+# T17a — feature carrying docs/superpowers spec+plan: purged before merge,
+# develop TIP clean, artifacts still recoverable from history (archive property)
+newrepo purgefeat; echo a>a; hookon; gitflow_init >/dev/null 2>&1
+gitflow_start feature pf >/dev/null 2>&1
+mkdir -p docs/superpowers/specs docs/superpowers/plans
+echo spec > docs/superpowers/specs/s.md
+echo plan > docs/superpowers/plans/p.md
+echo code > feat.txt
+git add -A; git commit -q -m "feat + transient spec/plan"
+gitflow_finish >/dev/null 2>&1
+# the add-commit stays reachable from develop via the --no-ff merge's 2nd parent;
+# --full-history defeats the path simplification that hides it, and `git show
+# <sha>:path` proves BDR-065's "git history = the archive" recovery.
+# shellcheck disable=SC2034  # pf_add_sha is used in the deferred chk eval string
+pf_add_sha="$(git log develop --full-history --format=%H -- docs/superpowers/specs/s.md | tail -1)"
+chk "T17a merged into develop"           'git log develop --oneline | grep -q "Merge feature/pf into develop"'
+chk "T17a develop TIP has no transient"  '[ -z "$(git ls-tree -r develop --name-only -- docs/superpowers)" ]'
+chk "T17a purge commit on record"        'git log develop --oneline | grep -q "purge transient planning artifacts"'
+chk "T17a artifact recoverable from history" '[ "$(git show "$pf_add_sha":docs/superpowers/specs/s.md 2>/dev/null)" = spec ]'
+chk "T17a non-transient code survives"   'git ls-tree -r develop --name-only | grep -qx feat.txt'
+chk "T17a feature branch deleted"        '! git rev-parse --verify -q refs/heads/feature/pf >/dev/null'
+
+# T17b — no artifacts → purge is a silent no-op, no spurious commit
+newrepo purgenone; echo a>a; hookon; gitflow_init >/dev/null 2>&1
+gitflow_start feature pn >/dev/null 2>&1; echo w>w.txt; git add w.txt; git commit -q -m w
+gitflow_finish >/dev/null 2>&1
+chk "T17b merged into develop"     'git log develop --oneline | grep -q "Merge feature/pn into develop"'
+chk "T17b no purge commit created" '! git log develop --oneline | grep -q "purge transient"'
+
+# T17c — opt-out (GITFLOW_PURGE_TRANSIENT=0) keeps the artifacts on develop
+newrepo purgeoff; echo a>a; hookon; gitflow_init >/dev/null 2>&1
+gitflow_start feature po >/dev/null 2>&1
+mkdir -p docs/superpowers/specs; echo spec > docs/superpowers/specs/s.md
+git add -A; git commit -q -m "feat + spec"
+GITFLOW_PURGE_TRANSIENT=0 gitflow_finish >/dev/null 2>&1
+chk "T17c opt-out keeps transient on develop TIP" '[ -n "$(git ls-tree -r develop --name-only -- docs/superpowers)" ]'
+
+# T17d — chore is OUT of purge scope (only feature/bugfix originate artifacts)
+newrepo purgechore; echo a>a; hookon; gitflow_init >/dev/null 2>&1
+gitflow_start chore pc >/dev/null 2>&1
+mkdir -p docs/superpowers/specs; echo spec > docs/superpowers/specs/s.md
+git add -A; git commit -q -m "chore + spec"
+gitflow_finish >/dev/null 2>&1
+chk "T17d chore leaves transient (not in scope)" '[ -n "$(git ls-tree -r develop --name-only -- docs/superpowers)" ]'
+
 echo
 echo "==== RESULT: $PASS passed, $FAIL failed ===="
 [ "$FAIL" -eq 0 ]

lib/gitflow.sh

@@ -18,6 +18,12 @@ GITFLOW_MAIN="main"
 GITFLOW_DEVELOP="develop"
 # template resolved relative to the lib; overridable for tests.
 GITFLOW_GITIGNORE_TEMPLATE="${GITFLOW_GITIGNORE_TEMPLATE:-$_GITFLOW_LIB_DIR/../templates/gitignore/standard.gitignore}"
+# Transient planning artifacts (superpowers spec/plan). A feature/bugfix run
+# COMMITS them (SDD worktree + reviewers read them from disk); finish PURGES
+# them before the merge reaches develop's tip (BDR-065). Fixed path list;
+# read GITFLOW_PURGE_TRANSIENT=0 at finish time to opt out (read in the helper,
+# never cached here, so an inline `VAR=0 gitflow_finish` override works).
+GITFLOW_TRANSIENT_PATHS=("docs/superpowers/specs" "docs/superpowers/plans")
 
 # ── predicates / pure helpers ────────────────────────────────────────────────
 
@@ -97,6 +103,42 @@ _gitflow_delete() {                # <branch>
   git branch -q -d "$br" || { echo "gitflow: '$br' not fully merged — branch kept" >&2; return 5; }
 }
 
+# _gitflow_purge_transient → remove the committed transient planning artifacts
+# (BDR-065) from the CURRENT branch just before the directed merge. Result: the
+# removal rides the feature/bugfix branch, whose earlier commits stay reachable
+# from develop through the --no-ff merge (`git show <sha>:…` = the archive),
+# while develop's TIP lands clean. Automates the manual post-merge chore that
+# BDR-065 left as doctrine (and that slipped once — commit 655e364).
+#
+# BEST-EFFORT BY CONTRACT: this NEVER aborts a finish. Nothing tracked → no-op;
+# uncommitted changes under those paths, or a failed commit → warn + degrade to
+# the old manual-cleanup behaviour, index/tree restored, merge still proceeds.
+# The scoped commit (`-- <paths>`) records only the deletions, so a dirty index
+# is never swept in. Opt out with GITFLOW_PURGE_TRANSIENT=0.
+_gitflow_purge_transient() {
+  [ "${GITFLOW_PURGE_TRANSIENT:-1}" = 1 ] || return 0
+  local p; local -a tracked=()
+  for p in "${GITFLOW_TRANSIENT_PATHS[@]}"; do
+    [ -n "$(git ls-files -- "$p")" ] && tracked+=("$p")
+  done
+  [ "${#tracked[@]}" -gt 0 ] || return 0             # nothing tracked → no-op
+  # only purge paths with no pending changes → git rm is all-or-nothing safe and
+  # never discards uncommitted work under docs/superpowers.
+  if ! git diff --quiet HEAD -- "${tracked[@]}" 2>/dev/null; then
+    echo "gitflow: transient artifacts have uncommitted changes — purge skipped, finishing without it (clean up by hand)" >&2
+    return 0
+  fi
+  if git rm -r -q -- "${tracked[@]}" >/dev/null 2>&1 \
+     && git commit -q -m "chore: purge transient planning artifacts (BDR-065)" -- "${tracked[@]}"; then
+    echo "gitflow: purged transient planning artifacts before merge (${tracked[*]})" >&2
+  else
+    echo "gitflow: transient-artifact purge failed — finishing without it (clean up by hand)" >&2
+    git reset -q HEAD -- "${tracked[@]}" 2>/dev/null || true   # unstage any partial rm
+    git checkout -q -- "${tracked[@]}" 2>/dev/null || true     # restore working tree
+  fi
+  return 0
+}
+
 # gitflow_finish [<type> <name>] → directed merge of the CURRENT branch per its
 # type, then delete. WHEN to call this is the human gate (SKILL.md).
 #
@@ -117,7 +159,10 @@ gitflow_finish() {
   fi
   type="$(gitflow_branch_type "$br")"
   case "$type" in
-    feature|bugfix|chore)
+    feature|bugfix)
+      _gitflow_purge_transient   # BDR-065 auto-cleanup, on HEAD, pre-merge; never blocks
+      _gitflow_merge_into "$GITFLOW_DEVELOP" "$br" && _gitflow_delete "$br" ;;
+    chore)
       _gitflow_merge_into "$GITFLOW_DEVELOP" "$br" && _gitflow_delete "$br" ;;
     release)
       _gitflow_merge_into "$GITFLOW_MAIN" "$br" \
@@ -283,8 +328,9 @@ if [ "${BASH_SOURCE[0]}" = "${0}" ]; then
     finish)         gitflow_finish "$@" ;;
     init)           gitflow_init "$@" ;;
     reconcile)      gitflow_reconcile_gitignore "$@" ;;
+    purge-transient) _gitflow_purge_transient ;;
     install-hook)   gitflow_install_hook "$@" ;;
     emit-hook)      _gitflow_emit_pre_commit ;;
-    *) echo "usage: gitflow.sh {type|protected-base|base-for|release-open|start|finish|init|reconcile|install-hook|emit-hook}" >&2; exit 2 ;;
+    *) echo "usage: gitflow.sh {type|protected-base|base-for|release-open|start|finish|init|reconcile|purge-transient|install-hook|emit-hook}" >&2; exit 2 ;;
   esac
 fi

lib/memory-commit.sh

@@ -19,6 +19,19 @@ set -uo pipefail
 
 MC_PATHS=(".claude/memory" ".claude/tasks")
 
+# bash 3.2 (macOS /bin/bash) predates the `mapfile` builtin; this is the portable
+# equivalent. Reads stdin's lines into the array named by $1, space-safe
+# (IFS= read -r). The array is reset first, so empty input yields an empty array
+# rather than a stale or unset one — `set -u` on bash < 4.4 trips on expanding
+# an array that was never assigned.
+_read_lines_into() {
+  local _name="$1" _line
+  eval "$_name=()"
+  while IFS= read -r _line; do
+    eval "$_name+=(\"\$_line\")"
+  done
+}
+
 _in_git_repo() { git rev-parse --git-dir >/dev/null 2>&1; }
 
 # True (0) when the repo is in a state where we must NOT auto-commit:
@@ -59,7 +72,7 @@ commit_memory() {
     return 3
   fi
   local changed
-  mapfile -t changed < <(_changed_paths)
+  _read_lines_into changed < <(_changed_paths)
   if [ "${#changed[@]}" -eq 0 ]; then
     echo "memory-commit: nothing pending — no-op" >&2
     return 0

lib/model-gate.md

@@ -35,3 +35,13 @@ yet rewritten) — that is why the self-check exists alongside it.
 
 then end the turn. No later step runs, no agent is dispatched, nothing is
 edited.
+
+## 4. Dispatch tiers (BDR-077 — no inherit)
+
+The gate guards the MAIN loop only. Dispatched work NEVER inherits the
+session model: typed agents run on their frontmatter pin; built-ins
+(general-purpose / Explore / Plan) carry an explicit `model=` at every call
+site — `model: "fable"` when the child performs reflection/orchestration on
+the main loop's behalf (skill-runners), otherwise its complexity tier
+(opus = dispatched judgment, sonnet = execution/collection, haiku = short
+mechanical probes).

lib/plugin-gate.md

@@ -0,0 +1,90 @@
+# Plugin gate — shared consumer include (plugin-check, onboard, init-project, ship-feature STEP 0)
+
+Runs in the CONSUMER'S MAIN LOOP. The detection and the reasoning are
+dispatched (BDR-077 tiers); the validation checkpoint, the report
+presentation, and the apply gate live HERE — a dispatched agent can neither
+ask the user nor safely mutate plugin state.
+
+## 1. PROBE (dispatch — sonnet)
+
+```
+Agent(subagent_type="plugin-probe", description="plugin gate — probe",
+      prompt="Run your probes from <PROJECT_ROOT>. Emit the PROBE REPORT.")
+```
+
+## 2. VALIDATION CHECKPOINT (main loop — between probe and reasoner)
+
+Validate the PROBE REPORT before any reasoning:
+- `EXTERNAL` non-empty AND each listed plugin's directory appears under
+  `CHECKPOINT plugin-dirs`.
+- At least one project signal present (MANIFESTS / FRAMEWORK-DEPS /
+  TSX-JSX-COUNT > 0 / DOCKER-COUNT > 0 / EMBEDDED hits). Else print
+  `⚠️ No project signals detected — recommendations will be conservative.`
+  and continue.
+- `CHECKPOINT toggle-script=UNAVAILABLE` → print `⚠️ toggle script
+  unavailable — recommendations will be advisory only, no auto-activation.`
+  and SKIP step 5 (apply) entirely.
+- PROBE REPORT missing/unparsable → retry the probe ONCE fresh; a 2nd
+  failure → STOP and surface (never reason over invented detection).
+
+## 3. REASON (dispatch — opus)
+
+```
+Agent(subagent_type="plugin-advisor", description="plugin gate — reason",
+      prompt="""
+REQUEST: <the user's request / project description, verbatim>
+PROBE REPORT (ground truth — do not re-detect):
+<the full PROBE REPORT from step 1>
+""")
+```
+
+## 4. PRESENT + BLOCKING GATE (main loop)
+
+Show the returned PLUGIN CHECK block.
+- `ACTION REQUIRED? YES` → offer: A) fix plugins B) type "force". STOP until
+  answered.
+- OK → print `✅ Plugin check passed — [active plugins] — complexity: <score>%`.
+
+## 5. APPLY GATE (main loop — only when the flow auto-activates)
+
+If any plugin has ⚡ ENABLE status:
+1. List the changes:
+   ```
+   PROPOSED CHANGES:
+     ⚡ Enable ui-ux-pro-max (frontend detected, complexity 65%)
+     ⚡ Pre-fetch ctx7 docs for next.js, prisma
+   Apply these changes? (yes / no / customize)
+   ```
+2. "yes" → apply via the exact commands the advisor emitted. "customize" →
+   user picks. "no" → proceed with current config.
+
+**Never auto-activate without showing the list and getting confirmation.**
+
+### Rollback on partial failure
+
+Track each toggle; roll back the partial set rather than leave a
+half-applied configuration:
+
+```bash
+applied=()
+for change in "${PROPOSED_CHANGES[@]}"; do
+  if bash "$HOME/.claude/lib/toggle-external.sh" enable "$change"; then
+    applied+=("$change")
+  else
+    echo "❌ failed to enable $change — rolling back ${#applied[@]} prior change(s)"
+    for prior in "${applied[@]}"; do
+      bash "$HOME/.claude/lib/toggle-external.sh" disable "$prior" \
+        || echo "⚠️ rollback of $prior also failed — manual cleanup required: see ~/.claude/plugins/cache"
+    done
+    exit 1
+  fi
+done
+```
+
+Surface: `✅ Applied N change(s).` — or on failure:
+
+```
+⚠️ Toggle failed at change <name>. Rolled back the N prior change(s).
+   To inspect manually: ls ~/.claude/plugins/cache; bash ~/.claude/lib/toggle-external.sh list
+   Re-run /plugin-check after fixing the underlying cause (e.g. permissions).
+```

lib/profile.sh

@@ -14,6 +14,9 @@
 #   - MCPs: delegated to lib/toggle-external.sh for known servers (magic),
 #           advisory otherwise
 #   - CLIs: advisory only (rtk, gsd, ctx7, graphify — installed externally)
+#   - `set` is SYMMETRIC on managed items (BDR-079): plugins, external packs
+#     and MCPs in the MANAGED_* allowlists are disabled when the profile
+#     does not list them — nothing outside those lists is ever auto-toggled.
 #
 # Always-on plugins (never toggled by `set`): security-guidance,
 # superpowers + rtk hook + .claude internal. The script refuses to disable
@@ -61,6 +64,23 @@ MANAGED_PLUGINS=(
   "pr-review-toolkit@claude-code-plugins"
 )
 
+# External skill packs that are toggle-managed by `set` — same allowlist
+# doctrine as MANAGED_PLUGINS: listed here only when the enabled state is
+# task-type-driven. `set` disables these when the profile does not list
+# them; anything else external (e.g. darwin-skill) is never auto-touched.
+MANAGED_EXTERNALS=(
+  emil-design-eng
+  frontend-design
+  design-motion-principles
+  impeccable
+)
+
+# MCP servers that are toggle-managed by `set`, both ways (enable AND
+# disable), delegated to lib/toggle-external.sh. Same allowlist doctrine.
+MANAGED_MCPS=(
+  magic
+)
+
 # Plugins that MUST stay enabled — `set` will refuse to disable these even if
 # they're not in the profile. (Defensive: belt-and-suspenders alongside
 # MANAGED_PLUGINS allowlist.)
@@ -271,6 +291,11 @@ enable_skill() {
         ok "enabled: $skill ($type)"
       elif [ -e "$SKILLS_DIR/$skill" ]; then
         :
+      elif [ "$type" = external ] && [ -d "$REPO/skills-external/$skill" ]; then
+        # Symlink never created (or hand-removed): recreate it from the
+        # vendored pack — mirrors toggle-external.sh's from-source path.
+        ln -sf "$REPO/skills-external/$skill" "$SKILLS_DIR/$skill"
+        ok "enabled: $skill (external, symlink created)"
       else
         warn "missing: $skill ($type)"
       fi
@@ -422,6 +447,48 @@ parked_gstack_count() {
   find "$DISABLED_DIR" -maxdepth 1 -name 'gstack__*' 2>/dev/null | wc -l | tr -d ' '
 }
 
+# ── `set` trim helpers — one per managed category ─────────────
+# Each disables the managed items NOT listed in the given profile. Allowlist
+# doctrine: only MANAGED_* entries are ever auto-disabled.
+
+disable_plugins_not_in() {
+  local prof="$1" keep_file p plugin_name marketplace
+  keep_file="$(mktemp)"
+  read_profile "$prof" \
+    | awk -F'\t' '$2 ~ /^plugin@/ { sub(/^plugin@/, "", $2); print $1"@"$2 }' \
+    | sort -u > "$keep_file"
+  for p in "${MANAGED_PLUGINS[@]}"; do
+    if ! grep -qx "$p" "$keep_file"; then
+      plugin_name="${p%@*}"
+      marketplace="${p#*@}"
+      disable_skill "$plugin_name" "plugin@${marketplace}"
+    fi
+  done
+  rm -f "$keep_file"
+}
+
+disable_externals_not_in() {
+  local prof="$1" keep_file x
+  keep_file="$(mktemp)"
+  read_profile "$prof" | awk -F'\t' '$2 == "external" { print $1 }' \
+    | sort -u > "$keep_file"
+  for x in "${MANAGED_EXTERNALS[@]}"; do
+    grep -qx "$x" "$keep_file" || disable_skill "$x" external
+  done
+  rm -f "$keep_file"
+}
+
+disable_mcps_not_in() {
+  local prof="$1" keep_file s
+  keep_file="$(mktemp)"
+  read_profile "$prof" | awk -F'\t' '$2 == "mcp" { print $1 }' \
+    | sort -u > "$keep_file"
+  for s in "${MANAGED_MCPS[@]}"; do
+    grep -qx "$s" "$keep_file" || disable_skill "$s" mcp
+  done
+  rm -f "$keep_file"
+}
+
 # ── Commands ──────────────────────────────────────────────
 
 cmd_list() {
@@ -506,24 +573,20 @@ cmd_apply() {
 
 cmd_set() {
   local prof="$1"
-  info "Setting profile: $prof (exclusive — disables non-listed gstack skills + managed plugins)"
+  info "Setting profile: $prof (exclusive — disables non-listed gstack skills + managed plugins/externals/MCPs)"
 
   # Disable gstack-origin skills not in profile.
   disable_gstack_not_in "$prof"
 
   # Disable managed plugins not in profile (PROTECTED_PLUGINS are excluded
   # by disable_skill itself — belt and suspenders).
-  local plugin_keep_file p plugin_name marketplace
-  plugin_keep_file="$(mktemp)"
-  read_profile "$prof" | awk -F'\t' '$2 ~ /^plugin@/ { sub(/^plugin@/, "", $2); print $1"@"$2 }' | sort -u > "$plugin_keep_file"
-  for p in "${MANAGED_PLUGINS[@]}"; do
-    if ! grep -qx "$p" "$plugin_keep_file"; then
-      plugin_name="${p%@*}"
-      marketplace="${p#*@}"
-      disable_skill "$plugin_name" "plugin@${marketplace}"
-    fi
-  done
-  rm -f "$plugin_keep_file"
+  disable_plugins_not_in "$prof"
+
+  # Symmetry (BDR-079): a profile switch also parks the managed external
+  # packs and unregisters the managed MCPs the new profile does not need —
+  # design leftovers (emil, magic…) no longer survive a `set backend`.
+  disable_externals_not_in "$prof"
+  disable_mcps_not_in "$prof"
 
   # Enable everything listed in the profile.
   cmd_apply "$prof"
@@ -679,9 +742,11 @@ EXAMPLES:
   bash lib/profile.sh reset            # restore everything
 
 NOTE:
-  Plugin and MCP entries print advisory commands — they are NOT toggled
-  automatically. Run "claude plugin enable|disable" or "claude mcp add|remove"
-  yourself for those.
+  "set" toggles the MANAGED items automatically, both ways: plugins
+  (ui-ux-pro-max, plugin-dev, pr-review-toolkit), external packs
+  (emil-design-eng, frontend-design, design-motion-principles, impeccable)
+  and the magic MCP. Anything outside those allowlists stays advisory —
+  run "claude plugin enable|disable" or "claude mcp add|remove" yourself.
 EOF
 }
 

lib/seo-data/README.md

@@ -80,9 +80,247 @@ fetch.sh queries --account client-a --property sc-domain:ex.com [--days 90] [--d
   → {"status":"degraded","reason":"no_credentials"|"token_revoked"|"network_error"|"rate_limited"}
 
 fetch.sh inspect --account client-a --property … --url https://ex.com/page
-  → {"status":"ok","source":"gsc","indexed":true,"coverage":"…","last_crawl":"…"}
+  → {"status":"ok","source":"gsc","indexed":true,"coverage":"…","last_crawl":"…",
+     "rich_results":{"verdict":"PASS|FAIL|NEUTRAL|VERDICT_UNSPECIFIED|ABSENT",
+                     "types":[{"type":"FAQ","items":2,"errors":2,"warnings":1,
+                               "issues":["Missing field 'acceptedAnswer'"]}]}}
   → {"status":"degraded","reason":"…"}
 
+  rich_results rides the SAME URL-Inspection response — Google already sends
+  it, `inspect` used to discard it. No extra call, quota or OAuth scope.
+  It is the only programmatic structured-data validation in the system.
+    • verdict PARTIAL is never emitted — the API reserves it as unused.
+    • verdict ABSENT is SYNTHETIC (not a Google enum): the API omits
+      richResultsResult entirely when it detects no rich results. Surfaced
+      as a value rather than a missing key, because a caller cannot tell an
+      absent key apart from a check that never ran. ABSENT = "none
+      detected", never "invalid".
+    • errors/warnings count issue INSTANCES; issues[] is deduped — the same
+      issueMessage repeats across every affected item.
+
+fetch.sh cannibal --account client-a --property … [--days 90] [--rows 1000]
+  → {"status":"ok","source":"gsc","days":90,"rows_scanned":1000,"capped":true,
+     "conflict_count":12,
+     "conflicts":[{"query":"plombier paris","pages":3,"total_impressions":2400,
+                   "urls":[{"url":…,"clicks":…,"impressions":…,"position":…}]}]}
+  → {"status":"degraded","reason":"…"}                # no account → NOT auditable
+
+  Keyword cannibalisation from Google's own data: queries where 2+ of OUR
+  pages compete. Groups query+page rows; conflicts ranked by total
+  impressions, and within each the strongest page first. `capped:true` means
+  the row window was full — more conflicts exist past the cut, say so.
+  Same auth, same quota family, no new scope: the API always accepted several
+  dimensions at once, this engine only ever asked for one.
+    • NOT the 30/70 duplication rule. This is a SERP fact Google measured.
+      30/70 is content similarity, which has no data source here — doing it
+      naively (compare two same-template pages without stripping nav/footer)
+      returns ~95% similar for every site, a confident false positive. It stays
+      an LLM judgement, labelled as one.
+    • `queries` now takes `--dim query,page` (comma-separated) and `--rows`.
+      Rows gained a `keys` list; `key` stays as keys[0], so the single-dim
+      consumer is untouched.
+
+safe_fetch.py — NOT a verb; the SSRF/DNS-rebinding-safe fetcher behind
+  sitemap._fetch, so every network verb (sitemap, linkgraph, rendercheck,
+  drift) inherits it. urlopen resolved then connected — two DNS lookups, a
+  window a hostile authority uses to answer PUBLIC to validation and PRIVATE
+  (169.254.169.254 metadata, 127.0.0.1, the LAN) to the connect. This resolves
+  ONCE, validates every IP (ipaddress, dual-stack v4+v6), refuses if ANY is
+  non-public (the multi-A vector), and connects to the exact validated IP with
+  Host+SNI+cert for the real host — no second resolution to poison. Redirects
+  are followed with each hop RE-VALIDATED (urlopen followed them blind).
+    • Better than the source idea (claude-seo url_safety.py, MIT): dual-stack
+      (theirs IPv4-only), no global monkeypatch so thread-safe by construction
+      (theirs locks a patched socket.getaddrinfo), stdlib-only (no requests).
+    • Refusal raises UnsafeTarget; callers already degrade → fail-open kept.
+    • NOT covered, and said so: the shell `curl` in the agent specs runs in
+      another process, unpinnable from here. Smaller surface (fixed set vs an
+      operator-confirmed $DOMAIN); `curl --resolve` would close it, separate change.
+
+fetch.sh sitemap --url https://ex.com/sitemap.xml
+  → {"status":"ok","source":"sitemap","index":false,"count":86,"dropped":0,
+     "urls":["https://ex.com/", …]}
+  → {"status":"ok","index":true,"children_total":4,"children_read":4,
+     "children_failed":0,"count":312,…}          # <sitemapindex>, one level deep
+  → {"status":"degraded","reason":"fetch_failed"|"parse_failed"|"no_urls"
+                                  |"unsafe_xml_dtd"}
+
+  No auth, no Google, no venv: stdlib only (urllib + xml.etree + gzip).
+  Gives STEP 9's COVERAGE line the denominator it was told to print and never
+  had, and STEP 5 a real sampling frame. Dedupes, strips whitespace, handles
+  .xml.gz. Caps: 50 children of an index, 50k URLs, 20 MB read — each cut is
+  REPORTED (children_skipped / truncated), never silent.
+
+    • NOT a security boundary. urllib fetches these, so nothing here reaches a
+      shell. The CONSUMER interpolates them into curl, so seo-analyzer runs
+      lib/url-guard.sh at the point of use — same contract as the sameAs check.
+      A second copy of the guard here would only drift.
+    • `unsafe_xml_dtd`: a sitemap NEVER has a DTD (sitemaps.org is <?xml?> then
+      <urlset xmlns=>). Any doctype/entity is refused BEFORE parsing. xml.etree
+      does not expand external entities, but it IS billion-laughs-vulnerable —
+      1 KB expands to gigabytes, and the 20 MB read ceiling bounds the input,
+      not the expansion. Refusing the construct beats depending on parser
+      internals AND keeps this stdlib-only; defusedxml would drag in a venv for
+      a document type that has no legitimate DTD.
+
+fetch.sh rendercheck --url https://ex.com/
+  → {"status":"ok","verdict":"server-rendered"|"client-rendered"|"partial",
+     "body_text_chars":7650,"h1_in_html":1,"jsonld_in_html":9,
+     "meta_description_in_html":true,"html_bytes":132447,
+     "warning":"…"}                       # warning only when not server-rendered
+
+  R2, the honest half of the SPA call. seo-analyzer has always recorded
+  `RENDERING: SSR/SSG/SPA` and never acted on it; this is the signal it acts
+  on. Verdict comes from what the server SENT — package.json cannot tell a
+  React SPA from a Next.js SSR app.
+    • client-rendered → the agent REFUSES to score On-page (N/A, not zero: a
+      zero says "your on-page is bad", N/A says "we could not see it"). Every
+      curl-based meta/H1/JSON-LD check would report "missing" against a site
+      that is fine once hydrated — false findings, and a bundle that "fixes"
+      tags which already exist.
+    • Does NOT render JS. No Playwright, no Chromium, no venv. Refusing IS the
+      finding.
+    • Script/style text is not page text: measured 7 chars on a React shell
+      whose inline window.__INITIAL_STATE__ is large. Without that, a 200 KB
+      bundle reads as a rich page.
+    • Measured 2026-07-17: zenquality 7650 chars/1 h1/9 jsonld and
+      lavageangels356 13973/1/1 → server-rendered; a Vite shell → 7/0/0.
+
+fetch.sh linkgraph --url https://ex.com/sitemap.xml [--max 500]
+  → {"status":"ok","source":"linkgraph","pages_crawled":86,"pages_failed":0,
+     "total_internal_links":2015,"capped":false,"max_depth":2,
+     "orphans":[…],"beyond_3_clicks":[…],"unreachable":[…]}
+  → {"status":"ok",…,"orphans_withheld":true,"reason_withheld":"crawl incomplete…"}
+  → {"status":"degraded","reason":"no_links_in_html"|"no_pages_fetched"|…}
+
+  Answers seo-analyzer.md:613 ("reachable within 3 clicks?") and :616 ("orphan
+  pages?") — asked since forever, never computed. Stdlib only (urllib +
+  html.parser + urljoin), no auth. Measured: 24 pages in 2.7s, 86 in 3.8s.
+    • EXHAUSTIVE OR NOTHING. Orphans cannot be sampled: proving no inbound
+      link means having read every other page. If the crawl is capped or any
+      page failed, orphans are WITHHELD, never truncated — a false orphan
+      sends a client fixing what is not broken.
+    • no_links_in_html = a JS-rendered site, not a link-less one. Every page
+      would read as orphaned, so it REFUSES rather than report that. Does not
+      render JS by design (see the R1/R2 arbitration).
+    • Filters what a link graph must never hold: assets (seen live:
+      /css/main.css?v=1778157313), #anchors, mailto:/tel:/javascript:, other
+      hosts. Normalises the trailing slash so /blog and /blog/ are one node
+      rather than a phantom orphan pair.
+    • Mock is pages.json ({url: html}), not a single page.html: one fixture
+      cannot express a graph — every node would carry identical links.
+
+fetch.sh score --findings <path.json | ->
+  → {"status":"ok","axes":{"technical":{"score_20":17.8,"weight":0.2,
+       "weight_renormalised":0.2857,"findings":2}},
+     "na":["off-page","on-page"],"weights_renormalised":true,"global_20":17.6}
+  → {"status":"error","reason":"unknown severity: 'bogus'"|"bad_findings_json"}
+
+  I7. /harden has a real scale (SKILL.md:435: -15/-8/-3/-1, clamp [0,100]);
+  /seo had none, so every axis was FELT and two runs over identical code could
+  disagree — while /client-handover gates on 17/20. Same scale here, /5 into
+  /20, one vocabulary across the family.
+    • The split: WHICH findings exist and how severe each is stays the LLM's
+      judgement. The addition is not. Same findings in, same score out.
+    • affected/sampled shift severity ONE step: >=50% of the sample escalates,
+      a single page de-escalates. A defect on 1 of 12 pages is not the defect
+      on 12 of 12.
+    • status:"na" → axis EXCLUDED, remaining weights renormalised. This is
+      R2's rule (client-rendered on-page) and I1's (unauditable off-page),
+      computed rather than done by hand. N/A is not a zero, and the engine
+      will not let it act like one.
+    • Malformed input is an error, never a silently wrong number — unlike the
+      fetch verbs, a degrade here would mean bad input, not a network fact.
+
+fetch.sh schema_gen <reservation|order|discussion|profile> [flags] [--script-tag]
+  → {"status":"ok","source":"schema_gen","type":"<@type>","jsonld":{…}}
+  → {"status":"error","reason":"bad_usage"}          # a REQUIRED flag omitted
+  → {"status":"degraded","reason":"…"}               # a required flag given, empty
+
+  fetch.sh schema_gen reservation --provider "Marea NYC" \
+    --start 2026-06-04T19:30:00-04:00 --party-size 4
+  fetch.sh schema_gen order --merchant "Acme Pizza" --order-url https://acme.example/order
+  fetch.sh schema_gen discussion --headline "…" --author "Sara Park" \
+    --url https://forum.example.com/t/123 --date 2026-05-12T14:00:00Z
+  fetch.sh schema_gen profile --name "Daniel Agrici" --url https://agricidaniel.com/about \
+    --same-as https://github.com/AgriciDaniel --knows-about "SEO" "Schema markup"
+
+  Adapted from claude-seo's `schema_generate.py` (MIT) into this contract.
+  Our system only AUDITS existing markup elsewhere; this is the one verb
+  that GENERATES it — deterministic JSON-LD skeletons for the four v2
+  high-leverage Schema.org types, so geo-analyzer's G2 batch stops
+  hand-writing markup by hand. It only generates STRUCTURE: unknown field
+  VALUES are the caller's job, `[À COMPLÉTER]` for anything unconfirmed —
+  this verb never invents a sameAs, an email, or a business name.
+    • Stdlib only, no network, no auth — runs even without the venv.
+    • `--script-tag` wraps the cleaned jsonld in
+      `<script type="application/ld+json">…</script>` under a `script` key,
+      still inside the `ok` envelope. It must be given AFTER the type
+      (`schema_gen reservation … --script-tag`, not before) — argparse
+      subcommand flags only parse after their subcommand.
+    • Never emits a JSON `null`: fields left unset are omitted from the
+      `jsonld` object entirely rather than serialised as `null`.
+    • A REQUIRED flag omitted → `{"status":"error","reason":"bad_usage"}`,
+      exit 2 (bad usage, like every other verb). A required flag GIVEN but
+      empty (argparse cannot catch that) → `{"status":"degraded",...}`,
+      exit 0 — fail-open, never a traceback.
+
+fetch.sh content_quality [--file <path.txt>] < text_on_stdin
+  → {"status":"ok","source":"content_quality","filler_score":0,"ai_pattern_score":0,
+     "information_density":1.0,"overall_quality":90,"flags":[],
+     "matches":{"filler":[],"ai_patterns":[]}}
+  → {"status":"degraded","reason":"empty_input"|"<file error>"}
+
+  fetch.sh content_quality --file article.txt
+  printf '%s' "$BODY_TEXT" | fetch.sh content_quality
+
+  Adapted from claude-seo's `content_quality.py` (MIT) into this contract.
+  100% deterministic — regex/word-lists (QRG §4.6 filler phrases + a
+  Wikipedia "AI Cleanup" catalogue of LLM-typical phrasings, CC BY-SA 4.0),
+  no LLM call, no network. Reads the text to score from `--file <path>` or,
+  when `--file` is `-` or omitted, from stdin — the same idiom `score.py`
+  uses for `--findings`.
+    • **ADVISORY, NOT A VERDICT.** The output never claims "this text is
+      AI-written" — modern generative tools can pass every heuristic here,
+      and human writers use some of these phrases too. `flags` are
+      candidates for HUMAN REVIEW, never an automatic finding. geo-analyzer
+      STEP 8 (Content Shape for AI) treats `overall_quality`/`flags` as ONE
+      measured input that INFORMS the axis; the axis itself stays an LLM
+      judgement (30/70, Definition Lead), never replaced by this score.
+    • `filler_score`/`ai_pattern_score` (0-100, higher = worse) count
+      phrase-list hits scaled per 1000 tokens; `information_density`
+      (0.0-1.0) is entities + numbers per 100 tokens; `overall_quality`
+      (0-100, higher is better) is the weighted composite (also folds in a
+      bigram-repetition penalty even though that score isn't itself a
+      top-level field). `flags` fires at fixed thresholds: `filler`,
+      `ai-patterns`, `low-density`, `repetitive`.
+    • Stdlib only (argparse/json/re/sys/collections/typing) — runs even
+      without the venv. Empty/whitespace-only input degrades rather than
+      returning a false zero-value "ok": an empty analysis is not a result.
+    • This is filler/AI-pattern SHAPE, not fact-checking — a text can be
+      dense and well-cited yet still wrong; that stays a human/LLM call.
+
+fetch.sh drift --url https://ex.com/sitemap.xml [--max 500]
+  → {"status":"ok","baseline":true,"captured":"…","pages":24,"store":"…"}
+  → {"status":"ok","baseline":false,"since":"…","gone":[…],"new":[…],
+     "regressions":[{"url":…,"field":"canonical","was":"…","now":null}],
+     "changes":[{"url":…,"field":"title","was":"…","now":"…"}]}
+
+  On-page drift between audits. seo-analyzer.md:1365 keeps only "date + score
+  + key changes" as PROSE the LLM writes about its own previous prose: lossy,
+  unreproducible, machine-uncomparable. So "the redesign silently dropped 40
+  canonicals" stays invisible. This snapshots title/description/canonical/
+  robots/h1_count/jsonld_types per URL and diffs them.
+    • NOT rank tracking (the common misread of this feature elsewhere).
+      Positions come from GSC `queries`. This is regression detection.
+    • Runs over the WHOLE sitemap, never a sample: a drift over a sample that
+      changes between runs compares nothing.
+    • LOSING a signal = regression. CHANGING one = change, possibly intended —
+      the agent judges that, the engine only says which kind it is.
+    • Store: ~/.claude/seo-data/drift/<host>.json, 0700, written via
+      os.replace — never a half-written baseline. Corrupt store → treated as
+      a first run rather than crashing the audit.
+
 fetch.sh forget --label client-a
   → {"status":"ok","removed":true|false}          # false = label wasn't in the store
 

lib/seo-data/content_quality.py

@@ -0,0 +1,242 @@
+#!/usr/bin/env python3
+"""Deterministic filler / AI-slop content-quality scorer. Stdlib only.
+
+Adapted from claude-seo (github.com/AgriciDaniel/claude-seo, MIT),
+content_quality.py — rewritten to the lib/seo-data fail-open contract.
+
+Scores a block of text against three regex/word-list heuristics: padding
+"filler" phrases (QRG §4.6), LLM-typical phrasings ("AI-pattern" list),
+and a measured information density (entities + numbers per token). 100%
+deterministic — no LLM call, no network.
+
+ADVISORY, NOT A VERDICT. This never claims "this text is AI-written" —
+modern generative tools can pass every heuristic here, and human writers
+use some of these phrases too. A low overall_quality or a filler/
+ai-patterns flag is a candidate for human review, nothing more. In
+geo-analyzer's STEP 8 (Content Shape for AI) it is ONE measured input
+that INFORMS the axis, which stays an LLM judgement (30/70, Definition
+Lead) — never a replacement for it, and never auto-filed as a finding on
+its own.
+
+Attribution: the AI-pattern list draws from the Wikipedia "AI Cleanup"
+project's catalogue of LLM-typical phrasings (CC BY-SA 4.0), the same
+list claude-seo cites.
+
+Envelope (see `_cli`)::
+
+    {"status": "ok", "source": "content_quality",
+     "filler_score": 0..100,        # higher = more filler-like
+     "ai_pattern_score": 0..100,    # higher = more AI-pattern hits
+     "information_density": 0.0..1.0,
+     "overall_quality": 0..100,     # composite, higher is better
+     "flags": ["filler", "ai-patterns", "low-density", "repetitive"],
+     "matches": {"filler": [...], "ai_patterns": [...]}}
+    {"status": "degraded", "reason": "empty_input" | "<why>"}
+"""
+import argparse, json, re, sys
+from collections import Counter
+from typing import Iterable
+
+# Padding / filler phrases QRG §4.6 flags as "little-to-no value". The
+# lists are the value of this module — kept intact from the source, not
+# trimmed.
+_FILLER_PHRASES = (
+    "it's important to note that",
+    "in this article, we'll explore",
+    "in this article we will explore",
+    "in today's fast-paced world",
+    "in today's digital age",
+    "in today's competitive landscape",
+    "needless to say",
+    "at the end of the day",
+    "when it comes to",
+    "when all is said and done",
+    "in the realm of",
+    "in the world of",
+    "the bottom line is",
+    "without further ado",
+    "first and foremost",
+    "last but not least",
+    "for what it's worth",
+    "it goes without saying",
+    "as we all know",
+    "the truth is that",
+    "the fact of the matter is",
+    "more often than not",
+    "let's dive in",
+    "let's dive into",
+    "let's take a closer look",
+    "let's take a deeper look",
+)
+
+# LLM-typical phrasings (Wikipedia AI Cleanup catalogue, CC BY-SA 4.0;
+# also used by claude-seo, MIT). Conservative: only phrases that
+# disproportionately appear in LLM output. Adding to this list should
+# require corpus evidence, not intuition.
+_AI_PATTERNS = (
+    "delve into",
+    "delve deeper into",
+    "in the ever-evolving",
+    "ever-evolving landscape",
+    "ever-changing landscape",
+    "in the dynamic landscape",
+    "navigating the",
+    "navigate the complexities",
+    "tapestry of",
+    "rich tapestry",
+    "intricate tapestry",
+    "embark on a journey",
+    "embarking on this",
+    "a testament to",
+    "a beacon of",
+    "the cornerstone of",
+    "a cornerstone of",
+    "at the heart of",
+    "at its core",
+    "in essence,",
+    "in conclusion,",
+    "ultimately,",
+    "moreover,",
+    "furthermore,",
+    "however, it's worth noting",
+    "it's worth noting that",
+    "by leveraging",
+    "leverage the power of",
+    "leveraging the power of",
+    "harness the power of",
+    "unlock the potential",
+    "unlock the full potential",
+    "the realm of possibilities",
+    "open up a world of",
+    "a world of possibilities",
+    "elevate your",
+    "transform your",
+    "revolutionize the way",
+    "game-changer",
+    "game-changing",
+    "cutting-edge",
+    "state-of-the-art",
+    "in summary,",
+    "to summarize,",
+    "to put it simply,",
+    "in a nutshell,",
+)
+
+_TOKEN_RE = re.compile(r"[A-Za-z][A-Za-z'\-]*")
+_NUMBER_RE = re.compile(r"\b\d+(?:[.,]\d+)?(?:%|st|nd|rd|th)?\b")
+# Capitalised multi-word names: rough proper-noun heuristic. Two or more
+# capitalised tokens in a row count as one entity.
+_ENTITY_RE = re.compile(r"\b(?:[A-Z][a-z]+(?:\s+[A-Z][a-z]+)+)\b")
+
+
+def _count_phrase_hits(text: str, patterns: Iterable[str]) -> list:
+    """Patterns that appear at least once in text (case-insensitive)."""
+    lowered = text.lower()
+    return [p for p in patterns if p in lowered]
+
+
+def _repetition_score(tokens):
+    """Bigram repetition: fraction of bigrams that recur more than once."""
+    if len(tokens) < 4:
+        return 0.0
+    bigrams = [tokens[i] + " " + tokens[i + 1] for i in range(len(tokens) - 1)]
+    counts = Counter(bigrams)
+    repeated = sum(1 for v in counts.values() if v > 1)
+    return repeated / max(1, len(counts))
+
+
+def analyse(text):
+    """Score text against the filler / AI-pattern / density / repetition
+    heuristics. Advisory only — see module docstring."""
+    tokens = [t.lower() for t in _TOKEN_RE.findall(text)]
+    n_tokens = len(tokens)
+
+    filler_hits = _count_phrase_hits(text, _FILLER_PHRASES)
+    ai_hits = _count_phrase_hits(text, _AI_PATTERNS)
+
+    # Density: entities + numbers per 100 tokens. A high-density article
+    # (case studies, data journalism) lands at ~5+; generic filler <2.
+    entities = len(_ENTITY_RE.findall(text))
+    numbers = len(_NUMBER_RE.findall(text))
+    density_per_100 = (entities + numbers) * 100.0 / max(1, n_tokens)
+    information_density = min(1.0, density_per_100 / 10.0)
+
+    rep_score = int(round(_repetition_score(tokens) * 100))
+
+    # Scale to per-1000 tokens so the score is comparable across lengths.
+    scale = max(1.0, n_tokens / 1000.0)
+    filler_score = min(100, int(round(len(filler_hits) / scale * 25)))
+    ai_pattern_score = min(100, int(round(len(ai_hits) / scale * 15)))
+
+    flags = []
+    if filler_score >= 50:
+        flags.append("filler")
+    if ai_pattern_score >= 40:
+        flags.append("ai-patterns")
+    if information_density < 0.20:
+        flags.append("low-density")
+    if rep_score >= 30:
+        flags.append("repetitive")
+
+    # Composite: invert penalty signals, weight by impact. Same weights
+    # as the source — the length bonus caps at 1000 tokens.
+    overall = (
+        (100 - filler_score) * 0.25
+        + (100 - ai_pattern_score) * 0.25
+        + information_density * 100 * 0.25
+        + (100 - rep_score) * 0.15
+        + min(100, n_tokens / 10.0) * 0.10
+    )
+
+    return {
+        "filler_score": filler_score,
+        "ai_pattern_score": ai_pattern_score,
+        "information_density": round(information_density, 3),
+        "overall_quality": int(round(overall)),
+        "flags": flags,
+        "matches": {"filler": filler_hits, "ai_patterns": ai_hits},
+    }
+
+
+def _build_parser():
+    p = argparse.ArgumentParser(
+        description="Deterministic filler / AI-slop content-quality scorer."
+    )
+    p.add_argument("--store", default=None)   # accepted+ignored (dispatch)
+    p.add_argument(
+        "--file", default="-",
+        help="Path to a text file, or - for stdin (default -).",
+    )
+    return p
+
+
+def _read_input(path):
+    """Read the analysis target from stdin ('-'/omitted) or a plain file.
+    Plain `open()` only — no pathlib, to stay stdlib-minimal per contract."""
+    if path in (None, "-"):
+        return sys.stdin.read()
+    return open(path, encoding="utf-8", errors="replace").read()
+
+
+def _cli():
+    try:
+        args = _build_parser().parse_args()
+        text = _read_input(args.file)
+        if not text or not text.strip():
+            print(json.dumps({"status": "degraded", "reason": "empty_input"}))
+            return
+        envelope = {"status": "ok", "source": "content_quality"}
+        envelope.update(analyse(text))
+        print(json.dumps(envelope, indent=2))
+    except SystemExit as e:
+        if e.code not in (0, None):
+            print(json.dumps({"status": "error", "reason": "bad_usage"}))
+        raise
+    except Exception as e:
+        # Fail-open: a missing --file, an unreadable/binary file, or any
+        # other unexpected error degrades rather than crashing the caller.
+        print(json.dumps({"status": "degraded", "reason": str(e)}))
+
+
+if __name__ == "__main__":
+    _cli()

lib/seo-data/drift.py

@@ -0,0 +1,184 @@
+#!/usr/bin/env python3
+"""On-page drift between audits. Stdlib only.
+
+seo-analyzer.md:1365 says "on re-run, move current content to Historique
+(summary: date + score + key changes)". That is prose the LLM writes about its
+own previous prose: lossy, unreproducible, and machine-uncomparable. So "the
+redesign silently dropped 40 canonicals" is invisible unless someone happens
+to notice.
+
+This snapshots the machine-readable signals per URL and diffs them.
+
+NOT rank tracking — a common misread of the same feature elsewhere. Positions
+come from GSC (`queries`). This is on-page regression detection: what the site
+said last time vs now.
+
+Runs over the WHOLE sitemap, never a sample: a drift over a sample that
+changes between runs compares nothing.
+"""
+import argparse, json, os, re, time
+from html.parser import HTMLParser
+
+import sitemap as sm
+
+STORE_DIR = os.path.expanduser("~/.claude/seo-data/drift")
+MAX_PAGES = 500
+# Losing a signal is a regression. Changing one may be intentional — the agent
+# judges that, we only report which kind it is.
+TRACKED = ("title", "description", "canonical", "robots", "h1_count", "jsonld_types")
+
+class _Signals(HTMLParser):
+    def __init__(self):
+        super().__init__(convert_charrefs=True)
+        self.title, self.description, self.canonical, self.robots = None, None, None, None
+        self.h1_count, self.jsonld_types = 0, []
+        self._in_title, self._in_ld = False, False
+
+    def handle_starttag(self, tag, attrs):
+        a = dict(attrs)
+        if tag == "title":
+            self._in_title = True
+        elif tag == "h1":
+            self.h1_count += 1
+        elif tag == "meta":
+            n = (a.get("name") or "").lower()
+            if n == "description":
+                self.description = (a.get("content") or "").strip() or None
+            elif n == "robots":
+                self.robots = (a.get("content") or "").strip() or None
+        elif tag == "link" and "canonical" in (a.get("rel") or "").lower():
+            self.canonical = (a.get("href") or "").strip() or None
+        elif tag == "script" and a.get("type") == "application/ld+json":
+            self._in_ld = True
+
+    def handle_endtag(self, tag):
+        if tag == "title":
+            self._in_title = False
+        elif tag == "script":
+            self._in_ld = False
+
+    def handle_data(self, data):
+        if self._in_title and data.strip():
+            self.title = re.sub(r"\s+", " ", data.strip())
+        elif self._in_ld:
+            self.jsonld_types.extend(re.findall(r'"@type"\s*:\s*"([^"]+)"', data))
+
+def _signals(html):
+    p = _Signals()
+    try:
+        p.feed(html)
+    except Exception:
+        pass
+    return {"title": p.title, "description": p.description,
+            "canonical": p.canonical, "robots": p.robots,
+            "h1_count": p.h1_count, "jsonld_types": sorted(set(p.jsonld_types))}
+
+def _mock_pages():
+    """{url: html}, same convention as linkgraph: a single page.html fixture
+    cannot express a multi-page snapshot — every URL would look identical."""
+    raw = sm._mock("pages.json")
+    return json.loads(raw.decode("utf-8")) if raw else None
+
+def _capture(urls):
+    pages = _mock_pages()
+    snap, failed = {}, 0
+    for u in urls:
+        if pages is not None:
+            html = pages.get(u)
+            if html is None:
+                failed += 1
+                continue
+        else:
+            try:
+                html = sm._fetch(u).decode("utf-8", "replace")
+            except Exception:
+                failed += 1
+                continue
+        snap[u] = _signals(html)
+    return snap, failed
+
+def _store_path(sitemap_url):
+    from urllib.parse import urlparse
+    host = urlparse(sitemap_url).netloc.lower()
+    safe = re.sub(r"[^a-z0-9.-]", "_", host) or "unknown"
+    return os.path.join(STORE_DIR, safe + ".json")
+
+def _load(path):
+    if not os.path.exists(path):
+        return None
+    try:
+        with open(path, encoding="utf-8") as f:
+            return json.load(f)
+    except Exception:
+        return None                        # corrupt store -> treat as first run
+
+def _save(path, snap, stamp):
+    os.makedirs(os.path.dirname(path), mode=0o700, exist_ok=True)
+    tmp = path + ".tmp"
+    with open(tmp, "w", encoding="utf-8") as f:
+        json.dump({"captured": stamp, "pages": snap}, f)
+    os.replace(tmp, path)                  # atomic: never a half-written baseline
+
+def _classify(old, new):
+    """LOST a signal = regression. Changed it = change. Only the first is
+    unambiguous; the agent judges the rest."""
+    regressions, changes = [], []
+    for f in TRACKED:
+        o, n = old.get(f), new.get(f)
+        if o == n:
+            continue
+        row = {"field": f, "was": o, "now": n}
+        # Covers every tracked field uniformly: "Titre" -> None, 1 -> 0,
+        # ["Article"] -> []. Had the value, lost the value.
+        (regressions if (o and not n) else changes).append(row)
+    return regressions, changes
+
+def drift(sitemap_url, max_pages=MAX_PAGES):
+    sm_res = sm.sitemap(sitemap_url)
+    if sm_res.get("status") != "ok":
+        return sm_res
+    urls = sm_res["urls"][:max_pages]
+    snap, failed = _capture(urls)
+    if not snap:
+        return {"status": "degraded", "reason": "no_pages_fetched"}
+    stamp = time.strftime("%Y-%m-%dT%H:%M:%SZ", time.gmtime())
+    path = _store_path(sitemap_url)
+    prev = _load(path)
+    _save(path, snap, stamp)
+    if prev is None:
+        return {"status": "ok", "baseline": True, "captured": stamp,
+                "pages": len(snap), "pages_failed": failed, "store": path}
+    old = prev.get("pages", {})
+    regressions, changes = [], []
+    for u, new in snap.items():
+        if u not in old:
+            continue
+        r, c = _classify(old[u], new)
+        for row in r:
+            regressions.append(dict(row, url=u))
+        for row in c:
+            changes.append(dict(row, url=u))
+    return {"status": "ok", "baseline": False,
+            "since": prev.get("captured"), "captured": stamp,
+            "pages": len(snap), "pages_failed": failed,
+            "gone": sorted(set(old) - set(snap)),
+            "new": sorted(set(snap) - set(old)),
+            "regressions": regressions, "changes": changes, "store": path}
+
+def _cli():
+    try:
+        p = argparse.ArgumentParser()
+        p.add_argument("--url", required=True, help="sitemap URL")
+        p.add_argument("--max", type=int, default=MAX_PAGES)
+        p.add_argument("--store", default=None)   # accepted+ignored
+        args = p.parse_args()
+        print(json.dumps(drift(args.url, args.max), indent=2))
+    except SystemExit as e:
+        if e.code not in (0, None):
+            print(json.dumps({"status": "error", "reason": "bad_usage"}))
+        raise
+    except Exception:
+        print(json.dumps({"status": "degraded", "reason": "unexpected_error"}))
+
+if __name__ == "__main__":
+    _cli()

lib/seo-data/fetch.sh

@@ -27,8 +27,23 @@ _label_safe() ( LC_ALL=C; case "$1" in ''|[!A-Za-z0-9]*|*[!A-Za-z0-9._-]*) exit
 cmd="${1:-}"; shift || true
 case "$cmd" in
   accounts) exec "$PY" "$HERE/tokenstore.py" list --file "$STORE" ;;
-  crux|queries|inspect)
+  crux|queries|inspect|cannibal)
     exec "$PY" "$HERE/google_seo.py" "$cmd" --store "$STORE" "$@" ;;
+  # No auth, no Google: stdlib-only, runs even without the venv.
+  sitemap)
+    exec "$PY" "$HERE/sitemap.py" --store "$STORE" "$@" ;;
+  score)
+    exec "$PY" "$HERE/score.py" --store "$STORE" "$@" ;;
+  schema_gen)
+    exec "$PY" "$HERE/schema_gen.py" --store "$STORE" "$@" ;;
+  content_quality)
+    exec "$PY" "$HERE/content_quality.py" --store "$STORE" "$@" ;;
+  drift)
+    exec "$PY" "$HERE/drift.py" --store "$STORE" "$@" ;;
+  rendercheck)
+    exec "$PY" "$HERE/render_check.py" --store "$STORE" "$@" ;;
+  linkgraph)
+    exec "$PY" "$HERE/linkgraph.py" --store "$STORE" "$@" ;;
   forget)
     # forget --label <label> → drop one account; forget --all → empty the store.
     # Local removal only — does NOT revoke the grant at Google's end.
@@ -41,6 +56,6 @@ case "$cmd" in
     fi
     echo '{"status":"error","reason":"usage: fetch.sh forget {--label <label>|--all} (label charset: A-Za-z0-9._-)"}'
     exit 2 ;;
-  *) echo '{"status":"error","reason":"usage: fetch.sh {accounts|crux|queries|inspect|forget} [flags]"}'
+  *) echo '{"status":"error","reason":"usage: fetch.sh {accounts|crux|queries|inspect|cannibal|sitemap|rendercheck|linkgraph|drift|score|schema_gen|content_quality|forget} [flags]"}'
      exit 2 ;;
 esac

lib/seo-data/fixtures-cannibal/gsc_queries.json

@@ -0,0 +1,7 @@
+{"rows":[
+  {"keys":["plombier paris","https://ex.com/plombier"],"clicks":40,"impressions":900,"ctr":0.044,"position":6.3},
+  {"keys":["plombier paris","https://ex.com/services/plomberie"],"clicks":3,"impressions":300,"ctr":0.010,"position":14.1},
+  {"keys":["urgence fuite","https://ex.com/urgence"],"clicks":5,"impressions":1200,"ctr":0.004,"position":8.9},
+  {"keys":["urgence fuite","https://ex.com/blog/fuite-que-faire"],"clicks":2,"impressions":800,"ctr":0.003,"position":11.4},
+  {"keys":["urgence fuite","https://ex.com/services/depannage"],"clicks":1,"impressions":400,"ctr":0.002,"position":19.2},
+  {"keys":["devis plomberie","https://ex.com/devis"],"clicks":9,"impressions":150,"ctr":0.060,"position":4.1}]}

lib/seo-data/fixtures-drift-v1/pages.json

@@ -0,0 +1,5 @@
+{
+  "https://ex.com/": "<html><head><title>Accueil</title><meta name='description' content='desc'><link rel='canonical' href='https://ex.com/'><script type='application/ld+json'>{\"@type\":\"LocalBusiness\"}</script></head><body><h1>Accueil</h1></body></html>",
+  "https://ex.com/a": "<html><head><title>Page A</title><link rel='canonical' href='https://ex.com/a'></head><body><h1>A</h1></body></html>",
+  "https://ex.com/gone": "<html><head><title>Bientot supprimee</title></head><body><h1>G</h1></body></html>"
+}

lib/seo-data/fixtures-drift-v1/sitemap.xml

@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
+  <url><loc>https://ex.com/</loc></url>
+  <url><loc>https://ex.com/a</loc></url>
+  <url><loc>https://ex.com/gone</loc></url>
+</urlset>

lib/seo-data/fixtures-drift-v2/pages.json

@@ -0,0 +1,5 @@
+{
+  "https://ex.com/": "<html><head><title>Accueil refondue</title><meta name='description' content='desc'><link rel='canonical' href='https://ex.com/'></head><body><p>plus de h1, plus de jsonld</p></body></html>",
+  "https://ex.com/a": "<html><head><title>Page A</title></head><body><h1>A</h1></body></html>",
+  "https://ex.com/neuve": "<html><head><title>Neuve</title></head><body><h1>N</h1></body></html>"
+}

lib/seo-data/fixtures-drift-v2/sitemap.xml

@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
+  <url><loc>https://ex.com/</loc></url>
+  <url><loc>https://ex.com/a</loc></url>
+  <url><loc>https://ex.com/neuve</loc></url>
+</urlset>

lib/seo-data/fixtures-linkgraph/pages.json

@@ -0,0 +1,9 @@
+{
+  "https://ex.com/": "<html><body><a href='/a'>a</a> <a href='/b/'>b trailing slash</a> <a href='#top'>anchor</a> <a href='/css/main.css?v=9'>asset</a> <a href='mailto:x@ex.com'>mail</a> <a href='tel:+33'>tel</a> <a href='https://other.com/x'>external</a> <a href='/img/logo.png'>img</a></body></html>",
+  "https://ex.com/a": "<html><body><a href='/'>home</a> <a href='/deep'>deep</a></body></html>",
+  "https://ex.com/b": "<html><body><a href='/'>home</a></body></html>",
+  "https://ex.com/deep": "<html><body><a href='https://ex.com/deeper'>deeper absolute</a></body></html>",
+  "https://ex.com/deeper": "<html><body><a href='deepest'>relative</a></body></html>",
+  "https://ex.com/deepest": "<html><body><a href='/'>home</a></body></html>",
+  "https://ex.com/orphan": "<html><body><a href='/'>home — links out, nobody links in</a></body></html>"
+}

lib/seo-data/fixtures-linkgraph/sitemap.xml

@@ -0,0 +1,10 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
+  <url><loc>https://ex.com/</loc></url>
+  <url><loc>https://ex.com/a</loc></url>
+  <url><loc>https://ex.com/b</loc></url>
+  <url><loc>https://ex.com/deep</loc></url>
+  <url><loc>https://ex.com/deeper</loc></url>
+  <url><loc>https://ex.com/deepest</loc></url>
+  <url><loc>https://ex.com/orphan</loc></url>
+</urlset>

lib/seo-data/fixtures-norich/gsc_inspect.json

@@ -0,0 +1,2 @@
+{"inspectionResult":{"indexStatusResult":{
+  "verdict":"PASS","coverageState":"Submitted and indexed","lastCrawlTime":"2026-07-01T10:00:00Z"}}}

lib/seo-data/fixtures-sitemap-dtd/sitemap.xml

@@ -0,0 +1,10 @@
+<?xml version="1.0"?>
+<!DOCTYPE urlset [
+  <!ENTITY lol "lol">
+  <!ENTITY lol2 "&lol;&lol;&lol;&lol;&lol;&lol;&lol;&lol;&lol;&lol;">
+  <!ENTITY lol3 "&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;&lol2;">
+  <!ENTITY lol4 "&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;&lol3;">
+]>
+<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
+  <url><loc>https://ex.com/&lol4;</loc></url>
+</urlset>

lib/seo-data/fixtures-sitemap-index/sitemap.xml

@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
+  <sitemap><loc>https://ex.com/sitemap-pages.xml</loc></sitemap>
+  <sitemap><loc>https://ex.com/sitemap-blog.xml</loc></sitemap>
+</sitemapindex>

lib/seo-data/fixtures-sitemap-index/sitemap_child.xml

@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
+  <url><loc>https://ex.com/child-a</loc></url>
+  <url><loc>https://ex.com/child-b</loc></url>
+</urlset>

lib/seo-data/fixtures-spa/page.html

@@ -0,0 +1,8 @@
+<!DOCTYPE html><html lang="fr"><head>
+<title>Mon App</title>
+<script type="module" crossorigin src="/assets/index-a1b2c3.js"></script>
+<link rel="stylesheet" href="/assets/index-d4e5f6.css">
+</head><body>
+<div id="root"></div>
+<script>window.__INITIAL_STATE__={"user":null,"routes":["/","/about","/contact"],"config":{"apiUrl":"https://api.example.com","features":["a","b","c"]}};</script>
+</body></html>

lib/seo-data/fixtures-ssr/page.html

@@ -0,0 +1,8 @@
+<!DOCTYPE html><html lang="fr"><head>
+<title>Lavage auto</title>
+<meta name="description" content="Lavage auto à la main en Seine-et-Marne.">
+<script type="application/ld+json">{"@context":"https://schema.org","@type":"LocalBusiness","name":"X"}</script>
+</head><body>
+<h1>Lavage auto à la main</h1>
+<p>Lavage automobile à la main à Lagny-sur-Marne, detailing et protection céramique. Lavage automobile à la main à Lagny-sur-Marne, detailing et protection céramique. Lavage automobile à la main à Lagny-sur-Marne, detailing et protection céramique. Lavage automobile à la main à Lagny-sur-Marne, detailing et protection céramique. Lavage automobile à la main à Lagny-sur-Marne, detailing et protection céramique. Lavage automobile à la main à Lagny-sur-Marne, detailing et protection céramique. Lavage automobile à la main à Lagny-sur-Marne, detailing et protection céramique. Lavage automobile à la main à Lagny-sur-Marne, detailing et protection céramique.</p>
+</body></html>

lib/seo-data/fixtures/gsc_inspect.json

@@ -1,2 +1,11 @@
-{"inspectionResult":{"indexStatusResult":{
-  "verdict":"PASS","coverageState":"Submitted and indexed","lastCrawlTime":"2026-07-01T10:00:00Z"}}}
+{"inspectionResult":{
+  "indexStatusResult":{
+    "verdict":"PASS","coverageState":"Submitted and indexed","lastCrawlTime":"2026-07-01T10:00:00Z"},
+  "richResultsResult":{"verdict":"FAIL","detectedItems":[
+    {"richResultType":"Breadcrumbs","items":[{"name":"Unnamed item","issues":[]}]},
+    {"richResultType":"FAQ","items":[
+      {"name":"Q1","issues":[
+        {"issueMessage":"Missing field 'acceptedAnswer'","severity":"ERROR"}]},
+      {"name":"Q2","issues":[
+        {"issueMessage":"Missing field 'acceptedAnswer'","severity":"ERROR"},
+        {"issueMessage":"Unspecified image","severity":"WARNING"}]}]}]}}}

lib/seo-data/fixtures/sitemap.xml

@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
+        xmlns:xhtml="http://www.w3.org/1999/xhtml"
+        xmlns:image="http://www.google.com/schemas/sitemap-image/1.1">
+  <!-- image:loc also ends with }loc — it must NOT be counted as a page -->
+  <url>
+    <loc>https://ex.com/</loc>
+    <changefreq>weekly</changefreq>
+    <xhtml:link rel="alternate" hreflang="en" href="https://ex.com/en/" />
+    <image:image>
+      <image:loc>https://ex.com/img/logo.png</image:loc>
+      <image:title>Logo</image:title>
+    </image:image>
+    <image:image>
+      <image:loc>https://ex.com/img/hero.jpeg</image:loc>
+    </image:image>
+  </url>
+  <url><loc>https://ex.com/services</loc></url>
+  <url><loc>https://ex.com/blog</loc></url>
+  <url><loc>https://ex.com/blog</loc></url>
+  <url><loc>   https://ex.com/spaced   </loc></url>
+  <url><loc>ftp://ex.com/nope</loc></url>
+  <url><loc>https://ex.com/bad"quote</loc></url>
+  <url><loc></loc></url>
+</urlset>

lib/seo-data/google_seo.py

@@ -89,13 +89,16 @@ def _gsc_session(store_path, account):
     return AuthorizedSession(creds)
 
 def _norm_queries(raw, dim):
+    # `keys` is the list the API actually returns (one entry per requested
+    # dimension); `key` stays as keys[0] so the single-dim consumer that reads
+    # it keeps working. Additive — nothing to migrate.
     return {"status": "ok", "source": "gsc", "dimension": dim, "rows": [
-        {"key": r["keys"][0], "clicks": r.get("clicks", 0),
+        {"key": r["keys"][0], "keys": r["keys"], "clicks": r.get("clicks", 0),
          "impressions": r.get("impressions", 0), "ctr": r.get("ctr", 0),
          "position": r.get("position")}
         for r in raw.get("rows", [])]}
 
-def queries(store_path, account, property, days=90, dim="query"):
+def queries(store_path, account, property, days=90, dim="query", rows=100):
     raw = _mock("gsc_queries.json")
     if raw is None:
         sess = _gsc_session(store_path, account)
@@ -106,14 +109,89 @@ def queries(store_path, account, property, days=90, dim="query"):
         import urllib.parse
         url = ("https://searchconsole.googleapis.com/webmasters/v3/sites/"
                + urllib.parse.quote(property, safe="") + "/searchAnalytics/query")
+        # dim accepts a comma-separated list: the API groups by several
+        # dimensions at once ("no limit... but you cannot group by the same
+        # dimension twice"), and query+page is what exposes cannibalisation.
+        dims = [d.strip() for d in dim.split(",") if d.strip()]
         r = sess.post(url, json={"startDate": start.isoformat(), "endDate": end.isoformat(),
-                                 "dimensions": [dim], "rowLimit": 100}, timeout=30)
+                                 "dimensions": dims, "rowLimit": rows}, timeout=30)
         if r.status_code == 429:
             return {"status": "degraded", "reason": "rate_limited"}
         r.raise_for_status()
         raw = r.json()
     return _norm_queries(raw, dim)
 
+def _rollup_issues(items):
+    """Count issue instances by severity; dedupe messages (they repeat per item)."""
+    errors = warnings = 0
+    msgs = []
+    for item in items:
+        for iss in item.get("issues", []):
+            sev = iss.get("severity")
+            if sev == "ERROR":
+                errors += 1
+            elif sev == "WARNING":
+                warnings += 1
+            msg = iss.get("issueMessage")
+            if msg and msg not in msgs:
+                msgs.append(msg)
+    return errors, warnings, msgs
+
+def _norm_rich(ir):
+    """richResultsResult → verdict + per-type rollup. Google OMITS the key when
+    it detects no rich results, so absence is data, not an error: surfaced as the
+    synthetic verdict ABSENT (not a Google enum) rather than a missing key, which
+    a caller cannot tell apart from a check that never ran. PARTIAL is never
+    emitted — the API reserves it as unused."""
+    rr = ir.get("richResultsResult")
+    if rr is None:
+        return {"verdict": "ABSENT", "types": []}
+    types = []
+    for det in rr.get("detectedItems", []):
+        errors, warnings, msgs = _rollup_issues(det.get("items", []))
+        types.append({"type": det.get("richResultType"),
+                      "items": len(det.get("items", [])),
+                      "errors": errors, "warnings": warnings, "issues": msgs})
+    return {"verdict": rr.get("verdict"), "types": types}
+
+def _group_by_query(rows):
+    """query+page rows -> {query: [row, …]}. Deterministic aggregation, not
+    judgement: the agent must not be asked to group 1000 rows by eye."""
+    by_q = {}
+    for r in rows:
+        keys = r.get("keys") or []
+        if len(keys) < 2:
+            continue
+        by_q.setdefault(keys[0], []).append(
+            {"url": keys[1], "clicks": r["clicks"],
+             "impressions": r["impressions"], "position": r["position"]})
+    return by_q
+
+def cannibal(store_path, account, property, days=90, rows=1000):
+    """Queries where 2+ of our own pages compete for the same term.
+
+    Google's own data says it; nothing in this system asked. Cannibalisation
+    is a SERP fact, not a content-similarity guess — do not confuse it with
+    the 30/70 duplication rule, which has no data source here."""
+    res = queries(store_path, account, property, days, "query,page", rows)
+    if res.get("status") != "ok":
+        return res
+    conflicts = []
+    for q, pages in _group_by_query(res["rows"]).items():
+        if len(pages) < 2:
+            continue
+        pages.sort(key=lambda p: p["impressions"], reverse=True)
+        conflicts.append({"query": q, "pages": len(pages),
+                          "total_impressions": sum(p["impressions"] for p in pages),
+                          "urls": pages})
+    conflicts.sort(key=lambda c: c["total_impressions"], reverse=True)
+    return {"status": "ok", "source": "gsc", "days": days,
+            "rows_scanned": len(res["rows"]),
+            # rows_scanned == rows means the window was FULL: there may be more
+            # conflicts past the cut. Reported, never silently truncated.
+            "capped": len(res["rows"]) >= rows,
+            "conflict_count": len(conflicts), "conflicts": conflicts}
+
 def inspect(store_path, account, property, url):
     raw = _mock("gsc_inspect.json")
     if raw is None:
@@ -126,11 +204,15 @@ def inspect(store_path, account, property, url):
             return {"status": "degraded", "reason": "rate_limited"}
         r.raise_for_status()
         raw = r.json()
-    isr = raw["inspectionResult"]["indexStatusResult"]
+    ir = raw["inspectionResult"]
+    isr = ir["indexStatusResult"]
+    # rich_results rides the SAME response — Google already sent it and this
+    # function used to discard it. No extra call, no extra quota, no new scope.
     return {"status": "ok", "source": "gsc",
             "indexed": isr.get("verdict") == "PASS",
             "coverage": isr.get("coverageState"),
-            "last_crawl": isr.get("lastCrawlTime")}
+            "last_crawl": isr.get("lastCrawlTime"),
+            "rich_results": _norm_rich(ir)}
 
 def _cli():
     try:
@@ -145,7 +227,15 @@ def _cli():
         pq.add_argument("--account", required=True)
         pq.add_argument("--property", required=True)
         pq.add_argument("--days", type=int, default=90)
-        pq.add_argument("--dim", default="query")
+        pq.add_argument("--dim", default="query",
+                        help="one dimension, or a comma-separated list (query,page)")
+        pq.add_argument("--rows", type=int, default=100)
+        pn = sub.add_parser("cannibal")
+        pn.add_argument("--store", required=True)
+        pn.add_argument("--account", required=True)
+        pn.add_argument("--property", required=True)
+        pn.add_argument("--days", type=int, default=90)
+        pn.add_argument("--rows", type=int, default=1000)
         pi = sub.add_parser("inspect")
         pi.add_argument("--store", required=True)
         pi.add_argument("--account", required=True)
@@ -156,7 +246,10 @@ def _cli():
             print(json.dumps(crux(args.url, args.strategy), indent=2))
         elif args.cmd == "queries":
             print(json.dumps(queries(args.store, args.account, args.property,
-                                      args.days, args.dim), indent=2))
+                                      args.days, args.dim, args.rows), indent=2))
+        elif args.cmd == "cannibal":
+            print(json.dumps(cannibal(args.store, args.account, args.property,
+                                       args.days, args.rows), indent=2))
         elif args.cmd == "inspect":
             print(json.dumps(inspect(args.store, args.account, args.property,
                                       args.url), indent=2))

lib/seo-data/linkgraph.py

@@ -0,0 +1,170 @@
+#!/usr/bin/env python3
+"""Internal link graph -> orphans + click depth. Stdlib only.
+
+seo-analyzer.md asks "Every important page reachable within 3 clicks?" (:613)
+and "Orphan pages (no inbound internal links)?" (:616) and has never had a
+command that answers either. This is that command.
+
+EXHAUSTIVE OR NOTHING. You cannot sample orphans: proving a page has no
+inbound link means having read every other page. A partial crawl invents
+orphans, and "page X has no inbound links" when it does is the worst finding
+this tool could emit — it sends a client fixing what is not broken. So when
+the cap bites, orphans are WITHHELD, not truncated.
+
+Does NOT render JS. On a client-side-rendered SPA the links are not in the
+HTML, every page looks orphaned, and that is a catastrophic false positive —
+so an empty link graph is REFUSED (no_links_in_html), never reported.
+"""
+import argparse, json
+from html.parser import HTMLParser
+from urllib.parse import urljoin, urlparse, urldefrag
+
+import sitemap as sm                      # sibling module: fetch + parse
+
+MAX_PAGES = 500
+# Extensions that are assets, not pages. Seen live: /css/main.css?v=1778157313
+ASSET_EXT = (".css", ".js", ".mjs", ".png", ".jpg", ".jpeg", ".gif", ".webp",
+             ".avif", ".svg", ".ico", ".woff", ".woff2", ".ttf", ".eot",
+             ".pdf", ".zip", ".mp4", ".webm", ".xml", ".json", ".txt", ".rss")
+
+class _Links(HTMLParser):
+    def __init__(self):
+        super().__init__(convert_charrefs=True)
+        self.hrefs = []
+    def handle_starttag(self, tag, attrs):
+        if tag != "a":
+            return
+        for k, v in attrs:
+            if k == "href" and v:
+                self.hrefs.append(v)
+
+def _norm(u):
+    """Canonical form for graph identity. Drops the fragment, keeps the query
+    (?p=2 IS a different page), and unifies the trailing slash so /blog and
+    /blog/ are one node rather than a phantom orphan pair."""
+    u = urldefrag(u)[0]
+    p = urlparse(u)
+    path = p.path or "/"
+    if len(path) > 1 and path.endswith("/"):
+        path = path[:-1]
+    out = "%s://%s%s" % (p.scheme, p.netloc.lower(), path)
+    return out + ("?" + p.query if p.query else "")
+
+def _page_links(base, html, host):
+    """Internal page links from one document. Filters what a link graph must
+    never contain: assets, #anchors, mailto:/tel:, and other hosts."""
+    p = _Links()
+    try:
+        p.feed(html)
+    except Exception:
+        pass                               # tolerate malformed markup
+    out = set()
+    for h in p.hrefs:
+        h = h.strip()
+        if not h or h.startswith(("#", "mailto:", "tel:", "javascript:", "data:")):
+            continue
+        absu = urljoin(base, h)
+        pr = urlparse(absu)
+        if pr.scheme not in ("http", "https") or pr.netloc.lower() != host:
+            continue
+        if pr.path.lower().endswith(ASSET_EXT):
+            continue
+        out.add(_norm(absu))
+    return out
+
+def _mock_pages():
+    """{url: html} for tests. A single page.html fixture cannot express a
+    GRAPH — every node would carry identical links — so the mock is a map."""
+    raw = sm._mock("pages.json")
+    return json.loads(raw.decode("utf-8")) if raw else None
+
+def _crawl(urls, host):
+    """Fetch each page once; return {page: {links}} plus a failure count."""
+    pages = _mock_pages()
+    graph, failed = {}, 0
+    for u in urls:
+        if pages is not None:
+            html = pages.get(u)
+            if html is None:
+                failed += 1
+                continue
+        else:
+            try:
+                html = sm._fetch(u).decode("utf-8", "replace")
+            except Exception:
+                failed += 1
+                continue
+        graph[_norm(u)] = _page_links(u, html, host)
+    return graph, failed
+
+def _depths(graph, root):
+    """BFS click-depth from the homepage. Absent = unreachable by links."""
+    seen, frontier, d = {root: 0}, [root], 0
+    while frontier:
+        d += 1
+        nxt = []
+        for node in frontier:
+            for tgt in graph.get(node, ()):
+                if tgt not in seen:
+                    seen[tgt] = d
+                    nxt.append(tgt)
+        frontier = nxt
+    return seen
+
+def linkgraph(sitemap_url, max_pages=MAX_PAGES):
+    sm_res = sm.sitemap(sitemap_url)
+    if sm_res.get("status") != "ok":
+        return sm_res                      # propagate the sitemap's own degrade
+    urls = sm_res["urls"]
+    capped = len(urls) > max_pages
+    host = urlparse(urls[0]).netloc.lower()
+    graph, failed = _crawl(urls[:max_pages], host)
+    if not graph:
+        return {"status": "degraded", "reason": "no_pages_fetched"}
+    total_links = sum(len(v) for v in graph.values())
+    if total_links == 0:
+        # Every page orphaned is never the truth — it is a JS-rendered site.
+        return {"status": "degraded", "reason": "no_links_in_html",
+                "pages_crawled": len(graph),
+                "hint": "links absent from served HTML (SPA?) — see R1/R2"}
+    inbound = {n: 0 for n in graph}
+    for src, tgts in graph.items():
+        for t in tgts:
+            if t in inbound and t != src:
+                inbound[t] += 1
+    root = _norm("%s://%s/" % (urlparse(urls[0]).scheme, host))
+    depth = _depths(graph, root)
+    out = {"status": "ok", "source": "linkgraph",
+           "pages_crawled": len(graph), "pages_failed": failed,
+           "total_internal_links": total_links, "capped": capped,
+           "max_depth": max(depth.values()) if depth else 0,
+           "beyond_3_clicks": sorted(n for n, d in depth.items() if d > 3),
+           "unreachable": sorted(n for n in graph if n not in depth)}
+    if capped or failed:
+        # A page can only be called orphaned if EVERY other page was read.
+        out["orphans_withheld"] = True
+        out["reason_withheld"] = ("crawl incomplete (capped=%s, failed=%d) — "
+                                  "an orphan from a partial crawl is a false "
+                                  "orphan" % (capped, failed))
+    else:
+        out["orphans"] = sorted(n for n, c in inbound.items()
+                                if c == 0 and n != root)
+    return out
+
+def _cli():
+    try:
+        p = argparse.ArgumentParser()
+        p.add_argument("--url", required=True, help="sitemap URL")
+        p.add_argument("--max", type=int, default=MAX_PAGES)
+        p.add_argument("--store", default=None)   # accepted+ignored
+        args = p.parse_args()
+        print(json.dumps(linkgraph(args.url, args.max), indent=2))
+    except SystemExit as e:
+        if e.code not in (0, None):
+            print(json.dumps({"status": "error", "reason": "bad_usage"}))
+        raise
+    except Exception:
+        print(json.dumps({"status": "degraded", "reason": "unexpected_error"}))
+
+if __name__ == "__main__":
+    _cli()

lib/seo-data/render_check.py

@@ -0,0 +1,106 @@
+#!/usr/bin/env python3
+"""Is the content in the served HTML, or painted by JS? Stdlib only.
+
+seo-analyzer records `RENDERING: SSR/SSG/SPA/hybrid` and then does nothing
+with it. That is the gap this closes. On a client-rendered site `curl` returns
+an empty shell, so every meta/H1/JSON-LD check reports "missing" and the audit
+emits a page of false findings against a site that may be perfectly fine.
+
+The verdict is taken from what the server actually sent — not from guessing at
+package.json, where a React SPA and a Next.js SSR app look identical.
+
+R2, not R1: this REPORTS blindness so the agent can refuse to score. It does
+not render JS. No Playwright, no Chromium, no venv.
+"""
+import argparse, json, re
+from html.parser import HTMLParser
+
+import sitemap as sm                       # sibling: _fetch / _mock
+
+# A shell can still carry a title + a couple of nav words. These thresholds
+# separate "shell" from "page" on the two real sites measured 2026-07-17
+# (server-rendered: 1 h1, thousands of body chars) and on a hydration stub.
+MIN_TEXT = 400
+MIN_H1 = 1
+
+class _Doc(HTMLParser):
+    """Collect body text and the tags an SEO audit reads. Script/style content
+    is NOT text: a 200 KB React bundle would otherwise look like a rich page."""
+    SKIP = ("script", "style", "noscript", "template", "svg")
+
+    def __init__(self):
+        super().__init__(convert_charrefs=True)
+        self.text, self.h1, self.jsonld, self.meta_desc = [], 0, 0, False
+        self._skip = 0
+        self._ld = False
+
+    def handle_starttag(self, tag, attrs):
+        a = dict(attrs)
+        if tag in self.SKIP:
+            self._skip += 1
+            self._ld = tag == "script" and a.get("type") == "application/ld+json"
+        elif tag == "h1":
+            self.h1 += 1
+        elif tag == "meta" and a.get("name", "").lower() == "description":
+            self.meta_desc = bool((a.get("content") or "").strip())
+
+    def handle_endtag(self, tag):
+        if tag in self.SKIP and self._skip:
+            self._skip -= 1
+            self._ld = False
+
+    def handle_data(self, data):
+        if self._ld:
+            self.jsonld += 1
+        elif not self._skip:
+            s = data.strip()
+            if s:
+                self.text.append(s)
+
+def _verdict(text_chars, h1, jsonld):
+    if text_chars >= MIN_TEXT and h1 >= MIN_H1:
+        return "server-rendered"
+    if text_chars < MIN_TEXT and h1 == 0 and jsonld == 0:
+        return "client-rendered"
+    return "partial"                       # shell + some SSR'd head, or thin page
+
+def render_check(url):
+    raw = sm._mock("page.html")
+    if raw is None:
+        try:
+            raw = sm._fetch(url)
+        except Exception:
+            return {"status": "degraded", "reason": "fetch_failed"}
+    html = raw.decode("utf-8", "replace")
+    d = _Doc()
+    try:
+        d.feed(html)
+    except Exception:
+        pass                               # tolerate malformed markup
+    text = re.sub(r"\s+", " ", " ".join(d.text)).strip()
+    verdict = _verdict(len(text), d.h1, d.jsonld)
+    out = {"status": "ok", "source": "render_check", "verdict": verdict,
+           "body_text_chars": len(text), "h1_in_html": d.h1,
+           "jsonld_in_html": d.jsonld, "meta_description_in_html": d.meta_desc,
+           "html_bytes": len(raw)}
+    if verdict != "server-rendered":
+        out["warning"] = ("content is not in the served HTML — curl-based "
+                          "on-page checks will report false 'missing' findings")
+    return out
+
+def _cli():
+    try:
+        p = argparse.ArgumentParser()
+        p.add_argument("--url", required=True)
+        p.add_argument("--store", default=None)   # accepted+ignored
+        args = p.parse_args()
+        print(json.dumps(render_check(args.url), indent=2))
+    except SystemExit as e:
+        if e.code not in (0, None):
+            print(json.dumps({"status": "error", "reason": "bad_usage"}))
+        raise
+    except Exception:
+        print(json.dumps({"status": "degraded", "reason": "unexpected_error"}))
+
+if __name__ == "__main__":
+    _cli()

lib/seo-data/safe_fetch.py

@@ -0,0 +1,164 @@
+#!/usr/bin/env python3
+"""SSRF- and DNS-rebinding-safe HTTP(S) fetch. Stdlib only.
+
+The verbs that fetch remote content (sitemap, linkgraph, render_check, drift)
+all route through sitemap._fetch, which used urllib.request.urlopen. urlopen
+resolves the host, then connects — two DNS lookups with a window between them.
+A hostile authority can answer PUBLIC to the validation lookup and a PRIVATE
+address (169.254.169.254 cloud metadata, 127.0.0.1, the LAN) to the connect
+lookup. That is DNS rebinding, and a name-level guard cannot see it.
+
+This collapses the two lookups into one: resolve ONCE, validate every returned
+IP, then connect to the exact validated IP while preserving the Host header,
+TLS SNI, and certificate validation for the real hostname. There is no second
+resolution to poison.
+
+Better than the reference implementation this idea came from (claude-seo
+url_safety.py, MIT) on three axes, all verified before writing:
+- dual-stack: validates IPv4 AND IPv6 (theirs is IPv4-only);
+- no global state: each connection pins its own socket, so it is thread-safe
+  by construction (theirs monkeypatches socket.getaddrinfo behind a global
+  lock);
+- stdlib only: http.client + ssl + ipaddress, no `requests`.
+
+NOT covered, stated rather than left silent: the shell `curl` calls in the
+agent specs (seo-analyzer/geo-analyzer STEP 4, the sameAs loop) run in a
+separate process and cannot be pinned from here. Their surface is smaller
+(a fixed set against an operator-typed/confirmed $DOMAIN). Closing them needs
+`curl --resolve` and is a separate change.
+"""
+import gzip
+import http.client
+import ipaddress
+import socket
+import ssl
+from urllib.parse import urljoin, urlparse
+
+DEFAULT_TIMEOUT = 20
+DEFAULT_MAX_BYTES = 20 * 1024 * 1024
+MAX_REDIRECTS = 5
+
+
+class UnsafeTarget(Exception):
+    """A URL resolved to a non-public address, or a redirect did. Raised BEFORE
+    any connection to that address. Callers already wrap _fetch in try/except
+    and degrade, so the fail-open contract is preserved."""
+
+
+# Special-use ranges that `is_global` reports as public but are not legitimate
+# fetch targets. 192.88.99.0/24 = RFC 3068 6to4-relay anycast (a security
+# review flagged it 2026-07-17). Grows if more surface.
+_EXTRA_DENY = (ipaddress.ip_network("192.88.99.0/24"),)
+
+
+def _ip_is_public(ip_str):
+    """A globally routable unicast address, dual-stack. `is_global` is the
+    decisive gate — it alone rejects CGNAT (100.64/10) that the per-flag checks
+    miss — with the explicit flags plus an extra special-use deny list as
+    defence in depth."""
+    ip = ipaddress.ip_address(ip_str)
+    if not ip.is_global:
+        return False
+    if any(ip in net for net in _EXTRA_DENY):
+        return False
+    return not (ip.is_private or ip.is_loopback or ip.is_link_local
+                or ip.is_reserved or ip.is_multicast or ip.is_unspecified)
+
+
+def _resolve_pinned(host, port, resolver=socket.getaddrinfo):
+    """Resolve host ONCE and return [(family, ip)] for connecting. Refuse if
+    ANY resolved address is non-public — a name advertising both public and
+    private A records is exactly the multi-answer rebinding vector, and a
+    legitimate public site does not do it. `resolver` is injected in tests to
+    plant a private address and prove the refusal."""
+    try:
+        infos = resolver(host, port, type=socket.SOCK_STREAM)
+    except socket.gaierror as e:
+        raise UnsafeTarget("cannot resolve %r: %s" % (host, e))
+    pinned = []
+    for family, _type, _proto, _canon, sockaddr in infos:
+        ip = sockaddr[0]
+        if not _ip_is_public(ip):
+            raise UnsafeTarget("%s resolves to non-public %s" % (host, ip))
+        pinned.append((family, ip))
+    if not pinned:
+        raise UnsafeTarget("%s resolved to nothing" % host)
+    return pinned
+
+
+class _PinnedHTTPSConnection(http.client.HTTPSConnection):
+    """HTTPS to a pinned IP, with SNI + cert validation for the real host."""
+    def __init__(self, host, pinned_ip, family, **kw):
+        super().__init__(host, **kw)          # host → Host header + SNI
+        self._pinned_ip = pinned_ip
+        self._family = family
+
+    def connect(self):
+        sock = socket.create_connection((self._pinned_ip, self.port),
+                                        timeout=self.timeout)
+        # server_hostname = the real host → SNI + hostname check both use it,
+        # never the IP.
+        self.sock = self._context.wrap_socket(sock, server_hostname=self.host)
+
+
+class _PinnedHTTPConnection(http.client.HTTPConnection):
+    """Plain HTTP to a pinned IP (Host header stays the real host)."""
+    def __init__(self, host, pinned_ip, family, **kw):
+        super().__init__(host, **kw)
+        self._pinned_ip = pinned_ip
+        self._family = family
+
+    def connect(self):
+        self.sock = socket.create_connection((self._pinned_ip, self.port),
+                                             timeout=self.timeout)
+
+
+def _one_request(url, timeout, max_bytes, resolver):
+    """One hop: resolve+pin the host, connect, return (status, headers, body)."""
+    p = urlparse(url)
+    if p.scheme not in ("http", "https"):
+        raise UnsafeTarget("scheme must be http/https: %r" % url)
+    host = p.hostname
+    if not host:
+        raise UnsafeTarget("no host in %r" % url)
+    port = p.port or (443 if p.scheme == "https" else 80)
+    family, ip = _resolve_pinned(host, port, resolver)[0]   # any is public here
+    ctx = ssl.create_default_context() if p.scheme == "https" else None
+    if p.scheme == "https":
+        conn = _PinnedHTTPSConnection(host, ip, family, port=port,
+                                      timeout=timeout, context=ctx)
+    else:
+        conn = _PinnedHTTPConnection(host, ip, family, port=port,
+                                     timeout=timeout)
+    try:
+        path = p.path or "/"
+        if p.query:
+            path += "?" + p.query
+        # No Accept-Encoding: keep HTTP bodies un-gzipped; the .xml.gz
+        # content-level case is handled by the caller's magic-byte check.
+        conn.request("GET", path, headers={"Host": host,
+                                           "User-Agent": "claude-seo-data/1.0"})
+        r = conn.getresponse()
+        body = r.read(max_bytes)
+        return r.status, {k.lower(): v for k, v in r.getheaders()}, body
+    finally:
+        conn.close()
+
+
+def safe_fetch(url, timeout=DEFAULT_TIMEOUT, max_bytes=DEFAULT_MAX_BYTES,
+               max_redirects=MAX_REDIRECTS, resolver=socket.getaddrinfo):
+    """Fetch url with resolve-then-pin, following redirects and RE-VALIDATING
+    each hop — urlopen followed redirects to whatever address the Location
+    named, re-opening the rebinding window on every hop. Returns the raw body
+    bytes (the caller handles content-level gzip)."""
+    seen = 0
+    current = url
+    while True:
+        status, headers, body = _one_request(current, timeout, max_bytes, resolver)
+        if status in (301, 302, 303, 307, 308) and "location" in headers:
+            seen += 1
+            if seen > max_redirects:
+                raise UnsafeTarget("too many redirects from %r" % url)
+            current = urljoin(current, headers["location"])   # re-validated next loop
+            continue
+        return body

lib/seo-data/schema_gen.py

@@ -0,0 +1,301 @@
+#!/usr/bin/env python3
+"""Deterministic JSON-LD generators for four Schema.org types. Stdlib only.
+
+Adapted from claude-seo (github.com/AgriciDaniel/claude-seo, MIT),
+schema_generate.py — rewritten to the lib/seo-data fail-open contract.
+
+Everywhere else in this repo we AUDIT existing markup (google_seo.py
+`inspect`, geo-analyzer's JSON-LD rules); this is the one verb that
+GENERATES it. Reservation + potentialAction matter now that AI Mode
+executes restaurant reservations; DiscussionForumPosting is a live SERP
+feature; ProfilePage with sameAs/knowsAbout is the cheapest entity-graph
+builder for AI citation correlation. geo-analyzer's G2 batch calls this
+instead of hand-writing the markup — it only generates STRUCTURE, unknown
+field VALUES stay the caller's `[À COMPLÉTER]` placeholder, never invented
+here.
+"""
+import argparse, json
+
+
+def reservation(provider, start, *, end=None, party_size=None,
+                 reservation_id=None, reservation_for_name=None,
+                 customer_name=None, customer_email=None,
+                 kind="FoodEstablishmentReservation"):
+    """Reservation JSON-LD block. Defaults to FoodEstablishment."""
+    payload = {
+        "@context": "https://schema.org",
+        "@type": kind,
+        "reservationStatus": "https://schema.org/ReservationConfirmed",
+        "provider": {"@type": "Organization", "name": provider},
+        "reservationFor": {
+            "@type": "FoodEstablishment"
+                     if kind == "FoodEstablishmentReservation" else "Place",
+            "name": reservation_for_name or provider,
+        },
+        "startTime": start,
+        "endTime": end,
+        "partySize": party_size,
+        "reservationId": reservation_id,
+    }
+    if customer_name or customer_email:
+        payload["underName"] = {"@type": "Person", "name": customer_name,
+                                 "email": customer_email}
+    return payload
+
+
+def order_action(merchant, *, order_url, name="Order online",
+                  accepted_payment_method=None, delivery_method=None):
+    """OrderAction potentialAction block. Attach to a Product/Service via
+    {"@type": "Product", "potentialAction": <this dict>}."""
+    payload = {
+        "@context": "https://schema.org",
+        "@type": "OrderAction",
+        "name": name,
+        "target": {
+            "@type": "EntryPoint",
+            "urlTemplate": order_url,
+            "inLanguage": "en-US",
+            "actionPlatform": [
+                "https://schema.org/DesktopWebPlatform",
+                "https://schema.org/MobileWebPlatform",
+            ],
+        },
+        "deliveryMethod": delivery_method or [
+            "https://schema.org/OnSitePickup",
+            "https://schema.org/ParcelService",
+        ],
+        "priceSpecification": {
+            "@type": "PriceSpecification",
+            "eligibleTransactionVolume": {
+                "@type": "PriceSpecification",
+                "minPrice": 0,
+                "priceCurrency": "USD",
+            },
+        },
+        "merchant": {"@type": "Organization", "name": merchant},
+    }
+    if accepted_payment_method:
+        payload["acceptedPaymentMethod"] = [
+            {"@type": "PaymentMethod", "name": m}
+            for m in accepted_payment_method
+        ]
+    return payload
+
+
+def discussion(headline, author, *, url, date_published, text=None,
+               date_modified=None, interaction_count=None,
+               comment_count=None):
+    """DiscussionForumPosting JSON-LD block."""
+    payload = {
+        "@context": "https://schema.org",
+        "@type": "DiscussionForumPosting",
+        "headline": headline,
+        "author": {"@type": "Person", "name": author},
+        "datePublished": date_published,
+        "dateModified": date_modified,
+        "url": url,
+        "mainEntityOfPage": {"@type": "WebPage", "@id": url},
+        "text": text,
+        "commentCount": comment_count,
+    }
+    if interaction_count:
+        payload["interactionStatistic"] = [
+            {"@type": "InteractionCounter",
+             "interactionType": "https://schema.org/%s" % k,
+             "userInteractionCount": v}
+            for k, v in interaction_count.items()
+        ]
+    return payload
+
+
+def profile(name, *, url, description=None, same_as=None, knows_about=None,
+            works_for=None, image=None, job_title=None):
+    """ProfilePage JSON-LD block. sameAs + knowsAbout is the entity-graph
+    helper for AI citation correlation — Wikipedia/GitHub/LinkedIn/ORCID
+    URLs in sameAs disambiguate the person across knowledge graphs."""
+    person = {
+        "@type": "Person",
+        "name": name,
+        "url": url,
+        "description": description,
+        "sameAs": list(same_as) if same_as else None,
+        "knowsAbout": list(knows_about) if knows_about else None,
+        "worksFor": {"@type": "Organization", "name": works_for}
+                    if works_for else None,
+        "image": image,
+        "jobTitle": job_title,
+    }
+    return {"@context": "https://schema.org", "@type": "ProfilePage",
+            "mainEntity": person, "url": url}
+
+
+def _strip_nones(value):
+    """Recursively drop dict keys AND list elements whose value is None —
+    the emitted JSON-LD must never contain a null."""
+    if isinstance(value, dict):
+        return {k: _strip_nones(v) for k, v in value.items() if v is not None}
+    if isinstance(value, list):
+        return [_strip_nones(v) for v in value if v is not None]
+    return value
+
+
+def _need(value, field):
+    """Raise on a schema-required field that is present but empty — the
+    case argparse's `required=True` cannot catch (an empty string is a
+    given flag, not a missing one)."""
+    if value is None or not str(value).strip():
+        raise ValueError("missing required field: %s" % field)
+    return value
+
+
+def _generate(kind, args):
+    """Route to the matching generator, enforcing schema-required fields."""
+    if kind == "reservation":
+        return reservation(
+            _need(args.provider, "provider"), _need(args.start, "start"),
+            end=args.end, party_size=args.party_size,
+            reservation_id=args.reservation_id,
+            reservation_for_name=args.reservation_for_name,
+            customer_name=args.customer_name,
+            customer_email=args.customer_email, kind=args.reservation_kind,
+        )
+    if kind == "order":
+        return order_action(
+            _need(args.merchant, "merchant"),
+            order_url=_need(args.order_url, "order_url"), name=args.name,
+            accepted_payment_method=args.accepted_payment_method,
+            delivery_method=args.delivery_method,
+        )
+    if kind == "discussion":
+        interaction = {"LikeAction": args.likes} if args.likes else None
+        return discussion(
+            _need(args.headline, "headline"), _need(args.author, "author"),
+            url=_need(args.url, "url"),
+            date_published=_need(args.date_published, "date_published"),
+            text=args.text, date_modified=args.date_modified,
+            interaction_count=interaction, comment_count=args.comment_count,
+        )
+    if kind == "profile":
+        return profile(
+            _need(args.name, "name"), url=_need(args.url, "url"),
+            description=args.description, same_as=args.same_as,
+            knows_about=args.knows_about, works_for=args.works_for,
+            image=args.image, job_title=args.job_title,
+        )
+    raise ValueError("unknown kind: %r" % kind)  # pragma: no cover — argparse
+
+
+def _envelope(payload, script_tag):
+    cleaned = _strip_nones(payload)
+    out = {"status": "ok", "source": "schema_gen",
+           "type": cleaned.get("@type"), "jsonld": cleaned}
+    if script_tag:
+        pretty = json.dumps(cleaned, indent=2, ensure_ascii=False)
+        out["script"] = ('<script type="application/ld+json">\n%s\n</script>'
+                          % pretty)
+    return out
+
+
+def _script_tag_parent():
+    """`--script-tag` as a shared parent parser, so it is valid on every
+    subcommand — `fetch.sh schema_gen <type> [flags]` puts the type FIRST,
+    and argparse only accepts a flag after a subcommand token if that flag
+    was declared on the subparser, not the top-level one."""
+    parent = argparse.ArgumentParser(add_help=False)
+    parent.add_argument(
+        "--script-tag", action="store_true",
+        help="Wrap jsonld in <script type=application/ld+json>.",
+    )
+    return parent
+
+
+def _add_reservation_args(sub, parents):
+    p = sub.add_parser("reservation", parents=parents,
+                        help="FoodEstablishmentReservation et al.")
+    p.add_argument("--provider", required=True)
+    p.add_argument("--start", required=True, help="ISO 8601 startTime.")
+    p.add_argument("--end")
+    p.add_argument("--party-size", type=int)
+    p.add_argument("--reservation-id")
+    p.add_argument("--reservation-for-name")
+    p.add_argument("--customer-name")
+    p.add_argument("--customer-email")
+    p.add_argument(
+        "--reservation-kind", dest="reservation_kind",
+        default="FoodEstablishmentReservation",
+        choices=(
+            "FoodEstablishmentReservation", "LodgingReservation",
+            "RentalCarReservation", "TaxiReservation", "EventReservation",
+            "TrainReservation", "FlightReservation",
+        ),
+    )
+
+
+def _add_order_args(sub, parents):
+    p = sub.add_parser("order", parents=parents,
+                        help="OrderAction (potentialAction).")
+    p.add_argument("--merchant", required=True)
+    p.add_argument("--order-url", required=True)
+    p.add_argument("--name", default="Order online")
+    p.add_argument("--accepted-payment-method", nargs="*", default=None)
+    p.add_argument("--delivery-method", nargs="*", default=None)
+
+
+def _add_discussion_args(sub, parents):
+    p = sub.add_parser("discussion", parents=parents,
+                        help="DiscussionForumPosting.")
+    p.add_argument("--headline", required=True)
+    p.add_argument("--author", required=True)
+    p.add_argument("--url", required=True)
+    p.add_argument("--date", dest="date_published", required=True)
+    p.add_argument("--text")
+    p.add_argument("--date-modified")
+    p.add_argument("--comment-count", type=int)
+    p.add_argument("--likes", type=int, default=None,
+                   help="LikeAction count (interactionStatistic).")
+
+
+def _add_profile_args(sub, parents):
+    p = sub.add_parser("profile", parents=parents,
+                        help="ProfilePage with sameAs / knowsAbout.")
+    p.add_argument("--name", required=True)
+    p.add_argument("--url", required=True)
+    p.add_argument("--description")
+    p.add_argument("--same-as", nargs="*", default=None)
+    p.add_argument("--knows-about", nargs="*", default=None)
+    p.add_argument("--works-for")
+    p.add_argument("--image")
+    p.add_argument("--job-title")
+
+
+def _build_parser():
+    p = argparse.ArgumentParser(
+        description="Schema.org JSON-LD generators (stdlib, deterministic)."
+    )
+    p.add_argument("--store", default=None)  # accepted+ignored (dispatch)
+    sub = p.add_subparsers(dest="kind", required=True)
+    parents = [_script_tag_parent()]
+    _add_reservation_args(sub, parents)
+    _add_order_args(sub, parents)
+    _add_discussion_args(sub, parents)
+    _add_profile_args(sub, parents)
+    return p
+
+
+def _cli():
+    try:
+        args = _build_parser().parse_args()
+        payload = _generate(args.kind, args)
+        print(json.dumps(_envelope(payload, args.script_tag), indent=2))
+    except SystemExit as e:
+        if e.code not in (0, None):
+            print(json.dumps({"status": "error", "reason": "bad_usage"}))
+        raise
+    except Exception as e:
+        # Fail-open: a missing required field or any other unexpected error
+        # is a normal outcome here, never a traceback or empty stdout.
+        print(json.dumps({"status": "degraded", "reason": str(e)}))
+
+
+if __name__ == "__main__":
+    _cli()

lib/seo-data/score.py

@@ -0,0 +1,113 @@
+#!/usr/bin/env python3
+"""Deterministic /20 scoring from a findings list. Stdlib only.
+
+/harden has a real scale (SKILL.md:435 — Critique -15, Haute -8, Moyenne -3,
+Basse -1, clamp [0,100]). /seo has none: every axis is felt, not computed, so
+two runs over identical code can produce different scores. That is a
+credibility problem on its own, and /client-handover gates on 17/20 — a
+wobbling number makes the gate arbitrary. H2 sharpens it further: now that
+drift reports what actually changed, a score moving on its own is visibly
+noise.
+
+The split is the point. The LLM keeps the irreducible judgement — WHICH
+findings exist and how severe each is. The arithmetic stops being judgement:
+same findings in, same score out. Same principle as grouping cannibalisation
+rows in the engine rather than asking a model to add up 1000 of them.
+
+Scale is /harden's, /5 into /20, so the whole skill family speaks one
+vocabulary.
+"""
+import argparse, json, sys
+
+PENALTY = {"critique": 15, "haute": 8, "moyenne": 3, "basse": 1}
+
+# STEP 9 weights. FULL = 7 axes, LOCAL = 4 (off-page/social/competitive are
+# not audited at that depth).
+WEIGHTS = {
+    ("FULL", "local"):    {"technical": .20, "on-page": .20, "seo-local": .25,
+                           "off-page": .10, "social": .10, "competitive": .05,
+                           "legal": .10},
+    ("FULL", "national"): {"technical": .30, "on-page": .30, "seo-local": .05,
+                           "off-page": .15, "social": .05, "competitive": .10,
+                           "legal": .05},
+    ("LOCAL", "local"):   {"technical": .25, "on-page": .35, "seo-local": .20,
+                           "legal": .20},
+    ("LOCAL", "national"):{"technical": .35, "on-page": .45, "seo-local": .05,
+                           "legal": .15},
+}
+
+def _axis_score(findings):
+    """100 - Σ penalties, clamped, then /5 → /20. Prevalence shifts severity
+    ONE step, never invents one: a finding on 1 of 12 sampled pages is not the
+    same defect as one on 12 of 12, and pretending otherwise is what made the
+    old scores unreproducible."""
+    total = 0
+    for f in findings:
+        sev = str(f.get("severity", "")).lower()
+        if sev not in PENALTY:
+            raise ValueError("unknown severity: %r" % f.get("severity"))
+        order = ["basse", "moyenne", "haute", "critique"]
+        i = order.index(sev)
+        aff, samp = f.get("affected"), f.get("sampled")
+        if isinstance(aff, int) and isinstance(samp, int) and samp > 0:
+            ratio = aff / samp
+            if ratio >= 0.5:
+                i = min(i + 1, len(order) - 1)      # widespread → escalate
+            elif aff <= 1:
+                i = max(i - 1, 0)                   # isolated → de-escalate
+        total += PENALTY[order[i]]
+    return round(max(0, 100 - total) / 5.0, 1)
+
+def score(payload):
+    depth = str(payload.get("depth", "FULL")).upper()
+    profile = str(payload.get("profile", "local")).lower()
+    key = (depth, profile)
+    if key not in WEIGHTS:
+        return {"status": "error", "reason": "unknown depth/profile: %s/%s"
+                                             % (depth, profile)}
+    weights, axes_in = WEIGHTS[key], payload.get("axes", {})
+    scored, na = {}, []
+    for axis, w in weights.items():
+        a = axes_in.get(axis)
+        if a is None or str(a.get("status", "")).lower() == "na":
+            na.append(axis)                          # N/A is not a zero
+            continue
+        try:
+            s = _axis_score(a.get("findings", []))
+        except ValueError as e:
+            return {"status": "error", "reason": str(e)}
+        scored[axis] = {"score_20": s, "weight": w,
+                        "findings": len(a.get("findings", []))}
+    if not scored:
+        return {"status": "degraded", "reason": "no_axis_scored"}
+    # Renormalise over what was actually measured. R2 mandates this for a
+    # client-rendered on-page axis and left it to the model to do by hand.
+    live = sum(v["weight"] for v in scored.values())
+    for v in scored.values():
+        v["weight_renormalised"] = round(v["weight"] / live, 4)
+    glob = sum(v["score_20"] * v["weight"] / live for v in scored.values())
+    return {"status": "ok", "source": "score", "depth": depth,
+            "profile": profile, "axes": scored, "na": sorted(na),
+            "weights_renormalised": round(live, 4) != 1.0,
+            "global_20": round(glob, 1)}
+
+def _cli():
+    try:
+        p = argparse.ArgumentParser()
+        p.add_argument("--findings", default="-", help="JSON path, or - for stdin")
+        p.add_argument("--store", default=None)      # accepted+ignored
+        args = p.parse_args()
+        raw = sys.stdin.read() if args.findings == "-" else \
+            open(args.findings, encoding="utf-8").read()
+        print(json.dumps(score(json.loads(raw)), indent=2))
+    except SystemExit as e:
+        if e.code not in (0, None):
+            print(json.dumps({"status": "error", "reason": "bad_usage"}))
+        raise
+    except Exception:
+        # Unlike the fetch verbs this is pure arithmetic: a degrade here means
+        # malformed input, never a network fact.
+        print(json.dumps({"status": "error", "reason": "bad_findings_json"}))
+
+if __name__ == "__main__":
+    _cli()

lib/seo-data/seo-data.test.sh

@@ -9,6 +9,9 @@ no()   { echo "  FAIL $1 — $2"; FAIL=$((FAIL+1)); }
 # assert stdout of a command contains / omits a fixed string
 has()  { if printf '%s' "$2" | grep -qF -- "$3"; then ok "$1"; else no "$1" "missing: $3"; fi; }
 hasnt(){ if printf '%s' "$2" | grep -qF -- "$3"; then no "$1" "forbidden: $3"; else ok "$1"; fi; }
+# Octal permission bits. GNU stat spells it -c %a, BSD stat (macOS) -f %OLp;
+# neither accepts the other's flag, so try one then the other.
+perm() { stat -c '%a' "$1" 2>/dev/null || stat -f '%OLp' "$1"; }
 
 echo "── tokenstore ──"
 TMP="$(mktemp -d)"; STORE="$TMP/tokens.json"
@@ -23,9 +26,9 @@ has   "list shows client-a"            "$LIST" '"client-a"'
 has   "list shows client-b"            "$LIST" '"client-b"'
 has   "list shows a property"          "$LIST" 'sc-domain:a.com'
 hasnt "list redacts refresh tokens"    "$LIST" 'RT_AAA'
-PERM="$(stat -c '%a' "$STORE")"
+PERM="$(perm "$STORE")"
 [ "$PERM" = "600" ] && ok "store file is 0600" || no "store file 0600" "got $PERM"
-DPERM="$(stat -c '%a' "$(dirname "$STORE")")"
+DPERM="$(perm "$(dirname "$STORE")")"
 [ "$DPERM" = "700" ] && ok "store dir is 0700" || no "store dir 0700" "got $DPERM"
 rm -rf "$TMP"
 
@@ -57,12 +60,363 @@ has "queries position field"     "$Q" '"position": 6.3'
 I="$(SEO_DATA_MOCK_DIR="$MOCK" python3 "$SD/google_seo.py" inspect \
   --store "$S2" --account client-a --property sc-domain:ex.com --url https://ex.com/x)"
 has "inspect indexed true"       "$I" '"indexed": true'
+# rich_results rides the same URL-Inspection response (no extra call/quota)
+has "rich verdict surfaced"      "$I" '"verdict": "FAIL"'
+has "rich type breadcrumbs"      "$I" '"type": "Breadcrumbs"'
+has "rich type faq"              "$I" '"type": "FAQ"'
+has "rich counts error severity" "$I" '"errors": 2'
+has "rich counts warn severity"  "$I" '"warnings": 1'
+has "rich keeps issue message"   "$I" "Missing field 'acceptedAnswer'"
+# same issueMessage repeats across items — the rollup must collapse it to one
+NMSG="$(printf '%s' "$I" | grep -cF "Missing field 'acceptedAnswer'")"
+[ "$NMSG" = "1" ] && ok "rich dedupes issue messages" \
+                  || no "rich dedupes issue messages" "got $NMSG occurrences"
+# Google OMITS richResultsResult when it detects none — absence is data, and
+# must not KeyError nor vanish into a missing key
+NR="$(SEO_DATA_MOCK_DIR="$SD/fixtures-norich" python3 "$SD/google_seo.py" inspect \
+  --store "$S2" --account client-a --property sc-domain:ex.com --url https://ex.com/x)"
+has "no-rich → synthetic ABSENT" "$NR" '"verdict": "ABSENT"'
+has "no-rich keeps index status" "$NR" '"indexed": true'
+hasnt "no-rich emits no PARTIAL" "$NR" 'PARTIAL'
 DEG="$(env -u SEO_DATA_MOCK_DIR python3 "$SD/google_seo.py" queries \
   --store "$TMP2/none.json" --account nobody --property sc-domain:ex.com)"
 has "gsc degrades w/o creds"     "$DEG" '"status": "degraded"'
 has "gsc degrade reason"         "$DEG" 'no_credentials'
 rm -rf "$TMP2"
 
+echo "── cannibalisation ──"
+# `keys` is additive: the single-dim consumer that reads `key` must not break
+has "queries keeps key (compat)"  "$Q" '"key": "plombier paris"'
+has "queries adds keys list"      "$Q" '"keys"'
+CAN="$(SEO_DATA_MOCK_DIR="$SD/fixtures-cannibal" python3 "$SD/google_seo.py" cannibal \
+  --store "$S2" --account client-a --property sc-domain:ex.com)"
+has "cannibal ok"                 "$CAN" '"status": "ok"'
+# fixture: 3 pages on "urgence fuite", 2 on "plombier paris", 1 on "devis"
+has "cannibal finds 2 conflicts"  "$CAN" '"conflict_count": 2'
+has "cannibal counts pages"       "$CAN" '"pages": 3'
+has "cannibal sums impressions"   "$CAN" '"total_impressions": 2400'
+hasnt "single-page query is not a conflict" "$CAN" 'devis plomberie'
+# biggest conflict first, and inside it the strongest page first
+CAN_FIRST="$(printf '%s' "$CAN" | python3 -c 'import sys,json; d=json.load(sys.stdin); print(d["conflicts"][0]["query"], d["conflicts"][0]["urls"][0]["url"])')"
+check_first() { [ "$1" = "$2" ] && ok "$3" || no "$3" "got[$1]"; }
+check_first "$CAN_FIRST" "urgence fuite https://ex.com/urgence" "cannibal ranks by impact"
+has "cannibal reports the cap"    "$CAN" '"capped": false'
+
+echo "── safe_fetch (DNS-rebinding / SSRF) ──"
+# Inject a hostile resolver: the name is public, the address is internal. This
+# is the rebinding vector a name-level guard cannot see — prove it is refused
+# BEFORE any connection. Deterministic + offline via the injected resolver.
+sfpy() { PYTHONPATH="$SD" python3 -c "$1" 2>&1; }
+REBIND="$(sfpy '
+import socket, safe_fetch as sf
+def meta(h,p,**k): return [(socket.AF_INET,socket.SOCK_STREAM,6,"",("169.254.169.254",p))]
+try: sf.safe_fetch("https://evil.example/", resolver=meta); print("CONNECTED")
+except sf.UnsafeTarget as e: print("REFUSED", e)')"
+has "rebind to metadata refused"  "$REBIND" 'REFUSED'
+has "refusal names the ip"        "$REBIND" '169.254.169.254'
+hasnt "never connected"           "$REBIND" 'CONNECTED'
+MIXED="$(sfpy '
+import socket, safe_fetch as sf
+def mix(h,p,**k): return [(socket.AF_INET,socket.SOCK_STREAM,6,"",("93.184.216.34",p)),
+                          (socket.AF_INET,socket.SOCK_STREAM,6,"",("127.0.0.1",p))]
+try: sf.safe_fetch("https://evil.example/", resolver=mix); print("CONNECTED")
+except sf.UnsafeTarget as e: print("REFUSED")')"
+has "multi-A public+private refused" "$MIXED" 'REFUSED'
+# classification, dual-stack — is_global catches CGNAT the per-flags miss
+CLS="$(sfpy '
+import safe_fetch as sf
+pub=[c for c in ["8.8.8.8","2606:2800:220:1:248:1893:25c8:1946"] if sf._ip_is_public(c)]
+bad=[c for c in ["169.254.169.254","127.0.0.1","10.0.0.1","192.168.1.1","100.64.1.1","::1","fe80::1","0.0.0.0"] if sf._ip_is_public(c)]
+print("PUB",len(pub),"BADPASS",len(bad))')"
+has "public v4+v6 pass"           "$CLS" 'PUB 2'
+has "no internal ip passes"       "$CLS" 'BADPASS 0'
+# security review 2026-07-17: 6to4-relay anycast passes is_global — extra deny
+SIXTOFOUR="$(sfpy 'import safe_fetch as sf; print("6TO4", sf._ip_is_public("192.88.99.1"))')"
+has "6to4 relay anycast refused"  "$SIXTOFOUR" '6TO4 False'
+# scheme + stdlib
+SCHEME="$(sfpy '
+import safe_fetch as sf
+try: sf.safe_fetch("file:///etc/passwd"); print("OK")
+except sf.UnsafeTarget: print("REFUSED")')"
+has "non-http scheme refused"     "$SCHEME" 'REFUSED'
+IMP="$(grep -E "^(import|from) " "$SD/safe_fetch.py" | grep -cvE "gzip|http\.client|ipaddress|socket|ssl|urllib\.parse" | tr -d ' ')"
+[ "$IMP" = "0" ] && ok "safe_fetch is stdlib-only" || no "safe_fetch is stdlib-only" "$IMP non-stdlib imports"
+hasnt "no requests dependency"    "$(cat "$SD/safe_fetch.py")" 'import requests'
+
+echo "── sitemap ──"
+SM="$(SEO_DATA_MOCK_DIR="$MOCK" python3 "$SD/sitemap.py" --url https://ex.com/sitemap.xml)"
+has "sitemap ok"                 "$SM" '"status": "ok"'
+has "sitemap not an index"       "$SM" '"index": false'
+# fixture holds 8 <loc>: 1 empty, blog twice, ftp:// and a quoted one to drop
+has "sitemap dedupes"            "$SM" '"count": 4'
+has "sitemap counts drops"       "$SM" '"dropped": 2'
+has "sitemap strips whitespace"  "$SM" '"https://ex.com/spaced"'
+hasnt "sitemap drops non-http"   "$SM" 'ftp://'
+hasnt "sitemap drops shell-meta" "$SM" 'bad"quote'
+# namespace-agnostic: real sitemaps carry sitemaps.org xmlns (+ xhtml here)
+has "sitemap reads namespaced"   "$SM" '"https://ex.com/services"'
+# REGRESSION: <image:loc> also ends with '}loc'. An endswith test counted image
+# sitemap entries as pages — a real native site returned 27 for 24 <url>, and
+# img/logo.png was about to be sampled and audited as a page.
+hasnt "image:loc is not a page"  "$SM" '/img/logo.png'
+hasnt "image:loc jpeg not a page" "$SM" '/img/hero.jpeg'
+has "image ns does not inflate count" "$SM" '"count": 4'
+
+IDX="$(SEO_DATA_MOCK_DIR="$SD/fixtures-sitemap-index" python3 "$SD/sitemap.py" \
+  --url https://ex.com/sitemap.xml)"
+has "sitemapindex detected"      "$IDX" '"index": true'
+has "sitemapindex fans out"      "$IDX" '"children_read": 2'
+has "sitemapindex no child fail" "$IDX" '"children_failed": 0'
+has "sitemapindex yields urls"   "$IDX" '"https://ex.com/child-a"'
+
+# A sitemap NEVER has a DTD. Refused at the door: xml.etree does not expand
+# external entities but IS billion-laughs-vulnerable, and the 20MB read ceiling
+# bounds the input, not the expansion. Refusing beats depending on the parser,
+# and keeps this module stdlib-only (no defusedxml, no venv).
+DTD="$(SEO_DATA_MOCK_DIR="$SD/fixtures-sitemap-dtd" python3 "$SD/sitemap.py" \
+  --url https://ex.com/sitemap.xml)"
+has "billion-laughs refused"     "$DTD" '"status": "degraded"'
+has "dtd reason is distinct"     "$DTD" 'unsafe_xml_dtd'
+hasnt "dtd never parsed"         "$DTD" '"count"'
+# security review 2026-07-17: a >4KB leading comment pushed <!DOCTYPE past the
+# old raw[:4096] scan while ET still parsed+expanded it. Now the whole doc is
+# scanned. Prove a padded DTD is refused and the entity never expands.
+PADDED="$(python3 -c '
+import sys; sys.path.insert(0,"'"$SD"'"); import sitemap as sm
+bomb=("<?xml version=\"1.0\"?>\n<!-- "+("x"*5000)+" -->\n"
+      "<!DOCTYPE d [ <!ENTITY lol \"lol\"> ]>\n<urlset><url><loc>https://x/&lol;</loc></url></urlset>").encode()
+try: sm._refuse_dtd(bomb); print("PARSED")
+except sm.UnsafeXML: print("REFUSED")')"
+has "padded DTD refused (full scan)" "$PADDED" 'REFUSED'
+
+echo "── render_check (R2) ──"
+SPA="$(SEO_DATA_MOCK_DIR="$SD/fixtures-spa" python3 "$SD/render_check.py" \
+  --url https://spa.example/)"
+has "spa → client-rendered"      "$SPA" '"verdict": "client-rendered"'
+has "spa has no h1 in html"      "$SPA" '"h1_in_html": 0'
+has "spa warns about false negs" "$SPA" 'false'
+# the shell carries a fat window.__INITIAL_STATE__ script: script text is NOT
+# page text, or a 200KB React bundle would read as a rich page
+has "script text is not content" "$SPA" '"body_text_chars": 7'
+SSR="$(SEO_DATA_MOCK_DIR="$SD/fixtures-ssr" python3 "$SD/render_check.py" \
+  --url https://ssr.example/)"
+has "ssr → server-rendered"      "$SSR" '"verdict": "server-rendered"'
+has "ssr counts jsonld"          "$SSR" '"jsonld_in_html": 1'
+has "ssr sees meta description"  "$SSR" '"meta_description_in_html": true'
+hasnt "ssr emits no warning"     "$SSR" 'warning'
+
+echo "── linkgraph ──"
+LG="$(SEO_DATA_MOCK_DIR="$SD/fixtures-linkgraph" python3 "$SD/linkgraph.py" \
+  --url https://ex.com/sitemap.xml)"
+has "linkgraph ok"               "$LG" '"status": "ok"'
+has "linkgraph crawls all"       "$LG" '"pages_crawled": 7'
+# THE test: a planted page nobody links to must be found. Two live sites both
+# returned zero orphans; without this, "always returns []" looks identical.
+has "finds the planted orphan"   "$LG" '"https://ex.com/orphan"'
+has "orphan is also unreachable" "$LG" '"unreachable"'
+has "depth chain measured"       "$LG" '"max_depth": 4'
+has "flags >3 clicks"            "$LG" '"https://ex.com/deepest"'
+# home links: /a and /b only. anchor, .css?v=, mailto:, tel:, external, .png
+# are not page links — 9 total across the 7 pages.
+has "filters non-page links"     "$LG" '"total_internal_links": 9'
+hasnt "no external host"         "$LG" 'other.com'
+hasnt "no asset link"            "$LG" 'main.css'
+hasnt "no image link"            "$LG" 'logo.png'
+# /b/ in the markup vs /b in the sitemap must be ONE node, not a phantom orphan
+hasnt "trailing slash unified"   "$LG" '"https://ex.com/b/"'
+
+# An orphan from a partial crawl is a false orphan: withhold, do not truncate.
+CAP="$(SEO_DATA_MOCK_DIR="$SD/fixtures-linkgraph" python3 "$SD/linkgraph.py" \
+  --url https://ex.com/sitemap.xml --max 3)"
+has "cap is reported"            "$CAP" '"capped": true'
+has "capped withholds orphans"   "$CAP" '"orphans_withheld": true'
+hasnt "capped emits no orphans"  "$CAP" '"orphans":'
+
+echo "── score (I7) ──"
+sc() { printf '%s' "$1" | python3 "$SD/score.py" --findings -; }
+# technical: haute(-8) + moyenne(-3) = 100-11 = 89 → 17.8
+B='{"depth":"FULL","profile":"local","axes":{"technical":{"findings":[{"severity":"haute"},{"severity":"moyenne"}]},"seo-local":{"findings":[]},"off-page":{"findings":[]},"social":{"findings":[]},"competitive":{"findings":[]},"legal":{"findings":[]},"on-page":{"findings":[]}}}'
+R="$(sc "$B")"
+has "harden scale, /5 into /20"   "$R" '"score_20": 17.8'
+has "no findings = 20"            "$R" '"score_20": 20.0'
+has "nothing renormalised"        "$R" '"weights_renormalised": false'
+# THE point of I7: same findings in, same score out
+A1="$(sc "$B" | python3 -c 'import sys,json;print(json.load(sys.stdin)["global_20"])')"
+A2="$(sc "$B" | python3 -c 'import sys,json;print(json.load(sys.stdin)["global_20"])')"
+[ "$A1" = "$A2" ] && ok "score is reproducible" || no "score is reproducible" "$A1 vs $A2"
+# N/A is not a zero, and R2 mandated renormalising by hand — now computed
+NA='{"depth":"FULL","profile":"local","axes":{"technical":{"findings":[]},"on-page":{"status":"na"},"seo-local":{"findings":[]},"off-page":{"status":"na"},"social":{"findings":[]},"competitive":{"findings":[]},"legal":{"findings":[]}}}'
+RN="$(sc "$NA")"
+has "na axes listed"             "$RN" '"on-page"'
+has "renormalisation flagged"    "$RN" '"weights_renormalised": true'
+# all axes 20 → global must stay 20: N/A must not drag the mean down
+has "na is not a zero"           "$RN" '"global_20": 20.0'
+# prevalence shifts severity ONE step, both ways
+WIDE='{"depth":"LOCAL","profile":"local","axes":{"technical":{"findings":[{"severity":"moyenne","affected":10,"sampled":12}]},"on-page":{"findings":[]},"seo-local":{"findings":[]},"legal":{"findings":[]}}}'
+ONE='{"depth":"LOCAL","profile":"local","axes":{"technical":{"findings":[{"severity":"moyenne","affected":1,"sampled":12}]},"on-page":{"findings":[]},"seo-local":{"findings":[]},"legal":{"findings":[]}}}'
+has "widespread escalates (-8)"  "$(sc "$WIDE")" '"score_20": 18.4'
+has "isolated de-escalates (-1)" "$(sc "$ONE")"  '"score_20": 19.8'
+# malformed input is an error, never a silently wrong number
+has "unknown severity rejected"  "$(sc '{"depth":"FULL","profile":"local","axes":{"technical":{"findings":[{"severity":"bogus"}]}}}')" '"status": "error"'
+has "unknown profile rejected"   "$(sc '{"depth":"FULL","profile":"martian","axes":{}}')" '"status": "error"'
+has "garbage json is an error"   "$(sc 'not json')" '"status": "error"'
+
+echo "── drift (H2) ──"
+DH="$(mktemp -d)"
+D1="$(HOME="$DH" SEO_DATA_MOCK_DIR="$SD/fixtures-drift-v1" python3 "$SD/drift.py" \
+  --url https://ex.com/sitemap.xml)"
+has "first run is a baseline"    "$D1" '"baseline": true'
+has "baseline captures pages"    "$D1" '"pages": 3'
+hasnt "baseline diffs nothing"   "$D1" '"regressions"'
+# v2: canonical lost on /a, h1+jsonld lost on /, title reworded, /gone removed,
+# /neuve added. Losses are regressions; a reworded title is not.
+D2="$(HOME="$DH" SEO_DATA_MOCK_DIR="$SD/fixtures-drift-v2" python3 "$SD/drift.py" \
+  --url https://ex.com/sitemap.xml)"
+has "second run diffs"           "$D2" '"baseline": false'
+has "detects removed url"        "$D2" '"https://ex.com/gone"'
+has "detects added url"          "$D2" '"https://ex.com/neuve"'
+has "lost canonical = regression" "$D2" '"canonical"'
+has "lost h1 = regression"       "$D2" '"h1_count"'
+has "lost jsonld = regression"   "$D2" '"jsonld_types"'
+# the classification IS the feature: losing a signal != changing one
+NREG="$(printf '%s' "$D2" | python3 -c 'import sys,json; print(len(json.load(sys.stdin)["regressions"]))')"
+NCHG="$(printf '%s' "$D2" | python3 -c 'import sys,json; print(len(json.load(sys.stdin)["changes"]))')"
+[ "$NREG" = "3" ] && ok "3 losses classed as regressions" \
+                  || no "3 losses classed as regressions" "got $NREG"
+[ "$NCHG" = "1" ] && ok "reworded title is a change, not a regression" \
+                  || no "reworded title is a change, not a regression" "got $NCHG"
+rm -rf "$DH"
+
+echo "── schema_gen ──"
+SG() { python3 "$SD/schema_gen.py" "$@"; }
+RES="$(SG reservation --provider "Chez X" --start "2026-08-01T19:00")"
+has "reservation ok"             "$RES" '"status": "ok"'
+has "reservation type surfaced"  "$RES" '"type": "FoodEstablishmentReservation"'
+has "jsonld has @context"        "$RES" '"@context": "https://schema.org"'
+has "reservation keeps provider" "$RES" 'Chez X'
+has "reservation keeps start"    "$RES" '2026-08-01T19:00'
+PROF="$(SG profile --name "Jane Doe" --url https://ex.com/about)"
+has "profile ok"                 "$PROF" '"status": "ok"'
+has "profile type surfaced"      "$PROF" '"type": "ProfilePage"'
+ORD="$(SG order --merchant "Acme" --order-url https://ex.com/order)"
+has "order ok"                   "$ORD" '"status": "ok"'
+has "order type surfaced"        "$ORD" '"type": "OrderAction"'
+DISC="$(SG discussion --headline "Q" --author "Jo" --url https://ex.com/t/1 \
+  --date 2026-05-01T00:00:00Z)"
+has "discussion ok"              "$DISC" '"status": "ok"'
+has "discussion type surfaced"   "$DISC" '"type": "DiscussionForumPosting"'
+# argparse required=True catches an OMITTED flag → bad usage, exit 2
+BADRES="$(SG reservation --start 2026-08-01T19:00 2>/dev/null)"; BADRC=$?
+hasnt "missing --provider is not ok" "$BADRES" '"status": "ok"'
+[ "$BADRC" = "2" ] && ok "missing --provider exit 2" \
+                    || no "missing --provider exit 2" "got $BADRC"
+# a required field argparse ALLOWS through (flag given, value empty) must
+# still fail open — degraded, not a crash, exit 0
+EMPTYRES="$(SG reservation --provider "" --start 2026-08-01T19:00)"; EMPTYRC=$?
+hasnt "empty --provider is not ok" "$EMPTYRES" '"status": "ok"'
+has "empty --provider degrades"  "$EMPTYRES" '"status": "degraded"'
+[ "$EMPTYRC" = "0" ] && ok "empty --provider exit 0" \
+                      || no "empty --provider exit 0" "got $EMPTYRC"
+# --script-tag must work AFTER the type, matching `fetch.sh schema_gen
+# <type> [flags]` — the shape the dispatcher actually calls it with. The
+# envelope is JSON, so the `script` field's own quotes are backslash-escaped
+# in the raw stdout — decode it to check the LITERAL wrapper string.
+SCRIPT="$(SG profile --name "Jane Doe" --url https://ex.com/about --script-tag)"
+SCRIPT_TAG="$(printf '%s' "$SCRIPT" | \
+  python3 -c 'import sys,json; print(json.load(sys.stdin)["script"])')"
+has "script-tag wraps output" "$SCRIPT_TAG" '<script type="application/ld+json">'
+# an omitted optional field must never surface as a JSON null
+hasnt "no null ever emitted"     "$RES" 'null'
+# stdlib ONLY — no requests/httpx/bs4/any third-party import
+IMPORTS="$(grep -E '^(import|from) ' "$SD/schema_gen.py")"
+if printf '%s' "$IMPORTS" | grep -qiE 'requests|httpx|bs4'; then
+  no "schema_gen stdlib only" "third-party import found: $IMPORTS"
+else
+  ok "schema_gen stdlib only"
+fi
+# dispatch wiring: --store precedes the type (fetch.sh's own convention),
+# --script-tag comes after it (the caller's convention) — both must work
+# through the real fetch.sh entrypoint, not just the bare script
+FSG="$(SEO_DATA_ENV_FILE=/dev/null SEO_DATA_STORE=/nonexistent bash "$SD/fetch.sh" \
+  schema_gen reservation --provider "Chez X" --start 2026-08-01T19:00 --script-tag)"
+has "fetch dispatches schema_gen" "$FSG" '"status": "ok"'
+FSG_TAG="$(printf '%s' "$FSG" | \
+  python3 -c 'import sys,json; print(json.load(sys.stdin)["script"])')"
+has "fetch schema_gen script-tag" "$FSG_TAG" '<script type="application/ld+json">'
+
+echo "── content_quality ──"
+CQ() { python3 "$SD/content_quality.py" "$@"; }
+# feed the phrase list's OWN entries so the match is exact, not paraphrased —
+# a detector proven only on the maintainer's paraphrase proves nothing
+FILLER_TXT="In today's fast-paced world, it's important to note that this \
+article will delve into the ever-evolving landscape of technology. Let's \
+dive in and navigate the complexities together, leveraging the power of \
+innovation to unlock the potential of your business. Ultimately, this \
+cutting-edge, state-of-the-art approach is a testament to progress. \
+Moreover, furthermore, in conclusion, transform your outcomes today."
+CLEAN_TXT="The 2024 ADEME report found French households spent 2,137 EUR \
+on heating, up 12% from 2021."
+FILLER_OUT="$(printf '%s' "$FILLER_TXT" | CQ)"
+CLEAN_OUT="$(printf '%s' "$CLEAN_TXT" | CQ)"
+has "filler text is ok"          "$FILLER_OUT" '"status": "ok"'
+has "clean text is ok"           "$CLEAN_OUT"  '"status": "ok"'
+# flags is a JSON array — extract it in isolation so the check can't be
+# fooled by the always-present "matches": {"filler": [...]} key sharing
+# the same quoted word
+FILLER_FLAGS="$(printf '%s' "$FILLER_OUT" | \
+  python3 -c 'import sys,json; print(",".join(json.load(sys.stdin)["flags"]))')"
+CLEAN_FLAGS="$(printf '%s' "$CLEAN_OUT" | \
+  python3 -c 'import sys,json; print(",".join(json.load(sys.stdin)["flags"]))')"
+case "$FILLER_FLAGS" in
+  *filler*|*ai-patterns*) ok "filler-heavy text is flagged" ;;
+  *) no "filler-heavy text is flagged" "flags: $FILLER_FLAGS" ;;
+esac
+hasnt "clean text is not flagged filler"      "$CLEAN_FLAGS" 'filler'
+hasnt "clean text is not flagged ai-patterns" "$CLEAN_FLAGS" 'ai-patterns'
+# proves BOTH directions: an always-flag or a never-flag detector is useless
+FILLER_Q="$(printf '%s' "$FILLER_OUT" | \
+  python3 -c 'import sys,json; print(json.load(sys.stdin)["overall_quality"])')"
+CLEAN_Q="$(printf '%s' "$CLEAN_OUT" | \
+  python3 -c 'import sys,json; print(json.load(sys.stdin)["overall_quality"])')"
+[ "$FILLER_Q" -lt 50 ] && ok "filler-heavy text scores LOW overall_quality" \
+                        || no "filler-heavy text scores LOW overall_quality" "got $FILLER_Q"
+[ "$CLEAN_Q" -gt "$FILLER_Q" ] && ok "clean dense text scores higher" \
+                                || no "clean dense text scores higher" "$CLEAN_Q vs $FILLER_Q"
+# empty / whitespace-only input never crashes and never claims a result
+EMPTY_OUT="$(printf '' | CQ)"
+has "empty input degrades"       "$EMPTY_OUT" '"status": "degraded"'
+has "empty input reason"         "$EMPTY_OUT" 'empty_input'
+WS_OUT="$(printf '   \n\t ' | CQ)"
+has "whitespace-only degrades"   "$WS_OUT" '"status": "degraded"'
+# --file path works, no fixture committed — mktemp + rm
+CQTMP="$(mktemp)"; printf '%s' "$CLEAN_TXT" > "$CQTMP"
+FILE_OUT="$(CQ --file "$CQTMP")"
+has "file input is ok"           "$FILE_OUT" '"status": "ok"'
+rm -f "$CQTMP"
+# a missing --file degrades, never a traceback
+MISSING_OUT="$(CQ --file /nonexistent/path/content-quality-test.txt)"
+has "missing --file degrades"    "$MISSING_OUT" '"status": "degraded"'
+# stdlib ONLY — asserted, not assumed
+CQ_IMPORTS="$(grep -E '^(import|from) ' "$SD/content_quality.py")"
+if printf '%s' "$CQ_IMPORTS" | grep -qivE '^(import argparse, json, re, sys|from collections import counter|from typing import iterable)$'; then
+  no "content_quality stdlib only" "unexpected import: $CQ_IMPORTS"
+else
+  ok "content_quality stdlib only"
+fi
+# ADVISORY HONESTY (LRN-131/133): a heuristic signal, never a verdict
+hasnt "never claims ai-written"  "$FILLER_OUT" 'ai-written'
+hasnt "never claims is AI verdict" "$FILLER_OUT" 'is AI'
+# dispatch wiring: --store precedes the verb (fetch.sh's own convention);
+# both stdin AND --file must work through the real entrypoint
+FCQ_STDIN="$(printf '%s' "$CLEAN_TXT" | \
+  SEO_DATA_ENV_FILE=/dev/null SEO_DATA_STORE=/nonexistent bash "$SD/fetch.sh" content_quality)"
+has "fetch dispatches content_quality (stdin)" "$FCQ_STDIN" '"status": "ok"'
+CQTMP2="$(mktemp)"; printf '%s' "$CLEAN_TXT" > "$CQTMP2"
+FCQ_FILE="$(SEO_DATA_ENV_FILE=/dev/null SEO_DATA_STORE=/nonexistent bash "$SD/fetch.sh" \
+  content_quality --file "$CQTMP2")"
+has "fetch dispatches content_quality (--file)" "$FCQ_FILE" '"status": "ok"'
+rm -f "$CQTMP2"
+
 echo "── fetch.sh ──"
 FETCH="$SD/fetch.sh"
 # SEO_DATA_ENV_FILE=/dev/null: tests must NEVER source the real ~/.claude/.env —
@@ -126,7 +480,7 @@ has   "clear reports ok"         "$CL" '"status": "ok"'
 has   "clear reports count"      "$CL" '"cleared": 1'
 L7="$(python3 "$SD/tokenstore.py" list --file "$S6")"
 has   "clear empties store"      "$L7" '"accounts": []'
-PERM6="$(stat -c '%a' "$S6")"
+PERM6="$(perm "$S6")"
 [ "$PERM6" = "600" ] && ok "store stays 0600 after clear" || no "store 0600 after clear" "got $PERM6"
 # via the real fetch.sh dispatch layer
 python3 "$SD/tokenstore.py" set --file "$S6" --label back --refresh-token RT_BACK \
@@ -188,6 +542,8 @@ tf "analyzer calls fetch crux"  "$REPO/agents/seo-analyzer.md"   "fetch.sh crux"
 tf "analyzer calls fetch queries" "$REPO/agents/seo-analyzer.md" "fetch.sh queries"
 tf "analyzer gsc subsection"    "$REPO/agents/seo-analyzer.md"   "Performance GSC"
 tf "catalog gsc oauth entry"    "$REPO/agents/resources/automation-catalog.md" "make seo-connect"
+tf "geo-analyzer wires schema_gen" "$REPO/agents/geo-analyzer.md" "fetch.sh schema_gen"
+tf "geo-analyzer wires content_quality" "$REPO/agents/geo-analyzer.md" "fetch.sh content_quality"
 
 echo "── account-mgmt locks ──"
 tf "skill routes account verbs" "$REPO/skills/seo/SKILL.md" "forget --all"
@@ -200,6 +556,9 @@ tf "readme documents fetch.sh" "$REPO/lib/seo-data/README.md" "fetch.sh"
 tf "readme documents seo-connect" "$REPO/lib/seo-data/README.md" "make seo-connect"
 tf "readme documents forget"   "$REPO/lib/seo-data/README.md" "forget --all"
 tf "readme revocation note"    "$REPO/lib/seo-data/README.md" "myaccount.google.com/permissions"
+tf "readme documents schema_gen" "$REPO/lib/seo-data/README.md" "schema_gen"
+tf "readme documents content_quality" "$REPO/lib/seo-data/README.md" "content_quality"
+tf "readme states advisory caveat" "$REPO/lib/seo-data/README.md" "ADVISORY, NOT A VERDICT"
 
 echo ""
 echo "seo-data engine: $PASS pass, $FAIL fail"

lib/seo-data/sitemap.py

@@ -0,0 +1,191 @@
+#!/usr/bin/env python3
+"""Sitemap discovery -> normalized JSON. Stdlib only: no venv, no requests, no
+auth. Gives STEP 9 COVERAGE the denominator it was told to report and never
+had, and STEP 5 a real sampling frame instead of "5-15 key pages" chosen by
+eye.
+
+Deliberately NOT a security boundary. urllib fetches these URLs, so nothing
+here reaches a shell and there is no injection surface to guard. The consumer
+is different: seo-analyzer interpolates URLs into curl, so IT must run
+lib/url-guard.sh at the point of use (same pattern as the sameAs check).
+Duplicating the guard here would just add a second copy to drift. `_sane`
+below is a cheap garbage filter, not that guard.
+"""
+import argparse, gzip, json, os
+from urllib.parse import urlparse
+
+MAX_URLS = 50000      # sitemaps.org caps one file at 50k
+MAX_CHILDREN = 50     # sitemapindex fan-out cap: bound the work, report the cut
+TIMEOUT = 20
+
+def _mock(name):
+    d = os.environ.get("SEO_DATA_MOCK_DIR")
+    if not d:
+        return None
+    path = os.path.join(d, name)
+    if not os.path.exists(path):
+        return None
+    with open(path, "rb") as f:
+        return f.read()
+
+def _fetch(url):
+    # SSRF + DNS-rebinding safe: resolve-then-pin, redirects re-validated.
+    # This is the single seam for ALL network egress — linkgraph/render_check/
+    # drift all call sitemap._fetch — so pinning here covers every verb.
+    import safe_fetch                                # sibling, lazy
+    raw = safe_fetch.safe_fetch(url, timeout=TIMEOUT, max_bytes=20 * 1024 * 1024)
+    if raw[:2] == b"\x1f\x8b":                       # sitemap.xml.gz is common
+        raw = gzip.decompress(raw)
+    return raw
+
+class UnsafeXML(Exception):
+    """A DTD reached the parser. Refused before parsing, not mitigated after."""
+
+def _refuse_dtd(raw):
+    """A sitemap NEVER has a DTD: sitemaps.org is <?xml?> then <urlset xmlns=>.
+    So refuse any doctype/entity outright, at the door.
+
+    This is the reason we do not pull in defusedxml. The stdlib parser is not
+    the problem for XXE — xml.etree.ElementTree does not expand external
+    entities, it raises on them — but it IS vulnerable to billion-laughs, where
+    a 1 KB document expands to gigabytes in RAM. The 20 MB read ceiling bounds
+    the input, not the expansion. Rejecting the construct beats depending on
+    the parser's internals, and keeps this module stdlib-only: no venv, same as
+    google_seo.py's mock/degrade paths. A sitemap with a DTD is not a sitemap
+    we want anyway.
+    """
+    # Scan the WHOLE document, not a prefix. A security review (2026-07-17)
+    # showed a >4 KB leading comment pushed <!DOCTYPE past the old raw[:4096]
+    # window while ET.fromstring still parsed and EXPANDED the entities —
+    # billion-laughs reopened. A legitimate sitemap contains neither construct
+    # anywhere, so a full case-insensitive scan is correct; over ≤20 MB it is a
+    # single re.search, microseconds, no 20 MB uppercased copy.
+    import re                                       # stdlib, lazy
+    if re.search(rb"(?i)<!\s*(DOCTYPE|ENTITY)", raw):
+        raise UnsafeXML("DTD in sitemap")
+
+SITEMAP_NS = "{http://www.sitemaps.org/schemas/sitemap/0.9}"
+
+def _is_page_loc(tag):
+    """A PAGE <loc>: sitemaps.org namespace, or namespace-less.
+
+    NOT <image:loc> or <video:loc>. Those live in Google's extension
+    namespaces and name an ASSET inside a <url>, not a page of its own. An
+    endswith('}loc') test matches them too — that shipped, and a real site
+    caught it: 24 <url> + 3 <image:loc> came back as a count of 27, so the
+    COVERAGE denominator was 12.5% too high and img/logo.png was about to be
+    sampled and audited as a page.
+    """
+    return tag == SITEMAP_NS + "loc" or tag == "loc"
+
+def _locs(raw):
+    """(page <loc> texts, is_sitemapindex).
+
+    Walks the DIRECT children of each <url>/<sitemap> rather than root.iter():
+    that alone excludes <image:image><image:loc>, and the namespace test above
+    is the second lock. XML comments iterate as elements with no children, so
+    they fall through harmlessly.
+    """
+    import xml.etree.ElementTree as ET               # stdlib, lazy
+    _refuse_dtd(raw)
+    root = ET.fromstring(raw)
+    is_index = root.tag.endswith("sitemapindex")
+    out = []
+    for entry in root:                               # <url> | <sitemap>
+        for child in entry:                          # direct children only
+            if _is_page_loc(child.tag):
+                text = (child.text or "").strip()
+                if text:
+                    out.append(text)
+                break                                # one <loc> per entry
+    return out, is_index
+
+def _sane(u):
+    """Cheap garbage filter — NOT lib/url-guard.sh. Drops what could never be a
+    real page URL; the consumer still guards before curling."""
+    if not u or len(u) > 2048:
+        return False
+    if any(c in u for c in '\n\r\t "\'\\`$<>{}|^'):
+        return False
+    return urlparse(u).scheme in ("http", "https")
+
+def _expand(children):
+    """Fetch each child sitemap of an index. A child that fails is skipped and
+    counted, never fatal: one dead child must not lose the other 49."""
+    urls, ok, failed = [], 0, 0
+    for c in children:
+        raw = _mock("sitemap_child.xml")
+        if raw is None:
+            try:
+                raw = _fetch(c)
+            except Exception:
+                failed += 1
+                continue
+        try:
+            sub, _ = _locs(raw)
+        except Exception:
+            failed += 1
+            continue
+        urls.extend(sub)
+        ok += 1
+    return urls, ok, failed
+
+def sitemap(url):
+    raw = _mock("sitemap.xml")
+    if raw is None:
+        try:
+            raw = _fetch(url)
+        except Exception:
+            return {"status": "degraded", "reason": "fetch_failed"}
+    try:
+        locs, is_index = _locs(raw)
+    except UnsafeXML:
+        # Distinct from parse_failed on purpose: this one is a finding, not a
+        # glitch. A sitemap carrying a DTD is either broken tooling or someone
+        # aiming a billion-laughs at the auditor.
+        return {"status": "degraded", "reason": "unsafe_xml_dtd"}
+    except Exception:
+        return {"status": "degraded", "reason": "parse_failed"}
+    out = {"status": "ok", "source": "sitemap", "index": is_index}
+    if is_index:
+        out["children_total"] = len(locs)
+        kids, ok, failed = _expand(locs[:MAX_CHILDREN])
+        out["children_read"], out["children_failed"] = ok, failed
+        if len(locs) > MAX_CHILDREN:                 # say what was cut
+            out["children_skipped"] = len(locs) - MAX_CHILDREN
+        locs = kids
+    seen, urls, dropped = set(), [], 0
+    for u in locs:
+        if not _sane(u):
+            dropped += 1
+            continue
+        if u in seen:
+            continue
+        seen.add(u)
+        urls.append(u)
+    if len(urls) > MAX_URLS:
+        out["truncated"] = len(urls) - MAX_URLS
+        urls = urls[:MAX_URLS]
+    out["count"], out["dropped"], out["urls"] = len(urls), dropped, urls
+    if not urls:
+        return {"status": "degraded", "reason": "no_urls"}
+    return out
+
+def _cli():
+    try:
+        p = argparse.ArgumentParser()
+        p.add_argument("--url", required=True)
+        p.add_argument("--store", default=None)   # accepted+ignored: uniform dispatch
+        args = p.parse_args()
+        print(json.dumps(sitemap(args.url), indent=2))
+    except SystemExit as e:
+        if e.code not in (0, None):
+            print(json.dumps({"status": "error", "reason": "bad_usage"}))
+        raise
+    except Exception:
+        # Same fail-open contract as google_seo.py: never a traceback, never
+        # empty stdout, exit 0 so the audit degrades instead of dying.
+        print(json.dumps({"status": "degraded", "reason": "unexpected_error"}))
+
+if __name__ == "__main__":
+    _cli()

lib/source-scope.sh

@@ -0,0 +1,82 @@
+#!/usr/bin/env bash
+# Emit the directory exclusions that separate SOURCE from BUILD OUTPUT.
+#
+#   EXCL="$(bash ~/.claude/lib/source-scope.sh grep)"
+#   grep -rl "gtag" $EXCL --include="*.html" .          # note: $EXCL unquoted
+#
+#   FEXCL=(); while IFS= read -r t; do FEXCL+=("$t"); done \
+#     < <(bash ~/.claude/lib/source-scope.sh findargs)
+#   (a read loop, not mapfile: macOS /bin/bash is 3.2 and has no mapfile)
+#   find . "${FEXCL[@]}" -iname '*.jpg' -printf '%s %p\n'   # quoted array!
+#
+# findargs emits ONE TOKEN PER LINE and MUST be consumed through a quoted
+# array. A flat string does not work: `find . $FEXCL ...` lets the shell glob
+# `*/dist/*` against the CWD before find ever sees it, and the matches are then
+# passed as search PATHS. Measured on zenquality: that turned 90 hits into 135
+# and kept every dist/ file. The array form passes each token literally.
+#
+# WHY: grep and find disagree about what is in the repo, and seo-analyzer uses
+# both.
+#
+#   grep  → Claude Code installs a shell function routing grep to ugrep with
+#           `--ignore-files`, i.e. .gitignore-aware. A gitignored dist/ is
+#           invisible to it when recursing from `.`. Verified 2026-07-17.
+#   find  → knows nothing about .gitignore. It sees everything.
+#
+# So on zenquality (Astro, dist/ gitignored, built locally) the spec's image
+# audit at seo-analyzer.md:497 returns 92 images of which 45 live in dist/ —
+# every asset listed twice, source and generated copy, identical bytes. Two
+# real consequences:
+#   1. "top 20 by size" is half generated duplicates: ~10 real images audited
+#      while 20 are claimed.
+#   2. Batch C (`cwebp -q 80 <img> -o <img>.webp`) can target dist/og-image.png.
+#      The .webp lands in dist/ and the `npm run build` that /seo runs to VERIFY
+#      the fix erases it. The fix lands, verification passes, nothing survives.
+#
+# The grep side is already safe by accident — do NOT "fix" it to match find.
+# `grep` mode below is defence in depth for the cases the shim misses: a repo
+# that COMMITS its build output (no .gitignore entry to honour), or a directory
+# that is not a git repo at all.
+#
+# `public/` is deliberately NOT in the always-list: it is SOURCE for
+# Astro/Vite/Next and holds the very files this audit checks — favicon.ico,
+# apple-touch-icon.png, robots.txt, OG images. It is build OUTPUT only for
+# Hugo and Gatsby, detected below. Blanket-excluding it would blind the audit
+# to its own resource checks.
+#
+# Exclusions are by NAME, not path, so a monorepo's frontend/dist is caught
+# exactly like a root ./dist.
+set -uo pipefail
+
+_die() { echo "source-scope: $1" >&2; exit 2; }
+
+# Build output + tool caches. Never source.
+ALWAYS=(node_modules .git dist build .next .nuxt .output _site .astro
+        .svelte-kit .cache out coverage .vercel .netlify .turbo)
+
+# public/ is output for exactly these two generators.
+_public_is_output() {
+  find . -maxdepth 3 \( -name "gatsby-config.js" -o -name "gatsby-config.ts" \
+    -o -name "gatsby-config.mjs" -o -name "hugo.toml" -o -name "hugo.yaml" \
+    -o -name "hugo.json" \) 2>/dev/null | read -r _ && return 0
+  # Hugo's legacy config.toml is ambiguous on its own — pair it with archetypes/
+  [ -d ./archetypes ] && [ -f ./config.toml ] && return 0
+  return 1
+}
+
+_list() {
+  printf '%s\n' "${ALWAYS[@]}"
+  _public_is_output && printf 'public\n'
+  return 0
+}
+
+case "${1:-}" in
+  list) _list ;;
+  # Safe unquoted: --exclude-dir=NAME carries no glob character.
+  grep) _list | while read -r d; do printf -- '--exclude-dir=%s ' "$d"; done; echo ;;
+  # One token per line — consume with a read loop into a QUOTED array (see
+  # the header: mapfile is bash 4+), never a flat
+  # string (see header: the shell would glob */dist/* against the CWD).
+  findargs) _list | while read -r d; do printf '!\n-path\n*/%s/*\n' "$d"; done ;;
+  *) _die "usage: source-scope.sh {list|grep|findargs}" ;;
+esac

lib/tests/config-protection.test.sh

@@ -1,74 +0,0 @@
-#!/usr/bin/env bash
-# lib/tests/config-protection.test.sh
-set -u
-H="$(cd "$(dirname "$0")/../.." && pwd)/hooks/config-protection.sh"
-pass=0; fail=0
-check() { if [ "$2" = "$3" ]; then pass=$((pass+1)); else fail=$((fail+1));
-  printf 'FAIL %s: got[%s] want[%s]\n' "$1" "$2" "$3"; fi; }
-# Run hook for a file_path with NO sentinel present (CWD = a clean temp dir).
-run() { local c r; c="$(mktemp -d)"; ( cd "$c" && printf \
-  '{"tool_name":"Edit","tool_input":{"file_path":"%s"}}' "$1" | bash "$H" ) \
-  >/dev/null 2>&1; r=$?; rm -rf "$c"; return "$r"; }
-
-# --- Guarded quality-gate files -> blocked (exit 2) ---
-run "/home/u/Documents/claude/lib/gitflow.sh";              check T1-gitflow           "$?" 2
-run "/home/u/.claude/settings.json";                        check T2-live-settings     "$?" 2
-run "/home/u/Documents/claude/.claude/settings.local.json"; check T3-local-settings    "$?" 2
-run "/home/u/Documents/claude/settings.json";               check T4-root-settings     "$?" 2
-run "/home/u/Documents/claude/.githooks/pre-commit";        check T5-githook           "$?" 2
-run "/home/u/Documents/claude/doctor.sh";                   check T6-doctor            "$?" 2
-run "/home/u/Documents/claude/.shellcheckrc";               check T7-shellcheckrc      "$?" 2
-# self-guard: the hook itself, other hooks, and the test suite are guarded
-run "/home/u/Documents/claude/hooks/config-protection.sh";  check T8-self-guard        "$?" 2
-run "/home/u/.claude/hooks/session-start.sh";               check T9-deployed-hook     "$?" 2
-run "/home/u/Documents/claude/lib/tests/config-protection.test.sh"; check T10-tests-guarded "$?" 2
-
-# --- Non-guarded -> allowed (exit 0) ---
-run "/home/u/Documents/claude/lib/gitflow-migrate.sh";      check T11-near-miss        "$?" 0
-run "/home/u/project/src/app.js";                           check T12-code             "$?" 0
-run "/home/u/project/settings.json";                        check T13-foreign-settings "$?" 0
-
-# --- Fail-open on malformed input (no file_path) -> allowed ---
-c="$(mktemp -d)"; ( cd "$c" && printf '{}' | bash "$H" ) >/dev/null 2>&1
-check T14-fail-open "$?" 0; rm -rf "$c"
-
-# --- Sentinel one-shot: non-empty reason -> allow + log + consume; 2nd edit blocked ---
-tmp="$(mktemp -d)"; mkdir -p "$tmp/.claude"
-printf 'fixing eslint false-positive' > "$tmp/.claude/.config-edit-ok"
-( cd "$tmp" && printf '{"tool_name":"Edit","tool_input":{"file_path":"/x/doctor.sh"}}' \
-  | HOME="$tmp" bash "$H" ) >/dev/null 2>&1
-check T15-sentinel-allow "$?" 0
-check T15-consumed "$([ -e "$tmp/.claude/.config-edit-ok" ] && echo present || echo gone)" gone
-check T15-logged "$(grep -c 'BYPASS.*doctor.sh.*fixing eslint' \
-  "$tmp/.claude/logs/config-protection.log" 2>/dev/null)" 1
-( cd "$tmp" && printf '{"tool_name":"Edit","tool_input":{"file_path":"/x/doctor.sh"}}' \
-  | HOME="$tmp" bash "$H" ) >/dev/null 2>&1
-check T16-second-blocked "$?" 2
-rm -rf "$tmp"
-
-# --- Sentinel with EMPTY reason -> refused + consumed ---
-tmp="$(mktemp -d)"; mkdir -p "$tmp/.claude"; : > "$tmp/.claude/.config-edit-ok"
-( cd "$tmp" && printf '{"tool_name":"Edit","tool_input":{"file_path":"/x/doctor.sh"}}' \
-  | HOME="$tmp" bash "$H" ) >/dev/null 2>&1
-check T17-empty-refused "$?" 2
-check T17-consumed "$([ -e "$tmp/.claude/.config-edit-ok" ] && echo present || echo gone)" gone
-rm -rf "$tmp"
-
-# --- T18/T19: payload shapes beyond Edit (locks against future Edit-only narrowing) ---
-c="$(mktemp -d)"; ( cd "$c" && printf \
-  '{"tool_name":"Write","tool_input":{"file_path":"/x/doctor.sh","content":"x"}}' | bash "$H" ) \
-  >/dev/null 2>&1; check T18-write-payload "$?" 2; rm -rf "$c"
-
-c="$(mktemp -d)"; ( cd "$c" && printf \
-  '{"tool_name":"MultiEdit","tool_input":{"file_path":"/x/doctor.sh","edits":[{"old_string":"a","new_string":"b"}]}}' | bash "$H" ) \
-  >/dev/null 2>&1; check T19-multiedit-payload "$?" 2; rm -rf "$c"
-
-# --- T20: sentinel with ONLY whitespace bytes (not literally empty) -> refused + consumed ---
-tmp="$(mktemp -d)"; mkdir -p "$tmp/.claude"; printf ' \n\t' > "$tmp/.claude/.config-edit-ok"
-( cd "$tmp" && printf '{"tool_name":"Edit","tool_input":{"file_path":"/x/doctor.sh"}}' \
-  | HOME="$tmp" bash "$H" ) >/dev/null 2>&1
-check T20-whitespace-only-refused "$?" 2
-check T20-whitespace-only-consumed "$([ -e "$tmp/.claude/.config-edit-ok" ] && echo present || echo gone)" gone
-rm -rf "$tmp"
-
-printf 'PASS=%s FAIL=%s\n' "$pass" "$fail"; [ "$fail" -eq 0 ]

lib/tests/contract-verifier.test.sh

@@ -67,7 +67,7 @@ fi
 tr_ "frontmatter name"                "$AGT" "^name: verifier$"
 tr_ "tools read-only set"             "$AGT" "^tools: Read, Grep, Glob, Bash$"
 tn  "no write-capable tools"          "$AGT" "^tools:.*(Edit|Write|NotebookEdit)"
-tf  "verdict grammar"                 "$AGT" "VERIFY — VERDICT: CONFORME | ECARTS(n) | ERROR(<reason>)"
+tf  "verdict grammar"                 "$AGT" "VERIFY — VERDICT: CONFORME | ECARTS(n) | ABANDONED(n) | ERROR(<reason>)"
 tf  "blind — no iteration history"    "$AGT" "NEVER receive iteration history"
 tf  "blind — complete every time"     "$AGT" "every verification is complete and blind"
 tf  "unverifiable is not met"         "$AGT" "\`UNVERIFIABLE\` ≠ \`MET\`"