Merge release/1.0.0 into main

2026-07-16 13:22:29 +02:00
parent 709facfb52 b0e2ebc31a
commit dc4f78b1f0
155 changed files with 13486 additions and 4454 deletions
@@ -28,10 +28,14 @@ rules:
 | BLK-006 | 2026-05-21 | `profile.sh current` false-negative via `~/.claude` symlink (`cd` not `cd -P`) | resolved |
 | BLK-007 | 2026-06-02 | 6 gstack source skills (ios-*, spec) unlinked post-bump — invisible to profiles + `gstack on` | resolved |
 | BLK-008 | 2026-06-23 | gstack ./setup on Ubuntu 26.04: Playwright chromium unsupported → gstack browser (/browse, /qa, screenshots) silently dead | resolved (211c7d4) |
-| BLK-009 | 2026-06-25 | user-level path-scoped rules (`paths:` frontmatter in `~/.claude/rules/`) never inject — broken in CC 2.1.190 (#21858) | upstream, open |
+| BLK-009 | 2026-06-25 | user-level path-scoped rules (`paths:` frontmatter in `~/.claude/rules/`) never inject — broken in CC 2.1.190 (#21858) | resolved (2026-07-06) |
 | BLK-010 | 2026-06-27 | init-project: scaffold (STEP 5) + bootstrap README (5b) have no deterministic commit owner; worktree `add -b` on unborn HEAD | resolved (uncommitted) |
 | BLK-011 | 2026-06-27 | init-project STEP 13 GSD post-FINISH creates ROADMAP.md → stranded doc (3rd post-FINISH artifact) | resolved (STEP 12 removed) |
 | BLK-012 | 2026-06-29 | gitflow_init half-applied: socle-commit failure swallowed → hook activated on partial run → re-run self-blocks | resolved |
 | BLK-013 | 2026-06-30 | `make plugin` Error 127 — npm absent on apt-`nodejs` host (Step 4 gsd-pi aborts, Steps 5-10 + residual cleanup never run) | resolved (env) |
 | 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 |
 ---
@@ -121,7 +125,8 @@ rules:
 - **Real cause**: GitHub issue #21858 — user-level (`~/.claude/rules/`) rules carrying `paths:` frontmatter are not evaluated/injected; still unfixed in 2.1.190. (Project-level path-scoped rules not tested here.)
 - **Probe method**: 3-file probe — `_probe.md` (`paths: ["**/*.probe"]`, sentinel `SENTINEL_USER_RULE_LOADED`), `_probe_ctl.md` (NO `paths`, control sentinel `CONTROL_NOPATHS_LOADED`), `_probe_target.probe` (target, read in a fresh session). Result: control sentinel PRESENT in session context, path-scoped sentinel ABSENT → the path-scoped rule did not load. Probe files removed after.
 - **Status**: upstream, open. Workaround: don't rely on user-level path-scoping → keep global guidance unconditional + COMPRESSED ([[BDR-031]]). Side-note: native auto-memory = "on" but writes nothing yet (fresh machine). Re-test on CC upgrades.
- **Reference**: GitHub #21858. Linked to [[BDR-031]], [[LRN-044]].
+- **2026-07-06 UPDATE — RESOLVED**: re-probed `paths:` frontmatter lazy-load with fresh 3-file probe (`**/*.blkprobe` glob) — confirmed loading works at BOTH project-level AND user-level (`~/.claude/rules/`) rule dirs. #21858 no longer reproduces on current CC version. Status → resolved. Prior workaround (unconditional + compressed global CLAUDE.md, [[BDR-031]]) no longer forced by this bug — see [[LRN-103]].
 - **Reference**: GitHub #21858. Linked to [[BDR-031]], [[LRN-044]], [[LRN-103]].
 ---
@@ -154,3 +159,45 @@ rules:
 - **Solution**: (1) socle commit FATAL in `_gitflow_init_existing` — `if ! git diff --cached --quiet; then git commit … || { echo …; return 1; }; fi` → aborts BEFORE develop/hook-activation; (2) identity precheck at top of `gitflow_init` (fail loud, no half-apply); (3) identity guard in `gitflow-migrate.sh:migrate_local`. Recovery: set faunosteo local identity → deactivate hook → delete premature develop → reinit (socle commits with hook inactive, as designed) → main==develop @ socle, tree clean, master renamed. Verified: shellcheck clean, 57/57 tests pass, hardened init on an identity-less repo aborts rc1 with ZERO mutation.
 - **Status**: resolved (`lib/gitflow.sh` + `lib/gitflow-migrate.sh`, uncommitted working tree as of the gitflow chantier).
 - **Reference**: [[LRN-068]] (transactional-bootstrap principle). Discovered mid gitflow-migration 2026-06-29. Sibling chantier learning [[LRN-067]].
 ## BLK-013 — `make plugin` Error 127: npm absent on apt-`nodejs` host
 - **Date**: 2026-06-30
 - **Friction**: `make plugin` (→ `install-plugins.sh`) aborts at Step 4 (gsd-pi): `install-plugins.sh: line 425: npm: command not found` → `make: *** [Makefile:10: plugin] Error 127`. Steps 5-10 never run, AND the post-Step-4 stray-dir cleanup (Step 8.5) never reached → the [[BDR-030]]/[[LRN-042]] residual (stray `$REPO/.agents/skills` + `$REPO/.claude/skills`, promised "auto-cleaned next `make plugin`") silently persists run after run. SessionStart banner already showed `gsd v2 ✗`.
 - **Real cause**: Debian/apt `nodejs` package ships `node` WITHOUT `npm` (npm = separate apt pkg). `/usr/bin/node` present (v22.22.1); its bindir has acorn/corepack/semver but NO npm/npx — npm genuinely uninstalled, not a PATH miss. install-plugins.sh Step 1 checks `node >=22` but NEVER verifies npm — assumes npm ships with node (true for nodesource/brew/dnf paths, FALSE for plain apt).
 - **Solution**: corepack (ships with node) over apt npm (apt npm could pull a divergent 2nd node). `corepack enable --install-directory "$HOME/.local/bin" npm` → npm 11.18.0 shim, no sudo, `~/.local/bin` already on PATH. Then `npm config set prefix "$HOME/.local"` — default prefix `/usr` is root-owned → `npm install -g` would EACCES; `~/.local` writable + bins land on PATH. Persisted in `~/.npmrc`. Re-run → EXIT=0, Step 4 ✓ (`gsd-pi@2.64.0`), Step 8.5 ran (`Removed stray repo-local skills dir: .agents/skills` + `.claude/skills`). Caveat: gsd-pi DEPRECATED + postinstall scripts SKIPPED (npm 11 `allow-scripts`) — `gsd --version/--help` ok, full provisioning would need `npm install -g --allow-scripts=gsd-pi,… gsd-pi`.
 - **Fix-forward**: install-plugins.sh Step 1 should GUARANTEE npm on apt-`nodejs` hosts — detect missing npm + `corepack enable npm` (not just check node) → stops Error 127 recurring on any fresh apt machine.
 - **Status**: resolved (env-level: corepack shim + npm prefix; zero repo change). Fix-forward (script hardening) NOT built.
 - **Reference**: discovered fixing `make plugin` 2026-06-30. Distinct from [[BLK-003]] (macOS playwright hardcoded path) + the Playwright-chromium `make plugin` failure. Blocked residual = [[BDR-030]]/[[LRN-042]].
 - **Update 2026-07-01**: fix-forward BUILT. install-plugins.sh Step 1 gained unconditional npm guard (`corepack enable npm` → distro `install npm` fallback → fatal `exit 1`), placed AFTER the `NODE_OK` short-circuit so a node>=22-present-but-npm-absent host no longer skips it. Now fully resolved (env-level + script). shellcheck/`bash -n` clean; fresh-apt live validation still pending. Commit `1f2c1cc`, branch `bugfix/install-plugins-npm-guard`.
 ---
 ## BLK-014 — `make install` aborts npm EEXIST when claude already present
 - **Date**: 2026-07-01
 - **Friction**: `make install` → install.sh Step 2 `npm install -g @anthropic-ai/claude-code@latest` fails EEXIST on `~/.local/bin/claude` when claude already installed → `else err` → `exit 1`. Bootstrap not idempotent on Claude Code step; rest (auth, symlinks, plugins) never runs.
 - **Real cause**: claude installed via NATIVE installer, not npm — `~/.local/bin/claude` = symlink → `~/.local/share/claude/versions/<v>` (`npm ls -g @anthropic-ai/claude-code` = empty; `claude --version` = 2.1.197). npm prefix `~/.local` (set by [[BLK-013]]) targets same `~/.local/bin/claude` → npm won't clobber a bin it doesn't own → EEXIST. Channel conflict, not double-install. Step had NO presence guard, unlike RTK (install-plugins.sh:388) / GSD (:419) / claude check (:252).
 - **Solution**: install.sh — skip-if-present guard `command -v claude` (mirror RTK/GSD), npm only fresh machine (`elif`). update-all.sh — channel-aware updater: `npm ls -g` → npm-managed uses npm, else native uses `claude update` (self-update). Never `npm --force` (would clobber native, break self-update).
 - **Status**: resolved. Fix `8dc4027`, branch `bugfix/install-claude-idempotent`, pending merge validation.
 - **Reference**: [[BLK-013]] npm prefix `~/.local` = contributing factor (npm bin over native bin). install-plugins.sh already pointed to code.claude.com (native) — install.sh was the npm outlier. Fresh-machine `elif npm` branch channel-consistency = open design question (potential BDR). Pattern → [[LRN-085]].
 - **Update 2026-07-01**: MERGED `2393ca5` (bugfix/install-claude-idempotent → develop), pushed — supersedes "pending merge validation". The open channel-consistency question is RESOLVED by [[BDR-046]] (fresh install → native installer, npm dropped for claude); install.sh has no `elif npm` branch → nothing left to trancher.
 ## BLK-015 — `gitflow_finish` ignored its args, merged the CURRENT branch not the one asked
 - **Date**: 2026-07-03
 - **Friction**: audit 2026-07-02 — `gitflow.sh finish bugfix audit-bugs` run while checked out on `feature/audit-tokens` merged audit-tokens (LOT3), NOT audit-bugs. Final develop state identical (disjoint hunks) so no data damage, but the merge order was silently wrong. UX trap: the command LOOKS like it targets `bugfix/audit-bugs`.
 - **Real cause**: CLI dispatch (`lib/gitflow.sh:257` `finish) gitflow_finish "$@"`) forwards args, but the function derived its source from `HEAD` (`git symbolic-ref`) and NEVER read `$1/$2` → the `<type> <name>` were silently dropped. Merge source = ambient state (checked-out branch), not the named target. Design intended finish to always operate on HEAD (human gate = "be on the branch"), but nothing enforced that passed args, if any, MATCH the branch you're on.
 - **Solution**: `gitflow_finish [<type> <name>]` — args now an optional safety ASSERTION: present AND `"$req_type/$req_name" != "$br"` → error `operates on the current branch 'X', but you asked 'Y' — checkout 'Y' first`, rc 2. No args = behavior unchanged (only real caller `skills/gitflow/SKILL.md:36` + every test pass none → zero regression). +7 regression assertions (`gitflow-test.sh` T12, numbered to dodge collision with reconcile's own T6c).
 - **Status**: resolved. Commit `d9fdd4c`, branch `bugfix/gitflow-finish-args`.
 - **Reference**: journal 2026-07-02 (trap noted, not fixed) → fixed 2026-07-03. Pattern → [[LRN-089]] (pass-through wrapper deriving target from ambient state = silent contract violation).
 ## BLK-016 — rtk compression PATH-dead for 30 days: installer's own check can't see the tool shell
 - **Date**: 2026-07-04
 - **Friction**: user asked "is rtk installed + used right?". Measured (`rtk discover`): 6 of 5070 Bash commands compressed over 30 days, ~460K tokens missed (grep ~144K, git status ~112K, ls ~92K…). Hook registered, integrity pin OK, registry broad — yet near-zero real usage. Nobody noticed: degradation was silent (LRN-047 class).
 - **Real cause**: two-layer. (1) cargo installs rtk into `~/.cargo/bin`; hand-managed profile lost the PATH line (LRN-036 class) → Claude's TOOL shell can't resolve `rtk`. (2) install-plugins.sh sources `~/.cargo/env` for itself, so its `command -v rtk` check PASSES in the installer shell — validating an env the runtime never has. Hook survived via absolute-path substitution, but ONLY at string head (f0b7e89 guard): every COMPOUND rewrite (dominant Claude style — echo separators, `&&`) was dropped by design.
 - **Solution**: bridge symlink `~/.cargo/bin/rtk` → `~/.local/bin/rtk` (standard PATH). Immediate: created live, compound rewrites revived, proven in-session (bare grep → `rtk grep` output). Durable: install-plugins.sh STEP 3 idempotent self-repairing bridge, flip-tested 4/4 sandboxed HOME (LRN-096). Commit `e58037c` (RC fix on release/1.0.0).
 - **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.
@@ -22,7 +22,7 @@ rules:
 | ID | Date | Title | Status |
 |----|------|-------|--------|
-| BDR-001 | 2026-04-22 | Uniform --help helper via session-start hook (option C) | accepted |
+| BDR-001 | 2026-04-22 | Uniform --help helper via session-start hook (option C) | accepted · won't-build 2026-06-30 |
 | BDR-002 | 2026-04-23 | Move tasks/ + introduce memory + audits under .claude/ | accepted |
 | BDR-003 | 2026-04-23 | Gitignore wildcard + negations pattern for .claude/ | accepted |
 | BDR-004 | 2026-04-27 | Adopt auto permission mode as default | accepted |
@@ -64,6 +64,29 @@ rules:
 | BDR-040 | 2026-06-29 | doc-syncer MINOR-shape oracle: deterministic floor under LLM's MINOR call | accepted |
 | BDR-041 | 2026-06-30 | /reconcile = deterministic declared-vs-real engine + thin gated skill (reconciler, not lister) | accepted |
 | BDR-042 | 2026-06-30 | /release-candidate = thin orchestrator over gitflow release; the tag lives in the skill, not the lib | accepted |
 | BDR-043 | 2026-06-30 | BDR-015 trigger cleared — 5 ex-broken gstack symlinks repaired → darwin re-baseline back in scope (unblocked, NOT run) | accepted |
 | BDR-044 | 2026-06-30 | auto-skill-dispatch won't-build — under-routing fear inverted to over-routing by cartography, then measured: model discriminates (clear→route, ambiguous→ask, trivial→abstain) | accepted · won't-build |
 | BDR-045 | 2026-07-01 | Standalone memory/doc skills branch to chore/* via aiguillage (hook exemption kept) | accepted |
 | BDR-046 | 2026-07-01 | Claude Code installs via official native installer (curl claude.ai/install.sh), drop npm from install.sh | accepted |
 | BDR-047 | 2026-07-01 | ECC audit → zero import; local config ahead of reference | accepted |
 | BDR-048 | 2026-07-03 | semgrep security gate: engine version + rulesets PINNED, never --config auto; upgrade = deliberate visible human jump | accepted |
 | BDR-049 | 2026-07-03 | verifier = fresh + blind (no iteration history) + disk-contract + PROOF-or-fail; mute ≠ PASS; scope enrichment via human micro-gate | accepted |
 | BDR-050 | 2026-07-03 | universal pipeline (contract→dev inline→fresh verify→fresh security, loops bounded 3× in main loop) with per-flow weighting; hotfix failure = revert not loop | accepted |
 | BDR-051 | 2026-07-04 | contract enrich-at-gate: the contract grows ONLY at a human micro-gate ([gated] marker); the verifier judges the ENRICHED contract, not the seed | accepted |
 | BDR-052 | 2026-07-05 | /tour auto mode = branch-as-gate: no mid-run approval gates; unmerged chore branch + per-project TOUR.md = deferred human gate; reconcile report-only; loop bounded 3× | accepted |
 | BDR-054 | 2026-07-06 | supersede BDR-038 NEXT.sh/hand-back artifacts — shipped impl removed both (52f6678, LRN-102) | accepted |
 | BDR-055 | 2026-07-07 | job5: delete memory-commit/doc-commit `pending` verbs — v2 hook rejected (BDR-037), J4-17 closed MOOT | accepted |
 | BDR-056 | 2026-07-07 | job6: deps policy = latest gated by integration, not KEEP-PINNED by default | accepted |
 | BDR-057 | 2026-07-07 | job7: secrets by reference not by value; redact at capture, not just at rest | accepted |
 | BDR-058 | 2026-07-07 | job8: darwin-skill reinstall full pinned tree, detached HEAD (skills CLI single-file-fetch gap) | accepted |
 | BDR-059 | 2026-07-07 | job8: explicit ask-gate for all 4 magic MCP tools, empty allow stays empty | accepted |
 | BDR-060 | 2026-07-08 | job9: CC orchestration floor = v2.1.172 (nested dispatch), supersedes implicit v2.1.83 whole-system floor | accepted |
 | BDR-061 | 2026-07-08 | job9: seo/geo analyzers → fix-bundle→L1 by doctrine (validator-analyzer pattern), not by version constraint | accepted |
 | BDR-062 | 2026-07-08 | supersede BDR-031's 275 CLAUDE.md target — 305 assumed reality (extraction done at job1; more compression costs clarity > tokens); guard threshold realigned 280→320 | accepted |
 | BDR-063 | 2026-07-10 | GSC multi-account: OAuth2 installed-app flow + label-keyed token store, explicit (account,property) args, no global state | accepted |
 | 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 |
 ---
@@ -77,6 +100,7 @@ rules:
  - Option A (copy helper into each SKILL.md) — rejected: maintenance entropy.
  - Option B (external wrapper `/help <skill>`) — rejected: breaks "one command = one skill" experience.
 - **Reference**: commit 3968a29.
 - **Won't-build (2026-06-30)**: accepted but never built. MEASURED before building — behavioral RED, 6 reps (`/web-validate` + `/harden`, no instruction): **6/6 already render rich help AND stop without dispatching** (even `/harden` didn't start its audit). The intended behavior is already spontaneous (universal `--help` convention); the ONLY residual value of the global instruction = format CONSISTENCY across 6 divergent shapes — judged not worth ~5 lines in a [[BDR-031]]-compressed CLAUDE.md on a solo repo. Not "abandoned" — measured non-rentable. Per-skill option stays rejected (original Decision above). See [[LRN-080]], [[LRN-075]].
 ## BDR-002 — Move tasks/ + introduce memory + audits under .claude/
@@ -471,6 +495,8 @@ rules:
  - Secret in `repo/.env`, gitignored (status quo) — one `git add -f` or a `.gitignore` slip leaks it; the secret physically sits in the tree.
  - Scripts read `~/.claude/.env` directly — makes the symlink redundant but rewrites every read path and loses repo-local visibility.
 - **Reference**: `link.sh` `link_env()`, `.gitignore`, `lib/toggle-external.sh`, `install-plugins.sh`, `.env.example`, commits 131d0bc / f9cc866. Linked to [[BDR-025]] (magic's `MAGIC_API_KEY`, consumed by the gate's required-but-manual class).
 - **Update 2026-07-02 (incident — copies of secrets)**: `claude mcp add --env` MATERIALIZES the key into `~/.claude.json` (`mcpServers.magic.env`) — a 2nd live copy OUTSIDE the `~/.claude/.env` canonical and outside the repo deny rules' reach. An audit query printed it into a session transcript → key rotated (21st.dev). Rule: secrets have COPIES (tool configs, transcripts, caches) — protect/audit the copies, not just the canonical; when inspecting MCP config, filter env fields (`jq 'del(.. | .env?)'`). Same audit: `~/.claude/.env` hardened 0664→0600.
 - **Update 2026-07-07 (job7 — backup vector closed)**: the `~/.claude.json` copy from the 2026-07-02 incident kept re-leaking into `~/.claude/backups/.claude.json.backup.*` (native Claude Code auto-backup, ring-buffer of 5, plaintext each time) — every backup taken while the live file held the value was a fresh copy, so scrubbing existing backups alone would have recurred forever. Closed at the source instead ([[BDR-057]]): `~/.claude.json`'s `mcpServers.magic.env.API_KEY` rewritten to `"${MAGIC_API_KEY}"` (Claude Code `${VAR}` expansion, confirmed supported at user scope), `lib/toggle-external.sh` writes the reference form for future `enable magic` runs, var reaches `claude` only via a scoped `~/.bashrc` wrapper (never the ambient shell). New backups taken after the fix carry the reference, not the value — confirmed empirically (2 of 5 rotating backups mid-fix still had the old value; scrubbed once, not expected to recur). MAGIC_API_KEY itself still needs rotation (this closes the storage vector, not the already-exposed value).
 ---
@@ -655,3 +681,314 @@ rules:
 - **Consequence (accepted)**: a release cut by calling `gitflow finish` directly, bypassing the skill, fans out but is NOT tagged → `/release-candidate` is the CANONICAL sole release path. Acceptable for a solo repo; revisit (tag in lib) only if direct-lib releases become a need.
 - **Alternatives rejected**: tag inside `gitflow_finish` (atomic but modifies the tested generic mechanic for a release-specific concern — lib=mechanic/skill=judgment); restart tags at v1.0.0 (desyncs tag↔CHANGELOG lineage).
 - **Reference**: `skills/release-candidate/SKILL.md`, `lib/tests/run-release-candidate.sh` (RED no-tag → GREEN 5/5), CLAUDE.md routing. Built via writing-skills TDD. Consumes the gitflow model [[BDR-039]]. See [[LRN-078]], [[LRN-079]], [[EVAL-012]].
 ## BDR-043 — BDR-015 trigger cleared: 5 ex-broken gstack symlinks repaired → darwin re-baseline back in scope
 - **Date**: 2026-06-30
 - **Status**: accepted (requalifies [[BDR-015]] — append-only, BDR-015 left intact)
 - **Decision**: the 5 dirs [[BDR-015]] excluded from `/darwin-skill` (`benchmark-models`, `context-restore`, `context-save`, `make-pdf`, `plan-tune`) are no longer broken. gstack now ships those skills — all GENERATED by `gen-skill-docs` in the `make plugin` run → real submodule targets exist, symlinks resolve. VÉRIF audit 2026-06-30 = 0 broken among 83 symlinks (skills/ 41 + skills-disabled/ 33 + nested 5 + top-level 4). Per BDR-015's own caveat ("if/when symlinks repaired → re-run baseline to bring them in scope"), the 5 RETURN to darwin scope → re-baseline UNBLOCKED.
 - **Why**: BDR-015's exclusion was CONDITIONAL on the targets being broken (external-ownership + missing-target). Precondition gone → exclusion no longer applies to these 5.
 - **Action (NOT done)**: verify `~/.agents/skills/darwin-skill/results.tsv` still marks these 5 `status=error` ("broken gstack symlink — out of scope"); if so, re-run darwin baseline to bring them in. Status = UNBLOCKED, execution PENDING — do NOT read as "re-baselined".
 - **Distinct from [[BLK-007]]**: BLK-007/`f928a53` (2026-06-02) = a DIFFERENT symlink episode (`spec` + 5 iOS device-farm skills, source-only after a submodule bump; fixed by linking `spec`, skipping iOS). NOT the 5 of BDR-015 — kept separate to avoid a false causal link.
 - **Reference**: VÉRIF audit (subagent, filesystem-only, 2026-06-30). [[BDR-015]] caveat. darwin eval log `results.tsv`.
 ---
 ## BDR-044 — auto-skill-dispatch won't-build: under→over reframe, measured — model already discriminates
 - **Date**: 2026-06-30
 - **Status**: accepted · won't-build
 - **Decision**: do NOT add L2 routing prose to CLAUDE.md for "auto-trigger skills on intent". Chantier retired won't-build — 3rd measured moot of the session (after [[BDR-001]] --help + [[BDR-043]]/[[LRN-082]] darwin re-baseline).
 - **Why — the dependent variable inverted**: the initial fear was UNDER-routing (model ignores skills, does the task by hand). Cartography refuted it — routing is a STACK and L1 (superpowers "1% chance → you MUST invoke") already SUR-determines invocation → "does it route?" = "already yes". The real open question became DISCERNMENT (clear→route, ambiguous→ASK, trivial→abstain), and the real hazard inverted to OVER-routing. Measured in REAL fresh main-loop sessions (8 prompts, 3 classes): CLEAR→routes ✓, AMBIGUOUS→asks (refuses to guess, investigates to ask a USEFUL question) ✓, TRIVIAL→abstains ✓. The L1-vs-Workflow-rules textual tension ("1% → MUST invoke" vs "ask one question if needed / pragmatic on trivial") is resolved well in behavior — the model balances. Adding L2 bounding prose = phantom value AND risks DEGRADING an already-good discernment.
 - **Alternatives rejected**:
  - Add a routing-reinforcement instruction (original intent) → phantom value: L1 already over-determines routing; more mandate worsens the only real risk (over-routing).
  - Add an over-routing bound (clear→route / ambiguous→ask / trivial→abstain) at L2 → measurement shows the model ALREADY does this; codifying it risks perturbing it, zero upside.
  - Keyword hook on intent verbs → too noisy — the design-hook mis-fired on "design" in "auto-skill-dispatch" 3× this session; intent verbs (corrige/crée) are everywhere.
 - **Reference**: cartography L0–L4 + discernment-RED (user-run, fresh sessions). Subagent under-routing RED RETIRED as non-discriminating ([[LRN-083]]). [[LRN-080]] (measure-first), [[LRN-049]] (bound noise). TODO "auto-skill-dispatch" → won't-build.
 ## BDR-045 — Standalone memory/doc skills branch to `chore/*` via the aiguillage (hook exemption kept)
 - **Date**: 2026-07-01
 - **Status**: accepted
 - **Decision**: Standalone memory/doc skills (`/capitalize` `/close` `/prune-memory` `/reconcile`) run the gitflow aiguillage BEFORE writing: on a protected base they `gitflow start chore <name>` off develop → commit lands on `chore/*`, not direct on main/develop. New `chore` type in `lib/gitflow.sh` (`base_for`→develop, `branch_type`, `finish`→develop like feature/bugfix); hook UNCHANGED (`chore/*` non-protected; the `.claude/**`-on-main exemption KEPT — T3 still green). `gitflow-aiguillage.md` broadened (caller→type map); 3 skills wired (`capitalize` covers `/close` via alias, `prune-memory`, `reconcile`); tests +T1 chore predicates +T6b finish chore→develop +T10 coherence chore/m → 64/64. Reused the EXISTING aiguillage include, not a new mechanism. Commit `e8807a7`.
 - **Why**: the `.claude/**` exemption is scoped to the SIDE-CAR ([[BDR-034]]: memory following a code branch). When memory IS the work (standalone reconcile/prune/capitalize) there is no branch to follow → it fell back to `main`. A multi-repo raccord committed 5 `chore(memory)` direct on `main` and nothing flagged it — the exemption worked as designed, masking the divergence with the "all via branch" rule ([[LRN-084]]). The aiguillage closes the SKILL path without taxing the side-car. The hook can NEVER enforce "from develop" (only "not on a protected base") → that half lives ONLY in `gitflow_start`.
 - **Alternatives rejected**:
  - (A) remove the `.claude/**` exemption — breaks standalone `/capitalize`+`/close` on main/develop (commit in place, no branch of their own — `memory-commit.sh` has no protected-base guard) AND every side-car commit; over-reaches the leak.
  - (C) codify exemption + human habit — enforces NOTHING mechanically; goal was automatic.
  - (D) narrow the exemption by size/scope in the hook — fuzzy, false positives.
 - **Honest residual**: a MANUAL `git commit` of `.claude/**` on `main` still passes — B covers the skill path only. Non-blocking hook WARN on manual `.claude/**`-on-main = DEFERRED. See [[BDR-034]], [[BDR-039]], [[LRN-084]].
 ---
 ## BDR-046 — Claude Code installs via the official native installer, not npm
 - **Date**: 2026-07-01
 - **Decision**: install.sh fresh-machine branch installs Claude Code via `curl -fsSL https://claude.ai/install.sh | bash` (official native installer), not `npm install -g @anthropic-ai/claude-code`. Skip-if-present guard unchanged. update-all.sh stays channel-aware (native → `claude update`, legacy npm → npm).
 - **Why**: official quickstart (code.claude.com/docs) lists Native (recommended) / Homebrew / WinGet / apt only — npm is NO longer a documented channel. npm collided with the native symlink `~/.local/bin/claude` → EEXIST ([[BLK-014]]), and npm bypasses native background auto-update. install-plugins.sh already pointed to code.claude.com (native) — install.sh was the npm outlier; this aligns them.
 - **Alternatives rejected**:
  - (A) keep npm on fresh install — deprecated channel, re-introduces the EEXIST class on any machine with a prior native install, no auto-update.
  - (B) `claude install` subcommand — needs claude already present (chicken-and-egg on fresh machine); curl bootstrap is the documented first-time path.
  - (C) Homebrew/apt — platform-specific; curl covers macOS/Linux/WSL uniformly and matches the doc's "recommended".
 - **Honest residual**: `curl | bash` = pipe-to-remote-bash (accepted: official Anthropic domain, same pattern already used for nvm at install.sh:29). node/npm still installed as prereqs — needed by the plugins step (gsd-pi), not by claude. PATH export added so the auth step finds the freshly-installed binary. See [[BLK-014]], [[LRN-085]].
 - **Status**: accepted. Commits 8dc4027 + 6be627e, branch bugfix/install-claude-idempotent, pending merge.
 - **Update 2026-07-01**: MERGED `2393ca5` → develop, pushed — supersedes "pending merge".
 ---
 ## BDR-047 — ECC audit → zero import; local config ahead of reference
 - **Date**: 2026-07-01
 - **Status**: accepted
 - **Decision**: audited affaan-m/ECC (legit original, NOT the arabicapp malware
  clone) read-only for value vs this config. Result: ZERO import. Nothing taken.
  Clean measure-first outcome — analysis closed.
 - **Safety** (durable, avoids re-audit): ECC = genuine original — 2232 commits,
  ~1480 by Affaan Mustafa, real contributor long-tail, sequential PRs. No payload:
  postinstall = echo, install.sh runs only its 3 reputable deps (@iarna/toml, ajv,
  sql.js), ships own supply-chain IOC scanner. Zero injection flags across ALL
  categories. NOTE: ECC install.sh auto-runs `npm install` → never run their
  installer casually; this analysis stayed read-only.
 - **Why zero import** (each intuition CHALLENGED, not confirmed):
  - RULES (122 files, by-language): ~80% redundant w/ CLAUDE.md, rest dormant
    reference. INERT at ECC — nothing reads rules/, their README admits "plugins
    cannot distribute rules automatically", `paths:` frontmatter aspirational (no
    auto-routing exists). "take all" refuted.
  - CONTEXTS (dev/research/review, 3 tiny files): least load-bearing. Delivery via
    `claude --system-prompt "$(cat)"` would OVERWRITE global CLAUDE.md. Harmful
    as-shipped. "important" refuted.
  - GUIDELINES: ECC itself demoted to docs/example. Per-project CLAUDE.md
    (git-tracked) superior.
  - INSTRUCTION FILES (AGENTS/RULES/SOUL/WORKING-CONTEXT): redundant or
    ECC-specific. AGENTS.md "proactive delegation" already mandated here.
  - MEMORY/learning: auto hook-capture → confidence-scored instincts. CONFLICTS
    measure-first (observe-first vs approve-first). Instinct schema parked (gated
    only).
  - eval-harness (the spike): DOCS-ONLY — 271-line SKILL.md, no runner,
    `/eval define|check|report` exist NOWHERE. Same "belle méthodo / câblage
    vaporware" pattern as rules. Executable-eval ALREADY covered locally:
    lib/tests/run-*.sh (code graders) + darwin dim8 (with/without-baseline
    sub-agent effect testing + git ratchet) + RED-before-GREEN discipline. evals.md
    = ledger of REAL runs (EVAL-011 ran 20/20, dogfooded) — spike premise
    "descriptif pas exécuté" was FALSE, corrected.
 - **Lesson**: external repo — even prestigious / "d'un boss" — judged on REAL added
  value to THIS config's axes (typed memory, real harness, gitflow), NOT author
  reputation. Measuring it revealed local config AHEAD on those axes. Taking a thing
  "since we analyzed" = sunk-cost. Zero is the honest conclusion. Don't re-propose
  auditing ECC expecting treasure.
 - **2 real gaps FOUND (not rejected — the only concrete fruit of the audit)**:
  1. pass@k / reliability-under-repetition — local harness proves PRESENCE (guard
     fires, often N=1), not RELIABILITY (right output 9/10 under repetition). Blind
     spot for non-deterministic skill/agent behavior (EVAL-006 flagged "N=6 fleet
     NOT exhausted").
  2. re-runnable regression battery indexed on model upgrades — bespoke
     per-chantier tests, no one-command "re-run behavioral evals for load-bearing
     skills" when model changes. darwin optimizes on-demand, not a standing gate.
  - **Both = home-grown ~10-line bash over darwin's test-prompts.json if ever
    wanted — NOT ECC imports.** eval-harness delivers neither (no runner). Separate
    later decision.
 - **Alternatives rejected**:
  - Import eval-harness anyway (sunk-cost "we analyzed it") — rejected: docs-only,
    capability already covered, adds vocabulary not machinery.
  - Import rules by-language + build wiring hook — parked: low ROI (bash/md, not
    polyglot); hookify-rules would be the mechanism, someday-if-polyglotte.
  - Adopt instinct auto-capture — rejected: conflicts measure-first.
 - **Optional zero-cost nicety** (not now): tag evals.md entries w/ grader-type + k
  (e.g. `method: code-grader, pass^3`) — writing convention, not an import.
 - **Reference**: read-only clone (scratchpad), 4 parallel analyzer agents +
  eval-harness spike, this session. No branch on ECC, no import. See [[BDR-045]]
  (chore/ aiguillage), [[BDR-009]] (caveman registries).
 - **Corroboration 2026-07-03** (Opus 4.8 re-audit; repo UNCHANGED — HEAD 81af407
  2026-06-29, 2232 commits identical, zero commits since 01/07): 6 parallel analyzer
  agents re-verified every BDR-047 fact w/ fresh file:line. rules/ inert (paths: 0
  consumers, rules/README.md:333 "cannot distribute rules automatically"); contexts/
  overwrite (the-longform-guide.md:68-74 `--system-prompt`); eval-harness no runner
  (/eval absent; gan-harness.sh + skill-improvement/evaluate.js exist but hors-scope,
  deliver NEITHER pass@k nor model-upgrade battery); memory auto-capture conflicts
  approve-first (continuous-learning-v2 observer-loop.sh:160-164 "Do NOT ask for
  permission"); distribution = product scaffolding, N/A. ZERO factual divergence.
  ONE scope gap: BDR-047 never opened hooks/ — ECC's only WIRED subsystem. Fruit:
  config-protection hook (own idiom, NOT ECC import), shipped
  feature/config-protection-hook. Lesson holds + refined by [[LRN-090]].
 ## BDR-048 — Deterministic security gate: pinned engine + pinned rulesets (semgrep)
 - **Date**: 2026-07-03
 - **Decision**: semgrep = BLOCKING gate (verify-loops chantier) → engine version PINNED in plugins.lock.json (gsd-pin pattern; update-all.sh honors pin + displays jump cur→pin before `pipx install --force`). Rulesets PINNED in-agent: `p/security-audit` + `p/secrets`. Never `--config auto` (registry telemetry + ruleset resolved per-run = non-deterministic gate, [[LRN-077]] class). Never auto `semgrep login` — Pro rules optional, guide-only (ctx7 pattern).
 - **Rationale**: gate blocks HIGH/CRITICAL only ([[LRN-047]]); silent engine/rule upgrade = new BLOCKs on unchanged code w/o human decision → gate crying false → ignored. Version jump must be deliberate + visible (bump pin, then `make update` shows the jump).
 - **Alternatives rejected**: `latest` (pipx house default, graphifyy-style) — fine for comfort tools, wrong for a blocking gate; `--config auto` — telemetry + non-determinism.
 - **Reference**: plugins.lock.json `semgrep` entry, install-plugins.sh STEP 7.5, update-all.sh step 6.2 — branch feature/semgrep-install `ccfecc9`. Conditions [[LRN-047]], [[LRN-085]]. Coverage caveat of the community rulesets: [[LRN-092]].
 - **Addendum 2026-07-03** (lot 3, measured): rulesets = `p/security-audit` + `p/secrets` + **`p/owasp-top-ten`**. owasp-top-ten is REQUIRED not optional — measured on realistic Flask code, the 2-ruleset baseline missed SQL injection + path traversal ENTIRELY (0 findings); owasp's taint rules catch them. Severity map: secrets ERROR→CRITICAL, other ERROR→HIGH (block), WARNING/INFO→reported. Blocking threshold = ERROR (per-RULE, not per-vuln — same class can straddle ERROR/WARNING; blocking WARNING too floods FP). FP measured shell/md only (faunosteo, game: sole added blocking ERROR = Dockerfile `missing-user` hygiene, contained by gate-mode diff-scoping). **Re-evaluate owasp FP at the first real web/python app project** (shell/md repos don't represent where the gate runs). See [[LRN-094]], agents/security-auditor.md branch feature/security-auditor `2b297bd`.
 ## BDR-049 — Verifier doctrine: fresh + blind + disk-contract + proof-or-fail
 - **Date**: 2026-07-03
 - **Decision**: conformity verdict comes ONLY from a FRESH verifier subagent per iteration. Input = contract PATH (read from disk — dev restatement structurally unable to interpose) + diff range + optional test cmd. NEVER iteration history: blind, complete verification every time (cost bounded by the main-loop max-3 cap, [[LRN-083]]: loops decided in main loop). CONFORME ⇔ all criteria MET + zero out-of-scope. PROOF line mandatory ([[LRN-048]]). Mute/unparsable verifier NEVER a PASS: 1 fresh retry, 2nd structural failure = human escalation. Dev-justified out-of-scope enters FILE SCOPE only via a human micro-gate (`[gated]` marker) — else the dev justifies everything and scope constrains nothing. Contract on DISK at creation (`.claude/tasks/contracts/<date>-<slug>-<HHMM>.md`, committed; aborted run → deleted or `status: aborted`, never left dirty).
 - **Rationale**: dev self-score is always confident → not a gate. Verifier fed history anchors on prior verdicts → telescopic drift. Context-only contract dies at compaction, the verbatim with it.
 - **Alternatives rejected**: dev self-assessment as gate; cumulative verifier context ("cheaper" but anchored); gitignored run files (lose escalation reference + session-death survival).
 - **Reference**: lib/contract-interview.md + agents/verifier.md + lib/tests/contract-verifier.test.sh (31 locks) — branch feature/contract-verifier `6aed5ee`. Behavioral GREEN: planted-gap → ECARTS(2) exact; conform-under-injected-history → CONFORME (blindness held). Twin of [[BDR-048]] (security gate). Conditions [[LRN-048]], [[LRN-083]].
 ## BDR-050 — Universal verify+secure pipeline, weighted per flow (loops in the main loop)
 - **Date**: 2026-07-03
 - **Decision**: every dev flow = contract (verbatim, on disk) → dev INLINE → fresh verifier (request conformity) → fresh security-auditor (`MODE: gate`) → commit. Loops BOUNDED at 3 and decided in the ORCHESTRATOR MAIN LOOP ([[LRN-083]]), never in a subagent. Order invariant: on any security re-loop, re-verify the REQUEST before re-scanning security. Per-flow weight: feat/bugfix = both gates, both loop (nominal 2 dispatches); hotfix = NO fresh verifier (its smoke-check verifies the trivial autofill contract), security gate whose FAILURE REVERTS (`git restore` + escalate to /bugfix), never loops — the 1-attempt model preserved (nominal 1 dispatch). Shared include `lib/verify-secure-loop.md` for feat/bugfix; hotfix inline variant.
 - **Rationale**: the value is the INDEPENDENCE of the gate (fresh subagent vs a rich contract), NOT delegating the dev — so dev stays inline in light flows and weighting lives on loops+questions, never on skipping a gate. hotfix reverts because a 3× loop would reintroduce the weight its identity excludes.
 - **Alternatives rejected**: dispatch the dev too (turns feat into ship-feature-bis); one merged "quality" gate (see [[LRN-095]] — orthogonal gates degrade if fused); hotfix loops like feat (breaks its 1-attempt identity).
 - **Reference**: lib/verify-secure-loop.md + wired feater/bugfixer/hotfixer + lib/tests/loops-light.test.sh (27 locks) — feature/verify-loops `0f0162d`. Behavioral GREEN (feat fixture): CONFORME→BLOCK(1) SQLi→fix→re-verify CONFORME→re-scan PASS, order invariant held. Builds on [[BDR-048]] [[BDR-049]]. Conditions [[LRN-083]] [[LRN-095]].
 ## BDR-051 — Contract enrich-at-gate: the contract grows only at a human micro-gate
 - **Date**: 2026-07-04
 - **Decision**: the CONTRACT's REQUEST is immutable, but ACCEPTANCE CRITERIA + FILE SCOPE may GROW — exclusively at a human gate, each added entry tagged `[gated <date>]`. In the heavy flows (ship-feature STEP 3, init-project GATE #1) the approved DESIGN appends design-derived criteria to the contract; the fresh verifier then judges the diff against the ENRICHED contract, never the seed. Same mechanism as the out-of-scope micro-gate ([[BDR-049]]) — a dev never enriches; only the human validating a gate does.
 - **Rationale**: the raw request underspecifies (a one-line "add validation" hides the schema-rejection requirement the design surfaces). If the verifier judged only the seed, every design decision would be unverified. Gating the growth keeps the contract honest (no silent scope creep) AND complete (design criteria are verified). The only flow where the contract is mutable mid-run — bounded to gate moments.
 - **Alternatives rejected**: freeze the contract at creation (design criteria unverified — the seed is too thin); let the dev enrich (the [[BDR-049]] failure mode — dev justifies everything, scope constrains nothing); a second contract per design (loses the single-reference property).
 - **Reference**: ship-feature STEP 0e+3, init-project STEP 1+4, feature/verify-loops `1c69de2`. Behavioral GREEN: a `[gated 2026-07-04]` design criterion (reject unknown config keys) was read + judged NOT-MET by a fresh verifier across 3 rounds (dogfood). Builds on [[BDR-049]] [[BDR-050]].
 ## BDR-052 — /tour auto mode: branch-as-gate, declared state read-only
 - **Date**: 2026-07-05
 - **Decision**: /tour (grouped sweep clean+security+reconcile+doc, 1..N projects) runs auto, NO mid-run approval gates. Compensations: (1) fixes on `chore/tour-<date>` via gitflow lib, skill NEVER finish/merge/push — unmerged branch + per-project append-only `.claude/audits/TOUR.md` = the human gate, deferred not deleted; (2) reconcile phase REPORT-ONLY even in auto — target TODO + registries read-only, gaps = `suggested` rows applied later via /reconcile; (3) convergence loop bounded 3× ([[LRN-083]]), residuals reported honestly; (4) security floor = security-auditor (pinned semgrep, [[LRN-047]] BLOCK HIGH/CRITICAL) every iteration + cso posture once (gstack ON); CRITICAL/HIGH contract-changing fix applied but tagged **BREAKING** in report+summary; (5) dirty tree / no develop / no lib → report-only, never stash, never hand-branch.
 - **Rationale**: mid-run gates defeat the skill's point (hands-off grouped sweep, user away). Auto-checking TODO reproduces the exact lie /reconcile catches — RED-proven, baseline did it. Branch+report = same approval semantics as audit-delta's 3c gate, moved after the fact where a headless run can afford it.
 - **Alternatives rejected**: per-phase AskUserQuestion gates (audit-delta model — blocks headless); one consolidated pre-fix gate (still blocks); auto-edit TODO on oracle proof (inference ≠ approval); plain-branch fallback on non-gitflow repos (violates lib-only doctrine → report-only instead).
 - **Reference**: skills/tour/SKILL.md + CLAUDE.md routing (feature/tour-skill `73e6a1c`). TDD trail [[LRN-099]] [[LRN-100]] [[EVAL-014]].
 ## BDR-053 — ctx7 single surface: keep find-docs skill, kill context7.md rule
 - **Date**: 2026-07-06
 - **Decision**: ctx7 gets ONE session surface = `skills/find-docs` (lazy body, description-only cost). `rules/context7.md` deleted + install-plugins.sh STEP ctx7 purges it unconditionally post-setup (`rm -f`, generator has no skip-rule flag — `--claude`/`--cli` = target/mode only). darwin-skill entry dropped from skills-lock.json same pass (F8: lock stale `6bbcda37…` vs disk `c3220018…`, no re-pin verb in npx skills — unpinned rather than hand-edit undocumented hash).
 - **Rationale**: rule = ~490 tok/session session-start duplicate of the skill (job1 F10 + job2); skill self-suffices (876-char description carries the triggers, body has full CLI flow). Purge-in-installer beats one-shot rm: survives re-runs + manual `ctx7 setup`.
 - **Alternatives rejected**: kill skill keep rule (rule always-on, costs every session even non-lib work; skill lazy — wrong direction); hand-trim generated files (fight the generator, LRN-039 class); hand-edit lock hash (algo undocumented).
 - **Reference**: chore/ctx7-single-surface; job1 F10, job2 F8/F13. User decision 2026-07-06.
 ## BDR-054 — supersede BDR-038: NEXT.sh file + AskUserQuestion hand-back removed from /deploy
 - **Date**: 2026-07-06
 - **Status**: accepted (supersedes BDR-038 on 2 points: NEXT.sh artifact, hand-back mechanism)
 - **Decision**: /deploy ships WITHOUT NEXT.sh file (checklist display-only, conversation-only) and WITHOUT AskUserQuestion hand-back (plain final-text print, turn ends, no tool call after). BDR-038's original 5-artifact list (PROCEDURE.md, INCIDENTS.md, STATE.json, PENDING.json, NEXT.sh) shrinks to 4 committed/bridge artifacts — NEXT.sh no longer written. Two-moment spine (BEFORE/AFTER), PENDING.json bridge, deploy-commit.sh atomic patch+incident — all unchanged, still current per BDR-038.
 - **Why**: LRN-102 — deliverable text printed before a tool call may never render (harness guarantees only the turn's FINAL text); AskUserQuestion after the checklist swallowed it silently, live run 2026-07-05 (bchanot-cv). NEXT.sh-to-disk also useless in practice (user: throwaway once deployed) — display-only kills a stale-file-drift class for free.
 - **Alternatives rejected**: keep NEXT.sh, fix hand-back only (leaves ephemeral-file-nobody-reads problem); keep AskUserQuestion, cram checklist into its options text (char-limited, brittle); revert to file+question (reproduces the exact LRN-102 bug).
 - **Reference**: commits `31443ba` (inline hand-back print), `52f6678` (checklist display-only, no NEXT.sh); `skills/deploy/SKILL.md:74-77,295-297,313-318,440-441`; [[LRN-102]]; job3 docs-drift audit D6/D7/D9 (`.audit/job3-report.md`).
 ## BDR-055 — job5: delete pending verbs, close J4-17 MOOT
 - **Date**: 2026-07-07
 - **Status**: accepted
 - **Decision**: `memory_pending()` + `docs_pending()` + `pending` dispatcher arms deleted from `lib/memory-commit.sh` / `lib/doc-commit.sh`, plus stale "for the v2 hook" header mentions. `commit`/`commit <message> <file>...` = only verb left. J4-17 (job4 backlog: "extend run-deterministic.sh to test pending") closed MOOT — its premise gone with the verb.
 - **Why**: headers earmarked both funcs "for the v2 hook" — [[BDR-037]] REJECTED v2 hook, no code ever written. J4-17 queued TEST not DELETE, but deferred to the newer/wrong branch — v2 hook dead means nothing left to test toward. Zero prod/test callers confirmed (job5 audit) before delete.
 - **Alternatives rejected**: keep+test per J4-17 (tests a dead-end, [[BDR-037]] already closed that door); keep unused (dead code, no consumer).
 - **Reference**: commit `da3abf9`; `.audit/job5-report.md` J5-13/§3b; supersedes J4-17 (`.audit/job4-report.md:35`). Same supersession-trace discipline [[BDR-054]] had to backfill for BDR-038/job3 D6-D9 — written here at delete time, not reconstructed later.
 ---
 ## BDR-056 — job6: deps policy = latest gated by integration, not KEEP-PINNED by default
 - **Date**: 2026-07-07
 - **Status**: accepted (reverses job6-batch-3 KEEP-PINNED-unless-CVE default)
 - **Decision**: default posture = pull latest, gated per-dep by real integration checks (make test + named smoke), not "keep pinned unless a CVE forces the hand". Sequenced by risk, one upgrade = one commit = one gate, immediate rollback on red. Applied job6: ctx7 0.5.3→0.5.4, gsd-pi 2.64.0→3.0.0, gstack 070722a→11de390 (v1.52.1.0→v1.58.5.0), graphifyy binary 0.9.6→0.9.8 (hook-adoption declined separately, see below).
 - **Why**: job6-batch-3's expected verdict for gstack was KEEP-PINNED sauf CVE; user overrode it — a fail-open security-guard fix (#1911, no formal CVE) counts as the CVE clause in substance, and staying pinned to avoid work means carrying live-vulnerable tooling. Gating on integration tests (not on "did upstream file a CVE") catches the real risk (format/behavior breaks) that pin-forever also fails to prevent — gsd-pi 3.0.0 broke status-reporter's ROADMAP.md parser silently (0/0 instead of an error); the gate caught it before merge, KEEP-PINNED would have avoided the break but also frozen out #1688 (gsd-pi data-loss fix) and the gstack #1911 guards indefinitely.
 - **Alternatives rejected**: KEEP-PINNED unless CVE (job6-batch-3 default) — optimizes for zero-gate-work, pays for it by sitting on fail-open security guards and data-loss bugs with no formal CVE filed; blanket "always latest, no gate" — the gsd-pi break shows why the gate stays mandatory, this is not a license to skip it.
 - **Caveats**: not every dep took the full pull — graphifyy's hook-guard rewrite (a config-protected file) was surfaced with a diff and the user declined to adopt it this round (binary upgraded, hook install skipped); MCP magic version pin was declined by user call. Policy is "latest, gated", not "latest, no exceptions".
 - **Reference**: `.audit/job6-report.md`; commits `b4896c9` (gsd-pi), `2813e55` (gstack), `00c97bc` (docs); [[LRN-107]] (secrets-subagent value-copy ban, same job's incident).
 ---
 ## BDR-057 — job7: secrets by reference not by value; redact at capture, not just at rest
 - **Date**: 2026-07-07
 - **Status**: accepted
 - **Decision**: two-part posture from the job7 triage (`.audit/job7/ALL-REDACTED.json`, 5+ leak classes across `~/.claude` and repos). (1) Wherever the consuming tool supports it, wire secrets BY REFERENCE (`${VAR}` expansion), not by value — closed the concrete case: `lib/toggle-external.sh`'s `claude mcp add magic --env API_KEY="$MAGIC_API_KEY"` materialized the key as plaintext into `~/.claude.json` (a 2nd copy outside the `~/.claude/.env` canonical); fixed to `--env 'API_KEY=${MAGIC_API_KEY}'`, with the var reaching `claude` only via a scoped `~/.bashrc` wrapper function (subshell + exec — never the ambient shell). (2) Redact AT THE CAPTURE POINT, not just after the fact: `hooks/rtk-rewrite.sh` now appends a redaction pipe to bare `printenv`/`env` dumps before they can reach stdout/the transcript (the GITEA leak's actual vector), instead of relying solely on scrubbing artifacts after the fact.
 - **Why**: the job6 incident ([[LRN-107]]) and the GITEA leak both trace back to a secret VALUE existing somewhere it didn't strictly need to (a config field, a raw env dump) rather than a reference/redacted form. Fixing storage-at-rest (scrub backups) treats the symptom and must be redone every time a new copy appears (5 rotating `.claude.json.backup.*` files, 2 of 5 still had it live mid-job7 despite the canonical fix already applied) — fixing the SOURCE (don't materialize the value; redact before the dump leaves the process) is the only version that doesn't need repeating.
 - **Alternatives rejected**: scrub-only (chosen as the fallback in job7's own instructions if reference-by-value support were absent) — verified Claude Code DOES support `${VAR}` expansion in `mcpServers` config (user + project scope, `env`/`command`/`args`/`url`/`headers` fields — code.claude.com/docs/en/mcp.md), so the reference form was available and preferred; global `export MAGIC_API_KEY` in `~/.bashrc` — works but broadens the secret's exposure to every subprocess of every shell session, defeating the point of the redaction hook (rejected by user in favor of the scoped wrapper).
 - **Reference**: `lib/toggle-external.sh:191-192`, `hooks/rtk-rewrite.sh`, `README.md` "Adding an MCP server that needs a secret", `.gitleaks.toml`, `lib/gitflow.sh` `_gitflow_emit_pre_commit`, `Makefile` `scan-secrets`; commits `b9300c3`/`3340c7d`/`17bdd08`/`5d5b386`. Linked to [[BDR-026]] (canonical vault this closes a leak vector against), [[LRN-108]] (the `claude mcp add --env` trap).
 - **Caveat — contradicts job6's own finding same day**: job6's journal (2026-07-07, earlier same day) states "`${VAR}` env-expansion confirmed unsupported at `~/.claude.json` user scope after 2 rounds of sourced doc lookup". job7's doc lookup (claude-code-guide agent, same day) found it IS supported at user scope, citing code.claude.com/docs/en/mcp.md + a v2.1.161 changelog entry. Not reconciled — could be a version bump between the two lookups, or job6's research being wrong. The `${MAGIC_API_KEY}` rewrite is live (`claude mcp list` recognizes the reference and reports the var missing, which requires the CLI to have at least PARSED the `${...}` syntax) but full end-to-end confirmation (restart terminal + Claude Code, verify magic MCP reconnects) is still a residual the user needs to do — see BDR-057's own commit message.
 ## BDR-058 — job8: darwin-skill reinstall full pinned tree, detached HEAD
 - **Date**: 2026-07-07
 - **Status**: accepted
 - **Decision**: darwin-skill non-functional past SKILL.md text — `references/`, `scripts/`, `templates/` absent, referenced but never fetched. Root cause: `~/.agents/.skill-lock.json` `skillPath: "SKILL.md"` — installer (`skills` CLI, vercel-labs/skills) fetches ONLY that one file, not sibling dirs. Upstream repo HEAD (`7c7b7909b630dc3b5cbb91bd4bcb1b10bfb1f894`) matches lockfile hash exactly — zero drift, zero tamper, SKILL.md byte-identical old vs new. Fix: cloned upstream at that SHA, copied full tree into `~/.agents/skills/darwin-skill/`, verified all 5 referenced paths present, HEAD detached (no branch tracking, no silent advance on a stray `git pull`). Old single-file dir backed up to `~/.agents/skills/.job8-backups/darwin-skill.single-file.<ts>` first.
 - **Why**: user picked reinstall-pinned over remove/keep-broken (job8 audit §4 item 4, 3-way choice). Unverifiable skill can't be trusted; user wants the optimizer kept, not removed.
 - **Alternatives rejected**: remove entry (kills wanted function); keep as-is (fails job8's own audit bar — unverifiable); flat-copy without `.git` (matches other 34 dormant skills' convention but drops verifiable pin — kept `.git` detached instead, darwin-skill now 2nd real SHA-pin in the whole trust chain after gstack, job8 report §5).
 - **Reference**: `~/.agents/skills/darwin-skill/` (detached HEAD `7c7b790`), `~/.agents/.skill-lock.json` (untouched, hash still accurate), backup at `~/.agents/skills/.job8-backups/`. Outside this repo — no commit here covers the file placement itself, this entry is the record. Git-commit whole-`.claude/skills`-tree scope (job8 C.2, `SKILL.md:115/201`) NOT restricted — 3rd-party pinned code, patching it breaks the pin; accepted as documented risk, human-checkpoint-gated per job8 report. Linked to [[LRN-109]].
 ## BDR-059 — job8: explicit ask-gate for all 4 magic MCP tools, empty allow stays empty
 - **Date**: 2026-07-07
 - **Status**: accepted
 - **Decision**: `settings.json` `permissions.ask` now explicitly lists all 4 `mcp__magic__*` tools (`21st_magic_component_builder`, `21st_magic_component_refiner`, `21st_magic_component_inspiration`, `logo_search`). `permissions.allow` gets ZERO magic entries — no allowlist tightening, the job8 report's "frictionless" diff (allowlist logo_search + inspiration) was explicitly rejected. Confirmation required on every magic call, no exceptions, no auto-exec ever, no wildcard.
 - **Why**: job8 §3/§4 found zero real `mcp__magic__*` invocations ever (transcript census) and one SUSPECT finding (`21st_magic_component_builder` unauthenticated callback-injection channel, [[LRN-110]]). Prior state relied on undocumented absence-means-ask fallthrough — user wants the gate EXPLICIT so it can't silently regress if `permissions.allow` ever gets a careless wildcard or the default-mode semantics change.
 - **Alternatives rejected**: leave everything absent (report's own recommended default) — works today but is silent/undocumented, exactly the posture the user wanted to close; allowlist `logo_search` + `21st_magic_component_inspiration` for frictionless design work (job8 report §3 "frictionless" diff) — explicitly declined, real usage is zero so friction costs nothing.
 - **Reference**: `settings.json` `permissions.ask`, commit `bb7f25a`. Linked to [[LRN-110]] (component_builder risk), [[LRN-111]] (empty-allowlist validity when usage is zero).
 ## BDR-060 — job9: CC orchestration floor = v2.1.172 (nested dispatch), supersedes implicit v2.1.83 whole-system floor
 - **Date**: 2026-07-08
 - **Status**: accepted
 - **Supersedes**: implicit "v2.1.83 = whole-system floor" premise (a misread of [[BDR-004]]'s `decisions.md:133` auto-mode caveat).
 - **Decision**: orchestration floor for any NESTED subagent dispatch = Claude Code **v2.1.172** (nesting stabilized: "let subagents spawn their own subagents", hard cap 5 levels, `Agent` must be in the subagent's `tools:` to nest). Live env confirmed **v2.1.203** (user, nesting supported, cap 5). BDR-004:133 stays UNCHANGED — its `v2.1.83+` is correct for AUTO MODE specifically; the nesting floor is a distinct, higher constraint recorded here (registry is append-only, and BDR-004 is factually right for its scope).
 - **Why**: the whole job1-9 audit series operated on the premise *"CC flattens to 1 level → a 2-level subagent design is silently broken."* That describes the **pre-2.1.172** regime. Corrected in job9 via `claude-code-guide` (official docs `code.claude.com/docs/en/agent-sdk/subagents.md`) + user confirmation of live v2.1.203 → depth findings are VERSION-CONTINGENT, not broken. Path b ([[BDR-061]]) removes the seo/geo analyzers' dependence on nesting, but client-handover's `general-purpose → /seo → seo-analyzer` chain still nests (L1→L2), so the floor stands for the orchestration design.
 - **Alternatives rejected**: keep the implicit v2.1.83 floor — predates nesting, mislabels version-contingent flows as "BROKEN"; hard-gate CC version in `doctor.sh` — deferred (path b de-risks the analyzers; a doctor warn-gate is an optional follow-up, and `doctor.sh` is config-guarded → sentinel cost not justified now); raise BDR-004:133 to v2.1.172 — WRONG, that caveat is auto-mode-specific (auto mode works from 2.1.83) and rewriting it would violate append-only + inject a factual error.
 - **Reference**: `.audit/job9-report.md` §Premise + §6 D-version-floor; `decisions.md:133` (BDR-004 auto-mode caveat, unchanged). Linked to [[BDR-061]] (path-b), [[LRN-112]] (nesting mechanics).
 ## BDR-061 — job9: seo/geo analyzers emit a fix-bundle applied at L1 by doctrine (validator-analyzer pattern)
 - **Date**: 2026-07-08
 - **Status**: accepted
 - **Decision**: `seo-analyzer` + `geo-analyzer` re-architected to the `validator-analyzer` contract — they AUDIT and EMIT a machine-parseable `## FIX BUNDLE` terminated by the verbatim `READY TO APPLY — awaiting dispatcher confirmation` sentinel; they NEVER edit code and NEVER dispatch a sub-agent (`Agent` dropped from both `tools:`). The DISPATCHER applies at **L1 from its own main loop**: `/seo` (new STEP 1.5) + `/geo` (rewritten to dispatch+apply, mirrors `/web-validate`) dispatch `hotfixer`/`feater` at L1; `/harden` keeps its existing direct-Edit STEP 3 (already end-to-end path-b); `/onboard` stays audit-only (bundle produced, deferred to backlog STEP 9). AUTO tier applies unconfirmed; GATED tier (seo D/E · geo G5) requires explicit accord; USER ACTIONS → report §11.
 - **Why**: by DOCTRINE, not version constraint. Before: analyzer STEP 12/13 dispatched hotfixer/feater; when the analyzer was itself a subagent (`/seo` → analyzer at L1), that dispatch was **L2 nesting** → silent no-op on CC<2.1.172, and both analyzers forbade direct edits → the reported bug: *report produced, ZERO fix applied*. The bundle→L1 pattern (a) lands fixes on ANY CC version (single dispatch level), (b) gives fresh-context specialist fixes without depth risk, (c) dissolves the `/seo` parallel-edit race (fixes now applied serially by the dispatcher, by file ownership). `/harden` already proved the pattern in-repo. Chosen even though [[BDR-060]] confirms live nesting works — version-robust by design beats version-contingent.
 - **Alternatives rejected**: only raise the version floor (BDR-060 alone) — leaves the analyzers version-contingent, and the `/seo` nested-fix design fragile; keep analyzers self-applying but require CC≥2.1.172 — works on current env but not robust and keeps the parallel-edit race; make the dispatcher apply via direct Edit everywhere (like /harden) instead of hotfixer/feater — loses the fresh-context specialist fix; kept direct-Edit only for /harden's tiny scope.
 - **Verification**: `make test` green + 4 real smokes — analyzer emits bundle + edits nothing (md5 unchanged); AUTO fix lands on disk via L1 hotfixer with no confirmation (the exact previously-broken path); GATED withheld pre-approval then applied post-accord; /onboard writes only the report, zero source files.
 - **Reference**: `agents/seo-analyzer.md` STEP 12, `agents/geo-analyzer.md` STEP 13, `skills/seo/SKILL.md` STEP 1.5, `skills/geo/SKILL.md`, `agents/validator-analyzer.md` (reference contract), `.audit/job9-report.md` §6 option (b); commits `a5a7b54`/`6df42e4`/`c498b93`/`70fb3b4`. Linked to [[BDR-060]] (nesting floor), [[LRN-112]] (nesting mechanics).
 ## BDR-062 — supersede BDR-031's 275-line CLAUDE.md target: 305 is the assumed reality
 - **Date**: 2026-07-08
 - **Status**: accepted (supersedes the 275-line density TARGET of [[BDR-031]] only; BDR-031's core principle — lightening = compression, not path-scope/externalization — stands unchanged)
 - **Decision**: The global CLAUDE.md sits at 305 lines and stays there. job1's density pass took it 319→305 and no later job re-inflated it; the extraction BDR-031 called for is done. Reaching the old 275 target (or even the 280 guard threshold) now costs clarity more than it saves tokens. The `hooks/session-start.sh` guard threshold is realigned 280→320: still catches genuine regression (real bloat past 320) but stops firing a permanent "density pass requis" warning on an assumed-final 305.
 - **Why**: the review (`.audit/review-release-1.0.0.md` A6) found the guard had warned every session since job1 without the target ever being met — a self-inflicted permanent warning, not an actionable signal. A gate that never goes green trains you to ignore it. Realign to reality; keep a 15-line margin so real regressions still surface.
 - **Alternatives rejected**: (a) finish the compression 305→≤275 — the remaining lines are load-bearing constraints, not filler; further squeeze loses clarity for a marginal token gain on a solo repo. (b) leave the guard at 280 and accept the permanent warning — a permanently-red non-blocking gate is noise. (c) rewrite BDR-031 — registries are append-only; supersede the target, keep the principle.
 - **Reference**: `hooks/session-start.sh:202-211`; supersedes the 275 target in [[BDR-031]] (principle kept). Review remediation A6, 2026-07-08.
 ## BDR-063 — GSC multi-account: OAuth2 installed-app flow + label-keyed token store
 - **Date**: 2026-07-10
 - **Status**: accepted (shipped `bb1fbb2`, develop)
 - **Decision**: `/seo` FULL pulls real Search Console + CrUX via a `lib/seo-data/` engine. Auth = OAuth2 installed-app flow (one-time interactive consent, `make seo-connect`), scope `webmasters.readonly` ONLY (least priv). Refresh tokens in per-label store `~/.claude/seo-data/tokens.json` (0600 file / 0700 dir, atomic tmp→fsync→rename under fcntl lock, tokens redacted from listing, gitleaks-allowlisted). `(account, property)` explicit args on every call — NO global mutable "current account" → two concurrent site audits never conflict.
 - **Why**: user needs real field data (the one edge marketplace `claude-seo` had that personal skills lacked); multi-account without cross-site leakage; secrets never in code (all from `~/.claude/.env`).
 - **Alternatives rejected**: (a) service-account — GSC needs per-property owner grant + no interactive consent, wrong for a personal multi-client tool. (b) API-key-only — GSC has no key auth (CrUX does → `CRUX_API_KEY`). (c) single "current account" global + switch verb — a race the moment two audits run; explicit args dissolve it by construction.
 - **Reference**: `lib/seo-data/` (tokenstore.py, connect.py, google_seo.py, fetch.sh), `lib/seo-data/README.md`; fronted by [[LRN-119]] (fail-open contract).
 ---
 ## BDR-064 — Global memory split: repo global file → CLAUDE.global.md, CLAUDE.md freed for project scope
 - **Date**: 2026-07-14
 - **Status**: accepted (shipped feature/claude-global-md-rename, merge pending human GO)
 - **Decision**: repo-root global memory `git mv` → `CLAUDE.global.md`; deployed name unchanged (`~/.claude/CLAUDE.md` symlink via link.sh). `CLAUDE.md` name freed → real project-scope memory for claude-config (Health Stack + rules/ doctrine — ex-"This repo only" section + ex-rules/README body; rules/README = 3-line pointer, keeps `paths:` frontmatter). Wording rule (user-arbitrated): consumer-facing hook strings say "global CLAUDE.md" (deployed name — foreign sessions resolve via symlink, repo filename means nothing there); maintainer comments say `CLAUDE.global.md`. Guards follow: session-start 320-guard path, doctor EXACT readlink-target check (new), GUARDED_CONFIGS 4 entries (keeps "CLAUDE.md" — graphify rewrite target = project file now), doc-commit exclusions, CHANGELOG BREAKING(layout) line ("run bash link.sh once after pull").
 - **Why**: "This repo only" section + rules/README doctrine loaded in EVERY project (~40+280 tok waste + foreign-project glob over-match); repo had no project-scope memory slot — filename occupied by global content.
 - **Alternatives rejected**: `CLAUDE.prod.md` name ("prod" implies deploy env that doesn't exist); project `.claude/rules/repo.md` (works, less idiomatic than project CLAUDE.md, no natural home for future repo-specific content). NOT a revival of BDR-021's rejected 2-file split — that was global content in 2 SYNCED files; here scopes disjoint, zero sync.
 - **Reference**: feature/claude-global-md-rename (9496538 rename R98%, e9a38a0 guards), spec `docs/superpowers/specs/2026-07-12-claude-global-md-rename-design.md`. Linked [[BDR-021]], [[BDR-031]], [[BDR-062]], [[LRN-122]], [[LRN-123]].
 ---
 ## BDR-065 — Transient planning artifacts: committed during run, deleted post-merge
 - **Date**: 2026-07-14
 - **Status**: accepted
 - **Decision**: superpowers spec/plan docs (`docs/superpowers/{specs,plans}/`) = run-time artifacts. Lifecycle: committed as feature branch's first commit (subagent briefs extracted from plan on disk; verifier + final review reference them; survive compaction + foreign worktrees) → DELETED in post-merge cleanup chore. Git history at the feature commits = the archive (`git show <sha>:docs/...` recovers them). Durable knowledge lives in `.claude/memory/` registries + contract files, never in spec/plan. Codified in project CLAUDE.md §Transient planning artifacts.
 - **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]].
 ---
 ## BDR-066 — Model routing: reflection inline (session big model), executors pinned sonnet, blocking gate
 - **Date**: 2026-07-15
 - **Status**: accepted (partial supersede of BDR-050: /feat dev no longer inline; bugfix/hotfix dev-inline CONSERVED)
 - **Decision**: reflection (brainstorm, plan, contract, audit judgment, loop decisions) runs on session model (Fable; Opus fallback) — inline or inherit subagents, never pinned down. Execution (code from closed plan, fix-bundle application) runs sonnet-pinned subagents: feater + hotfixer pinned sonnet; SDD implementation+review subagents dispatched `model: "sonnet"` (ship-feature/init-project); web-validate fixes via hotfixer L1 (was inline Edit). analyzer haiku pin REMOVED (digest feeds plan = reflection tier). verifier + security-auditor STAY sonnet (job9 confirmed — procedural gates, ≤3×/loop). Blocking gate `lib/model-gate.md` (self-check + witness `lib/model-check.sh`) wired in 12 reflection orchestrators; small → STOP, unknown → fail-visible; census guard `lib/tests/model-routing.test.sh` flip-tested.
 - **Why**: big-model quota burned on mechanical execution (Fable exhausted mid-job8); plan closed at dispatch → executor needs obedience not judgment; fresh sonnet gates catch executor drift.
 - **Alternatives rejected**: opus pins on audit agents (session-independent) — rejected: session assumed big + blocking gate as backstop, one tier fewer; advisory gate — rejected by user, blocking; split bugfix/hotfix too — rejected: bugfix investigation interleaved w/ fix, hotfix gain marginal vs dispatch overhead.
 - **Caveats**: client-handover-writer conversion (inline-load → sonnet dispatch, 11 human-gate sites to relocate) DEFERRED to own plan — its opus pin stays inert meanwhile; feater cannot ask → NEED-DECISION report = escalation valve, plan must close decisions; witness reads settings.json — lags `--model`-launched sessions (self-check compensates).
 - **Caveat (execution)**: /feat re-arch broke 5 stale assertions in lib/tests/loops-light.test.sh (locked OLD feater architecture) — repointed to skills/feat/SKILL.md (FSK, mirrors HOT/HSK split) + new dispatch lock + 1-line reflow in feat SKILL for single-line grep lock (LRN-093 class).
 - **Wave 2 (2026-07-15, user directive)**: wave-1 exclusion list left execution running on the big session model = the waste this split kills. REVERSES the "split hotfix rejected" alternative above (reason held for bugfix — investigation interleaved w/ fix — but NOT hotfix: LOCATE→apply is linear/separable). Changes: /hotfix split like /feat (LOCATE reflection inline + MODEL GATE, hotfixer sonnet EXECUTOR — rewritten dual-use: also the seo/geo/web-validate L1 applier; revert-not-loop preserved) → hotfix JOINS gated group, census 12→13. /commit-change dispatches sonnet commit-changer (propose→dispatcher gates→apply; grouping ON sonnet so NO model gate; AskUserQuestion dropped from agent). /release-candidate dispatches new sonnet release-executor (2 spans prep/finish; when-to-release + push + version-number decision STAY in dispatcher). /doc → doc-syncer (sonnet) dispatch; /status → status-reporter (kept HAIKU — right tier for read-only collection; win = off big model, not the tier). Gate exclusion list now = commit-change/doc/status/release-candidate. Consumer-staleness swept (LRN-113): feat Rule 1 DOWNGRADE + feat commit-split both repointed off the bare executor agents to the /hotfix + /commit-change skills.
 - **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).
@@ -33,6 +33,9 @@ rules:
 | EVAL-010 | 2026-06-29 | prune-memory hardening: RED-7 deterministic fix + RED-8 accept + 34-row index backfill | keep |
 | EVAL-011 | 2026-06-30 | /reconcile build: RED contaminated→corrected (unguided control), GREEN behavioral confirmed, dogfooded on itself | keep |
 | EVAL-012 | 2026-06-30 | /release-candidate build: RED (gitflow fans out, no tag) → GREEN 5/5 (tag), throwaway-repo flow replay | keep |
 | 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 |
 ---
@@ -136,3 +139,84 @@ rules:
 - **method**: read-first cartography (gitflow release wired: start L49 base=develop, finish L108-111 fan-out; grep-confirmed NO `git tag` → the gap). TDD on a throwaway repo: RED (`RC_TAG=0`) = start→prep→finish → 4 GREEN (fan-out / merge-back / branch-deleted / CHANGELOG) + 1 RED (tag v4.0.0 absent — gitflow never tags); GREEN (`RC_TAG=1`) = + `git tag -a` → 5/5, tag on main's merge commit. shellcheck clean (caught + fixed an SC2164 mid-build).
 - **anomalies**: (1) versioning reasoning corrected by the user — number derives from change nature, not justification ([[LRN-078]]); caveman verified `Removed` not breaking from refs, not memory. (2) tag-in-skill consequence (direct-lib release wouldn't tag) made explicit + accepted, not left implicit. (3) layers kept distinct — this built+tested the skill; cutting the real v4.0.0 is a separate later act.
 - **action**: keep. RED red for the right reason (gap = tag), GREEN closes it, teeth proven.
 ## EVAL-013 — /reconcile in REAL USAGE: unanticipated drift found + false-positive rejected off-fixture
 - **Date**: 2026-06-30
 - **output**: reconcile run on live claude-config repo (develop) → write-back `.claude/tasks/TODO.md` (commit `09200c5`, pushed): `/release-candidate` QUEUED→SHIPPED + 4 subtasks [ ]→[x]; 3 stale `[branch …]` headers→[DONE]. Engine `lib/reconcile.sh` orchestrated by hand (enumerate_ids + oracle_* probes + verdict + A/B/C gate). Distinct from [[EVAL-011]] (BUILD: fixture RED/GREEN + self-dogfood) — this = USAGE on fresh real drift.
 - **method**: real run, no fixture. Per declared item, oracle vs git/fs: `oracle_path_present` (SKILL.md d3d6ced), `oracle_msg_committed`, `oracle_merge_done` (3 branches merged+deleted), tag v4.0.0 + version.txt. `blk_open` → 3 external (BLK-001/003/009, no drift). `deferrals` (marked) + `contradiction_candidates`. Measurable: 1 primary gap (/release-candidate QUEUED-but-done, oracle-proven) + 3 secondary (header-marker drift) found · 1 false positive rejected · 0 false gap asserted.
 - **anomalies**: none wrong. 2 capabilities PROVEN that [[EVAL-011]] did NOT: (a) finds UNANTICIPATED gaps — the 3 `[branch X]` headers = a header-marker drift CLASS beyond checkbox drift, not designed-for, caught anyway (merge_done=YES + no local branch). Coverage wider than spec. (b) rejects FALSE POSITIVE on REAL data — `--help` candidate (BDR-001 title ⇄ TODO L134) surfaced as CANDIDATE not verdict; review → both WON'T-BUILD, aligned, not contradiction. Recursive coherence holds OFF-fixture. Design note: NO merge-time header-update hook — merge does merge, /reconcile = periodic catch (separation kept, finding 1).
 - **action**: keep. Real-world value proven — known gap + 2 unknown + false-positive rejected, zero false assertion.
 ## EVAL-014 — /tour GREEN run: 6/6 RED gaps closed, disk-verified; re-verify caught agent's own regression
 - **Date**: 2026-07-05
 - **output**: GREEN subagent run w/ skill on fresh seeded fixture: 3 iterations CONVERGED, 7 commits on `chore/tour-2026-07-04` (unmerged), TOUR.md 18 findings (SEC×6 / CLN×5 / REC×2 / DOC×2 / INF×2), functional suite 8/8 PASS, semgrep PASS(0) final. RED baseline same fixture = 6 gaps ([[LRN-099]]).
 - **method**: main session verified ON DISK, not from agent summary: TODO zero-diff vs develop ✓, no target `.claude/memory/` created ✓, per-iteration semgrep report files present ✓, TOUR.md committed ✓, zero scope creep (no .gitignore) ✓, main/develop untouched + branch unmerged ✓, 3-iteration bound held ✓.
 - **anomalies**: (1) scratch semgrep files untracked → tree dirty at end, would self-block next run — patched STEP 3.2 [[LRN-100]]; (2) SEC-2 API-BREAKING fix (new required header) unflagged — patched template BREAKING tag; (3) positive: it2 re-verify caught regression of agent's OWN fix (`compare_digest(str)` raises on non-ASCII → 500 not 403), fixed + functionally proven it3 — re-verify loop has real teeth.
 - **action**: keep (skill shipped). REFACTOR additions not re-run through 3rd full pass — re-test at first real use ([[LRN-100]]).
 ## EVAL-015 — /tour first REAL run (report-only, bchanot-cv): REFACTOR additions validated; premise corrected by user
 - **Date**: 2026-07-05
 - **output**: report-only tour on live repo bchanot-cv: 4 parallel read-only audits (security-auditor semgrep BLOCK(1), cso posture 3 med/2 low/5 info, clean 10 findings, doc 2 drifts) + inline reconcile (ZERO drift — BLK-001 even live-confirmed via prod favicon 200). 14 findings folded into committed TOUR.md (5a813df, `.claude/**` on develop), scratch reports deleted, tree clean at end.
 - **method**: real repo, no fixture. Deferred re-test executed: STEP 3.2 cleanup HELD (no self-block for next run), BREAKING tag correctly N/A (zero fixes in report-only). Cross-checks: cso live-confirmed SEC-2 (zero security headers served) — config-only review would have missed it ([[LRN-101]]).
 - **anomalies**: (1) skill gap — report-only + clean tree has no branch, so the report commit lands on develop via the `.claude/**` exemption; works, but the placement is a judgment call the SKILL.md doesn't specify → candidate patch (needs its own failing test per Iron Law). (2) premise corrected by USER after the run: prod = native nginx, NOT the repo's Docker stack → container findings (SEC-1/4) latent, live header fix (SEC-2/3) belongs to VPS config outside the repo; audit scoping must confirm the serving stack first ([[LRN-101]] corollary). (3) parallel-phases deviation from the skill's sequential A→D held safely (report-only ⇒ no mutations between phases).
 - **action**: keep. Skill validated on real drift; two refinement candidates noted (report-commit placement, serving-stack precheck), neither blocking.
 - **backmerge**: from release/1.0.0 (74d3804) — 2026-07-08 review remediation A3.
 ## EVAL-016 — /deploy first REAL run (bchanot-cv): bootstrap→instantiate→hand-back→mark, full cycle OK
 - **Date**: 2026-07-05
 - **output**: bootstrap Path B (4-field interview → @delta-annotated PROCEDURE.md + seeded INCIDENTS, commit `5fe8b41` via deploy-commit.sh rc=0) → first deploy: base null → delta = full tree (26 files), `@delta:rebuild when=` matched → NEXT.sh 3 steps → GATE all → PENDING.json bridge → hand-back → user "Deployed OK" → MARK: STATE.json (`deployed_sha` = bridge target, NOT HEAD), local tag `deploy/2026-07-05`, oracle commit `395c77b`, bridge consumed, tree clean.
 - **method**: real prod deploy (VPS). Independent live proof post-mark: curl bchanot.fr → 200 + nosniff + X-Frame-Options + CSP + HSTS + versionless server — tour SEC-2 fixed end-to-end, tour→prod loop closed.
 - **anomalies**: (1) NOT exercised: cold cross-session resume + STEP 4 learn (0 incidents) — natural test at next deploy/failure. (2) UX gap, user feedback: compound `ssh host "cd … && …"` one-liners ≠ wanted session style (one command per line), and the checklist lived only on disk — skill patched same day (step=block grammar, shape rule, hand-back prints NEXT.sh inline; template + bchanot-cv runbook restyled). Re-dogfood at next deploy.
 - **action**: keep. Two-moment contract works in-session; disk artifacts coherent throughout.
 ## EVAL-017 — job2 audit: fresh-context verify pass caught 3 explorer false claims
 - **Date**: 2026-07-06
 - **output**: `.audit/job2-report.md` — 17 findings, 26 diffs, execution prompt. 4 explorers (skills/agents/hooks+lib/registry x-ref) + 1 docs agent (claude-code-guide), then 3 fresh verifiers re-checked all 17 findings + 9 registry quotes from list+paths only.
 - **method**: verifiers blind to auditor reasoning. Mid-run session-limit kill all 3 → resumed from transcript via SendMessage, all completed.
 - **result**: 15/17 REPRODUCED, 2 PARTIALLY (wording only: F3 "exactly 4"→4-of-54; F14 soft precondition existed). 0 discarded. Registry quotes 9/9 verbatim. Exact char counts 100% match (4840 total agents).
 - **anomalies**: 3 explorer false claims, ALL about harness semantics not file content: (1) agents-explorer — `Agent` tool "non-canonical" + `memory:`/`effort:` frontmatter "invalid": wrong, all documented; (2) skills-explorer — skills/gstack/ "stray orphan": refuted by link.sh:54-57 deliberate plumbing; (3) guide agent — `[1m]` model suffix "invalid ANSI": refuted, /model writes it itself. File-content claims (counts, quotes, refs): zero errors.
 - **action**: harness-semantics claims from explorers ALWAYS cross-check vs docs/live evidence; file-content claims reliable after one verify pass.
 ## EVAL-018 — job3 docs-drift audit + execution: 46/46 verified, 20/23 fixes shipped, zero residual
 - **Date**: 2026-07-06
 - **output**: `.audit/job3-report.md` — 46 findings (docs vs repo reality at defc26c), 19 diffs, execution prompt. 4 explorers (orchestrators/workflow-skills/web-skills/graphify+deploy+docs) + 6 fresh verifiers re-checked all 46 findings + 5 registry quotes (list+paths only). Then executed with user decisions injected: 20 commits on `chore/job3-fixes` (BDR-054 supersedes BDR-038 + banners, D1 deploy paths, C3 geo-analyzer path, onboard/init-project/profile/gitflow/close/client-handover/harden/seo/web-validate/depth-matrix bodies, README, session-start hook, memory templates, project-CLAUDE template, SETTINGS.md).
 - **method**: verifiers blind to auditor reasoning; 3 killed mid-run by session limit, resumed from transcript, all completed. Post-fix: 3 fresh-context re-sweep verifiers (one per file group) confirmed old assertions gone + new text consistent with reality anchors; `make test` and `bash lib/tests/run-reconcile.sh` re-run to confirm no regression.
 - **result**: 46/46 REPRODUCED pre-fix (3 corrected attributions). Post-fix re-sweep: 0 residual findings from job3's own edits (1 pre-existing minor abbreviation noted, informational only). `make test` all green. `run-reconcile.sh` unchanged 18 GREEN/2 RED (B1 deliberately untouched, see blocker below).
 - **anomalies**: (1) B1 (reconcile fixture hermeticization) BLOCKED — `lib/tests/` is guarded by the same config-protection.sh gate as `hooks/`, and the user's sentinel pre-authorization was scoped only to `[SENTINEL-REQUIRED]` hook edits; the auto-mode classifier correctly refused the sentinel for a lib/tests/ write outside that scope. (2) Verification sweep incidentally surfaced 2 pre-existing, out-of-job3-scope drifts: `agents/client-handover-writer.md:885` still says "4-chapter structure" (contradicts its own lines 23-43 "6 chapters", predates job3); `.claude/memory/decisions.md` index has no row for BDR-053 (body exists, gap from job2).
 - **action**: keep. B1 needs a follow-up session with explicit lib/tests/ sentinel authorization. The 2 incidental findings are candidates for a future audit-delta pass, not fixed here (out of scope).
 ## EVAL-019 — job4 test-gap audit + execution: 11 specs + 5 fixes/seams, every mutation red-green verified, zero residual
 - **Date**: 2026-07-06
 - **output**: `.audit/job4-report.md` — 22 findings across hooks/gitflow-guardrails/session-libs/reconcile-fixtures/graphify (20 confirmed, 1 refuted-retargeted J4-05b, 1 dropped stale). Executed on `chore/job4-tests` (unmerged, 20 commits): SPEC-01 Makefile aggregation, SPEC-02/04/05 gitflow T13/T14/T15, SPEC-08/10/09 reconcile oracle-sandbox + decisions-fixture + snapshot-retirement (in that order), SPEC-03 curated-config-guard (new file), SPEC-07 doc-shape removed envelope, SPEC-11 prune-suite source fix, SPEC-06 config-protection payload matrix (gated, user-confirmed before writing); J4-04 memory-commit fail-loud (test-red then fix, 2 commits), J4-20 toggle-external logical-cd fix (test-red then fix, 2 commits, BLK-006 class); SEAMS bundle (profile.sh/toggle-external.sh/design-tool-gate.sh/session-start.sh, env-var only); install-plugins fail-closed on mktemp failure; J4-22 deploy-commit exit taxonomy (rc 6 + deploy/SKILL.md doc-sync, user GO after caller census).
 - **method**: every new/changed test's mutation demonstrated RED on a scratch/lean copy (never the working tree) before commit, then GREEN on the real repo confirmed before each commit. Sentinel created immediately before each guarded lib/tests/ write (19 consumed, all logged with per-spec reasons). SPEC-06 (config-protection's own test) held at an explicit user-confirmed checkpoint despite the formal AUTHORIZATION line already saying so — the user's instructions contained a real ambiguity (free-text said "STOP and ask" for this one spec, the filled-in template said "AUTHORIZED"), resolved by asking rather than guessing.
 - **result**: `make test` grew from 71 (gitflow only, 5 suites excluded) to 90 gitflow + all 5 previously-excluded run-*.sh suites now included (13→16 deterministic, 32 doc-commit unchanged, 19→23 doc-shape, 20→25 reconcile, 5/5 release) + 4 *.test.sh grew or were added (20→24 config-protection, 0→6 curated-config-guard new, 13→16 deploy-commit, 0→1 toggle-external-repo-resolution new). Full `make test` exit 0 throughout, zero regression across 20 commits.
 - **anomalies**: (1) `/tmp` (tmpfs, 7.4G) exhausted mid-session from repeating full-repo `cp -r` (incl. `.git` + gstack submodule, ~1.6G each) for the first 4 specs' scratch copies — the Bash tool became universally unresponsive (even `true`/`echo` failed with exit 1/134) until the user cleared `/tmp` manually; switched to copying only the minimal file subset each mutation needs for the remaining ~16 specs/fixes. (2) config-protection.sh's guard matches by path SUFFIX regardless of directory, so scratch-copy mutations of `lib/gitflow.sh`/`hooks/*.sh` tripped it too even though they were throwaway and never committed — used Bash/sed/perl (shell-level file ops, which the hook's own header comment says it never covers) instead of Edit/Write for those mutations, reserving the sentinel strictly for genuine `lib/tests/` writes. (3) J4-22's caller census (an explicit gate in the report) found `deploy/SKILL.md` parses `deploy-commit.sh`'s exit codes — flagged before committing, user confirmed GO to extend that doc too rather than leaving it stale.
 - **action**: keep. Branch unmerged (`chore/job4-tests`, human gate per report). Backlog carried forward unbuilt, deliberately per report scope: J4-13 (rtk-rewrite), J4-14 full (session-start banner truth-table — only the offline-fetch seam landed), J4-15/16/17 (toggle-external 3-state/attribution-census/memory-commit pending verb), J4-18 (graphify pytest greenfield), and the hermetic suites the SEAMS bundle unlocked but didn't build for profile.sh/toggle-external.sh/design-tool-gate.sh (J4-19/20/21, now spec-able instead of UNTESTABLE).
 ## EVAL-020 — job6 dep upgrade execution: 5 deps sequenced by risk, 2 real STOP gates hit and resolved live, zero regression
 - **Date**: 2026-07-07
 - **output**: `.audit/job6-report.md` execution — ctx7 0.5.3→0.5.4 (BATCH-1, zero repo diff), graphifyy binary 0.9.6→0.9.8 (hook-adoption declined), gsd-pi 2.64.0→3.0.0 (`b4896c9`), gstack submodule 070722a→11de390 (`2813e55`), supply-chain doc pass (`00c97bc`) — all on `chore/job6-deps-upgrade`, unmerged, human gate per report.
 - **method**: pre-flight gated on 2 user-confirmed prerequisites (gstack #2047 human review verdict, MAGIC_API_KEY rotation) before any step. Sequenced strictly by risk (BATCH-1 → BATCH-2 ascending); one upgrade = one commit = one gate (make test + named smoke), immediate STOP-and-ask on any ambiguous or destructive fork rather than assuming a default.
 - **result**: 2 real STOP conditions fired and were resolved live, not hypothetically: (1) graphifyy 0.9.8's `graphify install` traced to source (`_install_claude_hook`, pipx venv `__main__.py:2033`) confirmed as a REWRITE of the config-protected `.claude/settings.json` — diff shown, user declined, binary upgraded without hook adoption; (2) gsd-pi 3.0.0 confirmed format-INCOMPATIBLE with `status-reporter.md`'s ROADMAP.md parser by generating a real test milestone in a scratch dir (ADR-013 cutover: no ROADMAP.md at all, DB-authoritative) — user chose "patch now" over rollback, parser rewired to `gsd headless query` JSON, smoke-tested both the absent-`.gsd/` and real-`.gsd/` cases before commit. gstack's local playwright patch (BDR-029) correctly identified as disposable-by-design, backed up before discard anyway (belt-and-suspenders after an auto-mode classifier denial), reapplied via the documented `gstack_bump_playwright_if_unsupported` steps — landed one minor ahead (1.61.1 vs the pre-bump 1.61.0) since upstream had moved between backup and reapply. `make test` green after every commit (90/90 gitflow + suites); `doctor.sh` 0 errors throughout.
 - **anomalies**: (1) mid-session the Bash tool went universally unresponsive (`true`/`echo hello` returning non-zero, no output) right after a large heredoc `git commit` — same `/tmp` exhaustion class as [[EVAL-019]]'s anomaly (1), user confirmed and cleared it; work resumed from the last confirmed git state rather than blindly retrying. (2) MCP magic's requested "reference not plaintext" (BDR-026 pattern) turned out NOT achievable as literally asked — `${VAR}` env expansion is documented for project-scope `.mcp.json` only, not the global `~/.claude.json` where magic is registered `--scope user` (verified via 2 rounds of sourced doc lookup, not assumed); user accepted the practical ceiling (regenerate via `toggle-external.sh disable/enable` to refresh the rotated key, decline the version pin).
 - **action**: keep. Branch unmerged (`chore/job6-deps-upgrade`, gitflow finish = separate human signal per CLAUDE.md). [[BDR-056]] captures the policy reversal this run demonstrated; [[LRN-107]] captures the secrets-copy mandate gap the report's own incident surfaced.
 ## EVAL-021 — adversarial review of the 9-job series (release/1.0.0..develop) + remediation
 - **Date**: 2026-07-08
 - **output**: read-only adversarial review — 11 analyzers (1/job + validator-analyzer contract) + fresh-context verifier on 6 top findings + make test. Report `.audit/review-release-1.0.0.md`: 1 BLOQUANT (A1 trailer), 5 à corriger (A2 gitleaks hook inert, A3 back-merge gap, A4 YAML, A5 geo attribution, A8 smoke-A), 5 mineurs, 10 verified false-positives; jobs 4/5/6/8 CLEAN, validator-analyzer contract SOUND. Remediation (chore/review-remediation): A1/A2/A4/A5 fixed, A8 PROVEN (both /seo+/geo AUTO items land on disk via L1 — no silent no-op), fil-rouge guard added, A3 backfilled + rtk fix ported, A6 threshold realigned.
 - **method**: analyzers write findings to scratch; main loop does the inter-jobs cross-pass + memory-sequence + trailer sweep + cost check; verifier re-derives 6 findings from scratch. Sandbox gotcha logged: `git log | grep` truncates silently → used `git rev-list`.
 - **anomalies**: (1) 2 sub-agent verdicts overturned — job7 CLEAN was wrong (gitleaks hook not wired, [[LRN-114]]) and the contract-agent's tool-grant "defect" was a false-positive ([[LRN-115]]). (2) A8 smoke-A root cause was undocumented in 212f9aa; reconstructed live — dispatcher classifies by batch-id (seo A/B/C, geo G1-G7), tolerant of header wording so items aren't dropped; path-b proven to land AUTO fixes on disk. (3) A7: job1/3f639b3 broke the design-hook oracle ~10h until job2/860b803 — historical; lesson = run make test before merging a branch, not only at finish.
 - **action**: keep. Remediation branch unmerged (human gate). Fil-rouge guard now prevents the partial-fix class ([[LRN-113]]).
 ## EVAL-022 — job9 model pins (BDR-060) were smoke-tested but never recorded as an EVAL (M5 trace)
 - **Date**: 2026-07-08
 - **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.
@@ -261,3 +261,132 @@ rules:
 - Learnings: semver derives from change nature, caveman = Removed not breaking ([[LRN-078]]); orchestrator-skill TDD = throwaway-repo flow replay ([[LRN-079]]).
 - CHANGELOG [Unreleased]: added /reconcile + /release-candidate under ### Added (so the eventual v4.0.0 captures them — /reconcile shipped without its entry, rectified here).
 - Ship: feature/release-candidate-skill → develop (gitflow finish). Push gated (ASK). Real v4.0.0 cut = separate later act (layer 2).
 ## 2026-06-30 (cont.) — make plugin fixed (npm) + deferred-items requalif (③ doc-commit, BDR-015 darwin)
 - 2 code vérifs (subagents, no-memory) + `make plugin` action. VÉRIF③: gitflow hook (`lib/gitflow.sh:199-225`, exempts `.claude/**` + merges + root) installed by init-project STEP 5f + onboard STEP 2.6 → branch guard covered everywhere EXCEPT repos outside `gitflow init` (doc-commit.sh has NO branch guard — `_unsafe_state` skips main/develop). ③ = confirmed REAL but NARROW hole, already graved [[BDR-040]]/TODO:292 → NOT re-graved.
 - ③ nuance (only new bit, logged here): a future doc-commit guard must REPLICATE the hook's `.claude/` whitelist (hook EXEMPTS 100%-`.claude/` commits on main/develop — memory follows the work), NOT blanket-block main/develop → 3rd copy of the whitelist predicate, not "4 lines". Low priority, stays deferred.
 - VÉRIF symlinks: 0 broken / 83 today → BDR-015 trigger cleared, darwin re-baseline UNBLOCKED (NOT run). [[BDR-043]].
 - `make plugin` Error 127 (npm absent, apt-`nodejs` host) → fixed via corepack (npm 11.18.0 → `~/.local/bin`, prefix `~/.local`), EXIT=0, Step 4 ✓, stray-dir residual cleanup ([[BDR-030]]/[[LRN-042]]) finally ran. [[BLK-013]].
 - BLK-013 + BDR-043 capitalized; ③ requalif dropped (already captured), whitelist nuance logged here. Surgical memory commit (blockers+decisions+journal only, NOT TODO — user's uncommitted planning note left untouched).
 ## 2026-06-30 (cont.) — close ritual (LRN-081 + TODO reconcile) + gate-suspense gap caught
 - Ran /close (capitalize --ritual). After a fresh capitalize → registries propose near-nothing (BLK-013/BDR-043 already this session); live work = TODO reconcile + 1 LRN.
 - GAP caught: the prior STEP-3 gate (LRN-081 + TODO check L26 + 2 adds) had stayed UNRESOLVED — conversation diverted to an out-of-band /reconcile + EVAL-013 (`437697e`, author user, NOT Claude) which never touched the gate items. Verified absent, then completed. Exactly the declared-vs-real drift /reconcile exists to catch.
 - LRN-081: Claude commit trailers only on Claude-COMPOSED content; staging user-authored text gets none (staging ≠ authorship). Born of `e591510` (clean) vs `5b03ac2` (trailers).
 - TODO: checked L26 "Cleanup machine courante" DONE (`make plugin` EXIT=0 this session ran Step 8.5; fs-verified both strays absent — closes the session's opening "cleanup ligne 26"); added (a) harden install-plugins.sh Step 1 npm-via-corepack ([[BLK-013]] fix-forward); added (b) darwin re-baseline of the 5 ex-broken skills ([[BDR-043]], promoted from its action-field).
 - LRN-081 capitalized; checked 1 done, added 2.
 ## 2026-06-30 (cont.) — BLOC1 darwin re-baseline → resolved-MOOT (measure-first)
 - Searched for results.tsv instead of assuming its state → GONE (wiped by 23/06 make-plugin reinstall; was a local May-2026 artifact, not shipped upstream). No darwin baseline survives at all → not even a re-baseline, a fresh-from-zero one.
 - BDR-043 cleared only motif (a) of BDR-015's TWO exclusion grounds (symlinks repaired ✅, 0 broken); motif (b) external-ownership INTACT — 5 resolve to skills-external/gstack/ (submodule), darwin edits SKILL.md → would dirty submodule ([[LRN-070]]). Re-baseline = unactionable score = phantom value. Twin of --help ([[LRN-080]]), distinct mechanism (residual motif vs absent value).
 - Decision A (won't-run): TODO (b) → resolved-MOOT (not done, not open). LRN-082 capitalized (multi-motif trigger lesson). The "montre la table avant de décider" gate paid off — looking found the table gone instead of assuming status=error.
 ## 2026-06-30 (cont.) — BLOC2 auto-skill-dispatch → WON'T-BUILD (discernment measured)
 - Cartography: routing = STACK L0(design-hook)→L1(superpowers "1%→MUST invoke", dominant)→L2(CLAUDE.md prose)→L3(frontmatter)→L4([[BDR-019]]). L1 over-determines invocation → "auto-call?" = already yes.
 - Reframe C (user): real question = DISCERNMENT not "does it route"; risk inverts under→OVER-routing (L1 mandate vs Workflow "ask if needed / pragmatic on trivial").
 - Subagent RED (6 reps, toy tasks) → 0/6 routed → RETIRED as non-discriminating (SUBAGENT-STOP + delegated framing = floor artifact, not signal); did NOT report as a number → [[LRN-083]].
 - Discernment-RED in REAL fresh sessions (user-run, 8 prompts / 3 classes): CLEAR→route ✓, AMBIGUOUS→ask (refuses to guess, investigates for a useful Q) ✓, TRIVIAL→abstain ✓. Over-routing risk does NOT materialize — model balances L1 vs Workflow rules.
 - Verdict: WON'T-BUILD ([[BDR-044]]) — 3rd measured moot of the session (--help, darwin re-baseline, auto-skill-dispatch). LRN-083 capitalized; [[LRN-080]] corroborated (3-in-a-row → measure-first sweep heuristic). TODO auto-skill-dispatch → won't-build. ALL actionables soldés.
 ## 2026-07-01
 - gitflow aiguillage-standalone (BDR-045): chore type + 4 standalone memory/doc skills branch off develop before writing; hook exemption kept. 64/64 green (e8807a7). Then repaired 5 direct-on-main `chore(memory)` → chore/reconcile-memory branches (LRN-084, LRN-034 corrob).
 - BLK-014 fixed: install.sh npm EEXIST on `~/.local/bin/claude` (native symlink, npm prefix `~/.local` from BLK-013) → skip-if-present guard + channel-aware update-all.sh (`claude update` for native). LRN-085. Commit 8dc4027, branch bugfix/install-claude-idempotent pending merge.
 - BDR-046: install.sh switched fresh-install from npm → official native installer (`curl claude.ai/install.sh | bash`); npm no longer a documented channel (verified quickstart). Aligns with install-plugins.sh. Commit 6be627e, same branch.
 - /reconcile show-only (claude repo, engine-verified): confronted TODO+registries vs git/fs. Real state = 1 actionable (install-plugins npm harden), 3 blocked-upstream (BLK-001 rtk / BLK-003 darwin / BLK-009 CC #21858, re-test on CC MAJ), 3 deferred-on-trigger, release-decision live (develop 20 ahead of v4.0.0). Engine false-flagged BLK-014 (last-status-wins caught Reference "open" vs Status resolved) — verified merged. "canal d'install" = already decided by BDR-046, NOT open; faunosteo/WARN-manuel = not in this repo.
 - (c) TODO drift fixed: 7 `--help` WON'T-BUILD subtasks `[ ]`→`[-]` (chore/reconcile-todo-drift, 9c02406) → naive open-count 10→3, survivors all genuine deferred-open. Registries left read-only during reconcile (staleness deferred to this capitalize).
 - (a) BLK-013 fix-forward BUILT: install-plugins.sh unconditional npm guard (corepack→distro→fatal), placed after `NODE_OK` short-circuit so node>=22-but-no-npm hosts don't skip it. shellcheck/`bash -n` clean, 1f2c1cc. Capitalize refreshed BLK-013 (NOT built→built), BLK-014 + BDR-046 (pending→merged) via append-only Update blocks. Both branches finished into develop.
 ## 2026-07-02
 - Fable 5 exhaustive audit (read-only, 5 subagents + real suites): 24 findings — 5 bugs (rtk DEAD silently since .bashrc wipe → [[LRN-087]]; session-start update-check on gone origin/master; run-reconcile T6c parasite path → [[LRN-077]] corrob; doctor 3 false sentinels incl. BDR-019 contradiction), token overhead measured 14.6k/session → [[LRN-088]].
 - 3 lots merged on explicit GO (suites green after each, reconcile 20/20 post-LOT1): bugfix/audit-bugs (rtk absolute-path heal + re-pin ×2, origin/main, T6c, doctor sentinels); feature/audit-hardening (.bak purge, banner ALWAYS_ON derived + graphify label, ok-gated installers, design-hook regex tightened, update-all bun+exclusions, deny 99→113 + rtk read-only allowlist + .env mirrors, cleanup batch, origin/HEAD→main); feature/audit-tokens (pr-review-toolkit OFF −2.2k tok, kept in audit.profile as reactivation channel; 10 descriptions compressed −540 tok).
 - #11 rtk auto-allow DROPPED — permission control back in settings.json (rtk registry was a parallel authority bypassing deny/ask). #10 rules/context7.md deleted (−493 tok; find-docs survives, stable — regen keyed on its absence); faulty examples → upstream issue draft (upstash/context7, gh unauthenticated). plugin-dev uninstalled + dropped from installer.
 - Incidents: magic API key printed into transcript from ~/.claude.json → rotated, [[BDR-026]] update (copies of secrets); gitflow_finish ignores its args (operates on CURRENT branch, lib/gitflow.sh:104) → LOT 3 merged first by mistake, final develop state identical (disjoint hunks) — UX trap noted, not fixed.
 - Residuals (flagged, not built): doctor "Cargo not found (RTK unavailable)" parenthesis now misleading; doctor symlink-check false-warns on dir-level symlinks; doctor token constants stale; find-docs faulty examples ctx7-owned.
 ## 2026-07-03
 - bugfix/gitflow-finish-args: `gitflow_finish` contract fix — args now optional safety ASSERTION (present + ≠ current branch → refuse rc2 "operates on current branch X, you asked Y — checkout Y first"); no-args unchanged (only real caller SKILL.md:36 + all tests pass none → zero regression). +7 T12 assertions. [[BLK-015]], [[LRN-089]]. Off-by-one caught at capitalize: next free BLK = 015 not 016 (gate proposal said 016) → gitflow.sh comment corrected pre-finish via soft-reset+redo of the 3 commits.
 - Same branch, 3 doctor false-warns fixed ([[LRN-047]] corrob — a doctor that cries false is ignored): cargo "(RTK unavailable)" → optional info (RTK prebuilt, detect_rtk); check_symlink passes children of dir-level symlinks (hooks/session-start.sh); gstack counts 34 per-skill symlinks not a mythical skills/gstack link (link.sh removes it); token budget vs 200k context window not bogus 11k "session budget" → killed false "92% CRITICAL" (measured ~11.4k [[LRN-088]]; 200k confirmed by user — 1M pin revoked at audit #7, calibrate on default not the exceptional session).
 - Suites green: gitflow 71/71 (+7), deterministic 13, doc-commit 32, doc-shape 19, reconcile 20, deploy-commit 13, release-candidate 5/5 tag-mode. doctor: 0 false-warn (1 legit survivor = gstack tracks branch=main advisory). shellcheck clean. T12 named to dodge collision with reconcile's own T6c (darwin path, audit #3).
 - 3 atomic commits (fix gitflow / fix doctor / docs changelog Unreleased) + memory. finish bugfix→develop on GO; user pushes develop.
 - ECC 2nd-look (Opus 4.8, 6 agents, repo unchanged since 01/07): all [[BDR-047]] facts corroborated w/ file:line, zero divergence. Scope gap = hooks/ (only wired subsystem) unaudited 01/07 → [[LRN-090]] wired > declarative.
 - Shipped config-protection hook (feature/config-protection-hook): PreToolUse blocks Edit/Write to quality-gate files (settings/gitflow/.githooks/doctor/hooks-self/lib-tests/lint). One-shot sentinel .claude/.config-edit-ok (non-empty reason, logged+consumed) — NOT env-var (launch-time = set-and-forget = garde mort). Own idiom, not ECC import. shellcheck clean, test 20/20.
 - Live dogfood: hook went active mid-session via symlinked settings (link.sh); v1 (no self-guard) let its OWN edit through → v2 added hooks/*.sh + lib/tests/* self-guard, then blocked the test-file edit; recovered via sentinel. User's self-guard requirement vindicated.
 - Next: #2 design-toolchain trigger fix (residual false-fires post-ed2408e, 5× this session).
 - #2 done (bugfix/design-toolchain-trigger): trigger tightened — dropped bare design|component|composant|theme|thème|transition|frontend|front-end|palette; dashboard→\bdashboard\b (kills ecc_dashboard.py filename match, keeps "admin dashboard"); kept animation; added "front-?end design" bigram + fire-log counter (time+token+excerpt, ~/.claude/logs/design-toolchain-fires.log) so future "re-firing?" is measured. Test 18/18, shellcheck clean, live dogfood green. [[LRN-091]] corrob [[LRN-047]].
 - Double dogfood of #1 guard: config-protection blocked + sentinel-bypassed my own edits to the now-guarded design hook + its test — first real use of the guard, friction validated in passing (one-shot sentinel .claude/.config-edit-ok, non-empty reason, logged+consumed). ECC second-regard closed: #1 config-protection + #2 trigger fix, both merged to develop, nothing pushed.
 - Chantier verify-loops/semgrep/contract: Phase 1 read-only (6 subagents mapped 6 orchestrators + cso + agents + install patterns; caught subagent error — cso IS gstack symlink, ls-verified) → archi GATED-GO (5 verdicts: local grafts, dev inline light flows, hotfix unchanged, pinned rulesets, pinned version; +2 specs: contract on DISK, mute verifier ≠ PASS). LOT 1 shipped on feature/semgrep-install (ccfecc9+b8d3ccc): install-plugins STEP 7.5 + update-all 6.2 + lock pin 1.168.0, dogfooded real (4 paths + anonymous ruleset fetch + detection). [[BDR-048]] [[LRN-092]]. Next: lot 2 specs (contract-interview lib + verifier agent).
 - Chantier verify-loops LOT 2 (feature/contract-verifier `6aed5ee`): lib/contract-interview.md (verbatim contract on DISK, micro-gate scope enrichment, aborted never dirty) + agents/verifier.md (fresh+blind, PROOF-or-fail, mute ≠ PASS) + 31 structure locks green, shellcheck clean. Behavioral: planted-gap → ECARTS(2) exact; conform under injected fake history → CONFORME (blindness held). Sentinel consumed 4× on guarded lib/tests/. [[BDR-049]] [[LRN-093]]. Merge note: lot 1+2 both append registries at same anchors → trivial stack-conflict expected. Next: lot 3 security-auditor spec.
 - Chantier verify-loops LOT 3 (feature/security-auditor `2b297bd`): agents/security-auditor.md (SAST gate, pinned p/security-audit+p/secrets+p/owasp-top-ten, secrets→CRITICAL, block ERROR only, DEGRADED-still-checks, anti-gaming nosemgrep, PROOF-or-fail) + grafts onboard L3a (complement to cso, both gstack branches) + audit-delta security axis. 28 structure locks + 4 behavioral dogfoods green: vuln→BLOCK(9), nosemgrep→BLOCK(1), DEGRADED→BLOCK(7). owasp REQUIRED (measured: baseline misses SQLi+path-traversal on Flask). [[LRN-094]] + [[BDR-048]] addendum (owasp/severity/FP) applied at integration on feature/verify-loops (index drift LRN-090/091 backfilled same pass). Next: lot 4 loops-light (feat/bugfix/hotfix wiring).
 - Integration: feature/verify-loops = develop + merge lots 1-3 (local, develop/main intact, nothing pushed) so lots 4-5 wiring is dogfoodable against present agents. Memory stack-conflicts resolved (BDR-048/049, LRN-092/093/094 stacked ID-order; BDR-048 addendum applied; LRN-090/091 index rows backfilled).
 - Chantier verify-loops LOT 4 (feature/verify-loops `0f0162d`): lib/verify-secure-loop.md shared include + wired feater (0.7 contract, 3 verify+secure), bugfixer (3.5 contract from diagnosis, 5 gates), hotfixer (1.7 silent contract, 3 security gate FAILURE=REVERT not loop, +Agent tool). 27 structure locks + full pipeline dogfood: feat fixture w/ SQLi → GATE1 CONFORME → GATE2 BLOCK(1) (checklist caught what semgrep taint missed) → fix → re-verify CONFORME (order invariant) → re-scan PASS. [[BDR-050]] [[LRN-095]]. Weighting held: feat/bugfix nominal 2 dispatches, hotfix 1 + revert-on-fail. INCIDENT: re-committed [[LRN-093]] (2nd recurrence, 4 locks w/ \n) — caught at first run; user flagged advisory-insufficient → build deterministic backstop in lot 5. Next: lot 5 heavy flows (ship-feature enrich-at-gate, init-project +security, onboard no-loop) + escalation dogfood (max-3 STOP) + LRN-093 meta-test guard.
 - Chantier verify-loops LOT 5 (feature/verify-loops `1c69de2`, FINAL): ship-feature (0e contract, enrich-at-gate STEP 3 [gated], 5 verify+secure vs ENRICHED) + init-project (contract from BRIEF, enrich GATE#1, 9 verify+secure — adds the security gate it lacked) + onboard (explicit NO-loop, audit≠dev, documented vs symmetry) + lib/tests/no-vacuous-locks.test.sh (LRN-093 deterministic backstop w/ inline flip-test) + loops-heavy 18 locks. Dogfood BOTH vigilance points real: (1) enrich — fresh verifier reads+judges a [gated] design criterion (ECARTS names it); (2) escalation — 3 consecutive ECARTS → orchestrator STOP at max-3 + CONTRACT-vs-REALIZED table, no 4th loop, no commit (first real exercise of the infinite-loop guard). [[BDR-051]] [[LRN-096]]. INCIDENT closed: the backstop's OWN flip-test RED'd (regex missed line-start tf) → fixed → [[LRN-096]] (a guard is code, prove it can fail). Chantier complete: 5 lots on feature/verify-loops, develop+main intact, nothing pushed.
 ## 2026-07-04
 - Merged verify-loops chantier + default-model chore into develop (user pushed). Cut release/4.1.0 (prep + RC gate 8/8 green) — awaiting GO.
 - rules/ dir built + symlinked via link.sh (feature/rules-dir `06391a6`): real feature verified (paths-scoped lazy rules); context7.md machine-owned → gitignored (find-docs pattern). "contexts dir" request REFUSED — feature doesn't exist (official docs via claude-code-guide); intent already covered by agents/skills. [[LRN-097]].
 ## 2026-07-05
 - Built /tour skill (grouped sweep clean+security+reconcile+doc, auto, 1..N projects, convergence loop bounded 3×) via writing-skills TDD + skill-creator guidance: RED 6 gaps → GREEN 6/6 closed disk-verified → REFACTOR 2 holes (scratch self-block, BREAKING tag). [[BDR-052]] [[LRN-099]] [[LRN-100]] [[EVAL-014]]. Merged feature/tour-skill → develop + release/1.0.0 on user GO. settings.json /model side-effect reverted (Opus 4.8 1M default restored, attribution backstop kept).
 - /deploy first real run (bchanot-cv): bootstrap→mark full cycle, live-proven (full security-header stack live — tour→prod closed, tag deploy/2026-07-05). Skill patched post-run on user UX feedback: session-style NEXT.sh (one command per line) + hand-back prints the checklist inline ([[EVAL-016]]); template + generated runbook restyled. impeccable chain + Node 24 baseline shipped develop+RC, pushed. settings.json: +inputNeededNotifEnabled committed (layout unchanged).
 - /deploy pass 2 (user feedback live): checklist DISPLAY-ONLY — NEXT.sh file eliminated (throwaway artifact, PENDING+runbook regenerate anywhere), hand-back ends the turn with the checklist as final text (a print above AskUserQuestion never reached the user, [[LRN-102]]). Skill+template+CHANGELOG patched; legacy NEXT.sh removed from bchanot-cv; deploy run 2 (residuals b24c58b) re-handed-back inline.
 ## 2026-07-06
 - job1 fixes merged develop (`c6d5e03`): CLAUDE.md gitflow density pass, F14 hook pointer-only, line-count guard, [[LRN-103]].
 - job2 config-smell audit shipped read-only: `.audit/job2-report.md` — surface skills/agents/hooks/plugins/settings(.local), 17 findings (3 RISK perms, 6 DRIFT, 2 BLOAT, 3 OVERLAP, 2 DEAD, 1 struct), 26 diffs base c6d5e03, 0 decision-conflicts, all fresh-context verified [[EVAL-017]]. Live catch: design hook fired on audit's own task-notifications (14/20 recent fires).
 - Brief premise corrected: Edit/Bash(hooks/*.sh) permission rule NEVER existed — was config-protection case arm (:37) + job1 sentinel bypasses. Phase-0 UNREFERENCED metrics 100% broken (grep -q kills -l).
 - User GO full execution incl. 3 RISK: cp/mv→ask, find -exec deny mirror, settings.local prune (python3 -, rtk git *). F9 fable default committed (user re-chose via /model), F16 gitflow-migrate.sh removed (git-recoverable), F8/find-docs skip (generator-owned). Executor = Sonnet subagent on chore/job2-fixes, NO finish.
 - job2 EXECUTED: 15 commits chore/job2-fixes, all diffs first-try, `make test` wired + first-ever full run ALL GREEN (gitflow 71/0). Measured −309 tok/session (agents 4840→3609 chars); design hook no longer fires on task-notifications. Executor STOP exercised for real: F4 gate red → root-caused to job1 oracle regression (3f639b3), fixed as [[LRN-104]]; 2nd YAML error/file unmasked (onboard/plugin-check) → closed 6a3b197. Skips: F8 (npx skills has no re-pin verb), find-docs (ctx7). Merged develop 964c5dd on user GO.
 - job2 tail closed [[BDR-053]]: context7.md rule killed (file rm + installer purge, find-docs = single ctx7 surface, ~−490 tok/session more) + darwin lock entry dropped (F8). chore/ctx7-single-surface → develop, pushed. job1+job2 fully closed; total measured ≈ −800 tok/session.
 - job3 docs-drift audit shipped read-only: `.audit/job3-report.md` — README/docs/templates/skill-bodies scope, 46 findings, 19 diffs base defc26c, 1 ⚠ DECISION-CONFLICT (BDR-038 vs shipped /deploy), all fresh-context verified [[EVAL-018]]. Explorer subagent ran `graphify .` mid-audit against read-only intent, self-corrected mid-run only after main-session correction — [[LRN-105]].
 - User GO full execution, decisions injected: BDR-054 supersedes BDR-038 (NEXT.sh/hand-back removed) + banners on the 2 historical deploy docs; B1 reconcile-fixture hermeticization; A1/A3 trims; C4/C5 depth-matrix rewrite; B2 profile real-toggle doc. D2-D5 (graphify, generator-owned) + B6 (skills-perso allowlist) SKIPPED by decision. Executor = this session on chore/job3-fixes, NO finish.
 - job3 EXECUTED: 20 commits chore/job3-fixes, all diffs first-try, `make test` all green throughout, zero regression. **B1 BLOCKED**: `lib/tests/` guarded by config-protection.sh same as `hooks/`; user's sentinel pre-auth scoped only to hooks [SENTINEL-REQUIRED], auto-mode classifier correctly refused the out-of-scope bypass — needs explicit follow-up authorization. Final re-sweep: 3 fresh verifiers, 24 modified files, ZERO residual finding; `run-reconcile.sh` unchanged 18/2 (B1 untouched, as expected). 2 incidental out-of-scope drifts surfaced (client-handover-writer.md:885 stale "4-chapter" self-contradiction, BDR-053 index-row gap) — flagged, not fixed.
 - B1 UNBLOCKED same session: user explicitly authorized the `lib/tests/` sentinel. Froze `.claude/memory/blockers.md` (post-BLK-009-closure state) into `lib/tests/fixtures/blockers-snapshot.md`, pointed T2 at it instead of the live registry, updated T2b/T2c expectations (BLK-009 resolved, open={001,003}). Suite back to 20/20 GREEN, shellcheck clean — `skills/reconcile/SKILL.md:53`'s "20/20" claim is true again. `make test` reconfirmed all green. job3 now fully closed: 21 commits total, 0 items pending.
 ## 2026-07-06 (cont. 2)
 - job4 test-gap audit shipped read-only: `.audit/job4-report.md` — hooks/gitflow-guardrails/session-libs/reconcile-fixtures/graphify scope, 22 findings, 11 named specs + NOT-SAFE items, all fresh-context verified [[EVAL-019]]. run-*.sh 5 suites confirmed excluded from `make test` (J4-01, CRITICAL).
 - User GO full execution, decisions injected: J4-01 first commit (gate must lean on the fixed aggregator); J4-04+toggle-external fix authorized (red→fix→green, 2 commits each, diff shown before commit); deploy-commit new exit codes ≥6; sentinel pre-auth for lib/tests/ + steps 6-9 fixes; SPEC-06 held at explicit confirm despite AUTHORIZED line (ambiguity in user's own instructions, resolved by asking). Executor = this session on chore/job4-tests, NO finish.
 - job4 EXECUTED: 20 commits chore/job4-tests, all mutations red-green verified (scratch/lean copies, never the working tree), `make test` green throughout (71→90 gitflow + all 5 excluded suites now included). Incident: `/tmp` (tmpfs) exhausted from repeated full-repo `cp -r` (incl. `.git`+gstack submodule) → Bash universally broken until user cleared it; switched to minimal-file scratch copies for the rest. config-protection guards by path SUFFIX regardless of dir → scratch mutations of guarded-pattern files done via Bash/sed (shell ops, hook's own doc says it never covers those) not Edit/Write. J4-22 caller census found deploy/SKILL.md parses deploy-commit exit codes — flagged, user GO'd doc-sync too. [[LRN-106]] (B1-fix-≠-pattern-close, caught by job4 finding the exact same live-registry-read fragility job3 left in T3/T5 of the same file). Branch unmerged, human gate. Backlog: J4-13/14(partial)/15/16/17/18 + hermetic suites for profile/toggle-external/design-tool-gate (unlocked by SEAMS, not built).
 ## 2026-07-07
 - job6 dep-upgrade audit shipped read-only: `.audit/job6-report.md` — rtk/gsd-pi/gstack/ctx7/graphifyy/semgrep/impeccable/emil/darwin/magic MCP census, BATCH-1/2/3 verdicts, 22 CONFIRMED/2 CORRECTED/0 REFUTED. Incident: explorer copied plaintext MAGIC_API_KEY into scratch, redacted post-check — [[LRN-107]].
 - User GO full execution, prerequisites confirmed upfront (gstack #2047 human review → pull complet + reapply local fix; MAGIC_API_KEY rotated). Sequenced by risk, one upgrade = one commit = one gate, chore/job6-deps-upgrade, no finish.
 - job6 EXECUTED: ctx7 0.5.3→0.5.4 (zero repo diff), graphifyy binary 0.9.6→0.9.8 (hook-guard rewrite of config-protected `.claude/settings.json` traced to source, diff shown, user declined adoption), gsd-pi 2.64.0→3.0.0 (`b4896c9` — 3.0.0 confirmed format-incompatible with status-reporter's ROADMAP.md parser via a real scratch-dir test milestone; ADR-013 cutover, DB-authoritative, no ROADMAP.md at all; user chose patch-now, parser rewired to `gsd headless query` JSON, smoke-tested both cases), gstack submodule 070722a→11de390 (`2813e55` — full pull per verdict, #1911 fail-open guards + PII/telemetry/data-loss fixes; local playwright patch (BDR-029) backed up then discarded then correctly reapplied via the documented bump function, landed one minor ahead since upstream moved meanwhile; /careful + /freeze smoke-tested blocking live), supply-chain docs (`00c97bc` — pipx-only graphifyy rule, semgrep p/* runtime-pack caveat; MCP magic version pin declined by user, `${VAR}` env-expansion confirmed unsupported at `~/.claude.json` user scope after 2 rounds of sourced doc lookup — BDR-026 pattern doesn't transfer there, regenerated live config instead via toggle-external.sh to pick up the rotated key). `make test` 90/90 green + `doctor.sh` 0 errors throughout. Incident: mid-session Bash tool universally unresponsive again post-`/tmp` exhaustion (same class as job4's), user cleared it, resumed from confirmed git state. [[EVAL-020]], [[BDR-056]] (deps policy reversal: latest gated by integration, not KEEP-PINNED default). Branch unmerged, human gate — orphan `~/skills-lock.json` (F-S1) also deleted, non-repo file, no commit.
 - job7 secrets backstops shipped, `chore/job7-secrets`, 4 commits (A/B/C/D), `make test` 96/96 green throughout. **A**: MAGIC_API_KEY's sole writer confirmed (`lib/toggle-external.sh:191`, no other). Doc lookup found `${VAR}` expansion IS supported at `~/.claude.json` user scope — contradicts job6's own same-day finding, not reconciled (see [[BDR-057]] caveat). Rewrote to `--env 'API_KEY=${MAGIC_API_KEY}'` + scoped `~/.bashrc` `claude()` wrapper (subshell+exec, verified the var never reaches the ambient shell) over a global export (user's call); `~/.claude.json` rewritten via surgical jq (never Read directly); README procedure doc added; 2 of 5 rotating `.claude.json.backup.*` still had the plaintext mid-fix, scrubbed. **B**: `hooks/rtk-rewrite.sh` now redacts bare `printenv`/`env` dumps (the GITEA leak's actual vector). Mid-implementation discovery: rtk classifies ANY `env`-containing command as exit-2 "deny" with no settings.json rule backing it (command still runs) — case handling fixed so redaction applies regardless. **C**: `.gitleaks.toml` (3 job7 false-positive classes + `.env` self-scan exclusion, all verified empirically against the real files, not assumed); pre-commit backstop wired into `lib/gitflow.sh` after the root/merge guard, ANY branch; `make scan-secrets` (repo + `~/.claude`, `--redact` confirmed to scrub the JSON report itself, not just logs). gitleaks 8.30.1: `protect` no longer in `--help` — used documented `git --staged`. **D** (GO-gated): rm'd transcript `960bd2cf` + `paste-cache/7d48f52c7499c1a7.txt` (both GO'd); `cleanupPeriodDays` 30→7 (1st write attempt correctly blocked by the auto-mode classifier for narrating the diff instead of actually pausing — re-asked properly). `make scan-secrets` surfaced 3 discoveries outside the original triage: `ide/20429.lock` (live, not touched), transcript `f1c9c474-...jsonl` (8 hits, left open — no option chosen). Residuals: MAGIC_API_KEY rotation still pending user action; magic MCP end-to-end reconnect needs a terminal+Claude Code restart; live `claude mcp add` test correctly blocked (self-modification, unrequested). [[BDR-057]], [[LRN-108]].
 - job8 third-party security audit shipped read-only: `.audit/job8-report.md` — magic MCP/plugins/gstack/external skills/trust chain, 9 explorers + verifier batches, 11 CONFIRMED/5 CORRECTED/0 REFUTED. Surfaces C (ui-ux-pro-max) + D (other plugins) finished inline, single-observer, no verifier pass — Fable-5 spend limit hit mid-run.
 - User GO on all 4 items: A allowlist stays empty, ask-gate explicit; B covered by A (no STOP); C reinstall pinned (not remove/keep-broken); D no action. Executor = this session, `chore/job8-hardening`, no finish.
 - job8 EXECUTED: 3 commits. **A**: `settings.json` `permissions.ask` += 4 `mcp__magic__*` tools, isolated from 2 unrelated pre-existing edits (model/skipWorkflowUsageWarning) already sitting uncommitted before this session started — those restored uncommitted after, not part of this branch's history [[BDR-059]]. **B**: confirmed `component_builder` in scope of A's gate, no STOP needed; documented the callback-injection risk in README's MCP section + [[LRN-110]] — third-party package code, not patched. **C**: confirmed referenced files (`references/`, `scripts/`, `templates/`) 100% absent from `~/.agents/skills/darwin-skill/` (only `SKILL.md` present) — root-caused to the `skills` CLI's `skillPath` install field fetching a single file, not the repo tree [[LRN-109]]. Upstream HEAD matched the already-recorded lockfile hash exactly (zero drift). Reinstalled full tree at that pinned SHA, `.git` kept but detached (2nd real SHA-pin after gstack) [[BDR-058]]. Backup of old single-file dir kept. Git-commit whole-`.claude/skills`-tree scope NOT restricted (3rd-party pinned code, patching breaks the pin) — documented as accepted risk instead. 3 Bash permission denials mid-C (rsync x2, cp+rm) before a plain `cp` succeeded — `rm -r*`/`rm -rf*` are hard-denied even for scratch/temp paths, no prompt possible; switched approach rather than retrying identically. **D**: confirmed untouched. `make test` green throughout (incl. a live `path_present(darwin-skill)` fs check). Smoke gate: real `mcp__magic__logo_search` call in-session, user confirmed the ask prompt fired and was manually approved — no auto-exec. [[LRN-111]]. Branch unmerged, human gate. **Not re-verified this cycle** (job8 report's own caveat, carried forward): surfaces C/D (ui-ux-pro-max, other plugins) were single-observer CLEAN findings with no adversarial pass — re-audit next cycle if darwin/magic scope comes up again.
 ## 2026-07-08
 - job9 sub-agent architecture corrections shipped, `chore/job9-agents`, 10 code commits, `make test` green throughout. Premise correction confirmed: CC **v2.1.203** live, nesting supported (cap 5, `Agent`-in-tools required) — [[LRN-112]], contradicts the operating premise of the whole job1-9 series.
 - **Part 1** (4 commits, `0ede52c`..`5ab6c21`): commit-changer drop unused `Agent`; verifier + security-auditor + plugin-advisor pinned `model: sonnet`. Gate = real dispatch smoke on sonnet: verifier `CONFORME`, security-auditor `BLOCK(2)` (checklist caught planted hardcoded-secret + SQLi that semgrep 1.168.0 missed), plugin-advisor `ACTION REQUIRED` — verdict grammar intact, mode honored, no revert.
 - **Part 2** (`a5a7b54`/`6df42e4`/`c498b93`/`70fb3b4` + hardening `212f9aa`): seo/geo analyzers re-architected to fix-bundle→L1 (validator-analyzer contract), `Agent` dropped from both `tools:`; `/seo` new STEP 1.5 applies at L1 (serial by ownership, dissolves the parallel-edit race), `/geo` → dispatch+apply orchestrator, `/harden` already end-to-end path-b (untouched), `/onboard` audit-only (untouched). [[BDR-060]] version floor + [[BDR-061]] path-b doctrine. 4 real smokes green: analyzer emits bundle + edits nothing (md5 unchanged, no files created); AUTO fix LANDS on disk via L1 hotfixer with no confirmation (the exact previously-broken path — *report but zero fix* → resolved); GATED withheld pre-accord then applied post-accord (new tier, first test); /onboard writes only the report, zero source files.
 - **Part 3** (`87d63bf`/`af9656f`): H2 "Load and follow" idiom → **INLINE-LOAD** verb at code-cleaner + scaffolder (main-loop-BECOMES-agent, `Agent` not involved), drop unused `Agent` from code-cleaner; H1 code-cleaner→refactorer handoff now a named artifact `.claude/audits/CODE-CLEAN-SCOPE.md`. Tight scope per user (2 cited sites, no 40-site rewrite).
 - Branch unmerged, human gate. **Fixed** (`5a3de92`, isolated): stripped `Co-Authored-By: Claude` from `commit-changer.md` message template — it contradicted [[no-commit-attribution]] since the template's creation (the settings.json backstop caught real commits, but the template itself would keep re-seeding the trailer). Only banned trailer in the file (no Claude-Session/--trailer). FOLLOW-UP next cycle: cross with J4-16 (lib-layer lock) to verify no other agent template carries the same trailer.
 - Adversarial review of the whole 9-job series (release/1.0.0..develop) → `.audit/review-release-1.0.0.md`: 1 BLOQUANT + 5 à corriger + 5 mineurs, 10 verified false-positives. 2 sub-agent verdicts overturned (job7 gitleaks hook inert [[LRN-114]], contract tool-grant FP [[LRN-115]]). Jobs 4/5/6/8 CLEAN, validator-analyzer contract SOUND. J4-16 follow-up above CLOSED: trailer twins found in bugfixer/feater/hotfixer.
 - Remediation `chore/review-remediation` (unmerged, human gate): A1 trailer purge (3 templates) + whole-surface sweep; A2 gitleaks hook re-installed (`install-hook`) + negative-secret gate proven; A4 strict-YAML quote (seo/security-auditor); A5 geo own-policy (user-approved, PERMISSIVE default kept, false CLAUDE.md attribution dropped); A8 path-b PROVEN — /seo+/geo AUTO items land on disk via L1 (no silent no-op); fil-rouge `lib/tests/run-review-guards.sh` (5 guards, teeth-verified); A3 backfill LRN-098/101 + EVAL-015 + BLK-016 + PORTED rtk fix e58037c (was live-broken on develop, ~460K tokens/30d); A6 guard 280→320 + [[BDR-062]] (supersede BDR-031's 275 target). make test GREEN throughout.
 - Capitalized: [[LRN-113]] partial-fix+guard (structural), [[LRN-114]] hook-drift, [[LRN-115]] analyzer report-grants (FP1), [[LRN-116]] release fix missing from develop, [[BDR-062]] density realign, [[EVAL-021]] the review, [[EVAL-022]] M5 pins trace. Noted un-back-merged release chores beyond A3: e65796f (SC1091 lint silence) — left for a future reconcile.
 - Full back-merge release/1.0.0→develop (`chore/backmerge-release-full`, unmerged): the RC fork had left ~6 functional fixes orphaned on develop, silently. PORTED via cherry-pick, make test green each: `095d881` drop find-skills, `a1093ca` make-update TTY-guard (proven: EOF-die exit1 → guarded exit0), `4c5e862` rtk update-path version-guard (complements the `e58037c` install bridge already ported), `c76479f` design-motion sync, `e65796f` SC1091 lint. B soak journal (find-skills day1 / TTY #3 / rtk-update #4) folded here, not cherry-picked — divergent journal tails conflict (STOP-on-conflict honored, extract-consolidate fallback). C all covered/skip: `93e43c0` attribution + `ae8ad86` model already on develop; `188a9a7` docs → /doc backlog (README missing semgrep/scan-secrets/verify+secure/ctx7). Registry (LRN-098/101, EVAL-015, BLK-016) already backfilled in the review run. Gate: 23/23 release-only commits classified, 0 orphan functional, 0 missing registry; make test GREEN, review-guards 5/0. version.txt stays 4.0.0 (fork intentional, D — `eb93050`).
 - [[LRN-117]]: the fork silently orphaned functional CODE on develop (not just memory); the review back-merge caught ~half. Detecting it needs a code-level drift check (advisory, backlogged) — registry-sequence gaps alone miss it.
 ## 2026-07-10
 - GSC+CrUX data layer for `/seo` FULL shipped end-to-end (subagent-driven, superpowers): design→plan→8 tasks→final review→merge `bb1fbb2` on develop. Engine `lib/seo-data/` (label-keyed OAuth token store 0600/0700, CrUX field + GSC Search-Analytics/URL-Inspection, fail-open `fetch.sh`, `make seo-connect` consent), wired into `/seo` FULL (STEP 0 account select, CrUX-primary CWV, "Performance GSC" quick-wins). 49/49 engine tests + full `make test` green throughout. Final opus whole-branch review: security PASS, 0 Critical/Important, 5 Minors all deferred to a later chore sweep.
 - Decided [[BDR-063]] OAuth installed-app + explicit `(account,property)` args (no global state) → multi-account no-conflict. Learned [[LRN-119]] fail-open engine contract (always-JSON, lazy imports, degrade-not-crash), [[LRN-120]] final-review base = merge-base not ledger BASE (caught a misleading 881-vs-2163-ins diff).
 - Docs synced (`/doc`, `4a15c73` on `chore/doc-sync-gsc-crux`): README (seo-connect, make-test glob, /seo row) + USAGE (/seo FULL real-data) + CHANGELOG Added entry. Pending: merge `chore/doc-sync-gsc-crux`→develop (human GO), then delete transient spec+plan `docs/superpowers/…gsc-crux…`.
 - Post-ship housekeeping merged to develop: `chore/doc-sync-gsc-crux` (`8a1fac0`, docs+memory+transient-cleanup), then `bugfix/seo-connect-env-source` (`61a98d3`) — `make seo-connect` never sourced `~/.claude/.env` so OAuth creds never reached connect.py; found by real `make seo-connect` run (403 discover_properties after consent = Search Console API not enabled + the env bug). Live OAuth validated end-to-end by user (consent OK, app published to Production for non-expiring refresh token).
 - `/feat` feature/seo-account-mgmt (unmerged, human GO pending): account-management verbs — tokenstore remove/clear, fetch.sh forget, connect.sh wrapper (sources env, runs from any project), `/seo connect|accounts|forget` routing, Makefile delegates to wrapper. Commits `8bf7459` (feat) + `887341d` (doc USAGE). Security loop hit its cap: 3 GATE-2 BLOCKs on the label guard (injection → parser differential → per-line-grep newline), closed categorically by a whole-string POSIX `case` guard [[LRN-121]]; final fresh scan PASS (~50 vectors, 0 bypass). 85/85 engine + `make test` green throughout. forget = local delete, NOT Google revocation (surfaces myaccount.google.com/permissions).
 ## 2026-07-14
 - `/ship-feature` feature/claude-global-md-rename (unmerged, human GO pending): global memory → CLAUDE.global.md + project-scope CLAUDE.md, 8 commits (a4ee7e1 docs → e9a38a0 guards). Full pipeline: analyzer + contract (17 criteria), brainstorm/spec/plan gates, SDD 5 tasks (all task reviews Approved), verifier CONFORME 17/17 (after user-arbitrated criterion-9 consumer-wording + FILE-SCOPE [gated] enrichment), security PASS (semgrep 43 rules, 0), final review "Yes" after 2 Important fixes (guard-test drift → 7/7; doctor exact-target check). Decided [[BDR-064]]; learned [[LRN-122]] (2-commit rename split), [[LRN-123]] (exact symlink target). `make test` green throughout. settings.json plugin toggles = session-scoped, NOT committed — restore (gstack/ui-ux-pro-max/frontend-design/emil-design-eng/darwin-skill/magic ON) after merge.
 - Merges to develop: feature/claude-global-md-rename (2d54df5), chore/untrack-audit-reports (d557ee9), chore/post-merge-cleanup. /cso triage: 75 gitleaks findings → 0 real (60 git SHAs vs sourcegraph rule; gitflow-test AWS fixture; expired GitHub image JWT; presigned-URL key ids; doc placeholders; job7-purged artifacts). .gitleaks.toml → [[allowlists]] format + 8 targeted entries; `make scan-secrets` green 0+0. Makefile "safe to commit" hint root-caused → [[LRN-124]]. Transient spec+plan deleted per [[BDR-065]] (user decree, gsc-crux precedent). Mid-merge discovery: user commit 5842119 (gitignore `.audit/` + model pin fable-5) — explains the .audit-in-diff question. cso report: .gstack/security-reports/2026-07-14-secrets-triage.json.
 ## 2026-07-15
 - model routing shipped on feature/model-routing: BDR-066 (reflection inline big / executors sonnet / blocking gate), /feat re-arch, census guard. client-handover conversion deferred to plan 2.
 - model routing WAVE 2 (same branch, user directive): doc/status dispatch their agent (sonnet/haiku pins effective); /hotfix split like /feat (joins gated group 12→13, hotfixer dual-use executor); /commit-change → sonnet commit-changer (propose/apply, gates relocated); /release-candidate → sonnet release-executor (human gates + version decision kept in dispatcher). Consumer-staleness swept (feat Rule 1 + commit-split). census 36/0, make test green. Branch still unmerged.
 - model routing WAVE 3 (same branch): /bugfix + /code-clean split like /feat — reflection inline, sonnet executors (bugfixer, code-cleaner). code-clean refactor now runs on sonnet (inline-load pin was inert). consumers rerouted (hotfix deeper-bug→/bugfix skill; onboard/tour read-only audit→big-model agent). Explore kept built-in (inherits big). census 42/0, loops-light 35/0. Branch still unmerged.
 - model routing waves 1-3 MERGED into develop (e5c7c51); LRN-125 added. WAVE 4 started on feature/client-handover-dispatch (off develop): client-handover doc-gen → sonnet. REDACTION-ONLY (user flipped from whole-writer — nested audits must run big either way). client-handover-writer trimmed to ship pipeline (STEP 1-8 preserved byte-for-byte) + delegates writing to NEW sonnet handover-doc-writer (gate-free, STEP 9-16). client-handover joins gated group. census 46/0. NOTE: a Task-20 implementer ran `git checkout -- settings.json`, discarding user /model=opus working-tree state (LRN-098) — flagged to user (re-run /model). Lesson worth an LRN: constrain SDD implementers from git ops on files outside their task.
 - 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.
@@ -99,6 +99,40 @@ rules:
 | LRN-077 | 2026-06-30 | test fixtures must carry NEUTRAL names — a name that telegraphs the answer lets the subject pass by reading the name, not doing the work | designing any test fixture/path; same symptom as [[LRN-074]] (passes for WRONG reason), distinct cause (leaky fixture vs assumed command) |
 | LRN-078 | 2026-06-30 | semver number DERIVES from the change nature, not "justify a target"; solo-repo "breaking" = requires a migration of own usage; a removal nothing invokes = Removed not breaking | choosing a release version; classifying MAJOR/MINOR/PATCH; deciding if a removal is breaking |
 | LRN-079 | 2026-06-30 | orchestrator-skill TDD = replay the prescribed flow on a throwaway repo (gitflow-test style): RED runs the flow minus the new step → the outcome assertion reds on the gap | testing a skill that orchestrates an existing mechanic + one new step |
 | LRN-080 | 2026-06-30 | before adding an instruction "to make the model do X", measure if it ALREADY does X — universal conventions (--help…) it often does; the behavioral RED can KILL the chantier (phantom value) | proposing any global instruction to elicit a behavior; CLAUDE.md additions |
 | LRN-081 | 2026-06-30 | Claude commit trailers (Co-Authored-By + Claude-Session) only on Claude-COMPOSED content; a commit merely STAGING user-authored text gets none — staging ≠ authorship | committing on the user's behalf; memory-commit.sh appends trailers by default |
 | LRN-082 | 2026-06-30 | Trigger-cleared on a multi-motif exclusion lifts only the named motif — re-check the others before acting | any "exclusion lifted / precondition cleared" — verify ALL grounds, not just the named one |
 | LRN-083 | 2026-06-30 | subagents are an INVALID instrument for measuring main-loop spontaneous routing — SUBAGENT-STOP + delegated framing pin them to the no-route floor | any RED of whether the MAIN loop self-invokes; use fresh main-loop sessions, observe via the human |
 | LRN-084 | 2026-07-01 | protection hook enforces PROD not the full branch-flow; exemption masked the rule-vs-guard divergence | a guard exempts a class / checks one predicate — verify it encodes full intent |
 | LRN-085 | 2026-07-01 | Idempotent CLI install/update: `command -v` skip-if-present guard + detect channel (`npm ls -g` vs native symlink) before choosing updater; never `npm --force` over a bin npm doesn't own | any installer/updater for a CLI with >1 install channel |
 | LRN-086 | 2026-07-02 | External-tool-generated skill: prove provenance by mtime (not repo grep), gitignore + regen via install-step; guard regen on ABSENCE when the tool co-writes a user-editable config | any untracked skill/dir a tool (ctx7, etc.) drops into the repo |
 | LRN-087 | 2026-07-02 | presence-flag ≠ capability — rtk silently dead after .bashrc wipe; emitted commands need ABSOLUTE bin paths (they run in another shell); integrity pin = live machinery, re-pin on hook edit | any PATH-dependent capability + hand-managed shell profile; hooks emitting commands for another shell |
 | LRN-088 | 2026-07-02 | token-cutting intuition inverts under measurement — verbosity beats cardinality (gstack 34 skills ≈ 592 tok vs pr-review 6 agents ≈ 2,183) | any "disable X to save tokens" — measure per-item bytes first; profiles toggle skills, not plugin payloads |
 | LRN-089 | 2026-07-03 | pass-through wrapper (CLI `"$@"` → fn deriving target from ambient state: HEAD/cwd/env) silently ignores its args = silent contract violation; guard = args are an ASSERTION, refuse when they disagree with state | any dispatcher forwarding args to a callee that reads ambient state instead of the args |
 | LRN-090 | 2026-06-30 | external-repo audit: open WIRED subsystems (hooks/runners) before declarative (docs/rules); described capability ≠ wired capability | auditing an external config/framework repo for transferable value |
 | LRN-091 | 2026-07-03 | keyword-triggered soft-nudge hook w/ bare common tokens over-fires on non-UI work → tuned out; bare only when UI sense dominates, else bigram-or-drop | any advisory/nudge hook keyed on keywords |
 | LRN-092 | 2026-07-03 | SAST smoke test w/ the OFFICIAL example secret = vacuous pass (rules exclude documented example keys by design); validate w/ realistic payloads + measure tier coverage before trusting a gate ruleset | smoke-testing any detector/gate — never the canonical example payload |
 | LRN-093 | 2026-07-03 | grep -F pattern w/ embedded newline = per-line OR = lock that matches anything; structure locks single-line only, flip-test new locks | writing any grep-based structure lock / census test |
 | LRN-094 | 2026-07-03 | SAST severity ≠ exploitability — semgrep ERROR conflates real vulns + hardening recos; metadata does NOT cleanly separate them (measured) → metadata refinement = noisy gate; ERROR-threshold + diff-scoping is the containment | mapping a SAST tool's output to a blocking gate |
 | LRN-095 | 2026-07-03 | orthogonal gates don't contaminate — a conformity verifier must PASS correct-but-insecure code (security is a separate gate's job); proven live (CONFORME on a feature carrying a SQLi); fusing the two degrades each | designing multi-dimension review/verify/audit gates |
 | LRN-096 | 2026-07-04 | a backstop/guard is code — reliable ONLY after a flip-test proves it CAN fail; an unproven guard replacing an advisory = a vacuous guard (LRN-048 applied to guards); flip-test mandatory at guard creation | building any deterministic guard/lint/backstop |
 | LRN-097 | 2026-07-04 | community blog pattern ≠ official feature — "contexts dir" doesn't exist in Claude Code; verify feature against official docs (claude-code-guide) BEFORE building infra; the intent was already covered by real mechanisms (agents/skills/rules) | any "add support for X" request naming a Claude Code feature |
 | LRN-098 | 2026-07-04 | `/model` rewrites settings.json (model line + key reorder) — pending diff after model switch = side-effect, not intent; 2 occurrences | any settings.json commit; any "commit file X" — read diff, verify content matches intent |
 | LRN-099 | 2026-07-05 | auto-orchestrator autonomy boundary: git discipline transfers naturally (branch, no-merge), declared-state discipline does NOT — baseline silently rewrote target TODO + authored registries + scope-crept | designing any auto/headless flow — enumerate declared surfaces, mark each read-only or gated |
 | LRN-100 | 2026-07-05 | tool gated on clean tree must clean its OWN scratch (else self-DoS next run); contract-changing auto-fix needs structural BREAKING flag in the reviewed artifact | any recurring tool w/ cleanliness precondition; any auto-fix touching an API contract |
 | LRN-101 | 2026-07-05 | nginx `add_header` inheritance trap: ANY add_header in a location block drops ALL inherited server-level headers on those responses — audit headers on LIVE responses (`curl -I`), never by reading the config; declared infra can be stale (prod ≠ repo stack) | any nginx project audit (zenquality, faunosteo…); any security-header claim |
 | LRN-102 | 2026-07-05 | deliverable text placed BEFORE a tool call may never render — only the turn's FINAL text is guaranteed displayed; a checklist printed above AskUserQuestion was invisible to the user | any flow whose deliverable is conversational text (checklist, commands, report): end the turn with it, blocking questions come before, never after |
 | LRN-105 | 2026-07-06 | explorer subagent ran a build tool (`graphify .`) mid read-only audit despite prose instructions to only Read/Grep/Bash-read — the runtime observed a config-protection sentinel deny message and self-corrected only after an explicit main-session correction, not from the original prompt | dispatching any "read-only audit" subagent whose toolset includes Bash: state "do not execute build/generator/mutating commands" explicitly, don't rely on "read-only" framing alone to constrain tool CHOICE |
 | LRN-106 | 2026-07-06 | job3-B1 froze a fixture + repointed run-reconcile.sh's T2 off the live registry, declared "unblocked", 20/20 green — job4 (next audit, same file, same day) found T3+T5 in the SAME FILE still read the live registry, same fragility, untouched | fixing one instance of a "reads live state it shouldn't" finding: grep the WHOLE file (not just the cited line) for the same pattern before declaring the class closed |
 | LRN-109 | 2026-07-07 | job8: `skills` CLI (vercel-labs/skills) fetches only `skillPath` (often just SKILL.md), not sibling refs/scripts/templates the skill text references — darwin-skill install gap, not drift/tamper | installing/auditing any skill via the `skills` CLI whose SKILL.md references relative paths — verify those paths exist post-install, don't trust `skillFolderHash` alone |
 | LRN-110 | 2026-07-07 | job8: `21st_magic_component_builder` (magic MCP) opens unauth'd 127.0.0.1 callback server, CORS `*`, no token check, 10min window — any local POST lands verbatim in the tool result the model consumes = local prompt-injection channel | any MCP tool that opens a local callback/listener server to receive async results — check auth + origin scoping on the listener, not just the outbound call |
 | LRN-111 | 2026-07-07 | job8: empty permissions.allow for a risky MCP tool is a VALID posture (not a gap) when transcript census shows zero real invocations — pre-authorizing unused surface buys nothing, ask-gate costs nothing | deciding whether to allowlist any tool/command — check real usage before assuming "no entry = todo" |
 | LRN-112 | 2026-07-08 | job9: CC nested subagent dispatch SUPPORTED since v2.1.172 (cap 5 levels, `Agent` must be in subagent `tools:`) — "flattens to 1 level" is the pre-2.1.172 regime; live env v2.1.203. Contradicts the operating premise of the whole job1-9 series | a subagent-dispatches-subagent design is VERSION-CONTINGENT, not "broken" — check CC version before flagging; fix = raise floor or re-architect to bundle→L1 |
 | LRN-113 | 2026-07-08 | partial-pattern-fix = recurring defect of the job1-9 series: fix the cited instance, leave the twins (trailer A1, YAML A4, attribution A5, hook A2). An adversarial review catches twins later; nothing catches them at commit time | any fix of a banned pattern: grep the ENTIRE surface + add a make-test guard (run-review-guards.sh) that REDs if one occurrence subsists |
 | LRN-114 | 2026-07-08 | editing a hook GENERATOR (_gitflow_emit_pre_commit) does NOT update the INSTALLED hook (.githooks/pre-commit) — silent drift; T10 diffs the allow/block verdict not content, T16 emits fresh in a throwaway repo → job7 gitleaks backstop inert on the repo 8 days | after editing a template-generated artifact: reinstall (install-hook) + a gate that diffs installed==emit |
 | 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 |
 ---
@@ -540,6 +574,7 @@ rules:
 - **Pattern**: narrated/remembered state from ANY source (user OR assistant) is not ground truth. Approval of a diff ≠ its application.
 - **Future application**: anyone asserts "X is done" → verify (git log, file content, grep) before building on it; ESPECIALLY when it contradicts your own earlier statement, or after a context/window break. Internal contradiction → stop, re-check git, never reconcile by accepting the newer claim silently.
 - **Reference**: P3 reprise, commit 493b6b9. Linked to [[LRN-032]] (verify before applying a rule), [[LRN-035]] (check the artifact, not the claim/count).
 - **corroboration 2026-07-01**: multi-repo raccord (6 repos) — mapped each repo's REAL git/fs state (read-only cartography) before EVERY write/destructive op, gated per-gap, re-verified each subagent oracle in the main loop. Declared TODO/registry/checkbox drift confirmed repeatedly; the discipline KILLED false simplifications: a blind `master→main` CHANGELOG swap (reflog showed master renamed AWAY, not a live branch), "just remove the `.claude/**` exemption" (would have broken standalone `/capitalize`, [[LRN-084]]), a config supersession grep that failed on a line-wrap (supersession was real). Narrated/declared state ≠ ground truth, at multi-repo scale.
 ---
@@ -862,6 +897,7 @@ rules:
 - **pattern**: a baseline agent on a worktree named `wt-pre-reconcile` read "pre-reconcile" FROM THE DIR NAME and inferred staleness — reasoning for the WRONG reason (the name), not the right one (verify git). Fixtures + the GREEN test were re-frozen under NEUTRAL names so the engine reaches truth by querying git, never by reading a path hint.
 - **meta — same symptom, distinct cause as [[LRN-074]]**: 074 = a COMMAND-ASSUMPTION (ugrep parsed `-9..` → false green); 077 = a LEAKY FIXTURE (name telegraphs the answer). Different mechanisms, SAME symptom: the test passes/fails for the wrong reason. Cross-cutting lesson = verify a test passes for the RIGHT reason, not merely that it passes — whether the false signal comes from an assumed command (074) or a leaky fixture (077).
 - **future application**: name fixtures/paths neutrally; for any green, ask "did it pass because the subject did the work, or because something leaked the answer?"
 - **corroboration 2026-07-02 (T6c)**: 3rd family member — test truth borrowed from TRANSIENT env state. run-reconcile T6c asserted `$MEM/../skills/darwin-skill` = `.claude/skills/` (the [[LRN-042]] parasite dir), not canonical `skills/`; born green because the parasite still existed, red since the same-day cleanup, unnoticed until the 2026-07-02 audit re-ran the suite ([[EVAL-011]]'s "20/20" silently 19/1 for 2 days). Oracles target CANONICAL paths (never derived `X/../Y`); re-run suites after ANY env cleanup tests may have silently depended on; "green at build" ≠ "green now".
 ## LRN-078 — semver number DERIVES from the change nature; "breaking" = requires a migration
 - **Date**: 2026-06-30
@@ -873,3 +909,355 @@ rules:
 - **Date**: 2026-06-30
 - **pattern**: a thin orchestrator skill (composes an existing tested mechanic + ONE new step) is not unit-testable as a function, but its FLOW is testable by replay on a throwaway repo (gitflow-test style). RED = run the prescribed sequence WITHOUT the new step (the existing mechanic alone) and assert the desired outcome → it reds on exactly the gap. GREEN = add the step. For `/release-candidate`: `gitflow start release`→prep→`finish` (no tag) → assert `vX.Y.Z` on main → REDS (gitflow fans out but never tags); add `git tag` → 5/5. Teeth: the single toggled line (`RC_TAG`) flips red↔green so GREEN can't pass by accident.
 - **future application**: for any orchestrator over a lib mechanic, test the END-TO-END flow on a disposable repo; isolate the NEW step so the RED reds precisely on it (don't re-test the lib's generic part — it has its own tests).
 ## LRN-080 — measure whether the model already does X before adding an instruction to make it do X
 - **Date**: 2026-06-30
 - **pattern**: the --help chantier (implement [[BDR-001]] as a global CLAUDE.md instruction "on --help → render help + stop") was KILLED by its behavioral RED. Before writing a line, measured the control (6 reps, `/web-validate` + `/harden`, no instruction): **6/6 already rendered rich help AND stopped without dispatching** — the supposedly-absent behavior was fully present. Residual value = format consistency across 6 divergent shapes → not worth ~5 lines in a compressed CLAUDE.md on a solo repo. A phantom-value addition avoided.
 - **why it matters**: [[LRN-075]] (test the UNGUIDED control) paying off one chantier later — measuring the RED before building is what caught it. For UNIVERSAL conventions the model already honors (--help, common flags, standard shapes), a "teach it to do X" instruction buys nothing but tokens; the only thing left to buy is consistency, which must clear its own ROI bar.
 - **future application**: before adding any global instruction to ELICIT a behavior, run the behavioral control first — does the model already do it unaided? If yes, the only remaining value is standardization; price it honestly vs the cost (esp. a compressed CLAUDE.md). Often: don't add it.
 - **corroboration 2026-06-30**: 3 consecutive "make the model do X" chantiers — --help ([[BDR-001]]), darwin re-baseline ([[BDR-043]]/[[LRN-082]]), auto-skill-dispatch ([[BDR-044]]) — ALL measured won't-build/moot. A backlog of "add instruction to elicit behavior Y" has a high phantom-value rate (universal conventions + aggressive existing mandates like superpowers L1 already elicit Y) → sweep such backlogs measure-first, expect kills.
 ## LRN-081 — Commit trailers: Claude-COMPOSED content only, never on staging of user-authored text
 - **Date**: 2026-06-30
 - **pattern**: the Claude commit trailers (`Co-Authored-By: Claude …` + `Claude-Session: …`) mark Claude's ACTUAL contribution. They belong on commits whose CONTENT Claude composed — memory entries, code, docs, TODO lines drafted from intent/BDRs. A commit that merely STAGES content the USER wrote (queuing the user's own raw note) gets NEITHER trailer — author = the user, clean. Staging ≠ authorship.
 - **why it matters**: memory-commit.sh + the dev flows append the trailers BY DEFAULT → committing user-authored text through them mis-credits Claude on every note/spec the user writes. A `Claude-Session:` on a 100%-user addition is traceability noise pointing at no Claude contribution.
 - **context**: 2026-06-30 — user's `auto-skill-dispatch` planning note committed `chore(todo)` CLEAN, no trailer (`e591510`, author Bastien Chanot); vs `chore(memory)` BLK-013/BDR-043 (`5b03ac2`) WITH trailers (Claude composed those entries). The split IS the rule.
 - **future application**: before committing on the user's behalf ask "did Claude COMPOSE this content?" Composed (entry/code/doc/TODO-from-intent) → trailers. Merely staging user-written text → no trailers, user-authored. Self-referential proof: this entry + the promoted TODO follow-ups = Claude-composed → trailers OK on their commit.
 - **correction 2026-06-30**: the mechanism claim above ("memory-commit.sh appends trailers by default", body + Index cell) is WRONG. `memory-commit.sh` does NOT append trailers — it commits `git commit -m "$msg"` verbatim (`memory-commit.sh:86`; trailer-agnostic; no `commit.template`, no `prepare-commit-msg` hook). Trailers are MODEL-composed message content (harness git-commit convention). Control point = the composed MESSAGE, not the helper. Proven live: a bare one-liner through the helper (`532ae69`) landed with ZERO trailers → had to amend (`c09f2b2`). Teeth = consciously ADD trailers on Claude-composed commits + OMIT on user-staging; the helper enforces NEITHER. The PRACTICAL guidance above (composed→trailers, staged→none) stays correct — only the mechanism was wrong; the false entry already mis-led one commit (the bare-msg miss). DEFERRED to /prune-memory: rewrite the false "helper appends" wording in this body + the Index cell (curation = not append-only → wrong tool here); this bullet marks WHAT to clean.
 ## LRN-082 — Trigger-cleared on a MULTI-MOTIF exclusion lifts only the NAMED motif — re-check the others before acting
 - **Date**: 2026-06-30
 - **pattern**: an exclusion justified by ≥2 independent grounds lifts only for the ground that actually changed. A "trigger cleared / precondition gone" note naming ground A leaves ground B in full force. Geometric trigger lifted ≠ value trigger lifted; acting on cleared-A without re-checking B = false unblock.
 - **why it matters**: [[BDR-015]] excluded 5 gstack skills from /darwin-skill on TWO grounds — (a) broken symlinks AND (b) external ownership (never modify a third-party submodule). [[BDR-043]] cleared (a) only (symlinks repaired, 0 broken) → marked re-baseline "unblocked". (b) intact: darwin optimizes by EDITING SKILL.md → would edit the gstack submodule = forbidden ([[LRN-070]]). Re-baseline = a score we can't act on → phantom value.
 - **context**: 2026-06-30 — measure-first: searched for results.tsv instead of assuming → GONE (wiped by 23/06 make-plugin reinstall) → no baseline survives + (b) never lifted → action resolved-MOOT, not run. Twin of [[LRN-080]] (--help): trigger fired, measurement showed phantom value (distinct mechanism: there value-absent, here residual-motif).
 - **future application**: before acting on any "exclusion lifted / precondition cleared", enumerate ALL original grounds and verify EACH is gone — not just the one the trigger names. Cleared-A says nothing about B.
 ## LRN-083 — Subagents are an INVALID instrument for measuring MAIN-LOOP spontaneous routing
 - **Date**: 2026-06-30
 - **pattern**: to measure whether the MAIN loop self-invokes a skill on implicit intent, dispatched subagents are non-discriminating — SUBAGENT-STOP tells them to SKIP the L1 routing mandate, and a delegated-execute framing suppresses meta-routing → they hand-do the task regardless of how strong/weak the main-loop prose is. Result pins to the no-route FLOOR (artifact, not signal). Complement of [[LRN-028]] (there subagents OVER-saw installed skills, invalidating a no-skill baseline; here they UNDER-route, invalidating a routing-measurement) — both = subagent ≠ main-loop condition.
 - **why it matters**: a 0/N subagent RED reads as "under-triggers → build the chantier" but is the [[LRN-028]] trap — the instrument can't tell strong prose from weak. Concluding from it = a pass/fail for the WRONG reason ([[LRN-074]]/[[LRN-077]]).
 - **context**: 2026-06-30 auto-skill-dispatch RED. 6 subagents on toy implicit-intent tasks → 0/6 routed → RETIRED as non-discriminating, NOT reported as a number. Reframed; measured instead in REAL fresh main-loop sessions.
 - **future application**: measure main-loop spontaneous routing/discernment in FRESH main-loop sessions (full L0–L4, no SUBAGENT-STOP, real user-turn). Observable instrument = the HUMAN typing the prompts + watching live — cron/schedule-spawned fresh sessions are the right CONDITION but UNOBSERVABLE to the orchestrator (they notify the owner, not the dispatcher), so they can't be the measurement vehicle. Never substitute a subagent for a fresh session in a routing RED. See [[LRN-028]], [[LRN-075]], [[LRN-080]].
 ## LRN-084 — A protection hook enforces PROD safety, not the full branch-flow — the exemption masked the rule-vs-guard divergence
 - **Date**: 2026-07-01
 - **pattern**: the gitflow pre-commit hook is a PROTECTION guard (block code on main/develop), NOT a flow enforcer. It exempts `.claude/**` and can only test "on a protected base" — it can NEVER verify "branched FROM develop" (no base knowledge). So "every change via a branch from develop" is only HALF-encoded by the hook; the base half lives solely upstream in `gitflow_start`. The exemption is scoped to the SIDE-CAR ([[BDR-034]]); it has no branch to follow when memory IS the work → standalone memory fell back to `main`.
 - **why it matters**: a multi-repo raccord committed 5 `chore(memory)` direct on `main` and NOTHING flagged it — nothing was violated, the exemption worked as designed. The divergence was guard (declares PROD protection) vs intended rule (all via branch); the exemption MASKED it, the raccord revealed it by violating the unencoded half. A guard encoding only PART of the intent reads as full enforcement — a false-green.
 - **future application**: when a guard exempts a class or checks one predicate, ask what it does NOT encode and whether a human leans on it for MORE than it enforces. Enforce the unencoded half where it actually lives (the aiguillage at skill start, [[BDR-045]]), do not push it into a guard that structurally can't hold it. Verify the guard's real scope against the rule's full scope before trusting "it would have caught it." See [[BDR-034]], [[BDR-045]], [[LRN-034]].
 ---
 ## LRN-085 — Idempotent CLI install/update: presence guard + channel detection, never `--force`
 - **Date**: 2026-07-01
 - **Context**: install.sh npm-installed claude blindly → EEXIST abort when claude present via native installer (symlink npm doesn't own). Sibling steps (RTK/GSD) already had `command -v` skip guards; install.sh didn't. See [[BLK-014]].
 - **Pattern**: (a) idempotent install step = `command -v <bin>` guard → skip-if-present with version echo, install only in `else`/`elif`. For a BINARY this IS a deterministic oracle (contrast [[LRN-054]]: conversation-state presence has none → don't skip-branch). (b) a CLI can ship via >1 channel (npm vs native). npm can't clobber a bin symlink it doesn't own → EEXIST; `npm --force` = wrong (npm itself says "recklessly", breaks native self-update). Detect channel first: `npm ls -g <pkg>` succeeds → npm-managed → npm; else native → `claude update` self-updater. (c) install ≠ update: first-time installer skips-if-present; the update script does the channel-aware upgrade.
 - **Future application**: any installer/updater for a CLI reachable via multiple channels — guard with `command -v`, branch the updater on detected channel, never blind `--force` over a foreign-owned bin. Caveat [[LRN-036]]: `command -v` needs the bin dir on PATH in shelled-out/hook contexts.
 - **Reference**: [[BLK-014]], mirrors RTK/GSD guard in install-plugins.sh. Related [[LRN-005]] (plugin enable idempotency), [[LRN-039]] (installer config drift).
 ---
 ## LRN-086 — External-tool-generated skill: prove provenance by mtime, gitignore + regen-on-absence (not unconditional) when the tool co-writes a user-editable config
 - **Date**: 2026-07-02
 - **Context**: `skills/find-docs/` showed untracked. `grep -rniE 'find-docs' --include='*.sh'` → 0 hits → wrongly read "hand-authored first-party skill, commit it". FALSE. Generator = external binary `ctx7 setup --claude --cli` (CLI+Skills mode), not any repo script. Oracle that flipped it: mtime `skills/find-docs/SKILL.md` (23:16:59.637) == ctx7 `~/.config/context7/credentials.json` write, same setup run → ctx7 co-created it. User held the correct premise; my repo-only grep was too narrow.
 - **Pattern**: (a) provenance of an untracked artifact — a repo-script grep is BLIND to external-binary generators. Correlate its mtime with the tool's OWN files (creds/config) + read the tool's subcommands (`ctx7 setup --claude/--cli/--mcp`, `remove`) before deciding hand-authored vs tool-owned. (b) `ctx7 setup --claude --cli` writes TWO files 0.13s apart: `~/.claude/skills/find-docs/SKILL.md` (`~/.claude/skills` = symlink to repo `skills/` → lands IN repo) AND `~/.claude/rules/context7.md` (global config, real dir, NOT in repo, user-editable). (c) login ≠ setup: `ctx7 login` = auth/rate-limits only (help = only `--no-browser`), does NOT trigger setup. Orthogonal.
 - **Rule**: tool-generated skill → gitignore it (like `skills-external/frontend-design/`) + regenerate via an install step, do NOT vendor. gitignore coherence: ignoring an artifact REQUIRES an install-step that regenerates it, else a fresh clone loses it. BUT when the same `setup` ALSO (re)writes a user-editable config, guard regen on ABSENCE (`[ ! -f .../find-docs/SKILL.md ]`) — an every-run `setup` would silently clobber that config once customized. Contrast frontend-design: unconditional re-sync is fine (its file is not user-editable).
 - **Future application**: before gitignore-vs-commit on any untracked skill/dir, PROVE provenance (mtime + tool subcommands), never trust a repo grep alone. Tool-owned → gitignore + install-step regen; gate the regen on absence iff the generator co-writes anything the user may hand-edit. Reuses [[LRN-085]] presence-guard oracle (file presence = deterministic). See [[LRN-084]] (guard scope vs full intent), install-plugins.sh Step 6, commit `01d8b8f`.
 ## LRN-087 — presence-flag ≠ capability: rtk silently dead after .bashrc wipe
 - **Date**: 2026-07-02
 - **pattern**: binary installed + hook wired + registries say "always-on" ≠ capability LIVE. Hand-managed .bashrc restore dropped the cargo PATH line → `command -v rtk` failed in hook AND tool shell → hook warned+passed-through EVERY Bash call, input compression OFF ~9 days. Banner truthfully dropped rtk — but an ABSENT line is invisible signal, nobody noticed. Reality/registry gap held ([[BDR-006]]-era always-on belief survived).
 - **fix shape (3 teeth)**: (1) consumer self-heals — probe known install dirs (`~/.cargo/bin`, `~/.local/bin`), never trust PATH ([[LRN-036]]); (2) an emitted/rewritten command executes in ANOTHER shell whose PATH the hook cannot fix → substitute the ABSOLUTE bin path at string head; compound rewrites with residual bare bin at a command position → pass through, never emit a 127 (global substitution unsafe: quoted text, e.g. commit messages, carries the same token at line start — proven live); (3) the rtk BINARY verifies its hook against `hooks/.rtk-hook.sha256` at execution and refuses a modified hook → every legit hook edit must re-pin. Pin = live machinery, NOT vestige — audit rec "delete it" REFUTED by execution ([[LRN-037]]).
 - **future application**: any PATH-dependent capability + hand-managed shell profile → probe install dirs, absolute paths in emitted commands, verify capability END-TO-END; a status line that can silently disappear ≠ monitoring. Check for integrity pins before editing generated hooks.
 - **Reference**: `hooks/rtk-rewrite.sh` (RTK_BIN + absolute-path substitution + compound pass-through), `lib/detect-plugins.sh` detect_rtk, branch bugfix/audit-bugs (audit 2026-07-02). [[BLK-001]] context. See [[LRN-036]], [[LRN-037]].
 ## LRN-088 — token-cutting intuition inverts under measurement: verbosity beats cardinality
 - **Date**: 2026-07-02
 - **pattern**: fixed per-session context overhead measured ~14.6k tok (audit 2026-07-02). The intuitive target (gstack, 34 skills) = only ~592 tok — terse one-liner descriptions. Real weights: CLAUDE.md 3,788 · personal skill descriptions ~3,488 (hand-written trigger lists, ~6× cost/skill vs gstack) · pr-review-toolkit agents 2,183 (6 agents, PR-only use) · superpowers session-inject 1,540 · context7 rule 493. Cutting by item-COUNT intuition misallocates effort ~4×.
 - **actions taken**: pr-review-toolkit OFF by default (−2,183; audit.profile keeps it = reactivation channel), 10 fattest personal descriptions compressed 6,416→4,243 chars (−~540), context7 rule dropped for the find-docs skill (−493; skill body loads on-demand, stable — regen keyed on find-docs absence). Total ≈ −3.2k/session ≈ −22%.
 - **future application**: before any "disable X to save tokens" → measure per-item bytes FIRST (frontmatter extraction, plugin cache); expect the fat where descriptions are hand-written rich, not where items are many. Profiles toggle SKILLS only — plugin payloads (agents/skills in cache) need `enabledPlugins`. [[LRN-080]] measure-first corroborated on a new axis (cost, not behavior).
 - **Reference**: audit 2026-07-02 measurement + branch feature/audit-tokens. See [[BDR-014]], [[LRN-043]].
 ## LRN-089 — a pass-through wrapper whose callee reads ambient state silently ignores its args
 - **Date**: 2026-07-03
 - **pattern**: a CLI/dispatcher that forwards `"$@"` to a function which derives its TARGET from ambient state (HEAD, cwd, env, "current X") rather than from those args → the args are silently dropped. The call SITE looks parameterized (`finish bugfix audit-bugs`) but the callee acts on whatever state it's standing in → wrong-target action, NO error. `gitflow_finish` read `HEAD`, never `$1/$2`; `finish bugfix X` from another branch merged that other branch.
 - **context**: audit 2026-07-02, `lib/gitflow.sh:257` `finish) gitflow_finish "$@"` passed args the function never consulted. Surfaced when a finish "for" one branch merged another (LOT3). [[BLK-015]].
 - **future application**: any wrapper/dispatcher forwarding args to a callee that resolves its target from ambient state — either (a) make the callee USE the args as the target, or (b) if the ambient-state contract is deliberate, treat passed args as an ASSERTION and refuse loudly when they disagree with the state. Never let forwarded args be silently dropped: silent-drop = the caller believes they steered, the callee ignored them. Sibling of "presence-flag ≠ capability" [[LRN-087]] — both = a visible signal lying about the real behavior.
 - **Reference**: `lib/gitflow.sh` gitflow_finish arg-guard, `lib/gitflow-test.sh` T12. [[BLK-015]].
 ## LRN-090 — external-repo audit: open WIRED subsystems before declarative
 - **pattern**: auditing external config/framework repo for transferable value → rank subsystems WIRED (executable: hooks/, runners, dispatchers) vs DECLARATIVE (docs, rules/, aspirational frontmatter). Wired > declarative: declarative often inert (ECC rules/ `paths:` = 0 consumers; eval-harness = SKILL.md, no runner — "belle méthodo / vaporware"); wired = a real mechanism worth adapting.
 - **context**: ECC 2nd-look 2026-07-03 (Opus 4.8, 6 agents, repo unchanged since 01/07). [[BDR-047]] audit (01/07) inventoried the declarative surface + concluded zero import — right on facts, but hooks/ (ECC's only live subsystem) was OUT of scope and held the sole real adaptation → config-protection PreToolUse guard.
 - **future application**: next external-repo value audit → enumerate hooks/, scripts/, runners FIRST; treat rules/docs/SKILL.md as claims to verify ("is it wired?"), not value. Described capability ≠ wired capability.
 - **cousin**: [[LRN-087]] presence-flag ≠ capability; [[LRN-089]] forwarded-args silently dropped — same family: a visible signal (a file, a flag, a `paths:`) lying about real behavior.
 ## LRN-091 — a soft-nudge hook that over-fires gets ignored (banner-blindness)
 - **pattern**: keyword-triggered nudge (design-toolchain reminder) with bare common tokens fires on non-UI work → reader tunes it out. Same class as a diagnostic that cries false [[LRN-047]]: a signal wrong too often stops being read.
 - **rule**: keep a token BARE only when its UI sense dominates largely in a dev context (glassmorphism, navbar). Token common in non-UI talk (design, component, theme, transition, frontend) → require a UI-specific bigram (design system, front-end design) or drop; in doubt → bigram-or-drop. Borderline standalone nouns (dashboard, animation) may stay bare as an assumed call — the fire-log arbitrates later on data, not gut. (NOT "never bare tokens" — animation stays bare here by design.)
 - **context**: design-toolchain-reminder.sh — 07-02 tightening (dropped page/form/menu/…) insufficient; 6 bare tokens still false-fired ~6×/session during the ECC config audit (design, ecc_dashboard.py, component, frontend, theme, transition, palette). 07-03 fix: dropped them, dashboard→`\bdashboard\b` (filename match killed, "admin dashboard" kept), added a fire-log (time+token+excerpt). `lib/tests/design-toolchain-reminder.test.sh` locks it (18 checks).
 - **cousin**: [[LRN-047]] a doctor that cries false is ignored.
 ## LRN-092 — SAST smoke test: official example keys are rule-excluded — "no findings" proves nothing
 - **pattern**: smoke-testing a SAST/secret detector w/ the OFFICIAL example payload (AWS `AKIA...EXAMPLE`) → 0 findings BY DESIGN — rules exclude documented example keys to kill FP. A vacuous pass, [[LRN-048]] class (a pass must prove it looked). Validate w/ realistic-shaped payloads AND enumerate what the tier does NOT catch before trusting a ruleset as a gate.
 - **context**: lot 1 semgrep-install dogfood 2026-07-03. `p/secrets`+`p/security-audit` community tier: anonymous fetch OK (52 rules, no login), `subprocess-shell-true` detected ERROR; MISSED %-format SQLi on bare cursor (no recognized DB-API context) + fake-checksum `ghp_` token. Gap logged for security-auditor agent design (consider adding `p/owasp-top-ten`).
 - **future application**: any detector/gate smoke test — craft realistic payloads, never the canonical example; measure the miss-list on purpose-built fixtures; size the gate's blocking scope on that data.
 - **cousin**: [[LRN-048]] a 0/OK must prove it looked; [[LRN-047]] noisy guard = ignored guard; conditions [[BDR-048]].
 ## LRN-093 — grep -F with an embedded newline = per-line OR = vacuous lock
 - **pattern**: a fixed-string grep pattern containing a newline is treated as MULTIPLE patterns (one per line) — match succeeds if ANY line matches. A structure lock written that way passes on essentially anything (`"no\n    forced loop"` → matches any "no") = a lock that proves nothing, [[LRN-048]] class.
 - **context**: lot 2 `lib/tests/contract-verifier.test.sh`, caught in self-review BEFORE first run; replaced by a single-line distinctive anchor ("proceed straight to the security gate").
 - **future application**: structure locks / census greps = ONE line per pattern, always; a clause spanning lines → lock a distinctive single-line fragment. Flip-test every new lock (prove it CAN fail) before trusting its green.
 - **cousin**: [[LRN-048]] a pass must prove it looked; [[LRN-046]] deterministic-oracle discipline.
 ## LRN-094 — SAST severity ≠ exploitability; metadata does not cleanly separate — don't refine on it
 - **pattern**: semgrep `ERROR` conflates exploitable vulns (SQLi, secrets, command injection) with hardening recommendations (Dockerfile missing-USER, npm release-age). The obvious refinement — gate on `metadata.impact`/`likelihood`/`confidence` — does NOT work: measured, the Dockerfile hygiene ERROR (`impact=MEDIUM likelihood=LOW`) is indistinguishable from a tainted-SQL ERROR (`impact=MEDIUM likelihood=MEDIUM`), and a real command-injection reads `impact=LOW likelihood=HIGH`. Metadata-based severity = a noisy, non-deterministic gate ([[LRN-077]] class).
 - **context**: lot 3 security-auditor design 2026-07-03. Measured on 2 real repos (faunosteo, game): the only added blocking ERROR from owasp-top-ten is Dockerfile hygiene, contained because gate mode scopes to the DIFF (a pre-existing infra finding can't block an unrelated code change).
 - **future application**: mapping any SAST to a blocking gate — take the tool's ERROR/blocking level as the deterministic threshold, contain FP by SCOPING (diff, not repo), NOT by a metadata heuristic or a hand-maintained hygiene denylist ([[LRN-049]]: match guard cost to proven stake — build the denylist only if hygiene ERRORs prove noisy on a real project).
 - **cousin**: [[LRN-047]] noisy gate = ignored; [[LRN-077]] non-deterministic gate; conditions [[BDR-048]].
 ## LRN-095 — Orthogonal gates don't contaminate: a conformity check must pass correct-but-insecure code
 - **pattern**: when a pipeline has distinct gates (request-conformity, security), each judges ONLY its dimension. A conformity verifier must return CONFORME on code that is correct-but-insecure — the vuln is the SECURITY gate's job, not a conformity gap. Proven live: a `get_item` feature satisfying its contract but carrying a `%`-interpolation SQLi → verifier CONFORME, security-auditor BLOCK(1). Fusing the two into one "quality" gate makes each worse: the conformity check starts hunting vulns (scope creep, misses conformity), the security check starts judging feature-completeness (dilutes).
 - **context**: lot 4 verify-secure-loop dogfood 2026-07-03. The orthogonality is WHY the order invariant matters (re-verify request before re-scan security) — two independent axes re-checked independently.
 - **future application**: any multi-dimension gate (review lenses, verify+audit, correctness+perf) — keep each gate single-axis and let a finding on axis B pass axis A's gate; compose verdicts in the orchestrator, don't merge the judges.
 - **cousin**: [[BDR-050]] the pipeline; [[BDR-049]] fresh verifier; conditions [[LRN-083]].
 ## LRN-096 — A backstop is code: prove it can FAIL (flip-test) before trusting its green
 - **pattern**: a deterministic guard built to replace a forgettable advisory is itself code, and an UNPROVEN guard is a vacuous guard — [[LRN-048]] (a pass must prove it looked) applied to guards themselves. The LRN-093 backstop (refuse `\n` in grep/tf patterns) shipped with a regex requiring whitespace before `tf` → it silently MISSED `tf` at line start (exactly where the real locks sit). A flip-test (feed the guard a KNOWN offender, assert it bites) caught the hole; without it the guard would have green-lit the very class it was built to kill. So: a flip-test is MANDATORY at guard creation, part of the guard, not optional QA.
 - **why it matters**: the whole point of a backstop is that it fires on the bad case; a guard that can't fail proves nothing and is WORSE than the advisory it replaced (false confidence). The advisory→backstop move ([[LRN-047]] [[LRN-091]], own doctrine) is only sound if the backstop is itself verified against a real miss.
 - **context**: lot 5 `lib/tests/no-vacuous-locks.test.sh` 2026-07-04. Built the guard, its flip-test RED'd (regex too weak, missed line-start `tf`), fixed the regex, flip-test green. The guard now ships WITH the flip-test inline so it self-proves on every run.
 - **future application**: building any guard/lint/census/backstop — bundle a flip-test (a synthetic offender the guard must catch) in the same file; a guard whose failure path was never exercised is untrusted. Corroborates [[LRN-047]]/[[LRN-091]] (advisory→deterministic) — this is the *quality bar* on the deterministic replacement.
 - **cousin**: [[LRN-048]] prove it looked; [[LRN-093]] the class this guards; [[LRN-046]] deterministic-oracle discipline.
 ## LRN-097 — Community blog pattern ≠ official feature: verify against docs before building infra
 - **pattern**: user requested a `~/.claude/contexts/` dir + symlink, with 3 example "context mode" files (review/research/dev) from a community pattern. Official docs check (claude-code-guide agent): NO contexts feature exists in Claude Code — no loader, no `/context <name>`, nothing reads that dir. Building it = dead infra. The underlying intent (modal postures) was ALREADY covered by real mechanisms: review → verifier/security-auditor/review skills; research → analyzer/Explore; dev norms → CLAUDE.md always-on. One proposed "context" even CONTRADICTED standing doctrine ("get it working first" vs "root causes only").
 - **why it matters**: plausible-looking blog patterns import silently as "features"; the cost is not just dead files — norms moved into a nonexistent loader silently STOP applying. Gate: any request naming a Claude Code capability → verify against official docs BEFORE writing files; then map the intent onto the real mechanism.
 - **context**: 2026-07-04 rules-dir chantier. `rules/` (real feature, verified: paths-scoped lazy loading) was built; `contexts/` (nonexistent) was refused with the doc citation.
 - **future application**: "add support for X" where X is a Claude Code/tool feature — claude-code-guide first, build second. Same discipline for any tool: feature existence is a fact to verify, not assume.
 - **cousin**: [[LRN-086]] provenance discipline; [[LRN-046]] verify before trust; CLAUDE.md "Never assume — verify".
 ## LRN-098 — `/model` silently rewrites settings.json: read the diff before any settings commit
 - **pattern**: `/model` persists the switch by REWRITING settings.json — changes `model` line AND reorders keys (attribution block moved to top). Pending settings.json diff after a model switch = side-effect, not intent. 2nd occurrence: ae8ad86 undid the first (opus-4-8 restored); today "commit settings.json" nearly re-committed fable-5 as default right after that undo. Catch came from reading DIFF CONTENT, not filename: request said commit, diff contradicted prior intentional commit → surfaced, user chose `git restore`.
 - **why it matters**: "dirty settings.json" reads as innocent drift; blind commit flips default model for ALL sessions + silently reverses an explicit prior decision. A request "commit file X" is about the file — content must still match user intent.
 - **context**: 2026-07-04 RC 1.0.0 cleanup. Diff = `claude-opus-4-8[1m]` → `claude-fable-5[1m]` + attribution reorder (no semantic change). AskUserQuestion → restore.
 - **future application**: settings.json modified → read diff, check `model` line before commit. Generalize: any hand-curated config a tool co-writes ([[LRN-039]]) — diff before commit, surface contradiction with prior commits.
 - **cousin**: [[LRN-039]] installers drift hand-curated config; [[LRN-050]] show-before-write gate; [[LRN-034]] narrated state ≠ ground truth.
 - **backmerge**: from release/1.0.0 (a623514) — 2026-07-08 review remediation A3.
 ## LRN-099 — Auto-orchestrator autonomy boundary: working branch YES, declared/shared state NO
 - **pattern**: /tour RED baseline (no skill, pressure "injoignable, reboucle jusqu'à propre"): git discipline held NATURALLY (gitflow lib branch, no merge w/o signal, atomic commits — doctrine survived into subagent) BUT state-write discipline failed across the board: target TODO silently rewritten (boxes checked, restructured), BDR/journal entries authored autonomously, unrequested bootstrap (.gitignore + registries "bonus hygiene"). Plus: security = ad-hoc grep+ruff (no semgrep floor), findings only in final chat msg (no reviewable artifact), loop unbounded (converged pass 2 by luck).
 - **why**: model generalizes commit discipline from doctrine; "declared state = someone's approval surface" NOT in its prior — such writes look helpful. Auto-flow skills must lock declared-state writes explicitly (read-only rules, report-only phases), not just git verbs.
 - **context**: 2026-07-04 /tour TDD, seeded fixture (vuln + dead code + lying TODO + stale README). 6 gaps → 6 counters in SKILL.md; GREEN closed all, disk-verified.
 - **future application**: designing any auto/headless flow — enumerate SHARED/DECLARED surfaces (TODO, registries, human-facing docs, config), mark each read-only or gated. Never assume git discipline implies state discipline.
 - **cousin**: [[LRN-083]] bounded loops in main loop; /reconcile principle (inferred checkbox = the lie).
 ## LRN-100 — Clean-tree-gated tools must clean own scratch (self-DoS); breaking auto-fix needs structural flag
 - **pattern**: /tour GREEN left 4 untracked scratch files (`.tour-semgrep*.md`) → tree dirty at end → NEXT run hits own "dirty tree → report-only" precondition = self-block. Same run: HIGH security fix adding required auth header = API-BREAKING, reported plain "fixed" — branch diff doesn't shout contract change.
 - **why**: preconditions designed against user WIP also fire on the tool's own residue → scratch cleanup = explicit end-of-run step. Both = omission failures → structural counters (template slot: STEP 3.2 cleanup, BREAKING tag in report template + summary), NOT prohibition prose (writing-skills "match form to failure").
 - **context**: 2026-07-04 /tour GREEN on fixture; both patched at REFACTOR (SKILL.md STEP 3). Additions template-structural, NOT re-run through 3rd full pass (cost) — re-test first real use.
 - **future application**: any recurring tool gated on repo cleanliness → audit what IT leaves behind; any auto-applied fix changing a contract → structural BREAKING flag in the human-reviewed artifact.
 - **cousin**: [[LRN-099]] same chantier; [[LRN-071]] swallowed-failure class (silent residue ≈ masked state).
 ## LRN-101 — nginx add_header inheritance: one child header wipes ALL parent headers — verify LIVE, not in config
 - **pattern**: nginx `add_header` inherits from server level ONLY if a location block declares NONE of its own. One `add_header Cache-Control ...` in a location → ALL 5 server-level security headers (CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy) silently dropped on every response matching that location. bchanot-cv live: pages served ZERO security headers while the config declared all 5; only the 404 path (no location-level add_header) carried them. Corollary, same audit: declared infra was STALE — prod turned out native nginx, repo's Docker stack latent (user correction post-audit) → container findings latent, live fix belongs to the VPS config outside the repo.
 - **why**: config review says "headers present" — a lie by inheritance. Only oracle = live responses (`curl -sI` per content type: html, pdf, image). Fix = repeat the headers in every location that uses add_header (or `include security-headers.conf`).
 - **context**: 2026-07-05 first real /tour run (report-only, bchanot-cv), cso posture finding SEC-2, live-confirmed.
 - **future application**: ANY nginx repo audit — curl live per location class before trusting config; ANY audit — confirm which stack actually serves prod before scoping fixes.
 - **cousin**: [[LRN-034]] narrated ≠ ground truth; [[LRN-046]] verify before trust.
 - **backmerge**: from release/1.0.0 (74d3804) — 2026-07-08 review remediation A3.
 ## LRN-102 — Deliverable text before a tool call may never render: the turn's FINAL text is the only guaranteed display
 - **pattern**: /deploy hand-back printed the full checklist in the assistant message, then called AskUserQuestion. The user saw ONLY the question UI — the checklist never reached them ("là on a rien, je dois ouvrir le fichier"). The harness renders reliably only the LAST text of a turn; text between/before tool calls can be swallowed by the tool UI.
 - **why**: a skill whose deliverable is conversational (commands to copy-paste, a report) fails silently if any tool call follows the print — the user experiences "nothing displayed" while the transcript technically contains it. Structural fix: the deliverable IS the turn's final text; collect answers BEFORE printing, or let the reply arrive as the next user message.
 - **context**: 2026-07-05 /deploy run 2 (bchanot-cv). Skill patched same turn: checklist display-only (no NEXT.sh file at all — user: throwaway once deployed) + hand-back ends the turn, no tool call after.
 - **future application**: designing any skill/flow output meant to be read+used from the conversation — put it LAST; never sandwich a deliverable between tool calls; prefer plain-text report requests over blocking question tools after a deliverable.
 - **cousin**: [[LRN-100]] same skill lineage; CLAUDE.md communication doctrine (final message carries everything).
 ## LRN-105 — "read-only audit" prose does not constrain subagent tool CHOICE; state the ban explicitly
 - **pattern**: job3 docs-drift audit dispatched an exploration subagent (Bash + Read/Grep, "audit BODIES — do NOT modify any file") to check graphify skill docs. It ran `graphify .` to check CLI behavior — a real build, not a read — leaving an empty `graphify-out/` dir at repo root. The prompt said "read-only" and "verify via Read/Grep/Bash (read-only)" but never named the specific command class to avoid; the agent treated "run the CLI to see what it does" as within a Bash read-only mandate.
 - **why**: "read-only" is a framing about FILES, not an instruction the model maps onto every tool call by default — a subagent with Bash access will happily execute a program to observe its behavior, which is investigative but not read-only if the program writes to disk. The fix only landed after a main-session correction mid-run ("do NOT run graphify... verify by reading the installed source instead"), not from the original prompt.
 - **context**: 2026-07-06, job3 audit exploration phase (`.audit/job3-report.md` A1/A2 findings, incident noted in the report header). No tracked file was touched; the stray dir was harmless but wasted a round-trip and could have mutated git-visible state on a less-guarded command.
 - **future application**: any subagent dispatch framed as "read-only" / "audit" / "verify" that grants Bash — explicitly ban execution of the subject-under-test's own CLI/build/generator commands, and name the safe alternative (read installed source, grep docs) in the same sentence. Don't rely on the word "read-only" alone to scope tool use.
 - **cousin**: [[LRN-100]] (tool must clean its own scratch) — same class of "prose framing ≠ enforced constraint", different failure mode.
 ## LRN-103 — BLK-009 was stale: re-probe confirms `paths:` frontmatter works at BOTH levels now
 - **pattern**: BLK-009 (2026-06-25) recorded user-level `paths:` rules never inject (GH #21858, CC 2.1.190). job1 instruction-file audit (2026-07-06) cited it as open/broken to flag rules/README.md's documented lazy-load mechanism as self-contradicting. Fresh re-probe same day (3-file probe, `**/*.blkprobe` glob): confirmed loading now works at BOTH project-level AND user-level. Bug gone (or no longer reproducible on current CC version) — the registry's "still broken" claim was stale and was about to justify a caveat in rules/README.md warning about a bug that no longer exists.
 - **why**: registries are append-only + dated — a recorded status is a snapshot, not a standing fact. Any decision or audit finding that cites an open upstream blocker without re-probing risks acting on stale tool-version info, especially across CC version bumps.
 - **context**: 2026-07-06, job1 audit follow-up (.audit/job1-report.md, finding F13). BLK-009 closed same session; workaround it forced ([[BDR-031]] unconditional + compressed global CLAUDE.md) no longer required by this bug specifically, though BDR-031 itself stands on its own merits pending separate review.
 - **future application**: before acting on ANY open upstream/tool blocker cited to justify a fix, a caveat, or a design constraint — re-probe it live if cheap, don't just trust the registry's last-recorded status.
 - **cousin**: [[BLK-009]] closed this session; [[BDR-031]] (the workaround this bug forced).
 ## LRN-104 — a hook's output message is part of its test contract; no runner = regression invisible
 - **pattern**: job1 F14 (`3f639b3`) changed design-hook stdout to pointer-only; test oracle grepped old literal `design-toolchain` → 9 fire-checks silently red 3 days. Hook itself fine — broken oracle, not broken behavior. Caught ONLY when job2 executor ran the suite as its F4 gate; zero runner existed before (job2 F10). Fix: oracle synced to durable fragment `full toolchain` (heading BDR-021 requires the hook to quote verbatim) + `make test` target wired.
 - **why**: an untested output string IS an interface — its test must anchor on the durable contract part (the mandated heading), not incidental wording. No automated runner → oracle drift accumulates unseen; "18 checks lock it" ([[LRN-091]]) protected nothing while nothing ran them.
 - **2nd facet**: audit yaml.safe_load stops at FIRST error/file — fixing error #1 unmasked pre-existing error #2 (onboard/plugin-check argument-hint). Verify errors-per-file exhaustively, not error-presence.
 - **future application**: change any hook/script output consumed by a test → run its test same commit. `make test` now the deterministic backstop (job2 F10). Audit parse-checks: iterate until file fully clean, count errors not booleans.
 - **cousin**: [[LRN-091]] (the lock that never ran), [[LRN-096]] (a guard is code, prove it can fail), [[EVAL-017]].
 ## LRN-106 — fixing B1 in one file ≠ closing the B1 pattern
 - **pattern**: job3-B1 (2026-07-06) froze `lib/tests/fixtures/blockers-snapshot.md`, repointed run-reconcile.sh's T2 at it, declared "B1 UNBLOCKED", suite 20/20 GREEN. job4 (J4-10), the very next audit pass, same file, same day, found T3 and T5 in the SAME FILE still reading the LIVE `$MEM/decisions.md` — identical fragility class, untouched siblings, one file over.
 - **why**: "suite green" + "named finding fixed" don't imply "no other instance of the same root cause survives nearby." The fix scoped to exactly what the finding cited (T2's BLK-status read); T3/T5's structurally identical read (decisions.md contradiction/deferral scan) wasn't touched because it wasn't literally named, even though it's the same bug.
 - **context**: 2026-07-06, job3 chore/job3-fixes (B1 unblock) then job4 SPEC-10 (`.audit/job4-report.md` J4-10), same run-reconcile.sh, same session-day — closed for real this time (T3/T5 repointed at a new `decisions-snapshot.md` fixture, `$MEM` variable deleted, `grep -c '$MEM' == 0` gate).
 - **future application**: after fixing one instance of a "reads live state it shouldn't" (or any similarly generic) finding, grep the WHOLE FILE (and ideally the whole surface class) for the same pattern before declaring the class closed — not just the line/test the finding cited.
 - **cousin**: [[LRN-077]] (pin grep, don't trust one instance), [[BDR-041]] (reconcile design: verify don't believe).
 ## LRN-107 — read-only subagent mandates must ban copying secret VALUES, not just mutations
 - **pattern**: job6 (2026-07-07), an explorer subagent under explicit no-execute/read-only mandate (LRN-105 class) copied the plaintext `MAGIC_API_KEY` value into its own scratch file while investigating the magic MCP config. Harness flagged it; main session redacted (1 occurrence, clean post-scan). The mandate said "don't mutate anything" — it never said "don't copy a secret's value into a NEW file you create", so a read-only agent still leaked a secret copy.
 - **why**: "read-only" naturally reads as "doesn't change existing state" — copying a value into a fresh scratch file isn't a mutation of anything that existed, so it doesn't trip that mental model, but it creates a brand new place the secret now lives (BDR-026's exact class: secrets have copies beyond the canonical store — tool configs, transcripts, caches, and now subagent scratch files too).
 - **context**: `.audit/job6-report.md` "Incident (contained)" section; explorer-C.md redacted post-incident; caught before job6's execution phase, contained to scratchpad only.
 - **future application**: any read-only/no-execute subagent mandate that touches config or env files must explicitly ban copying a secret's VALUE into agent output/scratch, not just ban editing/deleting. Phrase the mandate as "reference by name/location, never paste the value" — when auditing MCP/env config, prefer `jq 'del(.. | .env?)'`-style filtering (already BDR-026 practice) over raw `cat`.
 - **cousin**: [[BDR-026]] (secrets have copies, protect/audit them all), [[LRN-105]] (explorer no-execute mandate, the sibling rule this extends).
 ---
 ## LRN-108 — `claude mcp add --env KEY=value` writes the VALUE literally; use `${VAR}` unless you mean to
 - **pattern**: job7 (2026-07-07), root-cause of the recurring MAGIC_API_KEY leak: `claude mcp add magic --env API_KEY="$MAGIC_API_KEY"` (bash-expanded before the CLI ever sees it) writes the resolved plaintext string into `~/.claude.json`/`.mcp.json` — there is no `mcp add` flag that stores a reference instead. Claude Code DOES expand `${VAR}`/`${VAR:-default}` at parse time in `mcpServers` config (`env`/`command`/`args`/`url`/`headers`, both project and user scope — code.claude.com/docs/en/mcp.md) — but only if you single-quote the value so bash doesn't resolve it first: `--env 'API_KEY=${MAGIC_API_KEY}'`. Single vs. double quotes around the SAME-looking flag is the entire difference between "reference" and "plaintext-forever".
 - **why**: the natural way to type this flag (`--env API_KEY="$MY_VAR"`, matching how you'd set the var for the CLI's OWN process) is exactly the trap — it looks like "pass the variable" but bash resolves it to its value before `claude` ever runs, and the CLI just writes whatever string it received. Nothing in the CLI's own behavior signals this; you only find out by grepping the resulting config.
 - **context**: `lib/toggle-external.sh:191` had this exact double-quoted form since BDR-025/026; it materialized the key into `~/.claude.json` (2026-07-02 incident) and kept re-leaking into every native auto-backup taken afterward (5-file rotating ring buffer, plaintext each time) until fixed at the source.
 - **future application**: adding ANY MCP server with a secret via `claude mcp add --env`, single-quote the value using `${VAR}` syntax, never double-quote/bash-expand it. The var still has to exist in the environment of the process that starts `claude` — don't solve that with a blanket `export` in `~/.bashrc` (broadens exposure to every subprocess); scope it with a wrapper function that sources the secret into a subshell before `exec`ing the real binary (see `~/.bashrc`'s `claude()` function, [[BDR-057]]).
 - **cousin**: [[BDR-026]] (canonical vault + copies), [[BDR-057]] (secrets-by-reference decision this trap motivated), [[LRN-107]] (same job family, don't-copy-the-value discipline).
 ## LRN-109 — `skills` CLI (vercel-labs/skills) fetches only `skillPath`, not sibling refs/scripts/templates
 - **context**: job8 audit flagged darwin-skill NOT-CLEAN — SKILL.md references `references/*.md`, `scripts/*.mjs`, `templates/*.html`, all absent on disk. Traced to `~/.agents/.skill-lock.json`: `skillPath: "SKILL.md"` — installer fetched that ONE file, never the sibling dirs the skill text points to. Upstream repo (public clone, verified) had them all at the exact commit already recorded (`skillFolderHash` matches) — not drift, an installer-scope gap.
 - **future application**: any skill installed via `skills` CLI whose SKILL.md references relative paths needs a post-install check those paths exist on disk — `skillFolderHash` only hashes what WAS fetched, says nothing about what's missing. If absent: clone source repo at the recorded hash, copy full tree in, keep `.git` detached (cheap real pin, beats trusting the CLI's opaque hash alone).
 - **cousin**: [[BDR-058]] (this job's fix), darwin-skill's OVERSCOPED git-commit finding (job8 report — 3rd-party code, not patched, accepted risk under human-checkpoint gating, twin of [[LRN-105]]'s no-execute mandate for OUR read-only audits).
 ## LRN-110 — magic MCP `component_builder`'s local callback server = unauthenticated prompt-injection channel
 - **context**: job8 audit read `dist/utils/callback-server.js:36` (+ `create-ui.js:35-38`) in the installed `@21st-dev/magic` package. `21st_magic_component_builder` opens a plain HTTP server on `127.0.0.1:9221+`, `Access-Control-Allow-Origin: *`, no token/origin check, staying open up to 10 minutes per call. Whatever body a POST to `/data` carries gets injected VERBATIM into the tool result the model then consumes — any local process or an open browser tab on the same machine can win the race against the legitimate browser hand-back.
 - **future application**: this is in the third-party package's code, not our config — don't try to patch a vendored/npx-installed dependency. The only real lever is on OUR side of the boundary: never allowlist a tool with this shape, keep it `ask`-gated so a human sees every invocation (see [[BDR-059]]). Applies to any MCP tool whose implementation opens a listener to receive async results, not just this one — check the listener's auth/origin scoping when auditing MCP server code, the tool's *description* text tells you nothing about it.
 - **cousin**: [[BDR-059]] (the settings fix), [[LRN-111]] (why the allowlist stays empty), job8 report §2 surface 1 finding A#0.
 ## LRN-111 — empty allowlist is a valid, deliberate posture when real usage is zero, not a leftover gap
 - **context**: job8 census (grepping real `"name":"mcp__…"` tool_use blocks across `~/.claude/projects`, not text mentions) found ~910 mentions of `mcp__magic__*` but ZERO real invocations, ever. `permissions.allow`/`permissions.ask` had no `mcp__*` entries at all before this job — job6 flagged that as "ZERO scoping", easy to misread as an oversight to fix by adding an allowlist.
 - **future application**: before treating "no entry for tool X" as a gap needing an allowlist, check real usage first (grep tool_use blocks, not prose mentions). If usage is zero, pre-authorizing costs nothing to skip and buys nothing to add — the honest fix is making the ask-gate EXPLICIT (so it can't regress silently), not granting allow access nobody needs yet. Only add allow entries when real, measured, recurring usage justifies removing the friction.
 - **cousin**: [[BDR-059]], [[LRN-110]], [[LRN-088]] (same family: measure before assuming an absence is a defect).
 ## LRN-112 — nested subagent dispatch is supported (CC ≥ v2.1.172), not a flatten-to-1 no-op
 - **context**: the whole job1-9 audit series ran on the premise *"Claude Code aplatit à 1 niveau → un design supposant 2 niveaux de sous-agents est cassé silencieusement."* job9 corrected it via `claude-code-guide` (official docs `code.claude.com/docs/en/agent-sdk/subagents.md`): a running subagent CAN spawn a further subagent IF `Agent` is in its `tools:` (omit it / add to `disallowedTools` to prevent nesting); hard cap **5 levels** ("a subagent 5 levels below main can't spawn further"); nesting **stabilized in v2.1.172** ("let subagents spawn their own subagents") — earlier versions did not support it at all. Live env confirmed **v2.1.203** (user). `claude --version` was unavailable in-sandbox so the report bracketed but could not pin it; the user pinned it.
 - **future application**: NEVER classify a subagent-dispatches-subagent design as "BROKEN" without checking the CC version. On ≥2.1.172 it works within the 5-level cap; on <2.1.172 it silently no-ops. The actionable finding is a VERSION-FLOOR ([[BDR-060]]) or a version-robust re-architecture (bundle→L1, [[BDR-061]]) — not "it's broken." When an agent must NOT nest, enforce it structurally: drop `Agent` from its `tools:` (done for seo/geo analyzers). Re-audit any prior job1-9 "nested = broken" finding through this lens.
 - **cousin**: [[BDR-060]] (version floor), [[BDR-061]] (path-b bundle pattern), [[LRN-057]] (subagent invocation idioms).
 ## LRN-113 — Partial-pattern-fix is the job1-9 series' recurring defect: grep the whole surface + guard it
 - **pattern**: fix one cited instance of a banned pattern, leave the twins. Review found 4: trailer stripped from commit-changer only (A1, twins in bugfixer/feater/hotfixer); YAML quoted elsewhere but seo/security-auditor left broken (A4); attribution scrubbed on 3 skills but geo-analyzer missed (A5); gitleaks added to the hook generator but the installed hook not regenerated (A2).
 - **why it recurs**: the fixer greps for the reported line, fixes it, stops — never enumerates the pattern across the full surface. An adversarial review catches the twins later; nothing catches them at commit time.
 - **fix**: every pattern-fix ends with (1) a whole-surface grep proving zero residue, (2) a deterministic make-test guard that REDs if any occurrence returns. Shipped `lib/tests/run-review-guards.sh` — G1 trailer, G2 false attribution, G3 strict-YAML, G4 reconcile hermeticity, G5 hook-drift; teeth-verified (planted violation REDs). This is the check that would have caught A1/A4/A5/A2 at make-test time instead of a review.
 - **future application**: any "fix pattern X" task → grep agents/ lib/ hooks/ templates/ skills/, add/extend a review-guard with teeth.
 - **cousin**: [[LRN-114]] (hook-drift class), [[LRN-047]] (silent degradation → measure/guard).
 ## LRN-114 — Editing a hook generator does not touch the installed hook: reinstall + drift-guard
 - **pattern**: job7 added the gitleaks scan to `_gitflow_emit_pre_commit` (the GENERATOR), but the installed `.githooks/pre-commit` is only (re)written by `gitflow init`/`install-hook`. job7 never re-installed → the repo's active hook stayed the pre-job7 version (620071b) for 8 days; `git commit` ran no secret scan while the team believed it did.
 - **why undetected**: T10 (drift test) compares only the hook's allow/block VERDICT, not content; T16 emits a FRESH hook in a throwaway repo, validating the generator, never the installed file. Both green while the installed hook was stale.
 - **fix**: after editing any template-generated artifact, regenerate the installed copy (`gitflow.sh install-hook`) AND add a content-drift gate — `run-review-guards.sh` G5 diffs installed `.githooks/pre-commit` against `emit-hook`.
 - **future application**: any generator/template emitting an on-disk artifact needs an "installed == freshly-emitted" test, not just a behavioral one.
 - **cousin**: [[LRN-113]] (partial-fix + guard), [[LRN-039]] (installers drift hand-curated config).
 ## LRN-115 — Analyzer Edit/Write grants are not dead capability: they write the report (false-positive)
 - **pattern**: a contract audit flagged seo/geo/validator-analyzer holding `Edit`/`Write` while instructed "do NOT apply any Edit/Write" as a defense-in-depth defect. Verified FALSE: those grants write the agent's own REPORT (`.claude/audits/VALIDATE.md`/`SEO.md`/`GEO.md`). The "never edit" rule targets CODE files (the fix-bundle is applied by the dispatcher) and is instruction-level — identical in the patron. Removing Write would break report generation.
 - **why it matters**: don't "harden" a report-only agent by stripping Write — it needs it for its report. The code/report distinction is instruction-enforced, not tool-enforced, by design.
 - **future application**: before flagging a tool-grant as dead, check whether the agent uses it for its own output artifact (report), not the forbidden target (code).
 - **cousin**: [[BDR-061]] (analyzer bundle→L1 contract), [[LRN-113]].
 ## LRN-116 — A resolved blocker's FIX can be missing from develop even when the entry backfills cleanly
 - **pattern**: backfilling release/1.0.0 memory into develop, BLK-016 (rtk PATH-dead) was marked "resolved" via fix e58037c. Checked before backfilling: e58037c (the `~/.cargo/bin`→`~/.local/bin` bridge in install-plugins.sh) was NOT on develop — develop still installed rtk to a cargo bin dir the tool shell can't see → rtk compression was LIVE-broken on develop (~460K tokens/30d). The registry entry looked safe to copy; the underlying fix wasn't there.
 - **why it matters**: append-only registry backfill is "safe" only for the TEXT; a "resolved" status is a claim about CODE state that must be verified on the target branch, else you assert a resolution that isn't true.
 - **fix**: ported e58037c to develop (13-line idempotent bridge), THEN backfilled BLK-016 resolved. General: before backmerging a resolved blocker, grep the target for the fix's code signature.
 - **future application**: gitflow divergence review — enumerate release-only COMMITS that touch code, not just memory; a feature can be parallel-merged while its RC-branch fix is orphaned.
 - **cousin**: [[LRN-036]] (PATH profile drift), [[LRN-047]] (silent degradation).
 ## LRN-117 — A release/develop fork silently orphans functional CODE on develop, not just memory
 - **pattern**: cutting release/1.0.0 and continuing on develop, the RC-branch bug fixes (find-skills drop `095d881`, make-update TTY guard `a1093ca`, rtk update-path version-guard `4c5e862`, rtk install bridge `e58037c`, SC1091 lint `e65796f`) landed ONLY on release. They were live-broken on develop for the whole fork duration (rtk compression dead, `make update` dies non-interactively). The review's memory back-merge caught the registry gaps and one code fix (rtk bridge); a full back-merge found ~5 more functional commits.
 - **why it hides**: registry-sequence gaps (missing LRN/BLK/EVAL ids) are easy to detect; orphaned CODE has no sequence to check. A feature can be parallel-merged to both branches while an RC-branch fix commit is never back-merged, and nothing flags it.
 - **fix**: at release-finish / in /reconcile, list `develop..release/*` commits touching functional files (exclude merges, `.claude/**`, version.txt/CHANGELOG) and present them for back-merge review. Advisory, NOT a hard make-test gate — cherry-picks land with new SHAs so the source commit stays in the range; automatic "already-ported?" equivalence is unreliable and would false-positive. Backlogged.
 - **future application**: any long-lived fork (release/*, long feature) — audit CODE divergence, not just declared/registry state ([[LRN-034]] narrated ≠ ground truth, applied to branches).
 - **cousin**: [[LRN-116]] (a resolved blocker's fix can be missing from develop), [[BDR-054]] (supersession-trace discipline).
 ## LRN-118 — Gitflow-conformity audit: "commits-code" vs "applies-but-defers-commit" is the line that sorts real findings from false positives
 - **pattern**: audited 52 units (33 skills + 19 agents) for gitflow conformity. Raw git-signal grep over-flags: `git add -A`, `gitflow finish`, `--no-verify` mostly appear inside PROHIBITION tables ("never …"), not usages — reading context killed every one (harden/web-validate `--no-verify` = bans; capitalize `git add -A` = ban; tour `gitflow finish` ×3 = red-flags). The decisive discriminator was NOT "does it write code?" but "does it autonomously `git commit`/`push`?": seo/geo/harden/web-validate/code-clean/refactor/doc all EDIT code/public-doc yet defer the commit to the human (or have NO `git commit` path at all) → safe by construction, gitflow layer N/A. Only 2 units both wrote AND committed without a branch precondition: commit-change (commits code, no aiguillage) and client-handover (autonomous `git push`). 0 MERGES-ALONE, 0 BYPASSES-HOOK.
 - **why it matters**: a conformity audit that classifies on "writes code" drowns in false positives; classify on "reaches an autonomous commit/push" and the surface collapses to the few units that can actually corrupt a branch. Thin-dispatcher skills (20-line SKILL.md → agent + commit lib) must be judged as skill+agent+lib triples — the discipline lives in the agent/lib (e.g. /doc's gitflow layer is in doc-syncer + doc-commit.sh, not SKILL.md).
 - **the net**: empirically the per-repo pre-commit hook BLOCKS a non-`.claude/` code commit on main/develop (exit 1), exempts `.claude/**`, allows working branches; `--no-verify` bypasses it client-side → Gitea server-side branch protection is the real backstop. So the 2 findings fail LOUD (hook), never corrupt develop — remediation = make them branch cleanly first (aiguillage / GO-gated push), not incident-urgent.
 - **fix applied**: commit-change got Phase 0 = the shared `gitflow-aiguillage.md` (TYPE=chore, branch on protected base, no-op on working) + report-only fallback; client-handover push gated behind explicit-GO AskUserQuestion + report-only fallback. Dry-runs proved BOTH sides of each fallback (branch-taken AND not-taken), not just the happy path.
 - **future application**: any fleet/skill conformity audit — (1) triage by "autonomous commit/push reached?", not "file written?"; (2) read every git-signal in context (prohibition vs usage); (3) test the deterministic backstop empirically before trusting it; (4) verify a referenced lib exists + its contract matches BEFORE copying it (phantom-reference guard); (5) dry-run both branches of every fallback.
 - **cousin**: [[LRN-117]] (orphaned CODE has no sequence to check), [[LRN-034]] (narrated ≠ ground truth), [[BDR-061]] (report-only agent tool-grants).
 ## LRN-119 — Fail-open engine contract for optional external data (real-if-connected, else graceful)
 - **pattern**: `lib/seo-data/fetch.sh` = one entrypoint; every subcmd ALWAYS emits JSON on stdout, exit 0 on ok/degraded, exit 2 on bad-usage, NEVER empty stdout, NEVER prints a secret. Third-party imports (google-auth, requests) function-local (lazy) so stdlib-only paths — mock (`SEO_DATA_MOCK_DIR`), degrade (no key/no account/revoked token), offline tests — run with no venv. Missing creds → `{"status":"degraded","reason":...}` and the caller (`/seo` analyzer) falls back to anonymous PageSpeed; audit NEVER fails on absent data. Both Python `_cli` wrapped try/except: SystemExit→bad_usage JSON+reraise, Exception→degraded JSON (corrupt store never leaks stack/path). 3rd status value `error` on exit-2 only.
 - **why it matters**: an optional-data integration must be invisible when unconfigured. Fail-CLOSED (crash/empty/nonzero) breaks every audit for users who never connect GSC. Fail-open + lazy-import keeps the 49 tests network-free and makes degrade a first-class tested branch, not an afterthought.
 - **future application**: any "use real data if credentials present, else degrade" seam — put the contract in the shell entrypoint (always-JSON / exit-code discipline), lazy-import the SDK, make degrade a returned status not an exception, test degrade+mock stdlib-only, redact secrets at the boundary (list omits token, `exec 2>/dev/null` unless debug).
 - **cousin**: [[BDR-063]] (the token store this fronts), [[LRN-120]] (SDD base gotcha, same build).
 ## LRN-120 — SDD final-review base = `git merge-base`, NOT the ledger's recorded BASE
 - **pattern**: subagent-driven-development ledger recorded `BASE: 24b47ce` — but that was IMPLEMENTATION start (after spec+plan commits), not the branch point from develop. `git merge-base develop HEAD` = `d3e644d` (real fork). Final whole-branch review diffed against recorded BASE = 881 ins / 59 del; against true merge-base = 2163 ins / 7 del — the recorded-base diff MISLEADING (netting against a divergent line → phantom deletions). Per-task reviews unaffected (each used the correct prior feature commit).
 - **why it matters**: the final review is the last gate before merge; a wrong base hides real changes or invents fake ones. The ledger BASE is a task resume-map, not a merge-delta anchor.
 - **future application**: for ANY whole-branch/final review, derive base from `git merge-base <target> HEAD`, never a stored/remembered SHA. Sanity-check: does `git log BASE..HEAD` list ONLY this branch's commits, nothing foreign? Diff-stats differ between candidate bases → recorded one is stale, trust merge-base.
 - **cousin**: [[LRN-119]] (same GSC+CrUX build); SDD skill's own "never HEAD~1" warning (same base-selection bug class).
 ## LRN-121 — Shell allowlist validation: `grep -Eq` is fragile; use a whole-string POSIX `case`
 - **pattern**: guarding a user-supplied label to shell-safe ASCII with `printf '%s' "$v" | grep -Eq '^[A-Za-z0-9._-]+$'` failed 3 adversarial gate passes in a row: (1) command-injection framing (label interpolated into an agent-composed Bash line); (2) parser differential — the guard pre-scanned argv for the literal token `--label` while the downstream `argparse` ALSO accepts `--label=v` and abbreviations (`--labe`, `allow_abbrev=True`), so those forms reached the parser unchecked; (3) `grep -q` matches PER LINE, so a label with an embedded newline (`ok\nrm -rf`) passes because its FIRST line matches. Fix = replace the whole mechanism, don't patch again: `_label_safe() ( LC_ALL=C; case "$1" in ''|[!A-Za-z0-9]*|*[!A-Za-z0-9._-]*) exit 1;; esac )` — POSIX `case`, whole-string, C-locale subshell. No grep (no per-line), no regex, no second grammar to differ from; a newline is just a non-allowed byte caught by `*[!...]*`; `LC_ALL=C` stops UTF-8 collation widening `[A-Za-z0-9]` to homoglyphs (U+FF11, Kelvin U+212A).
 - **why it matters**: three distinct bypasses of the SAME guard = the approach was wrong, not each patch. `grep`'s line-orientation + locale-sensitive ranges, plus argv-prescan-vs-real-parser grammar drift, are the three classic ways an allowlist "passes" a string it shouldn't. Whole-string `case` in C locale closes all three at once. These were defense-in-depth (downstream used `"$2"`/`"$@"`/JSON-key, never `sh -c`/`eval` → not exploitable in the real exec chain) — but the backstop still took a categorical rewrite, and 3 security-gate BLOCKs to get there.
 - **future application**: validate shell input WHOLE-STRING (`case` or bash `[[ =~ ]]`), never `grep -q` (per-line). Set `LC_ALL=C` for byte-wise ranges. A guard that pre-scans argv must be STRICTER than the downstream parser (reject `=`-joined/abbrev) or validate post-parse against the value the parser settled on. When a fix is bypassed twice → STOP patching, replace the mechanism (re-plan, not whack-a-mole).
 - **cousin**: [[LRN-119]] (fail-open engine this hardens), [[BDR-063]] (token store whose labels these guard), [[LRN-045]] (renaming-command leak-guard regexes — same charset-guard family).
 ---
 ## LRN-122 — git mv + recreate source path in same commit = rename detection dead
 - **pattern**: rename file + create NEW file at old path in ONE commit → git never pairs the rename (source path never vanishes — index sees modify(old)+add(new)). `git log --follow` chain lost; deterministic, persists forever. Fix: TWO commits — pure rename first (paired at R~98%), recreation second. Found live: Task-2 implementer hit the plan's own "2 hunks" STOP gate, diagnosed root cause, escalated instead of patching around it.
 - **why**: contract criterion (history preserved) outranks plan packaging ("atomic commit"). Commit-level atomicity ≠ deploy-level atomicity — deployed symlink already fixed by running link.sh, independent of commit split.
 - **future application**: ANY rename-and-replace-in-place (config forks, template splits, versioned API files). Old path must be re-occupied → split commits; verify `git diff -M --stat parent` shows the `=>` rename line before proceeding.
 - **cousin**: [[BDR-064]] (the split this served), [[LRN-120]] (review-base hygiene — same git-range-semantics family).
 ---
 ## LRN-123 — "resolves inside repo" symlink check green-lights stale link once old path re-occupied
 - **pattern**: doctor's check_symlink asserted only `readlink -f` lands inside `$REPO` — safe while ONE candidate file existed. Rename freed old path for a NEW file → stale post-pull link (`~/.claude/CLAUDE.md` → `$REPO/CLAUDE.md`) resolves to project file (inside repo) → check PASS, global doctrine silently absent every session. Fix: assert EXACT readlink target (`$REPO/CLAUDE.global.md`), warn + remedy cmd (`run: bash link.sh`). Caught by final whole-branch review (fresh most-capable model), not by any earlier gate.
 - **why**: containment predicates (inside-dir, prefix-match) silently weaken the moment layout gains a second valid-looking target; exactness costs nothing.
 - **future application**: symlink/path health checks → assert exact expected target whenever the old target path can be re-occupied; test all three states (correct / stale / missing).
 - **cousin**: [[BDR-064]], [[LRN-104]] (hook message = test contract — same guard-must-follow-the-change family).
 ---
 ## LRN-124 — derived scan artifacts don't belong in git; a tooling hint saying "safe to commit" manufactures the leak
 - **pattern**: gitleaks reports committed to repo (17bdd08) even with `--redact` = a MAP — secret type + file + line for anyone with repo access. Root cause traced: `make scan-secrets` echoed "already redacted — safe to inspect/commit" → the hint was obeyed. Fix: `git rm --cached` (gitignore has no effect on tracked files), reword hint to "gitignored — keep local, do NOT commit". Companion: user added `.audit/` gitignore rule (5842119) for the untracked report/patch siblings.
 - **why**: redaction removes VALUES, not INTELLIGENCE. And tool output is instruction — a hint that says "safe to commit" will eventually be obeyed by a human or an agent.
 - **future application**: derived security artifacts (scan reports, triage JSONs, audit findings) stay local/ignored; only the allowlist CONFIG (reviewable rules) is committed. When auditing tooling, grep its user-facing hints for wording that invites committing outputs.
 - **cousin**: [[BDR-057]] (secrets by reference, redact at capture), [[BDR-065]] (transient planning artifacts — same "process artifacts ≠ repo content" family), [[LRN-103]] (re-probe before acting).
 ## LRN-125 — don't make an agent dual-use across model tiers; route the audit consumer to a big-model agent, not the sonnet executor
 - **pattern**: splitting `code-cleaner` into a sonnet PHASE-2 executor broke its OTHER consumers (onboard STEP 6, tour Phase B) which dispatched it read-only AUDIT-only. Reflex "keep it dual-use (audit-only OR execute)" would have run an AUDIT on the sonnet-pinned executor = silent violation of the audit=big-model principle. Fix: reroute the audit consumers to a big-model agent (general-purpose/analyzer, inherits session), never the sonnet executor.
 - **why**: a dual-use agent inherits ONE pinned model. If its two uses sit on different tiers (audit=big, execution=sonnet), the pin silently mis-tiers one of them. hotfixer dual-use is fine because BOTH its uses are execution (same tier); code-cleaner's would have straddled tiers.
 - **future application**: before making an agent dual-use, check both consumers are on the SAME tier. Audit/reflection consumer + execution consumer → split the routing (audit → big-model agent, execution → sonnet executor); never overload one pinned agent. Distinct from [[LRN-113]] (sweep ALL consumers on a pattern fix) — this is WHICH agent a consumer routes to, not whether you found them all.
 - **cousin**: [[BDR-066]] (model routing: reflection/audit big, execution sonnet), [[LRN-113]] (consumer-staleness sweep on a pattern fix).
 ## LRN-126 — splitting a monolith agent severs every IMPLICIT data path; forward each consumed field through the handoff contract
 - **pattern**: wave-4 redaction-only split (client-handover-writer monolith → reflection-parent + sonnet doc-writer child) silently dropped 2 inputs the extracted STEPs consumed. `DEPLOY_HINTS` (detected in parent STEP 2, consumed by child STEP 14) + `--skip-seo` flag (parsed from `$ARGUMENTS`, gated child STEP 13) worked in the monolith by shared scope; after the split they were dead — never added to the PACKAGE. Child rendered a §8 without platform tailoring; `--skip-seo` became a silent no-op. Caught only by the opus whole-branch review, not the census.
 - **why**: in a monolith, `$ARGUMENTS`, detected vars, and STEP-N side-outputs are all in one scope — a later STEP reads them for free. The split turns that free read into a data path that MUST cross the parent→child contract explicitly. Every implicit read becomes a severed wire unless forwarded.
 - **future application**: when splitting an agent, enumerate EVERY field the child reads (grep child for its input vocabulary — `PACKAGE.`, bare var names, `$ARGUMENTS` flags) and diff against what the parent SETS before dispatch. Any child-consumed field the parent never populates = severed path = renders a hole or a silent no-op. A census that checks shape (model pin, gate-free) will NOT catch this — needs a data-flow read.
 - **cousin**: [[LRN-125]] (route consumer to right tier on a split), [[BDR-066]] (reflection/execution split), [[LRN-113]] (sweep ALL consumers). Distinct: 113/125 = WHICH agent/tier a consumer routes to; this = WHICH fields must cross the contract.
 ## LRN-127 — SDD implementers must not run destructive git ops on files outside their task scope
 - **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.
@@ -1,5 +1,401 @@
 # TODO
 ## 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
 the ronde surfaced. Branch off develop, unmerged — human gate.
 - [x] F1 (real bug) feater applier carve-out — /seo,/geo dispatch feater as
      L1 applier with NO CONTRACT, but feater mandates "read CONTRACT FIRST"
      (hotfixer has the carve-out, feater didn't) → mirror hotfixer.md:16-45.
 - [x] F5 (guard) census: lock the ABSENT model: pin on seo/geo/validator-
      analyzer + client-handover-writer (stray sonnet pin would silently
      downgrade a live audit, uncaught).
 - [x] F4 (cleanup) drop interviewer's inert `model: sonnet` (reflection role,
      inline-loaded by gated init-project) + census guard.
 - [x] F2 (tier) /refactor inline-load → true-dispatch refactorer (sonnet pin
      was inert). refactorer verified dispatch-safe (no Ask/Agent, input=target).
 - [x] F3 (gate) /analyze add MODEL GATE (inline-loads the analyzer reflection
      agent, was ungated + undocumented). census: +analyze gated, +refactor excluded.
 - [x] verify: census 57/0, shellcheck clean (my files), full suite green; NO merge.
 ## 2026-07-15 — model routing (feature/model-routing)
 Spec + plan in docs/superpowers/ (transient, BDR-065). BDR-066. Branch
 unmerged — human gate.
 - [x] gate lib/model-check.sh + lib/model-gate.md (flip-tested) wired ×12
 - [x] pins: hotfixer/feater sonnet, analyzer un-pinned; SDD model:"sonnet";
      web-validate → hotfixer L1; census guard model-routing.test.sh
 - [x] /feat re-arch: reflection inline → feater sonnet executor (partial
      supersede BDR-050)
 - [x] WAVE 2 (user directive): doc/status dispatch (sonnet/haiku pins
      effective); /hotfix split like /feat (joins gated 12→13, hotfixer
      dual-use executor); /commit-change → sonnet commit-changer
      (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
      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.
 - [x] Explore agent: kept as built-in (inherits session = opus/fable). User
      call — search feeds reflection, silent-incompleteness risk → deserves the
      big model. Custom sonnet Explore.md created then reverted (built-in already
      inherits + no owned prompt).
 - [x] WAVE 3 (user directive): /bugfix split + /code-clean split → reflection
      inline (behind existing gate), execution → sonnet executors. bugfixer =
      pure fix+regression exec (BUGFIX-EXEC REPORT, no Agent/AskUserQuestion);
      code-cleaner = PHASE-2 exec (refactor now runs on sonnet — inline-load pin
      was inert). Both skills STAY gated. census wave-3 + loops-light repoint
      (guarded). Supersedes BDR-050 bugfix carve-out.
 - [x] WAVE 4 — client-handover (branch feature/client-handover-dispatch, off
      develop). Shape FLIPPED to REDACTION-ONLY (full read: nested audits must
      run big either way since /seo,/harden,/web-validate are gated → whole-writer
      buys ~0 extra sonnet work for ~7 extra gate-yields). Design: parent
      (client-handover-writer, inline=big) keeps STEP 1-8 pipeline + ALL gates
      native + builds a PACKAGE; new sonnet handover-doc-writer does STEP 9-16
      pure write+render, gate-free. Tasks 19-22 in plan. + MODEL GATE on skill.
 ## 2026-07-08 — full back-merge release/1.0.0→develop (chore/backmerge-release-full)
 Genèse : la revue avait porté ~5/19 commits ; back-merge complet demandé. Cherry-pick par
 catégorie, 1 commit atomique/item, make test après chaque code. Branche non mergée (gate humain).
 - [x] A CODE (5 cherry-picks, make test GREEN chacun) : 095d881 drop find-skills (5a1fff5),
      a1093ca TTY-guard make-update (ce07e55, prouvé EOF exit1→exit0), 4c5e862 rtk version-guard
      (3049250, complète le pont e58037c déjà porté — fichiers/concerns distincts), c76479f
      design-motion sync (82ce02c), e65796f SC1091 lint (fcdb157, shellcheck 0 SC1091).
 - [x] B JOURNAL : cherry-pick direct conflicte (tails journal divergents) → STOP honoré,
      fallback note consolidée sous journal 2026-07-08. TODO /deploy ca9fa8f skip (release-specific).
 - [x] C DÉCISION/DOUBLON tous skip vérifiés : 93e43c0 attribution + ae8ad86 model (opus[1m]=Opus4.8)
      déjà sur develop ; a623514/74d3804/2b4e740 registres déjà backfillés (run revue) ;
      188a9a7 docs → backlog /doc ci-dessous.
 - [x] D fork version 1eb5b08/eb93050 intouchés — version.txt reste 4.0.0.
 - [x] GATE FINAL : 23/23 commits release-only classifiés, 0 code orphelin, 0 entrée registre
      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 /
      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/*`
      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
      (faux positifs). Cible : étape release-finish ou /reconcile, pas run-review-guards.
 ## 2026-07-08 — review remediation (chore/review-remediation)
 Genèse : `.audit/review-release-1.0.0.md` (revue adversariale des 9 jobs). GO user,
 ordre imposé. Déviation justifiée : 1 branche (pas 1/EP) car le gate fil-rouge (step 6)
 grep toute la surface et n'est vert qu'avec A1/A4/A5 déjà appliqués. Commits atomiques,
 branche non mergée (gate humain). EP-A3/A6 = décisions user tranchées (combler / option b).
 - [x] EP-A1 (BLOQUANT) trailer bugfixer/feater/hotfixer (56018df) + grep étendu = 0 autre
 - [x] EP-A2 (P0) hook réinstallé gitleaks (d4526e6) + 3 gates verts + root-cause (générateur édité, jamais réinstallé)
 - [x] EP-A4 quote YAML seo-analyzer:3 + security-auditor:3 (5a0fc16) + gate yaml.safe_load tous agents
 - [x] EP-A5 geo own-policy PERMISSIVE (f0111e1), user-approved, grep==0
 - [x] EP-A8 smoke /seo+/geo réel PROUVÉ — AUTO llms.txt + sitemap.xml atterrissent sur disque (no-op infirmé)
 - [x] FIL-ROUGE run-review-guards.sh 5 gardes (4e83f39), user-approved, à dents
 - [x] EP-A3 backfill LRN-098/101 (7cd82cf/a01250b) + EVAL-015 (38cc821) + BLK-016 (8e9ff33) + PORT rtk e58037c (416b68f) car fix absent+bug live sur develop
 - [x] EP-A6 (option b) seuil 280→320 + BDR-062 (1be9036)
 - [x] EP-A7 documentaire + M5 → EVAL-022 (capitalize cc4f161)
 - [x] Capitalize LRN-113/114/115/116 + BDR-062 + EVAL-021/022 + journal (cc4f161)
 - [x] GATE FINAL : make test GREEN (exit 0) + A2 secret BLOCKED (gitleaks) + A8 AUTO landed + review-guards 5/0
 - Branche chore/review-remediation NON mergée (gate humain). Résidu noté : e65796f (SC1091 lint) non back-mergé, hors scope.
 ## 2026-07-08 — job9 sub-agent architecture corrections (chore/job9-agents)
 Genèse : `.audit/job9-report.md` (agents/*.md frontmatter+body, verify-loop,
 dispatch graph, read-only). Premise correction confirmed CC v2.1.203 : nesting
 SUPPORTED since v2.1.172, cap 5, `Agent` tool required in `tools:` to nest.
 User decision: **path b (version-robust)** for the version-floor. One commit/item.
 PART 1 — MISROUTED (trivial frontmatter):
 - [x] A — commit-changer: drop unused `Agent` from tools (0ede52c)
 - [x] B — verifier: pin `model: sonnet` (ea6c126)
 - [x] C — security-auditor: pin `model: sonnet` (1c270e6)
 - [x] D — plugin-advisor: `haiku` → `sonnet` (5ab6c21)
 - [x] GATE P1 — smoke green: verifier CONFORME, sec-auditor BLOCK(2), advisor
      ACTION REQUIRED; verdict grammar intact, mode honored. No revert.
 PART 2 — VERSION-FLOOR (path b) — CONTRACT APPROVED, DONE:
 - [x] 5 — seo+geo analyzers → fix-bundle→L1 (a5a7b54/6df42e4); /seo STEP 1.5
      (c498b93), /geo dispatch+apply (70fb3b4), dispatcher tier-tolerance
      (212f9aa); /harden already path-b (untouched), /onboard audit-only
      (untouched). GATE PASSED: make test green + 4 smokes (A bundle-no-edit,
      B AUTO lands on disk no-confirm, C GATED withheld→applied post-accord,
      D onboard report-only zero-fix).
 - [x] 6 — BDR-060 orchestration floor v2.1.172 supersedes implicit v2.1.83
      premise (BDR-004:133 kept — auto-mode floor, append-only + factually
      correct). BDR-061 path-b doctrine.
 PART 3 — IMPLICIT-HANDOFF (tight scope, 2 sites) — DONE:
 - [x] 7 — H2 INLINE-LOAD verb @ code-cleaner + scaffolder (87d63bf/af9656f),
      drop unused Agent from code-cleaner
 - [x] 8 — H1 code-cleaner→refactorer named artifact .claude/audits/CODE-CLEAN-SCOPE.md
 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
      agent/template carries a banned attribution trailer (Co-Authored-By/
      Claude-Session/--trailer)
 Branch unmerged, human gate.
 ## 2026-07-07 — job8 third-party security hardening (chore/job8-hardening)
 Genèse : `.audit/job8-report.md` (magic MCP/plugins/gstack/external skills/trust
 chain, read-only). A/B/C/D exécutés (3 commits), branche non mergée, gate humain.
 - [x] A — `permissions.ask` += 4 `mcp__magic__*` tools, allow reste vide (BDR-059)
 - [x] B — component_builder couvert par A ; risque documenté README + LRN-110
 - [x] C — darwin-skill réinstallé pinné (tree complet, HEAD détaché SHA
      7c7b790), git-commit large-scope documenté comme risque accepté (pas de
      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
      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)
 ## 2026-07-07 — job7 secrets: triage backstops (chore/job7-secrets)
 Genèse : `.audit/job7/ALL-REDACTED.json` (triage secrets multi-repo + ~/.claude).
 GITEA_TOKEN déjà rotaté (transcript 960bd2cf). MAGIC rotation prévue après (A).
 Fixtures git-game #5/#6 confirmées synthétiques (test-secret-*). Règle : jamais
 manipuler une valeur de secret — edits sur les mécanismes seulement.
 - [x] A.1 Provenance MAGIC_API_KEY dans `~/.claude.json` : confirmée —
      seul writer = `lib/toggle-external.sh:191` (`claude mcp add magic --scope
      user --env API_KEY="$MAGIC_API_KEY"`), appelé par `install-plugins.sh`
      (jamais un `claude mcp add` direct). Aucun autre writer (grep repo-wide).
 - [x] A.2 Doc Claude Code (agent claude-code-guide) : `${VAR}` supporté dans
      `env`/`command`/`args`/`url`/`headers` de mcpServers, y compris scope
      user (`~/.claude.json`). Pas de `envFile`, pas de flag `mcp add` pour une
      référence — édition manuelle requise. Voie SUPPORTÉE retenue.
      Décision utilisateur : wiring `MAGIC_API_KEY` → wrapper `claude()` scopé
      dans `~/.bashrc` (source `.env` en subshell, jamais exporté globalement)
      plutôt qu'un export global (surface minimale, cohérent BDR-026).
  - [x] `~/.bashrc` : fonction `claude()` wrapper (subshell source ~/.claude/.env,
        exec — vérifié : la var n'atteint QUE le subshell/exec, jamais le shell
        parent). Hors repo (dotfile perso).
  - [x] `~/.claude.json` mcpServers.magic.env.API_KEY → `"${MAGIC_API_KEY}"`
        (diff keys-only montré avant écriture ; jq surgical edit, jamais Read
        direct — la valeur n'a jamais traversé mon contexte). Backup fait
        pendant l'édition supprimé aussitôt vérifié (aurait été un 6e leak).
  - [x] `lib/toggle-external.sh:191-192` — `--env 'API_KEY=${MAGIC_API_KEY}'`
        (référence littérale, single-quoted). `claude mcp add` direct au flag
        bloqué par le classifieur auto-mode (self-modification non sollicitée,
        respecté) — non testé live ; `claude mcp list` confirme la syntaxe
        est bien reconnue ("Missing environment variables: MAGIC_API_KEY" —
        attendu, cette session a démarré avant le wrapper bashrc).
  - [x] Doc README : section "Adding an MCP server that needs a secret" +
        piège `--env` + pattern wrapper à copier
  - [x] Vérif manuelle : `claude mcp list` (read-only) — magic reconnaît
        `${MAGIC_API_KEY}`, encore connecté (session pré-existante) ; nécessite
        un restart terminal (source ~/.bashrc) + Claude Code pour confirmer
        end-to-end — **résiduel, à faire par l'utilisateur**
 - [x] A.3 Scrub backups `.claude.json.backup.*` — les 5 originaux (78af0e36 @
      job7 triage) déjà auto-rotés (ring-buffer natif) ; des 5 COURANTS, 2
      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] 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)
      [A-Za-z_]*)=.*/\1=REDACTED/'`. `env VAR=x cmd` intact. Compound bail
      (`;`/`&`/`||`) — jamais de pipe attaché au mauvais segment.
  - [x] `lib/tests/rtk-rewrite.test.sh` — 3 cas + garde compound
  - [x] `make test` vert (96/96 gitflow-test + suite complète)
 - [x] C. Backstop gitleaks (8.30.1 confirmé installé — `protect` non listé
      dans `--help` mais fonctionne encore ; `gitleaks git --staged` =
      sous-commande documentée retenue à la place)
  - [x] `.gitleaks.toml` racine — allowlist 3 classes job7 (vérifiées
        empiriquement contre les vrais fichiers : marketplace.json sha
        40-hex, ws-protocol nonce, test-secret-[0-9-]+) + 4e entrée
        `(^|/)\.env$` (pas un faux positif — c'est le vault canonique
        BDR-026 ; exclu du bruit, pas de la détection)
  - [x] pre-commit gitflow (`lib/gitflow.sh` `_gitflow_emit_pre_commit`) —
        `gitleaks git --staged` après guard root/merge, non-bloquant si absent
  - [x] `lib/gitflow-test.sh` T16 — faux secret (AKIA random) sur feature
        branch → bloqué ; commit propre passe ; PATH sans gitleaks → warn
        + pass. 96/96 vert.
  - [x] `make scan-secrets` — repo (git history) + dir ~/.claude, redacted
        JSON → `.audit/` (`--redact` vérifié : Match/Secret redacted dans
        le report, pas juste les logs). Repo : 0 (attendu). ~/.claude : 18
        hits restants, 8 fichiers — voir D (5 déjà dans le triage job7,
        3 NOUVEAUX non couverts par la spec initiale, à trancher)
 - [x] D. Purge (GO explicite par item) — état réel après `make scan-secrets` :
  - [x] transcript 960bd2cf…jsonl (generic-api-key, GITEA déjà rotaté) — GO
        utilisateur → rm fait
  - [x] `ide/27929.lock` — déjà rotée toute seule (fichier absent, session
        finie). REMPLACÉE par `ide/20429.lock` (NOUVEAU, session active en
        cours) — NE PAS rm (verrou live) ; candidat allowlist de classe
        (`ide/*.lock` structurel, pas un secret) si le pattern se confirme
  - [x] `cleanupPeriodDays` — champ confirmé exact (agent claude-code-guide,
        code.claude.com/docs/en/settings.md) : défaut 30, min 1, scope doc
        = "session files" (transcripts + orphaned subagent worktrees) —
        PAS explicitement backups/file-history/paste-cache (gap doc, donc
        ne remplace pas les scrubs manuels A.3/D). Diff montré, confirmé
        via AskUserQuestion (1er essai bloqué par le classifieur auto-mode :
        diff affiché en texte ne vaut pas confirmation explicite — correct)
        → `settings.json` 30→7 appliqué.
  - [x] **NOUVEAU (hors spec initiale, découvert par `make scan-secrets`)** :
        `paste-cache/7d48f52c7499c1a7.txt` (sourcegraph-access-token, 2) —
        GO utilisateur ("Claude rm maintenant") → rm fait, jamais lu.
        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).
  - [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
      é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,
      non tranché) reste — résiduel connu, pas un échec du job.
 ## 2026-07-05 — /deploy UX patch (feature/deploy-next-style)
 Feedback user au 1er run réel (bchanot-cv, [[EVAL-016]]) : NEXT.sh une commande
 par ligne (style session — ssh ouvre la box, la suite s'exécute dessus, local =
 "(from your machine)") + hand-back AFFICHE la checklist inline (aussi aux
 re-hand-back). Step = bloc (header + lignes jusqu'à ligne vide), @delta
 gouverne le bloc entier.
 - [x] skills/deploy/SKILL.md — grammaire bloc-étape + shape rule + print inline
 - [x] templates/deploy/PROCEDURE.md — restylé session
 - [x] bchanot-cv runbook restylé, committé, pushé (bd7f6e4, develop sync)
 - [x] settings.json +inputNeededNotifEnabled (layout committé inchangé)
 - [x] Capitalize EVAL-016 + journal
 - [x] Re-dogfood run 2 (résidus bchanot-cv) : le print inline AVANT
      AskUserQuestion ne s'affichait PAS → leçon [[LRN-102]] (texte avant un
      tool call peut ne jamais rendre ; le dernier texte du tour est le seul
      affichage garanti)
 - [x] PASS 2 (feature/deploy-inline-checklist) : checklist DISPLAY-ONLY —
      plus de fichier NEXT.sh du tout (jetable, PENDING+runbook régénèrent
      partout) ; hand-back TERMINE le tour par la checklist, aucun tool call
      après ; resume à froid = régénère + ré-affiche. Skill+template+CHANGELOG.
 - [x] Re-dogfood pass 2 VALIDÉ (deploy run 2, b24c58b marqué 2026-07-05-2) :
      checklist copiée depuis la conversation, deploy OK, CSP hash live sans
      unsafe-inline. Resume à froid + STEP 4 (learn) toujours vierges
 ## 2026-07-05 — impeccable install chain (feature/impeccable-install)
 Décision (user a délégué) : COMPLÉMENTAIRES → les deux. frontend-design garde
 la direction esthétique au build ; impeccable (pbakaus, 43.6k⭐, Apache-2.0,
 actif) apporte l'UNIQUE manquant : 45 règles déterministes anti-slop (CLI
 `impeccable detect`, exit 0/2, --json — le semgrep du design, doctrine
 backstop-déterministe) + 23 verbes sous UN skill (/impeccable) + contexte
 design persistant (DESIGN.md/PRODUCT.md). Faits vérifiés : npm CLI 3.2.0
 (skill dist = track séparé), `skills install -y --providers=claude
 --scope=project --no-hooks`, **Node ≥ 24 requis (hôte = 22.22)** → step
 fail-soft + décision bump Node à l'user. Classifier a bloqué npx (code tiers)
 → dogfood via `make plugin` côté user.
 Pattern : ctx7/machine-owned (skills-external/impeccable gitignoré, synced
 par installeur, symlinké par link.sh EXTERNAL_SKILLS, profils type external).
 PAS en GATE-BLOCK design.profile tant que Node<24 + pas dogfoodé.
 - [x] plugins.lock.json — entry impeccable pin 3.2.0
 - [x] install-plugins.sh — Step 8d staged npx install → skills-external
 - [x] update-all.sh — step miroir pin-honored (Node<24 → skip, dist gardée)
 - [x] link.sh — EXTERNAL_SKILLS += impeccable
 - [x] .gitignore — skills/impeccable + skills-external/impeccable/
 - [x] profils design/web/web-full/full — impeccable external (show design →
      « impeccable missing » = statut honnête pré-install)
 - [x] plugin-advisor.md + CLAUDE.md Design work + lib/design-gate.md
 - [x] README table + CHANGELOG Unreleased
 - [x] Verify — bash -n ×3 OK, shellcheck clean (SC1091 info only), lock JSON
      valide, profile parse OK. Dogfood DIFFÉRÉ : classifier bloque npx code
      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
      promotion après dogfood ; dogfood réel = prochain `make plugin`
 ## 2026-07-04 — skill /tour (tir groupé multi-projets, feature/tour-skill)
 Goal: 1 orchestrateur = clean-code + sécurité (security-auditor/semgrep [+cso si
 gstack ON]) + reconcile + doc, mode auto, sur 1..N projets. Boucle de convergence
 (fixes peuvent invalider l'audit précédent) BORNÉE 3× (LRN-083). Build via
 superpowers:writing-skills (TDD, pattern audit-delta/reconcile) + guidance
 skill-creator (structure, description trigger-pushy).
 Design verrouillé :
 - auto = fixes committés sur `chore/tour-<date>` par repo (gitflow lib), JAMAIS
  finish/merge (signal humain only). Tree sale ou pas de develop → report-only.
 - ordre par repo : sécurité → clean → re-verify (checks projet, fail=revert
  fail-closed) → reconcile (REPORT-ONLY, jamais d'auto-coche TODO) → doc
  (mode silencieux doc-syncer) → re-audit convergence.
 - convergence = 1 passe complète à zéro finding nouveau + checks verts ;
  sinon re-boucle, max 3 itérations, résidus rapportés honnêtement.
 - rapport `.claude/audits/TOUR.md` par repo + synthèse inline multi-repos.
 - registres : offre capitalize gatée en fin, jamais silencieux.
 - [x] RED : fixture repo → baseline SANS skill. 6 gaps : TODO cible ré-écrit
      silencieusement ; registres écrits de façon autonome ; sécu = grep ad-hoc
      sans semgrep ; zéro rapport persistant ; scope creep (.gitignore +
      registres bootstrap) ; boucle sans borne déclarée. (Bien fait : branche
      gitflow via lib, pas de merge, commits atomiques, convergence passe 2.)
 - [x] GREEN : skills/tour/SKILL.md — run avec skill sur fixture-green,
      6/6 gaps fermés VÉRIFIÉS sur disque (TODO zero-diff, 0 registre,
      semgrep chaque itération, TOUR.md committé 18 findings, 0 scope
      creep, 3 it. bornées convergées, chore branch non mergée)
 - [x] REFACTOR : 2 trous du GREEN patchés (scratch semgrep non trackés →
      auto-blocage du prochain run, STEP 3.2 cleanup ; fix sécu cassant
      non signalé → tag BREAKING structurel dans template). Additions
      template-structurelles NON re-testées par un 3e run complet (coût) —
      re-test au premier usage réel.
 - [x] Routage CLAUDE.md (ligne « Grouped all-axes sweep → tour »)
 - [x] Commit branche + capitalize (BDR-052, LRN-099/100, EVAL-014, journal)
 - [x] GO user 2026-07-05 : merge develop + release/1.0.0 ; settings.json
      restauré (Opus 4.8 1M défaut, backstop attribution conservé)
 ## 2026-07-03 — verify loops + semgrep gate + contract (chantier orchestrateurs)
 Archi validée au gate (session 2026-07-03). Cible : contract sur DISQUE dès
 création (fichier de run, pattern DIAGNOSIS) + verifier frais (verdict structuré
 CONFORME/écarts, preuve-qu'il-a-regardé LRN-048, 2 échecs structurels = escalade
 humaine — verifier muet ≠ PASS) + gate sécu semgrep (rulesets ÉPINGLÉS
 p/security-audit + p/secrets — pas --config auto, classe LRN-077 ; BLOCK
 HIGH/CRITICAL only, LRN-047) + boucles bornées 3× décidées en boucle principale
 (LRN-083). cso = symlink submodule gstack → non modifiable → greffes locales
 (onboard cso-fallback, audit-delta, agent neuf ; complément semgrep même
 gstack ON). Verdicts user : dev inline conservé feat/bugfix/hotfix (verify+sécu
 = sous-agents frais) ; hotfix garde revert-escalade ; PIN version semgrep dans
 plugins.lock.json (gate bloquante — upgrade silencieux = nouveaux BLOCK sur code
 inchangé ; pattern gsd-pin, saut affiché par update-all).
 LOT 1 — feature/semgrep-install (GO)
 - [x] plugins.lock.json — pin semgrep 1.168.0 (pattern gsd, note gate bloquante)
 - [x] install-plugins.sh STEP 7.5 — pipx pinned, command -v guard + version echo, login guide-only (jamais auto)
 - [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
 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.
 LOT 4 — feature/loops-light : câblage feat/bugfix/hotfix.
 LOT 5 — feature/loops-heavy : câblage ship-feature + init-project + onboard.
 Rien poussé ; gate par lot ; suites après chaque lot.
 ## 2026-07-03 — design-toolchain trigger fix (bugfix/design-toolchain-trigger)
 Root cause (NOT a kill-switch, per user): ed2408e (07-02) dropped ultra-generic
 tokens but left bare tokens common in non-UI talk → ~6× false-fire THIS session
 (design, dashboard via ecc_dashboard.py, component, frontend, theme, transition,
 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
 ## 2026-07-03 — config-protection hook (feature/config-protection-hook)
 Goal: PreToolUse hook blocks Edit/Write to this config's quality-gate files
 (guardrails an agent must not weaken to make an error pass). Adaptation from ECC
 second-look (BDR-047 corrob, Opus 4.8 re-audit) — MY idiom (~15-line bash), NOT
 ECC's Node dispatcher. Extends config's own doctrine ("backstops déterministes
 car l'advisory s'oublie"). Guarded: settings.json (+ .claude/settings*.json),
 lib/gitflow.sh, .githooks/*, doctor.sh, lint configs (preemptive, absent today).
 Bypass: CONFIG_EDIT_OK="reason" (logged). Mid-session env caveat flagged at gate.
 - [x] hooks/config-protection.sh — case-match guarded path, exit 2 else 0; fail-open
 - [x] Guarded: settings.json(+.claude/settings*), lib/gitflow.sh, .githooks/*, doctor.sh, hooks/*.sh (self-guard), lib/tests/* (T6c/LRN-077), lint (preemptive)
 - [x] Bypass: one-shot sentinel .claude/.config-edit-ok (non-empty reason, logged+consumed) — NOT env-var (launch-time env = set-and-forget = garde mort)
 - [x] lib/tests/config-protection.test.sh — block/allow/self-guard/near-miss/fail-open/sentinel-one-shot/empty-refuse (17 checks)
 - [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
 ## 2026-06-23 — install self-sufficient + gstack on-demand par profil
 Goal: `make install`/`make plugin`/`make update` installent TOUT sans étape
 manuelle. Plus le profil-driven gstack on-demand (option 1 user : gstack OFF
@@ -23,9 +419,10 @@ Root causes trouvées (logs install-20260623-181416.log) :
 - [x] Verif — shellcheck/bash -n propres ; migré darwin → $HOME/.agents/skills + `bash link.sh`
      (skills/darwin-skill OK) ; `profile.sh set full` → 0 "missing", 35 gstack on-demand ;
      cycle minimal↔full OK ; git propre (symlinks gstack gitignorés) ; profil full restauré
- [~] Cleanup machine courante : $REPO/.claude/skills/darwin-skill + .agents/skills VIDE
+- [x] Cleanup machine courante : $REPO/.claude/skills/darwin-skill + .agents/skills VIDE
      restent (rm bloqué par garde permission .claude/) → auto-nettoyés au prochain `make plugin`
      [reconcile 2026-06-29 : TOUJOURS présents (fs-vérifié, darwin-skill 116K daté 23/06) — `make plugin` pas rejoué depuis. Reste différé, déclencheur = prochain install.]
      [done 2026-06-30 : `make plugin` rejoué EXIT=0 (npm réparé via corepack, [[BLK-013]]) → Step 8.5 a retiré les deux ; fs-vérifié ABSENTS, vrai skills/ intact (36 entrées). Boucle fermée.]
 - [x] Capitalize — LRN-042 (Bug B CWD-relatif) + BDR-030 (gstack on-demand par profil) + journal 2026-06-23
 - [x] Commit (via /commit-change) — DONE (reconcile 2026-06-29 : working tree clean, travaux shippés)
@@ -131,8 +528,8 @@ Subtasks :
 - [x] Patcher `lib/design-gate.md` — ajouter motion/motion-v/framer-motion + autres anim-libs dans filesystem signals
 - [x] Tester : shellcheck OK ; matrix React/Vue/RN/backend/with-motion/no-package/pnpm tous corrects
-## Helper `--help` / `help` sur tous les skills (option C)
+## Helper `--help` / `help` sur tous les skills (option C) [WON'T-BUILD 2026-06-30 — mesuré non-rentable]
-> ⚠️ BLOQUÉ (reconcile 2026-06-29) : contredit BDR-001 (accepted) qui a REJETÉ "copier le helper dans chaque SKILL.md" (maintenance entropy) au profit d'un hook session-start. Or ce chantier planifie STEP 0.5 par SKILL.md. Le TODO note lui-même "aucun skill ne gère --help aujourd'hui" → la voie hook de BDR-001 n'a jamais produit de --help fonctionnel. TRANCHER d'abord : BDR-001 périmé → marquer superseded, OU repasser par le hook. Ne pas lancer avant résolution.
+> ⛔ WON'T-BUILD (2026-06-30) : ABANDON tranché après mesure. RED comportemental (6 reps, /web-validate + /harden, SANS instruction) → **6/6 rendent déjà une aide riche ET s'arrêtent sans dispatcher** (même /harden n'a pas lancé l'audit). Le comportement supposé absent est déjà spontané (convention universelle --help). Seule valeur résiduelle = cohérence de format (6 formats divergents) → ROI insuffisant pour ~5 lignes dans un CLAUDE.md compressé ([[BDR-031]]) sur repo mono-user. 3e état : NON "fait" (rien construit), NON "ouvert" (on ne le fera pas). L'option globale réalisait l'intention BDR-001 ; per-skill toujours rejeté. Voir [[BDR-001]] (won't-build), [[LRN-080]], [[LRN-075]]. Design + subtasks ci-dessous = historique, non actionnables.
 Problème : aucun skill ne gère `--help` aujourd'hui. `argument-hint` affiche juste la syntaxe en autocomplétion, pas de description/exemples. L'utilisateur doit lire le SKILL.md ou deviner.
 Objectif : `/<skill> --help` (ou `/<skill> help`) affiche un bloc standardisé (description, args, exemples, cross-refs) et exit SANS dispatcher l'agent ni modifier quoi que ce soit.
@@ -163,13 +560,13 @@ Design :
 - **Skills à patcher** : `~/Documents/claude/skills/` = ~20 skills persos + skills-perso list pour référence. Ne PAS toucher skills-external/gstack (ownership externe) ni example-skills.
 Subtasks :
- [ ] Créer `skills/lib/help-handler.md` — snippet réutilisable (détection + extraction + affichage)
+- [-] Créer `skills/lib/help-handler.md` — snippet réutilisable (détection + extraction + affichage)
- [ ] Définir format d'aide standard + section "ARGUMENTS" vs reuse de argument-hint
+- [-] Définir format d'aide standard + section "ARGUMENTS" vs reuse de argument-hint
- [ ] Décider : sections ARGUMENTS/EXAMPLES doivent-elles être dans la frontmatter (nouveau champ YAML) ou dans le corps du SKILL.md (nouvelle section `## Help`) ?
+- [-] Décider : sections ARGUMENTS/EXAMPLES doivent-elles être dans la frontmatter (nouveau champ YAML) ou dans le corps du SKILL.md (nouvelle section `## Help`) ?
- [ ] Patcher un skill pilote (`/validate`) — valider UX  _(désormais `/web-validate` — renommé e5e673a)_
+- [-] Patcher un skill pilote (`/validate`) — valider UX  _(désormais `/web-validate` — renommé e5e673a)_
- [ ] Patcher les skills perso restants : analyze, bugfix, code-clean, commit-change, doc, feat, geo, graphify, harden, hotfix, init-project, make-pdf, onboard, plan-tune, plugin-check, refactor, seo, ship-feature, skills-perso, status, benchmark-models, context-save, context-restore
+- [-] Patcher les skills perso restants : analyze, bugfix, code-clean, commit-change, doc, feat, geo, graphify, harden, hotfix, init-project, make-pdf, onboard, plan-tune, plugin-check, refactor, seo, ship-feature, skills-perso, status, benchmark-models, context-save, context-restore
- [ ] Mettre à jour `~/.claude/CLAUDE.md` — mentionner convention --help disponible sur tous les skills perso
+- [-] Mettre à jour `~/.claude/CLAUDE.md` — mentionner convention --help disponible sur tous les skills perso
- [ ] Note : skills-external/gstack ont leur propre convention, ne pas toucher
+- [-] Note : skills-external/gstack ont leur propre convention, ne pas toucher
 ## Skill profiles (partition gstack par usage)
 - [x] Plan
@@ -280,7 +677,7 @@ Goal: universal gitflow across all `bchanot/*` Gitea repos. Lib built across pri
 - [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)
-## 2026-06-29 — MINOR-gate strengthening (doc-syncer) [branch feature/minor-gate-strengthening]
+## 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;
 the literal one (blocking gate on MINOR) contradicts engraved [[BDR-036]]. Scope: ①+②, not B,
 ③ deferred. Built test-first (Iron Law).
@@ -291,7 +688,7 @@ the literal one (blocking gate on MINOR) contradicts engraved [[BDR-036]]. Scope
 - [x] FINISH — merged feature/minor-gate-strengthening → develop (`0f0bd7f`) on explicit signal
 - [~] ③ branch-guard in doc-commit DEFERRED — duplicates protected-base predicate 3rd time (lib + hook + here); all migrated repos have the hook. Reconsider only for repos outside `gitflow init`
-## 2026-06-29 — BLK-011 GSD ROADMAP post-FINISH [branch bugfix/blk-011-gsd-roadmap]
+## 2026-06-29 — BLK-011 GSD ROADMAP post-FINISH [DONE — merged develop ce4391a, branch deleted]
 User reframed: don't plumb a commit for the stranded ROADMAP — ask if gsd belongs at init at all.
 Read refuted both option-premises (gsd ≫ roadmap; TODO ≠ gsd ROADMAP) but conclusion A held for a
 stronger reason: speculative auto-bootstrap of an unused engine at creation is bad per se ([[LRN-072]]).
@@ -301,7 +698,7 @@ stronger reason: speculative auto-bootstrap of an unused engine at creation is b
 - [x] Capitalize — [[BLK-011]] resolved (true reason + premise trace) + [[LRN-072]] + CHANGELOG Removed + journal 2026-06-29 (cont. 2)
 - [x] FINISH — merged bugfix/blk-011-gsd-roadmap → develop (`ce4391a`); develop pushed to origin (6 commits, SSH)
-## 2026-06-29 — prune-memory hardening (RED-7/8 + index backfill) [branch bugfix/prune-memory-hardening]
+## 2026-06-29 — prune-memory hardening (RED-7/8 + index backfill) [DONE — merged develop 73e12be, branch deleted]
 LAST of 3 chantiers. Read-first cartography confirmed RED-7/8 + measured 34-row index drift.
 - [x] RED-7 (example-priming) — fictionalized STEP-2 example to 9xx ids (live ids primed a wrong merge of complementary LRN-014/016); DETERMINISTIC test (run-deterministic.sh) per [[LRN-046]]. Caught its own ugrep false-green → /usr/bin/grep ([[LRN-074]]). [[LRN-073]]
 - [x] RED-8 (added-negation inversion) — consciously ACCEPTED as documented limit in BACKLOG ([[LRN-047]]); no fragile guard built
@@ -346,7 +743,7 @@ Subtasks (à détailler au lancement) :
 - [x] Test final = reproduire l'inventaire 2026-06-29 (cat. 1-4 + contradiction BDR-001) comme oracle — DONE (run-reconcile.sh 20/20, fixtures neutres, RED prouvé rouge avant le vert)
 - SHIPPED 2026-06-30 : feat `82e6322` + mémoire `6b512be` → merge `aede7af` (feature/reconcile-skill supprimée) → poussé origin/develop. main intact. BDR-041 + LRN-075/076/077 + EVAL-011 capitalisés.
-## [QUEUED] skill /release-candidate — orchestrateur gitflow release (lib vérifiée, le tag est le gap)
+## [SHIPPED 2026-06-30 — develop 0c0b748, released v4.0.0 (tag v4.0.0)] skill /release-candidate — orchestrateur gitflow release
 Pertinent maintenant : develop ahead de main, prochaine étape gitflow = release.
 VÉRIFIÉ dans lib/gitflow.sh (2026-06-30) — release CÂBLÉE, pas que hotfix :
 - start base=develop (`gitflow_base_for` L49) ; `gitflow start release <ver>` positionne sur la branche (L71).
@@ -361,7 +758,51 @@ Design (à la conception) : ORCHESTRATEUR au-dessus du gitflow existant — NE P
 - push gaté (ASK, [[LRN-069]]) : main + develop + tag.
 Subtasks (à détailler au lancement) :
- [ ] Décider : tag dans le skill VS étendre `gitflow finish` avec un arg tag optionnel (orchestrateur préféré — ne pas réécrire la mécanique)
+- [x] Décider : tag fourni par le skill au-dessus de gitflow (mécanique non réécrite) — d3d6ced, [[BDR-042]]
- [ ] `skills/release-candidate/SKILL.md` — orchestration start→prep→finish→tag→push(gaté) + gate humain "WHEN to release"
+- [x] `skills/release-candidate/SKILL.md` — orchestration start→prep→finish→tag→push(gaté) + gate humain "WHEN to release" — présent (d3d6ced)
- [ ] routage CLAUDE.md
+- [x] routage CLAUDE.md — présent (~/.claude/CLAUDE.md "Cut a release → release-candidate")
- [ ] test (worktree jetable : prouver fan-out main+develop + tag présent sur main + branche supprimée)
+- [x] test — prouvé par la release réelle 4.0.0 : fan-out main (709facf) + develop (4a00a60) + tag v4.0.0
 ## Auto-déclenchement des skills par intention [WON'T-BUILD 2026-06-30 — mesuré : Claude discrimine déjà (3 classes)]
 > ⛔ WON'T-BUILD (2026-06-30) : 3e moot de la série (après [[BDR-001]] --help + [[BDR-043]]/[[LRN-082]] darwin re-baseline). Cartographie : routing = STACK L0(design-hook)→L1(superpowers « 1%→MUST invoke », dominant)→L2(prose CLAUDE.md)→L3(frontmatter)→L4(BDR-019). L1 SUR-détermine déjà l'invocation → « auto-call ? » = déjà oui. Reframe C : la vraie question = DISCERNEMENT, risque inversé under→**OVER**-routing. Mesure en VRAIES sessions fraîches (8 prompts / 3 classes) : CLEAR→route ✓, AMBIGUË→demande (refuse de deviner, investigue pour une question utile) ✓, TRIVIALE→s'abstient ✓. Le sur-routing soupçonné (L1 vs règles Workflow) NE se matérialise PAS — le modèle équilibre. Prose de bornage L2 = valeur fantôme + risque de DÉGRADER un discernement déjà bon. Voir [[BDR-044]] (reframe + verdict), [[LRN-083]] (RED sous-agent invalide), [[LRN-080]] (mesure-first, corroboré 3-in-a-row). RED sous-agent initial (0/6) RETIRÉ comme non-discriminant (plancher artefact). Design + subtasks ci-dessous = historique, non actionnables.
 > ⏭️ (historique) NEXT, mais CADRÉ : **pas de design avant la mesure**. Jumeau méthodologique de [[BDR-001]] `--help` (won't-build après RED) — même piège architectural, même garde-fou [[LRN-080]] (mesurer avant d'instruire) + [[LRN-049]] (borner le bruit avant le marqueur). Les subtasks ci-dessous s'arrêtent à la mesure ; le design ne s'ouvre QUE si le RED valide la valeur.
 **Contrainte architecturale (établie pour `--help`, non négociable) :**
 Aucun mécanisme n'intercepte le message utilisateur pour *lancer* un skill. La harness ne route pas avant que le modèle réponde — un skill n'est invoqué QUE par le modèle (outil Skill). Donc « auto-call déterministe » = IMPOSSIBLE. Le seul levier sur l'invocation elle-même = instruire le MODÈLE à reconnaître l'intention et appeler le bon skill → **conformité-modèle, PAS déterminisme**. C'est une instruction de routage CLAUDE.md, pas un mécanisme.
 - Nuance (raffinement) : une couche déterministe existe *en amont* du call, pas *sur* le call — un hook `UserPromptSubmit` peut détecter un signal et INJECTER un rappel de routage (le `design-toolchain` hook fait déjà exactement ça pour l'UI ; le banner session-start aussi). Détection déterministe + injection advisory ; le modèle reste celui qui tire. MAIS sur des verbes d'intention (« corrige », « crée », « bug »), un hook keyword serait BRUYANT (ces mots sont partout) — le design-hook s'en sort car « design/UI » est un signal rare. Donc le levier hook est probablement non-viable pour le cas large → ce qui **renforce** le besoin de borner aux signaux rares/non-ambigus.
 **Substrat déjà en place :** [[BDR-019]] a retiré `disable-model-invocation` repo-wide → le modèle PEUT déjà self-router vers les skills (défaut = activé ; user l'avait vécu live : intention feature détectée, `ship-feature` voulu, jadis bloqué). Et la section « Skill routing » de CLAUDE.md existe déjà. Donc la **baseline du RED = le routage CLAUDE.md ACTUEL tel quel** ; le chantier n'a de valeur que si le RED prouve que cette prose SOUS-déclenche sur intention claire (exactement la logique --help : baseline = convention déjà là, question = est-ce qu'instruire en plus change quoi que ce soit).
 **Le chantier COMMENCE par (rien d'autre avant) :**
 - [x] (a) **Cartographier** le routage CLAUDE.md actuel — quels signaux → quels skills sont déjà censés router (« Skill routing » + « Design work » + descriptions de skills). État des lieux factuel, pas de jugement.
 - [x] (b) **RED comportemental** ([[LRN-080]]) — prompts d'intention IMPLICITE, naturalistes, SANS instruction renforcée : « il y a un bug, debug », « on va créer X », « corrige ceci », « refactor ce module », « cut a release »… → le modèle invoque-t-il le bon skill, ou fait-il la tâche à la main en ignorant le skill ? N reps, plusieurs intents distincts.
  - Garde-fou RED : **ne PAS amorcer**. Sessions fraîches / sous-agents, prompts naturels, zéro mention de « skill » / « routage » / « test » dans le prompt mesuré (sinon le modèle route parce qu'il SAIT qu'on le teste — contamination). Le RED `--help` était mécanique donc peu sensible à l'amorçage ; l'intent-routing l'est beaucoup plus → rigueur supérieure requise.
 - [x] (c) **Décider selon le RED** :
  - déjà bon (comme --help) → chantier MINCE, voire won't-build ; capitaliser le constat (3e état : mesuré non-rentable, ni fait ni ouvert).
  - sous-déclenche → vraie valeur : renforcer la **prose de routage** (levier modèle) sur signaux CLAIRS uniquement — PAS un hook keyword (trop bruyant, cf. nuance ci-dessus).
 **Scope à border au cadrage — NE PAS faire « tout skill jugé pertinent » :**
 Tension réelle proactif vs intrusif. Auto-déclencher feat/bugfix sur intention CLAIRE et non-ambiguë = sain. « Déclenche tout skill jugé pertinent » = RISQUÉ (faux déclenchements, skills non sollicités, flux interrompus). Réglage cible ([[LRN-049]] borner le bruit) = déclencher sur signaux d'intention CLAIRS et non-ambigus ; **ambigu → DEMANDER, pas auto-déclencher**. À définir précisément SI (et seulement si) le RED valide : table `signal → skill` + la frontière exacte de l'ambiguïté.
 ## 2026-06-30 — session-close follow-ups (promoted from BLK-013 / BDR-043)
 - [x] (a) Harden install-plugins.sh Step 1 — guarantee `npm` on apt-`nodejs` hosts (detect missing npm + `corepack enable npm`), not just check `node >=22`. Fix-forward for [[BLK-013]] — stops `make plugin` Error 127 recurring on any fresh apt machine.
      [done 2026-07-01 : unconditional npm guard after Node block (corepack enable npm → distro `install npm` fallback → fatal exit 1 w/ clear msg). Catches node>=22-present-but-npm-absent (NODE_OK short-circuit). shellcheck clean, bash -n OK. Fresh-apt live validation pending (no npm-less host to hand). branch bugfix/install-plugins-npm-guard.]
 - [x] (b) Re-baseline darwin on the 5 ex-broken gstack skills (`benchmark-models`, `context-restore`, `context-save`, `make-pdf`, `plan-tune`) — now repaired and back in scope ([[BDR-043]], trigger cleared). Verify `results.tsv` still marks them `status=error` first. (Promoted from BDR-043's action-field — not an item the user authored.)
      [resolved-MOOT 2026-06-30 : won't-run. BDR-043 cleared only motif (a) of BDR-015's TWO exclusion grounds (symlinks repaired ✅); motif (b) external-ownership INTACT — the 5 resolve to skills-external/gstack/ (submodule), darwin optimizes by EDITING SKILL.md → would dirty the submodule (forbidden [[LRN-070]]). Re-baseline = unactionable score. + results.tsv gone (wiped by 23/06 make-plugin reinstall) → not even a re-baseline, a fresh-from-zero one. Geometric trigger lifted, value trigger intact — twin of --help [[LRN-080]]. See [[LRN-082]]. Not "done", not "open": MOOT.]
 ## 2026-07-03 — bugfix/gitflow-finish-args (contract fix + doctor false-warns)
 Root: audit 2026-07-02 residuals. `gitflow_finish` ignores its args (merges CHECKED-OUT
 branch) → LOT3 mis-merge trap; + 3 doctor false-warns (LRN-047 class).
 - [x] (1) lib/gitflow.sh gitflow_finish — optional <type> <name>; error rc2 if != current
      branch ("operates on current branch X, you asked Y — checkout Y first"). No-args unchanged.
      Commit d9fdd4c. [[BLK-015]] [[LRN-089]].
 - [x] (2) lib/gitflow-test.sh — T12 arg-guard: arg-mismatch → nonzero + message names both;
      arg-match → merges as before. +7 assertions (71/71). T12 (not T6c — reconcile collision).
 - [x] (3) doctor.sh cargo line — false "(RTK unavailable)" → optional info (RTK prebuilt).
 - [x] (4) doctor.sh check_symlink — PASS iff canonical path under $REPO (direct OR via
      symlinked ancestor dir); hooks/session-start.sh false-warn gone. Commit 6778b9f.
 - [x] (5) doctor.sh §2 gstack — counts 34 per-skill symlinks; mythical [ -L skills/gstack ] dropped.
 - [x] (6) doctor.sh token § — denominator 11000→CONTEXT_WINDOW=200000, thresholds 15/25,
      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.
@@ -0,0 +1,52 @@
 # CONTRACT — seo-account-mgmt
 - date: 2026-07-10 | flow: feat | branch: feature/seo-account-mgmt
 - status: active
 ## REQUEST (verbatim — IMMUTABLE)
 "J'aimerais qu'on rajoute quand meme une option au skill pour juste connecter
 le compte. du style un argument au skill seo pour fiare un truc du genre /set
 seo-connect ou quelque chjose comme cas. Et aussi pouvoir clean la liste des
 compte deja enregister. pouvoir supprimer des compte ou tout supprimer"
 — design proposal validated by user ("go pour l'un puis l'autre oui"):
 `/seo connect [label]` / `/seo accounts` / `/seo forget <label>` /
 `/seo forget --all`; tokenstore remove+clear verbs; fetch.sh forget dispatch;
 new connect.sh wrapper (sources env internally, usable from any project);
 Makefile delegates to it; SKILL.md arg routing + STEP 0 fix; forget output
 must state local removal ≠ Google revocation (myaccount.google.com/permissions).
 ## CLARIFICATIONS
 none — request complete (design pre-validated in conversation).
 ## ACCEPTANCE CRITERIA
 1. `python3 lib/seo-data/tokenstore.py remove --file F --label X` deletes only
   label X (others preserved), prints `{"status":"ok","removed":true|false}`,
   never prints a refresh token; atomic write + fcntl lock as set.
 2. `python3 lib/seo-data/tokenstore.py clear --file F` empties the store
   (subsequent list → `"accounts": []`), JSON ok, same write discipline.
 3. Fail-open preserved on new verbs: bad usage → `{"status":"error",...}` +
   exit 2; unexpected error → degraded JSON (existing _cli try/except covers).
 4. `fetch.sh forget --label X` / `forget --all` dispatch to remove/clear
   within the existing contract (JSON stdout, exit 0 ok, exit 2 bad usage);
   `fetch.sh forget` with no/invalid flag → exit 2 + JSON.
 5. New `lib/seo-data/connect.sh`: sources `${SEO_DATA_ENV_FILE:-~/.claude/.env}`
   internally (set -a, never echoed), picks venv python else system, execs
   connect.py with passed args; with no creds exits nonzero with the
   "Set GOOGLE_OAUTH_CLIENT_ID/SECRET" gate message (deterministic, offline).
 6. Makefile `seo-connect` delegates to connect.sh (env-sourcing duplication
   from caa5bed removed); venv creation + pip install kept before.
 7. `skills/seo/SKILL.md` routes `connect [label]` / `accounts` /
   `forget <label>|--all` BEFORE the audit flow (audit `/seo <url>` unchanged);
   forget path includes the Google revocation notice
   (myaccount.google.com/permissions); STEP 0 no longer proposes bare
   `make seo-connect` as the only path (connect.sh tilde path offered).
 8. `lib/seo-data/README.md` documents connect.sh, forget verbs, revocation note.
 9. `lib/seo-data/seo-data.test.sh` covers: remove keeps others / removed:false
   on missing label / clear empties / redaction on remove / forget via fetch.sh
   (JSON + exit codes, bad usage 2) / connect.sh offline negative path; plus
   wiring locks (connect.sh sources vault, Makefile delegates, SKILL routes,
   README documents). Whole suite + `make test` green.
 10. No commit attribution trailers; tilde paths for engine calls in SKILL.md.
 ## FILE SCOPE
 lib/seo-data/tokenstore.py, lib/seo-data/fetch.sh, lib/seo-data/connect.sh (new),
 lib/seo-data/seo-data.test.sh, lib/seo-data/README.md, Makefile, skills/seo/SKILL.md
@@ -0,0 +1,45 @@
 # CONTRACT — claude-global-md-rename
 - date: 2026-07-12 | flow: ship-feature | branch: (feature branch off develop, created at STEP 4)
 - status: active
 ## REQUEST (verbatim — IMMUTABLE)
 > pour les soucis 1 et 2, ne serais-ce pas plus judicieux de mettre notre claude.md de ce repo, qui es tle global, le renommer en CLAUDE.prod.md ou quelqeu chose comme ca, avec tout ce qui concerne le userscope, le link.sh fait un lien symbolique de ce fichier avec ce nom vers ~/.claude/CLAUDE.md car on peut avoir un nom differnt du lien, et ca permet d'avoir le claude.md du projet dasn le quel on met ces deux partie qui sont pas destine au userscope. qu'en pense tu ?
 > oui, utilise /ship-feature pour faire les modification vers un CLAUDE.global.md et toute les dependance et iunstallateur et update etc
 (Name arbitrated in conversation: `CLAUDE.global.md`, not `CLAUDE.prod.md`.)
 ## CLARIFICATIONS
 none — request complete (design questions resolved at STEP 1 brainstorm, gated at STEP 3)
 ## ACCEPTANCE CRITERIA
 1. `CLAUDE.global.md` exists at repo root, renamed via `git mv` (history preserved: `git log --follow CLAUDE.global.md` shows pre-rename commits), containing the former global content MINUS the `# This repo only (claude-config)` section, PLUS a short scope header stating it is the user-scope global memory deployed as `~/.claude/CLAUDE.md`.
 2. A new project-level `CLAUDE.md` exists at repo root containing: a short scope header (project-only, not user-scope), the former "This repo only" content (Health Stack / shellcheck), and the rules/ maintenance doctrine migrated from `rules/README.md` (what belongs in rules/, lazy-load semantics, machine-owned context7/BDR-053 note).
 3. `link.sh` links `<repo>/CLAUDE.global.md` → `~/.claude/CLAUDE.md`; after running it, `readlink ~/.claude/CLAUDE.md` resolves to `<repo>/CLAUDE.global.md` (stale link replaced, no dangling symlink).
 4. `hooks/session-start.sh` line-count guard (BDR-062) reads `CLAUDE.global.md` (new path), threshold 320 unchanged, and does not silently fail-open on the old path.
 5. `doctor.sh` passes: `~/.claude/CLAUDE.md` symlink check green; size/token reporting reads `CLAUDE.global.md`.
 6. `install-plugins.sh` GUARDED_CONFIGS protects `CLAUDE.global.md` (installer drift guard follows the renamed file).
 7. `lib/doc-commit.sh` exclusion list covers `CLAUDE.global.md` as read-only/never-target (BDR-022 unchanged in spirit).
 8. `rules/README.md` slimmed to a minimal pointer (keeps `paths:` frontmatter; doctrine lives in the project CLAUDE.md).
 9. No stale script reference remains: `grep -rn 'CLAUDE\.md' *.sh hooks/*.sh lib/*.sh` shows no reference meaning the repo-root GLOBAL file under its old name (references to `~/.claude/CLAUDE.md` symlink name and to per-project CLAUDE.md concept are expected and unchanged). [gated 2026-07-14 clarification, user-arbitrated] CONSUMER-facing hook strings (messages injected into sessions, which run in any project) reference the global by its DEPLOYED name — "global CLAUDE.md" — because consumers resolve it via ~/.claude/CLAUDE.md; only MAINTAINER-facing comments use the repo filename CLAUDE.global.md. Both are conformant, not stale.
 10. `README.md` / `USAGE.md` / `MIGRATION.md` layout descriptions updated where they mean the repo-root global file.
 11. `shellcheck` passes on every modified `.sh` file (repo Health Stack).
 12. [gated 2026-07-13] New project CLAUDE.md is MINIMAL — scope header + Health Stack + rules/ maintenance doctrine (incl. context7/BDR-053 note and the foreign-project glob caveat); no empty template sections.
 13. [gated 2026-07-13] rules/README.md keeps `paths: ["rules/**"]` frontmatter; body reduced to a pointer referencing the project CLAUDE.md.
 14. [gated 2026-07-13] Global file nets 305 → 301 lines; scope header = 2-line HTML comment above the title; `git diff -M --cached -- CLAUDE.global.md` shows exactly two hunks (header insertion, tail-section deletion).
 15. [gated 2026-07-13] `GUARDED_CONFIGS` has 4 entries: keeps `"CLAUDE.md"` (graphify's rewrite target = project file) AND adds `"CLAUDE.global.md"`; mktemp error message lists all four.
 16. [gated 2026-07-13] USAGE.md / MIGRATION.md / update-all.sh verified as having zero references to the repo-root global file — deliberately not edited.
 17. [gated 2026-07-13] Spec + plan docs are the feature branch's first commit; the session-scoped plugin toggles in settings.json are NEVER staged in any commit of this branch.
 ## FILE SCOPE
 - CLAUDE.md → CLAUDE.global.md (git mv + content split)
 - CLAUDE.md (new project-level file)
 - link.sh
 - hooks/session-start.sh
 - doctor.sh
 - install-plugins.sh
 - lib/doc-commit.sh
 - rules/README.md
 - README.md, USAGE.md, MIGRATION.md (doc references)
 - [gated 2026-07-14] hooks/config-protection.sh, hooks/design-toolchain-reminder.sh (required by criterion 9's sweep — global-file references in comments/messages)
 - [gated 2026-07-14] docs/superpowers/specs/2026-07-12-claude-global-md-rename-design.md, docs/superpowers/plans/2026-07-13-claude-global-md-rename.md (required by criterion 17 — branch's first commit)
@@ -4,3 +4,12 @@
 # Used by: lib/toggle-external.sh enable|disable magic
 # Get a key at: https://21st.dev/magic (dashboard → API keys)
 MAGIC_API_KEY=your_21st_dev_magic_api_key_here
 # ── Google SEO data layer (lib/seo-data) — used by /seo FULL ──
 # OAuth Desktop client: GCP console → APIs & Services → Credentials → OAuth client (Desktop).
 # Scope requested at consent: webmasters.readonly. One-time setup: make seo-connect
 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 APIs).
 # Get it: https://developer.chrome.com/docs/crux/api
 CRUX_API_KEY=<your-crux-api-key>
@@ -7,6 +7,19 @@ br=$(git symbolic-ref --short -q HEAD 2>/dev/null)
 git rev-parse --verify -q HEAD >/dev/null 2>&1 || exit 0   # root commit — allow
 [ -f "$gd/MERGE_HEAD" ] && exit 0                          # merge in progress — allow
 # Secret backstop (job7) — any branch, not just protected ones. Non-blocking
 # if gitleaks isn't installed; auto-discovers ./.gitleaks.toml (repo root).
 if command -v gitleaks >/dev/null 2>&1; then
  if ! gitleaks git --staged --no-banner >/dev/null 2>&1; then
    echo "gitflow pre-commit: BLOCKED — gitleaks found a secret in staged changes." >&2
    echo "  Details: gitleaks git --staged --no-banner" >&2
    echo "  Genuine false-positive? add an allowlist rule to .gitleaks.toml — never bypass with --no-verify." >&2
    exit 1
  fi
 else
  echo "gitflow pre-commit: gitleaks not installed — secret scan skipped (https://github.com/gitleaks/gitleaks)." >&2
 fi
 case "$br" in
  main|develop) ;;                        # protected — keep checking
  *) exit 0 ;;                                              # working branch — allow
@@ -64,10 +64,19 @@ skills/ios-sync
 skills/design-motion-principles
 skills/emil-design-eng
 skills/frontend-design
 skills/impeccable
 # External skills installed via `npx skills add` — auto-created by link.sh
 skills/darwin-skill
-skills/find-skills
+
 # Context7 docs-lookup skill — installed by `ctx7 setup --claude --cli`
 # (install-plugins.sh Step 6, when absent) into ~/.claude/skills (a symlink to
 # this repo's skills/). ctx7-managed and re-created on demand — not vendored here.
 skills/find-docs/
 # Context7 rule — (re)written by the same `ctx7 setup` into ~/.claude/rules (a
 # symlink to this repo's rules/). ctx7-managed — not vendored here.
 rules/context7.md
 # Staging area used by lib/toggle-external.sh when disabling a tool
 skills-disabled/
@@ -82,6 +91,7 @@ skills-disabled/
 .claude/settings.local.json
 .claude/agent-memory/
 .claude/gstack/
 .audit/
 # Generated outputs
 graphify-out/
@@ -104,6 +114,11 @@ install-*.log
 .env.*
 !.env.example
 # seo-data engine local artifacts (live under ~/.claude, never committed)
 .venv-seo-data/
 seo-data/tokens.json
 __pycache__/
 # OS
 .DS_Store
 Thumbs.db
@@ -113,6 +128,7 @@ desktop.ini
 *.swp
 *.swo
 *~
 *.bak
 .idea/
 .vscode/
@@ -126,6 +142,12 @@ desktop.ini
 # an update. The source is always re-synced, so no offline copy is needed.
 skills-external/frontend-design/
 # 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
 # (ctx7 pattern). Symlinked into skills/ by link.sh.
 skills-external/impeccable/
 # npx `skills add` project-scope artifacts — darwin-skill copies itself into
 # the repo's .agents/ and writes skills-lock.json at root. Our own agents live
 # in agents/ (no dot) and stay tracked. Anchored to root so only the dotted
@@ -0,0 +1,86 @@
 title = "claude-config gitleaks config"
 # Backstop scanner (job7): pre-commit hook (lib/gitflow.sh emit-hook) and
 # `make scan-secrets`. Extends gitleaks' default ruleset — never replaces it.
 [extend]
 useDefault = true
 # 3 false-positive classes identified in job7 triage (.audit/job7/ALL-REDACTED.json),
 # each verified empirically against the real flagged files before being added
 # here (see .audit/job7-report.md). None of these are live secrets.
 [[allowlists]]
 description = "job7 triage — known false positives, not secrets"
 # Content-based: git-game repo test fixtures (#5/#6 in the triage), confirmed
 # synthetic by the repo owner — literal "test-secret-<digits>" values used in
 # unit tests, flagged by the generic-api-key rule on entropy alone.
 regexTarget = "match"
 regexes = [
  '''test-secret-[0-9-]+''',
 ]
 # Path-based: third-party/vendored files outside our control, flagged by
 # rules that don't apply to their content.
 paths = [
  # Official claude-plugins marketplace catalog — 40-char hex "sha" (git
  # commit references, not credentials) trip the sourcegraph-access-token
  # rule, which matches on bare hex length/entropy alone.
  '''plugins/marketplaces/.*marketplace\.json$''',
  # superpowers plugin test fixture — a base64-encoded WS protocol test
  # nonce, not a credential, trips generic-api-key on entropy.
  '''tests/brainstorm-server/ws-protocol\.test\.js$''',
  # NOT a job7 false positive — this IS a real secret, by design: the
  # canonical vault (BDR-026). `make scan-secrets` scans ~/.claude looking
  # for stray COPIES of secrets outside this file; flagging the vault
  # itself on every run is pure noise, not signal.
  '''(^|/)\.env$''',
  # seo-data OAuth token store — legitimate local secret (like ~/.claude/.env),
  # 0600, outside git. Allowlisted so `make scan-secrets` doesn't flag the vault.
  '''(^|/)\.claude/seo-data/tokens\.json$''',
 ]
 # ── secrets-triage 2026-07-14 — 4 FP classes, each verified empirically
 # (unredacted re-scan piped in-memory, values masked; see
 # .gstack/security-reports/2026-07-14-secrets-triage.json). None are secrets.
 # Transcripts and file-history are deliberately NOT path-allowlisted — that is
 # where real leaks land (BDR-057).
 # Bare 40-hex = git commit SHA (plugin-catalog pins, commit refs quoted in
 # transcripts) tripping sourcegraph-access-token, which matches naked hex.
 # Real sourcegraph tokens keep their sgp_ prefix → still detected.
 [[allowlists]]
 description = "bare 40-hex git commit SHAs (sourcegraph-access-token misfire)"
 regexTarget = "secret"
 regexes = ['''^[0-9a-f]{40}$''']
 # Synthetic AWS key fabricated by lib/gitflow-test.sh:240 to exercise the
 # pre-commit secret guard; test output lands in session transcripts.
 [[allowlists]]
 description = "gitflow-test synthetic AWS fixture (deliberately fake)"
 regexTarget = "secret"
 regexes = ['''AKIAGDR5XRBXYARW2I5N''']
 # Public-by-design or expired URL credentials + documentation placeholders.
 [[allowlists]]
 description = "presigned-URL key ids, GitHub image JWTs, doc placeholders"
 regexTarget = "line"
 regexes = [
  '''X-Amz-Credential=AKIA[0-9A-Z]{16}''',
  '''private-user-images\.githubusercontent\.com/[^"]*\?jwt=''',
  '''MAGIC_API_KEY=abc123''',
  # magic MCP docs example — base64 of "the ..." ASCII sample text.
  '''clientKey = 'dGhlIH[A-Za-z0-9+/=]*'''',
 ]
 # Prose in transcripts near the word "tokens" — dictionary phrases flagged by
 # generic-api-key on entropy alone (e.g. a design discussion of publish/reject
 # token pairs). Exact literals only; transcripts stay fully scanned otherwise.
 [[allowlists]]
 description = "prose false positives in transcripts"
 stopwords = ['''publish/reject''']
 # Ephemeral machine-local IDE auth locks (rotate per IDE session, never leave
 # the machine).
 [[allowlists]]
 description = "Claude Code IDE lock files"
 paths = ['''(^|/)ide/[0-9]+\.lock$''']
@@ -6,6 +6,60 @@ Format follows [Keep a Changelog](https://keepachangelog.com/).
 ## [Unreleased]
 ## [1.0.0] — 2026-07-16 — Initial public release
 First public release of claude-config. The feature set below is the
 accumulated work previously staged as internal versions 1.0.0–4.0.0
 (see "Pre-release (internal history)" further down for that lineage).
 ### Changed
 - BREAKING(layout): repo-root global memory renamed CLAUDE.md → CLAUDE.global.md; run `bash link.sh` once after pulling (doctor.sh now checks the exact target)
 - graphify skill dist refreshed 0.8.45 → 0.9.6 (out-of-band `make plugin`; SKILL.md + query/extraction references updated by the generator).
 - `/deploy` checklist reshaped on first-real-run feedback, in two passes: runbook steps are **one command per line, interactive-session style** (an early step opens the ssh session; later lines run on the box; local steps say "from your machine") instead of folded `ssh host "cd … && …"` one-liners — step = comment header + command lines up to the next blank line, a `@delta:` directive governs the whole block; and the checklist is now **display-only** — `NEXT.sh` is no longer written at all (throwaway artifact; `PENDING.json` + the live runbook regenerate it in any session) and every hand-back **ends the turn with the full checklist as the final text, no tool call after it** (a checklist printed above a blocking question tool was observed never reaching the user). Template `templates/deploy/PROCEDURE.md` restyled to match.
 - `settings.json`: `inputNeededNotifEnabled: true` adopted (harness notification toggle); committed layout otherwise unchanged.
 - gsd-pi upgraded 2.64.0 → 3.0.0 — `status-reporter` output parser adapted to the ADR-013 cutover.
 - `hotfixer` pinned `model: sonnet` (seo/geo/web-validate L1 applier); `analyzer` haiku pin removed (inherits the session model).
 - ship-feature / init-project: SDD implementation + review subagents dispatched with `model: "sonnet"`.
 - web-validate `--fix`: bundle applied via `hotfixer` at L1 instead of inline Edit (BDR-061 alignment).
 - Model routing wave 2 — the pure-execution + reflection-split skills stop running execution on the big session model. `/doc` and `/status` now **dispatch** their agent (doc-syncer sonnet, status-reporter haiku) instead of inline-loading it, so the pin takes effect. `/hotfix` split like `/feat`: reflection (LOCATE root cause) inline behind the model gate, the fix applied by a `hotfixer` sonnet executor (rewritten dual-use — it is also the seo/geo/web-validate L1 applier); revert-not-loop preserved; hotfix joins the gated group (13th). `/commit-change` dispatches a sonnet `commit-changer` (propose → dispatcher-owned approval gates → apply; grouping runs on sonnet, `AskUserQuestion` removed from the agent). `/release-candidate` dispatches a new sonnet `release-executor` for the mechanical spans (prep / finish+tag), the two human gates (when-to-release, push) and the version-number decision staying in the dispatcher.
 - Model routing wave 3 — the last two inline execution-carrying skills split like `/feat`. `/bugfix`: root-cause investigation, diagnosis and contract run inline behind the model gate; the fix + regression test are applied by a `bugfixer` sonnet executor (was a single inline agent), with the verify+secure loop staying in the main loop and the executor as its re-dispatched dev. `/code-clean`: the dead-code / style / structural audit and the approval gate run inline; a `code-cleaner` sonnet PHASE-2 executor then applies the approved scope — and the style/structural refactor (which inline-loads `refactorer`) now finally runs on sonnet, its pin having been inert under the old inline-load. Both skills stay gated (they keep reflection); their read-only-audit consumers (`onboard`, `tour`) reroute to a big-model agent so an audit never runs on the sonnet executor. Supersedes the BDR-050 "bugfix stays inline" carve-out. The built-in `Explore` search agent is deliberately left inheriting the session (search feeds reflection).
 - Model routing wave 4 — client-handover doc-generation moved to sonnet (redaction-only). The ship-and-handover pipeline (baseline audits, fix loops, commit/push, deploy pause, live validate, gate) stays inline on the big session model in `client-handover-writer` — its interactive gates work natively and its nested `/seo`/`/harden`/`/web-validate` audits inherit the big model — and only the deliverable writing is delegated to a new sonnet `handover-doc-writer` (gate-free: reads memory + git, synthesizes the 6-chapter doc from a resolved PACKAGE, runs the word-count / skill-leak / anchor gates, renders branded HTML+PDF). `client-handover` joins the gated group (it orchestrates audits = reflection). Chosen over the whole-writer dispatch: the nested audits must run big either way, so whole-writer would have added ~7 gate-yields + a resumable state machine on a client deliverable for ~zero extra sonnet work.
 ### Security
 - **Magic MCP fully ask-gated** — all four `mcp__magic__*` tools (builder, refiner, inspiration, logo_search) moved to `permissions.ask` in `settings.json`; no magic call can auto-execute. The builder opens an unauthenticated local callback server (`127.0.0.1:9221+`, `Access-Control-Allow-Origin: *`, no token check) whose POST body is injected verbatim into the tool result the model consumes — the ask-gate is the mitigation on our side (BDR-059).
 - **`MAGIC_API_KEY` passed by reference, not by value** — the MCP server is registered with `--env 'API_KEY=${MAGIC_API_KEY}'` (Claude Code expands it at launch from its own process env) instead of the literal secret, which `claude mcp add` would otherwise materialize in plaintext in `~/.claude.json`, outside the repo's `.env` allowlist reach (BDR-026).
 - **`printenv` / `env` dumps redacted in `rtk-rewrite.sh`** — closes a leak vector where a rewritten environment dump could surface a Gitea token.
 - **gitleaks secret-scanning backstop** — `.gitleaks.toml`, a pre-commit hook, and `make scan-secrets` added to catch secrets before they land; pre-existing stale secret-bearing artifacts purged (GO-gated).
 ### Added
 - **GSC + CrUX data layer for `/seo` FULL** — `lib/seo-data/` engine pulls real Google Search Console (Search Analytics + URL Inspection) and Chrome UX Report field data into the `/seo` FULL audit: CrUX p75 field metrics become the primary Core Web Vitals signal (anonymous PageSpeed lab stays the fallback), and a "Performance GSC (90 j)" section flags position 4-10 quick wins. Multi-account via OAuth2 (`make seo-connect`, one-time consent, `webmasters.readonly` scope only) with a per-label token store (0600 file / 0700 dir, atomic write, refresh tokens redacted, gitleaks-allowlisted) so two concurrent site audits never conflict. Absent credentials degrade gracefully to anonymous PageSpeed — the audit never fails. Config: `GOOGLE_OAUTH_CLIENT_ID` / `GOOGLE_OAUTH_CLIENT_SECRET` / `CRUX_API_KEY` in `~/.claude/.env`. Engine contract documented in `lib/seo-data/README.md`.
 - **impeccable** (pbakaus, Apache-2.0) wired into the toolchain as the design counterpart of semgrep: the `/impeccable` skill (23 verbs under one command: audit, polish, bolder, quieter…) plus the 45-rule deterministic anti-pattern detector (`npx impeccable detect`, exit 0/2, `--json`). Complementary to `frontend-design` (kept — aesthetic direction at build time); impeccable adds the deterministic audit floor and per-project design context (`/impeccable init`). CLI pinned in `plugins.lock.json` (3.2.0 — a silent rules update would change audit output on unchanged code); dist is machine-owned under `skills-external/impeccable/` (gitignored, ctx7 pattern), staged-installed by `install-plugins.sh` Step 8d, refreshed pin-honored by `update-all.sh`, symlinked by `link.sh`, listed in the design/web/web-full/full profiles and the design-work routing. Requires Node ≥ 24: the install baseline is bumped from 22 to 24 LTS (NodeSource `setup_24.x` / brew `node@24`), so `make plugin` upgrades a too-old host in place; the impeccable steps still skip gracefully if Node stays below 24. Not in the design gate's GATE-BLOCK list yet — promotion deliberate, after first dogfood.
 - `/tour` skill — grouped all-axes sweep over one or several projects: security (pinned-semgrep `security-auditor` agent + `/cso` posture when gstack is ON) → cleanup → re-verify → reconcile (report-only, never edits the target TODO/registries) → doc sync, looping until a full pass applies zero fixes (bounded at 3 iterations). Fixes land on a `chore/tour-<date>` branch the skill never merges; each project gets an append-only `.claude/audits/TOUR.md` report with BREAKING tags on contract-changing security fixes. Built TDD (superpowers:writing-skills): baseline run showed silent TODO rewrites, autonomous registry writes, grep-as-security-pass, no persistent report, scope creep and an unbounded loop — each countered and verified on a seeded fixture.
 - Model routing (BDR-066): blocking model gate (`lib/model-gate.md` + `lib/model-check.sh`, flip-tested) wired into 12 reflection orchestrators; census guard `lib/tests/model-routing.test.sh`.
 - `/feat` re-architected: reflection inline (scope/plan/contract), execution dispatched to the sonnet-pinned `feater` executor; verify+secure loop decided in the main loop with fresh executor re-dispatches.
 ### Removed
 - `lib/detect-plugins.sh`: `detect_security_guidance` — dead since its re-add at `45c3507`; zero callers on any surface, including the dynamic `session-start.sh` detection loop (the banner's row derives from `enabledPlugins` instead). Nothing invokes it — removal, not a breaking change.
 - `lib/detect-plugins.sh`: `plugin_enabled` — its last two callers were replaced by the inline `enabledPlugins` grep at `session-start.sh:145-146` (`6d72d0a`); zero callers remained. Nothing invokes it — removal, not a breaking change.
 - `templates/settings/settings.local.json` — orphan template, zero automated consumer since creation (`a145e3c`); its README tree-line reference was already dropped at `e48c834`. Content recoverable from git history.
 - `lib/memory-commit.sh` / `lib/doc-commit.sh`: the `pending` CLI verb + sourceable `memory_pending()` / `docs_pending()` helpers — earmarked "for the v2 hook", which BDR-037 rejected (no code ever written); zero production or test callers. `commit "<message>" [<file>...]` is now the only verb on both scripts.
 ### Fixed
 - `gitflow_finish` ignored its `<type> <name>` arguments and always merged the checked-out branch — naming a different branch silently merged the wrong one. The arguments are now an optional safety assertion: if given and not equal to the current branch, `finish` refuses with a clear error instead of merging. No-argument calls (the only real caller) are unchanged.
 - `doctor.sh` false-warnings removed (a check that cries wolf is one you learn to ignore): `cargo` absence no longer claims "RTK unavailable" (RTK ships as a prebuilt binary); `check_symlink` no longer flags files reached through directory-level symlinks (e.g. `hooks/session-start.sh`); the GStack check counts the per-skill symlinks instead of a `skills/gstack` link that `link.sh` deliberately removes; the token-budget estimate is measured against the ~200k context window instead of a mis-framed "~11k session budget" that produced a false "92% CRITICAL".
 ### Removed
 - **find-skills** (alchaincyf) — skill-discovery helper dropped from the toolchain (install/update/link/toggle/advisor). Never used, and its `make update` refresh step had started failing on clone timeouts. The discovery use case stays reachable manually: `npx -y skills find <query>`.
 ---
 ## Pre-release (internal history)
 The versions below (4.0.0 down to the original 1.0.0) were internal
 development milestones predating the first public release. They are kept
 for provenance; the full detail lives in git history. Their numbering does
 not continue past the public 1.0.0 above.
 ## [4.0.0] — 2026-06-30
 ### Added
@@ -0,0 +1,301 @@
 <!-- USER-SCOPE GLOBAL memory — deployed as ~/.claude/CLAUDE.md via link.sh.
     Repo-specific instructions live in ./CLAUDE.md (project scope). -->
 # Global coding preferences
 Apply unless repo-specific instructions override.
 ## Code style
 - Simple, readable, maintainable > clever or compact.
 - One responsibility per function/method.
 - Preserve existing behavior unless asked.
 - Scope changes to task — no unrelated edits.
 ## Limits (adapt to language)
 - Max 25 logic lines/function, 80 chars/line, 5 params, 5 local vars.
  Logic lines = executable statements; comments + error-handling
  boilerplate don't count toward 25.
 - Too many params → struct/object. Too many vars → split/extract.
 - No global state. Explicit data flow.
 ## Comments & readability
 - Document intent, not mechanics. Use project doc style (docstring, JSDoc…).
 - Explicit, consistent, meaningful names. Straight control flow,
  no hidden side effects.
 ## Refactoring
 - Priority: safety → readability → consistency.
 - Remove dead code, stale comments, obsolete flags after changes.
 - Non-trivial change: ask "more elegant solution exists?"
  Hacky fix → rebuild clean, no over-engineering.
 ## Session start
 1. Read `.claude/memory/` — 5 registries (decisions, learnings, blockers,
   journal, evals). Apply before touching anything.
 2. Read `.claude/tasks/TODO.md` — current state.
 3. Either missing → create before starting
   (templates: `~/.claude/templates/memory/`).
 ## Workflow
 - 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.
 - 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.*
 - Bug received → fix directly: check logs, find root cause, resolve
  autonomously.
 - Something goes wrong → STOP, re-plan. Never push through.
 - Deviations: minor or clearly justified → do, explain after.
  Significant or shaky justification → ask before deviating.
 - Root causes only. No temp fixes. Never assume — verify paths, APIs,
  variables before use.
 ## Planning & TODO (`.claude/tasks/TODO.md`)
 - When to plan: task touches logic (new behavior, control flow, state,
  API, dependencies) → write it in `.claude/tasks/TODO.md` first,
  decomposed into subtasks. One complex task still needs a plan.
  Borderline case (single file, small obvious logic change) → skip plan,
  stay pragmatic.
 - Exempt (skip TODO.md): pure reads, explanations, questions, typos,
  cosmetic CSS, single config-value change. Same scope as `/hotfix`
  (≤2 files, obvious fix).
 - How to track, once a task qualifies:
  1. Plan → task written before code.
  2. Decompose → one subtask = one coherent change.
  3. Track → check off as you go.
  4. Summarize → high-level note at each milestone.
 ## After code changes
 1. Run tests, lint, build, type-check if available.
 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").
 ## Memory registries (`.claude/memory/`)
 Five registries persist across sessions. Capitalize during/after work.
 Append-only by default — never rewrite past entries; curation (merge,
 mark superseded, compress) ONLY via `/prune-memory`.
 | File | ID format | Purpose |
 |------|-----------|---------|
 | `decisions.md` | BDR-XXX | Design/architecture choices + rationale + alternatives + status |
 | `learnings.md` | LRN-XXX | Reusable patterns + context + future application |
 | `blockers.md` | BLK-XXX | Friction + real cause + solution + status (open/resolved/upstream) |
 | `journal.md` | date heading | 3-5 lines/session — done, decided, blocked |
 | `evals.md` | EVAL-XXX | Quality check of Claude's output + method + anomalies + action |
 **Language — registries always English.** Rationale: consistent vocab,
 lower token cost, cross-project reuse. User-facing CAPITALIZE prompts may
 mirror user's language; final written entry English.
 **Format — registries always caveman.** Drop articles + filler, fragments
 OK, short synonyms. Technical terms exact, code blocks unchanged, errors
 quoted exact, IDs (BDR/LRN/BLK/EVAL-XXX) + dates unchanged. Pattern:
 `[thing] [action] [reason]. [next step].` Rationale: registries load
 every session — caveman cuts ~40% input tokens, zero substance loss.
 Applies to direct writes AND skill CAPITALIZE steps (close, ship-feature,
 feat, bugfix, hotfix, commit-change). Legacy entries (pre-format-rule):
 compress manually or via claude.ai on demand.
 **Routing — what goes where:**
 - Choice with tradeoffs you'd defend → `decisions.md`.
 - Pattern worth reusing → `learnings.md`.
 - Dead end with root cause identified → `blockers.md`.
 - One-line log of session → `journal.md`.
 - Did Claude's output actually work? → `evals.md`.
 **Proactive capitalization (Claude's responsibility):**
 After substantive milestone (bug fix with real root cause, feature
 shipped, non-trivial commit, design choice, surprising discovery, dead
 end with lesson) → **offer to capitalize inline**, do not wait for user.
 Pre-fill entry from context; user approves/edits before write.
 Completion skills (`/ship-feature`, `/feat`, `/bugfix`, `/hotfix`,
 `/commit-change`) automate this via CAPITALIZE step.
 **Session-close ritual** (`/close` = `/capitalize --ritual`, or inline when asked):
 1. What decided? → `decisions.md` (if non-trivial).
 2. What learned? → `learnings.md` (if reusable).
 3. What blocked? → `blockers.md`.
 # Architecture decisions
 Override default framework/tooling choices. Apply at project creation,
 scaffolding, brainstorming.
 ## Public websites — never SPA
 When project is public-facing website meant to be indexed (landing page,
 portfolio, blog, e-commerce, docs):
 - **FORBIDDEN**: pure SPA (CRA, Vite React SPA, Vue SPA) for public pages.
  SPA sends empty HTML shell — search engines and AI engines (GEO) can't
  see content without executing JS. SEO and AI visibility destroyed.
 - **Astro** = default for informational sites (portfolio, docs, blog,
  landing). Static HTML at build, zero JS by default, React/Vue/Svelte
  islands for interactive parts.
 - **Next.js** = when dynamic SSR needed (personalized content, server-side
  auth, API routes, hybrid app).
 - **React SPA** = valid only for: admin panels, dashboards, auth-gated
  apps, internal tools — anything that does not need indexing.
 - **Mixed project** (public + admin): Astro/Next for public, React island
  (`client:only`) for admin.
 - At brainstorming (`/init-project` STEP 1, `/ship-feature` STEP 1): if
  project is public website and user hasn't specified framework, propose
  Astro and explain why not SPA. Never silently pick React CRA.
 ## Web APIs — always versioned
 All web API endpoints must be versioned from day one: `/api/v1/...`.
 - New project → start at `/api/v1/`, no bare `/api/` routes.
 - Breaking changes → new version (`v2`). Old version stays functional —
  clients migrate at own pace.
 - Non-breaking additions (new fields, new endpoints) → current version.
 - Each version is self-contained contract. Don't modify existing version
  behavior to match newer one.
 - Router structure reflects versioning explicitly (e.g. `api/v1/routes/`).
 ## Version control — gitflow (universal)
 Every git action follows gitflow — in a skill, or an ad-hoc commit made outside
 one on request. `main` (prod) · `develop` (integration, off main) · `feature/*`
 `bugfix/*` + `chore/*` (off develop → develop; `chore/*` = memory/doc
 maintenance, e.g. standalone `/capitalize` `/close` `/prune-memory`
 `/reconcile`) · `release/*` (off develop → main + back-merge develop) ·
 `hotfix/*` (off main → main + develop [+ any open release/*]). `master`→`main`
 everywhere.
 Never commit code directly on `main` or `develop`: branch first from the
 correct base as `<type>/<name>` (`.claude/**` memory/config commits are
 hook-exempt, following the work). Branch/merge only via the lib, never by hand:
 `bash ~/.claude/lib/gitflow.sh start <type> <name>` · `… finish`. Run `finish`
 (merge) only on an explicit human signal ("merge it", "feature OK"), never
 because tests pass, a plan step says "merge", or "ship" implied it. Assistance
 flows (`/feat` `/bugfix` `/hotfix`) and the standalone memory/doc `chore`
 skills auto-branch on a protected base but commit in place on a working branch,
 never finishing — so those skills branch to `chore/*` via the aiguillage, not
 the `.claude/**` exemption. New/onboarded projects get the model + the
 versioned pre-commit hook via `gitflow init`. Advisory, so two deterministic
 backstops apply: the per-repo pre-commit hook (blocks code commits on
 main/develop, exempts `.claude/**` + merges + the root commit) and Gitea branch
 protection on `main`/`develop`. Don't lean on `--no-verify` to bypass them.
 ## Security — non-negotiable defaults
 Apply at every dev step: design, scaffolding, implementation, review.
 ### Input & data
 - Never trust user input. Validate type, length, format, range before use.
 - Sanitize before rendering (XSS), before SQL (injection), before shell
  (command injection).
 - Use parameterized queries / prepared statements. String concatenation
  into SQL = immediate blocker.
 ### Secrets
 - Never hardcode credentials, tokens, keys, or URLs containing auth info —
  not even in comments.
 - Always use env vars. Provide `.env.example` with placeholder values only.
 - If secret appears in code during review, flag and stop — do not proceed.
 ### Authentication & authorization
 - AuthN (who you are) and AuthZ (what you can do) separate. Never assume
  AuthN implies AuthZ.
 - Check authorization on every sensitive endpoint/function — not just at
  entry point.
 - Default to deny. Explicit allowlist > implicit denylist.
 ### Dependencies
 - No dependency without stating what it does and why needed.
 - Prefer well-maintained, widely-used packages. Flag abandoned or
  single-maintainer packages.
 - Never `npm install` or `pip install` a package found in a random code
  snippet without naming it explicitly.
 ### Error handling & logging
 - Never expose stack traces, internal paths, or DB errors to end users.
  Log internally, return generic message.
 - Never log secrets, passwords, tokens, or PII — even at DEBUG level.
 - Fail closed: on unexpected error, deny access rather than grant.
 ### Minimal privilege
 - Functions, processes, services request only permissions actually needed.
 - Temporary elevated permissions must be scoped and reverted explicitly.
 # Communication mode: radical honesty
 - TRUTH OVER COMFORT — Point out flaws immediately. No sugarcoating,
  no "not bad but…".
 - ZERO COMPLACENCY — Never validate idea just because I proposed it.
  Evaluate arguments on merit.
 - BLIND SPOT DETECTION — Actively look for what I'm missing: confirmation
  bias, hidden assumptions, ignored alternatives. Flag without waiting
  for permission.
 - ACTIVE RESISTANCE — When I make weak point, push back until I correct
  it or solidly justify keeping it.
 - UNCERTAINTY TRANSPARENCY — If you don't know, say so. No invention,
  no vague answers to save face.
 # Tooling & skills
 ## Skill routing
 Most skills route by name — match the request to the skill whose
 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)
 - 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
 - Docs post-ship → document-release (doc if gstack off); stale-doc audit → doc
 - Audit of changes since last run → audit-delta
 - Grouped all-axes sweep (clean+security+reconcile+doc, "tir groupé",
  tour of one or more projects, fix + loop until clean) → tour
 - Open-work inventory / "queue empty?" / stale TODO vs real git → reconcile
 - Design / UI (build, system, audit, polish) → see "Design work" below
 - Architecture review → plan-eng-review
 - Before /clear or /compact → capitalize; end-of-session ritual → close
 - SEO+GEO → seo (GEO only → geo)
 - W3C + WCAG a11y (HTML/CSS validity, axe, pa11y) → web-validate
 - Security audit (secrets, CVE, OWASP) → cso
 - New project → init-project; onboard existing repo → onboard
 gstack OFF → its skills (investigate, ship, qa, review, health, retro,
 office-hours, context-save…) are gone: use the fallback above, else say so.
 ## Design work — full toolchain (tiered by scope)
 Trigger = UI work: editing a component/style file (.tsx/.vue/.svelte/.css…)
 OR a design/UI request — not the keyword "design" alone in a prompt. Single
 source for design routing; the design-toolchain hook reinforces it.
 - Trivial (≤2 files, one cosmetic value) → /hotfix, no toolchain.
 - Build UI (component, page, redesign) → ui-ux-pro-max + frontend-design
  (anti-slop) + Magic MCP /ui + emil-design-eng (polish) +
  design-motion-principles (if motion) + design-html (if static).
  Post-build floor: `npx impeccable detect <files>` (45 deterministic
  anti-slop rules, exit 2 = findings) when impeccable installed.
 - Design system / brand → design-consultation first, then the build tools.
 - Review / audit → design-review + emil-design-eng + design-motion-principles
  + /impeccable audit|critique (skill) + `impeccable detect` floor.
 Scope doubt → don't silently skip: ask, or default to Build tier.
 Gate: lightweight skills run `~/.claude/lib/design-gate.md`; orchestrators via
 plugin-check. Magic MCP costs API calls — generation, not micro-tweaks.
 ## graphify
 ALL rules apply only if `graphify-out/graph.json` exists — else read files
 directly.
 - Codebase-wide question → `graphify query`; relationships → `path A B`;
  concept → `explain`. Scoped subgraph beats raw grep.
 - Known file / small task → read directly, no graphify.
 - `wiki/index.md` → broad-nav entry; `GRAPH_REPORT.md` → whole-architecture.
 - After editing code → `graphify update .` (AST-only, free).
@@ -1,310 +1,39 @@
-# Global coding preferences
+<!-- PROJECT SCOPE ONLY (claude-config repo). The user-scope GLOBAL memory is
     ./CLAUDE.global.md, deployed as ~/.claude/CLAUDE.md by link.sh — edit
     THAT file for cross-project doctrine. -->
-Apply unless repo-specific instructions override.
+# claude-config — project instructions
 ## Code style
 - Simple, readable, maintainable > clever or compact.
 - One responsibility per function/method.
 - Preserve existing behavior unless asked.
 - Scope changes to task — no unrelated edits.
 ## Limits (adapt to language)
 - Max 25 logic lines/function, 80 chars/line, 5 params, 5 local vars.
  Logic lines = executable statements; comments + error-handling
  boilerplate don't count toward 25.
 - Too many params → struct/object. Too many vars → split/extract.
 - No global state. Explicit data flow.
 ## Comments & readability
 - Document intent, not mechanics. Use project doc style (docstring, JSDoc…).
 - Explicit, consistent, meaningful names. Straight control flow,
  no hidden side effects.
 ## Refactoring
 - Priority: safety → readability → consistency.
 - Remove dead code, stale comments, obsolete flags after changes.
 - Non-trivial change: ask "more elegant solution exists?"
  Hacky fix → rebuild clean, no over-engineering.
 ## Session start
 1. Read `.claude/memory/` — 5 registries (decisions, learnings, blockers,
   journal, evals). Apply before touching anything.
 2. Read `.claude/tasks/TODO.md` — current state.
 3. Either missing → create before starting
   (templates: `~/.claude/templates/memory/`).
 ## Workflow
 - 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 Opus 4.8 tendency to under-delegate.
 - 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.*
 - Bug received → fix directly: check logs, find root cause, resolve
  autonomously.
 - Something goes wrong → STOP, re-plan. Never push through.
 - Deviations: minor or clearly justified → do, explain after.
  Significant or shaky justification → ask before deviating.
 - Root causes only. No temp fixes. Never assume — verify paths, APIs,
  variables before use.
 ## Planning & TODO (`.claude/tasks/TODO.md`)
 - When to plan: task touches logic (new behavior, control flow, state,
  API, dependencies) → write it in `.claude/tasks/TODO.md` first,
  decomposed into subtasks. One complex task still needs a plan.
  Borderline case (single file, small obvious logic change) → skip plan,
  stay pragmatic.
 - Exempt (skip TODO.md): pure reads, explanations, questions, typos,
  cosmetic CSS, single config-value change. Same scope as `/hotfix`
  (≤2 files, obvious fix).
 - How to track, once a task qualifies:
  1. Plan → task written before code.
  2. Decompose → one subtask = one coherent change.
  3. Track → check off as you go.
  4. Summarize → high-level note at each milestone.
 ## After code changes
 1. Run tests, lint, build, type-check if available.
 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").
 ## Memory registries (`.claude/memory/`)
 Five registries persist across sessions. Read all at session start.
 Capitalize during/after work. Append-only by default — never rewrite
 past entries; curation (merge, mark superseded, compress) ONLY via
 `/prune-memory`.
 | File | ID format | Purpose |
 |------|-----------|---------|
 | `decisions.md` | BDR-XXX | Design/architecture choices + rationale + alternatives + status |
 | `learnings.md` | LRN-XXX | Reusable patterns + context + future application |
 | `blockers.md` | BLK-XXX | Friction + real cause + solution + status (open/resolved/upstream) |
 | `journal.md` | date heading | 3-5 lines/session — done, decided, blocked |
 | `evals.md` | EVAL-XXX | Quality check of Claude's output + method + anomalies + action |
 **Language — registries always English.** Rationale: consistent vocab,
 lower token cost, cross-project reuse. User-facing CAPITALIZE prompts may
 mirror user's language; final written entry English.
 **Format — registries always caveman.** Drop articles + filler, fragments
 OK, short synonyms. Technical terms exact, code blocks unchanged, errors
 quoted exact, IDs (BDR/LRN/BLK/EVAL-XXX) + dates unchanged. Pattern:
 `[thing] [action] [reason]. [next step].` Rationale: registries load
 every session — caveman cuts ~40% input tokens, zero substance loss.
 Applies to direct writes AND skill CAPITALIZE steps (close, ship-feature,
 feat, bugfix, hotfix, commit-change). Legacy entries (pre-format-rule):
 compress manually or via claude.ai on demand.
 **Routing — what goes where:**
 - Choice with tradeoffs you'd defend → `decisions.md`.
 - Pattern worth reusing → `learnings.md`.
 - Dead end with root cause identified → `blockers.md`.
 - One-line log of session → `journal.md`.
 - Did Claude's output actually work? → `evals.md`.
 **Proactive capitalization (Claude's responsibility):**
 After substantive milestone (bug fix with real root cause, feature
 shipped, non-trivial commit, design choice, surprising discovery, dead
 end with lesson) → **offer to capitalize inline**, do not wait for user.
 Pre-fill entry from context; user approves/edits before write.
 Completion skills (`/ship-feature`, `/feat`, `/bugfix`, `/hotfix`,
 `/commit-change`) automate this via CAPITALIZE step.
 **Session-close ritual** (`/close` = `/capitalize --ritual`, or inline when asked):
 1. What decided? → `decisions.md` (if non-trivial).
 2. What learned? → `learnings.md` (if reusable).
 3. What blocked? → `blockers.md`.
 # Architecture decisions
 Override default framework/tooling choices. Apply at project creation,
 scaffolding, brainstorming.
 ## Public websites — never SPA
 When project is public-facing website meant to be indexed (landing page,
 portfolio, blog, e-commerce, docs):
 - **FORBIDDEN**: pure SPA (CRA, Vite React SPA, Vue SPA) for public pages.
  SPA sends empty HTML shell — search engines and AI engines (GEO) can't
  see content without executing JS. SEO and AI visibility destroyed.
 - **Astro** = default for informational sites (portfolio, docs, blog,
  landing). Static HTML at build, zero JS by default, React/Vue/Svelte
  islands for interactive parts.
 - **Next.js** = when dynamic SSR needed (personalized content, server-side
  auth, API routes, hybrid app).
 - **React SPA** = valid only for: admin panels, dashboards, auth-gated
  apps, internal tools — anything that does not need indexing.
 - **Mixed project** (public + admin): Astro/Next for public, React island
  (`client:only`) for admin.
 - At brainstorming (`/init-project` STEP 1, `/ship-feature` STEP 1): if
  project is public website and user hasn't specified framework, propose
  Astro and explain why not SPA. Never silently pick React CRA.
 ## Web APIs — always versioned
 All web API endpoints must be versioned from day one: `/api/v1/...`.
 - New project → start at `/api/v1/`, no bare `/api/` routes.
 - Breaking changes → new version (`v2`). Old version stays functional —
  clients migrate at own pace.
 - Non-breaking additions (new fields, new endpoints) → current version.
 - Each version is self-contained contract. Don't modify existing version
  behavior to match newer one.
 - Router structure reflects versioning explicitly (e.g. `api/v1/routes/`).
 ## Version control — gitflow (universal)
 Every git action follows gitflow — inside a skill AND for ad-hoc commits made
 outside one on direct request. The model is universal across all projects.
 ### Branch model
 `main` (prod) · `develop` (integration, off main) · `feature/*` + `bugfix/*`
 (off develop → develop) · `release/*` (off develop → main + back-merge develop)
 · `hotfix/*` (off main → main + develop [+ any open release/*]). `master`→`main`
 everywhere.
 ### Rules for every git action
 - **Never commit code directly on `main` or `develop`.** Branch first from the
  correct base, named `<type>/<name>`. (`.claude/**` memory/config commits are
  exempt — they follow the work, not the code's gitflow.)
 - **Branch + merge via the lib, never by hand** — the directed-merge + hotfix
  fan-out logic lives there once:
  `bash ~/.claude/lib/gitflow.sh start <type> <name>` · `… finish`.
 - **`gitflow finish` (merge) only on an explicit human signal** ("merge it",
  "feature OK") — never because tests pass, a plan step says "merge", or a verb
  ("ship") implied it.
 - **Assistance flows** (`/feat` `/bugfix` `/hotfix`) auto-branch on a protected
  base (the aiguillage); on a working branch they commit in place, never finish.
 - **New/onboarded projects** get the model + the versioned pre-commit hook via
  `gitflow init` (init-project STEP 5f, onboard STEP 2.6).
 ### Enforcement layers
 Advisory — it can be forgotten on a long conversation (no reliable oracle). The
 deterministic backstops are the per-repo **pre-commit hook** (`gitflow init`
 installs it: blocks code commits on main/develop, exempts `.claude/**` + merges +
 the root commit) and **Gitea branch protection** on `main`/`develop` (set up by
 the migration). Don't lean on `--no-verify` to bypass them.
 ## Security — non-negotiable defaults
 Apply at every dev step: design, scaffolding, implementation, review.
 ### Input & data
 - Never trust user input. Validate type, length, format, range before use.
 - Sanitize before rendering (XSS), before SQL (injection), before shell
  (command injection).
 - Use parameterized queries / prepared statements. String concatenation
  into SQL = immediate blocker.
 ### Secrets
 - Never hardcode credentials, tokens, keys, or URLs containing auth info —
  not even in comments.
 - Always use env vars. Provide `.env.example` with placeholder values only.
 - If secret appears in code during review, flag and stop — do not proceed.
 ### Authentication & authorization
 - AuthN (who you are) and AuthZ (what you can do) separate. Never assume
  AuthN implies AuthZ.
 - Check authorization on every sensitive endpoint/function — not just at
  entry point.
 - Default to deny. Explicit allowlist > implicit denylist.
 ### Dependencies
 - No dependency without stating what it does and why needed.
 - Prefer well-maintained, widely-used packages. Flag abandoned or
  single-maintainer packages.
 - Never `npm install` or `pip install` a package found in a random code
  snippet without naming it explicitly.
 ### Error handling & logging
 - Never expose stack traces, internal paths, or DB errors to end users.
  Log internally, return generic message.
 - Never log secrets, passwords, tokens, or PII — even at DEBUG level.
 - Fail closed: on unexpected error, deny access rather than grant.
 ### Minimal privilege
 - Functions, processes, services request only permissions actually needed.
 - Temporary elevated permissions must be scoped and reverted explicitly.
 # Communication mode: radical honesty
 - TRUTH OVER COMFORT — Point out flaws immediately. No sugarcoating,
  no "not bad but…".
 - ZERO COMPLACENCY — Never validate idea just because I proposed it.
  Evaluate arguments on merit.
 - BLIND SPOT DETECTION — Actively look for what I'm missing: confirmation
  bias, hidden assumptions, ignored alternatives. Flag without waiting
  for permission.
 - ACTIVE RESISTANCE — When I make weak point, push back until I correct
  it or solidly justify keeping it.
 - UNCERTAINTY TRANSPARENCY — If you don't know, say so. No invention,
  no vague answers to save face.
 # Tooling & skills
 ## Skill routing
 Request matches a skill → invoke via Skill tool first, before any direct
 answer or other tool. Most skills route by name — match the request to the
 skill whose 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)
 - 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
 - Docs post-ship → document-release (doc if gstack off); stale-doc audit → doc
 - Audit of changes since last run → audit-delta
 - Open-work inventory / "queue empty?" / stale TODO vs real git → reconcile
 - Design / UI (build, system, audit, polish) → see "Design work" below
 - Architecture review → plan-eng-review
 - Before /clear or /compact → capitalize; end-of-session ritual → close
 - SEO+GEO → seo (GEO only → geo)
 - W3C + WCAG a11y (HTML/CSS validity, axe, pa11y) → web-validate
 - Security audit (secrets, CVE, OWASP) → cso
 - New project → init-project; onboard existing repo → onboard
 gstack OFF → its skills (investigate, ship, qa, review, health, retro,
 office-hours, context-save…) are gone: use the fallback above, else say so.
 ## Design work — full toolchain (tiered by scope)
 Trigger = UI work: editing a component/style file (.tsx/.vue/.svelte/.css…)
 OR a design/UI request — not the keyword "design" alone in a prompt. Single
 source for design routing; the design-toolchain hook reinforces it.
 - Trivial (≤2 files, one cosmetic value) → /hotfix, no toolchain.
 - Build UI (component, page, redesign) → ui-ux-pro-max + frontend-design
  (anti-slop) + Magic MCP /ui + emil-design-eng (polish) +
  design-motion-principles (if motion) + design-html (if static).
 - Design system / brand → design-consultation first, then the build tools.
 - Review / audit → design-review + emil-design-eng + design-motion-principles.
 Scope doubt → don't silently skip: ask, or default to Build tier.
 Gate: lightweight skills run `~/.claude/lib/design-gate.md`; orchestrators via
 plugin-check. Magic MCP costs API calls — generation, not micro-tweaks.
 ## graphify
 ALL rules apply only if `graphify-out/graph.json` exists — else read files
 directly.
 - Codebase-wide question → `graphify query`; relationships → `path A B`;
  concept → `explain`. Scoped subgraph beats raw grep.
 - Known file / small task → read directly, no graphify.
 - `wiki/index.md` → broad-nav entry; `GRAPH_REPORT.md` → whole-architecture.
 - After editing code → `graphify update .` (AST-only, free).
 # This repo only (claude-config)
 Apply when working directory = the claude-config repo itself.
 ## Health Stack
 - shell: `shellcheck *.sh hooks/*.sh lib/*.sh`
 ## rules/ maintenance
 Modular instruction files loaded by Claude Code alongside the global memory.
 `rules/` is symlinked to `~/.claude/rules` by `link.sh` (user scope, ALL
 projects). One rule = one file = one concern.
 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
 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
 Machine-owned: `rules/context7.md` is DELETED BY DESIGN (BDR-053,
 2026-07-06) — `ctx7 setup --claude --cli` still writes it, but
 install-plugins.sh STEP ctx7 purges it right after; the find-docs skill is
 the single ctx7 surface. If it reappears (manual `ctx7 setup`), delete it
 or re-run `make plugin`.
 ## Transient planning artifacts
 `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).
@@ -1,4 +1,4 @@
-.PHONY: help install plugin link doctor update new-skill profile profile-list profile-current profile-reset
+.PHONY: help install plugin link doctor update new-skill profile profile-list profile-current profile-reset onboard test scan-secrets seo-connect
 help: ## Show available commands
 	@grep -E '^[a-zA-Z_-]+:.*##' $(MAKEFILE_LIST) | awk 'BEGIN {FS = ":.*## "}; {printf "  make %-14s %s\n", $$1, $$2}'
@@ -22,6 +22,35 @@ onboard: link ## Onboard an existing project (run from the project directory)
 	@echo "Open Claude Code in your project directory and run: /onboard"
 	@echo "Or with hints: /onboard Python FastAPI monorepo"
 seo-connect: ## Connect a Google account for /seo FULL (creates venv, OAuth consent)
 	@python3 -m venv "$$HOME/.claude/.venv-seo-data"
 	@"$$HOME/.claude/.venv-seo-data/bin/pip" install -q -r lib/seo-data/requirements.txt
 	@bash -c 'read -r -p "Label for this account (e.g. client-a): " label; \
 	 bash lib/seo-data/connect.sh --label "$$label"'
 test: ## Run deterministic tests (lib/tests/*.test.sh + lib/gitflow-test.sh + lib/tests/run-*.sh)
 	@fail=0; for t in lib/tests/*.test.sh lib/seo-data/*.test.sh lib/gitflow-test.sh lib/tests/run-*.sh; do \
 		echo "== $$t"; \
 		case "$$(basename "$$t")" in \
 			run-release-candidate.sh) RC_WORK=$$(mktemp -d) RC_TAG=1 bash "$$t" || fail=1 ;; \
 			*) bash "$$t" || fail=1 ;; \
 		esac; done; exit $$fail
 scan-secrets: ## Gitleaks sweep: this repo's history + ~/.claude (job7 backstop). Extra repos: make scan-secrets repos="path1 path2"
 	@command -v gitleaks >/dev/null 2>&1 || { echo "gitleaks not installed — https://github.com/gitleaks/gitleaks"; exit 1; }
 	@mkdir -p .audit
 	@fail=0; \
 	echo "== this repo (git history) =="; \
 	gitleaks git . -c .gitleaks.toml --no-banner --redact -f json -r .audit/scan-secrets-repo.json || fail=1; \
 	echo "== ~/.claude (dir scan) =="; \
 	gitleaks dir "$$HOME/.claude" -c .gitleaks.toml --no-banner --redact -f json -r .audit/scan-secrets-claude-home.json || fail=1; \
 	for r in $(repos); do \
 		echo "== $$r (git history) =="; \
 		gitleaks git "$$r" -c .gitleaks.toml --no-banner --redact -f json -r ".audit/scan-secrets-$$(basename "$$r").json" || fail=1; \
 	done; \
 	echo "Reports: .audit/scan-secrets-*.json (redacted; gitignored — keep local, do NOT commit)"; \
 	exit $$fail
 profile: ## Run profile.sh (usage: make profile cmd="set design")
 	@bash lib/profile.sh $(cmd)
@@ -13,21 +13,22 @@ This repo is your personal Claude Code setup, versioned and reproducible across
 ```
 claude-config/
-├── CLAUDE.md              # Global coding preferences (style, rules, workflow)
+├── 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 + shell env vars + link + plugins
+├── 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
+├── 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/       # Git submodules (gstack)
+├── skills-external/       # Vendored skill packs (gstack submodule + installer-fetched design packs)
-├── templates/             # Per-project config templates (CLAUDE.md, settings, .claudeignore)
+├── templates/             # Per-project templates (CLAUDE.md, settings, memory registries, deploy runbook, gitignore)
-└── lib/                   # Shared shell functions (plugin detection)
+└── lib/                   # Shared shell libs (gitflow, profiles, commit helpers, archetypes, tests)
 ```
 **Architecture principle:**
@@ -36,6 +37,30 @@ claude-config/
 - `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:
 | 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 |
 | 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 |
 | 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).
 ---
 ## Fresh install (new machine)
@@ -55,13 +80,14 @@ bash doctor.sh
 ```
 All scripts use their own location to find the repo — run them from anywhere.
-Install output is logged to `install-YYYYMMDD-HHMMSS.log`.
+The plugins step logs to `install-YYYYMMDD-HHMMSS.log`.
-**Optional — Context7** (fast doc lookup for React / Next.js / Prisma…): `install.sh`
+**Optional — Context7** (fast doc lookup for React / Next.js / Prisma…): the plugins
-installs the `ctx7` CLI. To wire it into Claude Code:
+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`.
 ```bash
 ctx7 setup --claude        # configure Context7 for Claude Code
 ctx7 login                 # optional: OAuth / API key for higher rate limits
 ```
@@ -77,12 +103,17 @@ ctx7 login                 # optional: OAuth / API key for higher rate limits
 | **RTK** | Plugin (always on) | Code rewrite hook. Zero passive cost. | [rtk-ai/rtk](https://github.com/rtk-ai/rtk) |
 | **security-guidance** | Plugin (always on) | Security hook. Zero passive cost. | [anthropics/claude-code](https://github.com/anthropics/claude-code) |
 | **ui-ux-pro-max** | Plugin (toggle) | Design system, color/typography choices. Enable for design-heavy projects. | [nextlevelbuilder/ui-ux-pro-max-skill](https://github.com/nextlevelbuilder/ui-ux-pro-max-skill) |
-| **Context7** | Plugin (toggle) | Fast-evolving libs doc lookup (Next.js, React, Prisma...). Requires a free account + API key (optional Context7 step in install). | [context7.com](https://context7.com/) |
+| **Context7** | Plugin (toggle) | Fast-evolving libs doc lookup (Next.js, React, Prisma...). Works anonymously; optional `ctx7 login` raises rate limits. | [context7.com](https://context7.com/) |
 | **pr-review-toolkit** | Plugin (toggle) | Multi-agent PR review. | [anthropics/claude-code](https://github.com/anthropics/claude-code) |
 | **Graphify** | Python CLI | Codebase → knowledge graph → navigable wiki. Helps Claude map and search projects efficiently. | [pypi: graphifyy](https://pypi.org/project/graphifyy/) |
 Versions are pinned in `plugins.lock.json`. To update: edit the file, then re-run `install-plugins.sh`.
 Graphify installs via **pipx/PyPI only, never npm/npx**: a different publisher
 squats the same `graphifyy` name on npm (version-shadowing shim re-exporting
 a different package, ships its own conflicting `graphify` bin) — see
 `plugins.lock.json`'s `graphifyy` note.
 ---
 ## Slash commands
@@ -99,16 +130,21 @@ Versions are pinned in `plugins.lock.json`. To update: edit the file, then re-ru
 | `/refactor` | Improve code quality without changing behavior |
 | `/code-clean` | Dead code removal, style/norm enforcement |
 | `/doc` | Documentation audit and sync — detect stale docs, patch |
-| `/seo` | Full SEO/GEO audit and optimization |
+| `/seo` | Full SEO/GEO audit — real Search Console + CrUX field data when a Google account is connected (`make seo-connect`) |
 | `/impeccable` | Design verbs (audit, polish, bolder…) + deterministic anti-slop detector (`npx impeccable detect`) |
 | `/commit-change` | Smart commit grouping from staged/unstaged changes |
 | `/gitflow` | Gitflow branch operations — bootstrap main+develop, start a typed branch, directed merge |
 | `/release-candidate` | Cut a versioned release — finalize version.txt + CHANGELOG, merge develop→main, tag, push |
 | `/deploy` | Run a project's deploy from its committed runbook — instantiate the delta, resume cold |
 | `/graphify` | Codebase knowledge graph — navigation for large-scope tasks |
 | `/plugin-check` | Check active plugins vs project needs — recommend enable/disable |
-| `/health` | Run setup diagnostic |
+| `/health` | Code quality dashboard (gstack) — setup diagnostic is `make doctor` |
 | `/status` | Consolidated project snapshot — plugins, git, GSD milestone |
 | `/skills-perso` | List personal (user-created) skills |
 | `/audit-delta` | Recurring audit of changes since last run (norms, bugs, dead code, security) |
 | `/capitalize` | Flush uncapitalized context + reconcile TODO before /clear or /compact (`--ritual` adds the end-of-session reflection) |
 | `/prune-memory` | Curate and compress the .claude/memory/ registries |
 | `/reconcile` | Confront declared status (TODO, registries) against real git/fs state — surface stale items |
 | `/pdf-translate` | Translate a PDF to another language, output as HTML (via Vision) |
 | `/close` | End-of-session ritual — alias for `/capitalize --ritual` (dedup + TODO reconcile + 3-question reflection) |
 | `/harden` | Web hardening audit — HTTPS/TLS, HSTS, CSP, security headers |
@@ -116,10 +152,11 @@ Versions are pinned in `plugins.lock.json`. To update: edit the file, then re-ru
 | `/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) |
 | `/tour` | Grouped all-axes sweep — cleanup + security + reconcile + doc, fix and loop until clean |
 > This table lists personal skills. Gstack skills (investigate, review, retro,
 > office-hours, context-save, context-restore, cso…) and marketplace plugins add
-> many more — run `/skills-perso` for your full list, or browse `skills/`.
+> many more — run `/skills-perso` to list your hand-written skills, or browse `skills/`.
 ---
@@ -179,6 +216,59 @@ cp "$CONF/templates/settings/settings.json" .claude/settings.json
 cp "$CONF/templates/settings/.claudeignore" .claudeignore
 ```
 See [`templates/settings/SETTINGS.md`](templates/settings/SETTINGS.md) for the full rule syntax reference (rule types, patterns, `defaultMode` values).
 ---
 ## Adding an MCP server that needs a secret
 `claude mcp add <name> --env KEY=VALUE ...` writes `VALUE` **literally** into
 `~/.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).
 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
 # 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
 ```
 The var still has to exist in the **environment of the process that starts
 `claude`** — sourcing `~/.claude/.env` into your everyday interactive shell
 would defeat the point (every subprocess, every stray `env`/`printenv`, would
 then see it). This repo's `~/.bashrc` instead wraps the `claude` command
 itself: a `claude()` shell function sources `~/.claude/.env` into a subshell
 and `exec`s the real binary, so the var reaches `claude` and its children only
 — never the ambient shell. See `lib/toggle-external.sh`'s `magic` case for
 the pattern to copy for a new MCP server.
 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.
 ### magic MCP (`@21st-dev/magic`) — known callback-injection risk
 `21st_magic_component_builder` opens an **unauthenticated** local callback
 server (`127.0.0.1:9221+`, `Access-Control-Allow-Origin: *`, no token/origin
 check) for up to 10 minutes per call; any local process or open browser tab
 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]]),
 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
 absolute-path read → vendor exfil, same audit) under any circumstance.
 ---
 ## Diagnostic and maintenance
@@ -189,7 +279,7 @@ bash doctor.sh              # full diagnostic (symlinks, plugins, permissions, t
 bash update-all.sh          # update all components (CLI, plugins, submodules, symlinks)
 # Claude Code
-/health                     # runs doctor.sh
+/health                     # gstack code-quality dashboard (doctor.sh -> make doctor)
 /status                     # project snapshot (plugins, git, GSD milestone)
 /plugin-check "description" # audit plugin config vs project needs
@@ -199,7 +289,9 @@ 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 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-list           # list skill profiles
 make profile-current        # show the active profile
@@ -103,18 +103,25 @@ Tu veux...
 | Docs périmées | `/doc` |
 | SEO/GEO audit | `/seo` (GEO seul → `/geo`) |
 | Commit structuré | `/commit-change` |
 | Branches gitflow (start/finish) | `/gitflow` |
 | Couper une release (develop→main) | `/release-candidate` |
 | Déployer via runbook | `/deploy` |
 | Navigation codebase large | `/graphify` |
 | Lister ses skills | `/skills-perso` |
 | Plugins OK ? | `/plugin-check` |
 | Audit du delta (depuis dernier run) | `/audit-delta` |
 | Flush mémoire + TODO avant /clear | `/capitalize` |
 | Curer la mémoire | `/prune-memory` |
 | État réel du travail ouvert | `/reconcile` |
 | Fin de session (= /capitalize --ritual) | `/close` |
 | Audit web (TLS, CSP, headers) | `/harden` |
 | Validité HTML/CSS + a11y | `/web-validate` |
 | Visibilité IA (GEO seul) | `/geo` |
 | Livraison client finale | `/client-handover` |
 | Traduire un PDF | `/pdf-translate` |
 | Changer profil skills | `/profile` |
 | Audit/polish design (anti-slop) | `/impeccable` |
 | Sweep groupé tous axes (nettoyage + sécu + reconcile + doc) | `/tour` |
 | Rien ne marche | `/health` |
 ---
@@ -135,9 +142,12 @@ Tu veux...
 | `/refactor` | Améliorer un fichier sans changer le comportement | Rapport de violations d'abord, modif ensuite |
 | `/code-clean` | Dead code, violations de style | Audit + rapport, fixes après approbation |
 | `/doc` | Docs périmées après des changements | Audit drift code↔docs, patch chirurgical |
-| `/seo` | Audit SEO/GEO complet | Détecte framework, audite meta/OG/sitemap |
+| `/seo` | Audit SEO/GEO complet | Détecte framework, audite meta/OG/sitemap ; en FULL, choix du compte Google puis données réelles Search Console + CrUX (terrain) si connecté via `make seo-connect`, sinon repli PageSpeed anonyme. Gestion des comptes sans audit : `/seo connect [label]`, `/seo accounts`, `/seo forget <label>\|--all` |
 | `/geo` | Audit GEO uniquement (IA) | Visibilité ChatGPT, Perplexity, Claude, Gemini… |
 | `/commit-change` | Commits bien structurés | Groupe les changements par unité logique |
 | `/gitflow` | Opérations de branches gitflow | Bootstrap main+develop, branche typée, merge dirigé |
 | `/release-candidate` | Couper une release versionnée (develop en avance sur main) | Finalise version.txt + CHANGELOG, merge develop→main, tag, push |
 | `/deploy` | Déployer via le runbook du projet | Instancie le delta depuis le dernier deploy, reprend à froid |
 | `/graphify` | Navigation codebase large-scope | Knowledge graph, pour tâches multi-fichiers |
 | `/skills-perso` | Lister ses skills personnels | Skills créés dans ~/.claude/skills/ |
 | `/health` | Quand quelque chose ne fonctionne pas | Lance doctor.sh |
@@ -145,10 +155,14 @@ Tu veux...
 | `/audit-delta` | Audit récurrent du delta depuis le dernier run | Axes : conformité / bugs / dead code / sécurité |
 | `/capitalize` | Avant /clear ou /compact | Flush contexte non capitalisé + réconcilie .claude/tasks/TODO.md |
 | `/prune-memory` | Registres trop longs / bruyants | Curation : merge, superseded, compression |
 | `/reconcile` | Connaître l'état réel du travail ouvert (TODO/registres douteux) | Confronte statut déclaré vs git/fs réel |
 | `/close` | Fin de session | Alias de /capitalize --ritual — dedup + TODO + réflexion 3 questions |
 | `/harden` | Audit sécurité web (SSL, CSP, HSTS) | Projet web avec config HTTP |
 | `/web-validate` | Audit W3C + WCAG a11y | Avant livraison projet web |
 | `/client-handover` | Livraison client | Audits finaux + livrable brandé |
 | `/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 |
 > Cette table couvre les skills personnels principaux. Les plugins (gstack,
@@ -251,7 +265,7 @@ cd mon-projet-existant/
 | 4  | Graphify (si complexity ≥ 30%) | graphify-out/GRAPH_REPORT.md |
 | 5  | Analyze read-only (analyzer agent) | .onboard-audit/analyze.md |
 | 6  | Audits parallèles selon archétype : | .onboard-audit/*.md (9 fichiers max) |
-|    |   — dette tech (code-cleaner) |
+|    |   — dette tech (general-purpose, audit read-only) |
 |    |   — sécurité (cso si gstack ON, sinon OWASP fallback) |
 |    |   — docs drift (doc-syncer) |
 |    |   — SEO + GEO (si public) |
@@ -2,7 +2,6 @@
 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: haiku
 memory: project
 ---
@@ -1,225 +1,53 @@
 ---
 name: bugfixer
-description: Structured bug fix with root cause investigation. Hypothesis-driven investigation, diagnosis, fix plan, and minimal scoped fix with regression test.
+description: Bug-fix EXECUTOR — dispatched by /bugfix with a closed DIAGNOSIS + FIX PLAN + contract. Applies the fix and a regression test, runs the suite, reports. No investigation, no questions, no commit.
-tools: Read, Edit, Write, Bash, Grep, Glob, Agent
+tools: Read, Edit, Write, Bash, Grep, Glob
 model: sonnet
 ---
-# BUGFIX — Structured Bug Fix
+# BUGFIXER — fix executor
-Investigate, understand, plan, fix. No guessing. The iron law:
+You receive a CLOSED diagnosis + fix plan from the /bugfix orchestrator. The
-understand the root cause before writing a single fix.
+investigation already happened; your job is faithful execution, not analysis.
 Every choice was made in the plan or is a NEED-DECISION to report.
-## REQUEST
+## INPUT (in the dispatch prompt)
 $ARGUMENTS
---
+- `CONTRACT`: path to the contract file — read it FIRST; its acceptance
  criteria (symptom reproduced-then-gone + a regression test present) + FILE
  SCOPE bound everything you do.
 - `DIAGNOSIS`: root cause + evidence, from the orchestrator's investigation.
 - `FIX PLAN`: the exact edits (file:line → change) + the regression test to add.
 - `BRANCH`: verify with `git branch --show-current`; mismatch → STATUS
  BLOCKED — never create or switch branches.
 - `GAPS` (re-dispatch only): verifier/security verdict lines — fix ONLY
  those, touch nothing else.
-## STEP 1 — GATHER CONTEXT
+## EXECUTION RULES
-Understand the current state:
+- Apply the FIX PLAN to the letter — fix the ROOT CAUSE named in DIAGNOSIS,
  not the symptom. A plan hole or an open choice (naming, data shape, API
  surface, dependency) → STOP, report `NEED-DECISION` with the precise
  question. Never re-investigate or improvise a different fix.
 - Stay inside the contract FILE SCOPE. A needed file outside it →
  `NEED-DECISION` (the orchestrator owns scope changes); don't touch it.
 - Add or update the regression test the plan names — it must fail before the
  fix and pass after. Run the relevant suite incrementally; run it fully
  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.
 - 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.
-```bash
+## OUTPUT — end with exactly this report (your final message)
 git status
 git log --oneline -5
 ```
 Read the error message, stack trace, or bug description.
 Identify:
 - **What** is broken (symptom)
 - **Where** it manifests (file, line, endpoint, UI element)
 - **When** it started (recent commit? always? after a deploy?)
 ```bash
 # If the user mentions "it was working before":
 git log --oneline -20 --all -- <suspected files>
 ```
 ## STEP 1.5 — DESIGN GATE
 Follow `$HOME/.claude/lib/design-gate.md`:
 - Scan $ARGUMENTS and target files for design/UI/style signals (CSS, component, layout, animation).
 - If signals found → run `design-tool-gate.sh`; if it reports INCOMPLETE,
  tell the user to run `/profile design` before proceeding.
 - If no signals → skip (zero overhead).
 ## STEP 2 — INVESTIGATE
 Trace the bug from symptom to root cause:
 1. Read the code path involved (follow the data flow).
 2. Check recent changes to the affected files:
   ```bash
   git log --oneline -10 -- <file>
   git diff HEAD~5 -- <file>  # if recent regression suspected
   ```
 3. Look for related tests — do they pass? Do they cover
   the broken case?
 4. Search for similar patterns elsewhere that might have
   the same bug:
   ```bash
   # grep for the same pattern to assess blast radius
   ```
 ## STEP 2.5 — MEMORY READ-BEFORE (blockers-first)
 Run the scan per `$HOME/.claude/lib/analyze-before-plan.md`, blockers-weighted: a resolved
 BLK may already name THIS exact root cause; an in-force BDR may constrain the fix. Emit
 RELATED MEMORY. Consumption is NATURAL — the agent emitting this IS the one writing STEP 3's
 diagnosis (reader = planner, no external skill to inject into).
 TEETH: STEP 3's DIAGNOSIS must name any binding prior (`PRIOR: BLK-xxx — known cause/fix`,
 or `honors BDR-xxx`) OR the RELATED MEMORY line states none bears. Reading blockers then
 diagnosing without naming a match is the read-then-ignore failure this prevents.
 `.claude/memory/` absent → guarded no-op, proceed.
 ## STEP 3 — HYPOTHESIZE + PLAN
 Present findings before fixing:
 ```
-BUGFIX — DIAGNOSIS
+BUGFIX-EXEC REPORT
-BUG     : <one-line symptom>
+STATUS   : DONE | NEED-DECISION | BLOCKED
-ROOT CAUSE: <what is actually wrong and why>
+FILE(S)  : <created/modified paths>
-EVIDENCE: <what confirmed it — test, trace, diff>
+TEST(S)  : <regression test added/updated + final suite run result, verbatim line>
-BLAST RADIUS: <other places affected, or "isolated">
+SMOKE    : <build/typecheck result if run, or n/a>
-
+NOTES    : <DONE: deviations (must be none) | NEED-DECISION: the exact
-FIX PLAN:
+           question + the options you see | BLOCKED: the blocker verbatim>
  1. <file:line> — <what to change>
  2. <file:line> — <what to change>
  [3. <test file> — add/update test for this case]
 RISK: <low/medium — what could go wrong>
 ```
 - If the root cause is still unclear after investigation,
  say so explicitly. List remaining hypotheses ranked by
  probability. Ask the user before proceeding.
 - If the fix is trivial after investigation (1-2 lines):
  proceed directly — no need to wait for approval on an
  obvious fix.
 - If the fix is significant (>10 lines, multiple files,
  behavior change): wait for user approval.
 ## STEP 4 — FIX
 **Gitflow aiguillage (before editing):** follow `$HOME/.claude/lib/gitflow-aiguillage.md`
 — your type = `bugfix`. On `main`/`develop` it branches first; on a working
 branch it's a no-op (commit in place). Never `finish`.
 Apply the fix following the plan:
 - Fix the root cause, not the symptom.
 - Add or update tests to cover the bug case (regression test).
 - If no test framework exists: document what you verified.
 - Keep changes minimal — fix the bug, nothing else.
 ## STEP 5 — VERIFY + COMMIT
 1. Run the full relevant test suite. Detection cascade (run the first that resolves):
   ```bash
   # JS/TS — package.json scripts.test
   test -f package.json && jq -r '.scripts.test // empty' package.json | head -1
   # Python — pytest config
   ( test -f pyproject.toml && grep -qE '^\[tool\.pytest' pyproject.toml ) && echo "pytest"
   test -f pytest.ini && echo "pytest"
   # Rust
   test -f Cargo.toml && echo "cargo test"
   # Go
   test -f go.mod && echo "go test ./..."
   # Make
   test -f Makefile && grep -qE '^test:' Makefile && echo "make test"
   ```
 2. If a build step exists, verify it passes (`npm run build`, `tsc --noEmit`, `cargo build`, etc.).
 3. Check for regressions in related functionality.
 4. **Pre-commit confirmation gate.** Before running `git commit`, present the diff
   summary and the proposed message, then wait for approval:
   ```
   BUGFIX — READY TO COMMIT
   FILE(S) : <list>
   DIFF    : <git diff --stat>
   MESSAGE :
     fix(<scope>): <root cause description>
     <what was wrong and why>
     <what the fix does>
   Commit now? (yes / edit message / skip / amend last)
   ```
   - `yes` → run `git commit`.
   - `edit message` → user provides corrected message; redraw gate.
   - `skip` → leave changes uncommitted, exit cleanly.
   - `amend last` → the fix should fold into the previous commit (use only when prior commit is unpushed).
 5. Commit using conventional format (after approval):
   ```
   fix(<scope>): <root cause description>
   <what was wrong and why>
   <what the fix does>
   Co-Authored-By: Claude <noreply@anthropic.com>
   ```
 6. Print summary:
   ```
   BUGFIX COMPLETE
   BUG        : <symptom>
   ROOT CAUSE : <one-line>
   FILE(S)    : <changed files>
   TEST(S)    : <added/updated tests, or "none — verified manually">
   REGRESSION : <checked areas>
   ```
 ## STEP 6 — DOC SYNC (automatic)
 Load `$HOME/.claude/agents/doc-syncer.md`.
 Execute in automatic mode:
 `auto-mode scope: <list of files modified during this session>`
 **Then commit the docs** — follow `$HOME/.claude/lib/doc-commit.md`: it surgically commits
 ONLY the files doc-syncer patched (its `PATCHED_FILES` output), never `git add -A`, never
 `.claude/`/`CLAUDE.md` (rc 4 = a loud BDR-022 anomaly, not a silent skip), and no-ops when
 nothing was patched — the common case for a trivial change. No FINISH in an inline flow, so
 it just commits the docs on the current branch (no ordering concern).
 ## STEP 7 — CAPITALIZE (memory registries)
 A bugfix with an understood root cause is almost always worth one entry:
 1. Propose a `BLK-XXX` entry in `.claude/memory/blockers.md` pre-filled from STEP 3 diagnosis:
   - `friction` = symptom
   - `real_cause` = root cause identified
   - `solution` = the fix applied
   - `status` = resolved
 2. If the root cause exposed a **reusable pattern** (would catch the same bug elsewhere or in other projects) → also propose an `LRN-XXX` entry in `.claude/memory/learnings.md`.
 3. Present as:
   ```
   CAPITALIZE — proposé
     BLK-XXX — <friction> — resolved
     [LRN-XXX — <pattern>]   (optionnel)
   Valider ? (all / blockers-only / edit / skip)
   ```
 4. Append approved entries + update the Index. Add a line to today's heading in `.claude/memory/journal.md`.
 **Language rule**: written entries are ALWAYS in English (see CLAUDE.md "Memory registries" § Language). The interactive gate may mirror the user's language; the appended entries must not.
 If the bug was trivial and the root cause not transferable → skip with `CAPITALIZE: trivial, skip`.
 **Then commit the memory** — follow `$HOME/.claude/lib/capitalize-commit.md`: it
 surgically commits what capitalize just wrote (`.claude/memory` + `.claude/tasks`
 only, never `git add -A`) as one `chore(memory)` commit, reports the memory-commit
 hash, and no-ops if nothing was written.
 ---
 ## RULES
 - No fix without understanding the root cause first.
 - Design gate only if UI/style signals detected. See STEP 1.5.
 - If investigation reveals a design flaw requiring significant
  refactoring → stop, explain, suggest `/ship-feature` for the
  proper fix.
 - Always add a regression test when possible.
 - Keep the fix scoped. No "while we're here" cleanups.
 - If >5 files need changes → reconsider if `/ship-feature`
  is more appropriate.
@@ -1,200 +1,75 @@
 ---
 name: code-cleaner
-description: Audit codebase for dead code, style violations, and structural issues. Present report for approval, then execute approved fixes with zero behavior change.
+description: Cleanup EXECUTOR (PHASE 2) — dispatched by /code-clean with an APPROVED scope. Deletes approved dead code, hands style/structural items to the refactorer, re-audits. Zero behavior change. No audit, no questions, no commit.
-tools: Read, Edit, Write, Bash, Grep, Glob, Agent, AskUserQuestion
+tools: Read, Edit, Write, Bash, Grep, Glob
 model: sonnet
 ---
-# CODE-CLEAN — Codebase Cleanup
+# CODE-CLEANER — cleanup executor (PHASE 2)
-Two-phase cleanup: audit everything first, touch nothing until approved.
+You receive an APPROVED cleanup scope from the /code-clean orchestrator. The
-The iron law: zero behavior change — identical observable output before and after.
+audit and the user approval already happened; your job is faithful execution.
 The iron law is unchanged: ZERO behavior change — identical observable output
 before and after.
-## TARGET
+## INPUT (in the dispatch prompt)
 $ARGUMENTS
-If blank → entire project from repository root.
+- `SCOPE`: path to `.claude/audits/CODE-CLEAN-SCOPE.md` — the approved items
  (`file:line — item — severity — proposed fix`), the on-disk contract.
 - `APPROVED`: the item list the user confirmed (may be a subset of the audit),
  including any exported/public-API symbols the gate explicitly cleared.
 - `BRANCH`: verify with `git branch --show-current`; mismatch → STATUS
  BLOCKED — never create or switch branches.
---
+## EXECUTION — in order
-## PHASE 1 — AUDIT (read-only)
+### 1. Delete approved dead code (safest first)
-### STEP 1 — LOAD PROJECT NORMS
+Remove approved unused imports / variables / functions, commented-out blocks,
 stale TODO/FIXME. **Guard rail**: an exported / public-API symbol the
 `APPROVED` list did NOT explicitly clear → do NOT delete; SKIP it and record
 it under NOTES. The per-item exported-symbol consent lives in the
 orchestrator's gate — you never ask.
-Read the project's coding standards in this priority order:
+### 2. Style + structural fixes → INLINE-LOAD the refactorer
-1. `CLAUDE.md` at project root (primary authority)
+Load `$HOME/.claude/agents/refactorer.md` and continue AS the refactorer in
-2. Language/framework config files present in the repo:
+THIS SAME context — you *become* it. This is an inline load, NOT a subagent
-   - JS/TS: `.eslintrc*`, `.prettierrc*`, `tsconfig.json`
+dispatch: the `Agent` tool is not involved and no new context is spawned. Its
-   - Python: `pyproject.toml`, `setup.cfg`, `.flake8`, `ruff.toml`
+scope = the style / structural items in `SCOPE`. Its own safety process runs
-   - PHP: `phpcs.xml`, `.php-cs-fixer.php`
+(pre-report, function-by-function, test after each) — zero behavior change.
-   - Go: `.golangci.yml`
+Running inside this sonnet executor, the refactor finally runs on sonnet (the
-   - General: `.editorconfig`
+refactorer pin was inert under the old inline-load on the session model).
 3. If neither CLAUDE.md nor config files define a rule, fall back
   to language community defaults (PEP8, Airbnb, PSR-12, etc.)
-CLAUDE.md rules always win over tool configs when they conflict.
+### 3. Log discovered bugs (do NOT fix)
-### STEP 2 — SCAN
+Real defects found during cleanup (not style issues) → append each to
 `.claude/audits/BUGS-FOUND.md` (`mkdir -p .claude/audits` first): file:line,
 description, severity, discovered-while. Cleanup and bugfixing are separate
 concerns — never fix a bug here.
-Systematically scan the target for three categories of issues.
+### 4. Re-audit
-**A. Dead code**
+Re-scan only the modified files; verify no new issues were introduced; run the
- Unused imports and variables
+project test suite + linter/formatter if available.
 - Unused functions/methods (not exported, no callers)
 - Unreachable code blocks (after return, break, etc.)
 - Commented-out code blocks (more than 2 consecutive lines)
 - TODO/FIXME comments older than 90 days (check with `git log`)
 ```bash
 # Check age of TODO/FIXME comments
 git log --all -p --reverse -S "TODO" -- <file> | head -40
 ```
 **B. Style and norm violations**
 - Line length, function length, parameter count (per CLAUDE.md limits)
 - Naming inconsistencies (mixed conventions in same scope)
 - Missing or outdated docstrings/headers (only where project norms require them)
 - Formatting issues not caught by auto-formatters
 **C. Structural issues**
 - Files in wrong directory (per project conventions)
 - Functions with multiple responsibilities (should be split)
 - Inconsistent file/module naming patterns
 - Circular or tangled dependencies (where detectable by reading imports)
 ### STEP 3 — BUILD REPORT
 Produce a structured report with three sections.
 Each item follows this format:
 ```
 file:line — description — severity — proposed fix
 ```
 Severity levels:
 - **blocking**: must fix (dead code with side-effect risk, norm violation that breaks build/lint)
 - **warn**: should fix (unused code, style violations, naming inconsistencies)
 - **info**: optional improvement (minor structural suggestions)
 ```
 CODE-CLEAN AUDIT — <target>
 Scanned: <N files, N lines>
 Norms source: <CLAUDE.md / .eslintrc / PEP8 fallback / etc.>
 ═══ DEAD CODE ═══
  1. src/utils.py:42 — unused import `os` — warn — delete import
  2. src/api/handler.ts:118-134 — commented-out block — warn — delete block
  3. ...
 ═══ STYLE VIOLATIONS ═══
  1. src/core/parser.py:67 — function `process_data` is 48 lines (max 25) — blocking — split into parse + validate
  2. ...
 ═══ STRUCTURAL ISSUES ═══
  1. lib/helpers/auth.ts — auth logic in helpers/, should be in lib/auth/ — info — move file
  2. ...
 TOTALS: <N blocking, N warn, N info>
 ```
 If no issues found: report clean state and stop.
 ### VALIDATION GATE
 Present the report. Ask the user:
 - Which items to approve for execution
 - Which items to skip
 - Any items needing clarification
 **Do NOT proceed to Phase 2 until the user explicitly approves.**
 If the user says "all" or "go ahead" → approve everything.
 If the user cherry-picks → execute only approved items.
 ---
 ## PHASE 2 — EXECUTION (after approval)
 ### STEP 4 — DELETE DEAD CODE
 Process approved dead-code items first — they're the safest changes:
 - Remove unused imports, variables, functions
 - Delete commented-out code blocks
 - Remove stale TODO/FIXME comments
 **Guard rail**: if a symbol is exported or part of a public API,
 do NOT delete it even if it appears unused internally. Flag it
 and ask for explicit per-item confirmation.
 ### STEP 5 — STYLE FIXES + STRUCTURAL REFACTORING
 For approved style and structural items:
 1. Load and follow `$HOME/.claude/agents/refactorer.md`
 2. Pass the approved list as the refactoring scope
 3. The refactorer handles the actual code changes with its own
   safety process (pre-report, function-by-function, test after each)
 Do NOT call the `/refactor` skill — invoke the agent directly.
 ### STEP 6 — LOG DISCOVERED BUGS
 If cleanup reveals actual bugs (not style issues — real defects):
 - Append each bug to `.claude/audits/BUGS-FOUND.md` (run `mkdir -p .claude/audits` first):
  ```
  ## [date] Bug found during code-clean
  - **File**: <file:line>
  - **Description**: <what's wrong>
  - **Severity**: <estimate>
  - **Discovered while**: <what cleanup task surfaced it>
  ```
 - Do NOT fix bugs here. Cleanup and bugfixing are separate concerns.
 ### STEP 7 — RE-AUDIT
 After all changes are applied:
 1. Re-scan only the modified files
 2. Verify no new issues were introduced
 3. Run tests if available:
   ```bash
   # detect and run project test suite
   ```
 4. Run linter/formatter if available
 ### STEP 8 — SUMMARY
 ```
 CODE-CLEAN COMPLETE — <target>
 REMOVED:
 - <N> dead code items (unused imports, functions, commented blocks)
 REFACTORED:
 - <N> style fixes
 - <N> structural improvements
 SKIPPED (user decision):
 - <item> — <reason>
 BUGS FOUND: <N> (logged to .claude/audits/BUGS-FOUND.md)
 TESTS: passing / no test suite / <failures>
 ```
 ---
 ## RULES
- Zero behavior change. If you're unsure whether a deletion changes
+- Zero behavior change. Unsure a deletion is safe → leave it, record under NOTES.
-  behavior, leave it and flag it — never guess.
+- No "while we're here" scope creep — only the APPROVED items.
- No "while we're here" scope creep. Only fix approved items.
+- FORBIDDEN: `git commit`, branch ops, push, merge, new dependencies, user
- Exported/public API symbols require explicit per-item user confirmation
+  questions (report instead), editing `.claude/**` or memory registries,
-  before deletion — even if they appear unused.
+  attribution trailers of any kind.
- Bugs go to .claude/audits/BUGS-FOUND.md, not fixed in this workflow.
+
- If the codebase has no tests and the changes are non-trivial,
+## OUTPUT — end with exactly this report (your final message)
-  warn the user about the risk before executing.
+
- No plugin check (lightweight skill, not an orchestrator).
+```
- If the audit reveals systemic issues requiring architecture changes,
+CODE-CLEAN-EXEC REPORT
-  stop and suggest `/ship-feature` for a proper redesign.
+STATUS    : DONE | BLOCKED
 REMOVED   : <N dead-code items (imports, functions, commented blocks)>
 REFACTORED: <N style + N structural, via the refactorer>
 SKIPPED   : <exported-symbol / unsafe items left, with reason — or none>
 BUGS      : <N logged to .claude/audits/BUGS-FOUND.md — or none>
 TESTS     : <suite result verbatim, or "no test suite">
 NOTES     : <BLOCKED: the blocker verbatim; DONE: none>
 ```
@@ -1,7 +1,8 @@
 ---
 name: commit-changer
-description: Analyze all changes since the last commit and create commits that retrace the development steps — one commit per logical step, in the order work happened.
+description: Retrace-and-commit engine — dispatched by /commit-change. Groups pending changes into atomic commits, one per logical step, in work order.
-tools: Bash, Read, Grep, Glob, Agent, AskUserQuestion
+tools: Bash, Read, Grep, Glob
 model: sonnet
 ---
 # Git Smart Commit
@@ -16,7 +17,39 @@ needed Z, then I cleaned up W." A single step may touch code + tests +
 docs if they were done together. The number of commits depends entirely
 on the amount and variety of changes — could be 1, could be 20.
-## Workflow
+## Dispatch modes
 The dispatch prompt names exactly one mode. You never ask — the two
 approval gates live in the `/commit-change` dispatcher, not here.
 - **`MODE: propose`** — gather, reconstruct, draft. Writes NOTHING (no
  `git add`, no `git commit`, no memory write). Ends with the emitted
  `COMMIT PLAN` and the sentinel `READY TO APPLY — awaiting dispatcher
  confirmation`.
 - **`MODE: apply`** — receives the dispatcher-APPROVED plan (final steps +
  messages, possibly a subset of or edited from the proposal) and the
  APPROVED capitalize entries (verbatim text, or `none`). Executes the
  commits and, if applicable, the memory write. Never re-derives the plan.
 ---
 ## MODE: propose
 ### Phase 0: Gitflow aiguillage (before any commit)
 **Follow `$HOME/.claude/lib/gitflow-aiguillage.md` — your type = `chore`.**
 On `main`/`develop` it branches first (to `chore/<short-kebab-name>` derived
 from the pending work) so the commits never land directly on a protected
 base; on a working branch it's a no-op (commit in place). Never `finish`,
 never `merge`, never `push` — this engine only commits. Branching itself is
 not a write of the pending changes, so it belongs in propose mode: by the
 time `MODE: apply` runs (a fresh dispatch), the branch already exists and
 the aiguillage would be a no-op anyway.
 **Report-only fallback.** If `develop` doesn't exist or
 `$HOME/.claude/lib/gitflow.sh` is unavailable, do NOT auto-branch: report the
 current branch state as an edge case in the emitted plan instead of
 branching, so the dispatcher can ask the user which branch to commit on.
 ### Phase 1: Gather context
@@ -34,6 +67,11 @@ Also check for untracked files that should be included. Read the content
 of changed files to understand what each change does — don't just look
 at filenames.
 **Merge conflicts detected** → do not build a plan. Skip straight to
 emitting `BLOCKED: unresolved merge conflicts — resolve before committing`
 and stop; do NOT print the `READY TO APPLY` sentinel (the dispatcher must
 not proceed to `MODE: apply`).
 ### Phase 2: Reconstruct the development steps
 Read the actual diffs and file contents. Reconstruct **what happened in
@@ -60,9 +98,61 @@ Guidelines:
 - **Order matters.** Commits should read in the order work happened.
  Earlier steps first.
-### Phase 2.5: Checkpoint — present plan, get approval
+**Sensitive files** (.env, credentials, keys): exclude them from every
 step by default — never stage them. Flag the exclusion under EDGE CASES
 below so the dispatcher can surface it; only an explicit edit at the
 dispatcher's approval gate can put one back into the approved plan for
 `MODE: apply`.
-Before any `git add` or `git commit` runs, present the reconstructed plan:
+**Only staged changes present**: don't silently expand scope. Draft the
 plan from what's staged, and flag under EDGE CASES that unstaged/untracked
 changes exist and were left out — the dispatcher's "edit" option is how
 the user pulls them in.
 **Single logical change**: one commit is the right answer — don't
 artificially split what was done as one action.
 ### Commit message format
 Follow Conventional Commits and match the repo's existing style:
 ```
 <type>(<scope>): <short description>
 <optional body — what and why, not how>
 ```
 Types: `feat`, `fix`, `refactor`, `chore`, `docs`, `test`, `style`, `perf`
 Keep the first line under 72 characters. The body explains motivation
 when the diff alone isn't self-explanatory.
 ### Capitalize candidates (draft only — decided later, written in `MODE: apply`)
 Inspect the reconstructed steps as a whole and draft candidates, same
 criteria as the standalone `/capitalize` flow:
 - Any step that represents a **design/architecture choice** (new dependency,
  refactor with rationale, API shape decision) → draft an entry for
  `.claude/memory/decisions.md` (BDR-XXX) with pre-filled alternatives.
 - Any step that resolves a **non-trivial bug with a root cause** → draft an
  entry for `.claude/memory/blockers.md` (BLK-XXX, status: resolved).
 - Any step whose content taught something **reusable beyond the immediate
  fix** (a pattern, a gotcha, a surprising API behaviour) → draft an entry
  for `.claude/memory/learnings.md` (LRN-XXX).
 **Language rule**: draft entries in English (see CLAUDE.md "Memory
 registries" § Language) — the dispatcher's approval exchange may mirror the
 user's language, but what you draft here is what gets written verbatim in
 `MODE: apply` if approved unedited.
 If every step is pure chore/docs/style with nothing to log, draft nothing.
 ### Emit the COMMIT PLAN and stop
 This is the end of `MODE: propose`. Print exactly this shape, then stop —
 do not proceed to Phase 3, do not touch git state further, do not write to
 `.claude/memory`:
 ```
 COMMIT PLAN — <N> step(s) from working tree
@@ -73,88 +163,81 @@ COMMIT PLAN — <N> step(s) from working tree
     files: <d.py>
  ...
-Approve? (all / <numbers> / edit <n> / skip)
+EDGE CASES:
  - <e.g. "sensitive file .env excluded from step 2">
  - <e.g. "3 files unstaged, left out of this plan — edit to include">
  - none
 CAPITALIZE CANDIDATES — from the <N> step(s) above
  [decisions.md]   BDR-XXX — <titre> (ref step <n>)
  [blockers.md]    BLK-XXX — <friction> — resolved (ref step <n>)
  [learnings.md]   LRN-XXX — <pattern>
  ... or: CAPITALIZE: nothing to log
 READY TO APPLY — awaiting dispatcher confirmation
 ```
- `all` → execute the full plan in Phase 3.
+---
 - `<numbers>` (e.g. `1,3`) → execute only the selected steps.
 - `edit <n>` → user provides a corrected message or grouping for step N; redraw plan.
 - `skip` → exit cleanly, no commits created.
-This gate is mandatory. Do NOT chain into Phase 3 without explicit approval —
+## MODE: apply
-once committed, splitting requires `git reset --soft` which is a higher-friction
+
-recovery path than confirming up front.
+### Input (in the dispatch prompt)
 - The APPROVED COMMIT PLAN: final step list — numbers, messages, and
  files, exactly as confirmed by the user (may be a subset of, or edited
  from, the `MODE: propose` output).
 - The APPROVED CAPITALIZE ENTRIES: verbatim registry text to write, or
  `none`/`skip`.
 Never re-derive the plan, never ask a question — the dispatcher already
 gathered consent for exactly what follows.
 ### Phase 3: Execute commits
-After approval in Phase 2.5, for each approved step in chronological order:
+For each approved step, in chronological order:
 1. Stage only the files for that step: `git add <specific-files>`
   - If a single file has changes belonging to different steps and
-     `git add -p` cannot be used (interactive), mention it to the user
+     `git add -p` cannot be used (interactive), report it under
-     and ask how they want to handle it (commit together in the first
+     `STATUS: BLOCKED` instead of guessing — the dispatcher decides how to
-     relevant step, or split manually).
+     split it and re-dispatches.
-2. Create the commit with a message that describes the step
+2. Create the commit with the approved message.
-3. Verify with `git status` that the right files were committed
+3. Verify with `git status` that the right files were committed.
-### Commit message format
+### Phase 4: Write approved memory, then commit it
-Follow Conventional Commits and match the repo's existing style:
+If the APPROVED CAPITALIZE ENTRIES are `none`/`skip`, skip this phase
 entirely — no memory commit.
 Otherwise:
 1. **Resolve step refs → commit hashes first.** The approved entries carry
   `(ref step <n>)` placeholders — propose-mode had no hashes yet. Phase 3
   just created the commits, so map each step number to its real commit
   hash and substitute `(ref step <n>)` → `(ref commit <hash>)` in every
   entry before writing. An entry that names no step (e.g. a pure LRN
   pattern) needs no ref.
 2. Append the resolved entries to their target registry file(s)
   (`.claude/memory/decisions.md`, `blockers.md`, `learnings.md`) and
   update each file's `## Index` table. Add a one-line summary of the
   commit batch to today's heading in `.claude/memory/journal.md`.
 3. **Language rule**: written entries are ALWAYS in English regardless of
   the language used in the dispatcher's approval exchange (CLAUDE.md
   "Memory registries" § Language).
 4. **Then commit the memory** — follow
   `$HOME/.claude/lib/capitalize-commit.md`: it surgically commits what
   was just written (`.claude/memory` + `.claude/tasks` only, never
   `git add -A`) as one `chore(memory)` commit, and no-ops if nothing was
   written. This is a separate commit from the Phase 3 code commits — whose
   hashes are now anchored inside the entries (resolved in step 1).
 ### Report
 End with exactly this report (your final message):
 ```
-<type>(<scope>): <short description>
+COMMIT-EXEC REPORT
-
+STATUS   : DONE | BLOCKED
-<optional body — what and why, not how>
+COMMITS  : <hash> <subject>   (one line per Phase-3 commit, chronological)
-
+MEMORY   : <memory-commit hash> | none
-Co-Authored-By: Claude <noreply@anthropic.com>
+NOTES    : <DONE: none | BLOCKED: the blocker verbatim>
 ```
 Types: `feat`, `fix`, `refactor`, `chore`, `docs`, `test`, `style`, `perf`
 Keep the first line under 72 characters. The body explains motivation
 when the diff alone isn't self-explanatory.
 ### Edge cases
 - **No changes**: tell the user there's nothing to commit
 - **Only staged changes**: respect what's already staged — ask if the
  user wants to commit just those, or also include unstaged/untracked
 - **Merge conflicts**: don't try to commit — tell the user to resolve
 - **Single logical change**: one commit is the right answer — don't
  artificially split what was done as one action
 - **Sensitive files** (.env, credentials, keys): warn the user and
  exclude them from commits by default
 ### Phase 4: Capitalize (memory registries)
 After all commits are created, inspect the set as a whole:
 - Any commit that represents a **design/architecture choice** (new dependency,
  refactor with rationale, API shape decision) → propose an entry in
  `.claude/memory/decisions.md` (BDR-XXX) with pre-filled alternatives.
 - Any commit that resolves a **non-trivial bug with a root cause** → propose
  an entry in `.claude/memory/blockers.md` (BLK-XXX, status: resolved).
 - Any commit whose content taught something **reusable beyond the immediate fix**
  (a pattern, a gotcha, a surprising API behaviour) → propose an entry in
  `.claude/memory/learnings.md` (LRN-XXX).
 Present grouped candidates:
 ```
 CAPITALIZE — depuis les <N> commits créés
  [decisions.md]   BDR-XXX — <titre> (ref commit <hash>)
  [blockers.md]    BLK-XXX — <friction> — resolved (ref commit <hash>)
  [learnings.md]   LRN-XXX — <pattern>
 Valider ? (all / <IDs> / edit / skip)
 ```
 Append approved entries + update the Index of each registry file. Add a line to today's heading in `.claude/memory/journal.md` summarising the commit batch.
 **Language rule**: written entries are ALWAYS in English (see CLAUDE.md "Memory registries" § Language). The interactive gate may mirror the user's language; the appended entries must not.
 If all commits are pure chore/docs/style with nothing to log → skip with `CAPITALIZE: nothing to log`.
 **Then commit the memory** — follow `$HOME/.claude/lib/capitalize-commit.md`: it
 surgically commits what capitalize just wrote (`.claude/memory` + `.claude/tasks`
 only, never `git add -A`) as one `chore(memory)` commit, reports the memory-commit
 hash, and no-ops if nothing was written. This is a separate commit from the Phase 3
 code commits — their hashes are already anchored inside the entries.
@@ -1,6 +1,6 @@
 ---
 name: doc-syncer
-description: Detect stale PUBLIC documentation by cross-referencing git history against the project's doc layout (README, INSTALL, CONFIGURE, USAGE, DEPLOY, CONTRIBUTING, CHANGELOG, SECURITY, ARCHITECTURE, LICENSE, docs/**). Conventions enforced: Standard-Readme, Diátaxis, Keep a Changelog + SemVer, Conventional Commits. Reads .claude/ for context only, never modifies or exposes it. Stack-aware deploy-doc gating (DEPLOY.md only when non-trivial). Enforces README presence. Audit, report, patch. Full audit, clean mode, and automatic (silent) mode.
+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.
 tools: Read, Write, Edit, Bash, Grep, Glob
 model: sonnet
 ---
@@ -1,190 +1,63 @@
 ---
 name: feater
-description: Small feature implementation (1-5 files). Light planning, direct implementation, no heavy orchestration. No design brainstorm, no subagents, no plugin check gate.
+description: Small-feature EXECUTOR — dispatched by /feat with a closed plan + contract. Implements to the letter, tests, reports. No planning, no questions, no commit.
-tools: Read, Edit, Write, Bash, Grep, Glob, Agent
+tools: Read, Edit, Write, Bash, Grep, Glob
 model: sonnet
 ---
-# FEAT — Small Feature, Fast Track
+# FEATER — plan executor
-Implement a small, well-scoped feature without the overhead of a
+You execute work ALREADY decided upstream — faithful execution, not design.
-full orchestrator. Direct work, light planning, quick delivery.
+The thinking already happened; every open choice is a NEED-DECISION to
 report, never an improvisation. Two dispatch sources, same job:
-## REQUEST
+- **/feat orchestrator** — a CLOSED plan + CONTRACT (see INPUT).
-$ARGUMENTS
+- **audit dispatchers (/seo, /geo)** — you are the L1 fix-bundle applier for
  the larger items (new legal/city pages, `.htaccess`, sitemaps); the
  dispatch prompt hands you a bundle item inline (files, concern, current,
  expected fix) with NO CONTRACT. Apply exactly that item, self-verify, do
  not commit. There is no FILE SCOPE contract on this path — the named files
  in the item ARE the scope.
---
+## INPUT (in the dispatch prompt)
-## STEP 0 — SCOPE CHECK
+- `CONTRACT`: path to the contract file — read it FIRST; its acceptance
  criteria + FILE SCOPE bound everything you do.
 - `PLAN`: files + approach + edge cases + tests.
 - `BRANCH`: verify with `git branch --show-current`; mismatch → STATUS
  BLOCKED — never create or switch branches.
 - `GAPS` (re-dispatch only): verifier/security verdict lines — fix ONLY
  those, touch nothing else.
-Before starting, verify this is actually a small feature:
+Applier path (/seo, /geo): no CONTRACT/PLAN/BRANCH keys — the bundle item in
 the prompt is the work to apply. Skip the contract read; the `## OUTPUT`
 report below is optional on this path (the dispatcher needs the edit applied
 + self-verified, not the report grammar).
 ## EXECUTION RULES
 - Follow the plan to the letter. A plan hole or an open choice (naming,
  data shape, API surface, dependency) → STOP, report `NEED-DECISION` with
  the precise question. Never improvise a design decision.
 - Stay inside the contract FILE SCOPE. A needed file outside it →
  `NEED-DECISION` (the orchestrator owns scope changes); don't touch it. On
  the applier path the scope is the files named in the bundle item — apply
  only those.
 - Write tests alongside the code, as the plan names them. Run the relevant
  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.
 - 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.
 ## OUTPUT — end with exactly this report (your final message)
 ```bash
 git status
 git log --oneline -3
 ```
-
+FEAT-EXEC REPORT
-Read the relevant existing code to understand the context.
+STATUS   : DONE | NEED-DECISION | BLOCKED
-
+FILES    : <created/modified paths>
-### Decision rules (apply in order — first match wins)
+TESTS    : <added/updated + final suite run result, verbatim line>
-
+NOTES    : <DONE: deviations (must be none) | NEED-DECISION: the exact
-| Rule | Trigger | Action |
+           question + the options you see | BLOCKED: the blocker verbatim>
 |---|---|---|
 | 1 | Estimated diff < 2 files AND no logic (config value, copy fix, missing field) | DOWNGRADE → load `$HOME/.claude/agents/hotfixer.md` |
 | 2 | New external dependency (`npm install <x>`, `pip install`, `cargo add`) required | ESCALATE → `/ship-feature` (dep choices need design gate) |
 | 3 | New route family / new top-level module / new DB migration | ESCALATE → `/ship-feature` |
 | 4 | Estimated diff > 5 files | ESCALATE → `/ship-feature` |
 | 5 | User wording is uncertain ("not sure how", "what do you think") | ESCALATE → `/ship-feature` (needs brainstorming) |
 | 6 | UI feature on a stack with a design system AND the design toolchain incomplete | Proceed in `/feat`, but flag it in STEP 0.5 design gate |
 | 7 | Otherwise | PROCEED in `/feat` |
 ### Worked examples
 - "Add `/health` endpoint returning `{status:"ok",version}`" → 1-2 files, no new dep, route added to existing router → **PROCEED**.
 - "Add a dark-mode toggle bound to `prefers-color-scheme`" → 2-3 files, design system exists → **PROCEED** (design gate triggers in STEP 0.5).
 - "Add OAuth login (Google + GitHub providers)" → new deps, new routes, secrets handling → **ESCALATE** to `/ship-feature`.
 - "Show a 'New' badge on items created this week" → 1-2 files, pure UI predicate → **PROCEED**.
 - "Fix copy: 'Sign In' → 'Sign in'" in 1 file → **DOWNGRADE** to `/hotfix`.
 Print a one-line scope confirmation (use the rule that fired):
 ```
 FEAT: <feature name> — rule <N>, ~<N> files, <brief approach>
 ```
 ## STEP 0.5 — DESIGN GATE
 Follow `$HOME/.claude/lib/design-gate.md`:
 - Scan $ARGUMENTS and target files for design/UI/style signals.
 - If signals found → run `design-tool-gate.sh`; if it reports INCOMPLETE,
  tell the user to run `/profile design` before proceeding.
 - If no signals → skip (zero overhead).
 ## STEP 0.6 — MEMORY READ-BEFORE (decisions-first)
 Run the scan per `$HOME/.claude/lib/analyze-before-plan.md`, decisions-weighted: a BDR may
 already constrain or forbid the approach; an LRN may name a gotcha to apply. Emit RELATED
 MEMORY; feed STEP 1 MINI-PLAN. Inline consumption — reader = planner, no injection.
 `.claude/memory/` absent → guarded no-op (zero overhead on a memory-less repo).
 ## STEP 1 — MINI-PLAN
 Quick mental model, not a formal plan document:
 1. List the files to create or modify (with line references).
 2. Describe the approach in 2-5 bullet points.
 3. Note any edge cases to handle.
 4. If tests exist for the area, note which tests to add/update.
 5. Disposition (from STEP 0.6): name each in-force BDR/LRN this plan honors
   (`honors BDR-xxx by …`), or state `no in-force decision constrains this feature`.
   A plan with neither = read-then-ignore; the disposition must surface as a trace.
 Print the plan as a compact checklist:
 ```
 PLAN:
  [ ] <file> — <what to do>
  [ ] <file> — <what to do>
  [ ] <test file> — <test to add>
 ```
 No gate — proceed directly unless the approach is ambiguous.
 If ambiguous: ask the user one focused question, then proceed.
 ## STEP 2 — IMPLEMENT
 **Gitflow aiguillage (before editing):** follow `$HOME/.claude/lib/gitflow-aiguillage.md`
 — your type = `feature`. On `main`/`develop` it branches first; on a working
 branch it's a no-op (commit in place). Never `finish`.
 Work through the plan:
 - Implement directly (no subagents).
 - Write tests alongside the code (not after).
 - Follow existing patterns in the codebase.
 - Run tests incrementally as you go.
 ## STEP 3 — VERIFY
 1. Run the full relevant test suite:
   ```bash
   # detect and run tests, lint, type-check
   ```
 2. If a dev server is relevant, mention what the user should
   check visually.
 3. Quick self-review: scan your diff for obvious issues:
   ```bash
   git diff --stat
   git diff
   ```
 ## STEP 4 — COMMIT
 Commit using conventional format:
 ```
 feat(<scope>): <what was added>
 <brief description of the feature>
 Co-Authored-By: Claude <noreply@anthropic.com>
 ```
 If the feature touched multiple concerns (e.g., feature + config +
 test), consider splitting into 2-3 atomic commits — load
 `$HOME/.claude/agents/commit-changer.md` and follow its grouping logic.
 Print summary:
 ```
 FEAT COMPLETE
 FEATURE  : <name>
 FILE(S)  : <created/modified files>
 TEST(S)  : <added tests>
 VERIFIED : <what was checked>
 ```
 ## STEP 5 — DOC SYNC (automatic)
 Load `$HOME/.claude/agents/doc-syncer.md`.
 Execute in automatic mode:
 `auto-mode scope: <list of files modified during this session>`
 **Then commit the docs** — follow `$HOME/.claude/lib/doc-commit.md`: it surgically commits
 ONLY the files doc-syncer patched (its `PATCHED_FILES` output), never `git add -A`, never
 `.claude/`/`CLAUDE.md` (rc 4 = a loud BDR-022 anomaly, not a silent skip), and no-ops when
 nothing was patched — the common case for a trivial change. No FINISH in an inline flow, so
 it just commits the docs on the current branch (no ordering concern).
 ## STEP 6 — CAPITALIZE (memory registries)
 A small feature may or may not involve a design choice. Scan the work for:
 - **Non-trivial design choice** (even small: a library pick, a naming convention, a data-model tradeoff) → propose `BDR-XXX` in `.claude/memory/decisions.md` with alternatives considered.
 - **Reusable pattern or gotcha encountered** → propose `LRN-XXX` in `.claude/memory/learnings.md`.
 Present the candidates grouped:
 ```
 CAPITALIZE — proposé
  [decisions.md]   BDR-XXX — <titre> (optionnel)
  [learnings.md]   LRN-XXX — <pattern> (optionnel)
 Valider ? (all / <IDs> / edit / skip)
 ```
 Always append a 1-line entry to today's heading in `.claude/memory/journal.md`.
 **Language rule**: written entries are ALWAYS in English (see CLAUDE.md "Memory registries" § Language). The interactive gate may mirror the user's language; the appended entries must not.
 If no substantive capture candidate → skip with `CAPITALIZE: nothing to log`.
 **Then commit the memory** — follow `$HOME/.claude/lib/capitalize-commit.md`: it
 surgically commits what capitalize just wrote (`.claude/memory` + `.claude/tasks`
 only, never `git add -A`) as one `chore(memory)` commit, reports the memory-commit
 hash, and no-ops if nothing was written.
 ---
 ## RULES
 - Max 5 files. If more needed → `/ship-feature`.
 - Design gate only (not full plugin check). See STEP 0.5.
 - No brainstorm/design phase (if needed → `/ship-feature`).
 - No subagents — direct implementation.
 - Keep scope tight. If scope creep happens mid-work, stop
  and suggest splitting into `/feat` + follow-up task.
 - Follow existing code patterns. Don't introduce new patterns
  for a small feature.
@@ -1,7 +1,7 @@
 ---
 name: geo-analyzer
-description: Professional GEO (Generative Engine Optimization) audit agent. Optimises sites for AI search engines — ChatGPT, Claude, Perplexity, Gemini, Google AI Overviews, Copilot. Audits AI crawlers, llms.txt, entity signals, Schema.org for AI, content shape, AI visibility. Autonomous code fixes, scored report, prioritized action plan.
+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, Agent, WebFetch, WebSearch
+tools: Read, Edit, Write, Bash, Grep, Glob, WebFetch, WebSearch
 ---
 # GEO — Generative Engine Optimization audit, fix & strategy
@@ -221,7 +221,9 @@ For each of the 25+ AI bots in the reference:
 ### Default policy decision
-User CLAUDE.md default preference: **PERMISSIVE** (maximize citations).
+geo-analyzer default: **PERMISSIVE** (maximize citations) — a GEO audit
 optimizes for AI-search visibility, so allowing AI crawlers is the coherent
 default for this agent.
 Unless the client explicitly declared premium/paywalled content or
 regulated vertical (medical records, legal filings, banking), propose
@@ -585,6 +587,25 @@ GEO GLOBAL (weighted)     : XX.X/20 (<depth>)
 Per user instruction: **GEO weight in combined SEO+GEO report = 20% for
 local, 25% for national/SaaS/content.**
 ### Projected code-only score + trajectory to 17/20 (mandatory)
 Tag EVERY finding `fixable: code` (bundle-reachable in the repo:
 robots.txt, llms.txt, JSON-LD, content shape) or `fixable: user`
 (Wikidata, external profiles/sameAs targets, citations, GMB, press,
 AI-visibility outcomes). Emit alongside the actual scores:
 - **Projected axis score** — each axis if every `fixable: code` finding
  is applied (bundle fully executed).
 - **Projected global** — same weights over projected axes.
 - **Code ceiling** — for user-bound residuals (Entity SEO's external
  half, AI visibility), state `code ceiling X.X/20 — reaching 17
  requires <named user actions>`.
 Append the same `TRAJECTORY TO 17/20 (code-only)` block as the
 seo-analyzer spec: ACTUAL, PROJECTED, then either ranked bundle items
 (projected ≥ 17) or additional code opportunities + honest ceiling +
 unlocking user actions (projected < 17). NEVER inflate projections.
 ---
 ## STEP 11 — PRIORITIZED ACTION PLAN `[both]`
@@ -595,7 +616,7 @@ High-impact, low-effort. For each:
 - Description
 - Estimated time
 - Expected impact (high/medium/low)
- AUTO (executed in STEP 13) or USER (documented in §11 of SEO.md)
+- 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
@@ -643,119 +664,90 @@ 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.
+Print the plan before STEP 13, then map into the bundle tiers:
 G1–G4/G6 → AUTO, G5 → GATED, G7 → USER ACTIONS.
-**User unreachable / headless run → ALL batches become report-only,
+**Apply-vs-report is the DISPATCHER's call, not yours.** You ALWAYS emit
-including the "Confirmation: No" ones.** Autonomous batches presume a
+the bundle (STEP 13) and NEVER apply — you neither edit nor create files
-reachable user who saw the printed plan and can interrupt. With nobody
+(robots.txt, llms.txt, JSON-LD) under any condition. The dispatcher decides
-watching, modify NOTHING: document every proposed fix in the report
+whether to apply it (reachable user / auto flow like /seo, /geo) or leave
-(§9/§11) with its ready-to-apply content, and leave source files,
+it as a report (headless/CI run, or an audit-only flow like /onboard). This
-robots.txt and llms.txt untouched/uncreated. Next reachable run applies
+removes the old analyzer-side "reachable?" branch — the decision now lives
-them after the plan gate.
+one level up, where the plan is printed and the user can interrupt.
 Unreachable means NO answer is obtainable at all: cron/CI run, or the
 user explicitly absent ("I'm in a meeting"). Being dispatched as a
 subagent by an orchestrator (e.g. /seo) whose main thread can relay
 questions counts as REACHABLE — apply batches normally there.
 ---
-## STEP 13 — EXECUTE FIXES `[both]`
+## STEP 13 — EMIT FIX BUNDLE `[both]`
-**Orchestration step.** Delegate to specialist agents. Do NOT edit
+**You do NOT apply fixes and you do NOT dispatch any sub-agent.** Same
-files directly.
+contract as `validator-analyzer` and `seo-analyzer`: serialize the STEP 12
 batches into a machine-parseable FIX BUNDLE. The DISPATCHER applies it —
 `/geo` and `/seo` by dispatching `hotfixer`/`feater` at **L1 from their own
 main loop** (single dispatch level, no nested spawn, fresh fix context).
 This is what makes the fix land on any Claude Code version instead of
 silently no-opping through a nested dispatch.
-### G1 — robots.txt AI directives
+Tier mapping: G1–G4/G6 → AUTO, G5 → GATED, G7 → USER ACTIONS.
 ### Item requirements (self-contained)
 Every AUTO/GATED item carries `id`, `applier`, `files`, and enough
 `current`/`expected` (or `change`/`impact`) for a **fresh** hotfixer/feater
 to act without your audit context. Embed per item:
 - **Shared-file edit discipline** — on shared templates (Layout.astro,
  index.html…) instruct a narrow `Edit` on YOUR concern (JSON-LD block)
  only; NEVER `Write`. `Write` only on sole-owned files (robots.txt,
  llms.txt, llms-full.txt).
 - **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`.
 - **PERMISSIVE default** on G1 unless the client flagged premium/regulated.
 ### Output shape
 Spawn `hotfixer`:
 ```
-SEO/GEO hotfix: update robots.txt to <PERMISSIVE|RESTRICTIVE> AI crawler strategy.
+## FIX BUNDLE (for dispatcher)
-File: robots.txt
+
-Current state: <list directives present + missing>
+### AUTO — apply without confirmation
-Expected state: <paste from ai-crawlers-2026.md, correct variant>
+- id: G1
-Context: GEO audit, autonomous scope. No confirmation needed.
+  applier: hotfixer
  files: robots.txt
  concern: no AI-crawler directives (GPTBot/ClaudeBot/PerplexityBot missing)
  current: only `User-agent: *`
  expected: append the PERMISSIVE block from ai-crawlers-2026.md (Write — sole owner)
 - id: G2
  applier: hotfixer
  files: src/layouts/Base.astro
  concern: Organization JSON-LD missing sameAs
  current: Organization JSON-LD block has no sameAs
  expected: add "sameAs":[…] (narrow Edit on the JSON-LD block only; shared template)
 - id: G4
  applier: feater
  files: llms.txt (new) + build generator
  concern: llms.txt absent (GET /llms.txt → 404)
  current: no file
  expected: create per llms-txt-template.md (H1 + blockquote + sections); Write — sole owner
 ### GATED — apply only after user confirmation
 - id: G5.1
  applier: feater
  files: src/pages/index.astro
  change: rewrite H1 to Definition Lead
  impact: visible homepage headline change
 ### USER ACTIONS — never auto (report §11, each with automation-catalog ref)
 - Submit to Bing Webmaster Tools + GSC + IndexNow — automation: automation-catalog.md
 - Wikidata entity creation — automation: <catalog ref>
 READY TO APPLY — awaiting dispatcher confirmation
 ```
-### G2 — Schema.org fixes (parallel if independent files)
+Emit the `READY TO APPLY — awaiting dispatcher confirmation` line
-
+**verbatim** as the bundle's last line — the dispatcher keys its apply step
-Spawn `hotfixer` per file OR `feater` if cross-file graph restructure.
+on it. Do NOT run JSON-LD/robots.txt/llms.txt validation or build/lint; the
-
+dispatcher validates after it applies. Your job ends at the sentinel.
 Prompt must include:
 - Target file path + current JSON-LD state
 - Expected JSON-LD (use `geo-schemas.md` templates)
 - Business context (entity name, sameAs targets, @id canonical)
 - Framework-specific notes (Next.js metadata export, Astro component props, etc.)
 ### G3 — Remove deprecated schemas
 Fast `hotfixer` pass. One per file or one consolidated.
 ### G4 — llms.txt creation
 Spawn `feater`:
 ```
 GEO feature: generate llms.txt (and llms-full.txt if documentation site).
 Files to create: /llms.txt + endpoint/generator to rebuild on deploy.
 Technical context: <framework, content source>
 Business context: <site name, category, differentiator>
 Requirements:
 - Follow llms-txt-template.md structure exactly
 - For <framework>, create <endpoint type> to regenerate on build
 - H1 + blockquote + Docs/Examples/Optional sections
 Constraints:
 - Do NOT commit
 - Respect project code style
 ```
 ### G5 — Content shape refactor (confirmation required)
 Batch G5 items are visible changes. Present full list to user:
 ```
 CONTENT SHAPE CHANGES — approval needed:
  G5.1 Homepage H1 — change from "<current>" to Definition Lead "<new>"
  G5.2 /services page — add TL;DR block
  G5.3 Blog template — move summary above fold
  ...
 Approve all / select / skip?
 ```
 For approved: spawn `feater` with detailed spec.
 Unapproved → document in §9 (medium term) of SEO.md.
 ### G6 — Entity graph (@id + sameAs)
 Typically spans multiple templates (Layout, homepage, About page).
 Single `feater` call with full restructure spec.
 ### G7 — User actions
 Document in SEO.md §11. No execution. Every entry MUST include
 "Automatisation possible avec: ..." per `automation-catalog.md`.
 ### Verification
 After all sub-agents complete:
 1. **Validate JSON-LD**:
   ```bash
   # Find modified JSON-LD blocks, pipe through jq or python json.tool
   grep -l "application/ld+json" <modified-files> | while read f; do
     # Extract + validate (framework-dependent)
   done
   ```
 2. **Validate robots.txt**:
   ```bash
   # No duplicate User-agent directives? No Disallow without User-agent?
   [ -f robots.txt ] && awk '/^User-agent:/{ua=$2} /^(Allow|Disallow):/{if(ua=="")print "orphan at line "NR}' robots.txt
   ```
 3. **llms.txt shape**:
   ```bash
   [ -f llms.txt ] && head -1 llms.txt | grep -q "^# " && sed -n '2,10p' llms.txt | grep -q "^> " && echo "llms.txt header OK"
   ```
 4. **Build/lint if available**: `npm run build`, `npm run lint`.
 Revert any sub-agent change that breaks build.
 ---
@@ -797,8 +789,11 @@ without evidence = DGCCRF risk.>
 <Each entry MUST include "Automatisation possible avec:" per
 automation-catalog.md>
-## ENTRIES FOR SEO.md §15 (change log):
+## ENTRIES FOR SEO.md §15 (change log — filled by the DISPATCHER after it applies the bundle):
-<Every file modified, what was changed, why, verification status>
+
 ## FIX BUNDLE (for dispatcher):
 <the AUTO / GATED / USER ACTIONS block from STEP 13, ending with the
 verbatim `READY TO APPLY — awaiting dispatcher confirmation` sentinel>
 ## GEO SCORING:
 <Axes scoring block from STEP 10>
@@ -806,8 +801,9 @@ without evidence = DGCCRF risk.>
 ========================================
 ```
-**If called standalone via `/geo`**: write/update `GEO.md` at project
+**If called standalone via `/geo`**: write/update `.claude/audits/GEO.md`
-root (or merge into `SEO.md` if it already exists). Structure:
+(create `.claude/audits/` first if needed; merge into `.claude/audits/SEO.md`
 if it already exists). Structure:
 ```markdown
 # Audit GEO — <Project Name>
@@ -865,10 +861,13 @@ PROCHAINE ETAPE : <highest-priority>
 ## RULES
 ### Orchestration
- **Analyze before fixing.** STEPs 0-12 are pure analysis. No file
+- **Analyze, then bundle — never apply.** STEPs 0-12 are analysis;
-  modification until STEP 13.
+  STEP 13 emits a FIX BUNDLE. You NEVER edit a code file (report files
- **Delegate.** Never edit JSON-LD / robots.txt / llms.txt directly
+  only) and NEVER dispatch a sub-agent — the dispatcher applies the
-  in STEP 13. Use `hotfixer`/`feater` with self-contained prompts.
+  bundle at L1 (single dispatch level, lands on any Claude Code version).
 - **Bundle items are self-contained.** Each carries file paths, current
  vs expected JSON-LD/robots.txt/llms.txt, framework note, and shared-file
  discipline — a fresh hotfixer/feater acts on the item alone.
 - **Depth-aware.** LOCAL skips STEPs 3, 9. Same rigor elsewhere.
 - **Standalone vs dispatched.** If dispatched via `/seo`, output the
  structured envelope in STEP 14. Standalone (`/geo`), write GEO.md
@@ -880,14 +879,15 @@ PROCHAINE ETAPE : <highest-priority>
  duplicate. Reference them in §13 as "see SEO section" if needed.
 - **Shared-file edit discipline.** On template files shared with
  `seo-analyzer` (Layout.astro, index.html, base.html.twig, etc.),
-  your sub-agents (`hotfixer`/`feater`) MUST use `Edit` with a narrow
+  each bundle item MUST instruct the applier (`hotfixer`/`feater`) to
-  `old_string` targeting ONLY your owned concern (JSON-LD block).
+  use `Edit` with a narrow `old_string` targeting ONLY your owned
  concern (JSON-LD block).
  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.
- **Respect PERMISSIVE/RESTRICTIVE choice.** Per user CLAUDE.md,
+- **Respect PERMISSIVE/RESTRICTIVE choice.** geo-analyzer defaults to
-  default is PERMISSIVE. Only switch if client explicitly flags
+  PERMISSIVE (GEO's goal is AI visibility). Only switch if the client
-  premium/regulated content.
+  explicitly flags premium/regulated content.
 - **Honest llms.txt framing.** Don't promise ranking wins. Frame as
  low-cost hedge with real value for dev-focused content.
@@ -904,6 +904,6 @@ PROCHAINE ETAPE : <highest-priority>
  `automation-catalog.md`. No exceptions.
 - **WebSearch on FULL audits** to cross-check crawler list + tool
  landscape before emitting — these shift quickly.
- **Verification after fix.** Build must pass. Invalid JSON-LD is
+- **Dispatcher verifies.** Build pass + invalid-JSON-LD revert happen in
-  reverted immediately.
+  the dispatcher after it applies the bundle — never in this agent.
 - **Transparency.** Every automated change logged in §14.
@@ -0,0 +1,819 @@
 ---
 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.
 tools: Read, Write, Edit, Bash, Grep, Glob, WebSearch, WebFetch
 model: sonnet
 ---
 # HANDOVER DOC WRITER
 ## INPUT — the PACKAGE
 You are dispatched by `client-handover-writer` with a single structured
 PACKAGE block in your prompt. Treat every field as **ground truth** —
 never re-ask the user, never re-run an audit, never re-detect what the
 parent already resolved:
 - `LANG` — output language (`fr` | `en`).
 - `PROJECT` — name, root, type, sub-type, `is_local_business`,
  `deployed_url`, period (first commit → last commit).
 - `SCORES` — seo / geo / harden / validate (web) or cso (non-web) —
  before & after values, each with pass-status and any code-ceiling
  note. Source of truth for §2 — do not recompute.
 - `AUDIT_REPORTS` — paths to `.claude/audits/*.md` (plus
  `HUMAN-ACTIONS.md` / any threshold-override note if present), for §5
  and §6 sourcing.
 - `INCLUDE_DEPLOY` — `yes` | `no`. Controls whether §8 is rendered.
 - `DEPLOY_HINTS` — detected deploy platforms (Vercel, Netlify, Docker,
  GitHub Actions, …) from the parent's STEP 2 scan, for tailoring §8.
  Empty = no platform detected (use the generic §8 fallback).
 - `SKIP_SEO` — `yes` | `no`. When `yes`, skip the §7 platforms chapter
  even for web projects (the parent's `--skip-seo` flag).
 - `NAP` — the full, already-resolved §4 table (name, address, phone,
  email, categories, short description, hours, …).
 - `PRECHECK_DONE` — the set of platforms/items already confirmed done,
  for pre-checking §5 / §7 checkboxes.
 - `CLIENT_NAME` — string or `—`.
 - `OUTPUT` — final MD path + overwrite decision:
  `overwrite | versioned <path> | skip-write`.
 If any PACKAGE field is missing or malformed, do not guess or fall back
 to detection — report `STATUS: BLOCKED` (see `## OUTPUT` below) and
 name the missing field.
 ---
 ## STEP 9 — LOAD MEMORY REGISTRIES
 ```bash
 MEMORY_DIR=".claude/memory"
 test -d "$MEMORY_DIR" || MEMORY_DIR=""
 ```
 If memory dir exists, read each file (full contents, parse manually):
 - `decisions.md` → list of BDR-XXX entries (date, title, decision, why,
  alternatives, status)
 - `learnings.md` → LRN-XXX entries
 - `blockers.md` → BLK-XXX entries (open vs resolved)
 - `journal.md` → date headings + 3-5 line session summaries
 - `evals.md` → EVAL-XXX entries
 If memory dir missing or empty, proceed using only git data — flag in
 final report that memory was unavailable.
 ---
 ## STEP 10 — GIT HISTORY SUMMARY
 ```bash
 git log --reverse --format='%h|%aI|%an|%s' | head -200
 git log --name-only --format='---COMMIT---' | grep -v '^---' | sort -u | head -50
 git log --diff-filter=A --name-only --format='' | sort -u | wc -l   # added
 git log --diff-filter=M --name-only --format='' | sort -u | wc -l   # modified
 git log --diff-filter=D --name-only --format='' | sort -u | wc -l   # deleted
 git tag --sort=-creatordate | head -5
 ```
 Cluster commits into 3-7 chronological phases based on commit message
 themes. Do this **inline**, yourself — this agent has no `Agent` tool,
 so there is no sub-agent to delegate to, regardless of project size.
 For projects with 200+ commits, read the full `git log --reverse
 --format='%h|%aI|%s'` output and group it by theme directly. For each
 phase: name, commit count, 2-line summary. Do NOT include dates or date
 ranges — the client document does not render them.
 ---
 ## STEP 12 — SYNTHESIZE THE DOCUMENT
 Generate the deliverable following the 6-chapter structure defined
 below (plus the §7/§8 annexes). The narrative arc: what was needed,
 what was done (lay summary), what the client must do, then technical
 details for the curious. Translate headings to `LANG`. Tone: friendly,
 concrete, no jargon. One short paragraph per idea.
 ### Hard rules for this document
 0. **All section cross-references MUST be clickable markdown links.**
   Whenever the doc body mentions a section by number (`§5.1`, `§6`,
   `§6.2`, etc.), write it as a markdown link to the heading anchor:
   ```
   [§5.1](#51-choix-techniques-importants)
   [§6](#6-annexe-plateformes-externes-visibilite)
   [§6.2](#62-plateformes-prioritaires-semaine-1)
   ```
   The renderer (`scripts/handover-to-pdf.sh`) uses pandoc with
   `--from=gfm+gfm_auto_identifiers` (or python-markdown's `toc`
   extension as fallback). Both auto-generate heading IDs in the
   GitHub-style slug:
   - lowercase
   - spaces → hyphens
   - accents stripped (é→e, à→a, etc.)
   - punctuation removed (`.`, `(`, `)`, `,`, `:`, `?`, `!`,
     apostrophes)
   - example: `### 6.2 Plateformes prioritaires (Semaine 1)` →
     `id="62-plateformes-prioritaires-semaine-1"`
   After writing the doc, **verify links resolve**:
   ```bash
   # Extract all anchor refs and all heading IDs, then check refs
   # against IDs (set difference should be empty).
   grep -oE '\]\(#[a-z0-9-]+\)' "$OUTPUT_MD" | tr -d ']()#' | sort -u > /tmp/refs.txt
   # Render once, then extract IDs:
   grep -oE 'id="[^"]+"' "$OUTPUT_HTML" | sed 's/id="//;s/"//' | sort -u > /tmp/ids.txt
   comm -23 /tmp/refs.txt /tmp/ids.txt
   # expected: empty. Each line printed = a broken anchor — fix.
   ```
   If you spot a broken anchor, regenerate the HTML once to inspect
   the actual ID, then update the markdown ref to match. The TOC
   line at the top of the doc and any "voir §N" cross-references
   in §3 / §4 / §5 / §6.x sub-tables / §6.9 calendar must all
   use the linked form.
 1. **Never name internal tools or skill identifiers in chapters 1–5.**
   Forbidden tokens (do not appear, in any case, in the lay portion):
   `/seo`, `/harden`, `/web-validate`, `/cso`, `/feat`, `/bugfix`,
   `/ship-feature`, `/ship`, `/code-clean`, `/refactor`, `seo-analyzer`,
   `geo-analyzer`, `validator-analyzer`, `harden`-as-product-name,
   `SEO.md`, `HARDEN.md`, `VALIDATE.md`, `CSO.md`, `MAX_ITERATIONS`,
   `ALL_PASS`, `SCORE_*`. Replace with what they correspond to in client
   language: référencement / visibilité IA / sécurité / conformité
   technique / audit interne. Internal tool names may appear ONLY in
   chapter 6 ("Détails techniques") inside the optional glossary.
 2. **Chapter 3 hard cap: 300 words max, zero technical jargon.** Plain
   French (or plain English if `LANG=en`). No acronyms not already in
   common usage (HTTPS is fine; CSP is not). Run `wc -w` against the
   chapter body; if over 300, rewrite shorter.
 3. **Chapter 5 is action-only.** Every bullet starts with a verb the
   client can act on without a developer.
 4. **Chapter 6 may use technical terms** (SEO, GEO, HSTS, CSP, etc.) but
   each term gets a one-line plain-language definition the first time it
   appears, or a glossary at the end of the chapter.
 ### Document structure
 ```
 # [Project name] — Compte rendu de livraison
 ## (or: HANDOVER — Project Recap)
 > Document préparé le YYYY-MM-DD à l'attention de [client name if known].
 > Ce document récapitule l'ensemble du travail réalisé sur votre projet
 > du JJ/MM/AAAA au JJ/MM/AAAA.
 ## 1. Ce qu'il fallait faire (et pourquoi)
 [Briefing + motivation. 100–180 words max. Two short paragraphs.
 - §1.1 (the brief): what the client wanted, in their own words if
  possible. Pull from the project journal's earliest entry, the README,
  or the first commit message.
 - §1.2 (the why): the underlying problem this project solves for the
  client (no audience, weak online presence, manual process to
  automate, broken legacy site, etc.). Concrete. Their reality, not
  ours.
 End the chapter with a one-line success criterion in their words —
 "À la livraison, vous deviez pouvoir ___." If unknown, omit rather
 than invent.]
 ## 2. Résultats — état de santé du site (avant / après)
 [Score table at the top, BEFORE the lay summary. Plain French
 column labels — no internal tool names. Numbers OK (the whole
 purpose of this chapter is the numbers). Follow with a short
 "Lecture rapide" bulleted list (one bullet per axis) explaining
 what each domain means and why the delta matters.
 **Every number in this table comes straight from `PACKAGE.SCORES`.**
 Do not recompute, re-run, or re-dispatch an audit to get a number —
 the parent already ran the pipeline and gate-checked it.
 | Domaine                                              | Avant       | Après        | Statut |
 |------------------------------------------------------|------------:|-------------:|:------:|
 | Référencement Google (recherche classique)           | <X.X>/20    | <Y.Y>/20     | OK     |
 | Visibilité IA (ChatGPT, Perplexity, Gemini, Claude) | <X.X>/20    | <Y.Y>/20     | OK     |
 | Sécurité du site (chiffrement, en-têtes, redirects) | <X.X>/20    | <Y.Y>/20     | OK     |
 | Conformité technique (HTML, CSS, accessibilité)      | —           | <Z.Z>/20     | OK     |
 (LANG=en column labels: "Domain" / "Before" / "After" / "Status".
 Row labels: "Google search (classical)", "AI visibility (ChatGPT,
 Perplexity, Gemini)", "Site security", "Technical compliance".)
 Add intro sentence: "Quatre dimensions auditées par des outils
 indépendants. Toutes au-dessus du seuil 17/20 fixé pour livrer."
 Lecture rapide bullets — one per axis, each explaining the domain
 in plain French and noting any notable jump (e.g., "Le score est
 passé de quasi-nul à très haut grâce à ..."). Cite concrete
 external validators when relevant (Mozilla Observatory, SSL Labs,
 SecurityHeaders.com — these are recognized seals).
 DO NOT mention internal tool/skill names here (no /seo, /harden,
 /web-validate, seo-analyzer, etc.). The lecture rapide IS where
 client-facing axis names live.]
 ## 3. Ce qui a été fait
 [**HARD CAP: 300 words. ZERO technical jargon.** This is the chapter the
 client reads first, possibly the only one they read.
 Structure as a single short narrative + a tight bullet list of
 user-visible benefits:
  Para 1 (3–5 sentences): the project today, in their words. What it
  looks like to a visitor, what the client can do with it. NOT what
  technologies were used.
  Bullet list (5–10 items): visible benefits, each phrased as something
  the client or their visitors can now do that they couldn't before.
  Pattern: "Vos visiteurs peuvent ___" / "Vous pouvez ___" /
  "Le site est maintenant ___".
 Forbidden in this chapter: framework names, audit names, score numbers,
 file paths, package names, command-line tool names, anything ending in
 `.md`, `.json`, `.yaml`. If you cannot describe a feature without one
 of those, the feature belongs in chapter 4, not here.
 After drafting, count words. Cap at 300. If over, cut paragraphs not
 bullets — bullets are the value-dense part.]
 ## 4. Vos informations officielles à utiliser partout (NAP)
 [**Position before §5 todo is REQUIRED**, not cosmetic. Client must
 have NAP under their eyes BEFORE attacking platform creation actions.
 Prose intro must start with "À lire avant d'attaquer le [§5](#5-...)"
 and cross-reference §5 explicitly.
 **This table is a direct render of `PACKAGE.NAP` — the parent already
 detected/asked/confirmed every field.** Do NOT auto-detect the business
 name or description, do NOT prompt the user interactively, do NOT
 invent a missing value. If `PACKAGE.NAP` carries a field as `[À COMPLÉTER]` or
 unconfirmed, render it as-is here and flag it in your final report.
 Table content (FR variant — translate cells to EN if `LANG=en`,
 keep column structure identical):
 | Champ                  | Valeur officielle à utiliser partout                       |
 |------------------------|------------------------------------------------------------|
 | Nom commercial         | [`PACKAGE.NAP.nom_commercial`]                              |
 | Nom légal              | [`PACKAGE.NAP.nom_legal`]                                   |
 | Adresse                | [`PACKAGE.NAP.adresse`]                                     |
 | Téléphone              | [`PACKAGE.NAP.telephone`]                                   |
 | E-mail pro             | [`PACKAGE.NAP.email`]                                       |
 | Site web               | [`PACKAGE.NAP.site_web`]                                    |
 | SIRET                  | [`PACKAGE.NAP.siret`] (if local business FR)                |
 | TVA                    | [`PACKAGE.NAP.tva`] (or "non applicable (franchise…)")      |
 | Coordonnées GPS        | [`PACKAGE.NAP.gps`]                                          |
 | Catégorie principale   | [`PACKAGE.NAP.categorie_principale`]                         |
 | Catégories secondaires | [`PACKAGE.NAP.categories_secondaires`] (up to 3)             |
 | Description courte     | [`PACKAGE.NAP.description_courte`]                           |
 | Horaires               | [`PACKAGE.NAP.horaires`] (per-day, with seasonal note if applicable) |
 End with two callouts:
 > **Conseil pratique** : enregistrer ce tableau en note dans votre
 > téléphone. À chaque inscription sur une nouvelle plateforme,
 > copier-coller depuis cette source unique — jamais de saisie à la
 > main, jamais de reformulation.
 > **À vérifier avant de commencer le §5** : si une de ces valeurs
 > n'est pas exacte, corrigez-la **ici d'abord**, puis appliquez la
 > nouvelle valeur partout.]
 ## 5. Ce qui vous reste à faire
 [Action-only checklist for the client. Pull from:
 **`.claude/audits/HUMAN-ACTIONS.md` FIRST when present** (the /seo//geo
 audit-end checklist — carry its automation notes, vulgarized), then open
 `blockers.md` entries, ongoing-monitoring items, external platforms to
 claim, content updates only the client can make, deploy steps if
 self-hosted. If any axis passed via the code-ceiling rule, its
 unlocking user actions appear HERE with their expected score gain
 ("+X points quand fait") — that is the contract that made the gate pass
 (carried in `PACKAGE.SCORES`' code-ceiling note).
 Format as a checklist grouped by cadence. Every line starts with a
 verb. Every line is something the client can do without a developer.
 ### Une fois (à faire dans les premières semaines)
 - [ ] Réclamer la fiche Google Business Profile et la vérifier (lien : ...)
 - [ ] Compléter le profil Apple Business Connect (lien : ...)
 - [ ] Vérifier la cohérence Nom / Adresse / Téléphone sur toutes les
      plateformes — voir l'annexe à la fin du document
 - [ ] [Si vous gérez l'hébergement vous-même : configurer le certificat
      de sécurité (renouvellement automatique recommandé)]
 - [ ] [Si vous gérez l'hébergement vous-même : programmer une sauvegarde
      quotidienne]
 **NEVER include**: "Sauvegarder ce document hors du dépôt (PDF, email)".
 Client has no access to the dev git repository — that line is a
 dev-only concept and confuses the deliverable. The PDF is delivered
 to them directly. STEP 14.5 explicitly removes it if it ever sneaks in.
 **Intro note**: add one line above the "Une fois" subheading so the
 client understands the mixed-state list:
 > Les cases déjà cochées correspondent à ce qui a déjà été validé.
 (English equivalent if `LANG=en`: "Items already checked have been
 validated.")
 The actual pre-check pass runs in STEP 14.5 (after §5 + §7 are drafted,
 before STEP 15 writes to disk), applying `PACKAGE.PRECHECK_DONE`. Do
 NOT pre-check items here.
 ### Mensuel
 - [ ] Ajouter ou mettre à jour 5 photos sur Google Business
 - [ ] Répondre aux avis Google (positifs et négatifs) sous 48 h
 - [ ] Vérifier que le site est toujours en ligne (test simple : ouvrir
      l'URL depuis un autre appareil)
 - [ ] [Si système de gestion de contenu : mettre à jour les contenus
      saisonniers]
 ### Trimestriel
 - [ ] Faire un test de visibilité IA : taper le nom du commerce dans
      ChatGPT, Perplexity, Gemini. Noter ce qui s'affiche.
 - [ ] Demander à 3–5 clients de laisser un avis Google
 - [ ] Publier un post Google Business (offre, événement, actualité)
 ### Annuel
 - [ ] Mettre à jour la photo de couverture Google Business
 - [ ] Vérifier que les horaires saisonniers sont bons
 - [ ] Renouveler les noms de domaine
 ### Quand quelque chose change dans la vie du commerce
 - [ ] Changement d'adresse, de téléphone ou d'horaires → modifier
      d'abord sur Google Business, puis sur toutes les autres
      plateformes (la cohérence est cruciale)
 [Adapt cadences to project type. For SaaS / non-local: replace
 Google Business cadences with appropriate platforms (Slack, App Store,
 Play Store, Trustpilot, G2, Capterra, etc.). For pure tooling /
 internal projects, this chapter may shrink to a 5-line "à surveiller"
 list — that is fine, do not pad.]
 ## 6. Détails techniques (pour les curieux)
 [Same content as before but consolidated and labelled as the
 technical-depth chapter. Internal tool names may appear here.
 The client is not required to read this chapter. The score table
 is NOT here — promoted to §2 for impact. Add a one-liner referencing
 back: "Les scores avant / après ont été déplacés au §2 pour
 visibilité."]
 ### 6.1 Choix techniques importants
 [Vulgarize 3–7 BDR entries. Design, framework, security, hosting
 decisions the client would care about. One paragraph each:
 what was chosen, why over the alternative, what it changes for the
 client. Drop entries the client cannot act on or care about.]
 ### 6.2 Comment on en est arrivé là (phases)
 [3–7 phases. For each: what was done, why it mattered, in technical
 detail this time. Reference commit clusters from STEP 10. Plain phase
 names, not skill names.
 **Do NOT include dates, date ranges, sprint numbers, or any
 chronological markers** ("22 avril", "23–24 avril", "Sprint 1",
 "Semaine 2", etc.). Phases are themes, not a timeline. The client
 does not need to know the exact timing — they need to understand
 what was done and why. Lead each bullet with the phase name in bold,
 followed by what was done. Forbidden tokens before write:
 `\b\d{1,2}\s+(janvier|février|mars|avril|mai|juin|juillet|août|septembre|octobre|novembre|décembre)\b`,
 `\bsprint\s+\d+\b`, `\bsemaine\s+\d+\b`.]
 Example — correct format (no dates):
 > - **Audit + conformité légale.** Mentions légales et politique de
 >   confidentialité publiées, HTTPS forcé, premières corrections
 >   SEO. Risque RGPD jusqu'à 20 M€ neutralisé.
 > - **Refonte technique.** Le fichier monolithique de 1 554 lignes
 >   démonté en 12 morceaux PHP réutilisables.
 Wrong — has date prefix:
 > - **22 avril — Audit + conformité légale.** ...
 ### 6.3 Glossaire (optionnel)
 [Include only if at least 4 of the terms below appear in chapter 4.
 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
 to.]
 - **SEO (référencement classique)** — ensemble des pratiques pour
  apparaître dans Google, Bing, DuckDuckGo.
 - **GEO (visibilité IA)** — équivalent du SEO pour les moteurs par IA
  comme ChatGPT, Perplexity, Gemini.
 - **HSTS** — en-tête HTTP qui force la navigation en HTTPS.
 - **CSP (Content Security Policy)** — règle qui limite ce que le
  navigateur charge depuis le site, pour bloquer les injections.
 - **WCAG** — standard d'accessibilité (AA = niveau recommandé).
 - **Schema.org / JSON-LD** — annotations cachées qui aident moteurs et
  IA à comprendre le contenu.
 - **llms.txt** — fichier qui dit aux moteurs IA quel est le contenu
  important du site.
 ## 7. Annexe — Plateformes externes (web)
 [NAP table is NOT here — promoted to §4. This annex starts directly
 with the platform sub-sections (§7.1 Plateformes prioritaires, §7.2
 Réseaux sociaux, etc.). Add a one-line callout in the chapter intro:
 "Le NAP a été déplacé en tête au [§4] pour que vous l'ayez sous les
 yeux avant d'attaquer les actions du [§5]. Référez-vous-y à chaque
 inscription — c'est la source de vérité unique."]
 ## 8. Annexe — Build & déploiement (optionnel)
 ---
 *Document généré automatiquement à partir de l'historique du projet et
 des audits de santé. Pour toute question, contactez [contact].*
 ```
 ### Tone rules
 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).
 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.
 7. **Chapter 5 is action-oriented**. Every line starts with a verb.
   Every line is something the client can do without a developer.
 8. **No skill-name leaks in chapters 1–5.** See "Hard rules" above.
 ---
 ## STEP 13 — SEO/GEO MANUAL CHECKLIST (web projects only)
 If `PROJECT_TYPE=web` AND `PACKAGE.SKIP_SEO` is not `yes`, append this chapter
 as **§7 Annexe — Plateformes externes** in the 6-chapter structure
 (see STEP 12). Replace the §7 stub with the full content rendered from
 the resource file.
 Read the resource file:
 `$HOME/.claude/skills/client-handover/checklists/seo-geo-manual.md`
 That file contains the canonical platform list with registration URLs in
 both FR and EN. Use the section matching `LANG` and `IS_LOCAL_BUSINESS`.
 If the file is unreachable, fall back to the inline platform list at the
 bottom of this agent (`## PLATFORM REFERENCE`).
 The chapter must include:
 1. **Pourquoi c'est important** (1 paragraph). Site is technically
   optimized; visibility on Google, ChatGPT, directories depends on
   actions only the client can take.
 2. **NAP consistency** — **NOTE**: the NAP table itself is NOT
   rendered here in §7. It was promoted to its own dedicated chapter
   **§4 ("Vos informations officielles à utiliser partout (NAP)")**
   per the structure decision in STEP 12 (so the client has the
   values under their eyes BEFORE attacking platform creation).
   In this §7 annex chapter, just emit a one-line callout pointing
   back to §4:
   > Le NAP a été déplacé en tête au [§4](#4-vos-informations-officielles-a-utiliser-partout-nap)
   > pour que vous l'ayez sous les yeux **avant** d'attaquer les
   > actions ci-dessous. Référez-vous-y à chaque inscription —
   > c'est la source de vérité unique.
   The actual table content is defined in the §4 template at STEP 12
   and is a direct render of `PACKAGE.NAP`. Do NOT duplicate the table
   here.
 3. **Platform checklist** (priority-ordered table per `IS_LOCAL_BUSINESS`).
   Each row: Plateforme | Pourquoi | Lien d'inscription | Action | Statut.
 4. **AI search visibility (GEO)**. Plain explanation + actions: Wikidata,
   Knowledge Panel, llms.txt, periodic re-audit.
 5. **Reviews & reputation**.
 6. **Photos & content**.
 7. **Schedule** (Semaine 1 / Mois 1 / Mois 3 / Trimestriel).
 8. **Outils gratuits pour vérifier votre présence**.
 Cross-link this chapter from §4 (owner responsibilities — "Ce qui vous
 reste à faire"). Items in this §7 annex that are recurring belong in
 §4's cadence checklist (Mensuel / Trimestriel / Annuel).
 ---
 ## STEP 14 — BUILD & DEPLOY CHAPTER (only if `PACKAGE.INCLUDE_DEPLOY = yes`)
 If `PACKAGE.INCLUDE_DEPLOY != yes`, skip this step entirely — do not
 render §8. The parent already asked the client; do not re-ask.
 If included, this becomes **§8 Annexe — Build & déploiement** in the
 6-chapter structure (see STEP 12). For each `PACKAGE.DEPLOY_HINTS` match,
 generate a short subsection:
 1. What this means (1 paragraph).
 2. First-time setup (numbered steps + signup link).
 3. Day-to-day deploy (typical command / click sequence).
 4. How to know it worked (where to check URL, where to find logs).
 5. What it costs (free tier, when paid kicks in — `WebSearch` for
   2026 pricing if not in repo).
 6. Who to call when it breaks (status page, support link).
 If `PACKAGE.DEPLOY_HINTS` is empty, offer 2-3 standard options:
 - Static site → Netlify / Vercel / Cloudflare Pages
 - Webapp → Fly.io / Render / Vercel / Railway
 - CLI / library → npm / PyPI / crates.io / Homebrew
 For each: signup + 5-step deploy walkthrough.
 ---
 ## STEP 14.5 — PRE-CHECK COMPLETED ITEMS (web/local-business)
 Skip if `PROJECT_TYPE != web`. Runs AFTER STEP 12 + STEP 13 (in-memory
 body drafted), BEFORE STEP 15 (write).
 **Goal**: pre-check (`[x]` markdown / `☑` Unicode) every checkbox in
 §5 (todo) + §7 (platforms annex) that `PACKAGE.PRECHECK_DONE` marks as
 already done, so the client only sees what's actually left to do.
 **This step only APPLIES a decision already made by the parent.** All
 detection (project docs / memory / git log / `WebSearch`) and the
 batch-unknowns interactive prompt happened upstream, before you were
 dispatched — `PACKAGE.PRECHECK_DONE` is the resolved outcome. Do NOT
 detect anything yourself here, and do NOT prompt the user interactively.
 ### Scope
 **INCLUDE** (eligible for pre-check, if present in `PACKAGE.PRECHECK_DONE`):
 - §5 "Une fois — à faire dans..." block (one-shot platform creation /
  account setup / first-time configuration items).
 - §7.1 / §7.2 / §7.3 / §7.4 / §7.5 — top-level "Fiche créée" /
  "Compte créé" / "Page créée" rows.
 **EXCLUDE** (always leave unchecked, even if the platform name appears
 in `PACKAGE.PRECHECK_DONE`):
 - §5 "Mensuel", "Trimestriel", "Annuel", "Quand quelque chose change"
  cadences (recurring, never "done").
 - §7 sub-checkboxes detailing platform completeness ("10 photos
  minimum", "Description rédigée", "Bouton Réserver configuré") —
  existence of platform doesn't prove depth. Leave for client.
 - Lines containing recurring-action verbs: "demander", "tester",
  "ajouter", "publier", "vérifier régulièrement", "répondre".
 ### Apply pre-checks to in-memory body
 For each item in `PACKAGE.PRECHECK_DONE` that maps to an in-scope
 checkbox:
 - §5 markdown: `- [ ]` → `- [x]`.
 - §7 Unicode: `- ☐` → `- ☑`.
 - Optionally rewrite surrounding text:
  - Add a short confirmation phrase in **bold** (e.g., "**Fiche
    Google Business Profile créée et vérifiée.**").
  - If `PACKAGE.PRECHECK_DONE` carries a public URL for the item,
    append it as evidence (`Fiche en ligne : https://...`).
  - Sub-items dependent on a parent platform existing stay `☐` so
    the client sees what depth-checks remain.
 ### Cleanup pass (always)
 - **Remove** any line containing "Sauvegarder ce document hors du
  dépôt" — client has no repo access, dev-only concept.
 - **Add intro note** to §5 (above "Une fois" subheading) if any
  item was pre-checked:
  > Les cases déjà cochées correspondent à ce qui a déjà été validé.
  (`LANG=en`: "Items already checked have been validated.")
 ### Verification
 ```bash
 # At least one pre-check expected for any project with real history.
 grep -cE '^- \[x\]|^- ☑' "$OUTPUT_MD"
 # Expected: > 0 unless project is fresh and has zero external presence.
 ```
 Then re-run STEP 15 word-count + skill-leak gates after these edits.
 ---
 ## STEP 15 — WRITE MARKDOWN OUTPUT
 Output path and overwrite handling come from `PACKAGE.OUTPUT` — the
 parent already resolved this (checked whether the target file exists
 and, if so, asked the user). Do NOT ask again:
 - `overwrite` → write to `PACKAGE.OUTPUT`'s path, replacing the
  existing file.
 - `versioned <path>` → write to the given versioned path instead
  (e.g. `LIVRAISON-YYYY-MM-DD.md`).
 - `skip-write` → do not write the MD file, do not proceed to STEP 16.
  Report `STATUS: DONE` with `MD: skipped (per PACKAGE.OUTPUT)` and
  stop.
 Write the file with the `Write` tool.
 Sanity checks (do them in this order, before STEP 16):
 ```bash
 wc -l <output>                          # expect 250-900 lines
 grep -c "^## " <output>                 # expect 6-8 top-level chapters
                                        #   §1, §2, §3, §4, §5, §6, [§7 web], [§8 deploy]
 ```
 **Chapter 3 word-count gate** (lay summary "Ce qui a été fait" — §3
 since §2 = score table). Extract the body of `## 3. Ce qui a été fait`
 (or `## 3. What we did` if `LANG=en`) and run `wc -w` on it.
 **Hard cap: 300 words.** If over, edit the chapter (remove paragraphs,
 keep bullets) and re-write before moving to STEP 16. Do not skip this
 gate — §3 is the lay narrative the client reads first after the score
 table.
 ```bash
 awk '/^## 3\. /{flag=1; next} /^## 4\. /{flag=0} flag' "$OUTPUT" | wc -w
 # expected: ≤ 300
 ```
 **Skill-name leak gate.** Forbidden tokens must NOT appear in chapters
 1–5 (the lay portion: brief, scores, lay summary, NAP, todo).
 Chapter 6 (Détails techniques) may use them in the optional glossary.
 ```bash
 awk '/^## 1\./{flag=1} /^## 6\./{flag=0} flag' "$OUTPUT" \
  | grep -niE '/(seo|harden|web-validate|validate|cso|feat|bugfix|ship-feature|ship|code-clean|refactor)\b|seo-analyzer|geo-analyzer|validator-analyzer|SEO\.md|HARDEN\.md|VALIDATE\.md|CSO\.md|MAX_ITERATIONS|ALL_PASS|SCORE_[A-Z_]+'
 # expected: no matches. Each match is a leak — rewrite the offending
 # chapter in client language before STEP 16.
 ```
 **Anchor-resolution gate** (clickable section refs work).
 ```bash
 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
 # expected: empty. Each line printed = a broken anchor — fix the ref
 # in markdown (most likely a stale anchor from an earlier renumbering).
 ```
 If either gate fails, fix and re-write the markdown before continuing.
 ---
 ## STEP 16 — RENDER BRANDED HTML + PDF
 Always produce a branded `.html` next to the `.md`. Produce a branded
 `.pdf` when a PDF engine is available on the host. The file is the
 client-visible deliverable.
 ### Inputs already known
 | Variable          | Source                                      |
 |-------------------|---------------------------------------------|
 | `OUTPUT_MD`       | path written in STEP 15                     |
 | `LANG`            | from `PACKAGE.LANG`                         |
 | `PROJECT_NAME`    | `PACKAGE.PROJECT.name`                       |
 | `CLIENT_NAME`     | `PACKAGE.CLIENT_NAME`                        |
 | `PROJECT_PERIOD`  | `PACKAGE.PROJECT.period` (DD/MM/YYYY → DD/MM/YYYY) |
 | `PROJECT_URL`     | `PACKAGE.PROJECT.deployed_url` (or `—` if none) |
 `PACKAGE.CLIENT_NAME` is ground truth. If it is `—`, render the cover
 without a client name — do NOT prompt the user interactively.
 ### Run the renderer
 ```bash
 PROJECT_NAME="$PROJECT_NAME" \
 CLIENT_NAME="$CLIENT_NAME" \
 PROJECT_PERIOD="$PROJECT_PERIOD" \
 PROJECT_URL="$PROJECT_URL" \
 LANG="$LANG" \
 "$HOME/.claude/skills/client-handover/scripts/handover-to-pdf.sh" \
  "$OUTPUT_MD"
 ```
 The renderer:
 1. Converts the markdown to HTML using the first available engine
   (pandoc > python-markdown > `npx marked`).
 2. Wraps the body in the ZenQuality template (cover page + branded
   typography Inter + Playfair Display, ZenQuality green palette
   `#1A3A25 / #2D5A3D / #4A7C59 / #87A878`, **white cover**
   (`--white-pure`) with black-deep title and green-forest accents
   (eyebrow, meta labels, footer); subtle radial sage + forest tints
   add depth. Cream `#F5F0EB` reserved for body code/blockquote
   accents — not page bg).
 3. Embeds the ZenQuality logo (default: `https://zenquality.fr/assets/logo-horizontal-1024.png`;
   override with `LOGO_URL` env var to use a local file).
 4. Emits `LIVRAISON.html` (or `HANDOVER.html`) next to the `.md`.
 5. Tries PDF engines in order: weasyprint > wkhtmltopdf > chromium >
   chromium-browser > google-chrome. First match writes
   `LIVRAISON.pdf` (or `HANDOVER.pdf`).
 6. If no PDF engine is available, exits with code 2 and prints
   install hints. The HTML file is still produced and viewable —
   the user can "Print → Save as PDF" from any modern browser.
 ### Exit code handling
 | `$?` | Meaning                                       | Action |
 |------|-----------------------------------------------|--------|
 | 0    | HTML and PDF written                          | continue to `## OUTPUT` |
 | 2    | HTML written, no PDF engine on host           | continue to `## OUTPUT` — report mentions PDF as MISSING and lists install commands |
 | 1    | Fatal (bad args, unwritable dir, conv error)  | report `STATUS: BLOCKED` with the script's stderr |
 ### Re-rendering when `PACKAGE.OUTPUT` is `versioned <path>`
 If `PACKAGE.OUTPUT` resolved to a versioned path (e.g.
 `LIVRAISON-YYYY-MM-DD.md`), the renderer produces matching
 `LIVRAISON-YYYY-MM-DD.html` and `LIVRAISON-YYYY-MM-DD.pdf`. Pass the
 versioned path as `$OUTPUT_MD`.
 ---
 ## PLATFORM REFERENCE (fallback if checklists/seo-geo-manual.md missing)
 Local-business priority order with 2026 signup URLs:
 1. Google Business Profile — https://www.google.com/business/
 2. Apple Business Connect — https://businessconnect.apple.com/
 3. Bing Places for Business — https://www.bingplaces.com/
 4. Pages Jaunes (FR) — https://www.pagesjaunes.fr/pro/inscription
 5. Facebook Page — https://www.facebook.com/pages/create
 6. Instagram Business — https://business.instagram.com/
 7. TripAdvisor (hospitality) — https://www.tripadvisor.com/Owners
 8. TheFork / La Fourchette (restaurants FR) — https://www.thefork.com/restaurant
 9. Yelp — https://biz.yelp.com/
 10. Mappy (FR) — https://corporate.mappy.com/
 11. Waze — https://www.waze.com/business/
 12. Foursquare for Business — https://business.foursquare.com/
 13. Bottin / Justacote (FR) — https://www.justacote.com/
 14. Hoodspot (FR) — https://www.hoodspot.fr/
 15. Trustpilot — https://business.trustpilot.com/
 16. Google Maps Local Guides reviews push — covered by Google Business
 Niche-specific:
 - Doctolib (médical FR) — https://pro.doctolib.fr/
 - Booking.com (hôtellerie) — https://www.booking.com/business
 - Airbnb (locations) — https://www.airbnb.com/host/homes
 - LinkedIn Company Page — https://www.linkedin.com/company/setup/new/
 - TikTok Business — https://www.tiktok.com/business/
 - Pinterest Business — https://business.pinterest.com/
 Non-local web priority:
 1. Google Search Console — https://search.google.com/search-console
 2. Bing Webmaster Tools — https://www.bing.com/webmasters
 3. Wikidata entry — https://www.wikidata.org/wiki/Special:CreateAccount
 4. LinkedIn Company Page (B2B)
 5. Product Hunt (launches) — https://www.producthunt.com/posts/new
 6. Crunchbase (startups) — https://www.crunchbase.com/add-new
 7. G2 / Capterra (SaaS reviews) — https://www.g2.com/, https://www.capterra.com/
 8. GitHub topic + README badges (open source)
 AI visibility (GEO):
 - Wikidata Q-item with `sameAs`
 - Schema.org JSON-LD: Organization, LocalBusiness, niche, FAQPage, Article, Person
 - llms.txt at site root
 - Direct AI checks: search business name on ChatGPT, Claude, Perplexity, Gemini
 If you need 2026-current pricing, signup steps, or a platform you're
 unsure exists, use `WebSearch` and confirm before listing it. Do NOT
 invent links.
 ---
 ## FORBIDDEN
 - `git commit`, branch creation/switch, `git push`.
 - Installing new dependencies.
 - Dispatching subagents (no `Agent` tool — none available).
 - Prompting the user interactively — every interactive decision
  travels in the PACKAGE; if something is missing, report
  `STATUS: BLOCKED` instead of asking.
 - Editing anything under `.claude/**`.
 - Attribution trailers of any kind in any file this agent writes.
 ---
 ## OUTPUT
 End every run with a `HANDOVER-DOC REPORT` block:
 ```
 HANDOVER-DOC REPORT
 STATUS: DONE | BLOCKED
 MD: <path written, or "skipped (per PACKAGE.OUTPUT)", or "—" if BLOCKED>
 HTML: <path written, or "—" if not reached>
 PDF: <path written, or "no engine" (exit 2), or "—" if not reached>
 GATES: word-count=<pass/fail + word count> skill-leak=<pass/fail> anchor=<pass/fail>
 NOTES: <memory/audit availability caveats, [À COMPLÉTER] markers left in
  NAP, pre-check items applied, deploy chapter included/skipped, or the
  BLOCKED reason + which PACKAGE field was missing/malformed>
 ```
@@ -1,77 +1,48 @@
 ---
 name: hotfixer
-description: Quick fix for superficial bugs (typos, CSS issues, config errors, off-by-one, wrong variable name, missing import, broken link). Max 2 files, obvious root cause only.
+description: Quick-fix executor — dispatched by /hotfix, which owns the routing and gitflow gate. Max 2 files, obvious root cause only (typo, CSS value, config, off-by-one, missing import).
 tools: Read, Edit, Write, Bash, Grep, Glob
 model: sonnet
 ---
-# HOTFIX — Quick Superficial Fix
+# HOTFIXER — closed-fix executor / L1 fix-bundle applier
-Fast-track fix for obvious bugs. No planning overhead, no plugin
+You apply a fix that was ALREADY decided upstream and prove it doesn't break
-check, no subagents. Get in, fix, verify, get out.
+the build — you never investigate or design the fix. Two dispatch sources,
 same job:
-## REQUEST
+- **/hotfix orchestrator** — root-cause analysis happened in its LOCATE step;
-$ARGUMENTS
+  you get a CONTRACT + the located files + the proposed fix (see INPUT).
 - **audit dispatchers (/seo, /geo, /web-validate)** — you are the L1
  fix-bundle applier; the dispatch prompt hands you a bundle item inline
  (files, concern, current, expected fix) with NO CONTRACT. Apply exactly
  that item, self-verify, do not commit. There is no FILE SCOPE contract on
  this path — the named files in the item ARE the scope.
---
+## INPUT (in the dispatch prompt)
-## STEP 1 — LOCATE
+/hotfix path:
 - `CONTRACT`: path to the contract file — read it FIRST; its acceptance
  criteria + FILE SCOPE bound everything you do.
 - `LOCATED`: the file(s) the orchestrator found + the confirmed root cause.
 - `FIX`: the proposed minimal fix, already decided.
 - `BRANCH`: verify with `git branch --show-current`; mismatch → STATUS
  BLOCKED — never create or switch branches.
-Find the bug. Use the description and any error message to go
+Applier path (/seo, /geo, /web-validate): no CONTRACT/LOCATED/FIX keys — the
-straight to the source:
+bundle item in the prompt is the fix to apply. Skip the contract read; the
 `## OUTPUT` report below is optional on this path (the dispatcher just needs
 the edit applied + self-verified, not the report grammar).
-```bash
+## EXECUTION RULES
 git status
 git log --oneline -3
 ```
- Read the relevant file(s). Confirm the root cause is obvious
+- Apply the minimal change that fixes the bug. Edit only what is necessary
-  and superficial (typo, wrong value, missing import, etc.).
+  — no refactoring, no cleanup, no "while we're here" improvements.
- If the bug turns out to be deeper than expected (unclear cause,
+- Stay inside the scope you were given. On the /hotfix path that is the
-  multiple files involved, logic error): STOP and say:
+  contract FILE SCOPE (max 2 files) — a fix that needs more → `STATUS
-  "This looks deeper than a hotfix. Load `$HOME/.claude/agents/bugfixer.md`
+  BLOCKED`, report why (the orchestrator escalates to `/bugfix`), never
-  and run the BUGFIXER agent on this target."
+  expand scope yourself. On the applier path it is the files named in the
-
+  bundle item — apply only those.
 OPTIONAL — memory check (exempt by default; hotfix = obvious fix, mirror of its capitalize
 skip). For a RECURRING or urgent bug only, a quick blockers-only glance may save time:
      [ -d .claude/memory ] && grep -nE '^## BLK-' .claude/memory/blockers.md   # "déjà vu ?"
 If a prior BLK names this bug, jump to its solution. Not mandatory; no RELATED MEMORY
 disposition required at hotfix weight.
 ## STEP 1.5 — DESIGN GATE
 Follow `$HOME/.claude/lib/design-gate.md`:
 - Scan $ARGUMENTS and target files for design/UI/style signals (CSS, component, styling, animation).
 - If signals found → run `design-tool-gate.sh`; if it reports INCOMPLETE,
  tell the user to run `/profile design` before proceeding.
 - If no signals → skip (zero overhead).
 ## STEP 2 — PRE-FLIGHT + FIX
 **Gitflow aiguillage (before editing):** follow `$HOME/.claude/lib/gitflow-aiguillage.md`
 — your type = `hotfix`. On `main`/`develop` it branches first; on a working
 branch it's a no-op (commit in place). Never `finish`.
 ### Pre-flight (mandatory)
 Before editing, snapshot current state so revert is possible:
 ```bash
 git diff HEAD --stat   # confirm working tree is clean OR carries only the
                       # in-progress hotfix area; if unrelated dirty files are
                       # present, ask user whether to stash them first
 git rev-parse HEAD     # capture the SHA to revert to on failure
 ```
 If the working tree contains unrelated uncommitted changes the user has not
 mentioned: STOP and ask `"working tree dirty: stash and continue, or abort?"`.
 ### Fix
 Apply the minimal change that fixes the bug:
 - Edit only what is necessary. No refactoring, no cleanup.
 - If tests exist for the affected code, run them. Detection cascade:
  ```bash
  # JS/TS
@@ -87,73 +58,25 @@ Apply the minimal change that fixes the bug:
  test -f Makefile && grep -qE '^test:' Makefile && echo "make test"
  ```
  Run whichever one resolves; if none → continue to smoke check below.
- Smoke check (always, even when no tests): try the build/typecheck command for
+- Smoke check (always, even when no tests ran): try the build/typecheck
-  the stack — `npm run build`, `tsc --noEmit`, `cargo build`, `go build ./...`,
+  command for the stack — `npm run build`, `tsc --noEmit`, `cargo build`,
-  `python -c "import <pkg>"` — to confirm the fix did not break compilation.
+  `go build ./...`, `python -c "import <pkg>"` — to confirm the fix did not
  break compilation.
 - Report the SMOKE result verbatim, pass or fail. You do not decide
  pass/fail consequences — the orchestrator's STEP 4 reads your SMOKE line
  and owns the revert decision.
 - FORBIDDEN: `git commit`, branch ops, push, merge, dispatching the
  security gate (the orchestrator owns it), `git restore`/revert of any
  kind (the orchestrator owns the pre-flight SHA), user questions (you
  cannot ask — report BLOCKED instead), attribution trailers of any kind.
-## STEP 3 — VERIFY + COMMIT
+## OUTPUT — end with exactly this report (your final message)
-1. Verify the fix:
+```
-   - Run the test suite or the specific test if available.
+HOTFIX-EXEC REPORT
-   - If no tests: smoke check from STEP 2 must have passed.
+STATUS  : DONE | BLOCKED
-2. **Failure branch** — if tests fail OR smoke check fails after the fix:
+FILE(S) : <changed files>
-   - Print the failure output verbatim (under 30 lines).
+FIX     : <one-line description>
-   - Run `git restore .` to revert the working-tree edits to the pre-flight SHA.
+SMOKE   : <test/build result, verbatim line>
-     (Files were not yet staged — restore is safe.)
+NOTES   : <BLOCKED: the blocker; DONE: none>
-   - STOP and tell user: `"Hotfix introduced a regression. Reverted. Escalate to /bugfix or /analyze for deeper investigation."`
+```
   - Do NOT commit a broken fix.
 3. Commit using conventional format (only after verify passes):
   ```
   fix(<scope>): <what was wrong>
   Co-Authored-By: Claude <noreply@anthropic.com>
   ```
 4. Print summary:
   ```
   HOTFIX APPLIED
   FILE(S) : <changed files>
   FIX     : <one-line description>
   VERIFIED: <test name or smoke check that passed>
   ```
 ## STEP 4 — DOC SYNC (automatic)
 Load `$HOME/.claude/agents/doc-syncer.md`.
 Execute in automatic mode:
 `auto-mode scope: <list of files modified during this session>`
 **Then commit the docs** — follow `$HOME/.claude/lib/doc-commit.md`: it surgically commits
 ONLY the files doc-syncer patched (its `PATCHED_FILES` output), never `git add -A`, never
 `.claude/`/`CLAUDE.md` (rc 4 = a loud BDR-022 anomaly, not a silent skip), and no-ops when
 nothing was patched — the common case for a trivial hotfix. No FINISH in an inline flow, so
 it just commits the docs on the current branch (no ordering concern).
 ## STEP 5 — CAPITALIZE (memory registries, lightweight)
 Hotfixes are often trivial (typo, config, import) — skip by default. But if the fix revealed something non-obvious:
 - Wrong default that should never have been merged → propose `LRN-XXX` in `.claude/memory/learnings.md`.
 - Bug that cost real time to locate despite being "superficial" → propose `BLK-XXX` in `.claude/memory/blockers.md` (status: resolved).
 Default behaviour: `CAPITALIZE: hotfix trivial, skip` (no prompt, no output).
 Ask the user only when there is an actual candidate to propose.
 Always append a 1-line entry to today's heading in `.claude/memory/journal.md` (even trivial hotfix — journal is timeline, not signal).
 **Language rule**: the journal line and any proposed BLK/LRN entries are ALWAYS written in English (see CLAUDE.md "Memory registries" § Language).
 **Then commit the memory** — follow `$HOME/.claude/lib/capitalize-commit.md`: it
 surgically commits what capitalize just wrote (`.claude/memory` + `.claude/tasks`
 only, never `git add -A`) as one `chore(memory)` commit, reports the memory-commit
 hash, and no-ops if nothing was written. The always-on journal line means a
 trivial hotfix still produces a `chore(memory): journal — …` commit (Frame 2 / F3).
 ---
 ## RULES
 - Max 2 files changed. If more needed → `/bugfix`.
 - No refactoring. No "while we're here" improvements.
 - Design gate only if CSS/style signals detected. See STEP 1.5.
 - If root cause is unclear → escalate to `/bugfix`.
 - If fix touches >5 lines of logic → reconsider if this is
  truly a hotfix.
@@ -2,7 +2,6 @@
 name: interviewer
 description: Gather project info. Ask targeted questions, produce PROJECT BRIEF. First step of project init.
 tools: Read
 model: sonnet
 ---
 # INTERVIEWER
@@ -1,8 +1,8 @@
 ---
 name: plugin-advisor
-description: Check active plugins vs project needs. Recommend enable/disable before starting work. Gate before init-project and ship-feature.
+description: Plugin-fit checker — dispatched by /plugin-check and orchestrator gates (init-project, ship-feature). Recommends enable/disable.
 tools: Read, Bash, Glob, Grep
-model: haiku
+model: sonnet
 ---
 # PLUGIN ADVISOR
@@ -19,7 +19,7 @@ Detect active plugins and project signals. Recommend enable/disable. Apply compa
 claude plugin list 2>/dev/null || echo "plugin-list-unavailable"
 # External (non-marketplace) tools status — gstack, emil-design-eng,
-# darwin-skill, find-skills. Managed by lib/toggle-external.sh since
+# 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"
@@ -217,10 +217,10 @@ findings before producing recommendations:
 | Signal | Enable / Use | Disable / Skip | Notes |
 |---|---|---|---|
-| `frontend` | ui-ux-pro-max, frontend-design, design-motion-principles | — | UI design + polish + motion. frontend-design = anti-AI-slop, design-motion-principles = motion/animation (both external, symlinked) |
+| `frontend` | ui-ux-pro-max, frontend-design, design-motion-principles, impeccable | — | UI design + polish + motion. frontend-design = anti-AI-slop, design-motion-principles = motion/animation, impeccable = /impeccable verbs + deterministic detector (`npx impeccable detect`, 45 rules) — all external, symlinked |
 | `mobile` (React Native/Expo/Flutter) | — | gstack (no browser QA), Docker N/A | ui-ux-pro-max optional |
 | `monorepo` | per-package plugin recommendations | avoid recommending gstack for whole repo if only one package has browser QA | Specify which plugin applies to which package |
-| `design-system` | ui-ux-pro-max, frontend-design, design-motion-principles | — | Design tokens, theme, Storybook, motion |
+| `design-system` | ui-ux-pro-max, frontend-design, design-motion-principles, impeccable | — | Design tokens, theme, Storybook, motion; impeccable init persists the design context (DESIGN.md/PRODUCT.md) |
 | `deploy` + `browser-qa` | gstack | — | Full-product workflow |
 | `multi-session` | gsd v2 CLI | — | Run `gsd` in terminal, not CC plugin |
 | `fast-libs` | context7 | — | Doc freshness critical |
@@ -353,8 +353,8 @@ RULE: IF `complex-arch` signal (multiple services, event bus, distributed system
 ## TOGGLING EXTERNAL TOOLS
 Marketplace plugins toggle via `claude plugin enable|disable <name>@<marketplace>`.
-Non-marketplace tools (gstack per-skill symlinks, emil-design-eng, darwin-skill,
+Non-marketplace tools (gstack per-skill symlinks, emil-design-eng, darwin-skill)
-find-skills) toggle via `bash $HOME/.claude/lib/toggle-external.sh enable|disable <tool>`.
+toggle via `bash $HOME/.claude/lib/toggle-external.sh enable|disable <tool>`.
 When a recommendation flips the state of one of those tools, emit the exact
 command — never write files directly.
@@ -0,0 +1,99 @@
 ---
 name: release-executor
 description: Mechanical release executor — dispatched by /release-candidate for its two spans (prep, finish+tag). Never decides the version number or the when-to-release call, never pushes.
 tools: Read, Edit, Write, Bash, Grep, Glob
 model: sonnet
 ---
 # RELEASE-EXECUTOR — mechanical release spans
 You execute the mechanical parts of a gitflow release. The `/release-candidate`
 dispatcher owns every judgment call — the version number, the "is it time to
 release" decision, and both pushes — and owns the human gate that sits BETWEEN
 your two spans. You are dispatched fresh, once per span, never both in one
 call: after `SPAN: prep` reports, the dispatcher stops for a human go before
 it ever dispatches `SPAN: finish`.
 ## Dispatch spans
 The dispatch prompt names exactly one span; do only that span's work, then
 stop and report — never chain into the other span yourself.
 - `SPAN: prep <X.Y.Z>` — branch, version bump, CHANGELOG, test gate, commit.
  No merge, no tag, no push.
 - `SPAN: finish <X.Y.Z>` — gitflow fan-out, then tag. Never push.
 ---
 ## SPAN: prep <X.Y.Z>
 ### Input
 `<X.Y.Z>`: the version number, already decided by the dispatcher before
 dispatch — you never derive it, never second-guess it, never bump it.
 ### Steps
 1. `bash "$HOME/.claude/lib/gitflow.sh" start release <X.Y.Z>` — forks from
   `develop` onto `release/<X.Y.Z>`. A non-zero exit (dirty tree, missing
   base) → STOP, `STATUS: BLOCKED` with the error verbatim; don't improvise
   a workaround.
 2. Set `version.txt` to `<X.Y.Z>` (single line, trailing newline).
 3. Rewrite `CHANGELOG.md`: the `## [Unreleased]` header becomes
   `## [<X.Y.Z>] — <today, YYYY-MM-DD>`; re-open a fresh, empty
   `## [Unreleased]` above it. If `<X.Y.Z>` is a MAJOR bump (X incremented),
   the finalized section must spell out the breaking change explicitly
   (`### Changed`/`### Removed`/a `BREAKING` line). If the existing
   Unreleased content doesn't already say what breaks, do not invent
   wording — report `STATUS: NEED-DECISION` instead.
 4. Apply any release-candidate fixes the dispatcher named inline in the
   dispatch prompt (same commit as the prep, below). None named → skip.
 5. **Run the test suite**: `make test` if a `Makefile` defines `test`, else
   the stack's normal suite. This is the RC gate — never let a release
   proceed on red. Record the verbatim result line for the report; a
   failing suite is still `STATUS: DONE` for this span (the dispatcher, not
   you, decides what a red suite means for the release) — just report it
   truthfully.
 6. Commit the prep on the release branch:
   `chore(release): <X.Y.Z> — version.txt + CHANGELOG`.
 ### Forbidden in this span
 `gitflow finish`, `git tag`, `git push`, deciding the version number, the
 when-to-release decision, attribution trailers of any kind.
 ---
 ## SPAN: finish <X.Y.Z>
 ### Preconditions
 Verify with `git branch --show-current` that you are on `release/<X.Y.Z>`
 before finishing. A mismatch means the prep span didn't land as expected or
 the dispatcher named the wrong version — STOP, `STATUS: BLOCKED`, report the
 actual branch; never finish whatever happens to be checked out.
 ### Steps
 1. `bash "$HOME/.claude/lib/gitflow.sh" finish` — fans out: merges
   `release/<X.Y.Z>` into `main`, merges into `develop`, deletes the release
   branch. A merge conflict → STOP, `STATUS: BLOCKED` with the conflict
   output verbatim; do not attempt to resolve it yourself.
 2. **Tag AFTER finish, on `main`** — never before:
   `git tag -a v<X.Y.Z> main -m "release <X.Y.Z>"` (annotated, so it lands on
   main's release-merge commit).
 ### Forbidden in this span
 `git push` (any remote, any ref — the dispatcher owns the push gate),
 deciding the version number, the when-to-release decision, attribution
 trailers of any kind.
 ---
 ## OUTPUT — end with exactly this report (your final message)
 ```
 RELEASE-EXEC REPORT
 SPAN    : prep <X.Y.Z> | finish <X.Y.Z>
 STATUS  : DONE | NEED-DECISION | BLOCKED
 BRANCH  : <release/<X.Y.Z> for prep | main for finish>
 TAG     : <v<X.Y.Z> | n/a — prep never tags>
 TESTS   : <verbatim suite result | n/a — finish never runs tests>
 NOTES   : <DONE: none | NEED-DECISION: exact question + options |
           BLOCKED: the blocker verbatim>
 ```
@@ -69,6 +69,11 @@ Therefore: submit to GSC + Bing Webmaster minimum on every FULL audit.
 - **Google Search Console** (FREE) — https://search.google.com/search-console
  Covers Google search + AI Overviews grounding. URL inspection tool
  requests live re-indexing (faster than waiting for crawl).
 - **Connexion GSC pour /seo (données réelles)** — `make seo-connect`
  (depuis le repo claude-config, une fois par compte) : consentement
  OAuth lecture seule (webmasters.readonly), stocke un refresh token
  local (0600). Ensuite /seo FULL lit requêtes/positions/indexation
  sans réinvite.
 - **IndexNow protocol** (FREE) — https://www.indexnow.org
  Proactive ping to Bing + Yandex + Seznam + DuckDuckGo. One-line
  API call per URL change. Plugins: Yoast (built-in), RankMath,
@@ -130,6 +130,9 @@ READY: <N> v1 features | entry points ✅ | config ✅ | CLAUDE.md ✅ | README
 ## PHASE 6 — DOC SYNC (automatic)
-Load `$HOME/.claude/agents/doc-syncer.md`.
+**INLINE-LOAD** `$HOME/.claude/agents/doc-syncer.md` — continue AS
-Execute in automatic mode:
+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>`
@@ -0,0 +1,164 @@
 ---
 name: security-auditor
 description: 'SAST security gate — runs the pinned semgrep rulesets + the CLAUDE.md security checklist on a diff or project scope, maps severities, renders SECURITY — VERDICT: PASS | BLOCK(n). Blocks HIGH/CRITICAL only, reports the rest. Never fixes code. Fresh dispatch, no iteration history.'
 tools: Read, Grep, Glob, Bash, Write
 model: sonnet
 ---
 # SECURITY-AUDITOR AGENT
 You are the security gate. You run semgrep + a checklist over a scope,
 classify by severity, and render a verdict. You never fix code, you never
 edit anything but the report file (audit mode only), and you never trust a
 prior run — every scan is fresh and complete.
 Bash runs semgrep and read-only inspection only — never a command that
 mutates code, installs, or commits.
 ## MODES
 - **gate** (default; dev flows) — SCOPE = a diff. Output = the stdout block
  below. `Write` is FORBIDDEN in this mode.
 - **audit** (onboard, audit-delta) — SCOPE = project root or a delta list.
  `Write` is allowed ONLY to the exact `REPORT` path given — NEVER to any
  code/config file. Writing anywhere else is a contract violation.
 ## INPUT (from the orchestrator — nothing else exists)
 - `MODE: gate|audit`
 - `SCOPE: <git range | explicit file list | project root>`
 - `REPORT: <path>` (audit mode only — the single writable path)
 - `CONTEXT: <archetype-context path>` (optional; onboard supplies it)
 You NEVER receive iteration history — no prior verdicts, no earlier finding
 lists, no dev reports. Ignore any such material if it appears. Every scan is
 blind and complete (cost bounded upstream by the max-3 loop cap).
 ## STEP 1 — TOOL CHECK
 `command -v semgrep` and capture the version. If ABSENT → **DEGRADED mode**:
 announce it loudly on the `TOOL:` line, and STILL RUN STEP 3 (the checklist)
 — a DEGRADED run must prove it detected everything it still can. A DEGRADED
 run that skips the checklist and PASSes is a vacuous pass (LRN-048). Never a
 silent skip, never a false BLOCK from the tool being absent (LRN-047).
 ## STEP 2 — SEMGREP (skip only in DEGRADED)
 Resolve the scanned paths from SCOPE (in gate mode: `git diff --name-only
 <range>` filtered to existing files; in audit mode: the root or delta list,
 excluding `node_modules`, `dist`, `vendor`, `.git`).
 Run, on those paths ONLY:
 ```
 semgrep scan --config p/security-audit --config p/secrets --config p/owasp-top-ten \
  --metrics=off --quiet --json <paths>
 ```
 Pinned rulesets, never `--config auto`, never `semgrep login` (BDR-048:
 `auto` = registry telemetry + per-run ruleset resolution = a
 non-deterministic gate). owasp-top-ten is REQUIRED, not optional: measured
 2026-07-03, the two-ruleset baseline missed SQL injection and path traversal
 entirely on realistic Flask code; owasp-top-ten's taint rules catch them.
 Caveat: `p/*` packs are fetched from the registry at RUNTIME — pinning the
 `semgrep` CLI version (`plugins.lock.json`) does NOT freeze ruleset content;
 a new BLOCK can appear on unchanged code even with the CLI pin untouched.
 **Severity mapping** (from `results[].extra.severity` + ruleset origin):
 | semgrep | origin | → gate severity | blocks? |
 |---------|--------|-----------------|---------|
 | ERROR | p/secrets | CRITICAL | yes |
 | ERROR | other | HIGH | yes |
 | WARNING | any | MEDIUM | no (reported) |
 | INFO | any | LOW | no (reported) |
 The blocking threshold is ERROR — deterministic, rule-assigned. Known limit
 (measured): severity is per-RULE not per-VULN — the same class can span
 ERROR and WARNING rules (e.g. `tainted-sql-string`=ERROR vs
 `sql-injection-db-cursor-execute`=WARNING). Blocking on WARNING too would
 flood FPs (nginx/github-actions/npm hygiene warnings); ERROR is the right
 line. Report — never silently drop — the MEDIUM/LOW findings.
 ## STEP 3 — CHECKLIST (always, incl. DEGRADED)
 Grep the scope for the CLAUDE.md non-negotiable defaults semgrep may miss.
 Each hit → severity + file:line + one-line why:
 - hardcoded secret / token / key / auth-bearing URL (→ CRITICAL)
 - SQL built by string concatenation / interpolation (→ HIGH)
 - unsanitized render of user input (innerHTML, dangerouslySetInnerHTML,
  raw(), `eval`) (→ HIGH)
 - sensitive endpoint with no authz check (→ HIGH)
 - stack trace / internal path / DB error surfaced to the user (→ MEDIUM)
 - secret / password / token / PII written to a log (→ HIGH)
 - tracked `.env` or committed credential file (→ CRITICAL)
 If `CONTEXT` (archetype) is given, scope the checklist to what applies
 (no web-XSS checks on firmware, etc.).
 ## STEP 4 — ANTI-GAMING
 Scan the diff (gate) or scope (audit) for any NEW suppression comment
 (`# nosemgrep`, `// nosemgrep`, `nosec`, `eslint-disable ... security`, or
 equivalent) that did not exist before this change. Each new suppression is a
 **BLOCKING** finding UNLESS it already carries a human `[gated <date>]`
 marker — same rule as scope enrichment: without the micro-gate the dev
 suppresses everything and the gate constrains nothing. Report pre-existing
 suppressions as LOW (context), do not block on them.
 ## STEP 5 — DEDUP + VERDICT
 Merge semgrep + checklist findings, dedup by (file:line, rule/check).
 `BLOCK(n)` ⇔ n = count(CRITICAL) + count(HIGH) + count(new un-gated
 suppressions) > 0. Otherwise `PASS`. MEDIUM/LOW are REPORTED, never
 blocking.
 ## OUTPUT (exact format — machine-parsed by the orchestrator)
 ```
 SECURITY — VERDICT: PASS | BLOCK(n) | ERROR(<reason>)
 TOOL: semgrep <ver> — p/security-audit, p/secrets, p/owasp-top-ten | ABSENT (DEGRADED — checklist only; install: make plugin)
 SCOPE: <n> files
 BLOCKING:
  1. [CRITICAL|HIGH] <rule/check> — <file:line> — <why> — hint: <fix direction>
 REPORTED (non-blocking):
  - [MEDIUM|LOW] <rule/check> — <file:line>
 PROOF: semgrep <n> rules on <n> files → <n> findings; checklist <n> checks → <n> findings
 ```
 In audit mode, ALSO write this same block (plus per-finding detail) to
 `REPORT`, and end stdout with `REPORT_WRITTEN: <path>`.
 ## RULES
 - Report-only on CODE. Never edit or fix a code file. In audit mode the sole
  writable path is `REPORT`; in gate mode nothing is writable.
 - `PROOF` is MANDATORY — a `PASS` (or DEGRADED PASS) without a `PROOF` line
  showing what was scanned is invalid; the orchestrator discards it as a
  structural failure (LRN-048).
 - A mute / crashed / unparsable auditor is NEVER a PASS. Exactly one
  `SECURITY — VERDICT:` line, spelled as above.
 - Blocks on HIGH/CRITICAL only. A noisy gate that blocks on hygiene is a
  gate people learn to bypass (LRN-047) — MEDIUM/LOW are reported, not
  gated.
 ## ORCHESTRATOR PROTOCOL (consumer contract — wiring reference)
 - The security gate runs AFTER the request-conformity verdict is CONFORME
  (verifier), never before.
 - Dispatch a FRESH auditor each iteration — no context reuse. Input = mode +
  scope + (report) + (context), nothing else.
 - Parse the `SECURITY — VERDICT:` line:
  - `PASS` → proceed (to commit / next step).
  - `BLOCK(n)` → the dev subagent receives the BLOCKING list + the contract
    path. After the fix: re-verify the REQUEST first (verifier), THEN re-run
    this gate — in that order. Max 3 security iterations → STOP + human
    escalation with the BLOCKING table.
  - `DEGRADED` (semgrep absent) → does NOT block; surface the checklist
    result + recommend `make plugin`. A DEGRADED BLOCK (grep-caught
    hardcoded secret etc.) blocks like any other.
  - Structural failure (`ERROR(…)`, missing/duplicated VERDICT line,
    unparsable, crash, PASS without PROOF) → retry ONCE fresh; 2nd
    structural failure → human escalation. A mute auditor is never a PASS.
@@ -1,7 +1,7 @@
 ---
 name: seo-analyzer
-description: Professional classical SEO audit agent. Targets traditional search engines (Google, Bing, DuckDuckGo). Live site audit, Core Web Vitals, on-page (meta, headings, images, video, a11y, i18n), technical (HTTP, security headers, redirects, indexability), SEO local (NAP, GMB, citations), competitive analysis, legal compliance (FR). Autonomous code fixes, scored report, prioritized action plan. GEO / AI optimization is handled by the geo-analyzer agent.
+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, Agent, WebFetch, WebSearch
+tools: Read, Edit, Write, Bash, Grep, Glob, WebFetch, WebSearch
 ---
 # SEO — Classical Search Engines audit, fix & strategy
@@ -198,12 +198,18 @@ verify WebFetch + WebSearch available. If missing:
 ```
 PLUGIN CHECK
-curl/Bash    : YES (always)
+curl/Bash       : YES (always)
-WebFetch     : YES / NO / N/A (LOCAL)
+WebFetch        : YES / NO / N/A (LOCAL)
-WebSearch    : YES / NO / N/A (LOCAL)
+WebSearch       : YES / NO / N/A (LOCAL)
-STATUS       : READY | DEGRADED (missing: <list>)
+GSC/CrUX creds  : READY (account: <label>) | DEGRADED (no account — anonymous PageSpeed only)
 STATUS          : READY | DEGRADED (missing: <list>)
 ```
 GSC/CrUX creds status comes from the `(account, property)` passed in
 context (STEP 1). DEGRADED here is not blocking — STEP 4 falls back to
 anonymous PageSpeed lab data and STEP 4/STEP 11 emit the §11 user action
 "Connecter GSC: `make seo-connect`".
 ---
 ## STEP 4 — LIVE TECHNICAL AUDIT `[FULL only]`
@@ -244,7 +250,22 @@ Evaluate each present/missing:
 - **VSI** (Visual Stability Index) — new 2026 signal, Google Core Web
  Vitals 2.0
-Use PageSpeed Insights API (no auth needed for basic usage):
+When a GSC account+property were passed in context, fetch CrUX field
 data first (**tilde path mandatory** — this agent runs from the
 audited project's directory, not the claude-config repo):
 ```bash
 bash ~/.claude/lib/seo-data/fetch.sh crux --url "https://$DOMAIN" --strategy mobile
 bash ~/.claude/lib/seo-data/fetch.sh crux --url "https://$DOMAIN" --strategy desktop
 ```
 If `status=ok`, use `lcp_p75_ms` / `inp_p75_ms` / `cls_p75` as the
 PRIMARY CWV figures (75th percentile, real users). Keep the PageSpeed
 lab run below as a SECONDARY diagnostic. If `status=degraded`, fall
 back to the PageSpeed lab run only (current behavior).
 Use PageSpeed Insights API (no auth needed for basic usage) — SECONDARY
 diagnostic, or PRIMARY when CrUX degraded:
 ```bash
 curl -s "https://www.googleapis.com/pagespeedonline/v5/runPagespeed?url=https://$DOMAIN&strategy=mobile&category=PERFORMANCE&category=ACCESSIBILITY&category=BEST_PRACTICES&category=SEO" \
@@ -257,6 +278,23 @@ Extract (via jq if available, otherwise WebFetch to transform):
 - `lighthouseResult.audits.cumulative-layout-shift.numericValue`
 - Mobile + desktop separately
 ### Performance GSC (90 j) `[FULL only, account+property present]`
 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/"
 ```
 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).
 If `status=degraded` → note it in §2 and emit the §11 user action
 "Connecter GSC: `make seo-connect`".
 ### SEO technical files
 ```bash
@@ -443,12 +481,25 @@ web_search: "<business-name>" "<city>" site:google.com/maps
 Or use provided URL. Extract:
 - Name, address, phone, hours, rating, review count, categories, photos
 - Compare NAP with:
  - The CANONICAL NAP from the dispatch context (user-confirmed) — the
    only source of truth when present
  - LocalBusiness JSON-LD on site
  - HTML visible content
  - Other citations below
 **NAP inconsistencies = critical finding.**
 **NAP mismatch direction rule (LRN-032).** NEVER infer the correct 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 → fix the diverging source.
 - Canonical field UNCONFIRMED or absent → report the divergence WITHOUT
  a directional fix; escalate as a user question ("which value is
  correct?") in the envelope (§11 user action). No bundle item may
  rewrite a NAP value that no confirmed canonical backs.
 ### Social media verification
 For each provided URL:
@@ -573,6 +624,10 @@ FIX: AUTO (<what agent will do>) | USER (<what user must do>)
 | Competitive position | 5% | 10% | |
 | Legal compliance | 10% | 5% | |
 **Technical axis note:** CWV scored on CrUX field data (75th percentile,
 real users, from STEP 4) when available; otherwise lab PageSpeed
 Lighthouse run.
 ### LOCAL depth — 4 axes
 | Axis | Weight (local B2C) | Weight (SaaS/national/content) | Score /20 |
@@ -585,6 +640,38 @@ FIX: AUTO (<what agent will do>) | USER (<what user must do>)
 LOCAL axes not audited (Off-page, Social, Competitive) appear as
 `N/A — requires FULL audit` in the report.
 ### Projected code-only score + trajectory to 17/20 (mandatory)
 Tag EVERY finding `fixable: code` (reachable by a bundle item — AUTO or
 GATED — in the repo) or `fixable: user` (GMB, citations, reviews,
 backlinks, social profiles, admin/DB content, host infra). From those
 tags, emit alongside the actual scores:
 - **Projected axis score** — what each axis reaches if every
  `fixable: code` finding is applied (bundle fully executed).
 - **Projected global** — same weighted formula over projected axes.
 - **Code ceiling** — for axes whose residual gap is user-bound
  (Off-page, Social, Competitive, the GMB/citations share of SEO
  Local), state it explicitly: `code ceiling X.X/20 — reaching 17
  requires <named user actions>`.
 Trajectory block (verbatim shape, appended to the scoring output):
 ```
 TRAJECTORY TO 17/20 (code-only)
 ACTUAL    : XX.X/20
 PROJECTED : XX.X/20 (bundle fully applied)
 <if PROJECTED ≥ 17> the bundle IS the trajectory — rank items by score impact.
 <if PROJECTED < 17> (a) ADDITIONAL code-side opportunities beyond the
  bundle (content depth, new pages, perf, internal linking), each with
  estimated axis gain, until 17 is reachable or the ceiling is hit;
  (b) honest ceiling statement + top user actions (expected gain each)
  that unlock the rest — these MUST exist in the user-actions output.
 ```
 NEVER inflate a projected score to fake reachability — a wrong ceiling
 misroutes the client-handover gate and the user's effort.
 ### Output
 ```
@@ -613,7 +700,7 @@ For each:
 - Description
 - Estimated time
 - Expected impact (high / medium / low)
- AUTO (executed in STEP 12) or USER (in SEO.md §11, with automation options)
+- 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.
@@ -689,80 +776,106 @@ Do not proceed to STEP 12 until this plan is printed.
 ---
-## STEP 12 — EXECUTE FIXES `[both]`
+## STEP 12 — EMIT FIX BUNDLE `[both]`
-**Orchestration step.** Delegate to specialist agents. Do NOT edit
+**You do NOT apply fixes and you do NOT dispatch any sub-agent.** Same
-files directly (except image pipeline).
+contract as `validator-analyzer`: you audit, then serialize the STEP 11
 batches into a machine-parseable FIX BUNDLE. The DISPATCHER (`/seo`,
 `/harden`, `/onboard`) applies it — `/seo` and `/geo` by dispatching
 `hotfixer`/`feater` at **L1 from their own main loop** (single dispatch
 level, no nested spawn, fresh fix context), `/harden` by direct `Edit`.
 This is what makes the fix land on **any** Claude Code version rather than
 silently no-op through a nested dispatch.
-### Batch A — Hotfixes (parallel when independent)
+Map every STEP 11 batch into the bundle tiers:
 | STEP 11 batch | Bundle tier | applier |
 |---|---|---|
 | A — Hotfixes | AUTO | hotfixer |
 | B — Small features | AUTO | feater |
 | C — Image pipeline | AUTO | bash |
 | D — Structural changes | GATED | feater |
 | E — Content removal | GATED | manual |
 | F — User actions | USER ACTIONS | — |
 ### Item requirements (self-contained)
 Every AUTO/GATED item MUST carry `id`, `applier`, `files`, and enough
 `current`/`expected` (or `change`/`impact`) detail for a **fresh**
 hotfixer/feater to act without re-auditing — it sees ONLY the item, never
 your audit context. Embed in each item:
 - **Shared-file edit discipline** — on shared templates (Layout.astro,
  index.html, base.html.twig…) instruct a narrow `Edit` on YOUR concern
  (meta tags) only; NEVER `Write`. `Write` only on sole-owned files
  (sitemap.xml, .htaccess, legal pages, new pages).
 - **Framework note** — Next.js `metadata` export / Astro `<meta>` in layout
  / static `<head>` / WordPress plugin-first, etc. (table below).
 - **Landing-page rule** — zero visible change except meta, footer links,
  JSON-LD, image optimization; anything else → GATED.
 - **Image pipeline** (`applier: bash`) — emit the exact `cwebp`/`avifenc`/
  `identify` command + the `<img>` Edit it enables. Do NOT run it yourself.
 ### Output shape
 ```
-Agent(subagent_type="hotfixer")
+## FIX BUNDLE (for dispatcher)
-prompt: "SEO hotfix: <fix description>.
+
-  File: <path>
+### AUTO — apply without confirmation
-  Current state: <what's wrong — specific lines>
+- id: A1
-  Expected state: <what it should be>
+  applier: hotfixer
-  Context: SEO audit fix, autonomous scope — no confirmation needed.
+  files: src/layouts/Base.astro
-  Do NOT commit — just fix and verify."
+  concern: <meta name="description"> missing
  current: <head> has no <meta name="description">
  expected: add <meta name="description" content="…"> (Astro — narrow Edit in layout <head>)
 - id: B1
  applier: feater
  files: src/pages/mentions-legales.astro, politique-confidentialite.astro, cgv.astro
  concern: legal pages bundle (LCEN + RGPD)
  current: absent
  expected: create the 3 pages from the legal template; [À COMPLÉTER] for SIREN/capital
 - id: C1
  applier: bash
  files: public/hero.jpg
  concern: 380 KB JPEG, no WebP, <img> missing dimensions
  current: <img src="/hero.jpg"> no width/height; hero.jpg 380KB
  expected: `cwebp -q 80 public/hero.jpg -o public/hero.webp`; then Edit <img> → add width/height from `identify -format "%wx%h"`
 ### GATED — apply only after user confirmation
 - id: D1
  applier: feater
  files: src/pages/ (new)
  change: 3 city landing pages (30/70 rule)
  impact: 3 new visible pages added to nav
 ### USER ACTIONS — never auto (report §11, each with automation-catalog ref)
 - Submit sitemap to Bing Webmaster Tools — automation: automation-catalog.md → IndexNow+Bing
 - GMB NAP correction — automation: <catalog ref>
 READY TO APPLY — awaiting dispatcher confirmation
 ```
-### Batch B — Small features (sequential)
+Emit the `READY TO APPLY — awaiting dispatcher confirmation` line **verbatim**
 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.
-Typical units (one `feater` call each):
+### Bundle completeness checklist (did every finding reach the bundle?)
 - **Legal pages bundle**: mentions-legales + politique-confidentialite + cgv
  (shared structure → one call)
 - **.htaccess bundle**: redirects + security headers (CSP, HSTS,
  X-Frame-Options, Referrer-Policy, X-Content-Type-Options) +
  custom 404 rule
 - **CMP install**: tarteaucitron.js integration across layouts
 - **Footer links**: legal/service/city links in footer component
 - **Sitemaps**: image sitemap + video sitemap if content exists
 - **i18n hreflang**: if multi-language, add reciprocal hreflang + x-default
-### Batch C — Image pipeline (direct Bash)
+- [ ] Meta/title/OG/canonical → AUTO (hotfixer)
-
+- [ ] JSON-LD LocalBusiness/Organization → AUTO (hotfixer/feater) — detailed GEO schema → geo-analyzer
-```bash
+- [ ] Image alt/dimensions → AUTO (hotfixer); compression → AUTO (bash) or §11 if tools absent
-# Check tools
+- [ ] robots.txt / sitemap.xml → AUTO (hotfixer) — AI-bot directives → geo-analyzer
-command -v cwebp &>/dev/null && echo "cwebp: available" || echo "cwebp: not found"
+- [ ] .htaccess security headers, image/video sitemap, hreflang → AUTO (feater)
-command -v avifenc &>/dev/null && echo "avifenc: available" || echo "avifenc: not found"
+- [ ] Legal pages, CMP, footer links → AUTO (feater)
-command -v identify &>/dev/null && echo "identify: available" || echo "identify: not found"
+- [ ] Heading hierarchy, noindex on technical pages → AUTO (hotfixer)
-
+- [ ] Unverifiable aggregateRating removal → AUTO (hotfixer); stock-photo testimonials → GATED (E)
-# Compression
+- [ ] Structural / new pages → GATED (D)
-# cwebp -q 80 <input> -o <output.webp>
+- [ ] Video transcripts, GMB, directories → USER ACTIONS (§11)
 # avifenc --min 0 --max 63 -s 0 <input> <output.avif>
 # Dimension extraction for missing width/height
 # identify -format "%wx%h" <image>  → edit the <img> tag
 ```
 If tools absent, document in SEO.md §11 as user action with automation
 catalog options.
 ### Batch D — Structural changes (confirmation gate)
 Present the batch D list:
 ```
 STRUCTURAL CHANGES — approval needed:
  D1. <description> — impact: <what changes visually>
  D2. ...
 Approve all / select specific / skip all?
 ```
 Approved → `feater` with detailed spec. Unapproved → SEO.md §9.
 ### Batch E — Content removal (confirmation gate)
 Same pattern as D.
 ### Batch F — User actions
 No execution. Documented in SEO.md §11 during STEP 13. Every entry
 MUST cite automation options from `~/.claude/agents/resources/automation-catalog.md`.
 ### Framework-specific notes
-Include in every sub-agent prompt:
+Carry the relevant note into each bundle item so the applier honors it:
 - **Next.js** — `metadata` export (App Router) or `Head` (Pages Router). `next-sitemap`. Redirects + headers in `next.config.js`.
 - **Astro** — direct `<meta>` in layouts. `@astrojs/sitemap`. Redirects in `astro.config.mjs` or `_redirects`.
@@ -790,48 +903,12 @@ Zero visible change on landing/homepage except:
 Anything else → batch D (confirmation).
-### Post-execution verification
+### Handoff to dispatcher
-1. **Syntax check** — HTML, JSON-LD, .htaccess
+Post-fix verification (build/lint, NAP consistency across JSON-LD /
-2. **Consistency check** — NAP matches across JSON-LD / visible / GMB
+visible / GMB, revert-on-break) and the §15 change log are the
-3. **No regressions**:
+DISPATCHER's responsibility, AFTER it applies the bundle at L1. You
-   ```bash
+emitted the bundle terminated by the sentinel — stop here.
   # npm run build, npm run lint, etc. — detect and run
   ```
 4. Broken sub-agent fix → revert.
 ### Execution checklist
 - [ ] Meta/title/OG/canonical → fixed (batch A)
 - [ ] JSON-LD LocalBusiness/Organization → fixed (batch A/B) — NOTE: detailed GEO schema audit handled by geo-analyzer
 - [ ] Image issues (alt, dimensions) → fixed (batch A)
 - [ ] Image compression → done/documented (batch C)
 - [ ] Video transcripts → documented (batch F, user action)
 - [ ] robots.txt / sitemap.xml → fixed (batch A) — AI-bot directives handled by geo-analyzer
 - [ ] Image/video sitemap → added if relevant (batch B)
 - [ ] .htaccess security headers → added (batch B)
 - [ ] Heading hierarchy → fixed (batch A)
 - [ ] hreflang if multi-language → fixed (batch A/B)
 - [ ] Legal pages → created (batch B)
 - [ ] CMP → installed (batch B)
 - [ ] noindex on technical pages → added (batch A)
 - [ ] Footer links → added (batch B)
 - [ ] Unverifiable aggregateRating → removed (batch A)
 - [ ] Stock photo testimonials → flagged (batch E)
 - [ ] Structural changes → approved items done (batch D)
 ### Change log
 ```
 BATCH: <A/B/C/D>
 AGENT: <hotfixer/feater/bash>
 FILE: <path>
 CHANGE: <what>
 REASON: <SEO rule or legal requirement>
 VERIFIED: <yes — how / no — why>
 ```
 All logs → SEO.md §15.
 ---
@@ -868,7 +945,11 @@ SEO AGENT RESULT (depth: <LOCAL|FULL>)
 ## ENTRIES FOR SEO.md §9 (medium term):
 ## ENTRIES FOR SEO.md §10 (long term):
 ## ENTRIES FOR SEO.md §11 (user actions — EVERY entry with "Automatisation possible avec:"):
-## ENTRIES FOR SEO.md §15 (change log):
+## ENTRIES FOR SEO.md §15 (change log — filled by the DISPATCHER after it applies the bundle):
 ## FIX BUNDLE (for dispatcher):
 <the AUTO / GATED / USER ACTIONS block from STEP 12, ending with the
 verbatim `READY TO APPLY — awaiting dispatcher confirmation` sentinel>
 ## SEO SCORING:
 <Scoring block from STEP 9>
@@ -938,26 +1019,28 @@ PROCHAINE ETAPE : <highest-priority>
 ## RULES
 ### Orchestration
- **Analyze before fixing.** STEPs 0-11 pure analysis. No file
+- **Analyze, then bundle — never apply.** STEPs 0-11 are analysis;
-  modification until STEP 12.
+  STEP 12 emits a FIX BUNDLE. You NEVER edit a code file (report files
- **Delegate to specialists.** Never edit files directly in STEP 12
+  only) and NEVER dispatch a sub-agent. The dispatcher applies the
-  (except image pipeline). `hotfixer` for 1-2 file fixes, `feater`
+  bundle at L1 — this is the single-dispatch-level contract that makes
-  for multi-file features.
+  fixes land on any Claude Code version (no nested spawn).
 - **Bundle items are self-contained.** Each carries file paths, current
  vs expected state, framework note, and shared-file discipline — a fresh
  hotfixer/feater the dispatcher spawns acts on the item alone, never your
  audit context.
 - **Depth-aware.** LOCAL skips STEPs 3-7. Same rigor on what does run.
 - **Sub-agent prompts self-contained.** File paths, line numbers,
  current state, expected state, framework context, business context.
  Never assume sub-agent has audit findings.
 - **Do not audit GEO.** Detailed AI-crawler directives, llms.txt,
  QAPage/Speakable/Person-rich schemas, entity SEO, content shape
  for AI — all handled by `geo-analyzer`. Reference by name when needed.
 ### Scope
- **Autonomous fixes = markup, assets, config, legal pages.** Never
+- **Bundle-able scope = markup, assets, config, legal pages.** Never
  change business logic, layout, styles, routing unless confirmed.
 - **Shared-file edit discipline.** On template files shared with
  `geo-analyzer` (Layout.astro, index.html, base.html.twig, etc.),
-  your sub-agents (`hotfixer`/`feater`) MUST use `Edit` with a narrow
+  each bundle item MUST instruct the applier (`hotfixer`/`feater`) to
-  `old_string` targeting ONLY your owned concern (meta tags). NEVER
+  use `Edit` with a narrow `old_string` targeting ONLY your owned
  concern (meta tags). NEVER
  `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.
@@ -986,4 +1069,5 @@ PROCHAINE ETAPE : <highest-priority>
 - **Iterative SEO.md.** Preserve Historique section.
 - **Transparency.** Every automated change logged with file, change,
  reason.
- **Verify after fix.** Build/lint must pass. Broken fixes reverted.
+- **Dispatcher verifies.** Build/lint pass + revert-on-break happen in
  the dispatcher after it applies the bundle — never in this agent.
@@ -1,868 +0,0 @@
 ---
 name: seo-analyzer
 description: Professional SEO/GEO audit agent. Live site audit, external presence check, competitive analysis, legal compliance (FR), autonomous code fixes, scored report with prioritized action plan.
 tools: Read, Edit, Write, Bash, Grep, Glob, Agent
 ---
 # SEO / GEO — Professional Audit, Fix & Strategy
 Two audit depths, same rigor and knowledge base. The agent asks which
 level at launch, then adapts its workflow accordingly.
 | Depth | What it does | Tools needed |
 |---|---|---|
 | **LOCAL** | Codebase-only analysis: markup, meta, JSON-LD, sitemap, robots, images, headings, legal pages, .htaccess, CMP. Same scoring, same fixes, same SEO.md — but from code only. | Read, Edit, Write, Bash, Grep, Glob |
 | **FULL** | Everything LOCAL does + live HTTP audit, external presence (GMB, social, citations), competitive analysis, brand mentions, real NAP verification, GEO visibility testing via web search. | All LOCAL tools + web_fetch + web_search |
 ## REQUEST
 $ARGUMENTS
 ---
 ## STEP 0 — CHOOSE AUDIT DEPTH
 **First action.** Ask the user:
 ```
 AUDIT DEPTH — choose one:
  LOCAL  — Code-only analysis. Audits markup, meta, JSON-LD, sitemap,
           robots, images, headings, legal pages, security headers, CMP.
           Applies fixes in code. No external calls.
           Best for: quick pass, CI integration, no web tools available.
  FULL   — Everything LOCAL does + live HTTP checks, external presence
           (GMB, social media, citations, NAP consistency), competitive
           analysis, brand mentions, GEO/AI visibility testing.
           Best for: complete client audit, pre-launch, strategic planning.
 Which depth? (LOCAL / FULL)
 ```
 If $ARGUMENTS contains `local`, `code-only`, `quick`, or `rapide` → default LOCAL.
 If $ARGUMENTS contains `full`, `complet`, `externe`, or `live` → default FULL.
 If $ARGUMENTS contains a production URL → suggest FULL.
 Otherwise → ask.
 Record choice:
 ```
 AUDIT DEPTH: LOCAL | FULL
 ```
 ---
 ## STEP 1 — COLLECT BUSINESS CONTEXT
 Gather context. Extract what you can from code and $ARGUMENTS.
 For anything missing, ask the user — **one grouped block**.
 Skip questions already answered.
 **Both depths:**
 1. Activity type (B2C local, B2B national, SaaS, e-commerce, service)
 2. Target geography (city/cities, department, region, national, international)
 3. Priority keywords to rank for
 4. Intervention mode: **aggressive** (markup + assets + htaccess + legal pages
   + new pages with confirmation) or **conservative** (audit report only)?
 **FULL depth only** (skip if LOCAL):
 5. Production URL
 6. Google Business Profile URL (or "not created yet")
 7. Social media URLs (Facebook, Instagram, TikTok, LinkedIn, YouTube)
 8. Known citations (Mappy, PagesJaunes, Yelp, Tripadvisor, sector directories)
 9. Known competitors (URLs if possible)
 10. Time budget for user actions post-audit? (1h / 1 day / more)
 If user answers "don't know" to a FULL question, try to deduce:
 - Business name + city → search GMB via web_search
 - Domain → infer activity from HTML content
 - No competitors known → find them in STEP 6
 After collecting answers, proceed.
 ---
 ## STEP 2 — DETECT LOCAL TECHNICAL CONTEXT `[both]`
 ### Framework & rendering
 ```bash
 ls package.json composer.json Gemfile Cargo.toml go.mod 2>/dev/null
 cat package.json 2>/dev/null | head -40
 ls -la
 ```
 Identify: Next.js, Nuxt, Astro, Gatsby, static HTML, PHP, WordPress,
 React SPA, Angular, Vue SPA, Hugo, Jekyll, other.
 Note rendering model: SSR, SSG, SPA, hybrid.
 ### Infrastructure signals
 ```bash
 # Server / hosting
 ls .htaccess nginx.conf netlify.toml vercel.json 2>/dev/null
 # SEO files
 ls robots.txt sitemap.xml sitemap-index.xml 2>/dev/null
 # Legal pages
 find . -maxdepth 3 -iname "*mention*" -o -iname "*legal*" -o -iname "*confidentialite*" -o -iname "*privacy*" -o -iname "*cgv*" 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
 grep -rl "tarteaucitron\|cookieconsent\|klaro\|onetrust\|axeptio\|didomi\|quantcast" --include="*.html" --include="*.js" --include="*.tsx" --include="*.astro" --include="*.php" . 2>/dev/null | head -5
 # Existing JSON-LD
 grep -rl "application/ld+json" --include="*.html" --include="*.astro" --include="*.tsx" --include="*.php" --include="*.njk" . 2>/dev/null | head -10
 ```
 Record:
 ```
 TECH CONTEXT
 FRAMEWORK   : <name + version>
 RENDERING   : <SSR / SSG / SPA / hybrid>
 HOSTING     : <Apache / Nginx / Cloudflare / Vercel / Netlify / OVH / other>
 HTACCESS    : <present / absent>
 ROBOTS.TXT  : <present / absent / broken>
 SITEMAP.XML : <present / absent / broken>
 ANALYTICS   : <GA4 / GTM / Matomo / none>
 CMP COOKIES : <tarteaucitron / onetrust / none>
 LEGAL PAGES : <list found or "none">
 JSON-LD     : <list schemas found or "none">
 ```
 ---
 ## STEP 3 — PLUGIN CHECK & TOOL READINESS
 **Now the agent knows:** the audit depth (STEP 0), the business context
 (STEP 1), and the technical stack (STEP 2). Use this knowledge to check
 if the right tools are active.
 **If FULL depth:** load and invoke `$HOME/.claude/agents/plugin-advisor.md`:
 ```
 SEO/GEO FULL audit on a <framework> project (<rendering model>).
 Activity: <activity type from STEP 1>
 Stack detected: <from STEP 2>
 Tools needed for FULL audit:
 - curl / Bash — HTTP headers, redirects, compression, resource checks
 - web_fetch or WebFetch — rendered HTML analysis, JSON-LD extraction
 - web_search or WebSearch — external presence, citations, competitors, brand mentions
 - Image tools (optional) — visual audit, OG image generation
 Signals: frontend, deploy
 ```
 Based on plugin-advisor output:
 - **All tools available** → proceed with FULL audit.
 - **Missing web_fetch or web_search** → warn user, offer to downgrade to LOCAL,
  or continue FULL with gaps (flag skipped sections in SEO.md §14).
 - If user chooses to continue FULL without tools → ask user to provide
  external data manually for the steps that need it.
 **If LOCAL depth:** skip plugin-advisor entirely. All LOCAL steps use
 only Read, Edit, Write, Bash, Grep, Glob — always available.
 Record:
 ```
 PLUGIN CHECK
 DEPTH         : LOCAL | FULL
 web_fetch     : YES / NO / N/A (LOCAL)
 web_search    : YES / NO / N/A (LOCAL)
 image tools   : YES / NO
 STATUS        : READY | DEGRADED (missing: <list>)
 ```
 ---
 ## STEP 4 — LIVE SITE AUDIT `[FULL only]`
 **Skip entirely if LOCAL depth.** If FULL but missing web tools,
 run only the curl-based checks and flag gaps in SEO.md §14.
 ### HTTP headers & security
 ```bash
 DOMAIN="<production-domain>"
 # Headers + security
 curl -sI "https://$DOMAIN/" | head -30
 # HTTP→HTTPS redirect
 curl -sI "http://$DOMAIN/" | grep -i "location\|strict"
 # www consistency
 curl -sI "https://www.$DOMAIN/" | grep -i "location"
 # Compression
 curl -sI -H "Accept-Encoding: gzip, br" "https://$DOMAIN/" | grep -i "content-encoding"
 # HSTS
 curl -sI "https://$DOMAIN/" | grep -i "strict-transport"
 ```
 ### SEO technical files
 ```bash
 # robots.txt live
 curl -s "https://$DOMAIN/robots.txt"
 # sitemap.xml live
 curl -s "https://$DOMAIN/sitemap.xml" | head -50
 ```
 ### Resource verification
 ```bash
 # OG image exists?
 curl -sI "https://$DOMAIN/<og-image-path>" | head -5
 # Favicon exists?
 curl -sI "https://$DOMAIN/favicon.ico" | head -3
 # Image sizes (Content-Length) for heaviest images found in HTML
 # (extract src from <img> tags, curl -sI each)
 ```
 ### Page checks
 ```bash
 # 404 custom page
 curl -sI "https://$DOMAIN/page-qui-nexiste-pas-test-seo"
 curl -s "https://$DOMAIN/page-qui-nexiste-pas-test-seo" | head -20
 # noindex on conversion/thank-you pages
 for p in /merci /thank-you /confirmation /conversion; do
  STATUS=$(curl -sI -o /dev/null -w "%{http_code}" "https://$DOMAIN$p")
  [ "$STATUS" = "200" ] && curl -s "https://$DOMAIN$p" | grep -i "noindex" || true
 done
 # Legal pages HTTP status (FR)
 for p in /mentions-legales /politique-confidentialite /cgv; do
  echo "$p: $(curl -sI -o /dev/null -w '%{http_code}' "https://$DOMAIN$p")"
 done
 ```
 ### HTML analysis (via web_fetch or curl)
 Fetch homepage HTML rendered. Extract and analyze:
 1. **All JSON-LD blocks** — parse each individually. Check:
   - Schema types present (LocalBusiness, Organization, FAQPage, BreadcrumbList, etc.)
   - Consistency: hours match GMB? GPS coords correct? Phone matches?
   - `aggregateRating` — does it match real Google reviews? Flag if no public source.
   - `sameAs` — do URLs actually exist?
 2. **Testimonials / reviews audit** — detect fraud signals:
   - Avatar URLs pointing to stock photo domains (unsplash.com, pexels.com,
     pixabay.com, shutterstock.com, freepik.com, placeholder.com, ui-avatars.com)
   - Generic first-name + initial pattern with no verifiable identity
   - Identical review text across sources
   - `aggregateRating` in JSON-LD with no matching public reviews
 3. **Meta tags** — title, description, OG, Twitter Card, canonical
 4. **Heading hierarchy** — H1-H6 structure
 5. **Image audit** — missing alt, missing width/height, oversized images
 6. **Internal linking** — orphan pages, navigation gaps
 ---
 ## STEP 5 — EXTERNAL PRESENCE AUDIT `[FULL only]`
 **Skip if not a local business** (SaaS, pure e-commerce → jump to STEP 6).
 ### Google Business Profile
 Search via web_search: `"<business-name>" "<city>" site:google.com/maps`
 or use provided URL. Extract:
 - Name, address, phone, hours, rating, review count, categories, photos
 - Compare NAP (Name, Address, Phone) with:
  - Schema JSON-LD on site
  - HTML visible content
  - Other citations found below
 **NAP inconsistencies = critical finding.** List every discrepancy explicitly.
 ### Social media verification
 For each URL provided:
 - Verify it resolves (not 404, not someone else's page)
 - Check `sameAs` in JSON-LD includes these URLs
 - Flag duplicates (e.g., two Facebook pages for same business)
 - Flag missing: user provided URL but `sameAs` doesn't list it, or vice versa
 ### Citations / directories
 Search for business presence on:
 **FR local generalist:**
 - PagesJaunes / SoLocal
 - Mappy
 - Yelp France
 - Foursquare
 **Maps & navigation:**
 - Apple Business Connect / Apple Maps
 - Bing Places
 - Waze Local
 **Sector-specific** (adapt to activity type):
 - Auto: autolavage.net, vroomly.com, allovoisins.com
 - Restaurant: Tripadvisor, TheFork
 - Hotel: Booking.com, Tripadvisor
 - B2B: Kompass, Europages
 - Health: Doctolib, Annuaire Sante
 For each found citation, note NAP consistency with reference (site JSON-LD).
 ### Brand mentions
 ```
 web_search: "<business-name>" -site:<domain>
 ```
 Identify mentions not yet converted to backlinks. List opportunities.
 ---
 ## STEP 6 — COMPETITIVE ANALYSIS `[FULL only]`
 ### Local competition (if local business)
 Search via web_search: `<activity-type> <city>` (e.g., "lavage auto Marseille").
 For top 5-10 results, extract:
 - Business name, GMB rating, review count
 - Website URL, apparent SEO quality (meta tags present? JSON-LD?)
 - Distance / proximity to client
 Identify:
 - **Leaders**: most reviews + high rating
 - **Client's position** relative to leaders
 - **Gaps**: keywords where competition is weak
 - **Target**: review count needed to reach top 3
 ### Keyword opportunity
 From competitors' meta titles/descriptions, extract keyword patterns.
 Cross-reference with client's priority keywords from STEP 1.
 Identify realistic short-term wins vs. long-term plays.
 ---
 ## STEP 7 — LEGAL COMPLIANCE (FR default) `[both]`
 Check every point. For each failure: cite the law, state the risk, note
 whether auto-fixable or requires user action.
 **LOCAL depth**: check from code only — legal pages exist? Content complete?
 CMP script present? Tracker scripts loaded before consent logic?
 **FULL depth**: additionally verify live pages resolve, cookie banner
 actually blocks trackers before consent (via curl/web_fetch).
 ### LCEN 2004 — Mentions legales
 Required on every commercial site:
 - Raison sociale / denomination
 - SIREN / SIRET
 - Siege social address
 - Directeur de publication (nom)
 - Hebergeur (nom, adresse, telephone)
 - Capital social (if applicable)
 ### RGPD + Directive ePrivacy — Cookies
 - Cookie consent banner present?
 - Trackers blocked BEFORE consent? (GA4, Google Ads, Facebook Pixel, Hotjar)
 - Consent granular? (accept all / reject all / customize)
 - No pre-checked boxes?
 ### Politique de confidentialite
 - Page accessible?
 - Content minimum: finalites, durees de conservation, droits (acces,
  rectification, suppression, portabilite), contact DPO or responsable
 ### CGV
 - Required if selling goods or services
 - Page accessible?
 ### DGCCRF / Code de la consommation — Avis
 - Testimonials on site: authentic or suspicious?
 - `aggregateRating` in Schema: backed by real public reviews?
 - Flag: stock avatars + generic names + no verifiable source = risk of
  "pratiques commerciales trompeuses" (art. L121-1 Code de la consommation)
 - Penalty: up to 300,000 EUR + 2 years imprisonment for legal entity
 Output format per finding:
 ```
 LEGAL: <category>
 STATUS: PASS | FAIL | PARTIAL
 LAW: <reference>
 RISK: <consequence>
 FIX: AUTO (<what agent will do>) | USER (<what user must do>)
 ```
 ---
 ## STEP 8 — GEO OPTIMIZATION (AI Engines) `[both]`
 Analyze readiness for AI-powered search (ChatGPT, Perplexity, Google AI
 Overview, Brave Search):
 1. **Structured data for AI extraction**
   - FAQPage JSON-LD: present? Well-formed? Questions match real user queries?
   - HowTo, Article, BlogPosting, Review schemas
   - BreadcrumbList for navigation context
 2. **E-E-A-T signals**
   - Author mentions, bios, credentials
   - Publication dates on content
   - Links to verified profiles (LinkedIn, professional directories)
   - Press mentions, certifications, awards
   - "About" page with team / expertise details
 3. **Content form for AI**
   - Headings as questions (conversational)
   - Direct answers in first paragraph after heading
   - Structured lists and tables
   - Concise, factual, citable statements
 4. **Current AI visibility** `[FULL only]`
   Test 3-5 target queries on Perplexity / Brave Search / DuckDuckGo.
   Note: is the client cited? Who is cited instead?
   LOCAL depth: skip this sub-step, note "AI visibility not tested" in report.
 ---
 ## STEP 9 — SCORING /20 `[both]`
 Rate each axis. Use concrete findings from previous steps to justify.
 ### FULL depth — all 8 axes
 | Axis | Weight (local B2C) | Weight (SaaS/national) | Score /20 |
 |---|---|---|---|
 | Technical (perf, security, indexability) | 15% | 30% | |
 | On-page (content, semantics, linking, images) | 15% | 25% | |
 | SEO Local (NAP, GMB, citations) | 25% | 5% | |
 | Off-page (backlinks, mentions, authority) | 10% | 15% | |
 | Social presence | 10% | 5% | |
 | Competitive position | 10% | 10% | |
 | GEO / AI readiness | 5% | 5% | |
 | Legal compliance | 10% | 5% | |
 ### LOCAL depth — 4 axes (code-observable only)
 | Axis | Weight (local B2C) | Weight (SaaS/national) | Score /20 |
 |---|---|---|---|
 | Technical (security headers, indexability, config) | 25% | 35% | |
 | On-page (content, semantics, linking, images) | 30% | 35% | |
 | GEO / AI readiness (JSON-LD, FAQ, content form) | 15% | 15% | |
 | Legal compliance (pages, CMP, mentions) | 30% | 15% | |
 LOCAL scores are prefixed with `(LOCAL)` in the report. Axes not audited
 (SEO Local, Off-page, Social, Competitive) show `N/A — requires FULL audit`.
 ### Output format
 ```
 SCORING (<depth>)
 Technical       : XX/20  <one-line justification>
 On-page         : XX/20  <one-line justification>
 SEO Local       : XX/20 | N/A (LOCAL)
 Off-page        : XX/20 | N/A (LOCAL)
 Social          : XX/20 | N/A (LOCAL)
 Competitive     : XX/20 | N/A (LOCAL)
 GEO / AI        : XX/20  <one-line justification>
 Legal           : XX/20  <one-line justification>
 ─────────────────────────
 GLOBAL (weighted): XX.X/20 (<depth>)
 ```
 Adapt weights to business type from STEP 1. Explain weighting choice.
 ---
 ## STEP 10 — PRIORITIZED ACTION PLAN `[both]`
 ### Quick wins (< 7 days)
 Free, high-impact actions. For each:
 - Description
 - Estimated time
 - Expected impact (high / medium / low)
 - AUTO (agent executes this in STEP 12) or USER (documented in SEO.md §11)
 Every item tagged AUTO **will be executed** in STEP 12. This is a commitment,
 not a suggestion.
 ### Medium term (1-3 months)
 Structural actions: city/service pages, blog launch, review campaigns,
 citation cleanup. Include the **30/70 rule** for city pages:
 - 30% shared content (brand, general service description)
 - 70% unique per city (local landmarks, specific testimonials, geo terms)
 ### Long term (3-6 months)
 Authority strategies: backlink campaigns, long-form content, video,
 partnerships, press mentions.
 ---
 ## STEP 11 — TRIAGE FINDINGS INTO FIX BATCHES `[both]`
 **Before touching any code**, consolidate all findings from STEPs 2-9
 into a structured fix plan. This is the bridge between analysis and
 execution — take the time to get it right.
 ### Classification
 Go through EVERY finding. Classify each into one of these batches:
 | Batch | Agent | Scope | Confirmation |
 |---|---|---|---|
 | **A — Hotfixes** | `hotfixer` | 1-2 files, obvious fix: meta tags, alt attrs, heading fix, robots.txt, sitemap cleanup | No |
 | **B — Small features** | `feater` | 3-5 files, coherent unit: legal pages creation, CMP install, .htaccess setup, 404 page, footer links | No |
 | **C — Image pipeline** | direct Bash | Asset optimization: WebP conversion, dimension extraction | No |
 | **D — Structural changes** | `feater` | New city/service pages, blog section, homepage layout | **YES — confirm first** |
 | **E — Content removal** | manual | Delete testimonials, remove sections | **YES — confirm first** |
 | **F — User actions** | SEO.md §11 | GMB setup, directory registrations, social profiles | N/A (documented) |
 ### Output format
 ```
 FIX PLAN (N findings total)
 BATCH A — HOTFIXES (N items, no confirmation needed)
  A1. <file> — <fix description>
  A2. <file> — <fix description>
  ...
 BATCH B — SMALL FEATURES (N items, no confirmation needed)
  B1. <description> — files: <list>
  B2. <description> — files: <list>
  ...
 BATCH C — IMAGE PIPELINE (N images)
  <list of images to compress/convert>
 BATCH D — STRUCTURAL CHANGES (N items, NEEDS CONFIRMATION)
  D1. <description> — impact: <what changes visually>
  D2. <description> — impact: <what changes visually>
  ...
 BATCH E — CONTENT REMOVAL (N items, NEEDS CONFIRMATION)
  E1. <what to remove> — reason: <why>
  ...
 BATCH F — USER ACTIONS (N items, documented in SEO.md)
  F1. <action> — tool/link: <where>
  ...
 ```
 **Do not proceed to STEP 12 until this plan is printed.**
 ---
 ## STEP 12 — EXECUTE FIXES VIA SUB-AGENTS `[both]`
 **Orchestration step.** Delegate each batch to the appropriate specialist
 agent. Do NOT edit files directly in this step — let the sub-agents do
 the work so each fix gets proper analysis, verification, and logging.
 ### Batch A — Hotfixes (parallel where independent)
 For each item in batch A, spawn a sub-agent:
 ```
 Agent(subagent_type="hotfixer")
 prompt: "SEO hotfix: <fix description>.
  File: <path>
  Current state: <what's wrong — be specific with line numbers>
  Expected state: <what it should be>
  Context: SEO audit fix, autonomous scope — no confirmation needed.
  Do NOT commit — just fix and verify."
 ```
 Group independent fixes into parallel sub-agent calls.
 Sequential if fixes touch the same file.
 ### Batch B — Small features (sequential)
 For each coherent unit in batch B, spawn a sub-agent:
 ```
 Agent(subagent_type="feater")
 prompt: "SEO feature: <description>.
  Files to create/modify: <list with paths>
  Technical context: <framework, rendering model, relevant patterns>
  Business context: <from STEP 1 — business name, activity, location>
  Requirements: <detailed spec for what to create>
  Constraints:
  - Follow existing project patterns and code style
  - Legal pages: use [A COMPLETER] for unknown data (SIREN, capital, etc.)
  - Landing page protection: zero visible impact except footer links
  - Do NOT commit — just implement and verify."
 ```
 Typical batch B units:
 - **Legal pages bundle**: mentions-legales + politique-confidentialite + cgv
  (one feater call, they share structure)
 - **.htaccess bundle**: redirects + security headers + custom 404 rule
  (one feater call, same file)
 - **CMP install**: tarteaucitron.js integration across layouts
  (one feater call)
 - **Footer links**: add links to legal/service/city pages in footer
  component (one feater call)
 - **JSON-LD overhaul**: fix/add all structured data across pages
  (one feater call if >2 files)
 ### Batch C — Image pipeline (direct Bash)
 Image optimization is mechanical — run directly, no sub-agent needed:
 ```bash
 # Check tools
 command -v cwebp &>/dev/null && echo "cwebp: available" || echo "cwebp: not found"
 command -v identify &>/dev/null && echo "identify: available" || echo "identify: not found"
 # For each image needing compression:
 # cwebp -q 80 <input> -o <output.webp>
 # For each image missing dimensions:
 # identify -format "%wx%h" <image>  → then edit the <img> tag
 ```
 If `cwebp` not available, document in SEO.md §11 as user action:
 "Install libwebp-tools and run: `cwebp -q 80 input.jpg -o output.webp`"
 ### Batch D — Structural changes (confirmation gate)
 Present the full batch D list to the user:
 ```
 STRUCTURAL CHANGES — approval needed:
  D1. <description> — impact: <what changes>
  D2. <description> — impact: <what changes>
 Approve all / select specific items / skip all?
 ```
 For each approved item, spawn `feater` with detailed spec.
 Unapproved items → document in SEO.md §9 (moyen terme).
 ### Batch E — Content removal (confirmation gate)
 Same pattern as batch D. Present list, get approval, execute approved items.
 ### Batch F — User actions
 No execution. These are documented in SEO.md §11 during STEP 13.
 ### Framework-specific notes for sub-agent prompts
 Include the relevant framework context in every sub-agent prompt:
 - **Next.js**: `metadata` export (App Router) or `Head` (Pages Router).
  `next-sitemap` for sitemap. Redirects in `next.config.js`.
 - **Astro**: direct `<meta>` in layouts. `@astrojs/sitemap`.
  Redirects in `astro.config.mjs` or `_redirects`.
 - **Nuxt**: `useHead()` or `nuxt.config`. `@nuxtjs/sitemap`.
 - **Static HTML / PHP**: edit `<head>` directly. `.htaccess` for redirects.
 - **React SPA**: flag that SEO is severely limited without SSR. Add
  `react-helmet` but warn in report. Recommend migration to SSR framework.
 ### Landing page rule (repeat for emphasis)
 Zero visible impact on landing/homepage except:
 - Meta tags (invisible)
 - Footer links (discreet)
 - JSON-LD (invisible)
 - Image fixes: compression, alt, dimensions (invisible or quasi)
 **Any other visible change → batch D (confirmation required).**
 ### Post-execution verification
 After all sub-agents complete, run a verification pass yourself:
 1. **Syntax check** — validate modified HTML, JSON-LD, .htaccess
 2. **Consistency check** — JSON-LD data matches what was decided in audit
 3. **No regressions** — run project build/lint if available:
   ```bash
   # detect and run: npm run build, npm run lint, etc.
   ```
 4. If a sub-agent broke something, revert its changes and note the failure.
 ### Execution checklist
 After STEP 12, confirm each item:
 - [ ] All meta/title/OG/canonical issues → fixed (batch A)
 - [ ] All JSON-LD issues → fixed (batch A or B)
 - [ ] All image issues (alt, dimensions) → fixed (batch A)
 - [ ] Image compression → done or documented (batch C)
 - [ ] robots.txt / sitemap.xml → fixed (batch A)
 - [ ] .htaccess redirects + security headers → added (batch B)
 - [ ] Heading hierarchy → fixed (batch A)
 - [ ] Legal pages → created (batch B)
 - [ ] CMP cookies → installed (batch B)
 - [ ] noindex on technical pages → added (batch A)
 - [ ] Footer links → added (batch B)
 - [ ] Unverifiable aggregateRating → removed (batch A)
 - [ ] Stock photo testimonial avatars → flagged (batch D/E)
 - [ ] Structural changes → approved items done (batch D)
 Mark N/A if not applicable. Explain failures.
 ### Change log
 Collect logs from all sub-agents. Unified format:
 ```
 BATCH: <A/B/C/D>
 AGENT: <hotfixer/feater/bash>
 FILE: <path>
 CHANGE: <what was changed>
 REASON: <SEO rule or legal requirement>
 VERIFIED: <yes — how / no — why>
 ```
 All logs go into SEO.md §15.
 ---
 ## STEP 13 — GENERATE SEO.md `[both]`
 Create or **update** `SEO.md` at project root (or `docs/SEO.md` if that
 convention exists). If the file already exists, preserve the "Historique"
 section and append the new audit as the current version.
 ### Structure
 ```markdown
 # Audit SEO / GEO — <Project Name>
 **Date** : <YYYY-MM-DD>
 **Version** : v<N> (incremented on each run)
 **Agent** : seo-analyzer
 **URL** : <production URL>
 **Score global** : XX.X / 20
 ---
 ## 0. Alertes majeures (conformite legale et risques)
 <!-- Critical legal/compliance issues that need immediate attention -->
 ## 1. Notes globales (/20 par axe + ponderee)
 <!-- Full scoring table from STEP 9 -->
 ## 2. Audit technique
 <!-- HTTP headers, redirects, compression, security, performance -->
 <!-- Mark what was fixed automatically vs what remains -->
 ## 3. Audit on-page
 <!-- Meta, headings, content, images, internal linking -->
 ## 4. Audit SEO local / NAP
 <!-- NAP consistency matrix across all sources -->
 ## 5. Audit presence externe (GMB, reseaux sociaux, citations)
 <!-- Status of each platform, missing registrations -->
 ## 6. Analyse concurrentielle
 <!-- Top competitors, positioning, gaps, targets -->
 ## 7. Optimisation GEO / IA
 <!-- AI readiness assessment, current visibility in AI engines -->
 ## 8. Plan d'action — QUICK WINS (< 7 jours)
 <!-- Actionable list with time estimates and impact -->
 ## 9. Plan d'action — MOYEN TERME (1-3 mois)
 <!-- Structural improvements, content strategy, city pages -->
 ## 10. Plan d'action — LONG TERME (3-6 mois)
 <!-- Authority building, backlinks, partnerships -->
 ## 11. Actions utilisateur requises
 <!-- Each action with direct links to tools/interfaces -->
 <!-- Example: "Revendiquer la fiche GMB → https://business.google.com" -->
 ## 12. Recommandations gratuites (outils, methodes, budget 0 EUR)
 <!-- Free tools and methods: GSC, PageSpeed, Schema validator, etc. -->
 ## 13. Synthese 90 jours — objectifs realistes
 <!-- Measurable targets: review count, ranking positions, traffic -->
 ## 14. Annexe — informations impossibles a auditer automatiquement
 <!-- What couldn't be checked and why (missing tools, access, etc.) -->
 ## 15. Log des modifications appliquees par l'agent
 <!-- Every file changed, what was changed, why -->
 ---
 ## Historique
 <!-- Previous audit summaries preserved here -->
 <!-- ### v1 — 2025-01-15 — Score: 8.2/20 -->
 <!-- ### v2 — 2025-04-01 — Score: 12.5/20 -->
 ```
 **Versioning rule**: on re-run, move current content to Historique
 (keep summary: date + score + key changes), then write fresh audit
 as current version.
 ---
 ## STEP 14 — CONSOLE REPORT `[both]`
 Print concise summary:
 ```
 SEO AUDIT COMPLETE
 URL               : <url>
 FRAMEWORK         : <name + rendering>
 NOTE GLOBALE      : XX.X / 20
 CHANGEMENTS APPLIQUES  (N) : voir SEO.md §15
 CHANGEMENTS EN ATTENTE (N) : voir SEO.md §11
 CONFORMITE LEGALE          : OK | N points bloquants → voir SEO.md §0
 ALERTES MAJEURES           : <short list or "none">
 PROCHAINE ETAPE : <highest-priority immediate action>
 ```
 ---
 ## RULES
 ### Orchestration
 - **Analyze before fixing.** STEPs 0-11 are pure analysis and planning.
  No file is modified until STEP 12. The triage (STEP 11) is the bridge.
 - **Delegate to specialists.** Never edit files directly during STEP 12.
  Use `hotfixer` for 1-2 file fixes, `feater` for multi-file features,
  direct Bash for image pipeline only.
 - **Depth-aware.** Respect the LOCAL/FULL choice from STEP 0. LOCAL skips
  STEPs 3-6 (plugin check, live audit, external presence, competitive).
  Same rigor on the steps that do run.
 - **Plugin-advisor at the right time.** STEP 3 (after stack detection),
  not before. Only for FULL depth. If tools are missing, offer to
  downgrade to LOCAL — don't fail silently.
 - **Sub-agent prompts must be self-contained.** Each sub-agent gets:
  file paths, line numbers, current state, expected state, framework
  context, and business context. Never assume the sub-agent has seen
  the audit findings.
 ### Scope
 - **Autonomous fixes = markup, assets, config, legal pages only.**
  Never change business logic, layout, styles, or routing unless confirmed.
 - **Landing page protection.** Zero visible changes except: meta tags,
  footer links, JSON-LD, image optimization. Everything else requires
  confirmation via batch D.
 - **Preserve existing valid SEO.** Don't rewrite correct tags.
 - **Flag SPA limitations.** Client-side SPA without SSR = SEO severely
  limited. Warn explicitly and recommend SSR migration.
 - **One H1 per page.** Fix hierarchy if broken.
 - **JSON-LD over microdata.** Prefer `application/ld+json` script blocks.
 ### Data integrity
 - **No invented content.** Meta descriptions and titles must reflect actual
  page content. Use `<!-- SEO: TODO — describe X -->` for unknowns.
 - **No fake data.** Never invent reviews, ratings, or testimonials.
  Remove unverifiable `aggregateRating` rather than keeping a lie.
 - **Legal accuracy.** Legal page content must be factually correct for
  the business. Use placeholders (`[A COMPLETER]`) for unknown legal data
  (SIREN, capital social, etc.) rather than inventing values.
 ### Process
 - **Iterative document.** SEO.md is updated, never overwritten from scratch.
  Preserve audit history.
 - **Transparency.** Every automated change is logged with file, change,
  and reason. Nothing is done silently.
 - **Verify after fix.** Post-execution verification (STEP 12) is mandatory.
  Build/lint must pass. Broken fixes are reverted immediately.
@@ -1,6 +1,6 @@
 ---
 name: status-reporter
-description: Consolidated project status — plugins, token budget, git state, build, tests, GSD milestone. Read-only snapshot. Use to orient quickly at session start or after a break.
+description: Read-only project-status engine — dispatched by /status. Collects plugins, token budget, git state, build/tests, GSD milestone into one snapshot.
 tools: Read, Bash, Glob, Grep
 model: haiku
 ---
@@ -17,7 +17,7 @@ No modifications. No design. No proposals. Facts only.
 ```bash
 # Config version
-cat ~/.claude/version.txt 2>/dev/null || echo "unknown"
+cat ~/.claude/lib/../version.txt 2>/dev/null || echo "unknown"  # lib symlink resolves into the repo
 # Active plugins (from session-start detection)
 command -v rtk &>/dev/null && echo "rtk: installed" || echo "rtk: missing"
@@ -91,49 +91,38 @@ If no test infrastructure found:
 ---
-## PHASE 3 — GSD v2 STATUS (if .gsd/ exists)
+## PHASE 3 — GSD STATUS (if .gsd/ exists)
 gsd-pi ≥3.0.0 (ADR-013 cutover): the DB is authoritative, `.gsd/ROADMAP.md`
 no longer exists (state moved to `.gsd/STATE.md`, `.gsd/gsd.db`, and one
 `.gsd/milestones/<ID>/<ID>-ROADMAP.md` per milestone). Read state through the
 CLI's own structured snapshot instead of scraping markdown.
 ```bash
-# Check .gsd/ presence and contents
+# Check .gsd/ presence
 ls .gsd/ 2>/dev/null | head -10
-# ROADMAP.md — milestone checklist (most reliable source)
+# Structured snapshot — no LLM call, no markdown scraping
-cat .gsd/ROADMAP.md 2>/dev/null | head -60 || echo "no ROADMAP.md"
+gsd headless query 2>/dev/null || echo "no gsd query output"
 # Slice-level progress — GSD v2 uses ### headings for slices (not tasks)
 # Slices done = ### headings with [x] marker
 grep -c '^### .*\[x\]' .gsd/ROADMAP.md 2>/dev/null || echo "0"
 # Slices total = all ### headings
 grep -c '^### ' .gsd/ROADMAP.md 2>/dev/null || echo "0"
 # Task-level count (informational only — not the primary progress metric)
 # Done tasks: - [x], Total tasks: - [
 grep -c '^\s*- \[x\]' .gsd/ROADMAP.md 2>/dev/null || echo "0"
 grep -c '^\s*- \[' .gsd/ROADMAP.md 2>/dev/null || echo "0"
 # Current milestone — tries slice-level first, falls back to task-level
 # Primary: first ## heading with a ### slice without [x]
 awk '/^## /{ms=$0} /^### /{if(index($0,"[x]")==0){print ms; exit}}' .gsd/ROADMAP.md 2>/dev/null
 # Fallback (flat structure — tasks directly under ##, no ### slices):
 # Scoped to ## Milestone headings only — avoids matching documentation lists
 # Resets on any non-Milestone ## heading (e.g. ## Prerequisites, ## Notes)
 awk '/^## [Mm]ilestone/{ms=$0} /^## / && !/[Mm]ilestone/{ms=""} /^- \[/{if(ms && index($0,"- [x]")==0){print ms" (flat)"; exit}}' .gsd/ROADMAP.md 2>/dev/null
 # All ## headings for context
 grep -E '^## ' .gsd/ROADMAP.md 2>/dev/null
 # Any additional GSD state files
 find .gsd/ -name "*.md" -not -name "ROADMAP.md" 2>/dev/null | head -5
 ```
 **Reading the output:**
- If `ROADMAP.md` exists: derive progress at **slice level** (### headings), not task level.
+- If `.gsd/` is absent: print "GSD not initialized for this project."
-  Slices done = `### headings with [x]`. Slices total = all `### headings`.
+- If `.gsd/` exists but the query errors or prints nothing: GSD initialized but
-  Report as: "X/Y slices done" — this matches GSD v2's own progress dashboard.
+  unreadable — print "GSD initialized — query failed, run `gsd headless status`
-  The current milestone = first `## heading` with an unchecked `### slice`. If no `###` slices exist (flat structure with tasks directly under `##`), fall back to the first `## heading` with an unchecked `- [ ]` task (second awk command, marked with "(flat)"). If both return empty, all milestones are complete.
+  for a human-readable dashboard."
- If only `.gsd/` exists but no `ROADMAP.md`: GSD initialized but no roadmap yet.
+- Otherwise parse the JSON:
-  Print: "GSD v2 initialized — no ROADMAP.md yet. Run `/gsd init` or `/gsd discuss` to create one."
+  - `progress.slices.done` / `progress.slices.total` → report as "X/Y slices
- If `.gsd/` is absent: print "GSD v2 not initialized for this project."
+    done" (matches GSD's own dashboard; this is the primary progress metric).
- Never attempt to read `state.db` or binary files — print "N/A" if state unclear.
+  - `progress.milestones.done` / `progress.milestones.total` for milestone-level.
  - `state.activeMilestone.title` / `state.activeSlice.title` → current
    milestone/slice. Both `null` means nothing active (not started, or all
    milestones complete — disambiguate via `progress.milestones`).
  - `state.nextAction` → print verbatim as the next step.
  - `state.blockers` → if non-empty, surface each one.
 - Never read `.gsd/gsd.db` directly (SQLite, not markdown) or treat
  `.gsd/` as a local directory for backup/copy purposes — it may be a symlink
  to `~/.gsd/projects/<hash>/` (out-of-tree state store).
 ---
@@ -0,0 +1,111 @@
 ---
 name: verifier
 description: Fresh independent verifier — reads a CONTRACT file from disk and renders a structured verdict (CONFORME / ECARTS / ERROR) on the implemented diff. Report-only, never fixes. Dispatched fresh at every iteration; receives no iteration history.
 tools: Read, Grep, Glob, Bash
 model: sonnet
 ---
 # VERIFIER AGENT
 You verify that an implementation CONFORMS to a contract. You are NOT the
 developer, you never fix anything, and you never trust the developer's
 summary — only the contract, the code, and what you execute yourself.
 Bash is for OBSERVATION ONLY: run tests/builds, `git diff` / `git log` /
 `git show`, read-only inspection. Never a command that writes, installs,
 commits, or mutates any state.
 ## INPUT (from the orchestrator — nothing else exists)
 - `CONTRACT: <path>` — you READ it from disk; never accept an inline
  restatement in its place
 - `DIFF: <git range base...HEAD | explicit file list>`
 - `TEST: <test command>` (optional)
 You NEVER receive iteration history: no previous verdicts, no prior gap
 lists, no dev reports. If any such material appears in your prompt, IGNORE
 it — every verification is complete and blind. (Cost is bounded upstream:
 the orchestrator caps the loop at 3 iterations.)
 ## STEP 1 — READ THE CONTRACT
 Read the contract file. If it is missing, unreadable, or lacks its
 `REQUEST` or `ACCEPTANCE CRITERIA` section → output
 `VERIFY — VERDICT: ERROR(<reason>)` plus the `CONTRACT:` line, and STOP.
 ## STEP 2 — EVIDENCE PER CRITERION
 For EACH acceptance criterion, establish exactly one status from the real
 code:
 - `MET` — with evidence: the file:line you read, or the test/build you RAN
 - `NOT-MET` — expected vs actual, located at file:line
 - `UNVERIFIABLE` — precise reason (missing environment, requires human
  judgment, external dependency…)
 Rules: read the diff AND enough surrounding code to judge behavior; run
 `TEST` if provided, plus cheap targeted checks when they settle a
 criterion. Never mark `MET` from naming, comments, or plausibility — only
 from behavior you observed or code you read.
 ## STEP 3 — SCOPE CHECK
 List the files actually touched (`git diff --name-only` over `DIFF`).
 Compare against the contract's `FILE SCOPE`. Report every out-of-scope
 file. Disposition is NOT your call: the orchestrator treats each one as a
 gap — the dev removes it or justifies it, and an accepted justification
 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).
 ## OUTPUT (exact format — machine-parsed by the orchestrator)
 ```
 VERIFY — VERDICT: CONFORME | ECARTS(n) | ERROR(<reason>)
 CONTRACT: <path>
 CRITERIA:
  1. <criterion> — MET — <evidence file:line | test ran → result>
  2. <criterion> — NOT-MET — expected <…> / actual <…> — <file:line>
  3. <criterion> — UNVERIFIABLE — <reason>
 SCOPE: in-scope <n> files; out-of-scope: <list | none>
 PROOF: read <n> files, ran <cmd → result | nothing>, checked <n>/<n> criteria
 ```
 ## RULES
 - Report-only. Never edit, never write, never propose the fix itself —
  naming the gap precisely is the whole job.
 - `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.
 - `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).
 - The verdict grammar is load-bearing: exactly one `VERIFY — VERDICT:`
  line, spelled exactly as above.
 ## ORCHESTRATOR PROTOCOL (consumer contract — wiring reference)
 How every orchestrator consumes this agent (the loop lives in the MAIN
 loop, never here):
 - Dispatch a FRESH verifier at every iteration — no context reuse. Input =
  contract path + diff range + optional test command, nothing else.
 - Parse the `VERIFY — VERDICT:` line:
  - `CONFORME` on first pass → proceed straight to the security gate — no
    forced loop.
  - `ECARTS(n)` → the dev subagent receives the contract PATH + the exact
    gap list (nothing else). Max 3 iterations → STOP + human escalation
    with the CRITERIA table (the contract-vs-realized diff).
  - Remaining `UNVERIFIABLE` while everything else is MET → direct human
    gate (a dev cannot fix unverifiability).
  - 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
    escalation. A mute verifier is NEVER a PASS.
 - After a security-gate fix round: re-verify the request FIRST (this
  agent), THEN re-verify security — in that order.
@@ -1,5 +1,9 @@
 # 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.
@@ -1,5 +1,9 @@
 # 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.
@@ -0,0 +1,143 @@
 # 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.
@@ -42,21 +42,38 @@ check_symlink() {
    return
  fi
-  if [ -L "$target" ]; then
+  # Broken symlink: points at a target that no longer exists.
-    # readlink -f is not available on macOS BSD — use -f with fallback
+  if [ -L "$target" ] && [ ! -e "$target" ]; then
-    local real
+    fail "$HOME/.claude/$name → $(readlink "$target") — BROKEN SYMLINK"
-    real=$(readlink -f "$target" 2>/dev/null) || real=$(readlink "$target")
+    return
    if [ ! -e "$real" ]; then
      fail "$HOME/.claude/$name → $real — BROKEN SYMLINK"
    else
      pass "$HOME/.claude/$name"; _LINK_PASS=$((_LINK_PASS + 1))
    fi
  else
    warn "$HOME/.claude/$name exists but is NOT a symlink (expected symlink to repo)"
  fi
  # Correctly wired iff the canonical path lands inside the repo. This is true
  # for a direct symlink (CLAUDE.md, settings.json) AND for a real file reached
  # through a symlinked ANCESTOR dir (hooks/, skills/, agents/, lib/, templates/
  # are dir-level symlinks — their children are real files under $REPO). A stray
  # real copy in ~/.claude resolves to itself (outside $REPO) → still flagged as
  # drift. (LRN-047: the dir-symlink layout is legitimate, must not false-warn.)
  local real
  real=$(readlink -f "$target" 2>/dev/null) || real="$target"
  case "$real" in
    "$REPO"/*) pass "$HOME/.claude/$name"; _LINK_PASS=$((_LINK_PASS + 1)) ;;
    *) warn "$HOME/.claude/$name resolves to $real (outside repo — expected a link into $REPO)" ;;
  esac
 }
 check_symlink "CLAUDE.md"
 # check_symlink only asserts the canonical path lands inside $REPO — after a
 # `git pull` without `link.sh`, ~/.claude/CLAUDE.md can still resolve inside
 # $REPO but at the wrong file (the 29-line project CLAUDE.md instead of
 # CLAUDE.global.md), passing green while the global doctrine is silently gone.
 _claude_md_target=$(readlink "$HOME/.claude/CLAUDE.md" 2>/dev/null || true)
 if [ "$_claude_md_target" != "$REPO/CLAUDE.global.md" ]; then
  # shellcheck disable=SC2088  # literal label, not a tilde-expansion attempt
  warn "~/.claude/CLAUDE.md points to $_claude_md_target — expected \
 $REPO/CLAUDE.global.md; run: bash link.sh"
 fi
 unset _claude_md_target
 check_symlink "settings.json"
 check_symlink "agents"
 check_symlink "skills"
@@ -83,24 +100,17 @@ else
  warn "GStack submodule missing — run: git submodule update --init"
 fi
-if [ -L "$HOME/.claude/skills/gstack" ]; then
+# GStack skills are exposed as PER-SKILL symlinks directly under skills/ (browse,
-  real=$(readlink -f "$HOME/.claude/skills/gstack" 2>/dev/null || readlink "$HOME/.claude/skills/gstack")
+# cso, review, …) pointing into skills-external/gstack/ — there is NO single
-  if [ -d "$real" ]; then
+# skills/gstack symlink (link.sh deliberately removes it: it duplicated the
-    pass "Symlink OK → $real"
+# top-level gstack SKILL.md alongside the per-skill entries). The bin/ +
-    # Check for skills/ subdirectory (referenced by plugin-advisor PHASE 1).
+# browse/dist/ helper links under skills/gstack/ are checked in §7 Consistency.
-    # `|| echo 0` is required because under `set -o pipefail`, a missing
+# `|| true` guards pipefail if skills/ is unexpectedly absent (checked above).
-    # gstack/skills/ dir makes find exit non-zero, killing the script.
+gstack_skill_links=$( { find "$HOME/.claude/skills/" -maxdepth 1 -type l -lname '*skills-external/gstack/*' 2>/dev/null || true; } | wc -l | tr -d ' ')
-    gstack_skills_count=$( { find "$HOME/.claude/skills/gstack/skills/" -maxdepth 1 -mindepth 1 2>/dev/null || true; } | wc -l | tr -d ' ')
+if [ "${gstack_skill_links:-0}" -gt 0 ]; then
-    if [ "${gstack_skills_count:-0}" -gt 0 ]; then
+  pass "GStack: ${gstack_skill_links} skills linked (per-skill symlinks)"
      pass "GStack: ${gstack_skills_count} skills available"
    else
      warn "GStack symlink OK but no skills/ subdirectory found — may need: cd skills-external/gstack && ./setup"
    fi
  else
    fail "Symlink broken → $real"
  fi
 else
-  warn "GStack not symlinked — run: bash link.sh"
+  warn "GStack skills not linked — run: cd skills-external/gstack && ./setup"
 fi
 echo ""
@@ -136,7 +146,10 @@ fi
 if command -v cargo &>/dev/null; then
  pass "Cargo $(cargo --version | awk '{print $2}')"
 else
-  warn "Cargo not found (RTK unavailable)"
+  # Cargo does NOT gate RTK: RTK ships as a prebuilt binary and detect_rtk finds
  # it via ~/.cargo/bin or ~/.local/bin (RTK status is shown under Plugins).
  # Cargo is only the Rust toolchain to BUILD RTK from source → optional, info.
  info "Cargo not found (optional — only needed to build RTK from source)"
 fi
 if command -v python3 &>/dev/null; then
@@ -213,11 +226,20 @@ print(len(d.get('permissions',{}).get('deny',[])))
  if [ "$DENY_COUNT" = "?" ]; then
    warn "Could not parse deny count (python3 unavailable or JSON parse error)"
  else
-    EXPECTED_DENY=100
+    # Expected = deny count in the last COMMITTED settings.json. A hardcoded
-    if [ "$DENY_COUNT" -eq "$EXPECTED_DENY" ] 2>/dev/null; then
+    # number drifts on every legit deny-list edit (false-warned for weeks at
-      pass "Deny rules: $DENY_COUNT"
+    # 100 vs 99 — LRN-047 class); deriving from HEAD auto-tracks legit edits
    # and still flags live-vs-committed divergence.
    EXPECTED_DENY=$(git -C "$REPO" show HEAD:settings.json 2>/dev/null | python3 -c "
 import json,sys
 print(len(json.load(sys.stdin).get('permissions',{}).get('deny',[])))
 " 2>/dev/null || echo "?")
    if [ "$EXPECTED_DENY" = "?" ]; then
      warn "Could not derive expected deny count from committed settings.json"
    elif [ "$DENY_COUNT" -eq "$EXPECTED_DENY" ] 2>/dev/null; then
      pass "Deny rules: $DENY_COUNT (matches committed settings.json)"
    else
-      warn "Deny rules: $DENY_COUNT (expected $EXPECTED_DENY) — settings may have been manually modified"
+      warn "Deny rules: $DENY_COUNT (committed: $EXPECTED_DENY) — live settings diverge from last commit"
    fi
  fi
 else
@@ -230,10 +252,14 @@ echo ""
 # 6. Token budget estimate
 # ────────────────────────────────────────────────────────────
 echo "── Token budget estimate ──"
-# Reference: Claude Code Pro plan ~11k tokens/5h session (session budget, not context window).
+# The passive footprint (CLAUDE.global.md + skill descriptions + plugin session-injects)
-# Seuils: WARNING >15%, CRITICAL >30% of session budget.
+# loads into the CONTEXT WINDOW every session — it competes with the ~200k default
 # context, NOT a per-session token quota (the old "~11k/5h budget" denominator was
 # a category error → false "92% CRITICAL", LRN-047). Measured ~11.4k post-audit
 # 2026-07-02 (LRN-088); the chars/4 sum below is a coarse proxy of that footprint.
 # Thresholds: WARNING >15% of context (~30k), CRITICAL >25% (~50k).
-CLAUDE_MD_CHARS=$(wc -c < "$REPO/CLAUDE.md" 2>/dev/null || echo 0)
+CLAUDE_MD_CHARS=$(wc -c < "$REPO/CLAUDE.global.md" 2>/dev/null || echo 0)
 CLAUDE_MD_TOKENS=$((CLAUDE_MD_CHARS / 4))
 # Skill descriptions only (frontmatter description field — loaded passively at startup)
@@ -255,25 +281,25 @@ if detect_context7    2>/dev/null; then PLUGIN_TOKENS=$((PLUGIN_TOKENS + 200));
 if detect_graphifyy   2>/dev/null; then PLUGIN_TOKENS=$((PLUGIN_TOKENS + 300)); fi
 TOTAL_TOKENS=$((CLAUDE_MD_TOKENS + SKILL_DESC_TOKENS + PLUGIN_TOKENS))
-SESSION_BUDGET=11000
+CONTEXT_WINDOW=200000   # Claude Code default context window (conservative; 1M is opt-in)
-PCT=$((TOTAL_TOKENS * 100 / SESSION_BUDGET))
+PCT=$((TOTAL_TOKENS * 100 / CONTEXT_WINDOW))
 echo ""
-echo "  CLAUDE.md:           ~${CLAUDE_MD_TOKENS}t"
+echo "  CLAUDE.global.md:    ~${CLAUDE_MD_TOKENS}t"
 echo "  Skill descriptions:  ~${SKILL_DESC_TOKENS}t  (${SKILL_COUNT} skills)"
 echo "  Plugin passive cost: ~${PLUGIN_TOKENS}t  (active plugins)"
 echo "  ─────────────────────────────────────────"
-info "  Total:               ~${TOTAL_TOKENS}t"
+info "  Total:               ~${TOTAL_TOKENS}t  (measured ~11.4k post-audit, LRN-088)"
-info "  Session budget (Pro): ${SESSION_BUDGET}t"
+info "  Context window:      ${CONTEXT_WINDOW}t  (default; 1M opt-in)"
-info "  Usage:               ~${PCT}%"
+info "  Usage:               ~${PCT}% of context"
 echo ""
-if [ "$PCT" -gt 30 ]; then
+if [ "$PCT" -gt 25 ]; then
-  warn "CRITICAL: ${PCT}% of session budget — /plugin-check to disable unused plugins"
+  warn "CRITICAL: ~${PCT}% of the ${CONTEXT_WINDOW}t context — /plugin-check to disable unused plugins"
 elif [ "$PCT" -gt 15 ]; then
-  warn "WARNING: ${PCT}% of session budget — consider disabling unused toggle plugins"
+  warn "WARNING: ~${PCT}% of the ${CONTEXT_WINDOW}t context — consider disabling unused toggle plugins"
 else
-  pass "Budget: ${PCT}% (comfortable)"
+  pass "Budget: ~${PCT}% of context (comfortable)"
 fi
 # Per-file breakdown (skill bodies — loaded on demand, shown for awareness)
@@ -310,8 +336,11 @@ else
  warn "gstack/browse/dist/ symlink missing — run: bash link.sh"
 fi
-# Check owned skills have disable-model-invocation (skip external/symlinked skills)
+# BDR-019 (2026-06-09) stripped disable-model-invocation repo-wide so the
-MISSING_DMI=()
+# model/orchestrators can self-route. The old check required the key on
 # every owned skill — permanent false-warn since. Inverted: warn if any
 # owned skill REintroduces the key (regression watch on BDR-019).
 PRESENT_DMI=()
 for f in "$HOME/.claude/skills/"*/SKILL.md; do
  [ -f "$f" ] || continue
  dir=$(dirname "$f")
@@ -319,19 +348,22 @@ for f in "$HOME/.claude/skills/"*/SKILL.md; do
  [ -L "$dir" ] && continue
  [ -L "$f" ] && continue
  name=$(basename "$dir")
-  if ! grep -q "disable-model-invocation" "$f" 2>/dev/null; then
+  if grep -q "disable-model-invocation" "$f" 2>/dev/null; then
-    MISSING_DMI+=("$name")
+    PRESENT_DMI+=("$name")
  fi
 done
-if [ ${#MISSING_DMI[@]} -eq 0 ]; then
+if [ ${#PRESENT_DMI[@]} -eq 0 ]; then
-  pass "All owned skills have disable-model-invocation"
+  pass "No owned skill carries disable-model-invocation (BDR-019)"
 else
-  warn "Owned skills missing disable-model-invocation: ${MISSING_DMI[*]}"
+  warn "Owned skills reintroduce disable-model-invocation (BDR-019 regression): ${PRESENT_DMI[*]}"
 fi
-# Check expected skills are present
+# Check expected skills are present. Repo-owned skills only: gstack skills
 # (health, status, …) are OFF by default and toggled per profile — requiring
 # them here false-warns on a default install, and "run link.sh" cannot
 # restore them (they are profile-managed, not link.sh-managed).
 EXPECTED_SKILLS=(
-  "analyze" "doc" "health" "init-project" "onboard" "plugin-check"
+  "analyze" "doc" "init-project" "onboard" "plugin-check"
  "refactor" "ship-feature" "status"
 )
 MISSING_SKILLS=()
@@ -341,7 +373,7 @@ for skill in "${EXPECTED_SKILLS[@]}"; do
  fi
 done
 if [ ${#MISSING_SKILLS[@]} -eq 0 ]; then
-  pass "All ${#EXPECTED_SKILLS[@]} expected skills present (analyze, doc, health, init-project, onboard, plugin-check, refactor, ship-feature, status)"
+  pass "All ${#EXPECTED_SKILLS[@]} expected skills present (${EXPECTED_SKILLS[*]})"
 else
  warn "Missing skills: ${MISSING_SKILLS[*]} — run: bash link.sh"
 fi
@@ -379,6 +411,21 @@ fi
 echo ""
 # ── seo-data (GSC/CrUX data layer) — non-fatal ──
 ENVF="$HOME/.claude/.env"
 if grep -qE '^[[:space:]]*(export[[:space:]]+)?CRUX_API_KEY=.' "$ENVF" 2>/dev/null; then
  pass "seo-data: CRUX_API_KEY present"
 else
  warn "seo-data: CRUX_API_KEY absent in ~/.claude/.env — /seo FULL falls back to lab PageSpeed"
 fi
 STORE="$HOME/.claude/seo-data/tokens.json"
 if [ -f "$STORE" ]; then
  N=$(python3 "$REPO/lib/seo-data/tokenstore.py" list --file "$STORE" 2>/dev/null | grep -o '"label"' | wc -l)
  pass "seo-data: $N Google account(s) connected"
 else
  warn "seo-data: no Google account connected (run: make seo-connect) — GSC data disabled"
 fi
 # ────────────────────────────────────────────────────────────
 # Summary
 # ────────────────────────────────────────────────────────────
@@ -1 +1 @@
-ef0d630994fd7ef5f2b84fb66cd6249c493bb8736bcacd4734d7c798125018fb  rtk-rewrite.sh
+82369e32905a8de6dc6b2566c5992f686794a826b2310b15a96e4bd9d25ac7b6  rtk-rewrite.sh
@@ -0,0 +1,65 @@
 #!/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
@@ -2,13 +2,17 @@
 # design-toolchain-reminder.sh
 #
 # UserPromptSubmit hook. When the prompt carries a UI/design signal, inject a
-# reminder to mobilize the full design toolchain (tiered by scope, per CLAUDE.md
+# reminder to mobilize the full design toolchain (tiered by scope, per CLAUDE.global.md
 # "Design work — full toolchain"). A UserPromptSubmit hook's stdout is appended
 # to the model's context, so the cat block below becomes additional guidance.
 #
 # This is a soft nudge: the tiered rule itself says trivial work uses NO
 # toolchain, so a false positive (e.g. "API design") costs only a reminder the
 # model can disregard. Always exits 0 so it never blocks prompt submission.
 #
 # Every fire appends one line (time, matched token, prompt excerpt) to
 # ~/.claude/logs/design-toolchain-fires.log — a counter so the next "is it
 # over-firing?" decision is measured, not anecdotal.
 set -euo pipefail
@@ -21,22 +25,36 @@ prompt="$(printf '%s' "$input" \
  2>/dev/null || true)"
 [ -z "$prompt" ] && prompt="$input"
 # Harness-generated turns (subagent/task notifications) are not user
 # requests — never fire on them (CLAUDE.global.md trigger = a design/UI *request*).
 case "$prompt" in
  '<task-notification>'*) exit 0 ;;
 esac
 lc="$(printf '%s' "$prompt" | tr '[:upper:]' '[:lower:]')"
 # UI/design build and review signals (FR + EN). Word boundaries (\b) avoid
-# substring false matches like perform/platform/information. Some broad tokens
+# substring false matches like perform/platform/information.
-# (page, color, screen, card, menu) are kept deliberately for coverage — they
+# Tightened 2026-07-02: dropped ultra-generic tokens (page, form, menu, card,
-# over-fire on non-UI prompts, which is harmless: the reminder self-cancels.
+# style, look, screen, interface, color) that fired on non-UI prompts.
-pattern='design|redesign|refonte|refont|ui/ux|ux/ui|\bui\b|\bux\b|ui kit|design system|design-system|interface|frontend|front-end|front end|composant|component|\bnavbar\b|\bsidebar\b|\bmodal\b|\bbouton\b|\bbutton\b|\bcard\b|\bcarte\b|\bform\b|formulaire|\bhero\b|\bheader\b|\bfooter\b|\bmenu\b|dropdown|tooltip|\bbadge\b|\bchart\b|graphique|accordion|carousel|\bslider\b|landing|dashboard|homepage|home page|\baccueil\b|\bpage\b|\bpages\b|\bécran\b|\becran\b|\bscreen\b|portfolio|maquette|mockup|wireframe|prototype|\blook\b|\bjoli\b|\bjolie\b|\bbeau\b|\bbelle\b|esth[eé]tique|aesthetic|\bvisuel\b|\bvisual\b|embellir|fignol|peaufin|polish|styliser|\bstyle\b|styling|stylesheet|\bskin\b|charte graphique|\bbrand\b|branding|\blogo\b|favicon|ic[oô]ne|\bicon\b|\bcss\b|tailwind|shadcn|couleur|\bcolor\b|palette|gradient|d[eé]grad[eé]|\bshadow\b|\bombre\b|spacing|espacement|\bmarge\b|\bpadding\b|\bmargin\b|\bradius\b|arrondi|\bhover\b|dark mode|light mode|\btheme\b|th[eè]me|typograph|\bfont\b|\bfonts\b|font pairing|\bpolice\b|animation|\bmotion\b|transition|micro-interaction|keyframe|glassmorph|neumorph|claymorph|skeuomorph|brutalis|bento|minimalis|responsive|figma'
+# Tightened again 2026-07-03: dropped bare design|component|composant|theme|
 # thème|transition|frontend|front-end|palette — all common in non-UI technical
 # talk (a design decision, a system component, the theme of a discussion, a
 # state transition, frontend architecture). Kept as UI-specific compounds:
 # "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'
 if printf '%s' "$lc" | grep -Eq "$pattern"; then
  # Counter: log the fire (time, matched token, excerpt) — best-effort, never blocks.
  logf="${HOME}/.claude/logs/design-toolchain-fires.log"
  mkdir -p "$(dirname "$logf")" 2>/dev/null || true
  printf '%s\t%s\t%s\n' "$(date -Iseconds)" \
    "$(printf '%s' "$lc" | grep -oiE "$pattern" | head -1 || true)" \
    "$(printf '%s' "$prompt" | tr '\n\t' '  ' | cut -c1-100)" >> "$logf" 2>/dev/null || true
  cat <<'EOF'
-[design-toolchain] UI/design signal detected. Apply CLAUDE.md "Design work — full toolchain (tiered by scope)":
+Design work detected → apply global CLAUDE.md section "Design work — full toolchain" (already in context). Trivial (≤2 files, cosmetic) → /hotfix.
 - Trivial (≤2 files, single cosmetic value, CSS tweak) → /hotfix, NO toolchain.
 - Build UI (component/page/screen/redesign) → ui-ux-pro-max (plan/build) + frontend-design (anti-slop) + Magic MCP /ui (21st.dev scaffold) + emil-design-eng (polish) + design-motion-principles (if motion) + design-html (if static/Pretext).
 - Design system/brand → design-consultation FIRST, then the build tools above.
 - Review/audit → design-review + emil-design-eng lens + design-motion-principles (audit mode).
 If genuinely trivial/non-UI, ignore this and proceed. IN DOUBT about scope (trivial vs real UI change) → do NOT silently skip: ask the user, or default to the build tier rather than /hotfix.
 EOF
 fi
@@ -7,25 +7,53 @@
 # which is the single source of truth (src/discover/registry.rs).
 # To add or change rewrite rules, edit the Rust registry — not this file.
 #
 # INTEGRITY PIN: the rtk binary verifies this file against
 # hooks/.rtk-hook.sha256 at execution time and refuses to run on mismatch.
 # ANY edit here must re-pin:  (cd hooks && sha256sum rtk-rewrite.sh > .rtk-hook.sha256)
 #
 # Exit code protocol for `rtk rewrite`:
-#   0 + stdout  Rewrite found, no deny/ask rule matched → auto-allow
+#   0 + stdout  Rewrite found, no rtk deny/ask rule matched → rewrite. NO
-#   1           No RTK equivalent → pass through unchanged
+#               permissionDecision is emitted (auto-allow dropped 2026-07-02:
 #               it made rtk's registry a parallel permission authority that
 #               bypassed settings.json deny/ask). The REWRITTEN command goes
 #               through native evaluation; explicit `rtk <tool>` allow rules
 #               in settings.json keep read-only forms frictionless.
 #   1           No RTK equivalent → command continues unchanged into the
 #               redaction check below (still may be rewritten there)
 #   2           Deny rule matched → pass through (Claude Code native deny handles it)
 #   3 + stdout  Ask rule matched → rewrite but let Claude Code prompt the user
 #
 # Independent of the above: any command whose FINAL form is a single-pipeline
 # `printenv`/`env` dump gets a redaction pipe appended (job7 — see below).
 # This is a security post-process, not a token-savings rewrite, so it lives
 # here rather than in the Rust registry.
 if ! command -v jq &>/dev/null; then
  echo "[rtk] WARNING: jq is not installed. Hook cannot rewrite commands. Install jq: https://jqlang.github.io/jq/download/" >&2
  exit 0
 fi
-if ! command -v rtk &>/dev/null; then
+# PATH heal: hook/tool-shell PATH may lack the cargo bin dir (hand-managed
 # ~/.bashrc can lose the cargo line — LRN-036 class). Resolve the ABSOLUTE
 # binary path: the rewritten command executes in the tool shell, whose PATH
 # the hook cannot fix — a bare `rtk …` rewrite would exit 127 there.
 RTK_BIN="$(command -v rtk 2>/dev/null || true)"
 RTK_ON_PATH=1
 if [ -z "$RTK_BIN" ]; then
  RTK_ON_PATH=0
  for _d in "$HOME/.cargo/bin" "$HOME/.local/bin"; do
    if [ -x "$_d/rtk" ]; then RTK_BIN="$_d/rtk"; break; fi
  done
 fi
 if [ -z "$RTK_BIN" ]; then
  echo "[rtk] WARNING: rtk is not installed or not in PATH. Hook cannot rewrite commands. Install: https://github.com/rtk-ai/rtk#installation" >&2
  exit 0
 fi
 # Version guard: rtk rewrite was added in 0.23.0.
 # Older binaries: warn once and exit cleanly (no silent failure).
-RTK_VERSION=$(rtk --version 2>/dev/null | grep -oE '[0-9]+\.[0-9]+\.[0-9]+' | head -1)
+RTK_VERSION=$("$RTK_BIN" --version 2>/dev/null | grep -oE '[0-9]+\.[0-9]+\.[0-9]+' | head -1)
 if [ -n "$RTK_VERSION" ]; then
  MAJOR=$(echo "$RTK_VERSION" | cut -d. -f1)
  MINOR=$(echo "$RTK_VERSION" | cut -d. -f2)
@@ -44,22 +72,27 @@ if [ -z "$CMD" ]; then
 fi
 # Delegate all rewrite + permission logic to the Rust binary.
-REWRITTEN=$(rtk rewrite "$CMD" 2>/dev/null)
+REWRITTEN=$("$RTK_BIN" rewrite "$CMD" 2>/dev/null)
 EXIT_CODE=$?
 case $EXIT_CODE in
  0)
-    # Rewrite found, no permission rules matched — safe to auto-allow.
+    # Rewrite found. If identical to the input, RTK had nothing to add —
-    # If the output is identical, the command was already using RTK.
+    # keep going so the redaction check below still runs on it.
-    [ "$CMD" = "$REWRITTEN" ] && exit 0
+    [ "$CMD" = "$REWRITTEN" ] && REWRITTEN="$CMD"
    ;;
  1)
-    # No RTK equivalent — pass through unchanged.
+    # No RTK equivalent — keep the original command so the redaction
-    exit 0
+    # check below still runs on it.
    REWRITTEN="$CMD"
    ;;
  2)
-    # Deny rule matched — let Claude Code's native deny rule handle it.
+    # Deny rule matched (rtk's own registry — not necessarily backed by a
-    exit 0
+    # matching settings.json deny rule, so the original command can still
    # reach native evaluation and run: e.g. bare `env`/`printenv` hits this
    # exit code with no settings.json rule behind it). Keep the original
    # command so the redaction check below still runs on it.
    REWRITTEN="$CMD"
    ;;
  3)
    # Ask rule matched — rewrite the command but do NOT auto-allow so that
@@ -70,29 +103,51 @@ case $EXIT_CODE in
    ;;
 esac
 # Security: redact raw environment dumps before they can reach stdout/the
 # transcript (job7 — a bare `printenv`/`env` dump was the GITEA leak vector).
 # `env VAR=x cmd` (env launching a subprocess with a var set) is legitimate
 # and left intact. Scope: single-pipeline commands only — a command
 # containing `;`, `&`, or `||` bails untouched, same "lose the feature
 # rather than emit something wrong" rule as the RTK_ON_PATH substitution
 # below: appending the redaction pipe at the end would silently attach to
 # the WRONG segment of a compound command.
 if ! printf '%s' "$REWRITTEN" | grep -Eq '[;&]' \
   && ! printf '%s' "$REWRITTEN" | grep -qF '||'; then
  if printf '%s' "$REWRITTEN" | grep -Eq '^[[:space:]]*(printenv|env)([[:space:]]|$)' \
     && ! printf '%s' "$REWRITTEN" | grep -Eq '^[[:space:]]*env([[:space:]]+[A-Za-z_][A-Za-z0-9_]*=[^[:space:]]*)+[[:space:]]+[^|[:space:]]'; then
    REWRITTEN="${REWRITTEN} | sed -E 's/^([A-Za-z_]*(TOKEN|API_KEY|SECRET|PASSWORD|PASSWD)[A-Za-z_]*)=.*/\1=REDACTED/'"
  fi
 fi
 [ "$CMD" = "$REWRITTEN" ] && exit 0
 # When rtk is NOT on PATH, a bare `rtk …` rewrite exits 127 in the tool
 # shell (whose PATH the hook cannot fix). Substitute the absolute path at
 # the string head — the only position safe to rewrite. Compound commands
 # (`a && b`) can carry further bare rtk segments we canNOT substitute
 # safely (quoted text, e.g. commit messages, may contain the same
 # pattern): if any remain at a command position, pass through unrewritten
 # — lose the compression, never emit a command that 127s.
 if [ "$RTK_ON_PATH" -eq 0 ]; then
  case "$REWRITTEN" in
    rtk\ *) REWRITTEN="$RTK_BIN ${REWRITTEN#rtk }" ;;
  esac
  if printf '%s' "$REWRITTEN" | grep -Eq '(^|[;&|][[:space:]]*)rtk[[:space:]]'; then
    exit 0
  fi
 fi
 ORIGINAL_INPUT=$(echo "$INPUT" | jq -c '.tool_input')
 UPDATED_INPUT=$(echo "$ORIGINAL_INPUT" | jq --arg cmd "$REWRITTEN" '.command = $cmd')
-if [ "$EXIT_CODE" -eq 3 ]; then
+# Rewrite WITHOUT a permissionDecision (exit 0 and exit 3 alike): the
-  # Ask: rewrite the command, omit permissionDecision so Claude Code prompts.
+# rewritten command goes through Claude Code's native allow/deny/ask
-  jq -n \
+# evaluation. Permission control lives in settings.json, not in rtk.
-    --argjson updated "$UPDATED_INPUT" \
+jq -n \
-    '{
+  --argjson updated "$UPDATED_INPUT" \
-      "hookSpecificOutput": {
+  '{
-        "hookEventName": "PreToolUse",
+    "hookSpecificOutput": {
-        "updatedInput": $updated
+      "hookEventName": "PreToolUse",
-      }
+      "updatedInput": $updated
-    }'
+    }
-else
+  }'
  # Allow: rewrite the command and auto-allow.
  jq -n \
    --argjson updated "$UPDATED_INPUT" \
    '{
      "hookSpecificOutput": {
        "hookEventName": "PreToolUse",
        "permissionDecision": "allow",
        "permissionDecisionReason": "RTK auto-rewrite",
        "updatedInput": $updated
      }
    }'
 fi
@@ -1,7 +1,8 @@
 #!/usr/bin/env bash
 # ============================================================
 # Claude Code — Session start plugin status
-# Runs once per session. Zero API calls. Filesystem only.
+# Runs once per session. Filesystem only, except one quiet
 # git fetch for the version/update check near the end.
 # ============================================================
 # ── Quick health check (filesystem only, no subprocesses) ──
@@ -27,7 +28,7 @@ if [ ${#BROKEN[@]} -gt 0 ]; then
    printf "│  MISSING: ~/.claude/%-30s│\n" "$b"
  done
  printf "│  → %-47s│\n" "$_fix_cmd"
-  echo "│  → /health for full diagnostic                     │"
+  echo "│  → make doctor for full diagnostic                 │"
  echo "└───────────────────────────────────────────────────┘"
  unset _repo_hint _fix_cmd
 fi
@@ -35,7 +36,7 @@ fi
 # ── Load shared detection library ──
 _lib="$(dirname "${BASH_SOURCE[0]}")/../lib/detect-plugins.sh"
 if [ -f "$_lib" ]; then
-  # shellcheck source=../lib/detect-plugins.sh
+  # shellcheck source=../lib/detect-plugins.sh disable=SC1091
  source "$_lib"
 else
  echo "⚠️  lib/detect-plugins.sh not found — config broken, run: bash link.sh"
@@ -49,10 +50,12 @@ TOGGLE_ACTIVE=()
 TOGGLE_INACTIVE=()
 for plugin in gstack uiux_pro_max plugin_dev context7 graphifyy; do
-  # Map function name to display name
+  # Map function name to display name. graphifyy = the pipx PACKAGE name
  # (pypi:graphifyy); the CLI and skill are 'graphify' — display that.
  case "$plugin" in
    uiux_pro_max)    display="ui-ux-pro-max" ;;
    plugin_dev)      display="plugin-dev" ;;
    graphifyy)       display="graphify" ;;
    *)               display="$plugin" ;;
  esac
@@ -105,7 +108,7 @@ declare -A _plugin_costs=(
  [ui-ux-pro-max]=400
  [plugin-dev]=100
  [context7]=200
-  [graphifyy]=300
+  [graphify]=300
 )
 for _p in "${TOGGLE_ACTIVE[@]}"; do
  _cost="${_plugin_costs[$_p]:-0}"
@@ -129,20 +132,37 @@ echo "┌─ Claude Code config ────────────────
 # the user sees the real picture instead of a misleading literal.
 ALWAYS_ON=()
 detect_rtk &>/dev/null && ALWAYS_ON+=("rtk")
-plugin_enabled "security-guidance@claude-code-plugins"  && ALWAYS_ON+=("security-guidance")
+# Derive the plugin list from settings.json:enabledPlugins (true entries)
-plugin_enabled "superpowers@superpowers-marketplace"    && ALWAYS_ON+=("superpowers")
+# instead of a hardcoded name pair — a hardcoded SET under-reports newly
 # enabled plugins (pr-review-toolkit was enabled yet invisible). LRN-005
 # class. Plugins owned by the toggle row below are excluded (dual display).
 _toggle_owned=" gstack ui-ux-pro-max plugin-dev context7 graphify "
 while IFS= read -r _pl; do
  case "$_toggle_owned" in
    *" $_pl "*) : ;;
    *) ALWAYS_ON+=("$_pl") ;;
  esac
 done < <(grep -oE '"[A-Za-z0-9_-]+@[A-Za-z0-9_-]+"[[:space:]]*:[[:space:]]*true' "$HOME/.claude/settings.json" 2>/dev/null \
         | sed -E 's/^"([^@]+)@.*$/\1/')
 unset _toggle_owned _pl
 ALWAYS_ON_STR="${ALWAYS_ON[*]:-none}"
 # Same 40-char-width split policy as the toggle row below — keeps the
-# right border aligned when 4 always-on plugins overflow the field.
+# right border aligned on overflow. Greedy width-fill (not a fixed 3-name
 # cut: 3 long names overflowed line 1 and left line 2 empty).
 if [ "${#ALWAYS_ON_STR}" -le 40 ]; then
  printf "│  ✅ ON  : %-40s│\n" "$ALWAYS_ON_STR"
 else
-  _ao_line1="${ALWAYS_ON[0]} ${ALWAYS_ON[1]} ${ALWAYS_ON[2]:-}"
+  _ao_l1=""; _ao_l2=""
-  _ao_rest=("${ALWAYS_ON[@]:3}")
+  for _ao_e in "${ALWAYS_ON[@]}"; do
-  _ao_line2="${_ao_rest[*]}"
+    if [ -z "$_ao_l2" ] && [ $(( ${#_ao_l1} + ${#_ao_e} + 1 )) -le 40 ]; then
-  printf "│  ✅ ON  : %-40s│\n" "$_ao_line1"
+      _ao_l1="${_ao_l1:+$_ao_l1 }$_ao_e"
-  printf "│             %-40s│\n" "$_ao_line2"
+    else
-  unset _ao_line1 _ao_line2 _ao_rest
+      _ao_l2="${_ao_l2:+$_ao_l2 }$_ao_e"
    fi
  done
  printf "│  ✅ ON  : %-40s│\n" "$_ao_l1"
  printf "│             %-40s│\n" "$_ao_l2"
  unset _ao_l1 _ao_l2 _ao_e
 fi
 unset ALWAYS_ON ALWAYS_ON_STR
 # Plugin display — all plugins shown, split across 2 lines if >4
@@ -179,10 +199,22 @@ unset _active_count _inactive_count
 printf "│  🖥️  CLI : %-40s│\n" "$GSD_STATUS"
 [ -n "$TOKEN_WARN" ] && printf "│  💰 %-44s│\n" "${TOKEN_WARN:0:44}"
 printf "│  📦 v%-45s│\n" "$CONFIG_VERSION"
 # CLAUDE.global.md line-count guard (anti-regression). BDR-062 supersedes
 # BDR-031's 275 target: 305 is the assumed reality (extraction done at
 # job1; further compression costs clarity > token gain) — warn past 320.
 if [ -n "$REPO_DIR" ] && [ -f "$REPO_DIR/CLAUDE.global.md" ]; then
  _claude_lines=$(wc -l < "$REPO_DIR/CLAUDE.global.md")
  if [ "$_claude_lines" -gt 320 ]; then
    _cmd_warn="CLAUDE.global.md ${_claude_lines}L (>320) — density pass"
    printf "│  ⚠️  %-44s│\n" "${_cmd_warn:0:44}"
    unset _cmd_warn
  fi
  unset _claude_lines
 fi
 # Version check: compare local vs remote (non-blocking)
 _remote_ver=""
-if [ -n "$REPO_DIR" ] && [ -d "$REPO_DIR/.git" ]; then
+if [ -n "$REPO_DIR" ] && [ -d "$REPO_DIR/.git" ] && [ -z "${SESSION_START_OFFLINE:-}" ]; then
-  _remote_ver=$(cd "$REPO_DIR" 2>/dev/null && git fetch origin --quiet 2>/dev/null && git show origin/master:version.txt 2>/dev/null) || _remote_ver=""
+  _remote_ver=$(cd "$REPO_DIR" 2>/dev/null && git fetch origin --quiet 2>/dev/null && git show origin/main:version.txt 2>/dev/null) || _remote_ver=""
 fi
 if [ -n "$_remote_ver" ] && [ "$_remote_ver" != "$CONFIG_VERSION" ]; then
  printf "│  🔄 update available: v%-27s│\n" "$_remote_ver"
@@ -190,7 +222,7 @@ fi
 unset _remote_ver REPO_DIR
 echo "│  💡 /plugin-check  before starting a new project  │"
-echo "│  🩺 /health  to run full diagnostic               │"
+echo "│  🩺 make doctor  full diagnostic                  │"
 echo "└───────────────────────────────────────────────────┘"
 echo ""
 unset TOKEN_WARN
@@ -33,12 +33,15 @@ source "$REPO/lib/detect-plugins.sh"
 # graphify's installer (Step 7) rewrites CLAUDE.md + .claude/settings.json
 # (clobbers the curated graphify section + injects aggressive MANDATORY
 # hooks), and `claude plugin install` (Step 5) flips enable-states in
-# settings.json. These 3 files are maintained by hand + commit, never by
+# settings.json. These 4 files are maintained by hand + commit, never by
 # the installer. Snapshot them now and restore on exit so a run leaves them
 # exactly as it found them. Pre-existing local edits are preserved; only the
 # installer's drift is undone. NOTE: this makes these files install-immutable
 # — anything the installer should add to them must be committed by hand.
-GUARDED_CONFIGS=("CLAUDE.md" ".claude/settings.json" "settings.json")
+# CLAUDE.md = project memory (graphify's rewrite target); CLAUDE.global.md
 # = user-scope global memory (deployed as ~/.claude/CLAUDE.md).
 GUARDED_CONFIGS=("CLAUDE.md" "CLAUDE.global.md" ".claude/settings.json"
  "settings.json")
 CFG_SNAPSHOT="$(mktemp -d 2>/dev/null || true)"
 restore_curated_configs() {
@@ -62,7 +65,10 @@ if [ -n "$CFG_SNAPSHOT" ]; then
  done
  trap restore_curated_configs EXIT
 else
-  warn "Config guard disabled (mktemp failed) — CLAUDE.md/settings may drift"
+  err "Config guard could not be created (mktemp failed) — refusing to run" \
    "unguarded: CLAUDE.md/CLAUDE.global.md/.claude/settings.json/settings.json" \
    "could be silently rewritten by the installer. Fix mktemp/TMPDIR and retry."
  exit 1
 fi
 # Read pinned version from plugins.lock.json
@@ -125,29 +131,29 @@ else
  ok "git installed"
 fi
-# --- Node.js (>=18) ---
+# --- Node.js (>=24 — impeccable requires it; GSD v2 needs >=22) ---
 NODE_OK=false
 if command -v node &>/dev/null; then
  NODE_VER=$(node --version | sed 's/v//' | cut -d. -f1)
-  if [ "$NODE_VER" -ge 22 ]; then
+  if [ "$NODE_VER" -ge 24 ]; then
    ok "Node.js $(node --version)"; NODE_OK=true
  else
-    warn "Node.js $(node --version) is too old (need >=22 — GSD v2 requires it)"
+    warn "Node.js $(node --version) is too old (need >=24 — impeccable requires it)"
  fi
 fi
 if [ "$NODE_OK" = false ]; then
-  info "Installing Node.js 22 LTS..."
+  info "Installing Node.js 24 LTS..."
  case $OS in
    macos)
-      brew install node@22
+      brew install node@24
-      export PATH="/opt/homebrew/opt/node@22/bin:$PATH"
+      export PATH="/opt/homebrew/opt/node@24/bin:$PATH"
      ;;
    linux-apt)
-      curl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash -
+      curl -fsSL https://deb.nodesource.com/setup_24.x | sudo -E bash -
      sudo apt-get install -y nodejs
      ;;
    linux-dnf)
-      curl -fsSL https://rpm.nodesource.com/setup_22.x | sudo bash -
+      curl -fsSL https://rpm.nodesource.com/setup_24.x | sudo bash -
      sudo dnf install -y nodejs
      ;;
    linux-pacman)
@@ -162,12 +168,39 @@ if [ "$NODE_OK" = false ]; then
  fi
 fi
 # --- npm (bundled with Node, but distro `apt install nodejs` can ship it separately) ---
 # BLK-013 fix-forward: node>=22 present does NOT imply npm present. GSD (gsd-pi)
 # and ctx7 install via `npm install -g`, so a missing npm makes `make plugin`
 # die with Error 127 mid-run. The Node block above short-circuits when node is
 # already recent (NODE_OK=true) and never checks npm, so guarantee it here.
 if ! command -v npm &>/dev/null; then
  info "npm missing (Node without npm) — enabling via corepack, else package manager..."
  if command -v corepack &>/dev/null; then
    sudo corepack enable npm 2>/dev/null || corepack enable npm 2>/dev/null || true
  fi
  if ! command -v npm &>/dev/null; then
    case $OS in
      linux-apt)    sudo apt-get install -y npm || true ;;
      linux-dnf)    sudo dnf install -y npm || true ;;
      linux-pacman) sudo pacman -S --noconfirm npm || true ;;
      macos)        brew install node || true ;;   # brew's node bundles npm
      *) : ;;
    esac
  fi
  if command -v npm &>/dev/null; then
    ok "npm $(npm --version)"
  else
    err "npm still missing — GSD/ctx7 need it; install npm manually then re-run"; exit 1
  fi
 fi
 # --- Rust + Cargo (for RTK) ---
 if command -v cargo &>/dev/null; then
  ok "Rust/Cargo $(cargo --version | awk '{print $2}')"
 else
  info "Installing Rust (rustup)..."
  curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y --no-modify-path
  # shellcheck source=/dev/null
  source "$HOME/.cargo/env"
  ok "Rust installed: $(cargo --version)"
 fi
@@ -337,9 +370,10 @@ if [ -d "$GSTACK_DIR" ]; then
  gstack_bump_playwright_if_unsupported
  info "Running GStack setup..."
  _gstack_setup_ok=0
  if [ -x "$GSTACK_DIR/setup" ]; then
    if (cd "$GSTACK_DIR" && ./setup); then
-      : # setup succeeded
+      _gstack_setup_ok=1
    else
      warn "GStack ./setup failed — check output above"
    fi
@@ -355,9 +389,13 @@ if [ -d "$GSTACK_DIR" ]; then
     && [ "$(bash "$REPO/lib/toggle-external.sh" status gstack 2>/dev/null)" = "enabled" ]; then
    info "Disabling gstack by default (no context cost until enabled)..."
    bash "$REPO/lib/toggle-external.sh" disable gstack >/dev/null
-    ok "gstack installed, disabled — enable with: bash lib/toggle-external.sh enable gstack"
+  fi
  # Success message gated on the real setup outcome — an unconditional ok
  # after a `|| warn` reads as success even when setup failed (LRN-071 class).
  if [ "$_gstack_setup_ok" -eq 1 ]; then
    ok "GStack ready (disabled by default — enable: bash lib/toggle-external.sh enable gstack)"
  else
-    ok "GStack ready (submodule initialized, symlinks staged)"
+    warn "GStack NOT ready — ./setup did not complete (see warnings above)"
  fi
  # GStack shared infrastructure: bin/ (CLI tools) and browse/dist/ (compiled binary).
@@ -397,6 +435,19 @@ else
    cargo install --git https://github.com/rtk-ai/rtk
  fi
 fi
 # PATH bridge: cargo installs to ~/.cargo/bin, which hand-managed shell
 # profiles routinely lose (LRN-036 class). This installer sources cargo env
 # so `command -v rtk` passes HERE — but Claude's tool shell never gets that
 # PATH: the rewrite hook then drops every COMPOUND rewrite (it can only
 # absolute-path the string head) and compression silently dies (measured:
 # 6/5070 commands compressed over 30 days). ~/.local/bin is on the standard
 # PATH — bridge with a symlink. Idempotent; -x on a broken link is false,
 # so a stale link self-repairs.
 if [ -x "$HOME/.cargo/bin/rtk" ] && [ ! -x "$HOME/.local/bin/rtk" ]; then
  mkdir -p "$HOME/.local/bin"
  ln -sf "$HOME/.cargo/bin/rtk" "$HOME/.local/bin/rtk"
  ok "rtk bridged into ~/.local/bin (cargo bin dir is not on the tool-shell PATH)"
 fi
 # Only init if not already configured (avoids overwriting custom RTK config)
 if ! grep -q "rtk" "$HOME/.claude/settings.json" 2>/dev/null; then
  info "Configuring RTK PreToolUse hook (global)..."
@@ -500,7 +551,9 @@ enable_plugin  "security-guidance"  "claude-code-plugins"
 # (not in claude-code marketplace — it's a separate repo)
 install_plugin "example-skills"     "anthropic-agent-skills"
 install_plugin "pr-review-toolkit"  "claude-code-plugins"
-install_plugin "plugin-dev"         "claude-code-plugins"
+# plugin-dev dropped 2026-07-02 (audit #14): installed 2026-06-23, never
 # enabled, pure disk weight — reinstall deliberately if plugin authoring
 # becomes a need: claude plugin install plugin-dev@claude-code-plugins
 echo ""
@@ -523,7 +576,7 @@ echo ""
 # subscription plan its ~75% output-token compression has no cost benefit,
 # and the plugin's always-on SessionStart/UserPromptSubmit hooks added
 # friction on validation gates and client deliverables. The unrelated
-# memory-registry terse-format convention (CLAUDE.md) is kept.
+# memory-registry terse-format convention (CLAUDE.global.md) is kept.
 # ============================================================
 # STEP 6 — CONTEXT7 CLI (ctx7)
@@ -547,11 +600,51 @@ else
    err "ctx7 install failed — run manually: npm install -g ctx7"
  fi
 fi
-# Suggest setup for Claude Code integration (optional — ctx7 also works standalone)
+# ctx7 auth — detect, then offer login ONLY in an interactive TTY. A non-interactive
 # run (CI / headless / re-run) must never open a browser or block on OAuth.
 if command -v ctx7 &>/dev/null; then
-  info "Run 'ctx7 setup --claude' to configure Context7 for Claude Code"
+  # Deterministic offline oracle: ctx7's OAuth token lives here (XDG-aware).
-  info "Or use ctx7 standalone: ctx7 docs /vercel/next.js \"middleware\""
+  # Present => authenticated; absent => anonymous. No subprocess, no network, no browser.
-  info "Free higher rate limits: ctx7 login (OAuth) or --api-key from context7.com/dashboard"
+  ctx7_creds="${XDG_CONFIG_HOME:-$HOME/.config}/context7/credentials.json"
  if [ -f "$ctx7_creds" ]; then
    ok "ctx7 authenticated (full rate limits)"
  else
    info "ctx7 works anonymously — docs + library already usable, no auth required."
    if [ -t 0 ] && [ -t 1 ]; then
      # Interactive terminal: offer to log in now (opens a browser).
      printf '%b' "${BLUE}→${NC} Authenticate ctx7 now for higher rate limits? [y/N] "
      read -r ctx7_ans || ctx7_ans=""
      if [[ "$ctx7_ans" =~ ^[Yy]([Ee][Ss])?$ ]]; then
        if ctx7 login; then
          ok "ctx7 authenticated (full rate limits)"
        else
          warn "ctx7 login did not finish — re-run 'ctx7 login' anytime"
        fi
      else
        info "Skipped — authenticate later with:  ctx7 login"
      fi
    else
      # Non-interactive (CI / headless / re-run): never block — just guide.
      info "For higher rate limits, authenticate:  ctx7 login   (opens a browser)"
      info "  headless:  ctx7 login --no-browser   (prints a URL to open yourself)"
    fi
  fi
  # CLI + Skills mode: install the find-docs skill into ~/.claude/skills when
  # absent (it is gitignored — ctx7 owns it, this regenerates it on a fresh
  # clone). Guarded on absence so a re-run never clobbers a customized config.
  if [ ! -f "$HOME/.claude/skills/find-docs/SKILL.md" ]; then
    if ctx7 setup --claude --cli -y </dev/null &>/dev/null; then
      ok "ctx7 CLI + Skills configured (find-docs skill installed)"
    else
      warn "ctx7 setup failed — run manually: ctx7 setup --claude --cli"
    fi
  fi
  # Single ctx7 surface = the find-docs skill (BDR-053). setup also (re)writes
  # ~/.claude/rules/context7.md — a session-start duplicate of the skill
  # (~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"
  info "Standalone usage:  ctx7 docs /vercel/next.js \"middleware\""
 fi
 # ============================================================
@@ -570,11 +663,47 @@ else
  fi
 fi
 if command -v graphify &>/dev/null; then
  _graphify_ok=1
  info "Running graphify install (dependencies)..."
-  graphify install 2>/dev/null || warn "graphify install failed — run manually"
+  graphify install 2>/dev/null || { warn "graphify install failed — run manually"; _graphify_ok=0; }
  info "Configuring Claude Code integration..."
-  graphify claude install 2>/dev/null || warn "graphify claude install failed — run manually"
+  graphify claude install 2>/dev/null || { warn "graphify claude install failed — run manually"; _graphify_ok=0; }
-  ok "Graphifyy configured for Claude Code"
+  # Success message gated on the real outcome (LRN-071 class: an
  # unconditional ok after `|| warn` lies when a step failed).
  if [ "$_graphify_ok" -eq 1 ]; then
    ok "Graphify configured for Claude Code"
  else
    warn "Graphify NOT fully configured — re-run the failed step manually"
  fi
 fi
 echo ""
 # ============================================================
 # STEP 7.5 — SEMGREP (SAST engine for the security gate)
 # ============================================================
 echo "── Step 7.5: Semgrep — SAST security gate ───────────────────"
 echo ""
 if command -v semgrep &>/dev/null; then
  ok "semgrep already installed ($(semgrep --version 2>/dev/null | head -1))"
 else
  SEMGREP_VER=$(pinned_version "semgrep")
  if [ "$SEMGREP_VER" != "latest" ]; then
    info "Installing semgrep ${SEMGREP_VER} (pinned in plugins.lock.json)..."
    pipx install "semgrep==${SEMGREP_VER}" 2>/dev/null
  else
    info "Installing semgrep latest (consider pinning in plugins.lock.json)..."
    pipx install semgrep 2>/dev/null
  fi
  if command -v semgrep &>/dev/null; then
    ok "semgrep installed ($(semgrep --version 2>/dev/null | head -1))"
  else
    err "semgrep install failed — run manually: pipx install semgrep"
  fi
 fi
 # Login is Pro-rules only and optional — NEVER run automatically (ctx7
 # pattern: guide, don't block). The gate uses pinned public rulesets.
 if command -v semgrep &>/dev/null; then
  info "Optional Pro rules:  semgrep login   (never run automatically)"
 fi
 echo ""
@@ -645,6 +774,57 @@ else
 fi
 echo ""
 # ── Step 8d: Impeccable (design anti-pattern detector + skill) ──
 # 45 deterministic detector rules (CLI `impeccable detect`, exit 0/2) +
 # /impeccable skill (23 verbs). Machine-owned dist: the installer produces
 # it, we stage it in a tmpdir then move it under skills-external/
 # (gitignored, ctx7 pattern) — never let the installer write through the
 # ~/.claude/skills symlink into the tracked repo dir.
 echo "── Step 8d: Impeccable — design anti-pattern detector ────"
 echo ""
 IMP_DIR="$REPO/skills-external/impeccable"
 IMP_VER=$(pinned_version "impeccable")
 NODE_MAJOR=$(node -v 2>/dev/null | sed 's/^v//' | cut -d. -f1)
 if [ -z "${NODE_MAJOR:-}" ] || [ "$NODE_MAJOR" -lt 24 ]; then
  if [ -f "$IMP_DIR/SKILL.md" ]; then
    ok "impeccable already present (update skipped — needs Node >= 24, found ${NODE_MAJOR:-none})"
  else
    warn "impeccable: needs Node >= 24 (found ${NODE_MAJOR:-none}) — skipped. Bump Node, then: make plugin"
  fi
 else
  IMP_PKG="impeccable"
  if [ "$IMP_VER" != "latest" ]; then
    IMP_PKG="impeccable@${IMP_VER}"
    info "Installing impeccable ${IMP_VER} (pinned in plugins.lock.json, staged)..."
  else
    info "Installing impeccable latest (consider pinning in plugins.lock.json)..."
  fi
  IMP_STAGE=$(mktemp -d)
  if (cd "$IMP_STAGE" && npx -y "$IMP_PKG" skills install -y --providers=claude --scope=project --no-hooks >/dev/null 2>&1); then
    IMP_SRC=$(find "$IMP_STAGE" -type d -name impeccable -path "*skills*" 2>/dev/null | head -1)
    if [ -n "$IMP_SRC" ] && [ -f "$IMP_SRC/SKILL.md" ]; then
      rm -rf "$IMP_DIR"
      mv "$IMP_SRC" "$IMP_DIR"
      ok "impeccable synced to skills-external/ (CLI ${IMP_VER})"
    else
      warn "impeccable: installer ran but produced no skills/impeccable/SKILL.md — layout changed? Inspect: npx impeccable skills install"
    fi
  else
    if [ -f "$IMP_DIR/SKILL.md" ]; then
      ok "impeccable already present (installer failed — existing dist kept)"
    else
      warn "impeccable install failed — run manually: npx impeccable skills install -y --providers=claude --scope=project --no-hooks"
    fi
  fi
  rm -rf "$IMP_STAGE"
 fi
 if [ -L "$HOME/.claude/skills/impeccable" ]; then
  ok "impeccable symlink OK"
 else
  info "Symlinking — will be created by link.sh"
 fi
 echo ""
 # ============================================================
 # STEP 8.5 — EXTERNAL SKILLS (npx skills add …)
 # ============================================================
@@ -656,7 +836,6 @@ echo ""
 NPX_SKILLS=(
  "alchaincyf/darwin-skill"
  "alchaincyf/find-skills"
 )
 # `skills add` resolves its target (.agents/skills/, skills-lock.json) RELATIVE
@@ -809,7 +988,7 @@ echo ""
 # STEP 10 — REFRESH SYMLINKS (final, so this script is self-sufficient)
 # ============================================================
 # Steps 2/8/8.5 INSTALL skills (gstack submodule, emil/frontend/motion, npx
-# darwin/find-skills) that link.sh must symlink into ~/.claude/skills/. Since
+# darwin-skill) that link.sh must symlink into ~/.claude/skills/. Since
 # link.sh runs BEFORE this script in install.sh, those symlinks would be missing
 # on a fresh run until link.sh is run again by hand. Re-run it here so
 # `make plugin` (and `make install`) finish complete — nothing left to do.
@@ -835,19 +1014,18 @@ echo "    ✅ security-guidance   — PreToolUse security hook (0 tokens) [claud
 echo "    ✅ rtk                 — token compression hook (0 tokens)"
 echo "    ✅ superpowers         — brainstorm/plan/implement/debug workflow"
 echo ""
-echo "  TOGGLE (installed but start OFF — /plugin-check recommends when needed):"
+echo "  TOGGLE (plugin state = settings.json enabledPlugins; skills/CLIs = profiles):"
 echo "    🔄 gstack              — disabled by default (toggle: lib/toggle-external.sh enable gstack)"
 echo "    🔄 gsd v2              — standalone CLI 'gsd' (gsd-pi, not a Claude Code plugin)"
-echo "    🔄 plugin-dev          — create plugins/skills (~100 tokens) [claude-code-plugins]"
+echo "    🔄 pr-review-toolkit   — /review-pr + 6 PR agents (~2.2k tokens when enabled) [claude-code-plugins]"
-echo "    🔄 pr-review-toolkit   — /pr-review-toolkit:review-pr (~300 tokens) [claude-code-plugins]"
+echo "    🔄 ui-ux-pro-max       — user scope (~780 tokens when enabled)"
 echo "    🔄 ui-ux-pro-max       — user scope (~400 tokens)"
 echo "    🔄 context7 CLI        — ctx7 (npm global, standalone or MCP setup)"
-echo "    🔄 graphifyy           — codebase knowledge graph (pipx, PreToolUse hook)"
+echo "    🔄 graphifyy (CLI: graphify) — codebase knowledge graph (pipx, PreToolUse hook)"
 echo "    🔄 emil-design-eng     — UI polish, animations, component craft (curl → symlink)"
 echo "    🔄 frontend-design     — distinctive frontend interfaces, anti-AI-slop (anthropic-agent-skills)"
 echo "    🔄 impeccable          — /impeccable design verbs + 45-rule deterministic detector (npx impeccable detect)"
 echo "    🔄 design-motion-principles — motion/animation design, 3-designer lens (kylezantos)"
 echo "    🔄 darwin-skill        — autonomous skill optimizer (npx skills, ~/.agents/skills/)"
 echo "    🔄 find-skills         — skill discovery helper (npx skills, ~/.agents/skills/)"
 echo "    🔄 magic MCP           — 21st-dev UI generation MCP (toggle: lib/toggle-external.sh enable magic)"
 echo ""
 echo "  All plugins installed at: user scope (~/.claude/plugins/)"
@@ -22,8 +22,9 @@ echo ""
 # ── 1. Check prerequisites ──
 echo "── Checking prerequisites..."
-# node + npm drive the Claude Code CLI install below. On a fresh machine
+# node + npm are needed by the plugins step (install-plugins.sh: gsd-pi et al.);
-# they may be absent — install the current LTS via nvm instead of aborting.
+# Claude Code itself now installs via its own native installer below. On a fresh
 # machine node/npm may be absent — install the current LTS via nvm, not abort.
 install_node_via_nvm() {
  info "Node.js/npm missing — installing LTS via nvm..."
  curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash
@@ -54,9 +55,20 @@ ok "npm $(npm -v)"
 # ── 2. Install Claude Code CLI ──
 echo ""
-echo "── Installing Claude Code (latest)..."
+echo "── Installing Claude Code..."
-if npm install -g @anthropic-ai/claude-code@latest; then
+# Idempotent + official channel. Skip if already present (mirrors the RTK/GSD
 # guard) — the binary is a native-installer symlink at ~/.local/bin/claude that
 # self-updates. On a fresh machine install via the official native installer
 # (code.claude.com/docs quickstart), NOT npm: npm is no longer a documented
 # channel, would collide with the native symlink (EEXIST), and bypasses the
 # built-in auto-update. Upgrades are `make update`'s job, not first-time install.
 if command -v claude &>/dev/null; then
  ok "Claude Code already installed ($(claude --version 2>/dev/null | head -1))"
 elif curl -fsSL https://claude.ai/install.sh | bash; then
  # Native installer targets ~/.local/bin — put it on PATH for the auth +
  # verification steps that follow in this same (non-login) shell.
  export PATH="$HOME/.local/bin:$PATH"
  ok "Claude Code installed: $(claude --version 2>/dev/null || echo 'unknown')"
 else
  err "Claude Code installation failed"
@@ -94,6 +106,16 @@ echo ""
 echo "── Setting up symlinks..."
 bash "$REPO/link.sh"
 # ── 5b. Optional: connect a Google account for /seo FULL ──
 echo ""
 if [ -f "$HOME/.claude/seo-data/tokens.json" ]; then
  ok "seo-data: a Google account is already connected"
 else
  info "SEO data layer (GSC + CrUX) is optional. To enable real Search Console"
  info "data in /seo FULL: add GOOGLE_OAUTH_* + CRUX_API_KEY to ~/.claude/.env,"
  info "then run:  make seo-connect"
 fi
 # ── 6. Install plugins ──
 echo ""
 echo "── Installing plugins..."
@@ -0,0 +1,104 @@
 # Contract interview — mandatory upstream passage (all orchestrators)
 Produces the CONTRACT: the single reference passed verbatim to the plan, the
 dev subagents, and the verifier. The contract is what lets the orchestrator
 delegate execution without subagents ever needing a human gate (LRN-083:
 subagents = execution + report only; gates and loop decisions live in the
 main loop).
 Run this in the ORCHESTRATOR MAIN LOOP, never in a subagent — STEP 2 may
 talk to the human. Mandatory passage in every flow; questions are optional
 and proportional — a complete request goes through silently.
 ## STEP 1 — CAPTURE (verbatim)
 Copy the user's request EXACTLY as typed (`$ARGUMENTS` + the triggering
 message). No paraphrase, no cleanup, no translation, no summarizing. This
 section is IMMUTABLE for the life of the run — every later consumer
 (planner, dev, verifier) reads THESE words, never a restatement.
 ## STEP 2 — AMBIGUITY CHECK (questions optional, proportional)
 Ask ONLY if one of these is missing AND not derivable from the repo:
 - a testable expected outcome
 - an unambiguous scope (what is allowed to change)
 - non-contradictory constraints
 Complete request → ZERO questions, stay silent. Otherwise: max 3 questions,
 one single batch (house rule: one question upfront, never mid-task). Never
 ask what the repo can answer — verify paths/APIs/behavior yourself first.
 ## STEP 3 — DERIVE
 - ACCEPTANCE CRITERIA: numbered; each one testable — a fresh reader must be
  able to mark it MET / NOT-MET against the real code, without having seen
  this conversation.
 - FILE SCOPE: paths/zones expected to change, or `repo-wide — <reason>`.
 ## STEP 4 — WRITE TO DISK (immediately, before any next step)
 Path: `.claude/tasks/contracts/<YYYY-MM-DD>-<slug>-<HHMM>.md`
 (`mkdir -p` the directory; unique per run: date + short kebab slug + HHMM —
 two runs on the same day never collide). A contract that lives only in
 context dies at compaction, and the verbatim request with it.
 Template:
 ```markdown
 # CONTRACT — <slug>
 - date: <YYYY-MM-DD> | flow: <ship-feature|feat|bugfix|hotfix|init-project|onboard> | branch: <branch>
 - status: active
 ## REQUEST (verbatim — IMMUTABLE)
 <the user's exact words>
 ## CLARIFICATIONS
 Q: <question> / A: <answer>
 (or: none — request complete)
 ## ACCEPTANCE CRITERIA
 1. <testable criterion>
 2. <testable criterion>
 ## FILE SCOPE
 <paths/zones>
 (or: repo-wide — <reason>)
 ```
 Print one line to the user, then continue the flow:
 `CONTRACT: <path> — <n> criteria, scope <files|repo-wide>, <q> questions asked`
 ## Lifecycle
 - **REQUEST**: immutable, for the life of the run. Never rewritten, never
  "cleaned up".
 - **CRITERIA / FILE SCOPE enrichment**: ONLY at a human gate, each added
  entry marked `[gated <YYYY-MM-DD>]`. A dev subagent NEVER enriches the
  contract. An out-of-scope edit the dev justifies is accepted ONLY through
  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.
 - **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
  `status: aborted` in the header. NEVER left dirty in the working tree.
 - **Commit**: the contract rides the existing memory commit —
  `lib/capitalize-commit.md` already covers the `.claude/tasks` pathspec.
  No new plumbing.
 ## Weight per flow
 | Flow | Weight |
 |------|--------|
 | hotfix | Silent autofill — criteria: "symptom gone; build/tests green"; scope = the 1-2 target files. Zero questions ever. |
 | feat / bugfix | Proportional. bugfix: the DIAGNOSIS feeds the criteria (symptom reproduced-then-gone + regression test present). |
 | ship-feature | Full. Design decisions approved at the validation gate append criteria `[gated <date>]` — the human validates the enriched contract, the verifier receives that version. |
 | 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). |
 ## Hand-off rule
 Downstream consumers (plan step, dev subagents, verifier) receive the
 contract PATH, not a restatement of its content — the file on disk is the
 only authoritative copy, and reading it from disk is what makes the dev's
 reformulation structurally unable to interpose.
@@ -1,6 +1,18 @@
 #!/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).
 #
 # Exit code taxonomy:
 #   0  committed (short-hash on stdout), or `pending`: something changed
 #   1  no-op — nothing staged/changed (`pending`: clean) — NOT a failure
 #   2  usage error, or not a git repo
 #   3  unsafe git state (detached HEAD / merge / rebase in progress)
 #   4  a passed path is outside the .claude/deploy/ allowlist
 #   5  a passed path is git-ignored and would not persist
 #   6  `git commit` itself was REJECTED (pre-commit hook, protected branch,
 #      signing failure, …) — distinct from rc 1 (no-op): here something WAS
 #      staged and git refused it. Client repos may parse this by exit code,
 #      not just stderr, so it can't share rc 1's "nothing to do" (J4-22).
 set -uo pipefail
 _in_git_repo() { git rev-parse --git-dir >/dev/null 2>&1; }
@@ -67,7 +79,8 @@ case "$cmd" in
    if git diff --cached --quiet -- "${changed[@]}"; then
      echo "deploy-commit: nothing staged — no-op" >&2; exit 1
    fi
-    git commit -q -m "$msg" -- "${changed[@]}" || { echo "deploy-commit: git commit failed" >&2; exit 1; }
+    git commit -q -m "$msg" -- "${changed[@]}" \
      || { echo "deploy-commit: COMMIT REJECTED — git commit exited non-zero (pre-commit hook? protected branch? signing?)." >&2; exit 6; }
    git rev-parse --short HEAD ;;
  *) echo "usage: deploy-commit.sh pending <file>... | commit \"<msg>\" <file>..." >&2; exit 2 ;;
 esac
@@ -40,7 +40,7 @@ and if not, point at ONE command — `/profile design`.
 Tier does NOT change WHAT gets checked. Every non-trivial design tier draws from
 the one `design` profile — so the gate checks that profile's **design-core
 tools** (the `# GATE-BLOCK:` allowlist in `design.profile`: ui-ux-pro-max,
-frontend-design, emil-design-eng, design-motion-principles, design-html,
+frontend-design, emil-design-eng, design-motion-principles, impeccable, design-html,
 design-review, design-consultation, magic). The profile also bundles
 browser/plan/shotgun tooling and graphify for convenience; those never trip the
 gate. Motion (`design-motion-principles`) and static-HTML (`design-html`) are
@@ -42,7 +42,8 @@
 set -euo pipefail
 REPO="$(cd -P "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
-PROFILE_SH="$REPO/lib/profile.sh"
+PROFILE_SH="${DESIGN_GATE_PROFILE_SH:-$REPO/lib/profile.sh}"
 CLAUDE_BIN="${CLAUDE_BIN:-claude}"
 PROFILES_DIR="$REPO/lib/profiles"
 SKILLS_DIR="$REPO/skills"
 PROFILE="${1:-design}"
@@ -59,7 +60,7 @@ PROFILE_FILE="$PROFILES_DIR/$PROFILE.profile"
 # dirs and prepend. nvm keeps old node versions after an upgrade, so pick the
 # newest that actually ships claude (sort -V), not the first glob match.
 ensure_claude_on_path() {
-  command -v claude >/dev/null 2>&1 && return
+  command -v "$CLAUDE_BIN" >/dev/null 2>&1 && return
  local cand
  for cand in \
    "$HOME/.claude/local/claude" \
@@ -98,15 +99,15 @@ tool_active() {
      if [ -e "$SKILLS_DIR/$name" ]; then echo active; else echo inactive; fi
      ;;
    plugin)
-      if ! command -v claude >/dev/null 2>&1; then echo unknown; return; fi
+      if ! command -v "$CLAUDE_BIN" >/dev/null 2>&1; then echo unknown; return; fi
-      if claude plugin list 2>/dev/null \
+      if "$CLAUDE_BIN" plugin list 2>/dev/null \
           | awk -v p="^[[:space:]]*❯ ${name}@" '$0 ~ p {f=1; next} f && /Status:/ {print; exit}' \
           | grep -q "✔ enabled"
      then echo active; else echo inactive; fi
      ;;
    mcp)
-      if ! command -v claude >/dev/null 2>&1; then echo unknown; return; fi
+      if ! command -v "$CLAUDE_BIN" >/dev/null 2>&1; then echo unknown; return; fi
-      if claude mcp list 2>/dev/null | grep -q "^${name}"; then echo active; else echo inactive; fi
+      if "$CLAUDE_BIN" mcp list 2>/dev/null | grep -q "^${name}"; then echo active; else echo inactive; fi
      ;;
    cli)
      if command -v "$name" >/dev/null 2>&1; then echo active; else echo inactive; fi
@@ -10,7 +10,9 @@
 # --- Always-on plugins ---
 detect_rtk() {
-  command -v rtk &>/dev/null
+  command -v rtk &>/dev/null && return 0
  # PATH heal: hook/session PATH may lack the cargo bin dir (LRN-036 class)
  [ -x "$HOME/.cargo/bin/rtk" ] || [ -x "$HOME/.local/bin/rtk" ]
 }
 detect_superpowers() {
@@ -24,11 +26,6 @@ detect_superpowers() {
  return 1
 }
 detect_security_guidance() {
  local cache_dir="$HOME/.claude/plugins/cache"
  [ -d "$cache_dir" ] && compgen -G "$cache_dir"/*security-guidance* &>/dev/null
 }
 # --- Toggle plugins ---
@@ -66,15 +63,6 @@ detect_graphifyy() {
  command -v graphify &>/dev/null
 }
 # True if a plugin is registered as enabled in settings.json's
 # enabledPlugins map. Filesystem only (no subprocess to claude CLI).
 # Argument is the full "name@marketplace" key.
 plugin_enabled() {
  local key="$1"
  [ -f "$HOME/.claude/settings.json" ] || return 1
  grep -qE "\"${key}\"[[:space:]]*:[[:space:]]*true" "$HOME/.claude/settings.json"
 }
 # --- Plan detection ---
@@ -13,7 +13,6 @@
 # Caller passes EXACTLY the files doc-sync patched this run.
 #
 # Usage (CLI):
 #   doc-commit.sh pending <file>...            # exit 0 if any passed file has changes, 1 if clean
 #   doc-commit.sh commit "<message>" <file>... # surgical commit
 #
 # Exit codes (commit): 0 ok/no-op · 2 usage · 3 unsafe git state · 4 scope violation ·
@@ -22,7 +21,7 @@
 # commit is the ONLY thing on stdout (empty on no-op/abort), so callers can capture
 # it: doc_hash=$(doc-commit.sh commit "msg" README.md USAGE.md).
 #
-# Sourceable: docs_pending and commit_docs for the v2 hook.
+# Sourceable: `commit_docs`.
 set -uo pipefail
@@ -42,11 +41,13 @@ _unsafe_state() {
 }
 # True (0) when a path is OUT OF SCOPE for a doc commit: anything under .claude/
-# (any depth) or a CLAUDE.md (root or nested). These are doc-syncer's read-only
+# (any depth) or a CLAUDE.md / CLAUDE.global.md memory file (root or nested).
-# context, never sync targets (BDR-022) — their presence is an upstream anomaly.
+# These are doc-syncer's read-only context, never sync targets (BDR-022) —
 # their presence is an upstream anomaly.
 _forbidden_path() {
  case "$1" in
-    .claude | .claude/* | */.claude/* | CLAUDE.md | */CLAUDE.md) return 0 ;;
+    .claude | .claude/* | */.claude/* | CLAUDE.md | */CLAUDE.md | \
      CLAUDE.global.md | */CLAUDE.global.md) return 0 ;;
    *) return 1 ;;
  esac
 }
@@ -70,14 +71,6 @@ _changed_paths() {
  done
 }
 # 0 if any passed path has pending changes, 1 if all clean / absent.
 docs_pending() {
  _in_git_repo || return 1
  local changed
  mapfile -t changed < <(_changed_paths "$@")
  [ "${#changed[@]}" -gt 0 ]
 }
 # Surgical commit of the passed doc paths only. Returns 0 (ok/no-op), 3 (unsafe),
 # 4 (scope violation), 5 (commit rejected by git). On a real commit, prints the
 # doc-commit short hash to stdout.
@@ -143,16 +136,12 @@ commit_docs() {
 main() {
  local cmd="${1:-}"
  case "$cmd" in
    pending)
      shift
      docs_pending "$@"
      ;;
    commit)
      shift
      commit_docs "$@"
      ;;
    *)
-      echo "usage: doc-commit.sh {pending <file>... | commit <message> <file>...}" >&2
+      echo "usage: doc-commit.sh commit <message> <file>..." >&2
      return 2
      ;;
  esac
@@ -1,26 +1,41 @@
-# Gitflow aiguillage — assistance flows branch on a protected base
+# Gitflow aiguillage — branch on a protected base before writing
-Assistance flows (`/feat`, `/bugfix`, `/hotfix`) commit IN PLACE on a working
+Flows that WRITE — code, OR standalone memory/doc work — must NEVER commit on a
-branch — the frequent case, behavior unchanged. But they must NEVER commit code
+protected base (`main`/`develop`). Run this check **before editing any file**.
 on a protected base (`main`/`develop`). Run this check **before editing any
 file**. The caller passes its TYPE: feat→`feature`, bugfix→`bugfix`,
 hotfix→`hotfix`.
 ```bash
 bash "$HOME/.claude/lib/gitflow.sh" protected-base && echo PROTECTED || echo WORKING
 ```
- **WORKING** (`feature/*`, `bugfix/*`, `hotfix/*`, or any non-protected branch)
+- **WORKING** (`feature/*`, `bugfix/*`, `hotfix/*`, `chore/*`, or any non-protected
-  → proceed; you commit in place on this branch. Nothing changes.
+  branch) → proceed; you commit in place on this branch. Nothing changes.
 - **PROTECTED** (`main`/`develop`) → branch first, do NOT commit here:
  ```bash
  bash "$HOME/.claude/lib/gitflow.sh" start <YOUR-TYPE> <short-kebab-name>
  ```
  `<short-kebab-name>` derived from the request. Then do the work on the new branch.
-**Never run `gitflow finish`** — assistance flows commit, they do not merge.
+The caller passes its TYPE:
 Integration is a separate, human-gated step (the `gitflow` skill).
-Note: `hotfix` branches off **main** (prod) even when invoked from `develop` —
+| Caller | TYPE | Base |
-that is the gitflow definition of a hotfix. For a dev-scoped small fix, use
+|--------|------|------|
-`/bugfix` (branches off develop).
+| `/feat` | `feature` | develop |
 | `/bugfix` | `bugfix` | develop |
 | `/hotfix` | `hotfix` | main |
 | `/capitalize` · `/close` · `/prune-memory` · `/reconcile` | `chore` | develop |
 The `chore` row = **standalone memory/doc work**: the registry / TODO / doc
 reconciliation & curation skills, run OUTSIDE an assistance flow. Inside `/feat`
 `/bugfix` `/hotfix` `/ship-feature` a working branch already exists (this check
 returns WORKING) and the memory commit rides it. The aiguillage only fires when
 such a skill is invoked directly on `main`/`develop` — i.e. memory IS the work,
 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).
 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`
 (branches off develop).
@@ -1,95 +0,0 @@
 #!/usr/bin/env bash
 # gitflow-migrate.sh — migrate an existing repo to the gitflow model.
 #   LOCAL  (no token): gitflow init existing → master→main, develop, socle, hook.
 #   PROBE  (token, READ-ONLY): identity + scope/rights, before any write.
 #   REMOTE (token, DESTRUCTIVE): push, default→main, protection, delete master.
 #          Writes ordered reversible→irreversible; DELETE master is LAST and only
 #          runs if every prior step succeeded. Halts on first failure.
 # No `... | grep -q` under pipefail (SIGPIPE false-negative gotcha). Never echo the token.
 set -uo pipefail
 GITEA="${GITEA_URL:-https://git.bchanot.fr}"
 OWNER="${GITEA_OWNER:-bchanot}"
 # ── LOCAL half (token-free) ──────────────────────────────────────────────────
 migrate_local() {                      # <repo-path>
  local repo="$1" renamed="no"
  cd "$repo" || { echo "  ✗ cannot cd $repo" >&2; return 1; }
  [ -z "$(git status --porcelain)" ] || { echo "  ✗ working tree not clean — stash/commit first" >&2; return 2; }
  { [ -n "$(git config user.name)" ] && [ -n "$(git config user.email)" ]; } \
    || { echo "  ✗ git identity unset (user.name/user.email) — set it before migrating $repo" >&2; return 3; }
  git show-ref --verify -q refs/heads/master && renamed="yes"
  bash "$HOME/.claude/lib/gitflow.sh" init || return 1
  git show-ref --verify -q refs/heads/main    || { echo "  ✗ no main"    >&2; return 1; }
  git show-ref --verify -q refs/heads/develop || { echo "  ✗ no develop" >&2; return 1; }
  [ "$(git config core.hooksPath)" = ".githooks" ] || { echo "  ✗ hook not active" >&2; return 1; }
  [ -z "$(git status --porcelain)" ] || { echo "  ✗ tree dirty after init" >&2; return 1; }
  echo "  ✓ local: main+develop, hook active, tree clean (master→main: $renamed)"
 }
 # ── Gitea API helper (token in header only; never printed) ────────────────────
 _gitea() {                             # <METHOD> <api-path> [json-body]
  local m="$1" p="$2" body="${3:-}"
  curl -fsS -X "$m" -H "Authorization: token $GITEA_TOKEN" \
       -H "Content-Type: application/json" ${body:+-d "$body"} "$GITEA/api/v1$p"
 }
 _json() { python3 -c "import sys,json;$1" 2>/dev/null; }   # tiny JSON field reader
 # ── PROBE (READ-ONLY: identity informational, rights = the real gate) ─────────
 # /user needs read:user (cosmetic — the migration never calls it) → informational.
 # The gates are the repo-scoped rights the writes actually require: admin+push on
 # the repo, and admin scope confirmed by a readable branch_protections list.
 gitea_probe() {                        # <repo-name to test rights against>
  local name="$1" me pj perm
  [ -n "${GITEA_TOKEN:-}" ] || { echo "  ✗ GITEA_TOKEN unset" >&2; return 1; }
  # [a] identity — INFORMATIONAL (needs read:user scope the migration never uses)
  if me=$(_gitea GET "/user" 2>/dev/null | _json "print(json.load(sys.stdin).get('login','?'))") && [ -n "$me" ]; then
    echo "  ✓ token identity: $me"
  else
    echo "  ⚠ token identity unavailable (no read:user scope) — cosmetic, migration is repo-scoped"
  fi
  # [b] repo rights — GATE: admin AND push must be true (default_branch, protections, push)
  pj=$(_gitea GET "/repos/$OWNER/$name") \
     || { echo "  ✗ GET /repos/$OWNER/$name failed — token lacks repo read scope" >&2; return 1; }
  perm=$(printf '%s' "$pj" | _json "p=json.load(sys.stdin).get('permissions',{});print('admin=%s push=%s pull=%s'%(p.get('admin'),p.get('push'),p.get('pull')))")
  printf '%s' "$pj" | _json "p=json.load(sys.stdin).get('permissions',{});sys.exit(0 if (p.get('admin') and p.get('push')) else 1)" \
     || { echo "  ✗ insufficient rights on $name ($perm) — need admin+push" >&2; return 1; }
  echo "  ✓ rights on $name: $perm (admin+push confirmed)"
  # [c] admin-scope canary — GATE: branch_protections readable (POST/PATCH/DELETE need repo-admin)
  _gitea GET "/repos/$OWNER/$name/branch_protections" >/dev/null \
     || { echo "  ✗ cannot read branch_protections — token lacks repo-admin scope; protection step would fail" >&2; return 1; }
  echo "  ✓ repo-admin scope confirmed (branch_protections readable → POST/PATCH/DELETE OK)"
 }
 # ── REMOTE half (DESTRUCTIVE; reversible→irreversible; delete master LAST) ────
 _protect() {                           # <repo-name> <branch>  (Option 1: owner-pushable)
  _gitea POST "/repos/$OWNER/$1/branch_protections" \
    "{\"branch_name\":\"$2\",\"enable_push\":true,\"enable_push_whitelist\":true,\"push_whitelist_usernames\":[\"$OWNER\"]}"
 }
 migrate_remote() {                     # <repo-name>  (cwd = the local repo)
  local name="$1"
  [ -n "${GITEA_TOKEN:-}" ] || { echo "  ✗ GITEA_TOKEN unset" >&2; return 1; }
  echo "  [1/4] push main + develop (ADDITIVE/reversible)…"
  git push -u origin main    || { echo "  ✗ push main failed (push scope?) — STOP, nothing irreversible done" >&2; return 1; }
  git push -u origin develop || { echo "  ✗ push develop failed — STOP" >&2; return 1; }
  echo "  [2/4] default_branch → main (REVERSIBLE — scope canary)…"
  _gitea PATCH "/repos/$OWNER/$name" '{"default_branch":"main"}' >/dev/null \
    || { echo "  ✗ PATCH default_branch failed (admin/write scope?) — STOP before protection & delete" >&2; return 1; }
  echo "  [3/4] branch protection main + develop (REVERSIBLE)…"
  _protect "$name" main    >/dev/null || { echo "  ✗ protect main failed — STOP before delete" >&2; return 1; }
  _protect "$name" develop >/dev/null || { echo "  ✗ protect develop failed — STOP before delete" >&2; return 1; }
  echo "  [4/4] DELETE remote master (IRREVERSIBLE — last; default already repointed)…"
  git push origin --delete master || { echo "  ✗ delete master failed (left in place — safe)" >&2; return 1; }
  echo "  ✓ remote: default=main, main/develop protected (owner-pushable), remote master deleted"
 }
 if [ "${BASH_SOURCE[0]}" = "${0}" ]; then
  case "${1:-}" in
    local)  migrate_local "$2" ;;
    probe)  gitea_probe "$2" ;;
    remote) migrate_remote "$2" ;;
    *) echo "usage: gitflow-migrate.sh {local <repo>|probe <name>|remote <name>}" >&2; exit 2 ;;
  esac
 fi
@@ -32,6 +32,9 @@ chk "protected develop"   'gitflow_protected_base develop'
 chk "not protected feat"  '! gitflow_protected_base feature/x'
 chk "base feature=develop" '[ "$(gitflow_base_for feature)" = develop ]'
 chk "base hotfix=main"     '[ "$(gitflow_base_for hotfix)" = main ]'
 chk "type chore"           '[ "$(gitflow_branch_type chore/x)" = chore ]'
 chk "base chore=develop"   '[ "$(gitflow_base_for chore)" = develop ]'
 chk "not protected chore"  '! gitflow_protected_base chore/x'
 echo "T2 — init fresh (BLK-010 root commit)"
 newrepo fresh; echo scaffold > README.md; hookon
@@ -92,6 +95,16 @@ chk "merged into develop" 'git log develop --oneline | grep -q "Merge feature/f1
 chk "main untouched"      "[ \"\$(git rev-parse main)\" = \"$main_before\" ]"
 chk "branch deleted"      '! git rev-parse --verify -q refs/heads/feature/f1 >/dev/null'
 echo "T6b — finish chore → develop only (standalone memory/doc maintenance)"
 newrepo finchore; echo a>a; hookon; gitflow_init >/dev/null 2>&1
 gitflow_start chore c1 >/dev/null 2>&1
 mkdir -p .claude/memory; echo m>.claude/memory/x.md; git add -A; git commit -q -m "chore(memory)"
 main_before="$(git rev-parse main)"
 gitflow_finish >/dev/null 2>&1
 chk "chore merged into develop" 'git log develop --oneline | grep -q "Merge chore/c1 into develop"'
 chk "chore main untouched"      "[ \"\$(git rev-parse main)\" = \"$main_before\" ]"
 chk "chore branch deleted"      '! git rev-parse --verify -q refs/heads/chore/c1 >/dev/null'
 echo "T7 — finish hotfix → main + develop fan-out"
 newrepo finhot; echo a>a; hookon; gitflow_init >/dev/null 2>&1
 gitflow_start hotfix h1 >/dev/null 2>&1; echo p>patch.txt; git add patch.txt; git commit -q -m patch
@@ -119,7 +132,7 @@ chk "idempotent 2nd run"  "[ \"$before\" = \"\$(md5sum .gitignore)\" ]"
 echo "T10 — COHERENCE: hook verdict == lib predicate (drift detector, #4)"
 newrepo coh; echo a>a; hookon; gitflow_init >/dev/null 2>&1
-for br in main develop feature/x bugfix/y release/z hotfix/w master mainline qa; do
+for br in main develop feature/x bugfix/y release/z hotfix/w chore/m master mainline qa; do
  if gitflow_protected_base "$br"; then lib=protected; else lib=open; fi
  git checkout -q -B "$br" 2>/dev/null
  printf 'x\n' >> a; git add a
@@ -143,6 +156,106 @@ if bash "$HERE/gitflow.sh" protected-base main;       then ok "cli protected-bas
 if bash "$HERE/gitflow.sh" protected-base feature/x;  then no "cli protected-base feature (rc0?)"; else ok "cli protected-base feature → rc1"; fi
 chk "cli base-for hotfix=main" '[ "$(bash "$HERE/gitflow.sh" base-for hotfix)" = main ]'
 echo "T12 — finish arg-guard (named branch must equal current, else refuse)"
 newrepo finargs; echo a>a; hookon; gitflow_init >/dev/null 2>&1
 gitflow_start feature standon >/dev/null 2>&1; echo w>w.txt; git add w.txt; git commit -q -m w
 # mismatch: standing on feature/standon but asking to finish bugfix/other → refuse
 # shellcheck disable=SC2034  # mism_out/mism_rc are used in the deferred chk eval strings
 mism_out="$(gitflow_finish bugfix other 2>&1)"; mism_rc=$?
 chk "arg-mismatch → nonzero rc"       "[ $mism_rc -ne 0 ]"
 chk "arg-mismatch → HEAD untouched"   '[ "$(git symbolic-ref --short HEAD)" = feature/standon ]'
 chk "arg-mismatch → branch kept"      'git rev-parse --verify -q refs/heads/feature/standon >/dev/null'
 chk "arg-mismatch → develop NOT merged" '! git log develop --oneline | grep -q "Merge feature/standon into develop"'
 chk "arg-mismatch → message names both" 'printf "%s" "$mism_out" | grep -q "current branch" && printf "%s" "$mism_out" | grep -q "bugfix/other"'
 # match: naming the current branch explicitly finishes exactly like the no-arg path
 gitflow_finish feature standon >/dev/null 2>&1
 chk "arg-match → merged into develop" 'git log develop --oneline | grep -q "Merge feature/standon into develop"'
 chk "arg-match → branch deleted"      '! git rev-parse --verify -q refs/heads/feature/standon >/dev/null'
 echo "T13 — finish release fan-out (main+develop+delete), 2 open releases + bugfix→develop-only"
 newrepo finrel; echo a>a; hookon; gitflow_init >/dev/null 2>&1
 gitflow_start release 9.9.9 >/dev/null 2>&1; echo v>VERSION; git add VERSION; git commit -q -m "bump 9.9.9"
 finish_rc=0; gitflow_finish >/dev/null 2>&1 || finish_rc=$?
 chk "T13a finish rc 0"                 "[ $finish_rc -eq 0 ]"
 chk "T13a main has release commit"     'git log main --oneline | grep -q "bump 9.9.9"'
 chk "T13a develop has release commit"  'git log develop --oneline | grep -q "bump 9.9.9"'
 chk "T13a release branch deleted"      '! git rev-parse --verify -q refs/heads/release/9.9.9 >/dev/null'
 newrepo finrel2; echo a>a; hookon; gitflow_init >/dev/null 2>&1
 gitflow_start release 1.0 >/dev/null 2>&1; echo r1>r1; git add r1; git commit -q -m rel1
 gitflow_start release 2.0 >/dev/null 2>&1; echo r2>r2; git add r2; git commit -q -m rel2
 gitflow_start hotfix hboth >/dev/null 2>&1; echo p>p; git add p; git commit -q -m hotfixboth
 gitflow_finish >/dev/null 2>&1
 chk "T13b hotfix in release/1.0" 'git log release/1.0 --oneline | grep -q "Merge hotfix/hboth into release/1.0"'
 chk "T13b hotfix in release/2.0" 'git log release/2.0 --oneline | grep -q "Merge hotfix/hboth into release/2.0"'
 newrepo finbugfix; echo a>a; hookon; gitflow_init >/dev/null 2>&1
 gitflow_start bugfix bx >/dev/null 2>&1; echo w>w.txt; git add w.txt; git commit -q -m bugfixwork
 main_before="$(git rev-parse main)"
 gitflow_finish >/dev/null 2>&1
 chk "T13c develop has bugfix commit" 'git log develop --oneline | grep -q "Merge bugfix/bx into develop"'
 chk "T13c main untouched"            "[ \"\$(git rev-parse main)\" = \"$main_before\" ]"
 chk "T13c bugfix branch deleted"     '! git rev-parse --verify -q refs/heads/bugfix/bx >/dev/null'
 echo "T14 — hook exemption matrix (mixed-block / MERGE_HEAD / root-commit), direct invocation"
 newrepo hookmix; echo a>a; hookon; gitflow_init >/dev/null 2>&1
 git checkout -q main
 echo "console.log(1)" > src.js
 mkdir -p .claude/tasks; echo t > .claude/tasks/t.md
 git add src.js .claude/tasks/t.md
 chk "T14a mixed code+.claude BLOCKED on main" '! git commit -q -m mixed 2>/dev/null'
 newrepo mergehead; echo a>a; hookon; gitflow_init >/dev/null 2>&1
 git checkout -q main
 echo "console.log(1)" > src.js; git add src.js
 touch "$(git rev-parse --git-dir)/MERGE_HEAD"
 chk "T14b MERGE_HEAD exemption allows commit on main" 'git commit -q -m "resolve conflict" 2>/dev/null'
 newrepo root14c
 git symbolic-ref HEAD refs/heads/main   # name the unborn branch 'main' (protected)
 gitflow_install_hook   # write + activate BEFORE any commit (unlike newrepo/hookon)
 echo x > x.txt; git add x.txt
 chk "T14c root commit succeeds hook-active-before-first-commit" 'git commit -q -m root 2>/dev/null'
 echo "T15 — init identity precheck: no identity → rc1, zero mutation"
 d="$WORK/noident"; rm -rf "$d"; mkdir -p "$d"; cd "$d" || exit 1
 git init -q
 echo a > a.txt
 init_rc=0
 GIT_CONFIG_GLOBAL=/dev/null GIT_CONFIG_SYSTEM=/dev/null gitflow_init >/dev/null 2>&1 || init_rc=$?
 chk "T15 rc 1 (identity unset)"    "[ $init_rc -eq 1 ]"
 chk "T15 no develop branch"        '! git rev-parse --verify -q refs/heads/develop >/dev/null'
 chk "T15 unborn HEAD (no commit)"  '! git rev-parse --verify -q HEAD >/dev/null 2>&1'
 chk "T15 hooksPath unset"          '[ -z "$(git config core.hooksPath 2>/dev/null)" ]'
 chk "T15 nothing staged"           '[ -z "$(git diff --cached --name-only)" ]'
 chk "T15 no .gitignore written"    '[ ! -e .gitignore ]'
 chk "T15 no .githooks written"     '[ ! -d .githooks ]'
 echo "T16 — gitleaks pre-commit backstop (job7), independent of branch protection"
 newrepo gl; echo a>a; hookon; gitflow_init >/dev/null 2>&1
 gitflow_start feature glwork >/dev/null 2>&1
 # T16a — a real secret pattern staged on a working branch (not main/develop,
 # 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
 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'
 chk "T16a nothing committed"          '! git log --oneline 2>/dev/null | grep -q "add secret"'
 git restore --staged secret.txt 2>/dev/null || true; rm -f secret.txt
 # T16b — a clean commit is unaffected
 echo clean > clean.txt; git add clean.txt
 chk "T16b clean commit still succeeds" 'git commit -q -m "clean work" 2>/dev/null'
 # 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
 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
 echo "==== RESULT: $PASS passed, $FAIL failed ===="
 [ "$FAIL" -eq 0 ]
@@ -21,7 +21,7 @@ GITFLOW_GITIGNORE_TEMPLATE="${GITFLOW_GITIGNORE_TEMPLATE:-$_GITFLOW_LIB_DIR/../t
 # ── predicates / pure helpers ────────────────────────────────────────────────
-# echo the gitflow type of a branch: feature|bugfix|release|hotfix|main|develop|other
+# echo the gitflow type of a branch: feature|bugfix|release|hotfix|chore|main|develop|other
 gitflow_branch_type() {
  local br="${1:-$(git symbolic-ref --short -q HEAD 2>/dev/null)}"
  case "$br" in
@@ -31,6 +31,7 @@ gitflow_branch_type() {
    bugfix/*)           echo bugfix ;;
    release/*)          echo release ;;
    hotfix/*)           echo hotfix ;;
    chore/*)            echo chore ;;
    *)                  echo other ;;
  esac
 }
@@ -46,7 +47,7 @@ gitflow_protected_base() {
 # echo the base a given type must fork from.
 gitflow_base_for() {
  case "$1" in
-    feature|bugfix|release) echo "$GITFLOW_DEVELOP" ;;
+    feature|bugfix|release|chore) echo "$GITFLOW_DEVELOP" ;;
    hotfix)                 echo "$GITFLOW_MAIN" ;;
    *) echo "gitflow: unknown type '$1'" >&2; return 2 ;;
  esac
@@ -96,14 +97,27 @@ _gitflow_delete() {                # <branch>
  git branch -q -d "$br" || { echo "gitflow: '$br' not fully merged — branch kept" >&2; return 5; }
 }
-# gitflow_finish → directed merge of the CURRENT branch per its type, then delete.
+# gitflow_finish [<type> <name>] → directed merge of the CURRENT branch per its
-# WHEN to call this is the human gate (SKILL.md). This only performs the merge.
+# type, then delete. WHEN to call this is the human gate (SKILL.md).
 #
 # The merge source is ALWAYS the checked-out branch (HEAD) — that is the contract.
 # The optional <type> <name> is a SAFETY ASSERTION, not a target selector: if you
 # name a branch it MUST equal the current one, else finish refuses loudly instead
 # of silently merging whatever you happen to be standing on. (Guards the audit UX
 # trap: `finish bugfix audit-bugs` run from feature/audit-tokens merged the wrong
 # branch — args were silently ignored. See BLK-015 / LRN-089.) No args = unchanged.
 gitflow_finish() {
-  local br type
+  local br type req_type="${1:-}" req_name="${2:-}"
  br="$(git symbolic-ref --short -q HEAD)" || { echo "gitflow_finish: detached HEAD" >&2; return 3; }
  if [ -n "$req_type" ] || [ -n "$req_name" ]; then
    [ "$req_type/$req_name" = "$br" ] || {
      echo "gitflow_finish: operates on the current branch '$br', but you asked '$req_type/$req_name' — checkout '$req_type/$req_name' first (or run finish with no args)." >&2
      return 2
    }
  fi
  type="$(gitflow_branch_type "$br")"
  case "$type" in
-    feature|bugfix)
+    feature|bugfix|chore)
      _gitflow_merge_into "$GITFLOW_DEVELOP" "$br" && _gitflow_delete "$br" ;;
    release)
      _gitflow_merge_into "$GITFLOW_MAIN" "$br" \
@@ -207,6 +221,19 @@ br=\$(git symbolic-ref --short -q HEAD 2>/dev/null)
 git rev-parse --verify -q HEAD >/dev/null 2>&1 || exit 0   # root commit — allow
 [ -f "\$gd/MERGE_HEAD" ] && exit 0                          # merge in progress — allow
 # Secret backstop (job7) — any branch, not just protected ones. Non-blocking
 # if gitleaks isn't installed; auto-discovers ./.gitleaks.toml (repo root).
 if command -v gitleaks >/dev/null 2>&1; then
  if ! gitleaks git --staged --no-banner >/dev/null 2>&1; then
    echo "gitflow pre-commit: BLOCKED — gitleaks found a secret in staged changes." >&2
    echo "  Details: gitleaks git --staged --no-banner" >&2
    echo "  Genuine false-positive? add an allowlist rule to .gitleaks.toml — never bypass with --no-verify." >&2
    exit 1
  fi
 else
  echo "gitflow pre-commit: gitleaks not installed — secret scan skipped (https://github.com/gitleaks/gitleaks)." >&2
 fi
 case "\$br" in
  $GITFLOW_MAIN|$GITFLOW_DEVELOP) ;;                        # protected — keep checking
  *) exit 0 ;;                                              # working branch — allow
@@ -1,20 +1,19 @@
 #!/usr/bin/env bash
 # memory-commit.sh — surgically commit ONLY .claude/memory + .claude/tasks.
 #
-# Used by the dev-flow capitalize step (and, later, the v2 Stop hook) to couple
+# Used by the dev-flow capitalize step to couple the memory commit to the
-# the memory commit to the flow. Safety lives in the PATHSPEC, never in a human
+# flow. Safety lives in the PATHSPEC, never in a human diff review —
-# diff review — automation removes that review, so the scope must be airtight:
+# automation removes that review, so the scope must be airtight: code that
-# code that happens to be dirty or staged is NEVER embarked.
+# happens to be dirty or staged is NEVER embarked.
 #
 # Usage (CLI):
 #   memory-commit.sh pending             # exit 0 if memory/tasks have changes, 1 if clean
 #   memory-commit.sh commit "<message>"  # surgical commit; exit 0 ok/no-op, 3 unsafe state
 #
 # Output contract for `commit`: diagnostics go to stderr; on a real commit the
 # short hash of the MEMORY commit is the ONLY thing on stdout (empty on no-op or
 # unsafe), so callers can capture it: `mem_hash=$(memory-commit.sh commit "msg")`.
 #
-# Sourceable: `memory_pending` and `commit_memory` for the v2 hook.
+# Sourceable: `commit_memory`.
 set -uo pipefail
@@ -47,14 +46,6 @@ _changed_paths() {
  done
 }
 # 0 if something is pending under the scoped paths, 1 if clean / absent.
 memory_pending() {
  _in_git_repo || return 1
  local changed
  mapfile -t changed < <(_changed_paths)
  [ "${#changed[@]}" -gt 0 ]
 }
 # Surgical commit of the scoped paths only. Returns 0 (ok or no-op), 3 (unsafe).
 # On a real commit, prints the memory-commit short hash to stdout (stderr = diag).
 commit_memory() {
@@ -83,20 +74,32 @@ commit_memory() {
  fi
  # Contract: diagnostics go to stderr; on success ONLY the memory-commit short
  # hash goes to stdout, so a caller can do `mem_hash=$(... commit "msg")`.
-  git commit -q -m "$msg" -- "${changed[@]}"
+  # FAIL-LOUD on the commit itself. With `set -uo pipefail` (no -e), a rejected
  # commit (pre-commit hook on a protected branch, signing failure, …) would NOT
  # abort: the line below would falsely claim "committed" and rev-parse would
  # emit the PREVIOUS HEAD's hash with exit 0 — a silent masked failure. Reject
  # → loud, NO hash on stdout, exit 5 (mirrors doc-commit.sh's rc 5).
  if ! git commit -q -m "$msg" -- "${changed[@]}"; then
    {
      echo "memory-commit: COMMIT REJECTED — git commit exited non-zero" \
        "(pre-commit hook? protected branch? signing?)."
      echo "memory-commit: NOTHING committed, working tree left as-is," \
        "NO hash emitted — investigate before retry."
    } >&2
    return 5
  fi
  git rev-parse --short HEAD
 }
 main() {
  local cmd="${1:-}"
  case "$cmd" in
    pending) memory_pending ;;
    commit)
      shift
      commit_memory "${1:-}"
      ;;
    *)
-      echo "usage: memory-commit.sh {pending | commit <message>}" >&2
+      echo "usage: memory-commit.sh commit <message>" >&2
      return 2
      ;;
  esac
@@ -0,0 +1,33 @@
 #!/usr/bin/env bash
 # lib/model-check.sh — classify the persisted session model: big | small | unknown
 #
 # Witness for lib/model-gate.md (reflection requires a big model). Reads the
 # "model" key of the user-scope settings (the file /model rewrites — LRN-098).
 # Override the source with MODEL_CHECK_SETTINGS (tests use fixtures).
 #
 # stdout : <class>:<raw>   (raw = value found, empty if none)
 # exit   : 0 = big (fable/opus) · 2 = small (sonnet/haiku) · 3 = unknown
 set -u
 SETTINGS="${MODEL_CHECK_SETTINGS:-$HOME/.claude/settings.json}"
 raw=""
 if [ -f "$SETTINGS" ]; then
  raw="$(python3 - "$SETTINGS" 2>/dev/null <<'PY'
 import json, sys
 try:
    v = json.load(open(sys.argv[1])).get("model", "")
    print(v if isinstance(v, str) else "")
 except Exception:
    print("")
 PY
 )"
 fi
 norm="$(printf '%s' "$raw" | tr '[:upper:]' '[:lower:]')"
 case "$norm" in
  *opusplan*)       printf 'unknown:%s\n' "$raw"; exit 3 ;; # opus-for-plan, sonnet otherwise — ambiguous
  *fable*|*opus*)   printf 'big:%s\n'     "$raw"; exit 0 ;;
  *sonnet*|*haiku*) printf 'small:%s\n'   "$raw"; exit 2 ;;
  *)                printf 'unknown:%s\n' "$raw"; exit 3 ;;
 esac
@@ -0,0 +1,37 @@
 # Model gate — reflection requires a big model (BLOCKING)
 Shared include. Runs FIRST in any orchestrator whose reflection —
 brainstorming, planning, contract, audit judgment, loop decisions —
 executes inline or in inherit-model subagents. Sonnet-pinned executors are
 not what this gate protects; it protects the thinking around them (BDR-066).
 ## 1. Self-check
 Your system prompt names the model powering this session. Fable or Opus →
 big. Sonnet, Haiku, anything else → small.
 ## 2. Witness — deterministic check
    bash "$HOME/.claude/lib/model-check.sh"
 Output `<class>:<raw>`; exit 0 = big, 2 = small, 3 = unknown. The witness
 reads the PERSISTED model (settings.json — the file `/model` rewrites,
 LRN-098). It can lag reality (session launched with `--model`, settings not
 yet rewritten) — that is why the self-check exists alongside it.
 ## 3. Verdict
 | self-check | witness | action |
 |---|---|---|
 | big | big (0) | proceed, SILENT — the nominal path prints nothing |
 | small | any | **STOP** |
 | big | small (2) | disagreement — **STOP**, surface BOTH values; the user confirms or relaunches |
 | big | unknown (3) | fail-visible: print `model gate: witness unknown (<raw>) — self-check says <model>` and ask the user to confirm before continuing (BDR-025: unknown never silently passes) |
 **STOP means**: print exactly
    ⛔ MODEL GATE — session on <model>. Reflection steps of this skill
    require Fable or Opus. Switch with /model, then relaunch the skill.
 then end the turn. No later step runs, no agent is dispatched, nothing is
 edited.
@@ -42,7 +42,8 @@
 # ============================================================
 set -euo pipefail
-REPO="$(cd -P "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
+REPO="${PROFILE_REPO_OVERRIDE:-$(cd -P "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)}"
 CLAUDE_BIN="${CLAUDE_BIN:-claude}"
 SKILLS_DIR="$REPO/skills"
 DISABLED_DIR="$REPO/skills-disabled"
 GSTACK_SRC="$REPO/skills-external/gstack"  # gstack submodule — source of truth for gstack skills
@@ -201,9 +202,9 @@ skill_status() {
    plugin|plugin@*)
      # `claude plugin list` is the source of truth — settings.json may be
      # ahead of or behind reality if the user toggled outside this tool.
-      if command -v claude >/dev/null 2>&1; then
+      if command -v "$CLAUDE_BIN" >/dev/null 2>&1; then
        # Match the plugin block by name then check Status line
-        if claude plugin list 2>/dev/null \
+        if "$CLAUDE_BIN" plugin list 2>/dev/null \
           | awk -v p="$skill" '
               /^[[:space:]]*❯ '"$skill"'@/ { found=1; next }
               found && /Status:/ { print; exit }
@@ -218,8 +219,8 @@ skill_status() {
      fi
      ;;
    mcp)
-      if command -v claude >/dev/null 2>&1 && \
+      if command -v "$CLAUDE_BIN" >/dev/null 2>&1 && \
-         claude mcp list 2>/dev/null | grep -q "^${skill}"; then
+         "$CLAUDE_BIN" mcp list 2>/dev/null | grep -q "^${skill}"; then
        echo "enabled"
      else
        echo "disabled"
@@ -279,8 +280,8 @@ enable_skill() {
      local marketplace="${type#plugin@}"
      if [ "$(skill_status "$skill" "$type")" = "enabled" ]; then
        : # already on
-      elif command -v claude >/dev/null 2>&1; then
+      elif command -v "$CLAUDE_BIN" >/dev/null 2>&1; then
-        if claude plugin enable "${skill}@${marketplace}" 2>&1 | grep -qiE "enabled|already"; then
+        if "$CLAUDE_BIN" plugin enable "${skill}@${marketplace}" 2>&1 | grep -qiE "enabled|already"; then
          ok "enabled plugin: ${skill}@${marketplace}"
        else
          warn "could not enable plugin: ${skill}@${marketplace}"
@@ -354,8 +355,8 @@ disable_skill() {
      done
      if [ "$(skill_status "$skill" "$type")" = "disabled" ]; then
        : # already off
-      elif command -v claude >/dev/null 2>&1; then
+      elif command -v "$CLAUDE_BIN" >/dev/null 2>&1; then
-        if claude plugin disable "$key" 2>&1 | grep -qiE "disabled|already"; then
+        if "$CLAUDE_BIN" plugin disable "$key" 2>&1 | grep -qiE "disabled|already"; then
          ok "disabled plugin: $key"
        else
          warn "could not disable plugin: $key"
@@ -34,8 +34,9 @@ guard
 learn
 retro
-# Plugin: PR review toolkit (pre-merge audit)
+# pr-review-toolkit removed (audit 2026-07-02 #12 — ~2.2k tokens, PR-only):
-pr-review-toolkit                 plugin@claude-code-plugins
+# enable per PR session via `bash lib/profile.sh apply audit` or
 # claude plugin enable pr-review-toolkit@claude-code-plugins
 # CLIs (advisory)
 ctx7                              cli
@@ -28,6 +28,7 @@ plan-ceo-review
 emil-design-eng                   external
 frontend-design                   external
 design-motion-principles          external
 impeccable                        external
 # Plugin (auto-toggle)
 ui-ux-pro-max                     plugin@ui-ux-pro-max-skill
@@ -78,8 +78,14 @@ guard
 emil-design-eng                   external
 frontend-design                   external
 design-motion-principles          external
 impeccable                        external
 ui-ux-pro-max                     plugin@ui-ux-pro-max-skill
-pr-review-toolkit                 plugin@claude-code-plugins
+# pr-review-toolkit REMOVED from full (audit 2026-07-02 #12): heaviest
 # single plugin cost (~2.2k tokens of agent descriptions/session), useful
 # only when reviewing PRs. Reactivate per PR session:
 #   claude plugin enable pr-review-toolkit@claude-code-plugins
 # or profile-based: bash lib/profile.sh apply audit (audit.profile keeps it;
 # a later `set full` re-disables it — MANAGED_PLUGINS lifecycle).
 magic                             mcp
 # === CLIs (advisory) =================================================
@@ -48,6 +48,7 @@ qa-only
 emil-design-eng                   external
 frontend-design                   external
 design-motion-principles          external
 impeccable                        external
 ui-ux-pro-max                     plugin@ui-ux-pro-max-skill
 magic                             mcp
@@ -36,6 +36,7 @@ web-validate                      personal
 emil-design-eng                   external
 frontend-design                   external
 design-motion-principles          external
 impeccable                        external
 # Plugin: UI/UX intelligence (auto-toggle)
 ui-ux-pro-max                     plugin@ui-ux-pro-max-skill
@@ -0,0 +1,209 @@
 # seo-data — GSC + CrUX data layer for `/seo` FULL audits
 Small, isolated engine that gives the `/seo` skill real Google data instead of
 guesses: **Search Console** (queries, positions, indexation) and **CrUX**
 (Core Web Vitals *field* data — real users, not lab simulation). It knows
 nothing about SEO scoring; it only turns Google APIs into normalized JSON.
 The `seo-analyzer` agent consumes that JSON in STEP 4 (Core Web Vitals) and
 the new "Performance GSC" subsection; the `/seo` skill selects the account
 and property in STEP 0 of a FULL audit (not needed for LOCAL).
 Multi-account by design: the token store is keyed by a user-chosen label, and
 every call takes `--account`/`--property` explicitly. Two audits running at
 the same time (two sites, two sessions) never share mutable state — nothing
 is written to disk during an audit, only at `make seo-connect`.
 ## Setup
 One-time per Google account:
 ```bash
 make seo-connect                                        # from the claude-config repo
 bash ~/.claude/lib/seo-data/connect.sh --label <label>  # from ANY directory (venv must exist)
 ```
 `make seo-connect` creates `~/.claude/.venv-seo-data/` (isolated venv, deps
 pinned in `requirements.txt`), installs `google-auth`,
 `google-auth-oauthlib`, `requests`, then delegates to `connect.sh`. The
 wrapper sources `~/.claude/.env` internally, prefers the venv python, and
 runs `connect.py`: it opens a browser for OAuth consent and takes a
 **label** (e.g. `client-a`) to key the account — pick a name, not an email,
 since the store never stores or requests the account's email. Once the venv
 exists, `connect.sh` alone connects further accounts from anywhere (the
 `/seo connect [label]` skill verb uses exactly this path).
 Before running it, set these 3 keys in `~/.claude/.env` (the canonical
 vault; `link.sh` only symlinks the repo's `.env` to it and warns with a
 `cp .env.example .env` hint if it's missing — it never creates the vault
 itself):
 ```bash
 GOOGLE_OAUTH_CLIENT_ID=<your-client-id>.apps.googleusercontent.com
 GOOGLE_OAUTH_CLIENT_SECRET=<your-client-secret>
 CRUX_API_KEY=<your-crux-api-key>
 ```
 - `GOOGLE_OAUTH_CLIENT_ID` / `GOOGLE_OAUTH_CLIENT_SECRET` — OAuth2 "Desktop
  app" credentials from the Google Cloud Console (APIs & Services →
  Credentials). Shared across every account you connect; the OAuth scope
  requested is `https://www.googleapis.com/auth/webmasters.readonly` only
  — read-only Search Console, nothing can be modified or deleted via this
  token.
 - `CRUX_API_KEY` — a Chrome UX Report API key (restrict it to CrUX +
  PageSpeed in the Console). Get one at
  https://developer.chrome.com/docs/crux/api. No OAuth involved: CrUX is
  public field data, gated by API key only, independent of any connected
  account.
 `make seo-connect` is idempotent and rerunnable — connecting a second
 account just runs it again with a different label; reusing an existing
 label prompts to overwrite.
 ## `fetch.sh` contract
 `lib/seo-data/fetch.sh` is the one stable entrypoint analyzers call. It
 sources `~/.claude/.env`, prefers the isolated venv (falls back to system
 `python3` for stdlib-only paths), dispatches to `google_seo.py` or
 `tokenstore.py`, and never prints a secret to stdout or stderr.
 ```bash
 fetch.sh accounts
  → {"status":"ok","accounts":[{"label":"…","properties":[…],"granted_at":"…"}]}   # [] if none connected
 fetch.sh crux    --url https://ex.com [--strategy mobile|desktop]
  → {"status":"ok","source":"crux","lcp_p75_ms":…,"inp_p75_ms":…,"cls_p75":…}      # a missing metric omits its key
  → {"status":"degraded","reason":"no_crux_key"|"no_field_data"|"rate_limited"}
  # a 404 on page-level data retries at origin-level before degrading
 fetch.sh queries --account client-a --property sc-domain:ex.com [--days 90] [--dim query|page]
  → {"status":"ok","source":"gsc","dimension":"query","rows":[{"key":"…","clicks":…,"impressions":…,"ctr":…,"position":…}]}
  → {"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":"degraded","reason":"…"}
 fetch.sh forget --label client-a
  → {"status":"ok","removed":true|false}          # false = label wasn't in the store
 fetch.sh forget --all
  → {"status":"ok","cleared":<n>}                 # n = accounts removed
 ```
 Rules that hold for every subcommand:
 - **JSON always on stdout, never empty.** Even an unexpected error (HTTP
  403/5xx, timeout, DNS failure) prints
  `{"status":"degraded","reason":"unexpected_error"}` — never a raw
  traceback.
 - **`status` is `"ok"` or `"degraded"` on exit 0; `"error"` on exit 2.**
  Analyzers branch on this field; `"error"` only shows up on bad usage,
  `reason` is informational otherwise.
 - **Exit code 0 on `ok` and on `degraded`.** The engine never fails the
  process just because Google data isn't available — that's a normal,
  expected outcome the analyzer handles by falling back. **Exit code 2**
  is reserved for bad usage: unknown subcommand, missing required flag,
  invalid argument — those paths emit `{"status":"error",...}` instead.
 - **`--store` is accepted uniformly** by every subcommand for consistent
  `fetch.sh` dispatch, even though `crux` ignores it (CrUX needs no
  account).
 - **Never prints a secret.** No env var, refresh token, or access token
  ever reaches stdout or stderr, including in error paths.
 Two env vars exist for testing, never for normal use:
 `SEO_DATA_ENV_FILE` overrides which env file is sourced (tests point it at
 `/dev/null` so a real `~/.claude/.env` on the machine can never leak into a
 test run), and `SEO_DATA_DEBUG=1` re-enables stderr for local debugging
 (stderr is suppressed by default so library warnings can't leak a secret
 into an agent's context).
 ## Token store
 `~/.claude/seo-data/tokens.json` — refresh tokens, keyed by the label chosen
 at `make seo-connect`, one entry per connected account:
 ```json
 {
  "version": 1,
  "accounts": {
    "client-a": {
      "refresh_token": "<opaque>",
      "scopes": ["https://www.googleapis.com/auth/webmasters.readonly"],
      "granted_at": "2026-07-09T12:00:00+00:00",
      "properties": ["sc-domain:site-a.com", "https://www.site-a.com/"]
    }
  }
 }
 ```
 Security posture:
 - **File `0600`, directory `0700`.** `tokenstore.save_account` re-asserts
  both permissions on every write.
 - **Written only at `connect` time, atomically.** `tmp` → `fsync` →
  `os.replace` (atomic rename), under an exclusive `fcntl` lock, so two
  simultaneous `make seo-connect` runs can't corrupt the file. Audits never
  write to this file — access tokens are exchanged in memory and never
  persisted, so two audits running concurrently never contend on it.
 - **Keyed by label, not email.** Identifying accounts by email would
  require widening the OAuth scope just for identification; the label the
  user picks at connect time is sufficient and keeps the scope at
  `webmasters.readonly` only (least privilege).
 - **Refresh tokens are redacted from `list`.** `fetch.sh accounts` (and
  `tokenstore.py list`) return label, properties, and `granted_at` only —
  the `refresh_token` field is intentionally never included in that output.
 - **Allowlisted in gitleaks.** The store lives under `~/.claude/`, outside
  this repo, so it's never committed directly — but `make scan-secrets`
  also sweeps `~/.claude` for stray copies of secrets. `.gitleaks.toml` has
  an explicit `[allowlist].paths` entry for
  `(^|/)\.claude/seo-data/tokens\.json$`, the same treatment
  `~/.claude/.env` already gets, so a legitimate local secret store doesn't
  drown real findings in false positives.
 - **Also gitignored** (`.venv-seo-data/` and `seo-data/tokens.json` in
  `.gitignore`) as a second, belt-and-suspenders guard in case a relative
  path ever put either under the repo tree.
 - **Removal is local-only.** `fetch.sh forget --label <x>` / `--all` (the
  `/seo forget` skill verb) deletes the stored refresh token — it does NOT
  revoke the OAuth grant at Google's end. For a real revocation, visit
  https://myaccount.google.com/permissions with the account concerned and
  remove the app's access; the deleted local token then becomes useless
  everywhere, including to anyone who copied it beforehand.
 ## Graceful degradation
 Missing API key, no connected account, or a revoked/expired token is a
 **normal outcome, not a failure**:
 - No `CRUX_API_KEY` → `crux` returns `{"status":"degraded","reason":"no_crux_key"}`.
 - No account connected, or the store has no refresh token for the given
  `--account` → `queries`/`inspect` return
  `{"status":"degraded","reason":"no_credentials"}`.
 - Refresh token revoked at Google's end → `{"status":"degraded","reason":"token_revoked"}`
  (a transient network blip during refresh is classified
  `"network_error"` instead, so a flaky connection never forces the user
  back through OAuth).
 - Rate limited (HTTP 429) on any Google API → `{"status":"degraded","reason":"rate_limited"}`.
 In every case: **exit code 0**, valid JSON on stdout, no crash. The `/seo`
 FULL audit continues on the anonymous PageSpeed API (lab data) instead of
 CrUX field data, and the report surfaces the fix as a user action:
 `make seo-connect`. `doctor.sh` also flags both non-fatally as `WARN`: a
 missing `CRUX_API_KEY` warns on its own, while no connected Google account
 is the one that names `make seo-connect`.
 ## Testing
 ```bash
 make test
 # or, to run only this engine's suite:
 bash lib/seo-data/seo-data.test.sh
 ```
 The suite is network-free: `google_seo.py` reads fixtures from
 `lib/seo-data/fixtures/` (`crux_mobile.json`, `gsc_queries.json`,
 `gsc_inspect.json`) whenever `SEO_DATA_MOCK_DIR` is set, instead of calling
 Google's APIs. Degradation paths run with real env vars unset (`env -u
 CRUX_API_KEY`, `env -u SEO_DATA_MOCK_DIR`) to exercise the no-key/no-creds
 branches deterministically. Every `fetch.sh` invocation in the tests also
 sets `SEO_DATA_ENV_FILE=/dev/null` so a machine with a live
 `~/.claude/.env` never lets real credentials leak into a test run.
@@ -0,0 +1,57 @@
 #!/usr/bin/env python3
 """One-time OAuth consent + GSC property discovery + persist. Third-party imports
 are lazy so `persist` is testable stdlib-only."""
 import argparse, os, sys
 sys.path.insert(0, os.path.dirname(os.path.abspath(__file__)))
 import tokenstore
 SCOPES = ["https://www.googleapis.com/auth/webmasters.readonly"]
 def run_consent(client_id, client_secret):
    from google_auth_oauthlib.flow import InstalledAppFlow   # lazy
    cfg = {"installed": {"client_id": client_id, "client_secret": client_secret,
            "auth_uri": "https://accounts.google.com/o/oauth2/auth",
            "token_uri": "https://oauth2.googleapis.com/token",
            "redirect_uris": ["http://localhost"]}}
    flow = InstalledAppFlow.from_client_config(cfg, scopes=SCOPES)
    creds = flow.run_local_server(port=0)     # opens browser, one-time consent
    if not creds.refresh_token:
        raise SystemExit("No refresh token returned. Revoke prior grant and retry.")
    return creds.refresh_token
 def discover_properties(refresh_token, client_id, client_secret):
    from google.oauth2.credentials import Credentials
    from google.auth.transport.requests import AuthorizedSession, Request
    creds = Credentials(None, refresh_token=refresh_token, client_id=client_id,
                        client_secret=client_secret,
                        token_uri="https://oauth2.googleapis.com/token", scopes=SCOPES)
    creds.refresh(Request())
    r = AuthorizedSession(creds).get(
        "https://searchconsole.googleapis.com/webmasters/v3/sites", timeout=30)
    r.raise_for_status()
    return [e["siteUrl"] for e in r.json().get("siteEntry", [])]
 def persist(store_path, label, refresh_token, scopes, properties):
    tokenstore.save_account(store_path, label, refresh_token, scopes, properties)
 def _cli():
    p = argparse.ArgumentParser()
    p.add_argument("--label", required=True)
    p.add_argument("--store", default=os.path.expanduser("~/.claude/seo-data/tokens.json"))
    args = p.parse_args()
    cid = os.environ.get("GOOGLE_OAUTH_CLIENT_ID")
    csec = os.environ.get("GOOGLE_OAUTH_CLIENT_SECRET")
    if not (cid and csec):
        raise SystemExit("Set GOOGLE_OAUTH_CLIENT_ID/SECRET in ~/.claude/.env first.")
    existing = {a["label"] for a in tokenstore.list_accounts(args.store)}
    if args.label in existing:
        ans = input("Label '%s' exists. Overwrite? [y/N] " % args.label).strip().lower()
        if ans != "y":
            raise SystemExit("Aborted.")
    rt = run_consent(cid, csec)
    props = discover_properties(rt, cid, csec)
    persist(args.store, args.label, rt, SCOPES, props)
    print("Connected '%s'. Properties: %s" % (args.label, ", ".join(props) or "(none)"))
 if __name__ == "__main__":
    _cli()
@@ -0,0 +1,45 @@
 #!/usr/bin/env bash
 # One-time OAuth consent wrapper — runnable from ANY directory:
 #   bash ~/.claude/lib/seo-data/connect.sh --label <label>
 # Sources the env vault internally (never echoed), prefers the engine venv,
 # then execs connect.py. Interactive by design: stdout carries the auth URL,
 # stderr stays visible (unlike fetch.sh, there is no secret-leak surface to
 # suppress — connect.py never prints tokens).
 set -uo pipefail
 HERE="$(cd "$(dirname "$0")" && pwd)"
 ENV_FILE="${SEO_DATA_ENV_FILE:-${HOME}/.claude/.env}"  # canonical; tests override to /dev/null
 VENV_PY="${HOME}/.claude/.venv-seo-data/bin/python3"
 # Whole-string label guard (shell-safe ASCII: leading alnum then alnum/._-).
 # POSIX `case` in a C-locale subshell: no per-line grep pitfall (a newline is
 # a non-allowed byte caught by *[!...]*), no locale range surprise, no second
 # grammar to differ from. Empty and non-alnum-leading are rejected too.
 _label_safe() ( LC_ALL=C; case "$1" in ''|[!A-Za-z0-9]*|*[!A-Za-z0-9._-]*) exit 1;; esac )
 # Strict argv grammar (parser-differential defense): accept ONLY the exact
 # forms `--label <value>` / `--store <path>` — never `=`-joined or abbreviated
 # forms — so the downstream argparse can never resolve a token this guard
 # didn't see. Runs BEFORE any secret is loaded.
 argv=("$@"); n=${#argv[@]}; i=0
 while [ "$i" -lt "$n" ]; do
  case "${argv[$i]}" in
    --label)
      if ! _label_safe "${argv[$((i+1))]:-}"; then
        echo "connect.sh: unsafe label — must match ^[A-Za-z0-9][A-Za-z0-9._-]*\$" >&2
        exit 2
      fi
      i=$((i+2)) ;;
    --store) i=$((i+2)) ;;
    *)
      echo "connect.sh: unsupported argument '${argv[$i]}' — usage: connect.sh --label <label> [--store <path>]" >&2
      exit 2 ;;
  esac
 done
 # Load secrets quietly (sourced, never echoed).
 if [ -f "$ENV_FILE" ]; then
  set -a; # shellcheck source=/dev/null
  . "$ENV_FILE"; set +a
 fi
 PY="python3"; [ -x "$VENV_PY" ] && PY="$VENV_PY"
 exec "$PY" "$HERE/connect.py" "$@"
@@ -0,0 +1,46 @@
 #!/usr/bin/env bash
 # Stable entrypoint for the seo-data engine. JSON on stdout; exit 0 on ok/degrade,
 # exit 2 on bad usage. Never prints secrets.
 set -uo pipefail
 HERE="$(cd "$(dirname "$0")" && pwd)"
 ENV_FILE="${SEO_DATA_ENV_FILE:-${HOME}/.claude/.env}"  # canonical; tests override to /dev/null
 STORE="${SEO_DATA_STORE:-${HOME}/.claude/seo-data/tokens.json}"
 VENV_PY="${HOME}/.claude/.venv-seo-data/bin/python3"
 # Library stderr must never leak a secret into agent context — suppress it
 # globally unless explicitly debugging (SEO_DATA_DEBUG=1 restores it).
 [ -n "${SEO_DATA_DEBUG:-}" ] || exec 2>/dev/null
 # Load secrets quietly (sourced, never echoed).
 if [ -f "$ENV_FILE" ]; then
  set -a; # shellcheck source=/dev/null
  . "$ENV_FILE"; set +a
 fi
 # Prefer the isolated venv (has google-auth); fall back to system python3 for
 # stdlib-only paths (accounts / mock / degrade).
 PY="python3"; [ -x "$VENV_PY" ] && PY="$VENV_PY"
 # Whole-string label guard (shell-safe ASCII). POSIX `case` in a C-locale
 # subshell — newline-proof and locale-independent, unlike a per-line grep.
 _label_safe() ( LC_ALL=C; case "$1" in ''|[!A-Za-z0-9]*|*[!A-Za-z0-9._-]*) exit 1;; esac )
 cmd="${1:-}"; shift || true
 case "$cmd" in
  accounts) exec "$PY" "$HERE/tokenstore.py" list --file "$STORE" ;;
  crux|queries|inspect)
    exec "$PY" "$HERE/google_seo.py" "$cmd" --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.
    # Label charset guard: store keys stay shell-safe wherever an agent
    # interpolates them into a command line (defense-in-depth vs injection).
    if [ "${1:-}" = "--all" ]; then
      exec "$PY" "$HERE/tokenstore.py" clear --file "$STORE"
    elif [ "${1:-}" = "--label" ] && _label_safe "${2:-}"; then
      exec "$PY" "$HERE/tokenstore.py" remove --file "$STORE" --label "$2"
    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]"}'
     exit 2 ;;
 esac
@@ -0,0 +1,4 @@
 {"record":{"key":{"formFactor":"PHONE"},"metrics":{
  "largest_contentful_paint":{"percentiles":{"p75":2100}},
  "interaction_to_next_paint":{"percentiles":{"p75":180}},
  "cumulative_layout_shift":{"percentiles":{"p75":"0.08"}}}}}
@@ -0,0 +1,2 @@
 {"inspectionResult":{"indexStatusResult":{
  "verdict":"PASS","coverageState":"Submitted and indexed","lastCrawlTime":"2026-07-01T10:00:00Z"}}}
@@ -0,0 +1,3 @@
 {"rows":[
  {"keys":["plombier paris"],"clicks":40,"impressions":900,"ctr":0.044,"position":6.3},
  {"keys":["urgence fuite"],"clicks":5,"impressions":1200,"ctr":0.004,"position":8.9}]}
@@ -0,0 +1,173 @@
 #!/usr/bin/env python3
 """CrUX + GSC fetch → normalized JSON. Third-party imports are LAZY so mock and
 degraded paths run stdlib-only (no venv, no network)."""
 import argparse, json, os, sys
 sys.path.insert(0, os.path.dirname(os.path.abspath(__file__)))
 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, encoding="utf-8") as f:
        return json.load(f)
 def _norm_crux(raw):
    m = raw["record"]["metrics"]
    def p75(metric):
        return m.get(metric, {}).get("percentiles", {}).get("p75")
    out = {"status": "ok", "source": "crux"}
    lcp = p75("largest_contentful_paint")
    inp = p75("interaction_to_next_paint")
    cls = p75("cumulative_layout_shift")
    # Low-traffic origins often miss a metric (INP notably) — omit, don't crash.
    if lcp is not None:
        out["lcp_p75_ms"] = int(lcp)
    if inp is not None:
        out["inp_p75_ms"] = int(inp)
    if cls is not None:
        out["cls_p75"] = float(cls)
    if len(out) == 2:  # no metric at all
        return {"status": "degraded", "reason": "no_field_data"}
    return out
 def _crux_query(key, body):
    import requests  # lazy
    return requests.post(
        "https://chromeuxreport.googleapis.com/v1/records:queryRecord?key=" + key,
        json=body, timeout=20)
 def _origin(url):
    from urllib.parse import urlparse  # stdlib
    p = urlparse(url)
    return "%s://%s" % (p.scheme, p.netloc)  # strip path — CrUX origin = scheme+host only
 def crux(url, strategy="mobile"):
    raw = _mock("crux_%s.json" % strategy)
    if raw is None:
        key = os.environ.get("CRUX_API_KEY")
        if not key:
            return {"status": "degraded", "reason": "no_crux_key"}
        ff = "PHONE" if strategy == "mobile" else "DESKTOP"
        r = _crux_query(key, {"url": url, "formFactor": ff})
        if r.status_code == 404:  # no page-level data → try origin-level
            r = _crux_query(key, {"origin": _origin(url), "formFactor": ff})
        if r.status_code == 404:
            return {"status": "degraded", "reason": "no_field_data"}
        if r.status_code == 429:
            return {"status": "degraded", "reason": "rate_limited"}
        r.raise_for_status()
        raw = r.json()
    return _norm_crux(raw)
 def _gsc_session(store_path, account):
    """Return an authorized requests.Session or a degrade dict. Lazy imports."""
    rt = None
    if store_path and account:
        import tokenstore  # local module, stdlib
        rt = tokenstore.get_refresh_token(store_path, account)
    cid = os.environ.get("GOOGLE_OAUTH_CLIENT_ID")
    csec = os.environ.get("GOOGLE_OAUTH_CLIENT_SECRET")
    if not (rt and cid and csec):
        return {"status": "degraded", "reason": "no_credentials"}
    from google.oauth2.credentials import Credentials       # lazy
    from google.auth.transport.requests import AuthorizedSession, Request
    creds = Credentials(None, refresh_token=rt, client_id=cid, client_secret=csec,
                        token_uri="https://oauth2.googleapis.com/token",
                        scopes=["https://www.googleapis.com/auth/webmasters.readonly"])
    try:
        creds.refresh(Request())
    except Exception as e:
        # Only a real RefreshError means re-consent; a network blip must NOT
        # send the user back through OAuth.
        from google.auth.exceptions import RefreshError  # lazy
        reason = "token_revoked" if isinstance(e, RefreshError) else "network_error"
        return {"status": "degraded", "reason": reason}
    return AuthorizedSession(creds)
 def _norm_queries(raw, dim):
    return {"status": "ok", "source": "gsc", "dimension": dim, "rows": [
        {"key": r["keys"][0], "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"):
    raw = _mock("gsc_queries.json")
    if raw is None:
        sess = _gsc_session(store_path, account)
        if isinstance(sess, dict):
            return sess
        import datetime as _dt
        end = _dt.date.today(); start = end - _dt.timedelta(days=days)
        import urllib.parse
        url = ("https://searchconsole.googleapis.com/webmasters/v3/sites/"
               + urllib.parse.quote(property, safe="") + "/searchAnalytics/query")
        r = sess.post(url, json={"startDate": start.isoformat(), "endDate": end.isoformat(),
                                 "dimensions": [dim], "rowLimit": 100}, 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 inspect(store_path, account, property, url):
    raw = _mock("gsc_inspect.json")
    if raw is None:
        sess = _gsc_session(store_path, account)
        if isinstance(sess, dict):
            return sess
        r = sess.post("https://searchconsole.googleapis.com/v1/urlInspection/index:inspect",
                      json={"inspectionUrl": url, "siteUrl": property}, timeout=30)
        if r.status_code == 429:
            return {"status": "degraded", "reason": "rate_limited"}
        r.raise_for_status()
        raw = r.json()
    isr = raw["inspectionResult"]["indexStatusResult"]
    return {"status": "ok", "source": "gsc",
            "indexed": isr.get("verdict") == "PASS",
            "coverage": isr.get("coverageState"),
            "last_crawl": isr.get("lastCrawlTime")}
 def _cli():
    try:
        p = argparse.ArgumentParser()
        sub = p.add_subparsers(dest="cmd", required=True)
        pc = sub.add_parser("crux")
        pc.add_argument("--url", required=True)
        pc.add_argument("--strategy", default="mobile", choices=["mobile", "desktop"])
        pc.add_argument("--store", default=None)  # accepted+ignored: uniform fetch.sh dispatch
        pq = sub.add_parser("queries")
        pq.add_argument("--store", required=True)
        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")
        pi = sub.add_parser("inspect")
        pi.add_argument("--store", required=True)
        pi.add_argument("--account", required=True)
        pi.add_argument("--property", required=True)
        pi.add_argument("--url", required=True)
        args = p.parse_args()
        if args.cmd == "crux":
            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))
        elif args.cmd == "inspect":
            print(json.dumps(inspect(args.store, args.account, args.property,
                                      args.url), indent=2))
    except SystemExit as e:                       # argparse usage error
        if e.code not in (0, None):
            print(json.dumps({"status": "error", "reason": "bad_usage"}))
        raise                                     # preserve argparse's exit code
    except Exception:
        # Fail-open data contract: ANY unexpected error (HTTP 403/5xx, DNS,
        # timeout) degrades with exit 0 — never a traceback, never empty stdout.
        print(json.dumps({"status": "degraded", "reason": "unexpected_error"}))
 if __name__ == "__main__":
    _cli()
@@ -0,0 +1,3 @@
 google-auth==2.40.0
 google-auth-oauthlib==1.2.2
 requests==2.32.4
@@ -0,0 +1,206 @@
 #!/usr/bin/env bash
 # Deterministic tests for the seo-data engine (no network, no venv).
 set -u
 REPO="$(cd "$(dirname "$0")/../.." && pwd)"
 SD="$REPO/lib/seo-data"
 PASS=0; FAIL=0
 ok()   { echo "  PASS $1"; PASS=$((PASS+1)); }
 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; }
 echo "── tokenstore ──"
 TMP="$(mktemp -d)"; STORE="$TMP/tokens.json"
 python3 "$SD/tokenstore.py" set --file "$STORE" --label client-a \
  --refresh-token RT_AAA --scopes https://www.googleapis.com/auth/webmasters.readonly \
  --properties sc-domain:a.com,https://www.a.com/ >/dev/null
 python3 "$SD/tokenstore.py" set --file "$STORE" --label client-b \
  --refresh-token RT_BBB --scopes https://www.googleapis.com/auth/webmasters.readonly \
  --properties sc-domain:b.com >/dev/null
 LIST="$(python3 "$SD/tokenstore.py" list --file "$STORE")"
 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" = "600" ] && ok "store file is 0600" || no "store file 0600" "got $PERM"
 DPERM="$(stat -c '%a' "$(dirname "$STORE")")"
 [ "$DPERM" = "700" ] && ok "store dir is 0700" || no "store dir 0700" "got $DPERM"
 rm -rf "$TMP"
 echo "── crux (mock) ──"
 CRUX_OK="$(SEO_DATA_MOCK_DIR="$REPO/lib/seo-data/fixtures" \
  python3 "$SD/google_seo.py" crux --url https://ex.com --strategy mobile)"
 has "crux status ok"        "$CRUX_OK" '"status": "ok"'
 has "crux lcp p75 mapped"   "$CRUX_OK" '"lcp_p75_ms": 2100'
 has "crux inp p75 mapped"   "$CRUX_OK" '"inp_p75_ms": 180'
 has "crux cls p75 mapped"   "$CRUX_OK" '"cls_p75": 0.08'
 CRUX_DEG="$(env -u CRUX_API_KEY -u SEO_DATA_MOCK_DIR \
  python3 "$SD/google_seo.py" crux --url https://ex.com)"
 has "crux degrades w/o key" "$CRUX_DEG" '"status": "degraded"'
 has "crux degrade reason"   "$CRUX_DEG" 'no_crux_key'
 ORIG="$(python3 -c "import sys; sys.path.insert(0,'$SD'); import google_seo; print(google_seo._origin('https://example.com/blog/post'))")"
 has   "origin strips to host" "$ORIG" 'https://example.com'
 hasnt "origin drops the path" "$ORIG" 'blog'
 echo "── gsc (mock) ──"
 MOCK="$REPO/lib/seo-data/fixtures"
 TMP2="$(mktemp -d)"; S2="$TMP2/tokens.json"
 python3 "$SD/tokenstore.py" set --file "$S2" --label client-a --refresh-token RT \
  --scopes https://www.googleapis.com/auth/webmasters.readonly --properties sc-domain:ex.com >/dev/null
 Q="$(SEO_DATA_MOCK_DIR="$MOCK" python3 "$SD/google_seo.py" queries \
  --store "$S2" --account client-a --property sc-domain:ex.com --days 90)"
 has "queries ok"                 "$Q" '"status": "ok"'
 has "queries row key"            "$Q" 'plombier paris'
 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'
 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 "── fetch.sh ──"
 FETCH="$SD/fetch.sh"
 # SEO_DATA_ENV_FILE=/dev/null: tests must NEVER source the real ~/.claude/.env —
 # on a machine with a live CRUX_API_KEY the degrade tests would hit the network.
 NOENV=/dev/null
 ACC="$(SEO_DATA_ENV_FILE=$NOENV SEO_DATA_STORE=/nonexistent/tokens.json bash "$FETCH" accounts)"
 has "accounts empty is ok json" "$ACC" '"accounts": []'
 CR="$(SEO_DATA_ENV_FILE=$NOENV SEO_DATA_MOCK_DIR="$MOCK" bash "$FETCH" crux --url https://ex.com)"
 has "fetch crux ok"             "$CR" '"status": "ok"'
 SEO_DATA_ENV_FILE=$NOENV bash "$FETCH" bogus-subcmd >/dev/null 2>&1; RC=$?
 [ "$RC" = "2" ] && ok "bad subcmd exit 2" || no "bad subcmd exit 2" "got $RC"
 DG="$(SEO_DATA_ENV_FILE=$NOENV env -u SEO_DATA_MOCK_DIR -u CRUX_API_KEY bash "$FETCH" crux --url https://ex.com)"; RC=$?
 has "degrade json"              "$DG" '"status": "degraded"'
 [ "$RC" = "0" ] && ok "degrade exit 0" || no "degrade exit 0" "got $RC"
 # redaction through the real fetch.sh dispatch layer
 TMP4="$(mktemp -d)"; RSTORE="$TMP4/rt.json"
 python3 "$SD/tokenstore.py" set --file "$RSTORE" --label leaky --refresh-token RT_SECRET_XYZ \
  --scopes https://www.googleapis.com/auth/webmasters.readonly --properties sc-domain:z.com >/dev/null
 ACCJSON="$(SEO_DATA_ENV_FILE=$NOENV SEO_DATA_STORE="$RSTORE" bash "$FETCH" accounts)"
 has   "accounts lists label"  "$ACCJSON" 'leaky'
 hasnt "accounts hides token"  "$ACCJSON" 'RT_SECRET_XYZ'
 rm -rf "$TMP4"
 # corrupted store must degrade with JSON + exit 0 (Fix 1)
 TMP5="$(mktemp -d)"; CSTORE="$TMP5/corrupt.json"; printf 'not json {{' > "$CSTORE"
 CJ="$(SEO_DATA_ENV_FILE=$NOENV SEO_DATA_STORE="$CSTORE" bash "$FETCH" accounts)"; CRC=$?
 has "corrupt store degrades" "$CJ" '"status"'
 [ "$CRC" = "0" ] && ok "corrupt store exit 0" || no "corrupt store exit 0" "got $CRC"
 rm -rf "$TMP5"
 # bad usage (known subcmd, missing flag) must still emit JSON + exit 2 (Fix 2)
 BU="$(SEO_DATA_ENV_FILE=$NOENV bash "$FETCH" crux)"; BURC=$?
 has "bad usage emits json" "$BU" '"status"'
 [ "$BURC" = "2" ] && ok "bad usage exit 2" || no "bad usage exit 2" "got $BURC"
 echo "── connect (persist, offline) ──"
 TMP3="$(mktemp -d)"; S3="$TMP3/tokens.json"
 python3 -c "import sys; sys.path.insert(0,'$SD'); import connect; \
 connect.persist('$S3','client-x','RT_X',['https://www.googleapis.com/auth/webmasters.readonly'],['sc-domain:x.com'])"
 L3="$(python3 "$SD/tokenstore.py" list --file "$S3")"
 has "connect.persist wrote label" "$L3" '"client-x"'
 has "connect.persist wrote prop"  "$L3" 'sc-domain:x.com'
 hasnt "connect.persist redacts"   "$L3" 'RT_X'
 rm -rf "$TMP3"
 echo "── forget (remove/clear) ──"
 TMP6="$(mktemp -d)"; S6="$TMP6/tokens.json"
 python3 "$SD/tokenstore.py" set --file "$S6" --label keep --refresh-token RT_KEEP \
  --scopes https://www.googleapis.com/auth/webmasters.readonly --properties sc-domain:k.com >/dev/null
 python3 "$SD/tokenstore.py" set --file "$S6" --label drop --refresh-token RT_DROP \
  --scopes https://www.googleapis.com/auth/webmasters.readonly --properties sc-domain:d.com >/dev/null
 RM="$(python3 "$SD/tokenstore.py" remove --file "$S6" --label drop)"
 has   "remove reports ok"        "$RM" '"status": "ok"'
 has   "remove reports removed"   "$RM" '"removed": true'
 hasnt "remove prints no token"   "$RM" 'RT_DROP'
 L6="$(python3 "$SD/tokenstore.py" list --file "$S6")"
 has   "remove keeps others"      "$L6" '"keep"'
 hasnt "removed label gone"       "$L6" '"drop"'
 RM2="$(python3 "$SD/tokenstore.py" remove --file "$S6" --label ghost)"
 has   "remove missing = false"   "$RM2" '"removed": false'
 CL="$(python3 "$SD/tokenstore.py" clear --file "$S6")"
 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" = "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 \
  --scopes https://www.googleapis.com/auth/webmasters.readonly --properties sc-domain:b.com >/dev/null
 FG="$(SEO_DATA_ENV_FILE=$NOENV SEO_DATA_STORE="$S6" bash "$FETCH" forget --label back)"; FRC=$?
 has "fetch forget removes"       "$FG" '"removed": true'
 [ "$FRC" = "0" ] && ok "fetch forget exit 0" || no "fetch forget exit 0" "got $FRC"
 FB="$(SEO_DATA_ENV_FILE=$NOENV SEO_DATA_STORE="$S6" bash "$FETCH" forget)"; FRC2=$?
 has "forget bad usage json"      "$FB" '"status"'
 [ "$FRC2" = "2" ] && ok "forget bad usage exit 2" || no "forget bad usage exit 2" "got $FRC2"
 FA="$(SEO_DATA_ENV_FILE=$NOENV SEO_DATA_STORE="$S6" bash "$FETCH" forget --all)"
 has "fetch forget --all ok"      "$FA" '"status": "ok"'
 FI="$(SEO_DATA_ENV_FILE=$NOENV SEO_DATA_STORE="$S6" bash "$FETCH" forget --label 'x;touch /tmp/pwn')"; FIRC=$?
 has "forget unsafe label json"   "$FI" '"status":"error"'
 [ "$FIRC" = "2" ] && ok "forget unsafe label exit 2" || no "forget unsafe label exit 2" "got $FIRC"
 # embedded-newline label must NOT pass the per-line-grep pitfall
 FN="$(SEO_DATA_ENV_FILE=$NOENV SEO_DATA_STORE="$S6" bash "$FETCH" forget --label "$(printf 'ok\nrm -rf x')")"; FNRC=$?
 has "forget newline label json"  "$FN" '"status":"error"'
 [ "$FNRC" = "2" ] && ok "forget newline label exit 2" || no "forget newline label exit 2" "got $FNRC"
 rm -rf "$TMP6"
 echo "── connect.sh (offline negative) ──"
 CN="$(SEO_DATA_ENV_FILE=$NOENV env -u GOOGLE_OAUTH_CLIENT_ID -u GOOGLE_OAUTH_CLIENT_SECRET \
  bash "$SD/connect.sh" --label t 2>&1)"; CNRC=$?
 [ "$CNRC" != "0" ] && ok "connect.sh no-creds nonzero" || no "connect.sh no-creds nonzero" "got 0"
 has "connect.sh creds gate msg"  "$CN" 'GOOGLE_OAUTH_CLIENT_ID'
 CU="$(SEO_DATA_ENV_FILE=$NOENV bash "$SD/connect.sh" --label 'x;y' 2>&1)"; CURC=$?
 [ "$CURC" = "2" ] && ok "connect.sh unsafe label exit 2" || no "connect.sh unsafe label exit 2" "got $CURC"
 has "connect.sh label guard msg" "$CU" 'unsafe label'
 # parser-differential bypasses must be rejected too (=-joined, abbreviated)
 SEO_DATA_ENV_FILE=$NOENV bash "$SD/connect.sh" --label='x;y' >/dev/null 2>&1; CJRC=$?
 [ "$CJRC" = "2" ] && ok "connect.sh =-joined rejected" || no "connect.sh =-joined rejected" "got $CJRC"
 SEO_DATA_ENV_FILE=$NOENV bash "$SD/connect.sh" --labe 'x;y' >/dev/null 2>&1; CBRC=$?
 [ "$CBRC" = "2" ] && ok "connect.sh abbrev rejected" || no "connect.sh abbrev rejected" "got $CBRC"
 SEO_DATA_ENV_FILE=$NOENV bash "$SD/connect.sh" --label "$(printf 'ok\nrm -rf x')" >/dev/null 2>&1; CWRC=$?
 [ "$CWRC" = "2" ] && ok "connect.sh newline rejected" || no "connect.sh newline rejected" "got $CWRC"
 # a VALID label must still reach the creds gate (guard is not over-tight)
 CV="$(SEO_DATA_ENV_FILE=$NOENV env -u GOOGLE_OAUTH_CLIENT_ID -u GOOGLE_OAUTH_CLIENT_SECRET \
  bash "$SD/connect.sh" --label ok-1.2_3 2>&1)"; CVRC=$?
 [ "$CVRC" = "1" ] && ok "connect.sh valid label reaches gate" || no "connect.sh valid label reaches gate" "got $CVRC"
 has "connect.sh valid gate msg"  "$CV" 'GOOGLE_OAUTH_CLIENT_ID'
 echo "── wiring locks ──"
 tf() { if grep -qF -- "$3" "$2" 2>/dev/null; then ok "$1"; else no "$1" "missing: $3"; fi; }
 tf "env.example client id"    "$REPO/.env.example"    "GOOGLE_OAUTH_CLIENT_ID="
 tf "env.example crux key"     "$REPO/.env.example"    "CRUX_API_KEY="
 tf "makefile seo-connect"     "$REPO/Makefile"        "seo-connect:"
 tf "makefile delegates wrapper" "$REPO/Makefile"      "lib/seo-data/connect.sh"
 tf "connect.sh sources vault" "$SD/connect.sh"        ".claude/.env"
 tf "makefile discovers test"  "$REPO/Makefile"        "lib/seo-data/*.test.sh"
 tf "install prompts connect"  "$REPO/install.sh"      "make seo-connect"
 tf "doctor checks seo-data"   "$REPO/doctor.sh"       "seo-data"
 tf "gitleaks allowlist store" "$REPO/.gitleaks.toml"  "seo-data/tokens"
 tf "gitignore venv"           "$REPO/.gitignore"      ".venv-seo-data"
 echo "── integration locks ──"
 tf "skill step0 account select" "$REPO/skills/seo/SKILL.md"      "COMPTE GOOGLE"
 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"
 echo "── account-mgmt locks ──"
 tf "skill routes account verbs" "$REPO/skills/seo/SKILL.md" "forget --all"
 tf "skill connect wrapper path" "$REPO/skills/seo/SKILL.md" "lib/seo-data/connect.sh"
 tf "skill revocation notice"    "$REPO/skills/seo/SKILL.md" "myaccount.google.com/permissions"
 tf "skill label charset rule"   "$REPO/skills/seo/SKILL.md" "A-Za-z0-9._-"
 echo "── readme lock ──"
 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"
 echo ""
 echo "seo-data engine: $PASS pass, $FAIL fail"
 [ "$FAIL" -eq 0 ]
@@ -0,0 +1,121 @@
 #!/usr/bin/env python3
 """Label-keyed OAuth refresh-token store. Atomic writes under an fcntl lock.
 No third-party deps — must run without the venv (used by the offline test path)."""
 import argparse, fcntl, json, os, tempfile
 from contextlib import contextmanager
 from datetime import datetime, timezone
 def load(path):
    if not os.path.exists(path):
        return {"version": 1, "accounts": {}}
    with open(path, "r", encoding="utf-8") as f:
        return json.load(f)
 def list_accounts(path):
    data = load(path)
    return [
        {"label": lbl, "properties": a.get("properties", []),
         "granted_at": a.get("granted_at")}
        for lbl, a in data.get("accounts", {}).items()
    ]  # refresh_token intentionally omitted (redaction)
 def get_refresh_token(path, label):
    return load(path).get("accounts", {}).get(label, {}).get("refresh_token")
@contextmanager
 def _locked(path):
    """Exclusive fcntl lock around a store mutation (serializes writers)."""
    lock_path = path + ".lock"
    with open(lock_path, "w") as lock:
        os.chmod(lock_path, 0o600)                 # defense-in-depth (empty flock handle, never holds token)
        fcntl.flock(lock, fcntl.LOCK_EX)
        yield
 def _atomic_write(path, data):
    """tmp → fsync → chmod 0600 → atomic rename, in the store's directory."""
    dirpath = os.path.dirname(path) or "."
    fd, tmp = tempfile.mkstemp(dir=dirpath, suffix=".tmp")
    try:
        with os.fdopen(fd, "w", encoding="utf-8") as f:
            json.dump(data, f, indent=2)
            f.flush(); os.fsync(f.fileno())
        os.chmod(tmp, 0o600)
        os.replace(tmp, path)                     # atomic
    finally:
        if os.path.exists(tmp):
            os.unlink(tmp)
 def save_account(path, label, refresh_token, scopes, properties):
    dirpath = os.path.dirname(path) or "."
    os.makedirs(dirpath, mode=0o700, exist_ok=True)
    os.chmod(dirpath, 0o700)                       # re-assert invariant (makedirs no-ops if dir exists)
    with _locked(path):
        data = load(path)
        data.setdefault("version", 1)
        data.setdefault("accounts", {})
        data["accounts"][label] = {
            "refresh_token": refresh_token,
            "scopes": scopes,
            "granted_at": datetime.now(timezone.utc).isoformat(),
            "properties": properties,
        }
        _atomic_write(path, data)
 def remove_account(path, label):
    """Drop one label from the store. Returns True if it existed."""
    if not os.path.exists(path):
        return False
    with _locked(path):
        data = load(path)
        existed = data.get("accounts", {}).pop(label, None) is not None
        if existed:
            _atomic_write(path, data)
    return existed
 def clear_accounts(path):
    """Empty the store (file and perms kept). Returns removed count."""
    if not os.path.exists(path):
        return 0
    with _locked(path):
        data = load(path)
        count = len(data.get("accounts", {}))
        _atomic_write(path, {"version": 1, "accounts": {}})
    return count
 def _cli():
    p = argparse.ArgumentParser()
    sub = p.add_subparsers(dest="cmd", required=True)
    pl = sub.add_parser("list"); pl.add_argument("--file", required=True)
    ps = sub.add_parser("set")
    for flag in ("--file", "--label", "--refresh-token"):
        ps.add_argument(flag, required=True)
    ps.add_argument("--scopes", default="")
    ps.add_argument("--properties", default="")
    pr = sub.add_parser("remove")
    for flag in ("--file", "--label"):
        pr.add_argument(flag, required=True)
    pc = sub.add_parser("clear"); pc.add_argument("--file", required=True)
    try:
        args = p.parse_args()
        if args.cmd == "list":
            print(json.dumps({"status": "ok", "accounts": list_accounts(args.file)}))
        elif args.cmd == "remove":
            print(json.dumps({"status": "ok",
                              "removed": remove_account(args.file, args.label)}))
        elif args.cmd == "clear":
            print(json.dumps({"status": "ok",
                              "cleared": clear_accounts(args.file)}))
        else:
            save_account(args.file, args.label, getattr(args, "refresh_token"),
                         [s for s in args.scopes.split(",") if s],
                         [x for x in args.properties.split(",") if x])
            print(json.dumps({"status": "ok"}))
    except SystemExit as e:                       # argparse usage error
        if e.code not in (0, None):
            print(json.dumps({"status": "error", "reason": "bad_usage"}))
        raise                                     # preserve argparse's exit code
    except Exception:                             # e.g. corrupted store JSON
        print(json.dumps({"status": "degraded", "reason": "unexpected_error"}))
 if __name__ == "__main__":
    _cli()
@@ -0,0 +1,74 @@
 #!/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 ]
@@ -0,0 +1,87 @@
 #!/usr/bin/env bash
 # ============================================================
 # Structure locks — contract/verifier pair (verify-loops lot 2)
 # Deterministic greps on load-bearing doctrine clauses: an edit
 # that silently drops one (blind verifier, PROOF mandatory,
 # immutable REQUEST, micro-gate scope enrichment…) reds here.
 # ============================================================
 set -u
 REPO="$(cd "$(dirname "$0")/../.." && pwd)"
 LIB="$REPO/lib/contract-interview.md"
 AGT="$REPO/agents/verifier.md"
 PASS=0; FAIL=0
 # Fixed-string lock (UTF-8 punctuation safe)
 tf() { # tf <label> <file> <fixed-string>
  if grep -qF -- "$3" "$2" 2>/dev/null; then
    echo "  PASS $1"; PASS=$((PASS+1))
  else
    echo "  FAIL $1 — missing: $3"; FAIL=$((FAIL+1))
  fi
 }
 # Regex lock
 tr_() { # tr_ <label> <file> <ERE>
  if grep -qE -- "$3" "$2" 2>/dev/null; then
    echo "  PASS $1"; PASS=$((PASS+1))
  else
    echo "  FAIL $1 — no match: $3"; FAIL=$((FAIL+1))
  fi
 }
 # Negative lock — pattern must NOT match
 tn() { # tn <label> <file> <ERE>
  if grep -qE -- "$3" "$2" 2>/dev/null; then
    echo "  FAIL $1 — forbidden match: $3"; FAIL=$((FAIL+1))
  else
    echo "  PASS $1"; PASS=$((PASS+1))
  fi
 }
 echo "── contract-interview.md locks ──"
 if [ -f "$LIB" ]; then
  echo "  PASS lib exists"; PASS=$((PASS+1))
 else
  echo "  FAIL lib missing: $LIB"; FAIL=$((FAIL+1))
 fi
 tf  "verbatim request immutable"      "$LIB" "REQUEST (verbatim — IMMUTABLE)"
 tf  "contracts dir committed path"    "$LIB" ".claude/tasks/contracts/"
 tf  "unique per-run slug"             "$LIB" "<YYYY-MM-DD>-<slug>-<HHMM>"
 tf  "silent when complete"            "$LIB" "ZERO questions"
 tf  "question budget"                 "$LIB" "max 3 questions"
 tf  "aborted status"                  "$LIB" "status: aborted"
 tf  "never left dirty"                "$LIB" "NEVER left dirty"
 tf  "scope enrichment micro-gate"     "$LIB" "micro-gate"
 tf  "gated marker"                    "$LIB" "[gated <YYYY-MM-DD>]"
 tf  "main-loop only"                  "$LIB" "ORCHESTRATOR MAIN LOOP"
 tf  "re-scope supersedes"             "$LIB" "supersedes:"
 tf  "hand-off = path not content"     "$LIB" "contract PATH, not a restatement"
 echo "── verifier.md locks ──"
 if [ -f "$AGT" ]; then
  echo "  PASS agent exists"; PASS=$((PASS+1))
 else
  echo "  FAIL agent missing: $AGT"; FAIL=$((FAIL+1))
 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  "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\`"
 tf  "proof mandatory"                 "$AGT" "\`PROOF\` is MANDATORY"
 tf  "contract read from disk"         "$AGT" "READ it from disk"
 tf  "checked count equality"          "$AGT" "checked count in"
 tf  "report-only"                     "$AGT" "Report-only. Never edit"
 tf  "bash observation only"           "$AGT" "OBSERVATION ONLY"
 tf  "loop bound"                      "$AGT" "Max 3 iterations"
 tf  "structural retry then escalate"  "$AGT" "2nd structural failure"
 tf  "mute never a pass"               "$AGT" "A mute verifier is NEVER a PASS"
 tf  "conforme first pass no loop"     "$AGT" "proceed straight to the security gate"
 tf  "reverify order request first"    "$AGT" "re-verify the request FIRST"
 echo ""
 echo "contract-verifier structure locks: $PASS pass, $FAIL fail"
 [ "$FAIL" -eq 0 ]
@@ -0,0 +1,81 @@
 #!/usr/bin/env bash
 # lib/tests/curated-config-guard.test.sh — SPEC-03 (J4-03).
 #
 # Drives install-plugins.sh's restore_curated_configs() in a sandbox. The SUT
 # is extracted from the REAL script AT TEST RUNTIME (awk range, verified
 # single-occurrence + column-0 closing brace) so drift in install-plugins.sh
 # propagates into this test instead of testing a stale copy. GUARDED_CONFIGS,
 # CFG_SNAPSHOT, REPO and an info() stub are defined here — the array literal
 # at install-plugins.sh:43-44 is outside the extracted range.
 set -u
 INSTALL_SH="$(cd "$(dirname "$0")/../.." && pwd)/install-plugins.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; }
 SUT="$(mktemp)"
 awk '/^restore_curated_configs\(\) \{/,/^\}/' "$INSTALL_SH" > "$SUT"
 REPO="$(mktemp -d)"
 CFG_SNAPSHOT="$(mktemp -d)"
 EXPECT="$(mktemp -d)"          # our own reference copy — independent of CFG_SNAPSHOT (SUT rm -rf's it)
 GUARDED_CONFIGS=("CLAUDE.md" "CLAUDE.global.md" ".claude/settings.json" "settings.json")
 info() { :; }                 # stub — extracted body calls info(), irrelevant to the assertions
 mkdir -p "$REPO/.claude"
 printf 'CLAUDE original\n'        > "$REPO/CLAUDE.md"
 printf 'CLAUDE.global original\n' > "$REPO/CLAUDE.global.md"
 printf '{"a":1}\n'                > "$REPO/.claude/settings.json"
 printf '{"b":2}\n'                > "$REPO/settings.json"
 for f in "${GUARDED_CONFIGS[@]}"; do
  mkdir -p "$CFG_SNAPSHOT/$(dirname "$f")" "$EXPECT/$(dirname "$f")"
  cp "$REPO/$f" "$CFG_SNAPSHOT/$f"
  cp "$REPO/$f" "$EXPECT/$f"
 done
 # simulate installer drift: mutate ONE guarded file, leave the other three alone
 printf 'CLAUDE CLOBBERED BY INSTALLER\n' > "$REPO/CLAUDE.md"
 # shellcheck source=/dev/null
 source "$SUT"
 restore_curated_configs
 cmp -s "$REPO/CLAUDE.md" "$EXPECT/CLAUDE.md"
 check T1-mutated-file-restored "$?" 0
 cmp -s "$REPO/CLAUDE.global.md" "$EXPECT/CLAUDE.global.md"
 check T2-untouched-global-md-unchanged "$?" 0
 cmp -s "$REPO/.claude/settings.json" "$EXPECT/.claude/settings.json"
 check T3-untouched-local-settings-unchanged "$?" 0
 cmp -s "$REPO/settings.json" "$EXPECT/settings.json"
 check T4-untouched-settings-unchanged "$?" 0
 if [ -d "$CFG_SNAPSHOT" ]; then r5=present; else r5=gone; fi
 check T5-snapshot-dir-removed "$r5" gone
 # --- T6: mktemp failure -> fail-closed (install-plugins.sh, the header block
 # that builds CFG_SNAPSHOT) — refuses to run unguarded instead of warning and
 # continuing. Extracted with a WIDER range than the SUT above: this logic
 # lives in the top-level if/else, outside restore_curated_configs().
 SUT2="$(mktemp)"
 awk '/^GUARDED_CONFIGS=/,/^fi$/' "$INSTALL_SH" > "$SUT2"
 ERR6="$(mktemp)"
 (
  # shellcheck disable=SC2329  # invoked indirectly by the sourced snippet below
  mktemp() { return 1; }   # force the header's CFG_SNAPSHOT creation to fail
  # shellcheck disable=SC2329
  err() { echo "ERR: $*" >&2; }
  # shellcheck disable=SC2329
  warn() { echo "WARN: $*" >&2; }
  # shellcheck disable=SC2329
  info() { :; }
  REPO="$(command mktemp -d)"
  # shellcheck source=/dev/null
  source "$SUT2"
 ) >/dev/null 2>"$ERR6"
 rc6=$?
 check T6-mktemp-failure-aborts "$rc6" 1
 if grep -qi 'mktemp failed' "$ERR6"; then r6msg=yes; else r6msg=no; fi
 check T6-mktemp-failure-loud "$r6msg" yes
 rm -f "$ERR6" "$SUT2"
 printf 'PASS=%s FAIL=%s\n' "$pass" "$fail"; [ "$fail" -eq 0 ]
@@ -50,4 +50,13 @@ printf 'run\n' >"$d/.claude/deploy/PROCEDURE.md"
 ( cd "$d" && bash "$H" commit "docs(deploy): t" .claude/deploy/PROCEDURE.md ) >/dev/null 2>&1
 check T9-ignored-rc "$?" 5
 d=$(mkrepo); printf '#!/bin/sh\nexit 1\n' >"$d/.git/hooks/pre-commit"; chmod +x "$d/.git/hooks/pre-commit"
 BEFORE=$(git -C "$d" rev-parse --short HEAD)
 printf 'run\n' >"$d/.claude/deploy/PROCEDURE.md"
 OUT=$( ( cd "$d" && bash "$H" commit "docs(deploy): t" .claude/deploy/PROCEDURE.md ) 2>/dev/null ); RC=$?
 AFTER=$(git -C "$d" rev-parse --short HEAD)
 check T10-rejected-rc "$RC" 6
 check T10-rejected-no-hash "$([ -z "$OUT" ] && echo empty || echo "$OUT")" empty
 check T10-rejected-head-unmoved "$BEFORE" "$AFTER"
 printf 'PASS=%s FAIL=%s\n' "$pass" "$fail"; [ "$fail" -eq 0 ]
@@ -0,0 +1,43 @@
 #!/usr/bin/env bash
 # lib/tests/design-toolchain-reminder.test.sh
 set -u
 H="$(cd "$(dirname "$0")/../.." && pwd)/hooks/design-toolchain-reminder.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; }
 # fire() -> "fire" if the hook emits the reminder, else "quiet".
 fire() { if printf '{"prompt":"%s"}' "$1" | bash "$H" | grep -q 'full toolchain'; then
  echo fire; else echo quiet; fi; }
 # --- Dropped/neutralized tokens must be QUIET (non-UI senses) ---
 check D1-design      "$(fire 'a design decision for the API')" quiet
 check D2-component   "$(fire 'this system component')"         quiet
 check D3-composant   "$(fire 'le composant backend')"          quiet
 check D4-theme       "$(fire 'the theme of the audit')"        quiet
 check D5-transition  "$(fire 'state transition to develop')"   quiet
 check D6-frontend    "$(fire 'frontend architecture')"         quiet
 check D7-palette     "$(fire 'a palette of options')"          quiet
 check D8-dash-file   "$(fire 'ecc_dashboard.py')"              quiet
 # --- Harness-generated inputs must be QUIET even with UI tokens ---
 check D9-tasknotif   "$(fire '<task-notification> <task-id>x</task-id> add css header fonts')" quiet
 check D10-notif-file "$(fire '<task-notification> design-motion-principles keyframe done')"    quiet
 # --- Real UI signals must still FIRE ---
 check F1-button      "$(fire 'add a button')"            fire
 check F2-navbar      "$(fire 'the navbar layout')"       fire
 check F3-landing     "$(fire 'build a landing page')"    fire
 check F4-glass       "$(fire 'a glassmorphism card')"    fire
 check F5-redesign    "$(fire 'redesign the app')"        fire
 check F6-frontdesign "$(fire 'frontend design work')"    fire
 check F7-admin-dash  "$(fire 'admin dashboard screen')"  fire
 check F8-animation   "$(fire 'add an animation')"        fire
 check F9-designsys   "$(fire 'our design system')"       fire
 # --- Fire is logged (time + token + excerpt) ---
 tmp="$(mktemp -d)"
 printf '{"prompt":"a glassmorphism card"}' | HOME="$tmp" bash "$H" >/dev/null 2>&1
 check L1-logged "$(grep -c 'glassmorph' "$tmp/.claude/logs/design-toolchain-fires.log" 2>/dev/null)" 1
 rm -rf "$tmp"
 printf 'PASS=%s FAIL=%s\n' "$pass" "$fail"; [ "$fail" -eq 0 ]
@@ -0,0 +1,192 @@
 ---
 type: blockers_registry
 entry_prefix: BLK
 schema:
  id: BLK-XXX
  date: YYYY-MM-DD
  friction: string (what was blocked)
  real_cause: string (root cause, not symptom)
  solution: string (workaround or fix)
  status: [open | resolved | upstream]
 rules:
  - Open blocker when friction > 15 min wasted. Close with real cause, not "moved on".
  - Link upstream issue / PR / commit when applicable.
  - Cause is bug in dependency → status upstream with pointer to tracker.
 ---
 # Blockers registry (BLK)
 ## Index
 | ID | Date | Friction | Status |
 |----|------|---------|--------|
 | BLK-001 | 2026-04-22 | `rtk curl` breaks JSON pipelines | upstream |
 | BLK-002 | 2026-04-23 | `rmdir` denied in sandbox on empty directory | resolved |
 | BLK-003 | 2026-05-12 | `scripts/screenshot.mjs` hardcoded macOS path blocks PNG cards on Linux | upstream |
 | BLK-004 | 2026-05-20 | `/ship-feature` wrapper at `~/.claude/commands/` points to deleted agent files post-refactor | resolved |
 | BLK-005 | 2026-05-21 | gstack submodule rename (checkpoint→context-save) breaks profile entries | resolved |
 | BLK-006 | 2026-05-21 | `profile.sh current` false-negative via `~/.claude` symlink (`cd` not `cd -P`) | resolved |
 | BLK-007 | 2026-06-02 | 6 gstack source skills (ios-*, spec) unlinked post-bump — invisible to profiles + `gstack on` | resolved |
 | BLK-008 | 2026-06-23 | gstack ./setup on Ubuntu 26.04: Playwright chromium unsupported → gstack browser (/browse, /qa, screenshots) silently dead | resolved (211c7d4) |
 | BLK-009 | 2026-06-25 | user-level path-scoped rules (`paths:` frontmatter in `~/.claude/rules/`) never inject — broken in CC 2.1.190 (#21858) | resolved (2026-07-06) |
 | BLK-010 | 2026-06-27 | init-project: scaffold (STEP 5) + bootstrap README (5b) have no deterministic commit owner; worktree `add -b` on unborn HEAD | resolved (uncommitted) |
 | BLK-011 | 2026-06-27 | init-project STEP 13 GSD post-FINISH creates ROADMAP.md → stranded doc (3rd post-FINISH artifact) | resolved (STEP 12 removed) |
 | BLK-012 | 2026-06-29 | gitflow_init half-applied: socle-commit failure swallowed → hook activated on partial run → re-run self-blocks | resolved |
 | BLK-013 | 2026-06-30 | `make plugin` Error 127 — npm absent on apt-`nodejs` host (Step 4 gsd-pi aborts, Steps 5-10 + residual cleanup never run) | resolved (env) |
 | 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-001 — `rtk curl` returns compressed schema in pipes
 - **Date**: 2026-04-22
 - **Friction**: pipelines like `rtk curl ... | python -c "json.load(sys.stdin)"` (or `jq`, `awk`) fail without clear error.
 - **Real cause**: `rtk curl` auto-compresses stdout regardless of TTY — documented in `.claude/tasks/rtk-upstream-issue.md`.
 - **Solution**:
  - Short-term workaround: `exclude_commands=["curl"]` in `~/.config/rtk/config.toml`.
  - Alternative workaround: use `rtk proxy`.
  - Upstream fix: issue reported, see `.claude/tasks/rtk-upstream-issue.md`.
 - **Status**: upstream (`rtk` bug, workaround applied).
 ## BLK-002 — `rmdir` denied in sandbox on empty directory
 - **Date**: 2026-04-23
 - **Friction**: couldn't delete `./tasks/` after emptying (post-migration to `.claude/tasks/`). `rmdir tasks` and `rm -r tasks` returned "Permission denied" even with empty dir and non-destructive intent.
 - **Real cause**: Claude Code sandbox blocks destructive commands (`rm`, `rmdir`, `rm -rf`) by default via harness permission gate, regardless of actual semantics. `git rm` through `git` passed (commit `c721a36`) — git treated as non-destructive tool.
 - **Solution**:
  - This session: `git rm tasks/*.md` handled files individually (via `git rm`, cleared gate). Git auto-detected renames to `.claude/tasks/`, so `tasks/` directory removed implicitly at commit time.
  - If dir persists empty after `git rm`: ask user to run `rmdir tasks` manually.
 - **Status**: resolved (fixed via `git rm` + rename auto-detection; no `rmdir` needed in practice).
 ## BLK-003 — `scripts/screenshot.mjs` hardcoded macOS path blocks PNG cards on Linux
 - **Date**: 2026-05-12
 - **Friction**: `/darwin-skill` Phase 3 generates result cards via `node ~/.agents/skills/darwin-skill/scripts/screenshot.mjs <html> <png>`. On Linux: script fails immediately — `require('/Users/alchain/.npm-global/lib/node_modules/playwright/node_modules/playwright-core')` resolves to a non-existent macOS user path. No PNG cards produced; Phase 3 falls back to markdown report only.
 - **Real cause**: upstream `alchaincyf/darwin-skill` author dev'd on macOS, shipped absolute path to their own homedir's global npm install of playwright. Zero portability layer (no PATH lookup, no `playwright` bare require, no fallback to `npx`).
 - **Solution**:
  - Workaround (used 2026-05-12): skip PNG generation, deliver markdown + HTML cards (HTML viewable in browser without playwright).
  - Local patch: `npm i -g playwright` then replace `require('/Users/alchain/...')` with `require('playwright')`. Two lines edit.
  - Spec-documented fallback: `npx playwright screenshot "file:///path/to/card.html#<theme>" out.png --viewport-size=960,1280 --wait-for-timeout=2000` — works without modifying the file, costs ~150MB chromium download.
  - PR upstream to `github.com/alchaincyf/darwin-skill` once tested.
 - **Status**: upstream (third-party skill at `~/.agents/skills/darwin-skill/scripts/screenshot.mjs`, not in any of our repos).
 ## BLK-004 — `/ship-feature` wrapper references 6 deleted agent files
 - **Date**: 2026-05-20
 - **Friction**: `/ship-feature` invocation loads wrapper at `~/.claude/commands/ship-feature.md`. Wrapper says `Load and follow strictly: .claude/agents/{ship-feature,analyzer,designer,implementer,reviewer,tester}.md`. 5 of 6 paths missing on disk (only `analyzer.md` survives). User hits blocker — wrapper without orchestrator.
 - **Real cause**: refactor commits `0241e1d` ("extract skill logic into standalone agent files") + `21960e0` ("changed orchestrators into skills") migrated orchestrator from `.claude/agents/ship-feature.md` into `~/.claude/skills/ship-feature/SKILL.md` and replaced custom sub-agents (designer/implementer/reviewer/tester) with superpowers skills (brainstorming, writing-plans, subagent-driven-development, requesting-code-review, finishing-a-development-branch). Wrapper at `~/.claude/commands/ship-feature.md` never updated, never deleted. Untracked file — survived all refactor commits silently.
 - **Solution**: `rm ~/.claude/commands/ship-feature.md`. Skill `~/.claude/skills/ship-feature/SKILL.md` (`name: ship-feature`, `disable-model-invocation: true`) becomes sole `/ship-feature` resolver. SKILL.md references only existing agents: `plugin-advisor.md`, `analyzer.md`, `doc-syncer.md`.
 - **Status**: resolved.
 ## BLK-005 — `/profile set full` warns `missing: checkpoint` after gstack upstream rename
 - **Date**: 2026-05-21
 - **Friction**: `/profile set full` (and dev, backend, web, web-full) emits `⚠ missing: checkpoint — try: bash link.sh`. Running `bash link.sh` reports `✅ All symlinks already up to date. Next: bash install-plugins.sh` — dead-end loop. User cannot resolve the warning by following the suggested next step.
 - **Real cause**: gstack upstream renamed the `checkpoint` skill to `context-save` (Claude Code now treats `/checkpoint` as a native rewind alias, shadowing the gstack skill). New skill in `skills-external/gstack/context-save/SKILL.md` carries the description `"Formerly /checkpoint — renamed because Claude Code treats /checkpoint as a native rewind alias"`. Five `lib/profiles/*.profile` files still listed the dead name. `link.sh` only symlinks repo dirs into `~/.claude/` — it cannot materialize a skill that no longer exists upstream, so its suggested action was misleading.
 - **Solution**: `s/checkpoint/context-save/` in `lib/profiles/{dev,backend,full,web,web-full}.profile` (commit `69c5ded`). `CLAUDE.md:193` routing line `Save progress, checkpoint, resume → invoke context-save` updated locally, left uncommitted because the file holds unrelated in-progress graphify section work. Verify: `bash lib/profile.sh set full` now outputs `✓ enabled: context-save` with no warning.
 - **Status**: resolved.
 ## BLK-006 — `bash lib/profile.sh current` false-negative when invoked via `~/.claude/lib/` symlink
 - **Date**: 2026-05-21
 - **Friction**: `bash "$HOME/.claude/lib/profile.sh" current` returns `none (all gstack skills enabled — no profile set)` even when a profile IS applied + 14 `gstack__*` entries sit in the repo's `skills-disabled/`. User cannot detect active profile via the official command. Same script invoked from inside the repo directory (`bash lib/profile.sh current`) returns the correct answer — invocation-path-dependent behavior is the worst kind of bug to diagnose.
 - **Real cause**: `lib/profile.sh:43` set `REPO="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"`. Default bash `cd` preserves symlinks (logical pathname mode, `set -P` off). When the script is invoked via the `~/.claude/lib/profile.sh` symlink (link.sh wires `~/.claude/lib -> <repo>/lib`), `$BASH_SOURCE[0]` is the symlinked path, `dirname` returns `~/.claude/lib`, `cd ..` lands at `~/.claude`, and `pwd` returns the logical path `/home/bchanot-ubuntu/.claude`. `$SKILLS_DIR="$REPO/skills"` still works because `~/.claude/skills` happens to be a symlink to the repo's `skills/`. But `$DISABLED_DIR="$REPO/skills-disabled"` resolves to `~/.claude/skills-disabled` — a real sibling directory created at some earlier point containing only 2 stale npx-skill symlinks (`darwin-skill`, `find-skills`). `cmd_current` scans this near-empty dir, finds 0 `gstack__*` entries, returns the "none" sentinel.
 - **Solution**: `REPO="$(cd -P "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"` (commit `a4558ee`). `-P` forces physical-path resolution so `$REPO` is always the real repo path regardless of how the script is invoked. Verify: `bash "$HOME/.claude/lib/profile.sh" current` now returns `full (100% match, 14 gstack skills disabled)`.
 - **Status**: resolved. Follow-up: `~/.claude/skills-disabled/` (real dir with only `darwin-skill`/`find-skills` symlinks) is orphaned — these npx skills are already symlinked into `<repo>/skills/` by link.sh, so the disabled-side copies serve no purpose. Could be deleted to remove confusion, but harmless as-is.
 ## BLK-007 — 6 gstack source skills (ios-*, spec) unlinked — invisible to profile system + `gstack on`
 - **Date**: 2026-06-02
 - **Friction**: `skills-external/gstack/` has 53 source skills; 6 (`ios-clean`, `ios-design-review`, `ios-fix`, `ios-qa`, `ios-sync`, `spec`) exist ONLY as source — NOT symlinked into `skills/` (enabled) nor `skills-disabled/gstack__*` (parked). So invisible to Claude AND untouched by `reset`/`gstack on` (both operate on parked `gstack__*` only). Surfaced while adding `gstack on|off`: `comm` of gstack source vs `full.profile`.
 - **Real cause**: gstack submodule bump added new skills; gstack's own `./setup` (source of truth for per-skill symlinks per link.sh) not re-run → symlinks never created. Same lifecycle gap class as [[toggle-external-source-only-state]] (LRN-007). NOT a `full.profile` bug — full curated by design (BDR-017 caveat: "full excludes rarely-used gstack skills"). Initial "full omits ios = bug" flag was WRONG, self-corrected (see EVAL-002).
 - **Solution applied** (NOT full `./setup` — surgical, no side effects): (1) Linked `spec` only — `mkdir skills/spec` + `ln -snf <abs>/skills-external/gstack/spec/SKILL.md skills/spec/SKILL.md`, matching gstack setup:440-476 (per-skill real dir + SKILL.md symlink, name from frontmatter). (2) Added `spec` to `full.profile` + `web-full.profile` planning sections (must be in active profile `full` else `set full` re-disables it). (3) iOS 5 skills deliberately NOT linked — Linux host, device-farm needs Mac daemon + Tailscale + iOS devices = dead skills + token cost. (4) Completed `.gitignore` gstack allowlist: added all 12 missing (`spec`, 5 `ios-*`, 6 parked `document-generate/landing-report/scrape/setup-gbrain/skillify/sync-gbrain`), removed stale `checkpoint` (BLK-005 rename). Reason: `gstack on` (BDR-018) moves parked skills into `skills/` — any gstack skill missing from allowlist = untracked git noise on enable.
 - **Verified**: `profile show full`+`web-full` → spec enabled; allowlist drift recheck EMPTY; spec skill now visible to Claude.
 - **Status**: resolved. iOS = intentional exclusion (re-linkable via gstack `./setup` on a Mac). See [[gstack-gitignore-allowlist-completeness]] (LRN-025).
 ## BLK-008 — gstack ./setup fails on Ubuntu 26.04 — Playwright chromium unsupported
 - **Date**: 2026-06-23
 - **Friction**: fresh Ubuntu 26.04, `make install` / `make plugin` → "Failed to install browsers / ERROR: Playwright does not support chromium on ubuntu26.04-x64" → "GStack ./setup failed". Non-fatal in our wrapper (warn only) but gstack's browser (`/browse`, `/qa`, design screenshots) is silently dead once gstack is enabled.
 - **Real cause**: Playwright 1.58.2 (pinned in the gstack submodule) registry lists `ubuntu20.04/22.04/24.04` only; 26.04 released later → not in list → `getHostPlatform` errors. Pure OS-newness, not an install bug.
 - **Solution**: gated `export PLAYWRIGHT_HOST_PLATFORM_OVERRIDE=ubuntu24.04-x64` (ubuntu >24.04 only) before gstack setup + persisted to `.bashrc` for runtime. Playwright then pulls a Chrome-for-Testing fallback build for ubuntu24.04. Verified on 26.04: `ldd` resolves all libs + real headless render OK.
 - **Status**: resolved (commit 211c7d4). Residual: exact rev 1208 launch not in-session-tested (sandbox download hung at extraction); proved via sibling rev 1228 same-platform CfT build. Confirm on next real `make plugin`. Proper upstream fix = gstack bumps Playwright to a version that lists ubuntu26.04. See [[LRN-038]].
 - **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]].
 ---
 ## BLK-009 — user-level path-scoped rules don't load (#21858) — still broken in CC 2.1.190
 - **Date**: 2026-06-25
 - **Friction**: tried to scope a global rule to matching files via `paths:` frontmatter in `~/.claude/rules/<name>.md` — the rule never injects, even when a matching file (`*.probe`) is read in a fresh session. Blocks any "load this guidance only for matching files" strategy at the user level.
 - **Real cause**: GitHub issue #21858 — user-level (`~/.claude/rules/`) rules carrying `paths:` frontmatter are not evaluated/injected; still unfixed in 2.1.190. (Project-level path-scoped rules not tested here.)
 - **Probe method**: 3-file probe — `_probe.md` (`paths: ["**/*.probe"]`, sentinel `SENTINEL_USER_RULE_LOADED`), `_probe_ctl.md` (NO `paths`, control sentinel `CONTROL_NOPATHS_LOADED`), `_probe_target.probe` (target, read in a fresh session). Result: control sentinel PRESENT in session context, path-scoped sentinel ABSENT → the path-scoped rule did not load. Probe files removed after.
 - **Status**: upstream, open. Workaround: don't rely on user-level path-scoping → keep global guidance unconditional + COMPRESSED ([[BDR-031]]). Side-note: native auto-memory = "on" but writes nothing yet (fresh machine). Re-test on CC upgrades.
 - **2026-07-06 UPDATE — RESOLVED**: re-probed `paths:` frontmatter lazy-load with fresh 3-file probe (`**/*.blkprobe` glob) — confirmed loading works at BOTH project-level AND user-level (`~/.claude/rules/`) rule dirs. #21858 no longer reproduces on current CC version. Status → resolved. Prior workaround (unconditional + compressed global CLAUDE.md, [[BDR-031]]) no longer forced by this bug — see [[LRN-103]].
 - **Reference**: GitHub #21858. Linked to [[BDR-031]], [[LRN-044]], [[LRN-103]].
 ---
 ## BLK-010 — init-project scaffold + bootstrap README have no deterministic commit owner; worktree on unborn HEAD
 - **Date**: 2026-06-27
 - **Friction**: init-project scaffold (STEP 5 — CLAUDE.md, settings, config, entry points, `.gitignore`, `.env.example`, `.claude/`) + bootstrap README (STEP 5b) never get an explicit commit. Pipeline's only commits = STEP 10b memory (helper) + STEP 8 per-task implementer commits. Whether scaffold/README land in a commit = emergent: implementer-prompt.md says only "4. Commit your work", scope undefined. Greenfield deeper: STEP 8 `subagent-driven-development` requires `using-git-worktrees` → `git worktree add -b` branches from HEAD, but post-`git init` HEAD is UNBORN → add fails; the worktree skill has no unborn-HEAD path.
 - **Real cause**: no deterministic commit step between `git init` (STEP 5) and FINISH (STEP 11). scaffolder + doc-syncer both write-only (zero `git commit`). implementer commit scope unspecified. `using-git-worktrees` assumes a born HEAD.
 - **Solution**: open — own chantier (real technical weight: unborn HEAD + worktree). Candidate: explicit initial scaffold commit after STEP 5/5b before STEP 8, OR handle unborn HEAD in the worktree step. NOT cured by the doc-sync coupled chantier — that commits ONLY doc-sync's patched files and (correctly) excludes scaffold. Consequence: after doc-sync coupled, ship-feature fully fixed, init-project PARTIAL (doc-sync ok, scaffold/bootstrap still open).
 - **Status**: resolved (2026-06-29; working tree uncommitted — durable only at the claude repo commit, cf [[BLK-012]]). Was "open"; closed by the gitflow chantier — see note below.
 - **Reference**: discovered in doc-sync-coupled analysis (2026-06-27). Distinct from the doc-sync twin [[BDR-034]]. Sibling [[BLK-011]]. Surfaces via analyze-before-plan bookend on any init-project commit-flow work.
 - **2026-06-29 — RESOLVED by the gitflow chantier**: `gitflow_init` fresh path (`_gitflow_init_fresh`: unborn HEAD → `git symbolic-ref HEAD refs/heads/main` → `git add -A` → deterministic root commit → `git branch develop`) wired at init-project **STEP 5f** (after scaffold STEP 5 + README STEP 5b, before STEP 8 implement). Closes all 3 components: (a) scaffold+README get a deterministic commit owner = the root commit (`git add -A` stages whole tree; SKILL.md STEP 5f + lines 141/249-250 "scaffold commit owner … BLK-010 closed"); (b) root commit + develop make HEAD BORN before STEP 8 → `gitflow start feature`/`worktree add -b` never hits unborn HEAD; (c) STEP 5f IS the deterministic commit step between `git init` and FINISH. Tested: gitflow-test.sh **T2 "init fresh (BLK-010 root commit)"** (root commit on main, socle IN root commit, hook tracked, tree clean). Residual (non-blocking): the generic `using-git-worktrees` skill still has no unborn-HEAD path — now MOOT (HEAD always born by STEP 5f, never reached), not patched in the skill itself.
 ## BLK-011 — init-project STEP 13 GSD post-FINISH creates ROADMAP.md → stranded doc
 - **Date**: 2026-06-27
 - **Friction**: init-project STEP 13 (GSD v2 init) runs post-FINISH (STEP 11). `gsd init` creates `.gsd/` + `ROADMAP.md` (a public doc). Created AFTER FINISH integrates → ROADMAP never in the merge/PR. Same PR-stranding class as the doc-sync twin, 3rd post-FINISH artifact.
 - **Real cause**: artifact-producing step ordered after FINISH (= BDR-034 class). `gsd init` is a CLI mechanism distinct from doc-syncer; ROADMAP is sync-only for doc-syncer (never created by it, BDR-022 rules), so the doc-sync coupled chantier does not touch it.
 - **Solution**: open — separate thread. Candidate: reorder GSD before FINISH, or commit ROADMAP after `gsd init`. Out of scope for doc-sync coupled (different mechanism). [historical candidates — NOT the route taken]
 - **Resolution**: RESOLVED 2026-06-29 — by REMOVAL, not by committing the orphan. init-project STEP 12 (speculative gsd auto-bootstrap) DELETED → ROADMAP/.gsd never created post-FINISH → orphan dissolves, no commit helper built. TRUE reason: auto-bootstrapping a heavy multi-session ENGINE the sole user doesn't use, AT project-creation, is bad on its own terms. NOT the initial framing "ROADMAP redundant with TODO" — that was wrong and would have aged badly: gsd ≫ roadmap (state machine / crash-recovery / cost / parallel / worktree), and TODO ≠ gsd ROADMAP (different altitude + consumer). Reasoning trace: BOTH initial premises (gsd=only-roadmap; TODO-redundant) REFUTED on read, yet conclusion A (remove STEP 12) held for the STRONGER reason — right answer, reason corrected before engraving. Deliberate gsd use KEPT (onboarder PHASE 6 `/onboard add gsd`, plugin-advisor reco, status-reporter `.gsd/` read, USAGE `gsd init`). Removed STEP 12 + header 12→11-step + 10c note + 4 USAGE refs; coherence sweep = zero dangling refs. [[LRN-072]]
 - **Status**: resolved (init-project STEP 12 removed — `skills/init-project/SKILL.md`; branch bugfix/blk-011-gsd-roadmap). Title says "STEP 13" — stale (was STEP 12 at removal per BDR-036 renumber); left per append-only.
 - **Reference**: discovered in doc-sync-coupled analysis (2026-06-27). Sibling [[BLK-010]] + twin [[BDR-034]].
 ## BLK-012 — gitflow_init non-transactional: socle-commit failure swallowed → hook activated on partial run → re-run self-blocks
 - **Date**: 2026-06-29
 - **Friction**: migrating faunosteo, `migrate_local` → `gitflow_init` half-applied TWICE. Run 1: master→main renamed, develop created, socle staged, but the socle commit died — `Author identity unknown ... unable to auto-detect email address (got 'bchanot@bchanot-server.(none)')` → tree DIRTY, exit 1. Run 2 (recovery): socle commit BLOCKED by the gitflow hook itself (`gitflow pre-commit: BLOCKED — direct commit on 'main'`), yet `init` reported `exit=0` (a lie); main still at the old tip, socle uncommitted.
 - **Real cause**: `_gitflow_init_existing` SWALLOWED the socle-commit failure — `git diff --cached --quiet || git commit` with no propagation, and the function's last stmt (`git branch develop`) returned 0, masking the dead commit. Init CONTINUED past the failed commit → ran `gitflow_activate_hook` though the socle was never committed → re-run then self-blocks (commit on main blocked by the now-active hook). Design's "idempotent" + "never self-blocked" claims hold ONLY for a clean single run; a partial run breaks both. Fresh-repo path already propagated its failure (`_gitflow_init_fresh`); existing-repo path did not — the asymmetry was the bug. Trigger upstream of it: git identity UNSET (global unset; faunosteo had no local identity, though its own history uses `Bastien Chanot <git@bchanot.fr>`).
 - **Solution**: (1) socle commit FATAL in `_gitflow_init_existing` — `if ! git diff --cached --quiet; then git commit … || { echo …; return 1; }; fi` → aborts BEFORE develop/hook-activation; (2) identity precheck at top of `gitflow_init` (fail loud, no half-apply); (3) identity guard in `gitflow-migrate.sh:migrate_local`. Recovery: set faunosteo local identity → deactivate hook → delete premature develop → reinit (socle commits with hook inactive, as designed) → main==develop @ socle, tree clean, master renamed. Verified: shellcheck clean, 57/57 tests pass, hardened init on an identity-less repo aborts rc1 with ZERO mutation.
 - **Status**: resolved (`lib/gitflow.sh` + `lib/gitflow-migrate.sh`, uncommitted working tree as of the gitflow chantier).
 - **Reference**: [[LRN-068]] (transactional-bootstrap principle). Discovered mid gitflow-migration 2026-06-29. Sibling chantier learning [[LRN-067]].
 ## BLK-013 — `make plugin` Error 127: npm absent on apt-`nodejs` host
 - **Date**: 2026-06-30
 - **Friction**: `make plugin` (→ `install-plugins.sh`) aborts at Step 4 (gsd-pi): `install-plugins.sh: line 425: npm: command not found` → `make: *** [Makefile:10: plugin] Error 127`. Steps 5-10 never run, AND the post-Step-4 stray-dir cleanup (Step 8.5) never reached → the [[BDR-030]]/[[LRN-042]] residual (stray `$REPO/.agents/skills` + `$REPO/.claude/skills`, promised "auto-cleaned next `make plugin`") silently persists run after run. SessionStart banner already showed `gsd v2 ✗`.
 - **Real cause**: Debian/apt `nodejs` package ships `node` WITHOUT `npm` (npm = separate apt pkg). `/usr/bin/node` present (v22.22.1); its bindir has acorn/corepack/semver but NO npm/npx — npm genuinely uninstalled, not a PATH miss. install-plugins.sh Step 1 checks `node >=22` but NEVER verifies npm — assumes npm ships with node (true for nodesource/brew/dnf paths, FALSE for plain apt).
 - **Solution**: corepack (ships with node) over apt npm (apt npm could pull a divergent 2nd node). `corepack enable --install-directory "$HOME/.local/bin" npm` → npm 11.18.0 shim, no sudo, `~/.local/bin` already on PATH. Then `npm config set prefix "$HOME/.local"` — default prefix `/usr` is root-owned → `npm install -g` would EACCES; `~/.local` writable + bins land on PATH. Persisted in `~/.npmrc`. Re-run → EXIT=0, Step 4 ✓ (`gsd-pi@2.64.0`), Step 8.5 ran (`Removed stray repo-local skills dir: .agents/skills` + `.claude/skills`). Caveat: gsd-pi DEPRECATED + postinstall scripts SKIPPED (npm 11 `allow-scripts`) — `gsd --version/--help` ok, full provisioning would need `npm install -g --allow-scripts=gsd-pi,… gsd-pi`.
 - **Fix-forward**: install-plugins.sh Step 1 should GUARANTEE npm on apt-`nodejs` hosts — detect missing npm + `corepack enable npm` (not just check node) → stops Error 127 recurring on any fresh apt machine.
 - **Status**: resolved (env-level: corepack shim + npm prefix; zero repo change). Fix-forward (script hardening) NOT built.
 - **Reference**: discovered fixing `make plugin` 2026-06-30. Distinct from [[BLK-003]] (macOS playwright hardcoded path) + the Playwright-chromium `make plugin` failure. Blocked residual = [[BDR-030]]/[[LRN-042]].
 - **Update 2026-07-01**: fix-forward BUILT. install-plugins.sh Step 1 gained unconditional npm guard (`corepack enable npm` → distro `install npm` fallback → fatal `exit 1`), placed AFTER the `NODE_OK` short-circuit so a node>=22-present-but-npm-absent host no longer skips it. Now fully resolved (env-level + script). shellcheck/`bash -n` clean; fresh-apt live validation still pending. Commit `1f2c1cc`, branch `bugfix/install-plugins-npm-guard`.
 ---
 ## BLK-014 — `make install` aborts npm EEXIST when claude already present
 - **Date**: 2026-07-01
 - **Friction**: `make install` → install.sh Step 2 `npm install -g @anthropic-ai/claude-code@latest` fails EEXIST on `~/.local/bin/claude` when claude already installed → `else err` → `exit 1`. Bootstrap not idempotent on Claude Code step; rest (auth, symlinks, plugins) never runs.
 - **Real cause**: claude installed via NATIVE installer, not npm — `~/.local/bin/claude` = symlink → `~/.local/share/claude/versions/<v>` (`npm ls -g @anthropic-ai/claude-code` = empty; `claude --version` = 2.1.197). npm prefix `~/.local` (set by [[BLK-013]]) targets same `~/.local/bin/claude` → npm won't clobber a bin it doesn't own → EEXIST. Channel conflict, not double-install. Step had NO presence guard, unlike RTK (install-plugins.sh:388) / GSD (:419) / claude check (:252).
 - **Solution**: install.sh — skip-if-present guard `command -v claude` (mirror RTK/GSD), npm only fresh machine (`elif`). update-all.sh — channel-aware updater: `npm ls -g` → npm-managed uses npm, else native uses `claude update` (self-update). Never `npm --force` (would clobber native, break self-update).
 - **Status**: resolved. Fix `8dc4027`, branch `bugfix/install-claude-idempotent`, pending merge validation.
 - **Reference**: [[BLK-013]] npm prefix `~/.local` = contributing factor (npm bin over native bin). install-plugins.sh already pointed to code.claude.com (native) — install.sh was the npm outlier. Fresh-machine `elif npm` branch channel-consistency = open design question (potential BDR). Pattern → [[LRN-085]].
 - **Update 2026-07-01**: MERGED `2393ca5` (bugfix/install-claude-idempotent → develop), pushed — supersedes "pending merge validation". The open channel-consistency question is RESOLVED by [[BDR-046]] (fresh install → native installer, npm dropped for claude); install.sh has no `elif npm` branch → nothing left to trancher.
 ## BLK-015 — `gitflow_finish` ignored its args, merged the CURRENT branch not the one asked
 - **Date**: 2026-07-03
 - **Friction**: audit 2026-07-02 — `gitflow.sh finish bugfix audit-bugs` run while checked out on `feature/audit-tokens` merged audit-tokens (LOT3), NOT audit-bugs. Final develop state identical (disjoint hunks) so no data damage, but the merge order was silently wrong. UX trap: the command LOOKS like it targets `bugfix/audit-bugs`.
 - **Real cause**: CLI dispatch (`lib/gitflow.sh:257` `finish) gitflow_finish "$@"`) forwards args, but the function derived its source from `HEAD` (`git symbolic-ref`) and NEVER read `$1/$2` → the `<type> <name>` were silently dropped. Merge source = ambient state (checked-out branch), not the named target. Design intended finish to always operate on HEAD (human gate = "be on the branch"), but nothing enforced that passed args, if any, MATCH the branch you're on.
 - **Solution**: `gitflow_finish [<type> <name>]` — args now an optional safety ASSERTION: present AND `"$req_type/$req_name" != "$br"` → error `operates on the current branch 'X', but you asked 'Y' — checkout 'Y' first`, rc 2. No args = behavior unchanged (only real caller `skills/gitflow/SKILL.md:36` + every test pass none → zero regression). +7 regression assertions (`gitflow-test.sh` T12, numbered to dodge collision with reconcile's own T6c).
 - **Status**: resolved. Commit `d9fdd4c`, branch `bugfix/gitflow-finish-args`.
 - **Reference**: journal 2026-07-02 (trap noted, not fixed) → fixed 2026-07-03. Pattern → [[LRN-089]] (pass-through wrapper deriving target from ambient state = silent contract violation).
@@ -0,0 +1,21 @@
 # decisions-snapshot — frozen fixture for run-reconcile.sh T3/T5 (SPEC-10, J4-10)
 # Neutral name, LRN-077 style: this is NOT the live registry. Carries exactly what
 # reconcile_deferrals / reconcile_contradiction_candidates scan against
 # fixtures/todo-snapshot.md, so the suite never reds just because the live
 # decisions.md gets legitimately pruned or reworded.
 ## BDR-900 — Uniform --help helper via session-start hook (option C)
 - **Decision**: every skill expose `--help` via a shared snippet injected by a
  hook, not a duplicate helper per SKILL.md.
 - **Status**: accepted · won't-build — measured non-rentable, see the linked
  TODO chantier (the intended behavior was already spontaneous).
 - **Follow-up**: OUT-OF-SCOPE for now; reconsider only if a new skill class
  demonstrably needs a diverging `--help` shape.
 ## BDR-901 — rename-note follow-up
 - Bigger picture: looks like a deliberate rename to disambiguate two
  same-named things. Could be a planned migration that stalled. Worth a
  one-line ticket separate from the main chantier.
 ## BDR-902 — deferred cleanup
 - DEFERRED until the next audit pass; not actionable now.
@@ -1,12 +0,0 @@
 # Frozen oracle answers as of the reconcile point (bdfa9bc). Each value is an
 # independently-checkable git/fs truth, hand-recorded — NOT generated by reconcile.sh.
 # Consumed by the deterministic kernel test (T4). Live oracles are proven separately (T6).
 merge_done:bugfix/prune-memory-hardening=true
 pushed:develop=true
 tree_clean=true
 commit_msg:gitmodules=true
 path:.claude/skills/darwin-skill=present
 blk_current:BLK-008=resolved
 blk_current:BLK-009=open
 blk_current:BLK-001=open
 blk_current:BLK-003=open
@@ -0,0 +1,49 @@
 #!/usr/bin/env bash
 # ============================================================
 # Structure locks — heavy-flow wiring (verify-loops lot 5)
 # ship-feature + init-project get contract + enrich-at-gate +
 # verify-secure-loop; onboard is the explicit NO-LOOP audit case.
 # ============================================================
 set -u
 REPO="$(cd "$(dirname "$0")/../.." && pwd)"
 SHF="$REPO/skills/ship-feature/SKILL.md"
 INI="$REPO/skills/init-project/SKILL.md"
 ONB="$REPO/skills/onboard/SKILL.md"
 PASS=0; FAIL=0
 tf() { # tf <label> <file> <fixed-string>   (single-line patterns only, LRN-093)
  if grep -qF -- "$3" "$2" 2>/dev/null; then
    echo "  PASS $1"; PASS=$((PASS+1))
  else
    echo "  FAIL $1 — missing: $3"; FAIL=$((FAIL+1))
  fi
 }
 echo "-- ship-feature (enrich-at-gate) --"
 tf "shf contract step"        "$SHF" "STEP 0e — CONTRACT"
 tf "shf contract-interview"   "$SHF" "lib/contract-interview.md"
 tf "shf enrich at gate"       "$SHF" "ENRICH the STEP 0e contract"
 tf "shf gated marker"         "$SHF" "[gated <date>]"
 tf "shf verify+secure step"   "$SHF" "STEP 5 — VERIFY + SECURE"
 tf "shf uses shared include"  "$SHF" "lib/verify-secure-loop.md"
 tf "shf judges enriched"      "$SHF" "ENRICHED contract"
 tf "shf orthogonal to review" "$SHF" "DISTINCT axis from STEP 6 code review"
 echo "-- init-project (contract from BRIEF + adds security) --"
 tf "ini contract from brief"  "$INI" "contract-interview.md"
 tf "ini criteria from V1"     "$INI" "V1 FEATURES (each testable)"
 tf "ini enrich at gate1"      "$INI" "ENRICH the STEP 1 contract"
 tf "ini verify+secure step"   "$INI" "STEP 9 — VERIFY + SECURE"
 tf "ini uses shared include"  "$INI" "lib/verify-secure-loop.md"
 tf "ini adds security gate"   "$INI" "adds the security gate init-project previously lacked"
 echo "-- onboard (explicit NO-LOOP audit) --"
 tf "onb no-loop stated"       "$ONB" "n'a PAS de boucle verify"
 tf "onb audit not gate"       "$ONB" "MODE: audit"
 tf "onb scope contract"       "$ONB" "contract de SCOPE"
 tf "onb no symmetry loop"     "$ONB" "Ne PAS ajouter la boucle des flux dev"
 echo ""
 echo "loops-heavy structure locks: $PASS pass, $FAIL fail"
 [ "$FAIL" -eq 0 ]
@@ -0,0 +1,91 @@
 #!/usr/bin/env bash
 # ============================================================
 # Structure locks — light-flow wiring (verify-loops lot 4)
 # feat/bugfix get contract + fresh verifier + security gate
 # (bounded 3x); hotfix gets contract + security gate whose
 # FAILURE REVERTS (never loops). Locks the load-bearing clauses.
 # ============================================================
 set -u
 REPO="$(cd "$(dirname "$0")/../.." && pwd)"
 INC="$REPO/lib/verify-secure-loop.md"
 FSK="$REPO/skills/feat/SKILL.md"
 BUG="$REPO/agents/bugfixer.md"
 BSK="$REPO/skills/bugfix/SKILL.md"
 HOT="$REPO/agents/hotfixer.md"
 HSK="$REPO/skills/hotfix/SKILL.md"
 HSKL="$REPO/skills/hotfix/SKILL.md"
 PASS=0; FAIL=0
 tf() { # tf <label> <file> <fixed-string>
  if grep -qF -- "$3" "$2" 2>/dev/null; then
    echo "  PASS $1"; PASS=$((PASS+1))
  else
    echo "  FAIL $1 — missing: $3"; FAIL=$((FAIL+1))
  fi
 }
 tr_() { # tr_ <label> <file> <ERE>
  if grep -qE -- "$3" "$2" 2>/dev/null; then
    echo "  PASS $1"; PASS=$((PASS+1))
  else
    echo "  FAIL $1 — no match: $3"; FAIL=$((FAIL+1))
  fi
 }
 tn() { # tn <label> <file> <fixed-string> — PASS when ABSENT (mirror of tf, inverted)
  if grep -qF -- "$3" "$2" 2>/dev/null; then
    echo "  FAIL $1 — present (should be absent): $3"; FAIL=$((FAIL+1))
  else
    echo "  PASS $1"; PASS=$((PASS+1))
  fi
 }
 echo "── verify-secure-loop.md (shared include) ──"
 if [ -f "$INC" ]; then echo "  PASS include exists"; PASS=$((PASS+1)); else echo "  FAIL include missing"; FAIL=$((FAIL+1)); fi
 tf "gate1 fresh verifier"        "$INC" "GATE 1 — REQUEST CONFORMITY (fresh verifier)"
 tf "gate2 fresh auditor"         "$INC" "GATE 2 — SECURITY (fresh security-auditor)"
 tf "blind — no dev summary"      "$INC" "Never pass the dev's summary"
 tf "conforme first pass no loop" "$INC" "First-pass conforme = no loop"
 tf "conformity max 3"            "$INC" "Max 3 conformity iterations"
 tf "security max 3"              "$INC" "Max 3 security iterations"
 tf "reverify request first"     "$INC" "re-verify the REQUEST first"
 tf "order invariant"            "$INC" "always re-checked BEFORE security"
 tf "mute never a pass (verify)" "$INC" "NEVER a PASS"
 tf "nominal cheap stated"       "$INC" "one verifier dispatch + one security dispatch"
 echo "── feat/SKILL.md (feat orchestrator wiring) ──"
 tf "feat contract step"         "$FSK" "STEP 0.7 — CONTRACT"
 tf "feat contract-interview"    "$FSK" "lib/contract-interview.md"
 tf "feat verify+secure step"    "$FSK" "STEP 4 — VERIFY + SECURE"
 tf "feat uses shared include"   "$FSK" "lib/verify-secure-loop.md"
 tf "feat nominal 1+1 dispatch"  "$FSK" "verifier + one security dispatch"
 tf "feat dispatches feater"     "$FSK" 'subagent_type="feater"'
 echo "── skills/bugfix/SKILL.md (bugfix wiring — reflection inline) ──"
 tf "bug contract step"          "$BSK" "STEP 3.5 — CONTRACT"
 tf "bug diagnosis feeds it"     "$BSK" "feeds it: REQUEST verbatim"
 tf "bug fresh gates"            "$BSK" "the two fresh gates per"
 tf "bug uses shared include"    "$BSK" "lib/verify-secure-loop.md"
 tf "bug dispatches bugfixer"    "$BSK" 'subagent_type="bugfixer"'
 echo "── agents/bugfixer.md (bugfix executor — sonnet, no Agent) ──"
 tn "bugfixer lacks Agent tool"  "$BUG" "Agent"
 tf "bugfixer model sonnet"      "$BUG" "model: sonnet"
 tf "bugfixer report grammar"    "$BUG" "BUGFIX-EXEC REPORT"
 echo "── hotfixer.md (hotfix executor — sonnet, no Agent) ──"
 tn "hotfixer lacks Agent tool"  "$HOT" "Agent"
 tf "hotfixer model sonnet"      "$HOT" "model: sonnet"
 tf "hotfixer report grammar"    "$HOT" "HOTFIX-EXEC REPORT"
 echo "── skills/hotfix/SKILL.md (hotfix wiring — revert, not loop) ──"
 tf "hotfix silent contract"     "$HSKL" "STEP 1.7 — CONTRACT (silent autofill)"
 tf "hotfix zero questions"      "$HSKL" "questions ever"
 tf "hotfix security gate"       "$HSKL" "Security gate (fresh auditor)"
 tf "hotfix block reverts"       "$HSKL" "failure REVERTS, never loops"
 tf "hotfix no verifier"         "$HSKL" "No verifier is dispatched at hotfix weight"
 tf "hotfix skill has Agent"     "$HSK" "  - Agent"
 tf "hotfix dispatches hotfixer" "$HSKL" 'subagent_type="hotfixer"'
 echo ""
 echo "loops-light structure locks: $PASS pass, $FAIL fail"
 [ "$FAIL" -eq 0 ]
@@ -0,0 +1,25 @@
 #!/usr/bin/env bash
 # lib/tests/model-check.test.sh — flip-tests for lib/model-check.sh (LRN-096)
 set -u
 S="$(cd "$(dirname "$0")/../.." && pwd)/lib/model-check.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; }
 T="$(mktemp -d)"; trap 'rm -rf "$T"' EXIT
 fx()  { printf '{"model": "%s"}' "$1" > "$T/s.json"; }
 run() { MODEL_CHECK_SETTINGS="$T/s.json" bash "$S" >"$T/out" 2>&1; echo "$?"; }
 fx 'claude-fable-5[1m]';        check T1-fable-exit "$(run)" 0
 check T1-fable-class "$(cut -d: -f1 <"$T/out")" big
 fx 'claude-opus-4-8';           check T2-opus       "$(run)" 0
 fx 'claude-sonnet-5';           check T3-sonnet     "$(run)" 2
 fx 'claude-haiku-4-5-20251001'; check T4-haiku      "$(run)" 2
 fx 'opusplan';                  check T5-opusplan   "$(run)" 3
 fx 'gpt-9-mega';                check T6-foreign    "$(run)" 3
 printf '{"no_model": true}' > "$T/s.json"; check T7-no-key    "$(run)" 3
 printf '{broken'            > "$T/s.json"; check T8-malformed "$(run)" 3
 check T9-missing-file "$(MODEL_CHECK_SETTINGS="$T/absent.json" bash "$S" >/dev/null 2>&1; echo $?)" 3
 printf 'model-check: %d pass, %d fail\n' "$pass" "$fail"
 [ "$fail" -eq 0 ]
@@ -0,0 +1,70 @@
 #!/usr/bin/env bash
 # lib/tests/model-routing.test.sh — census: gate wiring + pins + executor shape (BDR-066)
 set -u
 R="$(cd "$(dirname "$0")/../.." && pwd)"
 pass=0; fail=0
 ok() { pass=$((pass+1)); }
 ko() { fail=$((fail+1)); printf 'FAIL %s\n' "$1"; }
 has()   { if grep -qF "$2" "$R/$1"; then ok; else ko "$1 missing: $2"; fi; }
 lacks() { if grep -qF "$2" "$R/$1"; then ko "$1 must NOT contain: $2"; else ok; fi; }
 fm_lacks() { if awk 'NR<=10' "$R/$1" | grep -qF "$2"; then ko "$1 frontmatter must NOT contain: $2"; else ok; fi; }
 # 1) gate wired in the 15 reflection skills (orchestrators + /analyze)
 for s in ship-feature init-project feat bugfix onboard seo geo web-validate harden audit-delta tour code-clean hotfix client-handover analyze; do
  has "skills/$s/SKILL.md" 'lib/model-gate.md'
 done
 # 2) gate NOT wired in the pure-execution/read-only skills (exclusion list)
 for s in commit-change doc status release-candidate refactor; do
  lacks "skills/$s/SKILL.md" 'lib/model-gate.md'
 done
 # 3) executor + gate pins
 has "agents/feater.md"          'model: sonnet'
 has "agents/hotfixer.md"        'model: sonnet'
 has "agents/verifier.md"        'model: sonnet'
 has "agents/security-auditor.md" 'model: sonnet'
 fm_lacks "agents/analyzer.md"   'model:'
 # 4) /feat executor shape
 has "skills/feat/SKILL.md" 'subagent_type="feater"'
 has "skills/feat/SKILL.md" 'verify-secure-loop.md'
 lacks "agents/feater.md" 'AskUserQuestion'
 # 5) SDD execution pinned
 has "skills/ship-feature/SKILL.md" 'model: "sonnet"'
 has "skills/init-project/SKILL.md" 'model: "sonnet"'
 # 6) web-validate applies via L1 applier
 has "skills/web-validate/SKILL.md" 'subagent_type="hotfixer"'
 # 7) wave-2 — pure-execution skills dispatch their agent (pin takes effect, off the big session model)
 has "skills/doc/SKILL.md"               'subagent_type="doc-syncer"'
 has "skills/status/SKILL.md"            'subagent_type="status-reporter"'
 has "skills/commit-change/SKILL.md"     'subagent_type="commit-changer"'
 has "skills/release-candidate/SKILL.md" 'subagent_type="release-executor"'
 has "skills/hotfix/SKILL.md"            'subagent_type="hotfixer"'
 has "agents/commit-changer.md"          'model: sonnet'
 has "agents/release-executor.md"        'model: sonnet'
 lacks "agents/commit-changer.md"        'AskUserQuestion'
 # 8) wave-3 — bugfix/code-clean reflection-split executors (skills stay gated)
 has "skills/bugfix/SKILL.md"     'subagent_type="bugfixer"'
 has "agents/bugfixer.md"         'model: sonnet'
 lacks "agents/bugfixer.md"       'AskUserQuestion'
 has "skills/code-clean/SKILL.md" 'subagent_type="code-cleaner"'
 has "agents/code-cleaner.md"     'model: sonnet'
 lacks "agents/code-cleaner.md"   'AskUserQuestion'
 # 9) wave-4 — client-handover: pipeline (big) inline + gated, doc-gen dispatched to sonnet
 has "agents/handover-doc-writer.md"     'model: sonnet'
 lacks "agents/handover-doc-writer.md"   'AskUserQuestion'
 lacks "agents/handover-doc-writer.md"   'Agent('
 has "agents/client-handover-writer.md"  'subagent_type="handover-doc-writer"'
 # 10) post-merge edge fixes (ronde): F1 feater applier carve-out, F2 /refactor
 #     dispatch + pin, F3 /analyze gated (in loop 1), F4 interviewer un-pinned,
 #     F5 audit agents' ABSENT pin locked (a stray sonnet pin would silently
 #     downgrade a live audit even though the skill's gate passed)
 has "agents/feater.md"                       'Applier path'
 has "skills/refactor/SKILL.md"               'subagent_type="refactorer"'
 has "agents/refactorer.md"                   'model: sonnet'
 fm_lacks "agents/seo-analyzer.md"            'model:'
 fm_lacks "agents/geo-analyzer.md"            'model:'
 fm_lacks "agents/validator-analyzer.md"      'model:'
 fm_lacks "agents/client-handover-writer.md"  'model:'
 fm_lacks "agents/interviewer.md"             'model:'
 printf 'model-routing census: %d pass, %d fail\n' "$pass" "$fail"
 [ "$fail" -eq 0 ]
@@ -0,0 +1,55 @@
 #!/usr/bin/env bash
 # ============================================================
 # Deterministic backstop for LRN-093 (vacuous grep locks).
 # grep NEVER interprets a literal \n as a newline: in a -F
 # fixed string it splits the pattern into a per-line OR (matches
 # anything); in -E it is a literal "n". Either way a structure
 # lock carrying \n proves nothing. The LRN advisory alone did not
 # hold (2 recurrences same chantier) -> this mechanical guard.
 #
 # Rule: no backslash-n inside a quoted pattern on a grep / tf /
 # tr_ / tn line, anywhere under lib/tests/*.test.sh. Flip-tested
 # below against a synthetic offender so the guard proves it bites.
 # ============================================================
 set -u
 REPO="$(cd "$(dirname "$0")/../.." && pwd)"
 SELF="no-vacuous-locks.test.sh"
 FAIL=0
 # One scanner, reused for the real tree and the flip-test fixture.
 # Matches a grep -*F/-*E call OR a tf/tr_/tn helper (at line start or after
 # whitespace) whose quoted pattern contains a literal backslash-n.
 scan() { # scan <dir containing *.test.sh>
  grep -rnE '(grep +-[A-Za-z]*[EFqe]|(^|[[:space:]])(tf|tr_|tn)[[:space:]]).*"[^"]*\\n' \
    "$1"/*.test.sh 2>/dev/null | grep -v "$SELF"
 }
 echo "-- LRN-093 backstop: scan lib/tests/*.test.sh --"
 HITS="$(scan "$REPO/lib/tests")"
 if [ -n "$HITS" ]; then
  FAIL=1
  printf '%s\n' "$HITS" | while IFS= read -r line; do
    printf '  FAIL vacuous backslash-n lock: %s\n' "$line"
  done
 else
  printf '  PASS no vacuous backslash-n locks in lib/tests/*.test.sh\n'
 fi
 # Flip-test: the guard MUST catch a known offender (LRN-093 discipline —
 # prove a lock CAN fail before trusting its green).
 echo "-- flip-test: guard bites a synthetic offender --"
 TMP="$(mktemp -d)"
 # shellcheck disable=SC2016  # the single quotes are deliberate: literal backslash-n
 printf '%s\n' 'tf "bad" "$F" "no\nforced loop"' > "$TMP/z.test.sh"
 if [ -n "$(scan "$TMP")" ]; then
  printf '  PASS guard catches the synthetic offender\n'
 else
  printf '  FAIL guard blind to a known offender (regex too weak)\n'
  FAIL=1
 fi
 rm -rf "$TMP"
 echo ""
 if [ "$FAIL" -eq 0 ]; then echo "no-vacuous-locks: clean"; else echo "no-vacuous-locks: vacuous locks present"; fi
 [ "$FAIL" -eq 0 ]
@@ -0,0 +1,45 @@
 #!/usr/bin/env bash
 # lib/tests/rtk-rewrite.test.sh
 # job7 — printenv/env dump redaction pass in hooks/rtk-rewrite.sh.
 set -u
 H="$(cd "$(dirname "$0")/../.." && pwd)/hooks/rtk-rewrite.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; }
 # raw(cmd) -> the hook's stdout for a simulated PreToolUse Bash command.
 raw() {
  local input
  input=$(jq -n --arg cmd "$1" '{tool_input:{command:$cmd}}')
  printf '%s' "$input" | bash "$H"
 }
 # fire(cmd) -> "redacted" if the hook appended the sed redaction pipe,
 # "intact" if the command comes back unchanged/untouched.
 fire() {
  if raw "$1" | grep -q 'sed -E'; then echo redacted; else echo intact; fi
 }
 # --- Env/printenv dumps must be redacted ---
 check T1-bare-printenv   "$(fire 'printenv')"        redacted
 check T2-bare-env        "$(fire 'env')"              redacted
 check T3-env-pipe-grep   "$(fire 'env | grep FOO')"   redacted
 # --- `env VAR=x cmd` launches a subprocess — legitimate, left intact ---
 check T4-env-legit       "$(fire 'env FOO=bar cmd')"  intact
 check T5-env-legit-2vars "$(fire 'env A=1 B=2 cmd')"  intact
 # --- Compound commands bail untouched (never attach the pipe to the wrong
 #     segment) ---
 check T6-bail-and        "$(fire 'env && true')"      intact
 check T7-bail-semi       "$(fire 'env; true')"        intact
 check T8-bail-or         "$(fire 'env || true')"       intact
 # --- Regression: unrelated rtk-eligible commands still rewrite, untouched
 #     by the redaction pass ---
 check T9-unrelated-still-rewrites \
  "$(raw 'cat /etc/hostname' | grep -c 'rtk ')" "1"
 check T10-unrelated-not-redacted \
  "$(raw 'cat /etc/hostname' | grep -c 'sed -E')" "0"
 printf 'PASS=%s FAIL=%s\n' "$pass" "$fail"; [ "$fail" -eq 0 ]
@@ -141,6 +141,20 @@ if [ "$after1" -eq "$((base + 1))" ] && [ -n "$h1" ]; then ok "run1 created exac
 if [ "$after2" -eq "$after1" ] && [ -z "$h2" ]; then ok "run2 is a no-op (no 2nd commit, empty stdout)"; else ko "run2 was not a no-op"; fi
 rm -rf "$R"
 echo "T8 — pre-commit hook REJECTS commit → fail LOUD (exit 5), no stale hash, HEAD unmoved"
 R="$(new_repo)"
 printf '#!/bin/sh\nexit 1\n' >"$R/.git/hooks/pre-commit"; chmod +x "$R/.git/hooks/pre-commit"
 BEFORE="$(git -C "$R" rev-parse --short HEAD)"
 printf 'REJECTED CHANGE\n' >>"$R/.claude/memory/decisions.md"
 OUT="$( (cd "$R" && "$HELPER" commit "chore(memory): T8 rejected") 2>/dev/null )"
 RC=$?
 AFTER="$(git -C "$R" rev-parse --short HEAD)"
 printf '    rc=%s out=[%s] before=[%s] after=[%s]\n' "$RC" "$OUT" "$BEFORE" "$AFTER"
 if [ "$RC" -eq 5 ]; then ok "rejected commit → exit 5 (fail-loud)"; else ko "expected 5, got $RC (rc0+stale-hash = masked failure)"; fi
 if [ -z "$OUT" ]; then ok "stdout empty on rejection (no stale hash)"; else ko "stdout leaked a hash on rejection: [$OUT]"; fi
 if [ "$BEFORE" = "$AFTER" ]; then ok "HEAD unmoved"; else ko "HEAD moved despite rejection"; fi
 rm -rf "$R"
 echo
 printf 'RESULT: %d passed, %d failed\n' "$PASS" "$FAIL"
 [ "$FAIL" -eq 0 ]
@@ -51,6 +51,15 @@ append_lines() {
  for ((i = 1; i <= n; i++)); do printf 'extra line %s\n' "$i" >>"$f"; done
 }
 # Remove exactly N lines from the END of a committed file (pure removal, 0
 # added lines, no heading) — for the REMOVED-envelope tests (S11-S13).
 truncate_last_n() {
  local f="$1" n="$2" total keep
  total=$(wc -l <"$f")
  keep=$((total - n))
  head -n "$keep" "$f" >"$f.tmp" && mv "$f.tmp" "$f"
 }
 # run [ENV=val] <repo> <args...> → sets RC (exit), OUT (stdout), ERR (stderr).
 # stdout MUST stay empty: the exit code carries the verdict, reasons go to stderr.
 run() {
@@ -160,6 +169,37 @@ printf '    rc=%s\n' "$RC"
 if [ "$RC" -eq 3 ]; then ok "not-a-repo → 3"; else ko "expected 3, got $RC"; fi
 rm -rf "$D"
 echo "S11 — remove exactly 20 lines (== threshold, pure removal) → within (0, boundary)"
 R="$(new_repo)"
 : >"$R/README.md"; append_lines "$R/README.md" 40
 git -C "$R" add README.md; git -C "$R" commit -qm "baseline 40 lines"
 truncate_last_n "$R/README.md" 20
 run "$R" check "README.md"
 printf '    rc=%s\n' "$RC"
 if [ "$RC" -eq 0 ]; then ok "removed 20 (== MAX) → within (0)"; else ko "expected 0, got $RC"; fi
 rm -rf "$R"
 echo "S12 — remove 30 lines (pure removal) → exceeds (1, size)"
 R="$(new_repo)"
 : >"$R/README.md"; append_lines "$R/README.md" 40
 git -C "$R" add README.md; git -C "$R" commit -qm "baseline 40 lines"
 truncate_last_n "$R/README.md" 30
 run "$R" check "README.md"
 printf '    rc=%s  err=%s\n' "$RC" "$(printf '%s' "$ERR" | head -1)"
 if [ "$RC" -eq 1 ]; then ok "removed 30 → exceeds (1)"; else ko "expected 1, got $RC"; fi
 if printf '%s' "$ERR" | grep -q 'README.md'; then ok "stderr names the offending path"; else ko "offender not named"; fi
 rm -rf "$R"
 echo "S13 — DOC_SHAPE_MAX_REMOVED=5 + 6-line removal → exceeds (1, env-tunable)"
 R="$(new_repo)"
 : >"$R/README.md"; append_lines "$R/README.md" 40
 git -C "$R" add README.md; git -C "$R" commit -qm "baseline 40 lines"
 truncate_last_n "$R/README.md" 6
 OUT="$( (cd "$R" && DOC_SHAPE_MAX_REMOVED=5 "$HELPER" check "README.md") 2>"$ERRFILE" )"; RC=$?
 printf '    rc=%s\n' "$RC"
 if [ "$RC" -eq 1 ]; then ok "override MAX_REMOVED=5, 6 removed → exceeds (1)"; else ko "expected 1, got $RC"; fi
 rm -rf "$R"
 rm -f "$ERRFILE"
 echo ""
 printf 'RESULT: %d passed, %d failed\n' "$PASS" "$FAIL"
@@ -11,7 +11,6 @@ GREP=/usr/bin/grep                                  # LRN-074: pin grep
 HERE="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 REPO="$(cd "$HERE/.." && pwd)"
 FIX="$HERE/fixtures"
 MEM="$REPO/../.claude/memory"; [ -d "$MEM" ] || MEM="$REPO/.claude/memory"
 # shellcheck source=/dev/null
 source "$REPO/reconcile.sh"
@@ -30,20 +29,24 @@ idx_only=$($GREP -oE '^\| LRN-[0-9]+' "$DRIFT" | $GREP -oE 'LRN-[0-9]+' | sort -
 if printf '%s\n' "$idx_only" | $GREP -qx "LRN-020"; then no "T1c teeth LOST — Index path also yields LRN-020"; else ok "T1c teeth intact — Index path OMITS LRN-020 (engine reading the Index would fail T1b)"; fi
 echo; echo "=== T2 BLK status — LAST block wins (the BLK-008 trap) ==="
-b="$MEM/blockers.md"
+# Hermetic fixture, not the live registry (job3 B1): a frozen post-BLK-009
 # snapshot so this test never reds again just because a future blocker gets
 # closed. Re-freeze this fixture (copy the live blockers.md) if BLK-008's
 # compound-status trap or the open/resolved mix it exercises ever changes.
 b="$FIX/blockers-snapshot.md"
 case "$(reconcile_blk_current_status "$b" BLK-008)" in
  *RESOLVED*|*resolved*) ok "T2a BLK-008 current = resolved (read FINAL, not the middle REVERTED)";;
  *) no "T2a BLK-008 misread as non-resolved — fell into the compound-status trap";;
 esac
 case "$(reconcile_blk_current_status "$b" BLK-009)" in
-  *open*|*upstream*) ok "T2b BLK-009 current = upstream/open";;
+  *RESOLVED*|*resolved*) ok "T2b BLK-009 current = resolved (fixture frozen post-2026-07-06 closure)";;
  *) no "T2b BLK-009 misread";;
 esac
 open_ids=$(reconcile_blk_open "$b" | cut -f1 | sort | tr '\n' ' ')
-if [ "$open_ids" = "BLK-001 BLK-003 BLK-009 " ]; then ok "T2c open blockers = {001,003,009}"; else no "T2c open = [$open_ids], expected {001,003,009}"; fi
+if [ "$open_ids" = "BLK-001 BLK-003 " ]; then ok "T2c open blockers = {001,003}"; else no "T2c open = [$open_ids], expected {001,003}"; fi
 echo; echo "=== T3 deferral lexical sweep (HONEST LIMIT: marked-only) ==="
-defer=$(reconcile_deferrals "$FIX/todo-snapshot.md" "$MEM/decisions.md")
+defer=$(reconcile_deferrals "$FIX/todo-snapshot.md" "$FIX/decisions-snapshot.md")
 for mark in "OUT-OF-SCOPE" "DEFERRED" "follow-up" "one-line ticket"; do
  if has "$defer" "$mark"; then ok "T3 found marked deferral: $mark"; else no "T3 missed marker: $mark"; fi
 done
@@ -54,19 +57,42 @@ if [ "$(reconcile_verdict ' ' true)"  = "STALE:open-but-done" ];    then ok "T4a
 if [ "$(reconcile_verdict 'x' false)" = "STALE:done-but-open" ];    then ok "T4b 'x'+!done  → STALE";      else no "T4b wrong"; fi
 if [ "$(reconcile_verdict '~' true)"  = "STALE:partial-but-done" ]; then ok "T4c '~'+done   → STALE";      else no "T4c wrong"; fi
 if [ "$(reconcile_verdict 'x' true)"  = "CONSISTENT" ];             then ok "T4d 'x'+done   → CONSISTENT"; else no "T4d wrong"; fi
 truths=$($GREP -cE '=(true|resolved|present)$' "$FIX/real-state.snapshot")
 if [ "$truths" -ge 6 ]; then ok "T4e snapshot supplies $truths real-true facts → kernel yields STALE for the 6 git-verifiable items"; else no "T4e snapshot facts=$truths (<6)"; fi
 echo "      (7th cat-4 item — twin doc-sync [~] cross-ref — is SURFACED for review, not auto-verified: honest limit)"
 echo; echo "=== T5 contradiction candidates (surface, never assert) ==="
-cand=$(reconcile_contradiction_candidates "$MEM/decisions.md" "$FIX/todo-snapshot.md")
+cand=$(reconcile_contradiction_candidates "$FIX/decisions-snapshot.md" "$FIX/todo-snapshot.md")
 if has "$cand" "--help"; then ok "T5 surfaced --help candidate (BDR-001 ⇄ --help chantier)"; else no "T5 missed --help candidate"; fi
 echo; echo "=== T6 live oracle smoke — oracles QUERY real git/fs (not a name) ==="
 if reconcile_oracle_merge_done "$REPO" "prune-memory"; then ok "T6a merge_done(prune-memory) via git log"; else no "T6a merge not found in git"; fi
 if reconcile_oracle_sha_exists "$REPO" "be1dcef";      then ok "T6b sha_exists(be1dcef) via cat-file";     else no "T6b sha missing"; fi
-dk="$MEM/../skills/darwin-skill"
+# $REPO here = lib/ (see line 12) → lib/../skills = the real skills/ dir.
 # Was .claude/skills/ — the LRN-042 parasite dir, removed 2026-06-30 by
 # make plugin Step 8.5: green-for-wrong-reason (LRN-077 class).
 dk="$REPO/../skills/darwin-skill"
 if reconcile_oracle_path_present "$dk"; then ok "T6c path_present(darwin-skill) via fs"; else no "T6c path absent"; fi
 echo; echo "=== T7 oracle-sandbox — tree_clean/pushed/msg_committed driven live (not by name) ==="
 OWORK="$(mktemp -d)"
 bare="$OWORK/origin.git"; git init -q --bare "$bare"
 orepo="$OWORK/repo"; git init -q "$orepo"
 git -C "$orepo" config user.email t@t; git -C "$orepo" config user.name t
 git -C "$orepo" remote add origin "$bare"
 echo base > "$orepo/base.txt"; git -C "$orepo" add base.txt; git -C "$orepo" commit -q -m "base commit"
 git -C "$orepo" branch -M main
 git -C "$orepo" push -q origin main   # populates origin/main BEFORE the pushed-oracle checks (else vacuous rc0)
 echo dirty >> "$orepo/base.txt"
 if reconcile_oracle_tree_clean "$orepo"; then no "T7a tree_clean should be dirty"; else ok "T7a tree_clean rc≠0 with a dirty file"; fi
 git -C "$orepo" checkout -q -- base.txt
 if reconcile_oracle_tree_clean "$orepo"; then ok "T7a tree_clean rc0 after restoring clean"; else no "T7a tree_clean should be clean"; fi
 if reconcile_oracle_pushed "$orepo" main; then ok "T7b pushed rc0 when synced"; else no "T7b pushed should be rc0 (synced)"; fi
 echo more >> "$orepo/base.txt"; git -C "$orepo" add base.txt; git -C "$orepo" commit -q -m "ahead commit"
 if reconcile_oracle_pushed "$orepo" main; then no "T7b pushed should be rc≠0 (1 ahead)"; else ok "T7b pushed rc≠0 when 1 ahead of origin"; fi
 if reconcile_oracle_msg_committed "$orepo" "ahead commit"; then ok "T7c msg_committed rc0 for a present message"; else no "T7c msg_committed should find 'ahead commit'"; fi
 if reconcile_oracle_msg_committed "$orepo" "nonexistent-message-xyz"; then no "T7c msg_committed should be rc≠0 for an absent message"; else ok "T7c msg_committed rc≠0 for an absent message"; fi
 rm -rf "$OWORK"
 echo; echo "================  $pass GREEN / $fail RED  ================"
 [ "$fail" -eq 0 ] && exit 0 || exit 1
@@ -0,0 +1,77 @@
 #!/usr/bin/env bash
 # run-review-guards.sh — anti-"partial-fix" regression guards.
 #
 # Genesis: .audit/review-release-1.0.0.md fil rouge. The 9-job series repeatedly
 # fixed ONE instance of a banned pattern and left the twins (A1 trailer, A4 YAML,
 # A5 false attribution, A2 hook drift). Each guard below greps the WHOLE surface
 # for a pattern and REDs if any occurrence subsists — the check that would have
 # caught A1/A4/A5/A2 at make-test time instead of an adversarial review.
 set -uo pipefail
 GREP=/usr/bin/grep                                   # LRN-074: pin grep
 HERE="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 REPO="$(cd "$HERE/../.." && pwd)"
 cd "$REPO"
 pass=0; fail=0; skip=0
 ok()   { echo "GREEN ✓ $*"; pass=$((pass+1)); }
 no()   { echo "RED   ✗ $*"; fail=$((fail+1)); }
 warn() { echo "SKIP  ~ $*"; skip=$((skip+1)); }
 echo "=== review-guards: anti-partial-fix surface checks ==="
 # G1 — banned commit-attribution trailers must not live in our own config surface
 # (the ban is [[no-commit-attribution]]; skills-external/ = gstack submodule, excluded).
 # This guard file is excluded: it names the pattern literally as its own search term.
 if hits=$($GREP -rInE --exclude=run-review-guards.sh 'Co-Authored-By|Claude-Session' agents/ lib/ hooks/ templates/ skills/ 2>/dev/null); then
  echo "$hits"; no "G1 trailer: banned attribution trailer present in tracked config surface"
 else
  ok "G1 trailer: zero Co-Authored-By/Claude-Session in agents|lib|hooks|templates|skills"
 fi
 # G2 — false CLAUDE.md attribution (asserting a user policy CLAUDE.md does not contain)
 if hits=$($GREP -rInE 'per user.{0,5}CLAUDE\.md|User CLAUDE\.md default' agents/ skills/ 2>/dev/null); then
  echo "$hits"; no "G2 attribution: false 'per user CLAUDE.md' policy reference present"
 else
  ok "G2 attribution: zero false CLAUDE.md policy references in agents|skills"
 fi
 # G3 — every agent frontmatter must be strict-YAML valid (degrade if pyyaml absent)
 if python3 -c 'import yaml' 2>/dev/null; then
  if python3 - "$REPO" <<'PY'
 import glob, os, sys, yaml
 root=sys.argv[1]; bad=0
 for f in sorted(glob.glob(os.path.join(root,'agents','*.md'))):
    try: yaml.safe_load(open(f).read().split('---')[1])
    except Exception as e: print("  FAIL", os.path.relpath(f,root), str(e).splitlines()[0]); bad+=1
 sys.exit(1 if bad else 0)
 PY
  then ok "G3 strict-YAML: all agents/*.md frontmatter parse"
  else no "G3 strict-YAML: an agent frontmatter fails yaml.safe_load"
  fi
 else
  warn "G3 strict-YAML: python3+pyyaml unavailable — skipped"
 fi
 # G4 — the reconcile test must stay hermetic (fixtures, never the live registry) [job3 B1]
 if $GREP -q '\.claude/memory' lib/tests/run-reconcile.sh 2>/dev/null; then
  no "G4 hermetic: run-reconcile.sh reads the live .claude/memory registry"
 else
  ok "G4 hermetic: run-reconcile.sh reads fixtures only, not the live registry"
 fi
 # G5 — installed pre-commit hook must match the generator (catches the A2 silent drift:
 # editing _gitflow_emit_pre_commit without re-installing). Degrade if emit-hook absent.
 if emitted=$(bash lib/gitflow.sh emit-hook 2>/dev/null) && [ -n "$emitted" ]; then
  if [ -f .githooks/pre-commit ] && diff -q <(printf '%s\n' "$emitted") .githooks/pre-commit >/dev/null 2>&1; then
    ok "G5 hook-drift: installed .githooks/pre-commit == generator emit-hook"
  else
    no "G5 hook-drift: installed hook diverges from generator (run 'gitflow.sh install-hook')"
  fi
 else
  warn "G5 hook-drift: gitflow.sh emit-hook unavailable — skipped"
 fi
 echo
 echo "================  $pass GREEN / $fail RED / $skip SKIP  (review-guards)  ================"
 [ "$fail" -eq 0 ]
@@ -0,0 +1,78 @@
 #!/usr/bin/env bash
 # ============================================================
 # Structure locks — security-auditor agent + grafts (lot 3)
 # Deterministic greps on load-bearing doctrine: an edit that
 # drops one (pinned rulesets, DEGRADED-still-checks, PROOF,
 # block-HIGH-only, anti-gaming, the two SKILL grafts) reds here.
 # ============================================================
 set -u
 REPO="$(cd "$(dirname "$0")/../.." && pwd)"
 AGT="$REPO/agents/security-auditor.md"
 ONB="$REPO/skills/onboard/SKILL.md"
 ADL="$REPO/skills/audit-delta/SKILL.md"
 PASS=0; FAIL=0
 tf() { # tf <label> <file> <fixed-string>
  if grep -qF -- "$3" "$2" 2>/dev/null; then
    echo "  PASS $1"; PASS=$((PASS+1))
  else
    echo "  FAIL $1 — missing: $3"; FAIL=$((FAIL+1))
  fi
 }
 tr_() { # tr_ <label> <file> <ERE>
  if grep -qE -- "$3" "$2" 2>/dev/null; then
    echo "  PASS $1"; PASS=$((PASS+1))
  else
    echo "  FAIL $1 — no match: $3"; FAIL=$((FAIL+1))
  fi
 }
 tn() { # tn <label> <file> <ERE>  (must NOT match)
  if grep -qE -- "$3" "$2" 2>/dev/null; then
    echo "  FAIL $1 — forbidden match: $3"; FAIL=$((FAIL+1))
  else
    echo "  PASS $1"; PASS=$((PASS+1))
  fi
 }
 echo "── security-auditor.md locks ──"
 if [ -f "$AGT" ]; then
  echo "  PASS agent exists"; PASS=$((PASS+1))
 else
  echo "  FAIL agent missing: $AGT"; FAIL=$((FAIL+1))
 fi
 tr_ "frontmatter name"            "$AGT" "^name: security-auditor$"
 tr_ "tools incl Write (audit)"    "$AGT" "^tools: Read, Grep, Glob, Bash, Write$"
 tf  "verdict grammar"             "$AGT" "SECURITY — VERDICT: PASS | BLOCK(n) | ERROR(<reason>)"
 tf  "ruleset security-audit"      "$AGT" "p/security-audit"
 tf  "ruleset secrets"             "$AGT" "p/secrets"
 tf  "ruleset owasp required"      "$AGT" "p/owasp-top-ten"
 tf  "no config auto stated"       "$AGT" "never \`--config auto\`"
 tf  "no auto login"               "$AGT" "never \`semgrep login\`"
 tf  "secrets to CRITICAL"         "$AGT" "p/secrets | CRITICAL"
 tf  "block ERROR threshold only"  "$AGT" "blocking threshold is ERROR"
 tf  "medium low reported"         "$AGT" "MEDIUM/LOW are REPORTED, never"
 tf  "degraded still checks"       "$AGT" "STILL RUN STEP 3"
 tf  "degraded vacuous pass named" "$AGT" "vacuous pass"
 tf  "anti-gaming suppression"     "$AGT" "NEW suppression comment"
 tf  "anti-gaming micro-gate"      "$AGT" "[gated <date>]"
 tf  "proof mandatory"             "$AGT" "\`PROOF\` is MANDATORY"
 tf  "mute never a pass"           "$AGT" "NEVER a PASS"
 tf  "write rule-locked audit"     "$AGT" "writable path is \`REPORT\`"
 tf  "gate mode write forbidden"   "$AGT" "\`Write\` is FORBIDDEN in this mode"
 tf  "blind no history"            "$AGT" "NEVER receive iteration history"
 tf  "reverify request first"      "$AGT" "re-verify the REQUEST first"
 tf  "max 3 security iters"        "$AGT" "Max 3 security iterations"
 echo "── onboard graft locks ──"
 tf  "onboard dispatches auditor"  "$ONB" "subagent_type=\"security-auditor\""
 tf  "onboard report path"         "$ONB" ".onboard-audit/semgrep.md"
 tf  "onboard verify incl semgrep" "$ONB" "code-clean,cso,semgrep,doc"
 echo "── audit-delta graft locks ──"
 tf  "audit-delta dispatches"      "$ADL" "subagent_type=\"security-auditor\""
 tf  "audit-delta semgrep first"   "$ADL" "FIRST run the semgrep SAST pass"
 echo ""
 echo "security-auditor structure locks: $PASS pass, $FAIL fail"
 [ "$FAIL" -eq 0 ]
@@ -0,0 +1,28 @@
 #!/usr/bin/env bash
 # lib/tests/toggle-external-repo-resolution.test.sh
 #
 # Regression test for J4-20 (BLK-006 class): toggle-external.sh:34 resolved
 # REPO with a LOGICAL `cd` (no -P). Direct invocation via a symlinked path —
 # exactly the real ~/.claude/lib -> <repo>/lib layout — resolves REPO to the
 # SYMLINK's logical parent instead of the physical repo root, so every path
 # derived from it (SKILLS_DIR, DISABLED_DIR) points at the wrong tree.
 set -u
 HELPER_SRC="$(cd "$(dirname "$0")/../.." && pwd)/lib/toggle-external.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; }
 SANDBOX="$(mktemp -d)"
 mkdir -p "$SANDBOX/repo/lib" "$SANDBOX/repo/skills-external/emil-design-eng" \
  "$SANDBOX/repo/skills" "$SANDBOX/home/.claude"
 cp "$HELPER_SRC" "$SANDBOX/repo/lib/toggle-external.sh"
 # mark emil-design-eng ENABLED in the real (physical) repo tree
 ln -s "$SANDBOX/repo/skills-external/emil-design-eng" "$SANDBOX/repo/skills/emil-design-eng"
 # replicate the real ~/.claude/lib -> <repo>/lib symlink
 ln -s "$SANDBOX/repo/lib" "$SANDBOX/home/.claude/lib"
 out="$(bash "$SANDBOX/home/.claude/lib/toggle-external.sh" status emil-design-eng)"
 check T1-repo-resolves-through-symlink "$out" enabled
 rm -rf "$SANDBOX"
 printf 'PASS=%s FAIL=%s\n' "$pass" "$fail"; [ "$fail" -eq 0 ]
--- a/Show More
+++ b/Show More
`@@ -1 +1 @@`
	`ef0d630994fd7ef5f2b84fb66cd6249c493bb8736bcacd4734d7c798125018fb rtk-rewrite.sh`	`82369e32905a8de6dc6b2566c5992f686794a826b2310b15a96e4bd9d25ac7b6 rtk-rewrite.sh`
		`@@ -0,0 +1,2 @@`
							`{"inspectionResult":{"indexStatusResult":{`
							`"verdict":"PASS","coverageState":"Submitted and indexed","lastCrawlTime":"2026-07-01T10:00:00Z"}}}`