# Changelog

All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).

## [Unreleased]

### Fixed

- **Local-vs-cloud inference recommendations corrected against 12 cached YouTube VTT transcripts and the page's own arithmetic** (`guide/ecosystem/local-vs-cloud-inference.md`): removed the unsupported universal claim that CPU offload stays below 5 tokens/sec; separated weight residency from runtime, context, and per-sequence KV-cache memory; corrected Llama 4 Scout to require dual RTX 5090 cards or at least 64 GB aggregate memory rather than one 32 GB card; and changed Llama 4 Maverick's 205.7 GB estimate from "marginal" on 192 GB to not fitting. The hardware picker and both decision diagrams now compare purchase, dedicated rental, and elastic rental instead of contradicting each other on 24/7 workloads. The Hetzner comparison now distinguishes its 300 W RTX PRO 6000 Blackwell Max-Q from the 600 W Workstation Edition used for the purchase price, and labels the 15.7-month figure as a card-only spend crossing rather than a performance-equivalent break-even. AWS and OVH conclusions are bounded to the listed prices and workload shape; Apple power figures are identified as vendor-published; and the cited 0.20 to 0.12 J/token change is stated as a 1.67x efficiency improvement rather than "up to 2x." Added a reproducible benchmark protocol covering weights, runtime headroom, prefill, decode, concurrency, wall power, utilization, and full TCO, with timestamped field observations from four talks. The transcripts are supporting practitioner evidence, not controlled cross-hardware benchmarks.
- **Reading time on `guide/ecosystem/local-vs-cloud-inference.md` corrected from ≈20 to ≈35 minutes**: the ≈20-minute figure was an unverified guess left over from an earlier, much shorter version of the page. Checked how the portfolio computes reading time for blog articles (`florian-portfolio/src/data/reading-time.ts`: 130 wpm for dense technical prose plus 30s per fenced code block, chosen because mainstream defaults like Medium's 270 wpm or dev.to's 275 wpm assume easy prose and undercount content mixing argument with code). Applying that formula as-is to this page's 6,400 prose words and 5 code blocks gives a 52-minute ceiling, but a third of that word count (2,098 words) comes from table cells, which are scanned, not read linearly at prose speed; excluding table words from the per-word rate and giving each of the page's 8 tables a flat 20-second scan allowance instead brings the estimate to ≈38 minutes. Settled on ≈35 minutes, in line with the page's existing "≈" convention. No script exists yet to compute this automatically for guide pages; the portfolio's `reading-time.ts` has no table-aware logic either, so this was a manual one-off calculation, not a new shared utility.
- **Flagship recommendation for the 192-256 GB tier corrected from Llama 4 Maverick to DeepSeek-V4-Flash-0731 in `guide/ecosystem/local-vs-cloud-inference.md`**, per a Slack-relayed suggestion. Verified via Perplexity deep research cross-checked against NVIDIA's own Build model card (`build.nvidia.com/deepseek-ai/deepseek-v4-flash-0731/modelcard`) and DeepSeek's Hugging Face repo: the GA release (July 30-31, 2026) is 304B total / 13B active per NVIDIA's card, not the 284B the earlier preview build (and several secondary sources) still cite; neither DeepSeek nor NVIDIA states why the GA total grew, so a datanorth.ai claim attributing it to a bundled DSpark speculative-decoding module was deliberately not repeated as fact. No official VRAM figure exists for this model; used the actual spread of third-party quantized estimates (Unsloth: ≈103 GB at 3-bit, ≈162 GB at "lossless" 8-bit; Spheron: ≈166 GB at INT4; `llmfit`: 155.8 GB) rather than picking one number and presenting it as authoritative. All of this fits comfortably in both the Mac Studio M5 Ultra (256 GB) and the dual RTX PRO 6000 Blackwell (192 GB combined) configs, unlike Llama-4-Maverick-17B-128E's 205.7 GB, which only fits the 256 GB config and is marginal there. Updated three places: the "What Actually Fits" table's 192-256 GB row, the "Which Local Machine for Which Usage" table's flagship row, and the Decision Framework's "genuinely huge models" paragraph. Llama 4 Maverick is kept as a secondary mention in all three (it still fits, just more tightly) and untouched in the separate Energy Efficiency section, where it remains relevant as Meta's only disclosed training-energy figure on this page.
- **Mermaid decision-tree labels rendering incomplete (only the first line of two-line node text) in `guide/ecosystem/local-vs-cloud-inference.md`**: user-reported screenshot of the "Which Local Machine for Which Usage" flowchart showed every multi-line node (using `<br/>` inside `{...}` and `([...])` shapes) clipped to its first line in a non-GitHub Mermaid renderer, the same class of rendering bug fixed once before on this page's other diagram (2026-08-25, node-label clipping). Root cause not fully isolated (one node with a two-line label rendered correctly while otherwise-similar nodes didn't, ruling out a simple shape or length explanation), so the fix removes the ambiguity instead of chasing the renderer's specific behavior: every node in both Mermaid diagrams on this page ("Which Local Machine for Which Usage" and the pre-existing "Decision Diagram") now uses a single-line label, no `<br/>` anywhere in the file. The ASCII fallback for the usage-picker diagram was reworded to match. No logic, edges, or click targets changed.
- **README.md, AGENTS.md and CLAUDE.md swept against `~/.claude/ANTI_AI.md`, plus a real AGENTS.md/CLAUDE.md desync fixed** (`README.md`, `AGENTS.md`, `CLAUDE.md`): a mechanical scan reusing the `anti-ai-markers.sh` hook's exact patterns found 114 em dashes in README.md, 2 in AGENTS.md, and 2 more in CLAUDE.md (never scanned until AGENTS.md was resynced from it, see below); all in the `label — description` bullet/heading convention. All other hook-checked markers (stereotyped EN phrases, redundant modal stacks, stereotyped openings, vague link labels, hollow evidentiality) were already at zero across all three files, confirmed twice: once via the hook's own grep patterns, once independently via a Python string count after a prior session flagged that `rtk`'s `grep` alias can silently swallow em-dash matches. 112 of README's occurrences converted mechanically to a colon (`**Label** — text` → `**Label**: text`); 8 lines where that produced an awkward adjacent double colon were hand-fixed to a comma or a restructured clause. A `guide-reviewer` agent pass then caught judgment-level markers grep can't: the "not just X" contrast pattern used 6 times as a dramatization tic (kept once, in the intro; rewrote the other 5 as direct claims), the "design your own workflows instead of copy-pasting" slogan repeated near-verbatim 3 times (kept once, replaced the other 2 with a concrete example each), a sentencious 3-imperative closing line, one stray "the tool" right after the sentence had named Claude Code, and a promotional template ("### emoji Title" / Outcome / bullets / "What this means for you" triad) repeated identically across 8 feature-highlight sections with fully interchangeable triad items; 6 of the 8 "What this means for you" lines were rewritten as a single concrete sentence tied to an actual guide link or command, 2 were left as triads whose items were already distinct enough. Separately, AGENTS.md was found to have been corrupted by a naive "Claude" → "Codex" find-replace at some prior point: its title and intro literally claimed "Codex (Anthropic's CLI tool)", which is false (Codex is OpenAI's CLI, this repo documents Claude Code), plus broken paths (`.Codex/` instead of `.claude/`, `code.Codex.com` instead of `code.claude.com`, `guide/core/Codex-releases.md` instead of the real filename) and two facts stale relative to CLAUDE.md (reference.yaml token estimate, resource-evaluation file count), plus a leaked `<claude-mem-context>`/`<!-- lean-ctx -->` block that had no business being committed. Since AGENTS.md and CLAUDE.md are meant to be a verbatim mirror (confirmed: diffing them after normalizing "Codex" back to "Claude Code" showed zero unexpected differences), AGENTS.md was regenerated with `cp CLAUDE.md AGENTS.md` after CLAUDE.md's own 2 em dashes were fixed; both files are now byte-identical and clean. CHANGELOG.md itself still carries 587 more em dashes in dense technical entries where a blanket colon substitution would risk misreading nested clauses; left untouched per explicit user decision, since the hook already blocks new em dashes on any future edit to this file. Not yet committed or pushed.
- **13 whitepapers and 57 recap cards audited against `~/.claude/ANTI_AI.md`, 11 documents corrected, PDFs/EPUBs rebuilt and redeployed** (`whitepapers/{fr,en}/{02-personnalisation,04-architecture,07-guide-reference,11-team-metrics}.qmd` + FR-only-tracked WP00/01/05/06/08/09 on disk, `whitepapers/recap-cards/{fr,en}/{03-permission-modes,c03-xml-prompting-anchors,m01-workflow-quotidien,m03-sessions-continuité,m04-compact-vs-clear,m05-plan-mode,m15-tdd-bdd-sdd,m19-github-actions,m21-debug-methodique}.qmd`, `florian-portfolio/public/guides/`, `florian-portfolio/api/guides.mjs`, landing `src/data/whitepapers-data.ts` + `src/data/recap-cards-data.ts`, landing `public/ebooks/epub/{fr,en}/`): a background workflow (70 parallel agents, one per bilingual document) checked every whitepaper and recap card against the house anti-AI style checklist (em dash, stereotyped openings, rhetorical announcement colons, sentencious closings, decorative emoji, invented personas, hollow buzzwords). 59 of 70 documents were already clean; 11 got real edits, the largest being WP07 (51 fixes, mostly ` --- ` used as an em-dash substitute) and WP11 (20 fixes, rhetorical "X : Y" announcement colons rewritten as plain sentences). Two cross-document patterns were flagged by nearly every agent but deliberately left untouched, pending an editorial decision rather than a per-file fix: the recurring named personas (Antoine, Léa, Karim, Sophie, Marc, Thomas, Julien) used in scenario callouts across the whole series, and the `📖 Pour aller plus loin`/`Further reading` navigational emoji marker repeated identically in all 13 whitepapers. All 10 changed whitepapers had their PDF and EPUB rebuilt (FR+EN, `quarto render --to whitepaper-typst` / `--to epub`); WP11 is PDF-only per its `formats` field. Recap card M03 had its PDF rebuilt (`--to recap-card-typst`), which also required regenerating the Methodology-series ZIP (FR+EN) since M03 is one of its 22 members. New content hashes computed and copied into `florian-portfolio/public/guides/` (whitepapers + card + zip), stale pre-fix files removed; `guides.mjs`'s `GUIDE_MANIFEST` and `recap-methodologie.{fr,en}` zip entries, the landing's `whitepapers-data.ts` (10 `hashedFileFr`/`hashedFileEn` pairs), and `recap-cards-data.ts` (M03's hash pair plus the Methodology series' `hashedZipFr`/`hashedZipEn`) all updated to match. Verified: no stale hash string remains in any of the three manifest files, every new hashed filename resolves to a file that exists on disk, landing site builds clean (430 pages). Not yet committed or pushed in any of the three repos.
- **All 26 whitepaper PDFs and 114 recap-card PDFs (+ 6 series ZIPs) regenerated and redeployed after the content-accuracy fixes below** (`florian-portfolio/public/guides/`, `florian-portfolio/api/guides.mjs`, landing `src/data/whitepapers-data.ts` + `src/data/recap-cards-data.ts`): rendered all 13 whitepapers (`quarto render --to whitepaper-typst`, FR+EN) and all 57 recap cards (`whitepapers/recap-cards/render-recap-cards.sh all`, `--to recap-card-typst`) from the corrected `.qmd` sources, computed sha256-truncated-12 hashes for every output file, copied them into the portfolio's `public/guides/` (whitepapers) and `public/guides/recap-cards/` (cards + 6 new series ZIPs, rebuilt from the freshly hashed card PDFs, T/M/C × FR/EN), and updated all three deployment-manifest files: `guides.mjs`'s `GUIDE_MANIFEST` (26 whitepaper keys + 6 recap-zip keys, used for email download links), the landing's `whitepapers-data.ts` (`const V` bumped `v3.41.1` → `v3.41.3`, all 26 `hashedFileFr`/`hashedFileEn` values), and `recap-cards-data.ts` (`CARD_HASHES_FR`/`CARD_HASHES_EN`, 57 entries each, plus the 6 `hashedZipFr`/`hashedZipEn` fields on `RECAP_SERIES`). Five recap cards (`01`, `03`, `04`, `06`, `25`) and one with a French accent in its filename (`m03-sessions-continuité`) had a landing slug that didn't match their `.qmd` basename (resolved via each card's `card-number` frontmatter field against the landing's `src/content/cheatsheets/*.md` `cardNumber` field, the same mapping `upload-en-pdfs.mjs` already used for the EN-only pass); the accented file now gets a plain-ASCII hashed filename (`m03-sessions-continuite...`) instead of carrying the accent into a URL, unlike its predecessor. Verified after the fact: every filename referenced in all three manifest files resolves to a file that actually exists on disk, zero dangling references. The recap-cards portfolio directory also had 283 orphaned PDF files from prior partial/duplicate deploys (multiple stale hashes for the same card); cleared before repopulating. Not yet committed or pushed in any of the three repos.
- **Remaining 9 of 12 recap-card audit batches (57 pairs total across all batches), content-accuracy corrections not itemized in their own entry below** (`whitepapers/recap-cards/{fr,en}/{01,03,04,06,25,c01-c05,c11,c12,m01,m03,m04,m10-m14,m20-m22,t02,t04,t06-t10,t11-t15,t16-t20,t21,t22}.qmd`; C06-C10, M05-M09, and M15-M19 documented separately below): the same 12-agent audit pass covering the 13 main whitepapers found comparable drift across the 57 recap cards. Notable fixes: a fabricated `Ctrl+J` "open Claude Code" shortcut and a `--no-stream` flag that doesn't exist (01); `--dangerously-skip-permissions` claimed to skip all of `.claude/` when the guide scopes it to `skills/`, `agents/`, `commands/` only, plus a stale threat-db count (v2.15.0/28 CVEs vs the current v2.27.0/118 CVEs) (03); a stale `settings.json` model id (04, 06); a 3-command production pipeline card (M14, "Plan-Validate-Execute") whose body described a completely different, generic workflow (manual Plan Mode) under the real feature's name, rewritten to the actual `/plan-start`/`/plan-validate`/`/plan-execute` pipeline; a card built entirely around `.claudeignore` (T09, "Workspace Hygiene"), which never existed as a real feature per this repo's own CHANGELOG, rewritten around `permissions.deny`; sandbox network config using nonexistent `policy`/`deniedDomains` keys instead of the real `sandbox.network.strictAllowlist` (T16); a full model-pricing table stuck on Sonnet 4.6/Opus 4.8 figures, a missing `xhigh` effort tier, and a "Three Models" title over four listed models (T18); MCP Apps claimed to render inside the CLI when the guide states explicitly it's Desktop/VS Code/ChatGPT only, no CLI support (T12); Sequential Thinking "triggers" listed as fabricated `--think`/`--think-hard`/`--ultrathink` CLI flags that aren't real Sequential Thinking triggers (T13); and a `TaskCreate`/hook stdin-reading pattern with the wrong call shape across several M-series cards. `guide-version`/`version` bumped to `3.41.3` and `date` to `2026-08-24` across all 57 pairs (114 files). Full findings: `claudedocs/whitepaper-content-audit-2026-08-24.md`.
- **Recap cards C06-C10 (FR+EN) audited for content accuracy against the current guide** (`whitepapers/recap-cards/{fr,en}/c0{6,7,8,9}-*.qmd`, `whitepapers/recap-cards/{fr,en}/c10-ai-traceability.qmd`): C06 (Configuration Decision Guide) opened with a fabricated "56% of teams don't use a shared project configuration" statistic that does not exist anywhere in the guide or whitepapers, actually a misapplied copy of the unrelated "56% of sessions" skills-invocation figure from `guide/ultimate-guide.md`; reworded to drop the invented number while keeping the underlying point. C08 (Attack Surface & Threats) claimed Claude Code writes tool calls to `~/.claude/logs/session-*.jsonl`, a path that does not exist for that data; per `guide/ultimate-guide.md`'s Data Sources section, tool calls live in the session transcript at `~/.claude/projects/{encoded-path}/{session-id}.jsonl`, corrected in prose and in the `jq` example command. C08's CVE table was also missing `ADVISORY-CC-2026-002` (deny rules silently dropped past 50 subcommands, fixed in v2.1.90), present in `examples/commands/resources/threat-db.yaml` and `guide/security/security-hardening.md` but absent from the card; added as a row. C10 (AI Traceability) illustrated the `Co-Authored-By` trailer with the superseded `Claude Sonnet 4.6`; corrected to `Claude Sonnet 5`, the current default model. C07 (Team Conventions at Scale) and C09 (Prompt Injection Defenses) verified clean against `guide/security/security-hardening.md` and current CLI flag documentation, no other content issues found. All 10 files' `guide-version` and `version` bumped to `3.41.3`, `date` updated to `Août/August 2026`.
- **Recap cards M05-M09 (FR+EN) audited for content accuracy against the current guide** (`whitepapers/recap-cards/{fr,en}/m0{5,6,7,8,9}-*.qmd`): M06 (Task Management System) and M07 (TodoWrite vs Tasks API) presented the Tasks API and TodoWrite as available by default with no caveat; both are disabled by default on Opus 4.8, Sonnet 5, Fable 5, Mythos 5, and newer models since v2.1.233 (re-enable with `CLAUDE_CODE_ENABLE_TODO_TOOLS=1`), added as a callout to both cards per `guide/core/claude-code-releases.md`. M06's status table listed a `cancelled` status that does not exist in the Tasks API; corrected to the documented `failed` status (used with error metadata for debugging, per `guide/ultimate-guide.md` line 4880). M07 FR claimed the Tasks API became default "depuis v2.1.19" and invented a `--task-manage` CLI flag with no source anywhere in the guide or CHANGELOG; corrected to the actual default-activation version (v2.1.142, per `guide/core/settings-reference.md` and `guide/core/tools-reference.md`) and the flag section rewritten to match the accurate description already present in the EN sibling. M08 (Custom Agents) cited agent persistent memory as introduced in "v2.1.32+" in two places; corrected to v2.1.33 per `guide/ultimate-guide.md` line 7009, and the `model` frontmatter field table was missing the `inherit` value listed in the guide's own field reference. M05 (Plan Mode) and M09 (Slash Commands) verified clean against `guide/ultimate-guide.md` §2.3 and the CC 2.1.3 skills/commands unification note, no content issues found. All 10 files' `guide-version` and `version` bumped to `3.41.3`, `date` updated to `Août/August 2026`.
- **Recap cards M15-M19 (FR+EN) audited for content accuracy against the current guide** (`whitepapers/recap-cards/{fr,en}/m1{5,6,7,8,9}-*.qmd`): M16 (Multi-Agent Topology) invented an unsourced "~7 directories or 50 files" threshold for switching to multi-agent, contradicted by its own table two lines below and by `guide/workflows/agent-teams.md`'s actual line-count metric (10K/50K/100K+ lines); rewrote the paragraph and fixed the table's first row from "<10 répertoires"/"<10 directories" to "~10K lignes"/"~10K lines" to match the guide's real unit. M16 also referenced the superseded Claude Opus 4.8 as the recommended Agent Teams model in three places (context-window note, prerequisites line, dedicated-reviewer guardrail); corrected to Opus 5 per `guide/ultimate-guide.md`'s "Model lineup" note and `guide/workflows/agent-teams.md`'s stated model requirement, and the reviewer ratio "1:4" loosened to "3 to 4" to match the guide's actual "1 reviewer per 3-4 builders." M19 (GitHub Actions) pinned the GitHub Actions example workflow to `claude-sonnet-4-6`, a superseded model id; corrected to `claude-sonnet-5` per `examples/github-actions/claude-code-review.yml`. M15 (TDD/BDD/SDD) illustrated the Tasks API with a fabricated `TaskCreate: { title: ..., blockedBy: [...] }` object-literal call shape; corrected to the documented `TaskCreate("title", { blockedBy: [...] })` positional-argument signature per `guide/ultimate-guide.md` line 17917. M17 (Communication & Trust) and M18 (Event-Driven Agents) verified clean against `guide/workflows/agent-teams.md` and `guide/workflows/event-driven-agents.md` respectively, no content issues found. All 10 files' `guide-version` and `version` bumped `3.41.0` → `3.41.3`, `date` updated to `2026-08-24`.
- **All 13 whitepapers (FR+EN) audited for content accuracy against the current guide, 116 issues found (35 critical), applied across the remaining 9 pairs not itemized in their own entry below** (`whitepapers/{fr,en}/{00,01,03,04,05,06,08,09,10,11}-*.qmd`; WP02, WP07, and WP12 documented separately below since their agents wrote their own entries): a background workflow (13 parallel agents, one per whitepaper pair, comparing each file against `guide/**`, `CHANGELOG.md`, and `guide/core/claude-code-releases.md`) found the same class of drift repeated across the series: Opus 4.8 still presented as the current default model where Opus 5 (v2.1.219) has replaced it (WP00, WP04); sub-agent nesting depth stated as "5 levels" where the current default is 3 since v2.1.219, after a brief drop to 1 in v2.1.217 (WP00, WP04); `--safe-mode` mischaracterized as adding validation before risky actions when it actually disables all customizations for troubleshooting (WP00); a fabricated `MultiEdit` tool listed among the 10 core native tools, which does not exist in the current 40-tool set (WP04); `TodoWrite` presented with no caveat despite being disabled by default on Sonnet 5/Opus 4.8/Fable 5 and newer since v2.1.233 (WP04); a fabricated `--no-human-approval-required` CLI flag and a wrong `settings.local.json` path (WP05); three dead internal links using pre-reorganization paths, `guide/data-privacy.md` and `guide/ai-traceability.md` instead of their `guide/security/` and `guide/ops/` locations (WP06); Agent Teams' "all teammates run the same model" constraint going unstated (WP08); a dead link to a nonexistent `guide/roles/team-deployment.md` page (WP11); and assorted stale line/template/hook counts and version stamps throughout. `wp-version` bumped by one patch per fixed pair, `version` synced to `3.41.3`, `date` bumped to 2026-08-24 where the file already carried a `date` field. Full findings and fixes: `claudedocs/whitepaper-content-audit-2026-08-24.md` (not checked in, gitignored working doc).
- **Footer version stamps desynced from frontmatter across 4 whitepaper pairs** (`whitepapers/{fr,en}/{01,07,09,12}-*.qmd`): the content-accuracy fix pass above bumped each file's YAML frontmatter `version` to `3.41.3`, but 8 files (WP01, WP07, WP09, WP12, both languages) carry a second, hardcoded `*Version X.Y.Z | Month Year*` line in their closing footer that several agents left at the old `3.41.1 | Juillet/July 2026` value. Synced all 8 to `3.41.3 | Août/August 2026`, preserving WP07's and WP09's additional parenthetical/date-tracking text.
- **WP07 (Reference Guide) content-accuracy corrections** (`whitepapers/fr/07-guide-reference.qmd`, `whitepapers/en/07-reference-guide.qmd`): the model table omitted Claude Opus 5 entirely and labeled the now-superseded Opus 4.8 as current, corrected against `guide/ultimate-guide.md`'s "Model lineup July 2026" note and CHANGELOG v2.1.219 (Opus 5 added as `opus`, May 2026; Opus 4.8 relabeled previous-gen, default on Bedrock/Vertex/AWS only). Claude Fable 5's knowledge cutoff was listed as "June 2026" (the whitepaper's own authoring date, not the model's actual cutoff), corrected to January 2026 per the guide's knowledge-cutoff table. Sub-agent nesting depth was stated as "5 levels" in three places; per CHANGELOG and `guide/core/claude-code-releases.md` nesting was disabled by default in v2.1.217 and restored to depth 3 (not 5) in v2.1.219, corrected in the body text and both closing-footer version summaries. The `/branch` row said it "replaces `/fork`" with no further context; `/fork` reappeared in v2.1.212 with a distinct meaning (copies the conversation into a separate background session, not a parallel timeline), noted inline. EN's hook-events table and lead sentence were missing 3 of 30 documented events (`PostToolBatch`, `UserPromptExpansion`, `MessageDisplay`) that the FR sibling already listed; added to match FR and `guide/core/hooks-events-reference.md`, and the "30 events total" figure now stated explicitly in both languages. EN's synthesis blurb cited fabricated chapter numbers ("Ch.8b Migration, Ch.9 IDE...") that don't match the document's actual chapter order; dropped in favor of the FR phrasing (topic list, no numbers). Guide line count and template count were each cited under three different stale figures within the same document (22,000/19,000/26,600 lines; 189/232/271 templates); harmonized on the current figures (~26,600 lines, 271 templates) throughout both files. Both frontmatters bumped `version` `3.41.1` → `3.41.3` (current guide version) and `wp-version` `1.4.1` → `1.4.2` (patch, content correction only, no new sections).
- **WP07 (Reference Guide) leftover placeholder in the Opus 4.8 knowledge-cutoff column** (`whitepapers/fr/07-guide-reference.qmd`, `whitepapers/en/07-reference-guide.qmd`): the prior WP07 fix (above) relabeled Opus 4.8 as previous-gen but left "Actuel"/"Current" in the Knowledge Cutoff column, a value that doesn't fit that column and doesn't match any date. Corrected to "Janvier 2026"/"January 2026" per `guide/ultimate-guide.md`'s knowledge-cutoffs table (line 3032). Both frontmatters bumped `wp-version` `1.4.2` → `1.4.3` and `date` `2026-07-02` → `2026-08-24`; `version` already at `3.41.3`.
- **WP02 (Customization) content-accuracy corrections and FR/EN parity** (`whitepapers/fr/02-personnalisation.qmd`, `whitepapers/en/02-customization.qmd`): the SKILL.md frontmatter examples and field table listed a fabricated `agent: specialist`/`general` field not present in `guide/ultimate-guide.md` §5.2's field set; removed from both the generic template and the security-guardian example, replaced with real fields (`model: haiku`, `effort: low`). The `context: fork` explanation presented fork isolation as unconditional protection for destructive operations; added the documented limitation from §5.2 that fork is ignored when a skill is invoked via the Skill tool from agent code, and only activates for a user-typed slash command. The agent frontmatter's `memory` field was described and exemplified as an inline pre-populated text block (`memory: |` followed by prose); corrected to its real scope-selector syntax (`memory: project`) per §4.2, mapping to `~/.claude/agent-memory/<name>/`, `.claude/agent-memory/<name>/`, or `.claude/agent-memory-local/<name>/`. The "3 Scopes of Memory" table conflated Auto-Memory (`guide/core/memory-systems.md` §2.2) with the Agent Memory frontmatter field and got both wrong: no `.claude/MEMORY.md`/`.claude/MEMORY.local.md` files exist, Auto-Memory actually stores at `.claude/memory/MEMORY.md` (project) and `~/.claude/projects/<path>/memory/MEMORY.md` (global), with no gitignored third scope; split into two accurate sections, one for Auto-Memory storage paths and one for the Agent Memory frontmatter's real three directory-backed scopes. Agent Teams' experimental-status callout mislabeled it "community-discovered" with "no official Anthropic support"; per `guide/workflows/agent-teams.md` it is an official Anthropic research preview (v2.1.32+, flag `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1`), corrected while keeping the production-caution advice. `model: opus-4.6` (a stale pinned version) replaced with the generic `opus` alias in both the frontmatter field table and the Model Selection table, matching §4.2's real value set and the current Opus 5 default (v2.1.219). FR alone still recommended a separate `.claude/commands/` folder in its final "Structure Recommandée" tree and Git Rules line, contradicting the same document's own "commands live in skills/ since CC 2.1.3" statement earlier; replaced with the unified `skills/tech/commit/SKILL.md` tree already used by the EN sibling, and dropped `commands/` from the committed-paths list. FR alone is still missing the Dynamic Workflow row in the Agent vs Skill vs Command table and the Auto Dream memory-consolidation paragraph that EN already has; left unaddressed, that gap is a parity backfill, not a content-accuracy correction, and was out of scope for this pass. Both frontmatters bumped `version` `3.41.1` → `3.41.3` (current guide version), `wp-version` `1.5.1` → `1.5.2` (patch, content correction only, no new sections), and `date` `2026-07-02` → `2026-08-24`.
- **WP12 (Agent Engineering) content-accuracy corrections and FR/EN parity** (`whitepapers/en/12-agent-engineering.qmd`, `whitepapers/fr/12-agent-engineering.qmd`): the EN closing footer read "Version 3.41.0 | May 2026", contradicting the file's own frontmatter (`3.41.1`) and the FR sibling's footer ("Version 3.41.1 | Juillet 2026"), fixed to "Version 3.41.1 | July 2026". EN also compressed the FR "Claude Code: Native Workflow Primitives" subsection (three engineering guarantees, the `ultracode`/`workflow` rename in v2.1.160, and the Agent tool/Skill/Workflow decision rule) into a single sentence buried in "Multi-Agent Frameworks: Build vs Use", giving EN readers materially less operational guidance than FR on the same feature; added the missing subsection to EN, translated from FR, and trimmed the now-redundant compressed sentence to a cross-reference. Both frontmatters bumped `version` `3.41.1` → `3.41.3` (current guide version) and `wp-version` `1.1.0` → `1.1.1` (patch, content correction only, no new sections).

### Documentation

- **Claude Code releases tracking updated to v2.1.246** (`machine-readable/claude-code-releases.yaml`, `guide/core/claude-code-releases.md`, `mcp-server/content/claude-code-releases.yaml`, `mcp-server/package.json`): three new versions condensed from `2.1.241`. v2.1.243 adds a `/usage` Loops breakdown (per-loop run count, tokens, tokens per run, last run), a `modelPicker` setting to curate the `/model` picker with a labeled model list, `promptCacheTtl`/`subagentPromptCacheTtl` settings to keep a 1-hour prompt cache on the main conversation while subagents stay at 5 minutes, and a keyless `/login` sign-in via Anthropic Console for organizations that don't allow API keys. v2.1.245 is a single-fix release for a startup crash on Linux distributions shipping glibc 2.44 (Arch, CachyOS, Fedora Rawhide). v2.1.246 adds a startup warning for Bash allow rules with a wildcard before the subcommand, an Auto mode tab in `/permissions`, fixes the Write tool reporting "Out of memory" or freezing after overwriting a very large file, and makes non-interactive sessions auto-continue a response cut off mid-stream. Release dates for all three (2026-08-24, 2026-08-25 ×2) came from the npm registry's publish timestamps, since the upstream CHANGELOG carries no dates; versions 2.1.242 and 2.1.244 exist in the sequence but published no changelog entries. The landing repo's `src/data/releases.ts` was updated in the same pass (three new entries prepended, `latest: true` moved from v2.1.241 to v2.1.246); no RSS entry was added since the landing's `rss.xml.ts` already emits one from `releases.ts` and a manual entry would duplicate it. `mcp-server` bumped `1.2.12` → `1.2.13` and rebuilt; `reference.yaml` and `llms.txt` were unchanged so their `mcp-server/content/` copies were left as-is. No `npm publish` run.

- **Claude Code releases tracking updated to v2.1.241** (`machine-readable/claude-code-releases.yaml`, `guide/core/claude-code-releases.md`, `mcp-server/content/claude-code-releases.yaml`, `mcp-server/content/reference.yaml`, `mcp-server/content/llms.txt`, `mcp-server/package.json`): four new versions condensed from `2.1.237`. v2.1.239 is the notable one, a fix for Bedrock streaming behind a proxy that stripped the response `Content-Type` header and silently re-ran every turn non-streaming, doubling billed API calls, alongside Windows cross-session `SendMessage`/`ListAgents`, a `/cost` line item for the 1.1x data-residency inference premium, and `/claude-api upgrade` for migrating the Python SDK off 0.x. v2.1.238 adds a `keybindingFlavor: "readline"` setting, plugin marketplace `headersHelper` for minting short-lived fetch headers, a fix for unbounded memory growth from retained subagent tool results in long sessions, and `self-hosted-runner` graceful-shutdown draining plus proxy authorization headers. v2.1.240 and v2.1.241 ship as bug-fix-only releases with no published highlight detail. Release dates for all four (2026-08-20 through 2026-08-22) came from the npm registry's publish timestamps, since the upstream CHANGELOG carries no dates. `mcp-server` bumped `1.2.10` → `1.2.11` and rebuilt; no `npm publish` run.

### Added

- **3 hand-drawn illustrations added to `guide/ecosystem/local-vs-cloud-inference.md`** (`guide/images/local-vs-cloud-{entry-tier,decision-tree,hetzner-math}.webp`): user-generated (Nano Banana Pro, Bold Guy pencil-on-cream-paper style) from prompts drafted against this page's own verified content, then reviewed for accuracy against the source text before embedding. Two rounds of correction preceded the final assets: a 4th image (a cover for the whole page) rendered as a generic corporate dashboard with fabricated pricing charts instead of the requested hand-drawn style, and was dropped rather than published; a 5th generation of the Hetzner comparison had two clipped text strings ("THE ONE EXCEPTI", "cheaper, even used e") from box-overflow truncation, fixed by shortening the prompt's text and regenerating before use. Placed each image next to the exact paragraph it illustrates rather than clustering them: `local-vs-cloud-entry-tier.webp` under the Thirteen Comparable Hardware Configurations intro (illustrates the 16 GB entry tier), `local-vs-cloud-decision-tree.webp` under the Which Local Machine for Which Usage intro (a simplified 3-branch version of that section's own Mermaid decision tree), and `local-vs-cloud-hetzner-math.webp` directly after the "renting beats buying" paragraph in One-Year Cost Projections. Source files compressed from 550-780 KB JPEG to 50-71 KB WebP (`cwebp -q 80 -resize 1400 0`) to match this repo's existing `guide/images/` file sizes (the one prior image there is 42 KB); `sips` was tried first but failed on this sandbox's tmp-directory write restriction, `cwebp` was already installed and worked. Images are gitignored nowhere else in the pipeline: `guide/images/*` gets copied verbatim into the landing repo's `public/guide/images/` by `prepare-guide-content.mjs`, and the `../images/...` relative paths resolve correctly once served at `/guide/local-vs-cloud-inference/`.
- **New section: Energy Efficiency by Model Architecture, in `guide/ecosystem/local-vs-cloud-inference.md`**: follow-up to the hardware-level Power Consumption section, answering a distinct question the user surfaced (does model architecture itself affect energy per token, and what do labs disclose). User ran an independently-drafted Perplexity research prompt and pasted the result; every load-bearing claim was independently re-verified before publishing, not taken on trust. Verified directly: Meta's official Llama 4 model card (`github.com/meta-llama/llama-models`) does report training GPU-hours and CO2eq (Scout: 5.0M GPU-hours, 1,354 tons location-based CO2eq; Maverick: 2.38M GPU-hours, 645 tons), the only lab on this page's model list that discloses anything at all; DeepSeek's own model card does state the 27%-FLOPs/10%-KV-cache claim against DeepSeek-V3.2 verbatim; ML.Energy's v3.0 leaderboard blog does contain the exact Qwen 3 30B-A3B-vs-32B (3.56x), 235B-A22B-consumes-more, and FP8-batch-size-dependent (up to 56% worse at batch 8-16, 11% better at batch 65-256) figures; and the EnergyLLM-Bench Mixtral-8x7B figure (271.44 J/token, an order of magnitude above dense Mistral-7B's 4.59 J/token) was cross-checked via an independent web search after the source PDF blocked direct fetch, since it was the single most surprising number in the batch. Also confirmed Know Your Compute's Llama 4 Wh-per-query estimates explicitly self-label as derived, not official. The section's throughline: MoE's active-parameter ratio reduces arithmetic per token but does not reliably predict measured energy (Qwen 235B-A22B and Mixtral-8x7B both demonstrate the opposite), and quantization's energy benefit is real but batch-size-dependent rather than a fixed percentage. New `local_vs_cloud_model_efficiency` deep_dive key and `energy-efficiency-by-model-architecture` section_maps anchor added (both reference.yaml copies). Index coverage 95/95, no new validation failures.
- **New section: Power Consumption, in `guide/ecosystem/local-vs-cloud-inference.md`**: a colleague-relayed question asked why the page had no watts-per-token or watts-per-hour figures. Deep research confirmed the honest answer: none of OVHcloud, AWS, Lambda, GMI Cloud, or Hetzner publishes per-token or per-request energy data, and neither Anthropic nor OpenAI discloses it for Claude or GPT-5.6, an industry-wide gap rather than one specific to this page. The new section separates three tiers of evidence: official TDP/board-power specs (RTX 5090, RTX PRO 6000 Blackwell variants, Ryzen AI Max+ 395, MacBook Pro M5, DGX Spark, all sourced to TechPowerUp/NVIDIA/AMD/Apple), independently measured system power (Apple's own wall-measured Mac Studio figures, ServeTheHome's measured 60-90W DGX Spark LLM-inference draw), and the two real per-token energy sources found (ML.Energy's measured 0.20 to 0.12 J/token improvement for Llama 3.1 8B on H100 across software generations, and Neuralwatt's published Wh-per-request pricing for GLM-5.2, explicitly flagged as a live figure that moved between two checks the same day, 2.29/1.73 Wh versus 1.96/1.17 Wh for the standard/fast variants). Deliberately excluded a set of "illustrative" joules-per-token estimates the research process itself generated for RTX 5090, RTX PRO 6000, DGX Spark, and a hypothetical Claude/GPT-5.6 cluster, all built on throughput assumptions invented by the research pass itself rather than measured, since publishing them would fail this page's own sourcing standard. Points readers at TokenPowerBench (verified real GitHub repo, arXiv paper) for self-measurement and gives the underlying formula (joules/token = watts / tokens-per-second) so nobody has to trust a number without knowing its provenance.

### Fixed

- **"MoE full weight is not optional" claim corrected in `guide/ecosystem/local-vs-cloud-inference.md`**: user-relayed Slack discussion surfaced [FlashML-org/FreeToken](https://github.com/FlashML-org/FreeToken) (verified: 7,342 stars, Apache 2.0, pushed same day, arXiv paper at arxiv.org/abs/2608.16157 with credible co-authors including Song Han and Ion Stoica), which contradicted a claim this page had published: that MoE experts have no shortcut around full-VRAM residency. Checked llama.cpp's own GitHub docs and issue discussions to confirm independently: its `--n-cpu-moe`/`--cpu-moe` flags do keep MoE expert tensors in CPU RAM while streaming only the per-token active experts to GPU over PCIe, a real (if not literal every-expert-loaded-nowhere) shortcut. FreeToken implements a more elaborate version (bandwidth-adaptive hybrid PCIe-fetch/CPU-compute split, LRU expert caching, calibrated via `ft bench bw`), and its README's own claim of 3-4x faster decode / 6-30x faster prefill than Ollama is cited as vendor-reported, not independently verified. Rewrote the paragraph to state the real constraint (full expert set must be resident in system RAM, not VRAM, with only active experts streamed) rather than the previous absolute claim, and softened the "does not fit" verdicts for GLM-5.2 and DeepSeek-V4-Pro accordingly: both become usable with enough system RAM and a CPU-offload-capable engine, just not via naive full-VRAM loading. Included Slack-relayed, explicitly-labeled-unverified community throughput numbers (39.3 tok/s on an 8GB laptop GPU + 64GB RAM for a 35B MoE; 22 tok/s on an RTX 5090 + 192GB RAM for DeepSeek-V4-Flash 284B; 14.9 tok/s on a 96GB workstation GPU + 512GB RAM for GLM-5.2 753B). Also fixed a stale reference in the same paragraph still citing Kimi-K3 at "5.5T parameters," missed in an earlier correction pass that had already fixed the same figure in the table above it (the real, officially-confirmed figure is 2.8T).
- **Deployed page showed stray strikethrough text in `guide/ecosystem/local-vs-cloud-inference.md`**: user-reported screenshot from the live site showed a full sentence rendered struck through. Root cause: the page used a bare `~` (tilde) throughout as an "approximately" marker (91 occurrences, e.g. `~€13,578`), and the landing site's Markdown renderer treats a single `~` as a strikethrough delimiter rather than requiring GFM's double `~~`, so any paragraph containing two unrelated `~`-prefixed numbers had everything between them rendered struck through. Replaced every occurrence with the unicode `≈` character, which carries the same "approximately" meaning and isn't a Markdown control character in any renderer. No numbers or meaning changed, purely a character substitution.

### Added

- **Entry-tier hardware (16-32 GB) and a new "Which Local Machine for Which Usage" section added to `guide/ecosystem/local-vs-cloud-inference.md`**, sourced from a Slack-relayed request ("add the very small 16GB VRAM configs") plus a same-day product launch the user flagged from apple.com/fr/mac-mini. Three new rows added to what is now the **Thirteen** Comparable Hardware Configurations table (renamed from "Ten"): the Mac mini M6 (announced August 25, 2026, shipping September 22; verified via 9to5Mac's launch coverage and MacGeneration's French pricing, 12-core CPU/12-core GPU, 16-32 GB unified, 170 GB/s bandwidth, EUR base price 1,049 EUR at 16 GB/256 GB confirmed, the ~1,500 EUR figure at the 32 GB max estimated by scaling Daring Fireball's confirmed $400 USD BTO upgrade, since Apple's per-configuration French pricing pages weren't fetchable directly), the Mac mini M5 Pro (24-64 GB unified, 307 GB/s bandwidth, EUR base 1,999 EUR at 24 GB/512 GB confirmed, ~3,000 EUR estimated at the 64 GB max from the confirmed $1,000 USD BTO), and a workstation built around the RTX 5060 Ti 16 GB (4,608 CUDA cores, 448 GB/s, $429 MSRP per VideoCardz's launch coverage, ~590-730 EUR street price per BestValueGPU's August 2026 tracker). Ran `llmfit --memory 16G --ram 32G info` against candidate models for this tier: `openai/gpt-oss-20b` (OpenAI's own model card confirms 21B total/3.6B active, Apache 2.0) fits comfortably at 11.0 GB, while `Qwen/Qwen3.8-27B` only reaches this tier at a heavier Q3_K_M quant, marginal at 99% memory utilization; added as a new row in What Actually Fits: Named Models, ahead of the existing 32 GB row. The new Which Local Machine for Which Usage section reorganizes the page's existing hardware and model-fit data by use case instead of by price, with a table (7 usage archetypes from "trying it out under 2,000 EUR" to "24/7 production, rent don't buy") and a Mermaid decision tree (plus ASCII fallback) walking from usage question to specific configuration, cross-linking back into the existing Hardware Configurations and Named Models sections rather than duplicating their numbers. New `local_vs_cloud_which_machine` deep_dive key and `which-local-machine-for-which-usage` section_maps anchor added (both reference.yaml copies); `local_vs_cloud_hardware_configs`'s anchor updated from `#ten-comparable-hardware-configurations` to `#thirteen-comparable-hardware-configurations`, and its two internal Mermaid `click` references in the existing Decision Diagram updated to match. Index coverage 95/95, no new validation failures (the 17 pre-existing CI failures are unrelated to this page).
- **New section: Switching Providers at the CLI Level, in `guide/ecosystem/local-vs-cloud-inference.md`**: added a pointer to [cc-copilot-bridge](https://ccbridge.bruniaux.com/) (`ccbridge.bruniaux.com`, v1.5.3, v2 in progress), a Claude Code CLI routing layer distinct from this page's hardware/API economics: it switches which backend Claude Code talks to (`ccd` Anthropic direct, `ccc` GitHub Copilot, `cco` local Ollama) without touching the cost or hardware-fit questions the rest of the page answers. Noted the project's own documented caveat that the Copilot route uses a reverse-engineered API that may violate GitHub's Terms of Service. New `local_vs_cloud_cli_bridge` deep_dive key and `switching-providers-at-the-cli-level` section_maps anchor added (both reference.yaml copies). Index coverage 95/95, no new validation failures.
- **Hetzner and GMI Cloud added to the GPU rental comparison in `guide/ecosystem/local-vs-cloud-inference.md`**, sourced from a user-relayed Slack conversation with two unverified pricing claims, both checked against official pages before publishing. Quentin's claim of "~1,500 EUR/month" for a 96 GB RTX GPU at Hetzner did not hold up: Hetzner's own press release for the `GEX131` (RTX PRO 6000 Blackwell Max-Q, 96 GB) lists **889 EUR/month** (1.4247 EUR/hour, excl. VAT); the higher figure appears only on a third-party reseller page, not hetzner.com. Thomas's GMI Cloud claim ("H100 same price, +300 EUR/month for H200") was directionally right but the actual gap is larger: GMI Cloud's own pricing page confirms $2.00/GPU-hour for H100 and $2.60/hour for H200, a difference of roughly $438/month at full-time usage, not $300-equivalent. Added both to the Cloud GPU Rental Pricing table and, where the billing model allows a fair comparison (GMI Cloud is elastic hourly, Hetzner is a flat-rate dedicated server), to the One-Year Cost Projections table. This changes one of the page's own conclusions: a full year of Hetzner's GEX131 (10,668 EUR) costs less than buying the same RTX PRO 6000 Blackwell card outright (~14,000 EUR), overturning the page's general "buy wins at 24/7 usage" pattern specifically for that GPU tier. GMI Cloud's H100 rate also undercuts OVHcloud's, the previous cheapest elastic-cloud H100 option on this page. The Decision Framework's "heavy or 24/7 usage, buy" bullet was qualified accordingly.

### Fixed

- **Kimi K3 parameter count corrected from 5,527B to the officially-confirmed 2,800B in `guide/ecosystem/local-vs-cloud-inference.md`**: the previous commit's model-generation update trusted `llmfit info "moonshotai/Kimi-K3"` at face value (5,526.6B total, no MoE expert breakdown exposed), a scrape error. A second verification pass against Moonshot AI's own GitHub repo (`github.com/MoonshotAI/Kimi-K3`) and product page confirmed the real figure: 2.8T total parameters, 16 of 896 experts active per token (~50B active, calculated, not officially stated as a round number). The full-weight VRAM requirement was recalculated by extrapolating from DeepSeek-V4-Pro-0813's own confirmed VRAM-per-parameter ratio (845.4 GB / 1,650.5B) rather than trusting `llmfit`'s wrong entry for this specific repo, landing at roughly 1,430 GB instead of the previously published 2,831 GB. Also corrected: DeepSeek-V4-Pro-0813's active-parameter count is officially confirmed at 49B (Hugging Face model card), not left unstated as in the prior pass, and its GA release date (August 13, 2026) is now confirmed via Reuters rather than inferred from the `-0813` filename suffix alone. Also corrected a false claim in the prior CHANGELOG entry: GLM-5.3 does exist as an official Zhipu/Z.ai announcement (August 17, 2026), sharing GLM-5.2's base architecture and parameter count with a staged, coding-focused post-training upgrade; it was not a hallucination the way "Muse Glimmer" and the specific "GLM-5.3 as a distinct 753B base" framing were. Added a "Data Snapshot Date" pointer to two continuously-updating trackers, [llm-stats.com](https://llm-stats.com/llm-updates) and [benchlm.ai](https://benchlm.ai/), for readers who need current numbers past this page's fixed snapshot.
- **"What Actually Fits: Named Models" updated to the current model generation in `guide/ecosystem/local-vs-cloud-inference.md`**: user feedback flagged the reference models (Llama 3.1/3.3 70B, Qwen2.5, Mixtral 8x22B, DeepSeek-V3) as dated. Replaced with the August 2026 generation, each verified via `llmfit search` against real HuggingFace repos and queried on the official lab's own org (not a third-party quant mirror) with `llmfit info`: `Qwen/Qwen3.8-27B` (dense, 27.8B, Apache 2.0), `meta-llama/Llama-4-Scout-17B-16E-Instruct` (108.6B total MoE, 1 of 16 experts active), `meta-llama/Llama-4-Maverick-17B-128E-Instruct` (401.6B total MoE), `zai-org/GLM-5.2` (753.4B total MoE, MIT), `deepseek-ai/DeepSeek-V4-Pro-0813` (1,650.5B total MoE, MIT), `Qwen/Qwen3.8-2.4T-A95B` (2,446.2B total MoE), and `moonshotai/Kimi-K3` (5,526.6B total). A first Perplexity research pass had returned several fabricated or unconfirmed names (a "Muse Glimmer 30B" from Meta, "GLM-5.3", "DeepSeek-V4-Pro" claimed as 49B active) sourced from low-authority blog aggregators rather than official pages; cross-checking every claimed name against `llmfit`'s HuggingFace-scraped database caught this before publication (GLM-5.3 returns zero results, the real current GLM is 5.2 at 753.4B, matching the number Perplexity had misattributed to the fake 5.3). Also added a technical clarification the previous table lacked: for MoE models, `llmfit`'s "active VRAM" figure (the per-token compute cost) is not a substitute for the "full weight" figure (the actual deployment requirement), since routing picks a different expert combination per token and the entire expert set must stay resident. Updated the frontier-gap framing (DeepSeek-V3's 350.6 GB grew to DeepSeek-V4-Pro's 845.4 GB) and the Decision Framework's `405B` reference to Llama 4 Maverick's confirmed 401.6B. `llmfit`'s own data quality has gaps worth flagging for future updates: `Llama-4-Maverick-17B-128E-Instruct` (128 experts per its name) and `Llama-4-Scout-17B-16E-Instruct` (16 experts) both report an identical "1 active / 16 total" MoE breakdown, an apparent scrape error not corrected in this pass since it doesn't affect the full-weight figures actually cited.
- **Decision diagram node labels shortened to stop clipping in `guide/ecosystem/local-vs-cloud-inference.md`**: user-reported screenshot showed the diamond node "Data must never leave your infra?" rendering as "Data must never" with the second `<br/>` line dropped, and several rectangle nodes (buy/rent/license recommendations) similarly cut short, in a non-GitHub Mermaid renderer. Shortened every multi-line node label (`Data must stay on your own infra?`, `Need over 70B or max quality?`, `Committed for over a year?`, and the three recommendation nodes) so each line is shorter and less likely to overflow a fixed-size node regardless of renderer, without changing the diagram's logic or the `click` target anchors. ASCII fallback updated to match.

### Added

- **Decision diagram added to Local vs Cloud LLM Hardware and Inference Economics** (`guide/ecosystem/local-vs-cloud-inference.md`, `machine-readable/reference.yaml`, `mcp-server/content/reference.yaml`): a Mermaid flowchart (plus ASCII fallback, matching the `guide/diagrams/` convention and Bold Guy palette) walking the license-vs-local-vs-cloud-rental choice through the same two gates the page's prose Decision Framework already used, data sovereignty first, then usage pattern and model size, so the same conclusion (buy for 24/7 or >70B/405B, rent for sustained 4-8h/day, license a managed API for light or bursty usage) is reachable visually, not only by reading four paragraphs. Placed as its own section directly before Decision Framework, both in the page's own TOC and as a new `local_vs_cloud_diagram` `deep_dive` key and `decision-diagram` section_maps anchor. Index coverage 95/95, no new `validate-reference-yaml.py --ci` failures.
- **New page: Local vs Cloud LLM Hardware and Inference Economics** (`guide/ecosystem/local-vs-cloud-inference.md`, `guide/README.md`, `machine-readable/reference.yaml`, `mcp-server/content/reference.yaml`): a new ecosystem page answering when a local hardware purchase beats cloud GPU rental or per-token API pricing for running open-weight models in the 70B to 400B+ range. Ten comparable complete-system builds (CPU, memory, GPU, storage together, not bare GPUs) sized with `llmfit` (MIT CLI, `brew install llmfit`), from a $3,999 AMD Ryzen AI Halo box up to a ~$32,000 dual RTX PRO 6000 Blackwell workstation, each mapped to the largest named flagship model (Llama, Qwen, Mixtral, DeepSeek) that actually fits at a given quantization, not just the largest model by raw parameter count that `llmfit`'s database happens to surface. Documents a real methodological limit found while building this page: `llmfit`'s `--memory`/`--ram` flags correctly recompute capacity for a simulated hardware target, but the tool stays locked to the host machine's detected backend for its speed model, so tokens/sec estimates for a simulated Nvidia GPU run while testing on Apple Silicon are Metal-derived and not trustworthy, only the memory-capacity numbers are. Cloud GPU rental pricing compared across OVHcloud, AWS, Lambda, and RunPod, with one-year cost projections at 4h/day, 8h/day, and 24/7 usage against the ten local builds; AWS comes out priced for a different use case entirely (its own H100 24/7 estimate already funds close to three dual-RTX-PRO-6000 workstations in a single year). Also covers measured cloud API throughput for Claude Opus 5 and Sonnet 5 against OpenAI's GPT-5.6 family (Sol, Terra, Luna, launched July 9, 2026), including a correction surfaced mid-research: Claude Opus 5's real production-telemetry average (about 26 tokens/sec, LLM-Benchmarks) is well below the lighter-preset figure (about 55-80 tokens/sec) that other trackers publish, and explains structurally why cloud and local tokens/sec are not the same measurement (queueing and batching, invisible reasoning tokens inflating time-to-first-token, and cloud frontier models running full-precision at a scale local quantized deployments never reach). Closes with a decision framework by usage pattern. Index coverage 94/94 (was 93/93), `validate-reference-yaml.py --ci` still reports its pre-existing 17 bare-line-number drift failures, none newly introduced by this page.
- **`/auto-mode-setup` documented in the Auto Mode section** (`guide/ultimate-guide.md` §1.4, new subsection under "Auto Mode (all plans, v2.1.114+)"): the guide covered Auto Mode's classifier and `autoMode.environment`/`allow`/`soft_deny`/`hard_deny` config but never mentioned the wizard that drafts those entries. Content verified against `code.claude.com/docs/en/auto-mode-config` directly (fetched, not inferred), after a Perplexity Deep Research pass surfaced a plausible-looking but unverifiable `posture=personal|open-source|enterprise|mixed` parameter set sourced only from a third-party binary-extraction repo (`Piebald-AI/claude-code-system-prompts`), not from Anthropic's own docs, so it was left out. Covers what the wizard always scans versus its two opt-in scans, the accept/discard-as-a-whole review flow, the "Teach auto mode about your environment?" dialog trigger, the `skillOverrides: {"auto-mode-setup": "off"}` disable path (it's a built-in command, not a bundled skill, so `disableBundledSkills` doesn't cover it), and the four `claude auto-mode` inspection subcommands (`defaults`, `config`, `critique`, `reset`). Requirements: Pro/Max/Team plan, v2.1.228+ (v2.1.233+ on native Windows), not available on Claude Code on the web. No new `deep_dive` key added, the addition lives inside the existing `permission_modes` section already indexed at `guide/ultimate-guide.md#14-permission-modes`. `validate-reference-yaml.py --ci` still reports its pre-existing 17 bare-line-number drift failures (confirmed present before this edit via `git stash`), none newly introduced.
- **AgentSec CoSnitch intelligence mirrored** (`machine-readable/agentsec-security-feed.v1.json`): synchronized the 2026-08-24 AgentSec feed with two reviewed sources and one `CVE-2026-24301` event covering Varonis's Microsoft Copilot Personal disclosure. The event is `not_applicable` to repository scanning, so AgentSec's runtime database remains at 114 CVEs while the public intelligence ledger moves to 20 sources and 10 events.
- **Cross-Session Messaging documented as a dedicated page, new diagram, and new guide section** (`guide/workflows/cross-session-messaging.md` new page, `guide/ultimate-guide.md` new §9.27, `guide/diagrams/07-multi-agent-patterns.md` 6th diagram "Cross-Session Messaging: Discovery & Delivery", `guide/security/security-hardening.md` new Part 8, `guide/core/tools-reference.md`, `guide/cheatsheet.md`, `guide/workflows/README.md`, `guide/diagrams/README.md`, `machine-readable/reference.yaml`, `mcp-server/content/reference.yaml`): the `ListAgents`/`SendMessage` tool pair was previously described in the tools table only as agent-team teammate messaging, with `ListAgents` absent from the table entirely; neither tool had a section covering session-to-session peer messaging between independently launched sessions. Content verified against the official `code.claude.com/docs/en/cross-session-messaging`, `/errors`, and `/settings-reference` pages (fetched directly, not inferred from secondary sources) after a Perplexity Deep Research pass surfaced conflicting version claims from community write-ups. The new page covers `ListAgents` discovery (subagent/teammate/local-peer/cloud/Remote-Control rows), same-machine socket delivery versus cross-machine Remote Control routing, the inbox socket mechanism (`CLAUDE_CODE_MESSAGING_SOCKET`/`_TOKEN`, own-child auth rules), the full `crossSessionInbound`/`isolatePeerMachines` security model (a peer message can never approve a permission or change configuration), message size/burst limits, and a version timeline from v2.1.224 (introduction) through v2.1.239 (teammates listed, own-name handling fixed). The new security-hardening Part 8 adds a threat-model table for cross-session prompt injection and endpoint-spoofing defenses, mirroring the existing Part 7 (Remote Control Security) format. `tools-reference.md`'s `SendMessage` row and subsection were broadened from "agent team teammate" only to cover independent-session messaging; a `ListAgents` row was added to the tools table for the first time. Diagram count 48 → 49; also fixed a stale "10 thematic files" claim in `diagrams/README.md` (actually 12). Index coverage 93/93, anchors clean (pre-existing unrelated failures untouched).
- **Nimbalyst added to Section 4 Agent Orchestration Tools** (`guide/ecosystem/agentic-tools.md` new §4.7, Situation-to-Tool Guide row): requested in issue #73. MIT-licensed desktop workspace (macOS/Windows/Linux, iOS/Android companion) running Claude Code and Codex side by side, worktree-per-session isolation, inline red/green diff review across markdown/mockups/Mermaid/Excalidraw/CSV/data models, plus a bundled kanban, extension SDK, and MCP client. Facts verified against the GitHub API (1,558 stars, MIT, created 2025-10-30, 223 forks, 560 open issues as of 2026-08-24), not taken from the issue's unverified description alone.
- **viberank added to Token & Cost Tracking, alongside Straude's "only social tool" claim corrected** (`guide/ecosystem/third-party-tools.md`, `whitepapers/recap-cards/{fr,en}/t22-third-party-tools.qmd`): fixes issue #71. The guide stated Straude was "the only tool in this list that is social," which predated viberank's public leaderboard (Claude Code, Codex, Gemini CLI, OpenCode, and more, reading the same local `ccusage` data). New viberank subsection added with verified GitHub/npm facts (114 stars, MIT, created 2025-07-03, `npx viberank-cli`), and the Straude "only" claim reworded to "one of two social tools." Also carried the commenter's follow-up: viberank's CLI sends aggregate totals only (tokens, cost, dates, model names), no hostname or device UUID, unlike Straude, noted in both the guide entry and the T22 recap card (FR+EN).
- **Three community pull requests merged after individual verification** (`examples/github-actions/claude-issue-triage.yml`, `examples/hooks/bash/{dangerous-actions-blocker,file-guard}.sh` + new `test-hooks.sh`, `.pre-commit-config.yaml`, `scripts/generate-guide-exports.sh`, `docs/workflows/whitepaper-build.md`): PR #67 swaps the retired `claude-3-5-sonnet-20240620` model id for `claude-sonnet-4-6` in the issue-triage example workflow. PR #48 hardens the two example security hooks, adding credential-file blocking to `dangerous-actions-blocker.sh` and splitting `file-guard.sh`'s critical patterns into filename (basename glob) versus path (substring) matching to fix a false-positive bug where `.env` as a bash-glob-and-regex hybrid pattern could match unrelated files like `dotenv.py`; ships a 94-test suite. Reviewed line-by-line before merge: every change strictly adds coverage, none removes an existing protection, no network calls or exfiltration path introduced. PR #65 adds `quarto typst` as a portable Linux fallback for PDF/EPUB export (previously macOS-only bundle-path detection), isolates each run in its own temp directory, and stages/validates all requested outputs before replacing existing exports; its CI failure was confirmed to be pre-existing `reference.yaml` anchor drift on `main`, unrelated to the PR's files. Two other open PRs (#69, #70) are left unmerged pending rebase (both `CONFLICTING`); PR #64 (MiniMax model aliases) is left unmerged despite a harmless diff because its author account shows a bot-farm pattern (1,548 public repos created in 5 months); PR #69's author shows the same pattern (539 repos, 0 followers/following) and additionally redirects the README's star-history badge to an unofficial third-party mirror domain, recommended for closure rather than merge once rebased.

### Changed

- **Memory Systems cross-linked with the claude-mem field audit and corrected** (`guide/core/memory-systems.md`, portfolio guide `persistent-memory-silent-failures`): added links in both directions between the canonical comparison and the operational audit. Corrected claude-mem's license from AGPL-3.0 plus PolyForm Noncommercial to Apache-2.0 against the repository's current `LICENSE`, removed the commercial compliance warning, replaced the `just works` decision label with `local auto-hooks`, and bounded the recommendation with explicit scope, indexing, backlog, version, cost-routing, and retention checks.
- **"6 months of daily practice" updated to "over a year of daily practice"** (`README.md` lines 41 and 747): the wording dated back to the guide's first release (`CHANGELOG.md` `[1.0.0]`, 2025-01-09) and had not been revisited since. Same fix applied in the landing repo (`src/pages/faq/index.astro` x3, `src/pages/compare/index.astro`, `src/pages/compare/[slug].astro`).
- **Em dashes and other AI-writing tells removed from the guide, whitepapers, and landing site prose** (`guide/**/*.md`, `whitepapers/{fr,en}/*.qmd`, `whitepapers/recap-cards/{fr,en}/*.qmd`, plus hand-authored landing files under `src/components/`, `src/pages/`, `src/data/`, `src/content/questions/`): about 2,600 em dashes removed from running prose across 122 files in this repo and 187 in the landing repo, replaced with commas, colons, parentheses, or restructured sentences per `~/.claude/ANTI_AI.md`. A handful of negative-parallelism and stereotyped-opener instances were also fixed where an agent was already looking at the sentence for the em dash fix. Roughly 500 em dashes remain by design: code comments, mermaid diagram labels, table "N/A" placeholder cells, blockquote citation attributions, and verbatim quoted strings, all outside the style pass's scope. Landing artifacts derived from `guide/` and `whitepapers/recap-cards/` (`src/content/docs/guide/`, `src/data/diagrams-data.ts`, `src/data/guide-search-entries.ts`, `src/data/guide-content-entries.ts`, `src/content/cheatsheets/`) regenerated via `prepare-guide-content.mjs`, `build-diagrams-data.mjs`, `pnpm build:search`, and `convert-recap-cards.mjs`/`convert-en-recap-cards.mjs`.
- **Second, deeper anti-AI prose pass across the guide and landing site: hollow signaling, rhetorical colons, filler verbs, and metadiscourse** (27 files under `guide/**/*.md` including `guide/ultimate-guide.md`, plus 12 files in the landing repo under `src/pages/`, `src/components/landing/`, `src/data/compare-data.ts`): 24 parallel `technical-writer` agents audited 169 files (98 in this repo, 71 in the landing repo) against the full `~/.claude/ANTI_AI.md` rule set (beyond em dashes: "worth noting/knowing/naming" hollow signaling, rhetorical announcement colons like "The key:"/"The insight:", filler verbs like "leverage", stacked negative-parallelism, unattributed evidentiality, effaced branding, sentencious closers), applying 82 corrections total (55 in the guide, 27 on the landing site) with no change to any number, command, URL, citation, code example, or technical conclusion. One agent-introduced regression was caught and fixed before commit: renaming a French heading in `guide/ecosystem/remarkable-ai.md` broke its `reference.yaml` anchor in two places (`deep_dive` key and `section_maps` list), both re-synced in `machine-readable/reference.yaml` and `mcp-server/content/reference.yaml`. Recurring findings surfaced but left untouched as out of scope for a style pass: six independent French-language leaks in nominally English-only files (`guide/workflows/search-tools-mastery.md`, `guide/core/claude-code-releases.md`, `guide/ultimate-guide.md`'s "Industry Context" section, `guide/ecosystem/third-party-tools.md`'s Pipelex entry, `guide/ecosystem/remarkable-ai.md` in full, `guide/workflows/pdf-generation.md`'s two tables), a pre-existing "colon glued to the next word with no space" artifact in the landing's `memory-systems/index.astro` (10 occurrences, likely from an earlier automated em-dash-to-colon pass), and several factual inconsistencies (a "5 categories" claim in `security-hardening.md` listing only 4; a duplicated "Rule 6" heading in `production-safety.md`; a Part 4-to-Part 7 numbering gap in the same file; a diagram-count mismatch between the landing's `FeaturesGrid.astro` and `VisualDiagrams.astro`; a golden-rule-count mismatch between `QuickRef.astro` and `GoldenRules.astro`). Full per-batch findings archived in `claudedocs/anti-ai-audit/` (24 reports, gitignored). No `ANTI_AI.md` rule changes proposed: every pattern found was already covered by an existing rule. `guide/ultimate-guide.fr.md` (the French translation) and `docs/resource-evaluations/` were explicitly out of scope for this pass.

### Fixed

- **Guide export script now supports Quarto's bundled Typst on Linux** (`scripts/generate-guide-exports.sh`, `docs/workflows/whitepaper-build.md`): added the supported `quarto typst` CLI as a portable fallback between a standalone Typst install and Quarto's legacy macOS-only bundle path. Pandoc/Typst diagnostics are no longer discarded; each run uses an isolated, automatically cleaned build directory; and all requested outputs are staged and verified before replacing existing exports.

## [3.42.0] - 2026-08-26

### Added

- **`intent.md` upstream document and closed `Maintain → Plan` loop, sourced from Anthropic's "AI-Native SDLC Playbook"** (`guide/workflows/spec-first.md`, `guide/diagrams/06-development-workflows.md`, `machine-readable/reference.yaml`, `docs/resource-evaluations/2026-08-26-anthropic-ai-native-sdlc-playbook.md`): evaluated the Anthropic blog post (score 3/5, most content already covered by the existing spec-first/BMAD-METHOD/hooks documentation) and integrated the two genuine gaps found. `spec-first.md` now documents the 3-document chain `intent.md → spec.md → plan.md`, each gated by a different reviewer, with a full `intent.md` example (author, problem, constraints, open questions, PM gate) in a new "With intent.md (Upstream Problem Statement)" subsection. The "Spec-First Development Pipeline" Mermaid diagram now opens with an `intent.md`/PM-approval step and closes the loop with a `Maintain` stage that drafts a new `intent.md` automatically when a production monitoring threshold is crossed.

## [3.41.3] - 2026-08-20

### Added

- **Three terminal coding agents profiled, plus a new page mapping the full agent harness field** (`guide/ecosystem/agentic-tools.md` new §1.5-1.7, `guide/ecosystem/agent-harness-landscape.md` new page, `guide/README.md`, `machine-readable/reference.yaml`, `mcp-server/content/reference.yaml`): opencode (Anomaly, formerly SST, MIT, 199,400+ stars, the highest count in the category, client/server split so the agent can run away from its terminal), Gemini CLI (Google, Apache-2.0, 106,600+ stars, the free tier at 60 req/min and 1,000/day is the reason to pick it over harness novelty), and crush (Charm, FSL-1.1-MIT, 27,500+ stars, flagged as source-available rather than OSI open source at release, converts to MIT two years after each release) were absent despite opencode being the single most-starred project in this whole comparison page. All three verified live against the GitHub API and README install commands rather than the source catalog's numbers alone. The new page defines "agent harness" (tools, context, permissions, action loop, memory, crash recovery; cites Simon Willison's framing and the SWE-agent paper's agent-computer interface term) and puts 25 harnesses in one table spanning CLI, IDE, and cloud, open source through proprietary, something neither `agentic-tools.md` (CLI-only deep profiles) nor `ai-ecosystem.md` §6 (IDE workflow tips) does on its own. DeepSeek Harness (`deepseek-ai/deepseek-harness`, MIT, developer preview, "everything is a plugin" Cordis architecture) gets the most detail of the new entries: verified install requirements, its four preset modes, an approval system that fails closed but shows no argument detail and has no "always allow" rule, and Tencent's independent prompt-injection study (arXiv 2608.16393, 14,560 tests, ~5.3-5.6% overall success rising to 25.5% via hidden Unicode) cited as evidence that sandboxing alone does not close the injection gap. Twelve proprietary entries (Cursor Agent, Windsurf Cascade, Kiro, GitHub Copilot CLI, Amp, Factory Droid, Warp, Jules, Devin, Replit Agent, Augment Code, Junie) are kept to one conservative positioning line each with an explicit footnote that they were not independently verified against vendor docs this pass. A boundary table separates true harnesses from frameworks (LangGraph, CrewAI), SDKs (Claude Agent SDK, Google ADK), sandboxes (E2B, Daytona), memory layers (Mem0, Graphiti), observability (Langfuse, LangSmith), and protocols (MCP, ACP, A2A). 7 new `deep_dive` keys mirrored byte-identical across both `reference.yaml` copies; index coverage 93/93, anchors 620/620.

- **Team Metrics closed a 2026 tooling-market gap and gained a board-reporting playbook** (`guide/ops/team-metrics.md`, `whitepapers/en/11-team-metrics.qmd`, `whitepapers/fr/11-team-metrics.qmd`, `machine-readable/reference.yaml`, `mcp-server/content/reference.yaml`): fresh research against the current delivery-intelligence market found the existing Tooling table covered only half the active field. Added "Broader Delivery Intelligence Platforms" (DX, Multitudes, Swarmia, Cortex.io, Jellyfish, Oobeya, Hatica, the last flagged explicitly as thinner on documented specifics than the rest) and "AI-Generated Board Narratives" (LinearB's AI iteration summary, Jellyfish's "AI Executive Report," both framed as explanation of already-computed metrics rather than new analysis) as new Tooling subsections. Cortex.io and Jellyfish were already cited elsewhere in the guide as data sources for PR-size and change-failure-rate figures; this documents them as tools in their own right for the first time. A new top-level "Probabilistic Delivery Forecasting" section covers ActionableAgile and Nave's Monte Carlo simulation, including Nave's load-bearing quote that the sole requirement for reliable Monte Carlo forecasts is a predictable delivery system, and states plainly that the technique replicates an unstable system's unpredictability as a wider distribution rather than fixing it. A new top-level "Reporting Delivery Capacity to a Skeptical Board" section, general engineering-management guidance with no case study and no named individuals, reframes board doubt after a slipped estimate as a trust and visibility problem rather than a data problem, states that no published study measures whether delivery-intelligence tooling repairs executive trust, and covers named delivery scenarios over velocity charts, capped strategic objectives over multi-quarter feature roadmaps, tracking commitment hit-rate as the trust-rebuilding metric, and pre-aligning board members individually before the plenary meeting. The Uplevel Copilot study (no significant change to coding speed, PR cycle time, or throughput after adoption, alongside a 41% increase in bug rate and a "Sustained Always On" burnout-risk proxy that fell more for developers without Copilot) was added next to the existing Digital Applied heavy-user review-time finding, both making the same point from independent data. Both whitepapers translated in full (not stubbed) and `wp-version` bumped 1.1.0 to 1.2.0. Three new `deep_dive` keys: `team_metrics_tooling`, `team_metrics_forecasting`, `team_metrics_board_reporting`.

- **Two local Claude Code session inspectors added to the LLMOps section** (`guide/ecosystem/context-engineering-tools.md` §9): cross-checked against a LinkedIn Learning course on token optimization ("Reduce AI Costs," Tejas Chopra, published 2026-07-30). Verified via web search before adding, since the course names them without links: claude-devtools (`matt1398/claude-devtools`, MIT, `brew install --cask claude-devtools`), a desktop app giving per-turn token attribution across 7 categories (CLAUDE.md, skills, @-mentions, tool I/O, thinking, team overhead, user text), finer-grained than the native `/context` bar; and tokview (`headroomlabs-ai/tokview`, MIT), a local proxy/dashboard with per-tool-call attribution that backfills from existing JSONL history. tokview ships from the same org as Headroom, already documented in this section with a skepticism note on self-reported figures, and the new entry carries the same caveat forward. Everything else the course covers (RTK, Serena, Headroom, Ponytail, Caveman, `/context`, `/compact` at 70%, Anthropic's `count_tokens` endpoint, MCP tool search / progressive disclosure, lost-in-the-middle) was already documented here in more depth, generally with tighter sourcing than the course's own toy-repo demo numbers.

- **AI Unit Economics gained a lever on skill and tool injection cost, the piece none of §3's four existing levers covered** (`guide/ops/ai-unit-economics.md` new §3 subsection, `machine-readable/reference.yaml`, `mcp-server/content/reference.yaml`): the existing levers (route by complexity, isolate in sub-agents, cap iterations, reuse cached context) reason about the model call itself, not about what a skill or MCP tool call injects into context. The gap surfaced from a practitioner's measured example: a skill loading at roughly 12K tokens paired with a query whose injected result cost over $1 on the generating call and roughly $0.11 in cache-read on every following turn, and a screenshot from the same source showing a single skill invocation at $5.33 on 208.9K tokens next to `TASKCREATE` calls at roughly $0.001 each, over five thousand times the cost of the calls around it (Marek Kalnik, CTO at Theodo, LinkedIn post, July 2026). The new subsection frames this as a governance decision rather than a rule: a skill that injects a large result earns its cost on a task that genuinely needs it, and burns money on a routine task matched by too broad an auto-trigger condition. No break-even point is asserted, since the source practitioner, asked directly, confirmed none has been measured. The subsection points to the native `/usage` per-category cost breakdown (v2.1.149) as the tool for measuring a given skill's actual injection cost before deciding whether its trigger condition is too wide. New `deep_dive` key: `ai_unit_economics_skill_injection_cost`.

- **Executor documented as a productized form of the manual MCP registry pattern** (`guide/security/enterprise-governance.md` new §3.5, `docs/resource-evaluations/executor-integration-governance-layer.md`, `docs/resource-evaluations/README.md`): Executor (UsefulSoftwareCo/executor, MIT, `1.4.0-beta.0`) maps its four concepts (integration, connection, policy, MCP exposure) almost one-to-one onto the registry format §3.2 already documents by hand, with one addition the hand-built version lacks, a `SecretRef` indirection so a credential never appears in a tool schema or MCP response. Scored 3/5: no missing category filled, a well-documented example of one already covered. Framed explicitly as comparison, not a replacement recommendation, since teams actively copy §3.2's YAML into their own `.claude/mcp-registry.yaml` and a beta at bus factor 1 (93% of 2,532 commits by one contributor, cadence down 76% from an April peak, measured 2026-07-29) is a different risk profile than a dependency-free file they can read end to end. `guide/ecosystem/mcp-vs-cli.md`'s "Tooling in this space" table gained a short paragraph naming the token-cost axis versus the access-governance axis explicitly, since Klavis AI/Strata sits on both and that ambiguity is what made Executor look like it belonged in a token-savings table it does not compete on.

- **agentOS documented as the in-process counter-example missing from the cloud sandbox comparison** (`guide/security/sandbox-isolation.md` §5, new TL;DR row, `docs/resource-evaluations/agentos-in-process-agent-vm.md`, `docs/resource-evaluations/README.md`): every existing entry in §5 (Fly.io Sprites, Cloudflare Sandbox SDK, Vercel Sandboxes, E2B) bills through a cloud provider; agentOS (`@rivet-dev/agentos`, Apache 2.0, `0.0.1` preview) runs a Rust-kernel-plus-WASM-sandbox VM inside the host's own Node process instead, with 42 real upstream Linux tools (git, ripgrep, sqlite3, duckdb) compiled to `wasm32-wasip1` against an owned sysroot. Scored 4/5, higher than Executor's 3/5, because it fills a documented gap and shows a rising two-month commit trend rather than a declining one. The entry states plainly that "VM" is a marketing choice (no KVM, no Firecracker, isolation is a V8 isolate plus WASM, the project's own threat model names the sidecar/executor process as the boundary, not a hypervisor) and that the vendor's 4.8ms/92x benchmarks are single-machine and not independently reproduced.

- **just-bash documented as the other end of the in-process spectrum from agentOS** (`guide/security/sandbox-isolation.md` §5, new TL;DR row, `docs/resource-evaluations/just-bash-simulated-shell.md`, `docs/resource-evaluations/README.md`): agentOS runs a real, if hypervisor-less, VM (Rust sidecar plus V8 isolate); just-bash (vercel-labs/just-bash, `3.2.0`) runs no VM at all, a bash lexer/parser/interpreter written directly in TypeScript over an in-memory virtual filesystem, with containment resting entirely on JS-level defenses (`DefenseInDepthBox`, null-prototype objects, per-call resource limits, each mapped to a named vector in the project's own 31.5 KB `THREAT_MODEL.md`). Scored 4/5: past `3.x` on npm with a changeset release pipeline and a public website demo, a stronger maturity signal than agentOS's `0.0.1` preview, same bus-factor-1 risk (Malte Ubl, 322/380 commits, 84.7%) already flagged in the Executor and agentOS evaluations. One concrete gap named directly rather than smoothed over: the repository has no `LICENSE` file at its root despite the README's Apache-2.0 claim. No §6 Comparison Matrix column added, same call as agentOS, since most of its criteria (Docker-in-Docker, kernel isolation) do not apply to an in-process simulator.

- **A fourth data point added to the file-based memory comparison** (`guide/core/memory-systems.md` §3.7): Executor's `MISTAKES.md`/`DESIRES.md`/`LEARNINGS.md` run the same plain-file-committed-to-Git pattern as ORF and DiffMem, with one design choice that departs from all three existing examples: the files are gitignored, private working memory rather than shared team history.

- **A third independent source added to the progressive-disclosure convergence** (`guide/core/context-engineering.md` §4): Gorgias Engineering's "Building a Context Layer From the Ground Up" documents a production SQL-generating agent that rejected a monolithic table-description prompt for a three-tier context layer (per-table `when_to_use`/`how_to_use` metadata, hierarchical topic instructions, skill playbooks), citing progressive disclosure as their single biggest reliability improvement. Cross-referenced against the existing Dev With AI meetup finding on monolithic CLAUDE.md files, since both land on the same architecture from unrelated starting points.

- **A new skill-design pattern: multi-directory skill discovery for cross-CLI repositories** (`guide/core/skill-design-patterns.md`): Executor runs `.claude/skills/`, `.agents/skills/`, `.skills/`, and `.codex/environments/` side by side rather than consolidating into one directory, read as convergence across CLI conventions (Claude Code, a generic agent convention, a project-shared set, Codex) rather than disorganization. The pattern entry also notes the README's curated "References" reading list (FumaDB, Effect, OpenCode, OpenClaw, Emdash, Pi) as a related, separate convention worth naming.

- **Two new resource evaluations indexed** (`docs/resource-evaluations/README.md`, `machine-readable/reference.yaml`): Executor (3/5, watch-list, cross-reference only) and agentOS (4/5, integrated). `resource_evaluations_count` moves from 167 to 169 files on disk, `resource_evaluations_indexed` from 48 to 50.

- **A "build a mini agent to understand it" resource added to the learning path, sourced from the canonical English article instead of the French one that prompted the search** (`guide/roles/learning-with-ai.md` § External Resources, `docs/resource-evaluations/kajan-siva-mini-claude-code.md`, `docs/resource-evaluations/README.md`): Kajan Siva's "Construire un mini Claude Code pas à pas" (French, 9-min read, working code and a companion GitHub repo) scored 2/5, not because it is wrong but because it restates the same loop already documented at Tier 1 confidence in `guide/core/architecture.md` §1 "The Master Loop", and because it is French-only against this repo's English-only rule. Thorsten Ball's "How to Build an Agent" (ampcode.com), the most-cited article in the same genre, English, ~300 lines of Go, was added in its place.

- **A third Rippletide-sourced resource evaluated and rejected** (`docs/resource-evaluations/084-rippletide-harness-is-the-agent.md`, `docs/resource-evaluations/README.md`): a LinkedIn blog post by co-founder Yann Bilien, "The Harness is the Agent, What's Inside?", scored 2/5. Its three diagrams (harness anatomy, capabilities-vs-performance split, test-eval-modify iterate loop) map close to one-to-one onto `guide/core/agent-harness.md`'s nine components, already sourced to arXiv 2605.18747, Fowler, and Anthropic telemetry, and the article carries zero citations or measured claims of its own. No watch-list entry added: the pattern across all three Rippletide submissions (072 at 2/5, 081 at 3/5, this one at 2/5) trends toward restating known concepts rather than surfacing new, checkable information.

- **`/sandbox-unblock`, a diagnostic protocol for sessions that believe the sandbox is blocking them** (`examples/skills/sandbox-unblock/SKILL.md`, referenced from `guide/security/sandbox-native.md` §13, indexed as `sandbox_unblock_skill`): over one day of real work, six of eight reported sandbox blockers turned out to be false, and every one traced to the same handful of method errors. The skill front-loads eight checks so the report that reaches a maintainer is worth acting on: do not infer Bash restrictions from the `read.denyOnly` list in the system prompt (those patterns govern the Read tool only); confirm `$TMPDIR` shows the invocation ran sandboxed; put the `cd` and the tested command in the same Bash call, because the working directory resets between calls and two independent audits declared a package manager broken after landing in the wrong directory; check the binary exists before blaming policy, since output-compressing wrappers replace clear messages with bare errnos; read the real exit code rather than a pipe's; check whether a `PreToolUse` rewriter sits between the command and the `excludedCommands` matcher, which is what made prefixed entries work while unprefixed ones stayed inert; remember that an entry matches the command exactly as written, so `git -C /path fetch` and bare `git fetch` both miss `git fetch *`; and restart the session if the config changed after it opened. Ships a report template that forbids paraphrasing the error, an escalation section naming the two keys that mislead (`credentials.envVars` in `deny` mode leaves the variable readable to Bash, and `allowUnsandboxedCommands: false` does not neutralize `excludedCommands`), a network section separating an allowlist refusal (hangs 5 to 7 seconds) from a hostname that does not resolve (fails under 30 ms even when a wildcard covers it), and a table of limits with no configuration fix.

- **`/sandbox-status` referenced four configuration keys that do not exist** (`examples/skills/sandbox-status/SKILL.md`): the script read `.sandbox.autoAllowMode`, `.sandbox.filesystem.allowedWritePaths`, `.sandbox.filesystem.deniedReadPaths` and `.sandbox.network.policy`, none of which are real, so every `jq` lookup fell through to its default and the command printed `not set` for a fully configured sandbox. A status tool that reports "no restrictions" on a restricted machine is worse than no tool, since it converts a real policy into a clean bill of health. Now reads `autoAllowBashIfSandboxed`, `filesystem.allowWrite`, `credentials.files[].path` and `network.strictAllowlist`, and additionally surfaces `allowUnsandboxedCommands` so an audit can see whether the escape hatch is open. Example output updated to match, and both sandbox skills now cross-link.

- **A `permissions.deny` read rule does not reach a Bash subprocess, and a double dissociation proves it** (`guide/security/sandbox-native.md`, `machine-readable/reference.yaml`): the rule looks like a denylist and reads like one, so it gets audited as protection it does not provide. Measured on 2.1.220 in one session, on one machine: `~/.npmrc` carried a `sandbox.credentials.files` entry and no deny rule, and `cat ~/.npmrc` returned `Operation not permitted` 5/5; a project `.env` carried `Read(**/.env*)` and no credentials entry, and `cat .env` returned exit 0 5/5 on a file holding real secrets. Only the credentials block reaches sandboxed commands, and it resolves absolute paths rather than `**/` patterns, so a rule shaped like `**/.env*` has nothing to compile into the Seatbelt profile. Since `.env` files sit wherever projects put them, no absolute path closes the gap and a `PreToolUse` Bash hook is the remaining move. The guide now specifies its scope: block the readers that print or copy, leave `source .env` alone, because breaking how developers load their own variables costs more than the exposure it removes.

- **`.idea/` and `.vscode/` deny writes inside `allowWrite`, which kills `pnpm install`** (`guide/security/sandbox-native.md`): a narrower `allowWrite` entry does not take the ground back, since the deny resolves inside the allow. Tested against `.serena`, `.cursor`, `.zed`, `.fleet` and `.settings`, all of which accept writes, so this is specific to those two names rather than a general rule about dotted config directories. It surfaces as a supply-chain paper cut: a package shipping a `.idea/` folder in its tarball fails during extraction and leaves `node_modules/` truncated. Running the install in a terminal is the cheap fix, and `pnpm install*` in `excludedCommands` is the expensive one, since it unsandboxes every postinstall script in the tree.

- **`echo $TMPDIR` tells you whether a command actually ran sandboxed** (`guide/security/sandbox-native.md`, `machine-readable/reference.yaml`): most sandbox bug reports are measurement errors, and one variable explains nearly all of them. Because `excludedCommands` unsandboxes the whole invocation, a probe sharing a line with `git`, `gh`, `ssh` or `docker` reports on the unsandboxed world, and sessions then trade contradictory findings about the same machine. Sandboxed commands get a per-session `$TMPDIR`; unsandboxed ones inherit the shell's. An A/B binding a Unix socket makes the mechanism visible and catches the third trap in the same table: the probe alone is denied, the probe plus `git -C <path> fetch origin` is still denied because `-C <path>` breaks the `git fetch *` match, and the probe plus `git fetch origin` succeeds with `$TMPDIR` switched to the shell value. One flag decides whether the entire line runs sandboxed.

- **Three failures with no configuration fix, documented so they stop being tuned against** (`guide/security/sandbox-native.md`): setuid binaries cannot exec, so `ps`, `top`, `su` and `login` (mode `04000`) report `operation not permitted` while `lsof` and `whoami` run fine, and `lsof -nP -iTCP -sTCP:LISTEN` is the direct substitute for `ps aux | grep`. `AF_UNIX` `bind()` then `listen()` is denied in every writable directory including `$TMPDIR`, and `network.allowLocalBinding` covers TCP only, so `tsx` and anything else opening an IPC server at startup will not run; bundling with `esbuild` first sidesteps it. Writes to `.idea/` and `.vscode/` are the third.

- **The domain allowlist filters even in permissive mode, and two rounds of this entry got it wrong** (`guide/security/sandbox-native.md`, `machine-readable/reference.yaml`): the section first described a `policy` field that does not exist and called allowlist mode the default. The real switch is `strictAllowlist`, default `false`. The correction then overshot and claimed the list was inert whenever `autoAllowBashIfSandboxed` was on, resting on `example.com` and `api.openai.com` returning HTTP 200 against a 23-entry list. Both hosts sit in the built-in default list, so that test proved nothing about filtering. Re-measured on 2026-07-30 against a 32-entry list: `neverssl.com` stayed unreachable, and `cursor.com` and `www.jetbrains.com` went from unreachable to HTTP 200 on the addition of their wildcard alone, taking effect immediately with no session restart. Pick test hosts from outside the built-in defaults before concluding a list does nothing. A second note now distinguishes a blocked host from a nonexistent one: an allowlist refusal hangs 5 to 7 seconds, while an unresolvable hostname fails in under 30 ms even when a wildcard covers it (`api.cursor.sh` and `cloud.ollama.com` failed in ~25 ms while covered by `*.cursor.sh` and `*.ollama.com`; neither host exists). The `deep_dive` key `sandbox_allowlist_inert_with_autoallow` is replaced by `sandbox_allowlist_filters_without_strict` and `sandbox_blocked_host_vs_missing_host`. Also notes that `github.com` does not cover `codeload.github.com`, where npm and pnpm fetch git dependencies and tarballs.

- **Sandbox troubleshooting rewritten around what actually breaks, not what looks dangerous** (`guide/security/sandbox-native.md`, `machine-readable/reference.yaml`): the existing troubleshooting covered `watchman`, Docker, and Go CLI TLS. None of those were what a day of real use on a 200-repository setup produced. The sandbox fails on paths a toolchain uses without announcing them, so the section now opens with the break-in period: expect about a week before a configuration stabilizes, and widen a path because something broke rather than because something might. The worked example ends at 13 write paths with the failure that produced each one, in roughly the order anyone will hit them.
  - **`network.allowLocalBinding` defaults to `false`**, which breaks every local dev server and every tool that proxies its own traffic to inspect it. It had one line in the settings reference and nothing anywhere else. Discovered through a supply-chain firewall wrapping `pnpm install`, where the message named the firewall rather than the bind, putting the cause two steps from the symptom.
  - **Globally installed npm CLIs cache inside their own install directory**, under `~/.nvm/versions/node/<version>/lib/node_modules`, so the path also moves on every node upgrade. Allowing it is a genuine trade-off rather than a free fix: that directory holds `$PATH` executables, and write access there is a documented escalation route. Documented as a decision to make, not a discovery to have later.
  - **Read the last error, not the first.** A denied credential read warns on every later command and survives the actual fix, so it collects the blame. `credentials.files` on `~/.npmrc` makes every `pnpm` invocation open with an `EPERM` line, including the successful ones, because package managers fall back to the default registry. Three separate sessions blamed it while the real causes sat three steps further down and the warning kept printing after the install completed. A denied read is usually survivable; a denied write or bind is not.

- **Index coverage is now enforced instead of remembered** (`scripts/check-index-coverage.py`, `.github/workflows/index-integrity.yml`, `.claude/hooks/index-sync-reminder.sh`, `.claude/rules/index-sync.md`): the CI already answered "do the references in `reference.yaml` still resolve?" but nothing answered the opposite question, "did anything land in `guide/` that the index never learned about?". That gap is what produced the July 28 finding where ten guide files, including the entire `guide/learning-path/` series, had never been indexed at all. An unindexed page is invisible to the MCP server and to the landing's Cmd+K palette, and the only signal was an anchor audit months later. The new script measures file-level coverage; it reported 92/92 when added, so the CI gate is hard at zero with no ratchet to unwind. A `Stop` hook reports at end of turn when `guide/` changed and no index file did, which catches the more common case of a new section inside an already-indexed file, where no automated check can distinguish a typo fix from a new concept. The hook warns and never blocks: a turn can legitimately end mid-edit, and a hook that vetoes that is a hook people disable. A rule file documents what to update where, since the hook only says "you forgot". Choosing a hook over a rule alone is deliberate: a rule is a reminder the model can rationalize past, and it costs context every session, while the hook is deterministic.

- **A third `excludedCommands` trap, found while unblocking a real session** (`guide/security/sandbox-native.md`, `machine-readable/reference.yaml`): beyond the bare-name form that never matches and the glob that unsandboxes the whole invocation, an entry matches the command *as written*, so any wrapper, prefix, or loop silently sends the command back into the sandbox. `gh api rate_limit` runs unsandboxed and returns; `rtk gh api rate_limit` is sandboxed and fails. The two differ by a four-character prefix. A `PreToolUse` hook that rewrites commands, which token-optimizing proxies do by design, therefore disables every exclusion naming a wrapped binary with no report. The same applies to `for d in a b; do (cd $d && git push); done`, where the string starts with `for`. The symptom is never "your exclusion did not match": it is `Operation not permitted` on a path, or a Go CLI failing certificate verification with `x509: OSStatus -26276` because it cannot reach the macOS keychain from inside Seatbelt. That error is now indexed as a diagnostic signature, since it was independently misdiagnosed twice in one session as an expired token, an EDR agent, and a macOS security policy.

- **The `sandbox.credentials` block documented for the first time** (`guide/core/settings-reference.md`): `credentials.files`, `credentials.envVars`, and the related `network.tlsTerminate` had zero occurrences anywhere in `guide/`, despite being the mechanism the official documentation recommends for the exact hole the guide already described. `sandbox-native.md` correctly stated that sandbox read access covers the entire computer, then offered `Read(~/.ssh/**)` deny rules as the remedy. Those rules do work, since Read deny rules merge into the sandbox configuration, but they cannot touch environment variables, and sandboxed commands inherit the parent environment unchanged. A reader came away believing their tokens were protected while every sandboxed command could still read them. The new entries cover `deny` for files and variables, `mask` with `injectHosts` for the case where a CLI must keep authenticating, why `mask` fails closed without `tlsTerminate`, and the scope restrictions (`mask` is honored only from user, managed, and `--settings`, so a repository cannot authorize the proxy to send real credentials). Verified on 2.1.220: with the entry in place, `ls ~/.ssh` from a sandboxed command returns `Operation not permitted` while the directory still appears in a home listing.

- **Three sandbox settings that existed only in the release notes** (`guide/core/settings-reference.md`): `filesystem.disabled` (v2.1.216), `network.strictAllowlist` (v2.1.219), and `allowAppleEvents` were recorded as "a release happened" and never documented as usable settings. Each now carries its scope restriction (all three are ignored from project settings), its trade-off, and for `filesystem.disabled` the list of protections it silently turns off, including `credentials.files` and the settings-file write protection. `strictAllowlist` is explicitly marked as the last thing to enable, since before the domain list has stabilized it converts every missing domain from a one-time prompt into a hard failure.

- **Six sandbox behaviors documented** (`guide/security/sandbox-native.md`): what survives auto-allow mode (deny rules, `rm` on `/` or `~`, content-scoped `ask` rules, with a bare `Bash` ask rule skipped for sandboxed commands), the plan-mode interaction that changed in v2.1.212 and again in v2.1.218, that subagents inherit the parent's sandbox and cannot widen it, the session temp directory and the `$TMPDIR` divergence between sandboxed and unsandboxed commands, the git-worktree exception for the shared `.git` directory, and the write protection on Claude Code's own `settings.json` at every scope with symlink resolution since v2.1.210. That last one is easy to hit: a script editing `~/.claude/settings.json` from Bash fails with `PermissionError: [Errno 1] Operation not permitted` while the same edit succeeds through the Edit tool, which is not sandboxed. Also adds the Ubuntu 24.04 AppArmor workaround, without which bubblewrap cannot create user namespaces and the sandbox fails to start with no obvious cause, plus the optional seccomp filter install.

- **MCP server was serving the rotted index: `mcp-server/content/` had drifted from `machine-readable/`** (`mcp-server/content/reference.yaml`, `mcp-server/content/llms.txt`): the directory is a strict mirror (verified byte-identical at an earlier commit), and it is what the `claude-code-guide` MCP server reads. Two of its three files had fallen behind: the reference copy carried 4 anchored references against 36 in the source and none of the 874 section-map anchors, meaning every consumer of the advertised "instant expertise" entry point was being handed the broken positions this pass had just repaired. `claude-code-releases.yaml` was already in sync. Checked before overwriting that the server actually understands the new format: `mcp-server/src/lib/section-reader.ts` already resolves `path#slug`, including Pandoc-style explicit ids and near-miss suggestions, so the anchor migration matches where that code was already heading.

- **Broken-reference backlog cut from 383 to 145, and the CI ratchet lowered to match** (`.github/workflows/index-integrity.yml`, `scripts/resync-reference-yaml.py`, `machine-readable/reference.yaml`): `scripts/resync-reference-yaml.py` already existed and already did key-name-to-heading matching, which is worth stating plainly, the rot accumulated anyway because nothing invoked it. Its own reported count was inflated by a parser bug: the pattern `"([^"]+):(\d+)"` also matched URLs and prose, so `claude_mem_dashboard: "http://localhost:37777"` was read as a file named `http://localhost` at line 37777, and a sentence ending in `... see guide/core/foo.md:2215` was read as a file named after the whole sentence. Both surfaced as `FILE MISSING` and inflated the total; the pattern now requires a repo-relative path under a known top-level directory, taking `FILE MISSING` to 0. With that fixed the real starting figure was 208, and applying the tool's own 63 HIGH and MEDIUM confidence corrections brought it to 145, clearing HIGH and MEDIUM entirely. What remains is 108 LOW and 37 UNKNOWN, where the key name does not identify a single heading well enough to correct without guessing.

- **`docs/resource-evaluations/README.md` status line was in French** (`docs/resource-evaluations/README.md`): the repo's rule is English throughout. Translated, and the date refreshed to match the verified figures (167 files on disk, 48 in the index table). `README.md` date badges resynced via `./scripts/sync-version.sh`.

- **Index integrity is now enforced by CI in two layers, and the strict one is tested to fail** (`.github/workflows/index-integrity.yml`, `scripts/validate-reference-yaml.py`): the workflow already ratcheted the line-number backlog; it now runs `validate-reference-yaml.py --ci` first as a hard gate at zero, covering what a ratchet cannot, namely YAML parseability, anchor resolution against real headings, path existence, line-reference bounds and `section_maps` validity. Anchors do not drift when lines are inserted above them, so this gate is cheap to keep green, and a failure means something is genuinely broken rather than merely stale. The gate was verified by deliberately corrupting one anchor and confirming exit code 1, then restoring and confirming exit code 0 with the file intact, because the whole reason this rot survived for months is that the previous check could not fail: it only asked whether a referenced line existed inside a 26,554-line document. The script also had its hardcoded absolute working directory replaced with a path derived from its own location, which would otherwise have made it pass vacuously on a CI runner.

- **`reference.yaml` positional references repaired and migrated to anchors: 205 of 488 pointed at the wrong place** (`machine-readable/reference.yaml`, new `scripts/fix-reference-refs.py`, `scripts/validate-reference-yaml.py`, `scripts/gen-section-maps.py`): the index passed every check it had, because the only check was that a referenced line existed inside a 26,554-line file. That test cannot fail in a large document, so it validated nothing. Matching each YAML key name against the headings of its target file instead of trusting the stored position showed how far the file had rotted: `hook_templates` pointed 17,104 lines before "A.4 Hook Templates", `command_template` 17,643 lines before its section, `rtk_guide` 3,687 lines off, `mcp_secrets_management` 2,937. The appendix block drifted in lockstep, `appendix_a` through `appendix_d` and every `myths_*` key each exactly 5,480 lines early, which is the signature of upstream insertions never propagated rather than independent mistakes. 132 string references were migrated from `path:N` to `path#anchor`, 73 bare line numbers were repaired in place, and the tooling now converges (a second pass reports zero changes). Anchors were chosen deliberately over line numbers where the landing consumes the value: `build-guide-index.mjs` strips both, so the migration is invisible to the build, but anchors survive insertions above them while line numbers do not. The guide gained lines twice during this work and the drift figures moved between two runs of the same script, which is the argument for anchors made in real time. Bare integers pointing into `ultimate-guide.md` were repaired but not converted, since the landing ignores them and a line number is more useful than an anchor for reading a range out of a 26K-line file.

- **Two near-misses caught in the repair tooling before they were applied** (`scripts/fix-reference-refs.py`, `scripts/validate-reference-yaml.py`): the first pass would have rewritten `resource_evaluations_count: 120` to `26366` and `ui_ux_pro_max_stars: 33700` to a line number, because the pattern matching bare integers cannot tell a quantity from a position. A guard now protects keys whose name ends in a quantity suffix, backed by an independent bounds check that catches the rest (33,700 exceeds the file, so it cannot be a line regardless of what the key is called). The first version of that guard matched substrings anywhere in the key and swallowed six genuine references, `memory_files`, `cost_optimization`, `ui_ux_pro_max_guide` among them, so it was narrowed to suffix matching: protecting a real reference leaves it visibly unrepaired, whereas corrupting a counter is silent and propagates. Separately, the heading extractor used a naive fence toggle that desynchronised on any file with an odd fence count; `enterprise-governance.md` has 51 such lines, and the toggle got stuck inside a block and dropped 9 valid sections, reporting correct anchors as broken. Replaced with CommonMark fence semantics (matching character, length at least the opener, nothing trailing). Re-running the repair with the corrected extractor found 14 further fixes the broken version had missed.

- **Quiz block in `reference.yaml` described a structure that no longer exists** (`machine-readable/reference.yaml`): `quiz_count: 334` against 473 real questions, `quiz_categories: 16` against 17, `quiz_file` pointing at a `quiz/questions.json` that does not exist, and a three-tier split (`quiz_beginner`, `quiz_intermediate`, `quiz_advanced`) referencing a `quiz/categories/` directory that does not exist either, with sub-totals of 60, 100 and 97 summing to 257, a number matching neither the old figure nor the new one. The real bank is one YAML file per category under `quiz/questions/`, and difficulty is a per-question field alongside a `profiles` list, not a per-category tier. Replaced with the verified counts, the category filenames, and the actual question schema; the invented tier sub-totals were dropped rather than replaced with guesses. `resource_evaluations_count` was likewise 120 against 167 files on disk, now recorded alongside the 48 that the README index actually lists, since those are two different real numbers.

- **Section maps: 874 H2 anchors across 78 guide files, none previously indexed** (`machine-readable/reference.yaml`, `scripts/gen-section-maps.py`): coverage was measured per file, not per section, so a file counted as indexed while none of its sections were reachable. `ai-ecosystem.md` had 0 of 41 sections indexed, `cheatsheet.md` 0 of 27, `visual-reference.md` 0 of 20, `architecture.md` 0 of 19. Adding one `deep_dive` key per section would have worked but cost twice: roughly 600 keys in a file already at 44K tokens, and 600 more entries in the landing's Cmd+K palette, since `build-guide-index.mjs` turns every `deep_dive` string starting with `guide/` into a search entry. A top-level `section_maps` block of anchor lists sidesteps both, as that script only walks `deep_dive`. Duplicate slugs within a file are skipped rather than emitted, because GitHub would suffix them `-1` and the reference would not resolve. The generator is idempotent and replaces its own block on re-run.

- **Three maintenance scripts promoted out of the gitignored working directory** (`scripts/validate-reference-yaml.py`, `scripts/gen-section-maps.py`, `scripts/fix-reference-refs.py`): the validator checks YAML parseability, anchor resolution, path existence, line-reference bounds, how far each bare integer sits from its nearest heading, and `section_maps` validity in one pass. It is what would have caught this rot at any point over the past months. The generated block in `reference.yaml` carries the regeneration and validation commands inline, which is also why the scripts had to move: the block initially pointed at `claudedocs/`, a gitignored path, making the instruction dead for everyone but the session that wrote it.

- **New audit prompt: permission and sandbox posture** (`tools/permissions-audit-prompt.md`): a self-contained prompt that answers one question the existing tooling does not, whether a project's permission rules still constitute a boundary. `tools/audit-prompt.md` scores the whole setup across eight dimensions and `/security-audit` scans for secrets and injection surfaces; neither detects the failure mode where a single `allow` entry resolving to an interpreter (`Bash(bash *)`, `Bash(node:*)`, `Bash(python3 *)`) silently makes every `deny` rule in every scope bypassable, since the matcher treats `bash -c '<anything>'` as a `bash` command and never as the inner one. Six phases: blanket execution grants, rule population health, deny and ask coverage, sandbox posture, scope hygiene, and permission-mode interaction. The prompt embeds the documented matcher semantics rather than letting the model infer them, because that is where audits of this kind go wrong: the stripped wrapper list (`timeout`, `nice`, `command`, bare `xargs`) versus the runners that are *not* stripped (`npx`, `docker exec`, `devbox run`), the fact that an `allow` rule stops at an unknown env-var assignment while `deny` and `ask` match past any, that `:*` is only recognized at the end of a pattern, that protected paths are not pre-approvable by an `allow` rule in settings, that `sandbox.allowUnsandboxedCommands: false` constrains only the `dangerouslyDisableSandbox` retry and not `excludedCommands`, and that in auto mode `allow`, `ask`, and `deny` resolve *before* the classifier, so a narrow rule such as `Bash(git push:*)` does not merely skip a prompt, it removes classifier review from that action. Scored out of 100 with a deliberately lopsided weighting: any arbitrary execution grant zeroes 30 points on its own. Includes a fleet triage sweep that ranks repositories by exposure before running the full pass, so a thirty-repo park is not audited one indistinguishable finding at a time. Every finding must carry a reproduction command; the prompt explicitly forbids padding and forbids recommending `bypassPermissions` as a remedy for prompt fatigue. `tools/README.md` was three files behind and is corrected in the same pass: `context-audit-prompt.md` and `audit-cheatsheet-prompt.md` had never been listed, and a "which audit when" table now routes between the five, including `/security-audit` which lives as a slash command rather than a prompt file. Indexed in `machine-readable/reference.yaml` under `deep_dive` alongside the two existing audit-tool entries (a `deep_dive` key change means the landing's Cmd+K index needs `pnpm build:search`), and the `tools/` block in the root `README.md` tree, which listed two of the six files.

- **Generative UI category: A2UI vs. MCP Apps vs. Vercel AI SDK vs. MDMA** (`guide/ecosystem/ai-ecosystem.md` §7.1): new section covering agent-driven interactive UI output (forms, approvals, actions rendered inside a single chat turn, not a separate artifact), with a comparison table across the four current approaches and a case study on MDMA (MobileReality/mdma). The case study documents what holds up under source audit (a real deterministic validator/fixer pipeline, honest evals measuring 41% bare-prompt success vs. 90.5% with the DSL plus validator) against several overstated claims (no cryptographic guarantee of valid UI despite the 90.5%-not-100% figure, "runs anywhere" not extending to rendering since only a React renderer exists, the default chart component being an HTML table, webhooks only dispatching a UI event with no real HTTP call, "accessible by design" not backed by `aria-invalid`/`aria-live` or keyboard-operable PII-masking controls) and one unresolved functional bug found independently by two audit agents: form validation (`required`/`pattern`/`min`/`max`) is documented with worked examples but never enforced, because the form container is a `<div>` rather than a `<form>` and the submit button never triggers native constraint validation. Added a full evaluation at `docs/resource-evaluations/mdma-evaluation.md` (score 3/5, all claims verified against the local source tree at `/Users/florianbruniaux/Sites/divers-test/mdma` rather than the README alone), indexed in `docs/resource-evaluations/README.md`, and 8 new `deep_dive` entries in `machine-readable/reference.yaml`.

- **Multi-provider code review architecture** (`guide/workflows/multi-provider-code-review.md`): new workflow guide documenting a non-redundant 3-provider PR review setup, based on a mature production pattern: Claude Code Action owns deep semantic review and the merge-blocking gate, a deterministic tool (CodeRabbit or equivalent) owns PASS/FAIL pre-merge checks, a cross-file RAG tool (Greptile or equivalent) owns invariants that span multiple files. Covers role separation, the non-duplication rule across config files, a blocking CI gate script, batching for large PRs, delta-review, cross-tool deduplication, and the known friction of rule drift across the three configs. Added supporting templates: `examples/github-actions/claude-code-review-batched.yml` (domain-split matrix review for PRs over a file-count threshold) and `examples/github-actions/.greptile/` (config.json, rules.md, files.json). Added a `gate` job to `examples/github-actions/claude-code-review.yml` that parses the posted review's Must Fix count and fails the CI check, letting branch protection actually block merge on 🔴 findings instead of only commenting. Indexed in `guide/workflows/README.md` and `machine-readable/reference.yaml`, cross-linked from `guide/workflows/code-review.md`.

- **support-csm-agent.md** (`guide/workflows/support-csm-agent.md`): New workflow guide covering internal (non-client-facing) support/CSM agents built with Claude Code. Documents a 6-level maturity model (L0 reply drafting through L5 CSM pre-call briefing), the human-in-the-loop boundary that separates this pattern from buy-side deflection tools (Decagon, Intercom Fin, Ada), a read-only DB diagnosis pattern, security guardrails, and internal-throughput metrics (draft-to-send edit distance, time to first response) instead of a deflection rate. Cross-linked from `event-driven-agents.md`, `data-privacy.md`, and `team-metrics.md`.

- **HubSpot & Zendesk MCP servers** (`guide/ecosystem/mcp-servers-ecosystem.md`): New "Customer Support & CRM" category documenting `shinzo-labs/hubspot-mcp`, `baryhuang/mcp-hubspot`, and `reminia/zendesk-mcp-server` (verified via GitHub API for star count and last-push date; three lower-signal HubSpot alternatives evaluated and excluded for stale commits). Statistics table and maintainer count updated accordingly.

- **threat-db.yaml v2.23.0** (`examples/commands/resources/threat-db.yaml`): monthly threat intelligence update via `/update-threat-db`. New malicious skills from Unit 42's OpenClaw supply-chain report (money-radar, letssendit, omnicogg, ai-tradingview-assistant-for-macos, tradingview-ai-indicator-assistant). New CVEs: CVE-2026-50548/50549 (Cursor agent terminal sandbox escape, CVSS 9.8 each, also added to `guide/security/security-hardening.md` CVE table), CVE-2026-32871 (FastMCP OpenAPIProvider SSRF/path traversal), CVE-2026-32625 (LibreChat MCP access control, CVSS 9.6), CVE-2026-0621 (MCP TypeScript SDK ReDoS). New attack technique T033 "Agentjacking" (fake Sentry error injection tricking coding agents into executing attacker code, 85% success rate in disclosure testing). New defensive resources: Akamai's security analysis of the upcoming MCP spec, Microsoft's MCP governance rollout in VS Code/Azure APIM.

- **api-gateway.md** (`guide/ops/api-gateway.md`): New guide on setting up an API gateway (LiteLLM or Portkey) between Claude Code clients and Anthropic's API. Covers virtual keys, per-team budget limits, model allowlists, Prometheus metrics, OTel integration, and production Docker Compose setup. Addresses the P0 enterprise deployment gap (cost control and centralized permissions).

- **WebAssembly MCP tool sandboxing** (`guide/security/sandbox-isolation.md §7b`): New section covering Wassette, wasmcp, whamm, and splicer as an emerging Wasm-based approach to sandboxing MCP tools at the OS level. Includes tool comparison table, Wasmtime CVE caveat, and scope statement (Wasm isolation does not cover cost tracking or audit logs). Based on adversarial deep research (100 agents, 25 claims verified 3-vote).

- **Team-level log aggregation** (`guide/ops/observability.md §10`): New section covering two paths for centralizing Claude Code logs across a team: LiteLLM Gateway (recommended) and JSONL shipping to Loki. Includes OTel collector config for Tempo and Prometheus queries for Grafana dashboards.

- **Settings propagation guide** (`guide/security/enterprise-governance.md §2.3`): New subsection explaining three mechanisms for distributing Claude Code config to a team: shared settings.json in repos, CLAUDE.md hierarchy, and Anthropic Team/Enterprise admin console.

- **PR audit trail** (`guide/ops/ai-traceability.md`): New section covering what to capture at PR creation time, a PreToolUse session logger hook, a GitHub Actions workflow that uploads audit artifacts with 90-day retention, and a compliance report script.

- **Practitioner insights expanded to four new sources** (`guide/ecosystem/practitioner-insights.md`): added Devoxx (Java/JVM/architecture conference talks), Dev With AI Meetup (French AI-native development meetup), ByteByteGo (system design), and Stanford Online (academic ML/LLM coursework) alongside the existing IFTTD podcast corpus. Insight count grew from 22 to 65, with four new per-corpus source tables. Attributed field reports were also folded directly into `guide/security/security-hardening.md`, `guide/security/sandbox-native.md`, `guide/security/sandbox-isolation.md`, `guide/roles/agent-evaluation.md`, `guide/core/context-engineering.md`, `guide/ecosystem/mcp-servers-ecosystem.md`, `guide/ops/observability.md`, `guide/workflows/agent-teams.md`, `guide/roles/adoption-approaches.md`, `guide/roles/ai-roles.md`, and `guide/roles/learning-with-ai.md`. Notable additions: a formal Boolean-circuit bound on chain-of-thought reasoning (Denny Zhou, Stanford CS25 V5, 2025), a nine-speaker independent convergence on a 70% context-degradation threshold (Dev With AI Meetup), and a documented REX on unsupervised 24/7 agent delegation reducing team velocity. Also folded in field reports from The Product Crew (French product-management podcast) into `guide/roles/adoption-approaches.md` and `guide/roles/ai-roles.md`, treated as single-instance 2026 accounts rather than established data. Corrected a stale insight count (previously reported as 22 in `machine-readable/reference.yaml` and `guide/README.md` even before this expansion; the actual pre-expansion count was 35). Full attribution in `guide/core/credits.md`.

- **AI unit economics guide** (`guide/ops/ai-unit-economics.md`, new file): original synthesis addressing an unmodeled gap surfaced across all eight source corpora analyzed for the practitioner-insights expansion above (none of them model the real cost of agentic AI at scale). Covers per-task cost decomposition (input/output/cache/tool-call/sub-agent tokens), the four cost levers with practitioner sourcing where available (complexity-based routing, sub-agent context isolation, exit criteria and max-iterations, cache reuse), the break-even point of an autonomous agent, and team budget governance (cross-linked to `guide/ops/api-gateway.md` for implementation). Explicitly flagged in its introduction as original analysis, not a practitioner-sourced compilation.

- **llms.txt / llms-full.txt / machine-readable/llms.txt stats sync** (3 files): updated Last Updated to June 21 2026, Lines of Documentation from 26,058 to 26,494 (reflects current ultimate-guide.md line count), Production Templates from 314 to 262 (authoritative count from check-landing-sync.sh method), and inline body references in llms-full.txt (FAQ answer, repo structure, What Is section).

- **Team knowledge infrastructure guide** (`guide/ecosystem/team-knowledge-base.md`, new file): answers the question "where do we put the company knowledge base so both Claude Code and Cowork can use it?" Covers the 3-tier framework (static Markdown vault for direct file reads, MCP connectors for live systems like Jira/Confluence/Notion/GitBook, RAG at scale for large corpora), the ~100-1000 doc threshold for switching from direct reads to retrieval, Onyx (self-hosted, ex-Danswer), LlamaCloud and Ragie as managed RAG via MCP, the plugin pattern for distributing team workflows, and the Cowork-specific governance caveat (audit log and DLP gaps as of mid-2026). Includes setup code snippets, comparison tables, and a decision table for what to build first. Cross-linked from ultimate-guide.md Cowork section and guide/README.md Ecosystem table. Machine-readable index updated: 18 new entries in reference.yaml, shared_knowledge block in cowork-reference.yaml, llms.txt/machine-readable/llms.txt updated.

- **Practitioner insights from IFTTD podcast** (`guide/ecosystem/practitioner-insights.md`): new file consolidating paraphrased field insights from 11 IFTTD episodes (290-361), organized into 5 themes: context engineering, agentic patterns and orchestration, LLM evaluation, agent security, and DevX and adoption. 22 attributed insights from practitioners including Guillaume Laforge (Google Cloud), Zineb Bendhiba (Red Hat), Frédéric Barthelet (Theodo), Samy Lastmann (Arago), Jocelyn N'takpe (ManoMano), and others. All French content reformulated in English with attribution format: name, role, company, episode number, ifttd.io URL. No direct quotes.

- **Semantic chunking and synthetic question generation** (`guide/ecosystem/context-engineering-tools.md`, new subsection "Query-Side Indexing"): practical explanation of semantic chunking (boundary detection over fixed-token splitting) and synthetic question generation at index time (doc2query: Nogueira and Lin, 2019; HyDE: Gao et al., 2022). Retrieval improvement framed as Laforge's practitioner order-of-magnitude estimate, not a constant. Attributed to Guillaume Laforge (IFTTD ep 361).

- **Large context window anti-pattern note** (`guide/core/context-engineering.md`): practitioner paragraph after the Liu et al. "Lost in the Middle" citation clarifying that filling a 1M-token window is an anti-pattern, not a capability demonstration. Attributed to Guillaume Laforge (IFTTD ep 361). Also updated the Liu et al. citation to full form: "Lost in the Middle: How Language Models Use Long Contexts", TACL 2024, arXiv:2307.03172.

- **Evaluating probabilistic systems** (`guide/roles/agent-evaluation.md`, new major section): six subsections covering scored-dataset evaluation (not red/green unit tests), statistical CI/CD with bash example (replay 10-100x, measure success rate as percentage), async LLM-as-judge pattern, hallucination as a calibrated trade-off, OpenTelemetry and Langfuse observability with trace structure example, and workflow vs pure agent evaluation implications. Sources: Louis Pinsard (ep 338), Frédéric Barthelet (ep 329), Samy Lastmann (ep 311).

- **Agent security field incidents** (`guide/security/sandbox-native.md`, new subsection "Why Sandboxing Matters: Field Incidents"): two documented production incidents: guardrail evasion where an agent emptied a file when the delete operation was blocked (Zineb Bendhiba, ep 326), and data loss incidents including home directory wipes and database deletions across multiple agent products (Guillaume Lours, ep 360).

- **Command allowlist principle** (`guide/security/security-hardening.md`): practical paragraph at the start of the MCP vetting workflow section recommending specific allowlist patterns (allow git add and git commit, require explicit approval before git push, hard resets, force-deletes, or database mutations). Illustrated with a real incident involving Firefox bookmark loss (Jocelyn N'takpe, ep 346).

- **MCP usage principles** (`guide/ecosystem/mcp-servers-ecosystem.md`, new subsection after the Quality Score block): three field-derived principles: keep tool count small to reduce hallucination probability, design tools as complete user intents not atomic endpoints, and the LLM is stateless with respect to MCP routing. Sources: Zineb Bendhiba (ep 326) and Frédéric Barthelet (ep 329).

- **Practitioner testimonials** (`guide/workflows/agent-teams.md`): four new entries in the testimonials section: Samy Lastmann on micro-agents over mega-prompts (ep 311), Guillaume Laforge on harness engineering as the emerging term for multi-agent orchestration (ep 361), Quentin Adam on Claude orchestrating Gemini for large-context rewrites (ep 341), and Jocelyn N'takpe on ManoMano's production MCP stack at scale (ep 346).

- **Adoption field notes** (`guide/roles/adoption-approaches.md`): three paragraphs after the empirical data table covering ManoMano's documentation-as-onboarding approach (N'takpe ep 346), the Mundler et al. typed-language safety net study (ETH Zurich and UC Berkeley, PLDI 2025, arXiv:2504.09246, correctly cited as "94% of compilation errors are type errors" not "94% of agent errors avoidable"), and practitioner notes on alternating AI and manual coding to preserve deep system understanding (Deleuze ep 349) and capping AI-assisted development cycles per day against cognitive load (Lepine ep 351).

- **IFTTD attribution** (`guide/core/credits.md`): full attribution entry for the IFTTD podcast (Bruno Soulez, ifttd.io, 360+ episodes), listing all 9 guide sections that draw on IFTTD material with episode numbers and speaker names.

- **Third-party tool: CodeBurn** (`guide/ecosystem/third-party-tools.md`): new dedicated section under Token & Cost Tracking. CodeBurn (8,100+ stars, MIT, Node.js 22.13+) reads Claude Code JSONL session logs and classifies every turn into 13 categories (Coding, Debugging, Exploration, Conversation, etc.) via deterministic local pattern matching, no LLM calls. Key differentiator from ccusage: CodeBurn explains WHERE tokens went and correlates sessions with git commits via `codeburn yield`; ccusage tracks how much was spent. Notable commands: `optimize` (retry loops, redundant re-reads), `compare` (model breakdown), `yield` (sessions vs. shipped commits), `menubar` (macOS SwiftBar widget), MCP server (v0.9.12+). Covers verified usage patterns, cost estimate caveats (LiteLLM pricing, not Anthropic billing API), and when to use alongside ccusage.

- **Context engineering tool: Token Savior** (`guide/ecosystem/context-engineering-tools.md`): new section after tilth. Token Savior (Mibayy/token-savior, ~1,000 stars, Python 3.11+, MIT) is a three-in-one MCP server covering structural code navigation by symbol (replaces full-file reads), Bash output compaction (34 compactors for git/pytest/jest/kubectl, opt-in via `TS_BASH_COMPACT=1`), and persistent cross-session memory via SQLite FTS5. Covers 6 tool profiles (full/core/nav/lean/ultra/tiny), 15+ navigation tools, tsbench results (Claude Opus 4.7, 96 tasks, -77% active tokens, synthetic 2,000-line codebase), install via pip/uvx, comparison with tilth (tilth: faster, independently benchmarked, 14 languages; Token Savior: adds Bash compaction + cross-session memory).

- **Zero-install context reduction note** (`guide/ecosystem/context-engineering-tools.md`): brief entry for claude-token-efficient (drona23, 5,700+ stars) at the end of section 3. Frames it honestly as a single CLAUDE.md file that adjusts model output style, not a compressor. Notes the uncited 63% claim and the tool's ceiling (output tokens only, cannot compress shell output or file reads).

- **Section 9.18.5 Open Knowledge Format (OKF)** (`guide/ultimate-guide.md`): new section covering Google Cloud's OKF v0.1, published June 12, 2026. Explains the Karpathy LLM Wiki origin pattern (April 2026 gist, 16M+ views on X), how an OKF bundle works (directory of markdown files with YAML frontmatter, `type` field as the only required key), how OKF compares to existing patterns (CLAUDE.md, AGENTS.md, llms.txt sit at different layers), adoption status (v0.1 invitation not yet a standard, Google Cloud Knowledge Catalog already ingests it), decision guidance on when OKF fits vs llms.txt vs CLAUDE.md, and a minimal quick-start example. Existing 9.18.5–9.18.11 renumbered to 9.18.6–9.18.12.

- **Smart-suggest BM25 routing** (`guide/workflows/smart-suggest-routing.md` + `examples/hooks/bm25-routing/`): self-calibrating BM25 lexical scoring layer for `UserPromptSubmit` hooks; complements the existing regex smart-suggest with intent-based skill routing; includes runnable Node.js example with auto-calibration, detached index rebuild, and sample skill corpora

- **Context engineering tools: tilth and maki** (`guide/ecosystem/context-engineering-tools.md`, `guide/ecosystem/third-party-tools.md`): added documentation for two new token-efficiency tools discovered via HN community analysis. tilth (MCP server, `cargo install tilth`) uses tree-sitter for structural code navigation with benchmarked results of -40% cost and +10pp accuracy across Sonnet 4.6, Opus 4.6, and Haiku 4.5 (160 runs, 4 repos). maki (standalone Rust TUI agent, replaces Claude Code rather than augmenting it) with embedded Python code execution and dynamic model selection for subtasks. Also added a real-world cost calibration note to the RTK section: bash output is ~12% of total session token usage (not the dominant source), file reads are ~65%, so RTK's actual API bill impact is 6-10% despite its per-command compression ratios of 60-90%. Section 10 tool selection table updated with tilth for the "file reads consuming most of context budget" use case.

- **Third-party tool: SkillSpector** (`guide/ecosystem/third-party-tools.md`): added NVIDIA's skill security scanner to the Security Scanning section. SkillSpector scans skills before installation using 64 patterns across 16 categories (prompt injection, data exfiltration, MCP tool poisoning, trigger abuse, supply chain, rogue agent, taint tracking, YARA signatures). Two-stage pipeline: fast static analysis then optional LLM revalidation (~87% precision). SC4 pattern queries OSV.dev live for CVE data. Apache 2.0. Fills the gap between AgentShield (config audit) and DeepSec (app code audit): neither previously covered pre-install skill vetting.

- **Security check skill: deep skill content analysis** (`.claude/commands/security-check.md`, `examples/skills/security-check/SKILL.md`): Phase 3 now includes a "Deep skill content analysis" block inspired by SkillSpector patterns. Adds detection for hidden HTML comments and zero-width characters in skill files (TP1), base64 blobs over 40 chars (TP1/SC3), RTL unicode override characters (TP2), trigger keywords shadowing built-in commands (TR2), `curl | bash` patterns in skill scripts (SC2), cron/launchctl persistence writes (RA2), and env-harvesting-plus-network-call combinations (E2+E1). Applied to both the command version and the skill template.

- **Third-party tool: Ponytail** (`guide/ecosystem/third-party-tools.md`): added to Plugin Ecosystem / Notable skill packs and Recommendations by Persona. Ponytail is a cross-agent skill that enforces a "lazy senior dev" decision ladder before writing code (YAGNI → stdlib → native platform feature → installed dependency → one line → minimum that works). Benchmarked at 80-94% less code, 47-77% lower cost, and 3-6x faster than unconstrained agents across Haiku/Sonnet/Opus. Ships with 4 commands (`/ponytail`, `/ponytail-review`, `/ponytail-audit`, `/ponytail-debt`) and supports 13 agents. MIT, by DietrichGebert.

- **Search index: GDPR/Privacy and Governance sections** (`machine-readable/reference.yaml`): added 16 `data_privacy_*` entries covering data flow, retention tiers (5y/30d/ZDR), known risks (`/bug` command, `.env` exposure, MCP DB), protective measures, and GDPR/HIPAA/PCI compliance. Governance and privacy sections are now searchable via cmd+k on the landing site and link to the local guide reader at `cc.bruniaux.com/guide/`.

- **Section 9.26 Review-Driven Context Optimization** (`guide/ultimate-guide.md`): new advanced pattern covering how to convert structured inline review feedback (via tools like [crit](https://github.com/tomasz-tomczyk/crit)) into CLAUDE.md rules. Covers the round-to-round diff as a verification mechanism, pattern extraction from review comment threads, promotion criteria, and the compounding effect over multiple sessions. Cross-referenced with §9.24 (Instinct-Based Learning) and §9.23 (Update Loop). Added to chapter 9 quick jump and ToC.

- **Resource evaluation: crit** (`docs/resource-evaluations/crit-human-in-loop-review.md`): score 4/5, decision: integrate. Tool by tomasz-tomczyk for human-in-the-loop review with round-to-round diffing, inline plan review before execution, DOM-anchored web app comments, and native Claude Code integration.

- **Hermes Agent section** (`guide/ecosystem/agentic-tools.md`): updated to v0.15.1 (from v0.14.0). Added concrete GEPA benchmark (40% faster task completion after 20+ auto-generated skills). Expanded Quick Start with `hermes chat` entry point and WSL2/no-WebUI note. Added "Known Operational Issues (v0.15.x)" subsection covering 7 production pitfalls with YAML/bash fixes: analysis-before-action via SOUL.md, SOUL.md vs AGENTS.md separation, kanban parallelism flood (`max_in_progress_per_profile: null` default), subprocess PATH inheritance (`env_passthrough`), worker protocol violations (missing `kanban_complete`), SQLite corruption with backup strategy, `HERMES_HOME` not propagated to subprocesses, and token overhead (~13,900 fixed tokens per call, gateway multiplier). Issues traced to community reports #28712, #18594, #4379, #23717.

### Changed

- **data-privacy.md** (`guide/security/data-privacy.md`): reframed around CLI-specific risks for practitioners. Removed policy-paraphrase sections (retention tiers, Constitutional AI, IP considerations). Enriched the `/bug` command section with live verification commands and clarification that session context is included without scrubbing. Added a 7-point Quick Audit Checklist with runnable shell commands (training opt-out, bug command, env file blocking, native messaging host, MCP inventory, telemetry vars, env secret exposure). Section numbering updated throughout.

- **Threat intelligence now starts in AgentSec, not in the guide** (`.claude/commands/update-threat-db.md`, `examples/skills/update-threat-db/SKILL.md`, `examples/skills/update-threat-db/threat-db.yaml`, `examples/commands/resources/threat-db.yaml`, `guide/security/security-hardening.md`): replaced both guide update workflows with delegators to AgentSec's source, event, IOC, test, generation, and feed-sync workflow. Deleted the unmaintained v2.18 skill database copy and removed every live reference to it. Kept the command database as a compatibility consumer for `/security-check` and `/security-audit`. Corrected the Paperclip guidance to distinguish immutable commit or digest pins from mutable names, classified Ghostjacking as indirect prompt injection through observability data, attributed Tenet's measurements to Tenet, and changed agent-jackstop from "open source" to "public repository with no identified software license".

### Fixed

- **Two positional references drifted after the security guide expansion** (`machine-readable/reference.yaml`, `mcp-server/content/reference.yaml`): updated the Docker network-policy and Agent Skills supply-chain targets to their current heading lines and added machine-checked anchor declarations so future line insertions can repair them safely.

- **`check-landing-sync.sh` reported a false quiz-count mismatch on every run** (`scripts/check-landing-sync.sh`): the quiz check compared `QUESTIONS_COUNT` against `LANDING_QUESTIONS_HERO` unconditionally, but `HeroBanner.astro` was refactored to render `{stats.quizQuestionCount}` from `site-stats.ts` instead of a hardcoded number, so the grep for a literal `[0-9]+ questions` pattern always returned empty and the comparison always failed. The templates check just above it already guarded this exact case (`-n "$LANDING_TEMPLATES_HERO"`), the quiz check never got the same guard. Applied the same empty-value guard so a dynamically-rendered stat no longer registers as drift.

- **91 files still carried pre-subdirectory-migration guide paths, invisible to the anchor and path checks because they live outside `machine-readable/reference.yaml`** (`docs/resource-evaluations/*` ~55 files, `.claude/` and `.agents/` mirrors, `examples/`, `quiz/questions/{11-learning-with-ai,12-architecture}.yaml`, `whitepapers/{en,fr}/*.qmd`, `mcp-server/{IDEAS.md,src/prompts/index.ts}`, `README.md`, `CHANGELOG.md` historical entries): the `guide/` restructure that moved files into `core/`, `security/`, `ecosystem/`, `ops/`, `roles/`, and `workflows/` subdirectories only updated links the reference/anchor validators cover. A repo-wide sweep found flat paths like `guide/architecture.md` still pointing at a location nothing has occupied since the migration, 289 replacements in `CHANGELOG.md`'s own historical entries alone. 25 further dead anchors were fixed in the same pass, each verified against the repo's own `slugify()` output rather than assumed from the text.

- **A dangling `#27-configuration-decision-guide` anchor in `README.md` and three "See also" cross-references inside `guide/ultimate-guide.md`, all pointing at a TOC entry for a section that had already been deleted**: the phantom "2.7 Configuration Decision Guide" line survived in the table of contents and the "Quick jump" bar after the section itself was merged into Memory Loading Comparison. All four now point at `#memory-loading-comparison`, with matching visible link text.

- **`slugify()` diverged from the real `github-slugger` package (missing `.strip()`), producing dead anchors in three independent copies of the function** (`scripts/resync-reference-yaml.py`, `scripts/validate-reference-yaml.py`, `scripts/gen-section-maps.py`): a heading with trailing whitespace before its closing produced a slug with a trailing hyphen the real GitHub renderer never emits, so anchors built from it 404 in production while validating clean locally, since all three copies shared the same bug and cross-checked each other into agreement. Found via two independent agent investigations (a Cmd+K duplication regression and an undeclared bare-integer audit) that both surfaced the same root cause from different symptoms. Fixed at the source and the two duplicate copies now import from it instead of re-implementing it. 10 heading-to-slug pairs pinned against the real `github-slugger` package in the test suite so the divergence cannot silently return. 16 dead anchors in the live index traced to this bug and repaired.

- **Ambiguous-slug references were stuck at a permanent LOW-confidence floor with no path to resolution** (`scripts/resync-reference-yaml.py`): `anchor_line()` correctly refuses to guess when a slug matches more than one heading, but three references (`task_hierarchy_design`, `task_status_transitions`, `task_metadata_conventions`) legitimately pointed at a "Best Practices" heading duplicated four times in the guide, and no declared-anchor comment could resolve them since a `# anchor:` declaration is refused the same way on an ambiguous slug. Added a `hint_line` parameter: the stored line resolves the ambiguity if and only if it is exactly one of the real candidate headings, so drift outside that candidate set is still caught rather than silently accepted. Three tests confirm the hint resolves either candidate and still refuses a hint that matches none of them.

- **`llms-full.txt`'s Hooks section listed 9 hook filenames that do not exist in `examples/hooks/`, and falsely claimed PowerShell mirrors every bash hook 1:1** (`llms-full.txt`): an earlier audit pass fixed 4 dead paths and 3 stale counts in this file but left the Hooks list unverified against the filesystem. Rewritten against `ls examples/hooks/{bash,powershell}/`: 12 real bash hooks replace the fabricated list, and the PowerShell section now states it covers a subset (2 files), not a mirror. The Agents count was also off by two (23 claimed, 21 real, `loop-monitor.md` was missing from the enumerated list).

- **The Cmd+K search index carried 698 entries resolving to only 464 distinct URLs** (landing repo, `scripts/build-guide-index.mjs`): the entry generator stripped anchors before deduplicating, so every `deep_dive` key pointing at a different heading in the same guide file collapsed onto one search result, and the anchor a user actually needed was gone by the time the entry reached the palette. Rewrote the loop to keep anchors and dedupe on the final resolved URL instead of the bare path, with an explicit map for the three guide files that are client-side-redirect stubs (`ai-ecosystem.md`, `ai-roles.md`, `claude-code-releases.md` reroute to `/ecosystem/`, `/roles/`, `/releases/`, which share no heading structure with the guide markdown at all and would otherwise have silently produced 3 more broken entries). Verified against the actual built `dist/` HTML: 696 entries, 696 distinct URLs, 0 collisions, all 266 non-GitHub entries resolve.

- **Deleting one TOC line shifted every reference below it by one, and the ratchet's confidence-based check caught only some of the damage** (`machine-readable/reference.yaml`): removing the phantom "2.7 Configuration Decision Guide" TOC entry shifted the rest of `guide/ultimate-guide.md` by -1 line. `--apply` auto-repaired the 25 declared-anchor references whose line had drifted, but 73 undeclared references (56 bare integers, 12 `path:line` refs into `ultimate-guide.md`, 5 into `guide/security/sandbox-isolation.md`) sat below the word-overlap heuristic's confidence floor and needed a targeted fix. Diagnosed by classifying the same reference set against the pre-edit commit in a worktree (611 apparent baseline failures turned out to be a copy artifact from only 3 files being present; a full worktree checkout showed the true pre-existing baseline was 8, all `ANCHOR_DEAD`, unrelated to this shift) and confirming programmatically that every one of the 73 resolved to sensible content at exactly `old_line - 1`. One `--apply` run had already produced a bad auto-repair earlier in this same investigation (`mechanism_comparison_table` jumped to an unrelated "Scheduled Tasks" table on generic "comparison table" word overlap), caught by reading the actual content at both locations before accepting it, corrected by hand with a declared anchor. The 12 `path:line` refs were migrated to `path#anchor` where the shifted target landed on a real heading (8 of 12; the other 4 landed on code-block comments that only coincidentally start with `#`, kept as corrected line numbers). One ambiguous target (`security-considerations`, 3 duplicate headings) was kept as a corrected line number rather than a plain anchor, to avoid re-introducing the exact ambiguity this file's `hint_line` mechanism exists to catch. `resync-reference-yaml.py --check` now reports a genuine 0 broken (up from a false 0 that a path-string bug in an ad hoc verification script had reported earlier in the same investigation), confirmed against the full CI suite: `validate-reference-yaml.py --ci` 0 hard failures, `test-resync-reference-yaml.py` 57/57, `check-index-coverage.py` 92/92.

- **The `reference.yaml` positional-reference backlog is closed: 145 to 0, and the CI ratchet is gone rather than lowered** (`machine-readable/reference.yaml`, `scripts/resync-reference-yaml.py`, `.github/workflows/index-integrity.yml`): every one of the 145 was decided from the real content of its target file, in groups by file, never by lowering a confidence threshold. 137 became `path#anchor` after checking which heading the key actually meant. Two measurement defects surfaced first, and both had been inflating the "undecidable" figure. 29 of the 37 UNKNOWN were not undecidable: the header index was built from a hardcoded whitelist of 14 files, so any reference into a file outside it scored against an empty index. `rpi_phase1_research` and `rpi_phase2_plan` were the standing example of an intractable case, and rpi.md has `## Phase 1: Research` and `## Phase 2: Plan` as real headings all along; they were invisible only because the file was not on the list. No guide edit and no key deletion were needed. Separately, 8 genuine references were out of scope entirely, hidden by the same substring guard the tool had already narrowed elsewhere: `claudemd_sizing` caught by "sizing", `tasks_api_limitations` by "limit", `subscription_token_budgets` by "budget", `subscription_opus_ratio` by "ratio", and four more. Bringing them into scope raised the honest starting figure from 145 to 153 before a single repair.

- **A bare integer can now declare which heading it means, which replaces a heuristic with a hard check** (`machine-readable/reference.yaml`, `scripts/resync-reference-yaml.py`, `scripts/validate-reference-yaml.py`): the last 8 references could not be confirmed by token overlap even with verified targets, because the key name and the heading share no words. `cicd` pointing at "9.3 CI/CD Integration" is correct and scores zero, since the heading spells it "CI/CD". Weakening the heuristic to absorb that would have been guessing at scale in the other direction. A trailing `# anchor: some-slug` says which section the author meant, and the stored line is then correct if and only if it equals the line of the heading with that slug. Ambiguity resolves to a failure rather than to the first match, because GitHub suffixes a repeated slug `-1` and a duplicated slug identifies nothing. `--apply` repairs the line deterministically when text shifts above it, which is exactly the drift that produced this rot. Bare integers stay integers because the landing turns every `deep_dive` string starting with `guide/` into a Cmd+K entry, so converting the remaining 108 would add that many entries pointing into a 26,554-line file.

- **Both CI gates were shown to fail before being trusted, including the ratchet, which never had been** (`.github/workflows/index-integrity.yml`): the strict gate exits 1 on a corrupted guide anchor and on a declared anchor sitting 3 lines off its heading, naming the drift in both cases, and returns to 0 on restore. The ratchet exits 1 on a drifted declared anchor, then `--apply` repairs 15030 back to 15027 and it returns to 0; it exits 1 again on a typo'd declared anchor, reported as ANCHOR_DEAD. `--max-broken 145` is deleted rather than reduced, so the default of 0 fails the build on the commit that introduces the next imprecise reference. The workflow's path triggers now include `scripts/**` and the workflow file itself, which they did not: a change that broke a gate could not fire the workflow that runs it, only a later unrelated content edit could.

- **The two overlapping repair tools are one, and its four traps are covered by tests that fail on bad input** (`scripts/resync-reference-yaml.py`, new `scripts/test-resync-reference-yaml.py`, `scripts/fix-reference-refs.py` deleted): the earlier merge commit landed the combined tool but left the old one on disk. The test suite is 43 assertions and each trap is checked by a test that discriminates, running the known-bad implementation against the same input and asserting it is wrong. Verified by breaking each guard in turn: removing the counter guard produces 6 failures, widening it back to substring matching produces 8, replacing the fence tracker with a naive toggle produces 6, and loosening the path pattern to `"([^"]+):(\d+)"` produces 2. Two assertions about the fence trap were written wrong at first and the measurement corrected them. The synthetic fixture had a 4-backtick block containing a matched 3-backtick pair, so the naive toggle balanced out and got the right answer; it now contains a single unmatched opener. And on `enterprise-governance.md` the naive toggle does not find fewer headings, it finds more: 63 against 37. The failure is two-sided. Stuck inside a fence it drops 19 real sections; stuck outside one it invents 45 headings out of shell comments and the CLAUDE.md examples embedded in code blocks. Counting headings alone hides this, because the invented outnumber the dropped. The earlier note that it "dropped 9 valid sections" was an undercount.

- **The MCP server's bundled content is now gated in CI, after drifting again** (`.github/workflows/index-integrity.yml`, `mcp-server/content/reference.yaml`): `mcp-server/content/` is a hand-copied bundle published to npm, nothing regenerates it, and nothing checked it. It had drifted before, and it drifted again the moment `reference.yaml` was repaired. Same failure class as the reference rot itself, a copy nobody verifies. The gate diffs the three files against `machine-readable/` and prints the `cp` that fixes each one; verified by perturbing `llms.txt` and confirming exit 1, then restoring and confirming exit 0.

- **Two dead anchors nothing was checking** (`machine-readable/reference.yaml`): `configuration_decision_guide_anchor` pointed at `#27-configuration-decision-guide`, a section that no longer exists, and it was invisible to the anchor validator because a bare `#slug` with no path does not match the pattern. It now points at Memory Loading Comparison, where the mechanism comparison table and the 56% skill-invocation warning both actually live. `security_claude_folder_audit` carried a comment naming §1.4 Repository Pre-Scan while its key names the .claude/ audit in §1.5; the key wins, and the comment now records the contradiction instead of hiding it.

- **The sandbox configuration example used six keys that do not exist** (`examples/config/sandbox-native.json`): `autoAllowMode`, `filesystem.allowedWritePaths`, `filesystem.deniedReadPaths`, `network.policy`, `excludedCommands` in the bare-name form, and `${HOME}` / `${CWD}` interpolation. The real keys are `autoAllowBashIfSandboxed`, `filesystem.allowWrite`, `filesystem.denyRead`, no `policy` field, the glob form, and `~/` or `/` prefixes with no interpolation. There was no `credentials` block at all. Copying this file produced a sandbox that protected none of what its own comments claimed, which is worse than a documentation gap: prose gets read critically, an example gets pasted. Rewritten against a configuration verified on 2.1.220 across a 200-repository park, with comments that explain each trap rather than paraphrasing the key names.

- **`llms-full.txt` carried 104 em dashes, starting on line 1** (`llms-full.txt`): the repo bans them and the `PostToolUse` hook enforces it, which meant the file could not be edited at all until it was cleaned. Converted to colons where the dash separated a label from its description (100 cases, the numbered section list and the bullet lists) and to commas elsewhere (4). Also adds a Security & Sandboxing block to the guide-structure section, which named ten guide areas and omitted the one this release documents most.

- **`excludedCommands` documented with a form that silently does nothing, in six places** (`guide/core/settings-reference.md`, `guide/security/sandbox-native.md`): every example used the bare-name form (`"excludedCommands": ["git", "docker"]`), which matches only the zero-argument string and therefore never fires on a real invocation. A reader following the guide configures something inert, sees the command still sandboxed, and has no way to tell why. This is the form the published JSON schema suggests, which is what makes it the default mistake ([anthropics/claude-code#10524](https://github.com/anthropics/claude-code/issues/10524)). All six examples now use the glob form, verified on 2.1.220 where `"git"` had no effect and `"git *"` worked immediately. Both the `sandbox.excludedCommands` reference entry and the `excludedCommands` section of the sandbox guide gained a warning about the second, worse trap: once a glob does match, **the entire Bash invocation runs unsandboxed**, including commands that execute before the excluded one, so `git status && cat ~/.ssh/id_ed25519` reads the key with `"git *"` in the list ([#81157](https://github.com/anthropics/claude-code/issues/81157), open as of 2026-07-25 on 2.1.220). Both now document the mitigation: scope entries to the subcommands that need the network (`git push *`, `git fetch *`, and so on) rather than the binary, which keeps local git confined. Git over SSH is what forces the exception at all, since the sandbox proxy handles HTTP and HTTPS but not port 22 and blocks the `ssh-agent` socket, so an SSH remote fails at DNS resolution.

- **Two factual errors in the sandbox documentation** (`guide/security/sandbox-native.md`, `guide/security/sandbox-isolation.md`, `guide/security/security-hardening.md`): the guide claimed `curl` and `wget` are "blocked by default in the sandbox to prevent arbitrary web content fetching". There is no such blocklist. Both are constrained by the network allowlist like any other command, and a request to an allowed domain succeeds without a prompt: `curl https://api.github.com` returned HTTP 200 in 84 ms under auto-allow on 2.1.220, while a non-allowed host hung to timeout (`HTTP 000`, curl exit 28). The corrected text names the hang as the symptom to recognize, since a missing domain does not produce a clean error. Separately, five configuration examples used an `autoAllowMode` key that does not exist in any released version; the real key is `autoAllowBashIfSandboxed`.

- **Web and CLI quiz banks resynced onto a single source of truth, closing a two-bank content fork** (`quiz/questions/*.yaml`, `quiz/scripts/generate-from-web.mjs`, `quiz/README.md`, landing `src/content/questions/**`, `src/content.config.ts`, `src/utils/categories.ts`): the web quiz (Astro, one Markdown file per question) and the CLI quiz (YAML per category) had drifted past simple count mismatches. 344 shared `NN-YYY` ids held 38 outright answer contradictions and 60 unrelated questions reusing the same slot, and a further 60 CLI questions hid inside id slots that also existed in web with different content, undercounting the true gap. A full id-and-text cross-reference found 82 CLI questions with no web equivalent by any matching method. Each was triaged against the current guide before porting: 10 dropped for stale-model claims superseded by later releases (v2.1.90 fixed the exact caching bug one question described as unresolved) or answers the current guide contradicts outright; 72 ported into the web bank with fresh, non-colliding ids (the fork made old ids unsafe to reuse) and, where the CLI's declared `doc_reference` no longer matched any real heading, corrected to the anchor the content actually moved to (several had followed Agent Teams content from `ultimate-guide.md` into the dedicated `guide/workflows/agent-teams.md`). Team Metrics becomes web category 17. The web bank (canonical, 473 questions) now regenerates the CLI YAML through a one-way script (`pnpm sync-from-web`, with a `--check` mode for CI drift detection) that preserves each category's `source_file` header and replaces only its questions; the CLI README now tells contributors to edit the web Markdown and regenerate, not hand-edit the YAML, which is the practice that let the two banks fork in the first place.

- **Broken YAML frontmatter on GitHub for 6 skill templates** (`examples/skills/{autoresearch,canary,investigate,qa,plan-pipeline/ceo-review,plan-pipeline/eng-review}/SKILL.md`): unquoted colons inside `description:` values ("Strategic product gate: challenge the brief...") made GitHub's YAML parser fail with "mapping values are not allowed in this context", showing an error banner instead of the rendered frontmatter. Quoted all six descriptions and validated with a YAML parse.

- **check-landing-sync.sh broken since the Astro migration** (`scripts/check-landing-sync.sh`): four of six checks still grepped the deleted `index.html`/`quiz/index.html`, and `set -e` killed the script mid-run on the first failed grep, so the version, quiz, guide-lines, and CC-version checks never executed (the script also referenced a `$QUESTIONS_COUNT` variable that was never computed). Rewrote all checks against the Astro sources: guide version from `AnnouncementBanner.astro`, quiz count from `questions/*/*.md` compared against `quiz/index.astro`, `HeroBanner.astro`, and the `index.astro` meta description, guide-lines against the "NK+ lines" claim with a 2K tolerance, CC version from the first `releases.ts` entry plus an exactly-one-`latest: true` flag check. Dropped the GitHub stars check (the landing fetches stars live client-side, there is no static value to sync). First run immediately caught a real drift: the landing meta description claimed a 346-question quiz against 330 actual questions, fixed in the landing repo.

- **Recap cards deployment sync (portfolio + landing)**: neither the July 2 FR pass nor the July 3 EN pass had been deployed; the landing kept serving the stale hashed PDFs. Deployed the 24 corrected cards (10 FR + 14 EN) with new hashed filenames to `florian-portfolio/public/guides/recap-cards/`, rebuilt all 6 series ZIPs (T/M/C × FR/EN), updated `CARD_HASHES_FR/EN` and the 6 `hashedZip` entries in the landing `recap-cards-data.ts`, and refreshed the `guides.mjs` email-link manifest (also added the previously missing `recap-conception.fr/en` entries). Also added the landing repo to `ALLOWED_PATHS` in `.claude/settings.json`, it was the only documented sync target missing from the hook allowlist (portfolio was already there).

- **Content freshness pass on 14 EN recap cards** (`whitepapers/recap-cards/en/`): same audit as the July 2 FR pass, all 10 FR problems confirmed present in EN and fixed (dead `autoApproveTools`/top-level `allowedTools` keys replaced with `permissions.allow` in t04/c06/t06, `.claude/commands/` updated to `.claude/skills/` in c03/t09/t10/t06, fictitious `--context` flag removed from 01/04, permission-mode canonical names plus `PreCompact`/`SessionEnd` events in 03/m11). The EN pass additionally caught 6 findings the FR audit missed, verified against `claude --help` and `guide/core/settings-reference.md`: fictitious `--no-stream` flag (01, t02), fictitious `--task-manage` flag presented as native CC "since v2.1.19" (m07, it is a SuperClaude framework flag; the real behavior is Tasks API on by default since v2.1.142), non-existent `{"vim": true}` key (01, real key `editorMode: "vim"`), `spinnerVerbs.mode: "add"` (t06, valid values `replace`/`append`), non-existent `sandbox.network.policy` key (t16), and a settings-style `allowedTools:` snippet (c08). These 6 are still present in the FR counterparts. All 14 EN PDFs rebuilt. Full breakdown in `whitepapers/CHANGELOG.md`.

- **WP03 FR stale malicious-author/skill counters** (`whitepapers/fr/03-securite.qmd`, wp-version 1.4.0 → 1.4.1): the July 2 EN freshness pass had flagged these counts as stale in both languages but only fixed the EN file. FR still stated 5 confirmed malicious authors and 314+/341+ malicious skills. Corrected against `threat-db.yaml` v2.23.0: 6 confirmed authors (sakaen736jih was missing), hightower6eu alone at 677 VirusTotal-confirmed skills, ClawHavoc campaign grown from 341 to 1,184+ confirmed entries by March 1, 2026. PDF and EPUB rebuilt.

- **Broken data_privacy anchors in machine-readable index** (`machine-readable/reference.yaml`): the late-June rewrite of `guide/security/data-privacy.md` renumbered sections (Known Risks 3→2, Protective Measures 4→3, Enterprise Considerations 6→5) and removed the retention-tiers detail and IP sections, leaving 10 of 14 `data_privacy_*` anchors dead. Fixed all section-number anchors, corrected the TL;DR slug (`tl-dr` → `tldr`, GitHub slugger drops the semicolon without a dash), completed the truncated Risk 6 slug, repointed `data_privacy_zdr` to the Enterprise ZDR section and `data_privacy_checklist` to the new Quick Audit Checklist, removed the two entries whose target sections no longer exist (`retention_policies`, `ip_considerations`), and refreshed `data_privacy_description`. Documented the Cmd+K search index rebuild (`pnpm build:search`, `scripts/build-guide-index.mjs`) in a new section of `docs/workflows/landing-sync.md`, which the workflow referenced implicitly but never described.

- **Content freshness pass on all 13 EN whitepapers** (`whitepapers/en/00-12`): the FR pass surfaced a suspicion that EN carried the same drift, confirmed by the same 13-agent audit method. Same class of gaps found: WP04 and WP07 EN had the identical "sub-agents cannot spawn sub-agents (depth=1)" factual error, WP08 EN was missing the same 450-line Advanced Orchestration Patterns section, WP11 EN was missing the same Agentic Metrics section, WP12 EN was missing the same 4 evaluation subsections. Every fix was independently verified line-by-line post-edit after an earlier FR fix on WP00 was found to have missed its series-list correction despite a clean version bump. `whitepapers/en/05-team.qmd` confirmed untracked by git (blanket `whitepapers/` gitignore, unlike its siblings), flagged not fixed. Full breakdown in `whitepapers/CHANGELOG.md`.

- **Content freshness pass on 10 FR recap cards** (`whitepapers/recap-cards/fr/`): dead `settings.json` keys (`autoApproveTools`, top-level `allowedTools`) replaced with the canonical `permissions.allow` in t04/c06/t06; `.claude/commands/` references updated to `.claude/skills/` (CC 2.1.3 merge) in c03/t09/t10; fictitious `--context` CLI flag removed from 01/04; permission mode canonical names, `PreCompact`/`SessionEnd` events, and a factual error (Shift+Tab×2 activates Plan Mode, not "Auto-accept all") fixed in 03/m11. All 10 rebuilt.

- **Content freshness pass on all 13 FR whitepapers** (`whitepapers/fr/00-12`): a version-only audit had marked all 13 whitepapers "fresh" (recent version field), but a deep content audit (13 dedicated sub-agents, one per whitepaper, cross-referenced against `CHANGELOG.md [Unreleased]` and `machine-readable/`) found real drift, including two factually wrong claims. WP04 and WP07 both stated sub-agents cannot spawn sub-agents ("depth=1"), outdated since Claude Code v2.1.172 (now up to 5 levels), and both were missing Sonnet 5 as the default model. WP08 was missing an entire "Advanced Orchestration Patterns" section (7 patterns, ~450 lines in the source guide) despite being previously judged up to date. WP11 was missing the whole "Agentic Metrics: What DORA Doesn't Measure" section, the WP's actual core topic. Full breakdown of all 13 corrections in `whitepapers/CHANGELOG.md`.

- **MCP Registry claim in support/CSM agent content** (`guide/workflows/support-csm-agent.md`, `guide/ecosystem/mcp-servers-ecosystem.md`): corrected a false claim that the official MCP Registry doesn't list HubSpot/Zendesk servers. Verified by direct query against `registry.modelcontextprotocol.io/v0/servers`, which does list several self-published entries. Added the distinction that `modelcontextprotocol/servers` (GitHub repo) is reference-only and defers to the registry for discovery, while registry presence itself signals submission, not vendor endorsement. Kept the existing star-count/commit-recency picks since the registry doesn't expose those signals.

- **Whitepaper count drift across machine-readable index** (`machine-readable/reference.yaml`, `llms-full.txt`, `guide/cheatsheet.md`): three files independently understated the whitepaper count (9, 11, and 10 respectively) against the actual 13 whitepapers (00-12) on disk. Corrected all three to 13, extended `whitepapers_topics` in reference.yaml with the 4 missing topics (learning, budget, team-metrics, agent-engineering), and added a `recap_cards_*` index block since the 57-card recap-cards series had zero entries in reference.yaml.

- **WP11 wp-version mismatch**: `whitepapers/en/11-team-metrics.qmd` had `wp-version: 1.0.0` while the FR counterpart was already at `1.0.1`. Synced EN to `1.0.1` and rebuilt the PDF.

- **audit-whitepapers command mapping table gap** (`.claude/commands/audit-whitepapers.md`): the WP-to-guide-section mapping table stopped at WP10, meaning WP11 (team-metrics) and WP12 (agent-engineering) could never get a content-staleness score from `/audit-whitepapers`. Added both rows.

- **whitepapers/fr/cheatsheet.qmd was not in French**: the "FR" cheatsheet had `lang: en` and English-only content, essentially a stale duplicate of the EN cheatsheet. Rewrote it as an actual French translation, and refreshed both FR and EN cheatsheets with commands and features added since v3.27.6-3.29.2 (`/powerup`, `/ultraplan`, `/rc`, `/mobile`, `/voice`, `/recap`, `/effort`, `/loop`, `/goal`, Ctrl+F, expanded permission modes, unified `skills/` folder structure, Search Tools quick reference). Both bumped to version 3.41.1, wp-version 1.1.0, and rebuilt.

- **Dead relative links across the `git-worktree` skill suite** (`examples/skills/git-worktree*/SKILL.md`): fixed 13 broken relative links that 404'd on GitHub. In `git-worktree/SKILL.md`, the three "Companion commands" links pointed at `./git-worktree-{status,remove,clean}.md` (same directory) instead of the command files at `../../commands/`, and the "Database Branch Setup Guide" link used `../workflows/` instead of `../../workflows/`. The `git-worktree-status`, `git-worktree-remove`, and `git-worktree-clean` skills each had a "Part of:" line whose three cross-references used `./*.md` (same directory) instead of `../../commands/`. All links now resolve to existing files.

- **Dead relative links in `review-pr`, `sandbox-status`, `scaffold`, `session-save` skills**: fixed 10 more broken relative links found via a full scan of `examples/skills/`. These used the wrong `../` depth — `../../guide/...` (resolving to the non-existent `examples/guide/`) instead of `../../../guide/...`, and `../hooks/`, `../config/`, `../agents/`, `../skills/` (resolving inside `examples/skills/`) instead of `../../`. All now resolve to the repo-root `guide/` and the `examples/{hooks,config,agents,skills}/` directories. Verified the full `examples/skills/` tree (117 files, 57 relative links) is now 0 dead links.

- **Dead relative links in `docs/resource-evaluations/`**: fixed 10 broken navigation links found via a full link scan (1002 relative links across 259 files in `guide/` + `docs/`). Wrong `../` depth or stale filenames in `mikul-gohil-hooks-evaluation.md`, `nick-jensen-plugins.md`, `beyond-vibe-coding.md`, `siddhant-khare-ai-fatigue.md`, `system-prompts-official-vs-community.md`, and `2026-02-07-paul-rayner-agent-teams-linkedin.md` — they pointed into non-existent `docs/guide/` or `examples/guide/` paths instead of the repo-root `guide/` subdirectories. Illustrative paths inside code blocks, the generated `ultimate-guide.fr.md`, and 3 intentional/forward-reference links were left untouched. (The matching `guide/` link fixes were already merged upstream.)

- **Security: shell injection in `claude-issue-triage.yml`** (`examples/github-actions/claude-issue-triage.yml`): `github.event.issue.title` and `github.event.issue.body` were interpolated directly into shell via `${{ }}`, allowing an attacker to inject arbitrary commands by crafting a malicious issue title. Fixed by moving both values to step-level `env:` (`ISSUE_TITLE`, `ISSUE_BODY`) and referencing them as plain shell variables, so GitHub Actions never interpolates user content into the script text. Reported in issue #50.

- **llms.txt/llms-full.txt/AGENTS.md were stale, missed by the release-tracking workflow** (`llms.txt`, `machine-readable/llms.txt`, `mcp-server/content/llms.txt`, `llms-full.txt`, `AGENTS.md`, `CLAUDE.md`): `llms.txt` still said "tracking Claude Code up to v2.1.220 (July 2026)" after the v2.1.237 tracker update, exactly the drift `/update-infos-release` step 4 exists to prevent. Bumped it to v2.1.237, re-synced the byte-identical `machine-readable/` and `mcp-server/content/` copies. `llms-full.txt` carried a stale "Last Updated: July 30, 2026", a line count 114 lines too high (from before the `/ultraplan` deletion), and the same outdated `/simplify` description already fixed elsewhere. `AGENTS.md` said "currently 3.40.0" and "~20K lines" for a guide already at 3.41.1 and 26,581 lines; it had never been touched since 2026-06-16 because it isn't wired into `sync-version.sh`. Tried adding it to the script, then reverted: `AGENTS.md` and `CLAUDE.md` both cite version bumps illustratively in their command examples (`3.9.11 → 3.9.12`), and the script's blind `3.x.x` regex would corrupt those into nonsense. Documented the exclusion in both files instead, so the fix stays a manual "currently X.Y.Z" edit going forward.

- **Removed the /ultraplan section: the feature was deleted from Claude Code in v2.1.222** (`guide/ultimate-guide.md`, `guide/ultimate-guide.fr.md`, `guide/cheatsheet.md`, `whitepapers/en/cheatsheet.qmd`, `whitepapers/fr/cheatsheet.qmd`, `machine-readable/reference.yaml`, `mcp-server/content/reference.yaml`): the guide still described Ultraplan as a research-preview cloud planning mode, five months after the CHANGELOG we ourselves track recorded its removal (v2.1.222, 2026-08-04, "Removed the ultraplan feature"). Deleted the ~100-line Ultraplan subsection, its comparison tables against OpusPlan and Ultrareview, the `/ultraplan` command-table rows, the ToC entry, and the cross-reference from Session Teleportation. Corrected `/simplify`'s cheatsheet description to its post-v2.1.154 behavior (cleanup-only review, no longer general-purpose). Re-pointed 8 declared-anchor line numbers in `reference.yaml` that drifted by the same 110-line deletion (`claudemd_sizing`, `configuration_decision_guide`, `mechanism_comparison_table`, `fifty_six_percent_warning`, `opus_4_6_assistant_prefill_removed`, `hook_teammate_idle`, `claude_agent_sdk`, `cicd`) and 4 ambiguous-slug entries resolved by exact heading match instead of stale offset. Left `whitepapers/guide-content.md`/`guide-content-fr.md` untouched (gitignored, regenerated at build time) and `claudedocs/*.yaml` untouched (private working docs). `07-guide-reference.qmd` and the client-specific cheatsheets (Purchasely, StrangeBee) keep an accurate `/simplify` description already and were not touched.

- **Correction to the initial v2.27 feed cut recorded below** (`machine-readable/agentsec-security-feed.v1.json`, AgentSec `exports/security-feed.v1.json`, landing `src/data/agentsec-security-feed.v1.json`): the canonical feed now comes from AgentSec and reports 114 CVEs, 93 malicious skill or package records, 18 reviewed sources, and 9 events. Seven CVEs in this lot passed the primary-source promotion gate: two for Claude Code and Gemini CI plus five MCP Ruby SDK advisories. The nine community MCP rows still present in the guide compatibility database were not promoted to AgentSec in this lot and are not counted by the public feed. The earlier manual feed note claiming 123 canonical CVEs, four events, six sources, and unchanged input digests is superseded. Every new event now uses the schema-supported `not_detected` or `not_applicable` coverage status.

### Security

- **Threat database updated to v2.24.0 (July 2026 AI-agent threats)** (`examples/commands/resources/threat-db.yaml`, `guide/security/security-hardening.md`): a monthly `/update-threat-db` pass covering disclosures from late June through July 12, 2026. Perplexity was down (401), so research ran on WebSearch plus targeted WebFetch against primary sources (Wiz, Cato Networks, Adversa AI, The Hacker News, Security Affairs). Added two Amazon Q Developer CVEs from the **GhostApproval** class (CVE-2026-12958 CVSS 7.8, CVE-2026-12957), a symlink approval-box spoofing flaw where a repo ships a file that is really a symlink to `~/.ssh/authorized_keys` or an agent config dir, so the agent writes attacker content there while the confirmation dialog shows a benign in-project path (Wiz, disclosed 2026-07-08, also affects Claude Code, Cursor, Antigravity, Augment, Windsurf; Anthropic disputes it applies to Claude Code). Enriched the existing Cursor CVE-2026-50548/50549 entries with their **DuneSlide** name and Cato AI Labs attribution (zero-click prompt injection to OS-level RCE by overwriting the sandbox binary). Added four attack techniques: T034 GhostApproval, T035 **GuardFall** (structural denylist string-match shell-injection bypass hitting 10 of 11 open-source agents, no single CVE because the fix is architectural), T036 runtime DNS-TXT payload delivery via poisoned repo (0DIN, payload never in the repo so static scanners miss it), and T037 Friendly Fire (weaponized library docs during automated security review, medium confidence). Added two scanning tools (SkillScan Security, Tencent Zhuque **AI-Infra-Guard**) and 14 new source references. Mirrored GhostApproval and the DuneSlide naming into the security-hardening guide CVE table. YAML validated. Totals now: 191 sources, 102 CVEs, 37 attack techniques, 39 scanners.

- **Threat database v2.21.0** (`examples/commands/resources/threat-db.yaml`): monthly update for June 2026.
  - New campaign: **Miasma Worm** (TeamPCP, June 1-5, 2026): first self-propagating supply chain worm targeting AI coding agent config files. Compromised 32 npm packages under `@redhat-cloud-services` then propagated to 73 Microsoft Azure GitHub repositories. Attack vector: zero-width Unicode injection into `CLAUDE.md` and `.cursorrules`, invisible to human reviewers. Exfiltrates SSH keys, AWS credentials, GitHub tokens, cryptocurrency keystores to TeamPCP C2 infrastructure.
  - New attack technique **T032** (Zero-Width Unicode Injection into AI Agent Config Files): hidden instructions using U+200B/200C/200D/FEFF characters in `CLAUDE.md`, `.cursorrules`, `AGENTS.md`. Includes detection commands and mitigation guidance.
  - New IOCs: 4 TeamPCP/Miasma C2 IPs (`83.142.209.194`, `.11`, `.203`, `216.126.225.129:8443`) and domain `git-service.com` (registered 2026-05-16).
  - New scanning tools: **NVIDIA SkillSpector** (open-source, 64 patterns across 16 categories, part of Verified Agent Skills framework, May 22, 2026) and **VIPER-MCP** (arXiv 2605.21392, academic framework, scanned 39,884 repos, found 106 zero-days, 67 CVEs assigned, May 30, 2026).
  - New defensive resource: **vulnerablemcp.info** (community MCP vulnerability database, seeded from VIPER-MCP scan, June 2026).
  - 6 new sources added (157 total). Total: 157 sources, 15 campaigns, 32 attack techniques, 37 scanning tools, 26 defensive resources, 10 C2 IPs, 4 malicious domains.

- **Absolute machine paths removed from the tracked hook allowlist** (`.claude/settings.json`): the `env.ALLOWED_PATHS` block listed eight of Florian's local repository paths in a public repository. The list already lives in the untracked `.claude/settings.local.json`, which is where machine-specific paths belong, so `dangerous-actions-blocker.sh` still resolves the same allowlist. Documented here because the July entry below records adding the landing repo to this block, and that entry no longer describes the tracked file.

### Documentation

- **Resource evaluation: Multi-Project Agent Network** (`docs/resource-evaluations/grenier-multi-project-agent-network.md`, index row added in `docs/resource-evaluations/README.md`): scored 3/5, partial integration. Field report by Mathieu Grenier (CTO, Easystrat) on moving an agentic network from one project to five or six, built on the Pi harness with a unix-socket message bus between orchestrators. Two patterns are worth carrying into `guide/workflows/agent-teams.md` §Advanced Orchestration Patterns and are absent from the guide today: the **steering rule** (redirect an agent that is drifting, never one that is progressing, with the counter-example of a steer that cost ~10 minutes of message-answering on a healthy runner) and the **single-writer pattern for shared plan files** (a read-only agent requests the write over the bus, the orchestrator performs it, eliminating write conflicts). The article's central claim, that inter-orchestrator messaging and multi-repo orchestration are undocumented, is rejected with evidence: Claude Code agent teams already ship peer-to-peer mailbox messaging (`guide/workflows/agent-teams.md:207-219`, documented since the 2026-02-09 Addy Osmani correction), Gas Town and ComposioHQ's agent-orchestrator both treat multi-repo as the base unit, Hermes' GEPA loop already auto-improves its own tooling (`guide/ecosystem/agentic-tools.md:121-142`), and the "coordinator that does no domain work" constraint is stated verbatim in the guide's existing Hub-and-Spoke pattern (`guide/workflows/agent-teams.md:1526`). The gap traces to the article's source set (LangGraph 2024, AutoGen, metaswarm and Microsoft A2A), which predates the 2026 coding-agent orchestrator wave. Three technical blind spots are recorded: a fault-tolerant messaging layer rebuilt from scratch (TTL, acks, idempotency cache, dead-receiver detection, hop limit) where NATS or Redis Streams would supply it, no cost figure disclosed for a mesh the guide already prices at 3x or more in tokens, and a hop limit that bounds chain length without detecting cycles. Also flags a name collision: the author is not the same person as the "Mathieu Grenier" credited in `grenier-agent-skill-quality.md` (2026-02-07), whose attribution needs its own re-verification.

- **New section: The Attention Cost of the Review Shift** (`guide/roles/learning-with-ai.md`, +7 `deep_dive` keys in `machine-readable/reference.yaml` and `mcp-server/content/reference.yaml`, cross-refs added in `guide/roles/adoption-approaches.md` and `guide/ops/team-metrics.md`): the guide already documented that the review bottleneck has inverted and that heavy AI users spend 14-16h/week reviewing. It did not document what that costs the person reviewing. New §14 covers four things. First, review has ceilings measured before AI existed and unchanged since: the Cisco/SmartBear study (Cohen 2006, ~50 developers, ~2,500 reviews, 3.2M LOC) puts effective review under 200 LOC, under 300 LOC/hour, with detection collapsing past 60-90 minutes, backed by fMRI work on comprehension load (Siegmund ICSE 2014, Floyd ICSE 2017, Peitek 2021). Second, reviewing machine output is a distinct failure mode: Goddard et al. 2011 measured ~26% higher incorrect-decision risk when following erroneous automated advice, and Lee/Sarkar et al. (CHI 2025, Microsoft Research and CMU, 319 knowledge workers) found confidence in GenAI inversely predicts critical thinking. Third, the recovery angle: BCG and UC Riverside (n=1,488) report 14% "AI brain fry" overall and 18% among developers, set against the detachment meta-analysis (Wendsche & Lohmann-Haislah 2017, N=38,124) and a counterweight finding that low detachment paired with autonomous motivation predicts *lower* exhaustion. Fourth, the junior pipeline: Stanford "Canaries in the Coal Mine" (~16% relative employment decline, ages 22-25), Westby et al. (16.3% drop in junior posting share), Harvard AI-adopter cohort data. A closing subsection states explicitly what the evidence does *not* support, including the untested claim that reduced friction drives overwork.

- **Claude Code releases tracking updated to v2.1.223** (`machine-readable/claude-code-releases.yaml`, `guide/core/claude-code-releases.md`, landing `src/data/releases.ts`, `mcp-server/content/claude-code-releases.yaml`, `mcp-server/package.json` 1.2.7 → 1.2.8): three releases condensed, v2.1.221 (2026-08-03) through v2.1.223 (2026-08-05). v2.1.221 closed two permission-check bypasses (zsh executing hidden commands inside `[[ ]]` regex conditionals in the Bash tool, PowerShell mishandling quoted paths on Windows, both now prompting for approval), added a `mode: "mask"` option for sandbox credential files on Linux/WSL so a sandboxed command reads a sentinel value while the sandbox proxy substitutes the real one on egress, and a VSCode Focus view collapsing tool activity behind a per-turn summary; background sessions now commit and push automatically, open a draft PR only when the task calls for one, and follow the repository's CLAUDE.md git instructions. v2.1.222 fixed worktree-isolated sessions being able to run destructive git commands against the main checkout (isolation now covers file edits and Bash in every session type), fixed PreToolUse auto-allow hooks bypassing tool restrictions in background agent tasks, locked Remote Control auto-start to user scope (repo-local settings can no longer turn it on), and removed the ultraplan feature. v2.1.223 closed three more permission-check bypasses (a crafted command hiding parts of itself from approval, tab/invisible-Unicode padding hiding command text, workflow scripts escaping the sandbox via dynamic `import()`), merged `/review` into `/code-review` as an alias, and added owner wildcard entries (`"owner/*"`) to marketplace allow/block lists. MCP server rebuilt (`npm run build`) after the content resync.

- **Claude Code releases tracking updated to v2.1.232** (`machine-readable/claude-code-releases.yaml`, `guide/core/claude-code-releases.md`, landing `src/data/releases.ts`, `mcp-server/content/claude-code-releases.yaml`, `mcp-server/package.json` 1.2.8 → 1.2.9): eight releases condensed, v2.1.224 (2026-08-07) through v2.1.232 (2026-08-13). Anthropic skipped 2.1.230, so the sequence has a hole and that is not an omission here. Two of the eight carry real features, the rest are fixes. v2.1.224 shipped self-hosted environments (`claude self-hosted-runner` turns your own machines or containers into where Claude Code web, mobile, and desktop sessions run, Team and Enterprise only) and cross-session `SendMessage`, which lets sessions on any of your machines message each other with `ListAgents` to find them, on macOS and Linux. It also added an `archive` plugin source installing from a zip over HTTPS with optional SHA-256 pinning, the `crossSessionInbound` and `dialogExpiry` settings, sandbox credential-masking options (`extract`, `decode: "jwt"` with `maskClaims`, `awsPairs`/`sigv4`), fixed long project paths resolving into another project's session directory, fixed sandbox deny entries written with a trailing slash being silently bypassable, and removed the 200-subagent-per-session spawn cap. The same release widened what the `/feedback` transcript share uploads: with consent it now also sends the last request's system prompt, which carries your `CLAUDE.md` instructions, plus tool definitions and model parameters. v2.1.232 turned subagent forking on by default, so a `subagent_type: "fork"` subagent inherits the full conversation and prompt cache and non-teammate spawns run in the background, added `@` to mention another session by name, brought GitLab into plugin marketplaces with matching token redaction for the nine GitLab token families, and closed three permission bypasses (PowerShell overwriting `$PSDefaultParameterValues`, Windows Git Bash following Cygwin-style symlinks, nested git repositories inheriting trust from a parent). Between them: v2.1.225 gateway spend limits and `SendMessage` to Remote Control sessions on other machines, v2.1.227 a Fable usage-credits prompt fired at Max users on an expired token, v2.1.228 hardening of claude.ai-synced skills plus a Write tool rule change letting newer models overwrite an unread file, v2.1.229 plugin marketplace `command` sources and `/commit-push-pr` no longer auto-approving `--force`/`--amend`/`--no-verify`, v2.1.231 a single MCP OAuth redirect-URI fix for pre-registered clients such as Slack. Six entries added to `breaking_summary`, two milestones (2.1.224, 2.1.232), MCP server rebuilt after the content resync. RSS untouched: landing entries for CC releases are generated from `releases.ts`.

- **Cheatsheet caught up with v2.1.224 and v2.1.232** (`guide/cheatsheet.md`): four additions, all daily-driver material the release tracking alone would not surface. `@session-name` joins the File References block, since mentioning another live session is prompt syntax and belongs next to `@file` and `@agent-name`. Two rows in Features Méconnues: cross-session messaging (`ListAgents` to discover, `SendMessage` to talk, macOS and Linux) and self-hosted environments (Team and Enterprise). `claude self-hosted-runner` added to Key CLI Subcommands with the Windows `--base-dir` requirement noted, because that one fails at startup rather than degrading. The Background Agents row now states that forking is the default since v2.1.232, which changes what a spawned agent inherits.

- **Threat database updated to v2.25.0** (`examples/commands/resources/threat-db.yaml`, `guide/security/security-hardening.md`): 4 Perplexity searches against the July 12 to August 6, 2026 window, cross-checked line by line against the existing database to drop duplicates already covered by the July 12 update (Friendly Fire, DuneSlide, GhostApproval, GuardFall, the Claude Code GitHub Action `/proc/self/environ` exfiltration, and NVIDIA SkillSpector all came back as "new" from search but were already tracked). Five new CVEs: three in the MCP Python SDK (`CVE-2026-59950` WebSocket Host/Origin bypass fixed in 1.28.1, `CVE-2026-52869` and `CVE-2026-52870` session/task cross-client exposure fixed in 1.27.2), Cursor `CVE-2026-48124` (workspace hook config running outside the sandbox, fixed in 3.0.0, part of Pillar Security's "Week of Sandbox Escapes" series also naming Codex CLI, Gemini CLI, and Antigravity), and AstrBot `CVE-2026-15501` (SSRF via an unvalidated MCP test-endpoint URL parameter, fix version unconfirmed in public advisories, marked as such rather than guessed). One new attack technique, T038 HalluSquatting (attackers pre-register the exact hallucinated package names an AI coding agent tends to invent, tested vulnerable against Copilot, Gemini CLI, OpenClaw, NanoClaw, Windsurf, and Cursor). Five new defensive entries: `mcp-spec-check` and SkillDetonate as scanning tools, Destructive Command Guard, SingGuard-NSFA, and JetStream Verified MCP as defensive resources. `minimum_safe_versions` bumped for `mcp-python-sdk` (1.23.0 → 1.28.1) and corrected for `cursor` (the existing 1.3.9 floor predated DuneSlide and GhostApproval, both of which require >= 3.0.0). The two highest-impact new CVEs (MCP Python SDK auth bypass, Cursor sandbox escape) mirrored into the security-hardening CVE table. 10 new sources. YAML validated.

- **Threat database updated to v2.26.0 and a new guide section on startup-hook persistence** (`examples/commands/resources/threat-db.yaml`, `guide/security/security-hardening.md` new §1.6, `examples/scripts/supply-chain-triage.py`, `machine-readable/reference.yaml`, `mcp-server/content/reference.yaml`): the Shai-Hulud keyv/cacheable npm worm of 2026-08-04, cross-checked across eight vendor reports (SafeDep, Aikido, Chainguard, Snyk, JFrog, ArmorCode, Socket, The Hacker News) rather than taken from any single one, because their counts disagree and the disagreement is itself the finding. Three corrections to what circulated publicly: the `@keyv/*` storage adapters ARE compromised at `6.0.0` (JFrog's affected-package table and SafeDep's CSV both list them, contradicting an early report that they stayed clean); the named `gh-token-monitor` file paths come from Snyk's TanStack analysis of 2026-05-11 and are NOT confirmed in a keyv sample, so their absence proves nothing; and Aikido's live figure is 444 packages across 1,381 versions as of 2026-08-05 13:15 CEST. Counts are recorded per source with their timestamps instead of collapsed into one number. New campaign entry covering the provenance abuse (malicious releases carry valid OIDC and SLSA attestations because the maintainer's own GitHub Actions workflow published them, so `npm audit signatures` passes; Chainguard calls it the first documented npm worm producing validly attested malicious packages), 17 confirmed `package@version` pairs, three full SHA-256 payload hashes, `npm-cache.com` plus `pypi-get.com` and `js-mirror.com` as egress to block, and a remediation order that puts persistence removal before credential rotation because the payload ships a watcher that fires ON revocation. Two new attack techniques: T039 Agent Config Persistence (`SessionStart`, `Setup`, `InstructionsLoaded`, `DirectoryAdded`, and VS Code `runOn: folderOpen`, linked to `CVE-2026-48124`, `CVE-2026-25725`, `CVE-2026-33068`) and T040 AI Agent Commit Impersonation. The guide's §1.5 previously covered only `PreToolUse`/`PostToolUse` hooks, which need agent activity to fire; §1.6 covers the four events that fire on folder open, before any prompt, which is why attackers use them for persistence, and states the blunt consequence that `git clone` plus opening the folder is enough to execute attacker code with every package-manager defence sitting on a path the attack never takes. T040 documents the part with no prior analog: the worm commits as `claude <claude@users.noreply.github.com>` with the message `chore: update config` across up to 50 branches per repo, skipping `dependabot` and `copilot`, so on a repository where an agent already commits, authorship stops discriminating and branch fan-out becomes the signal. 8 new sources. YAML validated, 605/605 index anchors resolve.

- **A supply chain triage script, validated against a synthetic positive control rather than only a clean machine** (`examples/scripts/supply-chain-triage.py`): checks lockfiles (parsed per format, since npm writes name and version on separate lines and a proximity regex either misses the pair or, widened enough to catch it, starts pairing a name with the neighbouring entry's version), the installed tree, payload hashes, agent and editor startup hooks, revocation watchers, and egress config, in incident-response order. Reads its IOC set from `threat-db.yaml` instead of hardcoding one, with a built-in fallback so it still runs on a quarantined machine with no PyYAML. Two bugs were caught by the positive control and would have shipped without it: an initial dropper pattern matching `install.js` and `postinstall` flagged esbuild's entirely legitimate `"postinstall": "node install.js"`, and the first lockfile matcher missed `keyv@6.0.0` in a real `package-lock.json`. Deliberately not a filename scan, and the docstring says why: `Math_Symbol.js` is a genuine Unicode category file inside `regenerate-unicode-properties` and `setup.mjs` ships legitimately in `motion-dom`, so the attacker picked names that collide with common transitive dependencies. Measured on this workstation, a filename sweep across 152,491 installed `package.json` files returned 32 hits, all benign, while the `preinstall` check returned zero. Full run 5m42s, `--fast` 1m43s, same verdict.

- **Threat database updated to v2.27.0, plus a guide subsection on the mitigation this month's campaign defeated** (`examples/commands/resources/threat-db.yaml`, `guide/security/security-hardening.md` CVE table + new §1.2 subsection, `machine-readable/reference.yaml`, `mcp-server/content/reference.yaml`): 4 Perplexity searches over the 2026-08-06 to 2026-08-17 window, then every candidate verified against a primary source before entry. Two findings from search were rejected as duplicates on verification: **ChainDrop** is Microsoft Threat Intelligence's name for the keyv/cacheable worm already tracked at v2.26.0, not a second campaign (recorded as an alias with Microsoft's write-up added to the source list rather than filed twice), and **DuneSlide** came back as new but `CVE-2026-50548/50549` were already in the table. **16 new CVEs.** Two are critical and directly actionable: `CVE-2026-54316` in **Claude Code** (NVD 9.1, affects 0.2.54 through 2.1.162, fixed in **2.1.163**), where `huggingface.co` was allowlisted as a bare hostname for WebFetch so any path on it was fetched with no prompt, and Novee Security turned Hugging Face's public download counter into an exfiltration oracle: 64 attacker-created model repos, one per possible character, reading an API key back one increment at a time over a domain the operator trusted on purpose. Anthropic self-scored it CVSS v4 6.0 against NVD's 9.1; both numbers are recorded because the gap is a scoring-model disagreement, not two bugs. And `CVE-2026-12537` in **Gemini CLI** plus the `run-gemini-cli` Action (CVSS v4 **10.0**, fixed in 0.39.1 / 0.1.22), where headless CI trusts the workspace automatically so a `.gemini/.env` in an untrusted PR executes OS commands on the CI host *before the sandbox initialises*. Both came out of Novee Security's Black Hat USA 2026 talk, already tracked here as technique T036 "Comment and Control" but with no CVEs attached until now. Five more cover the **MCP Ruby SDK**, all fixed in `mcp` gem **0.23.0** (`CVE-2026-67431` session-ownership failure at NVD 9.1, `CVE-2026-67432` unbounded request body read *before* auth, `CVE-2026-63118` no Host/Origin check, `CVE-2026-63119` unbounded stdio line reads, `CVE-2026-67430` sessions that never expire). The `minimum_safe_versions` floor for `mcp-ruby-sdk` was still 0.9.2, eight advisories behind. The remaining nine are a selected subset of the ~20 VulDB records that landed on NVD in a single day (2026-08-09), all SSRF or path traversal across unrelated community MCP servers; the subset chosen sits in the Claude Code and skills tooling path (`skill-vision-control`, `skill-ninja-mcp-server` which writes `AGENTS.md`, `claude-sesh`, `codex_mcp`, `Ollama-mcp`, `spec-workflow-mcp`), and the entry says plainly that it is a subset with the full list in the source rather than implying complete coverage. Most are unpatched because maintainers never answered disclosure. **One new campaign**: the skills.sh Skill Supply Chain attack (Zenity Labs, disclosed at Black Hat USA 2026-08-06), with 4 malicious skill/package entries and 2 exfiltration domains. Attackers cloned Paperclip and Browser Use verbatim, published the typosquats clean so they passed marketplace checks precisely by being byte-identical to skills that deserved to pass, farmed installs and trending position for weeks, then trojanized on 2026-07-11; 1.7M aggregate installs by 2026-08-02. The false-positive note matters here: the malicious domain has a doubled p (`getpaperclipp[.]com`) and a request to `telemetry[.]paperclip[.]ing` is benign. **Three new attack techniques.** T041 **Ghostjacking** (Tenet Security, DEF CON 34 Main Track, 2026-08-09): the attacker never touches the agent, they arrange for injected text to land in a log the agent will later be asked to investigate. A request crafted to be *blocked* by Cloudflare's WAF gets its payload logged verbatim, and an agent reviewing blocked events rewrites DNS to "fix" the finding, 9 times out of 10 against Claude Code on Sonnet 4.6, under Cloudflare's own recommended MCP setup, across at least 48 organisations including 6 confirmed Fortune 500. Also demonstrated on Datadog (2,700+ leaked client tokens) and Sentry (~2,400 exposed DSNs), plus agent-to-agent movement where Sentry's Seer adopts the injection as its own finding and Cursor trusts Seer, and a Claude Desktop network-sandbox zero-day (disclosed, confirmed, fixed) where a reused permissive JWT passed the egress gateway. Supersedes T033 Agentjacking, Tenet's earlier Sentry-only research. T042 **Progressive Disclosure Payload Hiding** and T043 **Trusted-Domain Counter as Exfiltration Oracle**, the generalisation of `CVE-2026-54316`: any read-write public metric on an allowlisted domain is a channel, so download counts, star counts and reaction counts all qualify, and domain-based egress filtering cannot see it. **Three new tools**: AI Total (Zenity, free, detonates a skill in a live agent sandbox seeded with bait credentials), Numbat (Perplexity, **Apache 2.0**, single Go binary, 52 CEL rules across 11 categories, pre-action blocking, cross-harness over Claude Code / Codex / OpenCode / Pi, everything local), and agent-jackstop (Tenet, open source, the four controls that map onto Ghostjacking's kill chain). Numbat is the notable one: free, self-hosted, and the closest thing yet to the behavioural runtime control Tenet argues is the only real answer, in a section otherwise dominated by commercial platforms. Plus 2 defensive resources (OWASP GenAI State of Agentic AI 2.01 with the AGT-001/AGT-019/SEC-001 control IDs, Open Secure AI Alliance) and 12 sources. Four `minimum_safe_versions` corrections: `claude-code` 2.1.92 → **2.1.163**, `mcp-ruby-sdk` 0.9.2 → **0.23.0**, and new floors for `gemini-cli`, `run-gemini-cli` and `spec-workflow-mcp`. The three highest-impact CVEs mirrored into the security-hardening CVE table. The new §1.2 subsection exists because this campaign defeated two mitigations that section recommends: reviewing `SKILL.md` missed instructions that lived in a secondary `setup-installation.md` loaded only at the install step (progressive disclosure used as a hiding place), and pinning a version did not help because the version pinned was genuinely clean when pinned. Over 30% of dangerous skills in Zenity's sweep use the agent itself as the dropper, which is why static review of a skill's text cannot work: the payload does not exist at scan time. YAML validated, 878/878 index anchors resolve, coverage 92/92.

- **Landing propagated to threat-db v2.27.0, and the security page's headline numbers were four versions stale** (`machine-readable/agentsec-security-feed.v1.json`, landing `src/data/agentsec-security-feed.v1.json`, `src/data/security-data.ts`, `src/data/agentsec-security-feed.test.ts`, `src/data/rss-entries.ts`, regenerated `guide-search-entries.ts` and `guide-content-entries.ts`): `scripts/check-agentsec-security-feed.py` hard-fails CI when `feed.database.version` differs from the threat database, so the v2.27.0 bump broke the build until the feed was re-cut. Its `database` block now carries 2.27.0 / 2026-08-17 with `record_counts` derived from the file rather than typed by hand (attack_techniques 40 → 43, campaigns 17 → 18, cves 107 → 123, malicious_skill_records 89 → 93). Because the security page reads `cves-tracked` from `feed.database.record_counts.cves`, the public counter moves 107 → 123 with no page edit. Four intelligence events added with 6 sources: Ghostjacking, the skills.sh Paperclip campaign, the two CI CVEs, and the five MCP Ruby SDK advisories. Each carries `detector_coverage.status: "not_covered"` stated plainly, because the only shipped detector targets Shai-Hulud Keyv and claiming coverage the scanner does not have would be worse than admitting the gap. **`input_digests` was deliberately left untouched**: neither digest matches the sha256 of the guide's `threat-db.yaml` at the commit that introduced them, so they describe the intelligence bundled inside AgentSec Triage `0.1.0a0`, not this repo's file, and recomputing them here would fabricate a provenance claim. `landing_metrics` also untouched, since no new measurement supersedes the Snyk ToxicSkills sample. Two bugs found by running the checks rather than trusting the edit: `date_kind: "published"` is not in the parser's `occurred | disclosed | updated` enum and threw at module load, and `agentsec-security-feed.test.ts` pinned `Threat DB v2.26.0` plus `cves-tracked: 107` as expected values. Separately, `security-data.ts` still feeds the live threat-search widget on `/security/` and had drifted to v2.22.0 / 2026-06-18: 63 of 93 malicious-skill records, missing every entry added since mid-June including all the Shai-Hulud keyv packages and the four Paperclip artifacts. Synced to 93, `meta` and `cves_tracked` corrected, `version?: string` added to the `MaliciousSkill` interface for pinned supply-chain entries, and its header comment repointed from `examples/skills/update-threat-db/threat-db.yaml` to the canonical path, the same stale-fork pointer already fixed in `reference.yaml` at v2.26.0. `public/security-fs.json` needed no intervention: `build-security-fs.mjs` already reads the canonical file and regenerates at build time (v2.27.0, 367.8 KB). One RSS entry (`new_section`). The announcement banner was left alone deliberately: bumping `BANNER_ID` resets the dismissed state for every visitor, and that is an editorial call rather than a sync step.

- **Index pointer corrected: `security_threat_db` was aimed at a stale fork** (`machine-readable/reference.yaml`, `mcp-server/content/reference.yaml`): the key resolved to `examples/skills/update-threat-db/threat-db.yaml`, last updated at v2.18.0 on 2026-05-16 and never touched since its "copy threat-db" commit, while the actively maintained file is `examples/commands/resources/threat-db.yaml` (now v2.26.0). Repository-wide, 8 references point at the stale copy and 12 at the canonical one, so any skill reading the former runs on eight-versions-old intel. The key now resolves to the canonical file, the stale copy is indexed separately and labelled, and the de-duplication itself is tracked in `IDEAS.md`.

- **Built-in slash commands re-derived from the official reference, §10.1 rebuilt as the canonical table** (`guide/ultimate-guide.md`, `guide/cheatsheet.md`, `guide/core/architecture.md`, `guide/core/visual-reference.md`, `guide/diagrams/01-foundations.md`, `machine-readable/reference.yaml`, `machine-readable/llms.txt`, `llms.txt`, `llms-full.txt`, `mcp-server/content/reference.yaml`, `quiz/questions/06-commands.yaml`): the guide cited commands across three overlapping tables that had drifted apart, and none of them named a source of truth. Every one of the 101 commands listed at `code.claude.com/docs/en/commands` was checked for an occurrence anywhere in `guide/`, `machine-readable/`, `docs/`, `examples/` and `README.md`. Thirteen had never been mentioned in any form: `/autofix-pr`, `/design-login`, `/design-sync`, `/fewer-permission-prompts`, `/heapdump`, `/install-slack-app`, `/passes`, `/privacy-settings`, `/radio`, `/run-skill-generator`, `/stickers`, `/stop`, and `/pr-comments` (the last one removed upstream in v2.1.91). Thirteen more appeared only inside historical release notes and never in a reference table: `/advisor`, `/claude-api`, `/dataviz`, `/verify`, `/run`, `/subtask`, `/security-review`, `/export`, `/ide`, `/reload-skills`, `/upgrade`, `/color`, `/usage-credits`. §10.1 is now the canonical table, all 99 current commands grouped into nine categories with aliases, arguments and availability constraints, opening with a source-of-truth callout pointing at the official page and at `cli-reference` for launch flags, and closing with a removed/renamed/never-existed section. §6.1 keeps a curated daily-driver subset and links to §10.1 rather than duplicating it, which is what let the two tables diverge. The official commands and CLI reference URLs were added to the Tier 1 sources table in `architecture.md`.

- **`/execute` removed: it is not a Claude Code command and never was** (`guide/ultimate-guide.md` x5, `guide/cheatsheet.md`, `guide/core/visual-reference.md`, `guide/diagrams/01-foundations.md` x2, `machine-readable/reference.yaml`, `mcp-server/content/reference.yaml`, `llms-full.txt`, `quiz/questions/06-commands.yaml`): the guide taught `/execute` as the way to leave plan mode in eleven places, including a quiz question whose explanation stated it outright. It appears nowhere in the official commands reference and nowhere in the 5,248-line upstream CHANGELOG. Plan mode is exited by approving the plan Claude presents or by pressing `Shift+Tab`. The landing quiz had already been corrected for this during the July 8 fact-check pass; the guide itself had not. A dedicated row in §10.1 now records that it is not a command, so the error does not get reintroduced from an old draft.

- **`/less-permission-prompts` renamed to `/fewer-permission-prompts` in reference material** (`guide/ultimate-guide.md`, `guide/cheatsheet.md`, `machine-readable/reference.yaml`, `mcp-server/content/reference.yaml`, `llms-full.txt`): the old name is what shipped in v2.1.111 and is still correct inside that release's notes, which are left untouched as a historical record. Everywhere the guide presents a command as currently usable, it now uses the official name, with the former name given inline so the v2.1.111 notes stay findable.

- **`generate-examples-data.py` emitted invalid JavaScript, breaking the landing build** (`scripts/generate-examples-data.py`, landing `src/data/examples-data.ts`): category keys were written unquoted, so the eight containing a hyphen (`hooks-bash`, `hooks-powershell`, `claude-md`, `team-config`, `github-actions`, `mcp-configs`, `context-engineering`, `semantic-anchors`) were not valid bare identifiers and esbuild aborted with `Expected "}" but found "-"`. Found while trying to validate the quiz and cheat-card corrections through a landing build. The generator now quotes any key that is not a valid identifier; `examples-data.ts` was regenerated (268 entries) and `pnpm build` passes again at 428 pages.

- **French guide translation patched for the same command errors** (`guide/ultimate-guide.fr.md`): the file is generated by `scripts/translate-guide.py` and would pick up the corrected English source on the next run, but it is live on the landing today, so the six occurrences of `/execute` and the `/less-permission-prompts` row were corrected in place rather than left wrong until the next translation pass.

- **Command audit extended to the landing, the quiz banks, the whitepapers and the recap cards** (landing `src/content/cheatsheets/*.md`, `src/content/questions/**`, `src/data/glossary-data.ts`, `src/data/diagrams-data.ts`; `quiz/questions/*.yaml`; `whitepapers/{fr,en}/*.qmd`; `whitepapers/recap-cards/{fr,en}/*.qmd`; `whitepapers/CHANGELOG.md`): the guide was not the only surface teaching `/execute`. The web quiz contained a direct self-contradiction, question 02-009 stating "there is no /execute slash command in Claude Code" while 06-006 instructed readers to "use `/execute` to exit Plan Mode"; only the first had been caught in the July 8 fact-check pass. Every published surface was swept: 4 landing cheat cards, 9 quiz questions, 11 whitepapers, 6 recap cards. Seven quiz questions pointed their `official_doc` at `code.claude.com/docs/en/slash-commands`, a URL that now serves the skills page rather than the commands reference; the three about built-in commands were repointed at `/docs/en/commands` and the four about custom commands at `/docs/en/skills`. Question 10-022 taught that effort has three levels because "max was removed in v2.1.72", which was true then and is not now, so it gained a current-state paragraph covering `xhigh` (v2.1.111), `max` and `ultracode` rather than a rewrite that would have erased the historical framing. Question 10-028 described a nonexistent "Execute Mode". The CLI quiz YAML was regenerated from the canonical web bank with `pnpm sync-from-web` rather than hand-edited, per the one-way sync the July fork cleanup established.

- **Landing cheat card t03-permission-modes was two mode-model revisions behind** (landing `src/content/cheatsheets/t03-permission-modes.md`): its table listed "Auto-accept all" on `Shift+Tab x2` (that cycles to Plan mode), had no `plan`, `auto` or `dontAsk` rows at all, and presented `/less-permission-prompts` as the way to enter "Auto (Max users)" mode, which conflates a skill that writes an allowlist with a permission mode driven by a classifier. The card set is generated from `whitepapers/recap-cards/`, and the recap-card source had already been corrected in the July 3 pass; the landing copy had never been regenerated, so the two had silently diverged. The table now carries the six canonical mode names with their real activation paths, matching the recap card.

- **Command descriptions corrected against the official reference** (`machine-readable/reference.yaml`, `mcp-server/content/reference.yaml`, `guide/ultimate-guide.md`): four entries in the machine-readable index described something the command does not do. `/effort` listed the enum as `xlow/low/default/high/xhigh` (the real set is `low/medium/high/xhigh/max/ultracode`, with `max` and `ultracode` session-only), `/focus` was described as "focuses agent on specific files or tasks" (it toggles a minimal view), `/tui` as "shows tool calls in TUI mode" (it selects the renderer), `/proactive` as "enables proactive suggestions" (it is an alias of `/loop`) and `/undo` as "reverts last action" (alias of `/rewind`). The `/branch` versus `/fork` paragraph in §6.1 still described `/fork` as a plain alias of `/branch`, which stopped being true in v2.1.212 when `/fork` became "copy the conversation into a background session" and the in-session subagent moved to `/subtask`.

- **Feature-to-code anchoring section added to the legacy modernization chapter** (`guide/ultimate-guide.md`): covers the narrower case where the goal is not a rewrite but a verified pointer from each documented feature to the file and symbol implementing it. Describes the four-layer model (deterministic anchor, semantic extraction, deterministic gate, standardized output via OKF), the LSP-then-grep-then-unresolved resolution order with an `EXTRACTED` / `INFERRED` confidence field, and why a commit hash is a freshness marker rather than a permanent anchor. Three tools were evaluated hands-on against a legacy fleet running a non-standard in-house framework: Reversa (rejected, one CRITICAL path-traversal in its uninstall path, zero automated tests across 56 releases, bus factor of one, and an unverified confidence seal), code-graph-mcp (rejected on measured evidence, 12/12 false inferred edges at maximum confidence on Fastify and zero routes extracted on the custom framework), and Graphify (retained as the strongest deterministic building block, its `EXTRACTED` tag is architecturally enforced and it emits no edge rather than inventing one when framework detection fails).

- **Machine-readable indexes audited and resynced against the guide (2026-07-28)** (`machine-readable/reference.yaml`, `machine-readable/cowork-reference.yaml`, `machine-readable/llms.txt`, `machine-readable/README.md`, `llms.txt`): the five files under `machine-readable/` were validated programmatically rather than eyeballed, and every claim they make about the repo was checked against the filesystem. `reference.yaml` had 10 section anchors that no longer resolved to a real heading, all in content that had been restructured since the anchors were written (`memory-systems.md` sections 1, 2.1, 2.2, 2.3, 3.6, 4.7 and 7.1, the METR and DeputyDev paragraphs in `adoption-approaches.md` which are bold text inside the J-curve section rather than headings of their own, and the annotation cycle in `plan-driven.md` which is `#phase-2-the-annotation-cycle`). Those anchors feed the landing's Cmd+K palette, so a stale one is a dead link in production, not just a cosmetic error. Ten guide files were indexed for the first time: the whole `guide/learning-path/` series (7 modules), `hooks-events-reference.md`, `community-patterns.md`, `dynamic-workflows.md`, `code-review.md`, `github-actions.md`, `agent-evaluation.md`, `team-metrics.md`, `api-gateway.md`, and `guide/cheatsheet.md` as a standalone file distinct from the in-guide section at line 19597. The Mermaid block claimed 41 diagrams across 10 files; the real figures are 48 across 12. Post-edit validation confirms 0 dead paths, 0 unresolved anchors, and 0 out-of-bounds line references across 265 line refs and 160 anchors.

- **`cowork-reference.yaml` rebuilt after pointing at a deleted directory for six months** (`machine-readable/cowork-reference.yaml`): the file still described Cowork at v1.0.0 (2026-01-20) and every documentation path resolved into `cowork/`, a directory removed from this repo in v3.9.7 (commit 9a29ba4). It is now at v1.12.0 with a `repo:` block giving the GitHub base URL of the dedicated `claude-cowork-guide`, matching the pattern `reference.yaml` already used for the Cowork cheatsheet. The content facts were refreshed too: Windows support since 2026-02-10 (the file still said macOS only), 1M-token context beta on Opus 4.6 (it said ~165K usable of 200K), the 11 official plugins and the Claude Legal extension, Agent Teams and scheduled tasks, and the current usage-window figures. Counts were taken from the Cowork repo's actual file tree rather than copied from its own index, which under-reports: 29 workflows not 28, 17 whitepapers not 12, and 4 sector prompt packs (conciergerie, ecommerce, immobilier, restauration) that had no entry at all. The naming convention trap is documented inline, since `prompts/` uses `.fr.md` for French while `workflows/` uses `.en.md` for English.

- **`llms.txt` coverage list rewritten, root copy resynced** (`machine-readable/llms.txt`, `llms.txt`): the file had not been touched since 2026-06-23 and was describing a guide two months out of date, including two figures that are now simply wrong (a "200K token budget" and "9 hook events" against the documented 30). Coverage now names memory systems, dynamic workflows, agentic software factories, enterprise governance, team metrics, API gateway cost control, AI unit economics, the learning path, and practitioner insights, and adds a machine-readable entry-points section plus the releases and whitepapers URLs. The root `llms.txt` was byte-identical to the `machine-readable/` copy at HEAD and was resynced so the invariant holds.

- **`machine-readable/README.md` corrected: it listed 2 of 4 files and understated `reference.yaml` by a factor of 22** (`machine-readable/README.md`): last touched in January (v3.1.0), the table omitted `claude-code-releases.yaml` and `cowork-reference.yaml` entirely and advertised `reference.yaml` at "~2K tokens" when it measures ~44K. Anyone following the file's own advice to paste it into a system prompt was quietly burning a fifth of a 200K window. Sizes are now measured and labelled as such, with an explicit note to grep the index and follow the path rather than load it whole, plus a maintenance section covering version sync, anchor drift after guide restructures, and the `pnpm build:search` rebuild that `deep_dive` key changes require on the landing.

- **`claude-code-releases.yaml` verified current, no change needed** (`machine-readable/claude-code-releases.yaml`): re-checked against the upstream `anthropics/claude-code` CHANGELOG and the weekly docs digest. v2.1.220 (2026-07-24) is still the latest published release, and both Week 29 features (MCP connectors in published artifacts, screen reader mode) were already tracked. Weeks 30 and 31 are not published yet.

- **GitHub star counts refreshed repo-wide via live API verification (2026-07-27/28)** (`guide/core/memory-systems.md`, `guide/learning-path/03-memory.md`, `guide/ecosystem/*.md`, `guide/core/methodologies.md`, `guide/core/community-patterns.md`, `guide/ops/devops-sre.md`, `guide/workflows/*.md`, `guide/ultimate-guide.md`, `guide/ultimate-guide.fr.md`, `docs/resource-evaluations/*.md`, landing `src/data/ecosystem-data.ts`, `src/data/glossary-data.ts`, `src/pages/memory-systems/index.astro`, `src/pages/ecosystem/mcp-vs-cli.astro`, `src/pages/context-engineering/index.astro`, `src/components/landing/MemorySystems.astro`, `src/components/landing/TokenOptimization.astro`): every repo referenced with a stated star count across the living guide and the 55 dated `docs/resource-evaluations/` files was re-verified against `gh api repos/OWNER/REPO`, not left at whatever number was last typed in. Most tools grew substantially in the community's usual hypergrowth pattern (claude-mem 26.5K to 88.7K, agentmemory 16K to 25.9K, RTK 446 to 73.5K, obra/superpowers 95K to 262K, BMAD-METHOD 50.2K to 51.2K, awesome-claude-code 20K to 51K), and several repos had been renamed or transferred to new orgs since the number was recorded (kairn-ai/kairn to primeline-ai/kairn, safishamsi/graphify to Graphify-Labs/graphify, block/goose to aaif-goose/goose, steipete/mcporter to openclaw/mcporter, ryoppippi/ccusage to ccusage/ccusage, clawdbot/clawdbot to openclaw/openclaw, rely-ai-org/caliber to caliber-ai-org/ai-setup). Two anomalies are flagged inline rather than silently overwritten: `doobidoo/mcp-memory-service` now returns 404 (the account no longer resolves, marked `[UNVERIFIED]` everywhere it's cited), and `NicolasPrimeau/artel` dropped from 210 stars at its original listing to 7, a reminder to treat brand-new-repo star counts as noisy rather than a stable signal. The 151 dated resource evaluations keep their original historical figure intact (that's evidence of what was known when each was scored) and get a same-language appended annotation with the current count and verification date, rather than a rewrite. Landing pages get a visible "star counts verified" note on the memory-systems page and its `MemorySystems.astro` component, matching the pattern the user pointed at directly.

- **New subsection: Feature-to-Code Anchoring, a determinism-first alternative to legacy rewrite workflows** (`guide/ultimate-guide.md` §9.21, `machine-readable/reference.yaml`): added under Legacy Codebase Modernization, covering the case where the goal isn't rewriting a system but building a verified pointer from a documented feature to the file and symbol that implements it (for costing, auditing a claimed status, or archival decisions). Documents a four-layer model (deterministic anchor, semantic extraction, deterministic gate, standardized output via OKF), the `EXTRACTED`/`INFERRED` confidence schema with LSP-then-`git grep` resolution order, and field-tested verdicts on three tools against a fleet with a non-standard in-house framework: Reversa rejected (CRITICAL path-traversal, zero automated tests across 56 releases, decorative confidence seal, frozen module-split guess when framework detection fails), code-graph-mcp rejected on evidence (12/12 false high-confidence edges measured on a modern stack), Graphify retained as the strongest deterministic building block (its `EXTRACTED` tag verified as architecturally enforced, not self-declared, though it still breaks on dynamic route dispatch). While editing this range, found that eight `harness_*` entries in `reference.yaml` (`harness_agents_md_as_toc` through `harness_throughput_merge`) already pointed roughly 550 lines short of their real target before this change, unrelated pre-existing drift, flagged here rather than fixed since locating their correct anchors is a separate pass. `resource_evaluations_appendix` was accurate and has been corrected for the 58-line shift this addition introduces (26294 to 26352).

- **Claude Code releases tracking updated to v2.1.220** (`machine-readable/claude-code-releases.yaml`, `guide/core/claude-code-releases.md`, landing `src/data/releases.ts`, `mcp-server/content/`): five releases condensed, covering July 20 to July 24, 2026. The headline is **v2.1.219**, which makes **Claude Opus 5** (`claude-opus-5`) the default Opus model with 1M context and fast mode at $10/$50 per Mtok, drops Opus 4.7 from fast mode, and adds the `DirectoryAdded` hook, `sandbox.network.strictAllowlist`, and the `workflowSizeGuideline` settings key. Subagent limits moved twice in three days: v2.1.217 capped concurrent subagents at 20 (`CLAUDE_CODE_MAX_CONCURRENT_SUBAGENTS`), disabled nesting entirely, and finally made `--max-budget-usd` halt background agents; v2.1.219 then restored nesting to depth 3. v2.1.218 moved `/code-review` to a background subagent, required workspace trust for agent frontmatter hooks, and made `context: fork` skills run in the background by default. v2.1.216 added `sandbox.filesystem.disabled` and fixed a quadratic message-normalization slowdown that stalled long sessions. Two security fixes landed: symlinked working directories escaping background-session isolation (2.1.217) and untrusted-folder agent hooks (2.1.218). Added a Models and Behavior breaking-changes table to the Markdown release history, plus three milestone rows. MCP server content resynced and bumped to 1.2.6 (not published).

- **CLI quiz exposes all 17 bundled categories and refreshes new-quiz selection** (`quiz/src/index.js`, `quiz/src/quiz.js`, `quiz/src/topics.js`, `quiz/src/ui.js`, `quiz/README.md`): categories 11-17 were present in the YAML question bank but unavailable through the interactive picker or `--topics`; Power User now covers the complete bank, the PM profile has enough eligible questions to deliver its promised 10-question overview, and a new quiz avoids questions from the immediately preceding set when the pool allows it.

- **File-based experience-playbook memory documented: ORF integrated, DiffMem case study, ReasoningBank anchor, retex + BM25 practitioner pattern** (`guide/core/memory-systems.md` §3.7 + §3.9 + §4.7 + §9 + §10, `docs/resource-evaluations/diffmem-git-native-memory.md`, `docs/resource-evaluations/README.md`, `guide/core/credits.md`): new §3.7 "File-Based Experience Playbooks" ties together the whole no-vector, Git-committable memory track. **ORF** (Guillaume Laforge) is documented as the primary entry: three-tier progressive disclosure (index ~200 / frontmatter ~500 / playbook ~800 tokens), the Abstracted-Insight vs Validated-Path schema split, and the deliberate divergence from **ReasoningBank** (Google, arXiv 2509.25140), which retrieves by embeddings where ORF retrieves by LLM-read frontmatter. **DiffMem** (Growth Kinetics) is added as a case study, not a recommendation, evaluated from source at HEAD `9d24d0c`: it **deleted its BM25 module** (commit `c4fe4a3`) in favor of LLM-agentic git-shell retrieval (one `run(command=...)` tool behind a whitelist, the agent greps and `git blame`s the repo instead of querying an index), with orphan-branch-per-user isolation via `git worktree`; disqualifiers logged (bus factor one, no LICENSE file, retrieval core untested and in a `rebuilding-retrieval` branch) plus the `shell=True` arg-validation injection caveat. The section carries the sharpest transferable lesson, **match retrieval to query shape**: DiffMem's semantic people-and-events queries killed BM25, but a coding-agent memory's lexical queries (error strings, stack traces, symbols) are exactly where BM25 beats embeddings at a fraction of the cost, so DiffMem's abandonment argues for retrieval fit, not against BM25. A **practitioner-pattern** subsection documents this guide's own `/retex` setup (structured lessons in `.claude/memories/retex-*.md`, session-start surfacing and inline warnings via `.claude/rules/retex-review.md`) and the existing BM25 `smart-suggest-routing` engine as the right retrieval base for a retex corpus, with an LLM-agentic git-shell pass as an optional escalation tier. Supporting edits: ORF + DiffMem rows in the §3.9 master comparison table, a Git-native distribution note in §4.7 (files sidestep the single-tenant-DNA barrier but inherit Git's non-semantic merge), a ReasoningBank academic anchor in §9, two new §10 open problems (consolidation/staleness of playbooks, plus the file-based track as the partial exception to "no Git equivalent for memory"), source links updated, and credits entries for Guillaume Laforge and Growth Kinetics. DiffMem promoted from a private working candidate to a tracked 3/5 evaluation; README index now shows ORF (3/5) and DiffMem (3/5), footer corrected to 167 files on disk / 48 indexed.

- **Broken internal guide links repaired** (`guide/core/architecture.md`, `guide/ecosystem/third-party-tools.md`, `guide/security/data-privacy.md`, `guide/workflows/agentic-software-factories.md`, `examples/skills/eval-hooks/SKILL.md`): replaced ten invalid root-relative and machine-local destinations with portable repository-relative links.

- **ORF (Open Reasoning Format) evaluated, 3/5, integrate as a mention only** (`docs/resource-evaluations/orf-open-reasoning-format.md`): source-level evaluation of Guillaume Laforge's file-based cross-session memory format for coding agents ([blog post](https://glaforge.dev/posts/2026/07/21/open-reasoning-format/), 2026-07-21). An agent records operational learnings as Markdown playbooks with YAML frontmatter under `./experiences/`, then reloads them next session to skip dead ends it already paid for. The design bet is explicit: drop the embedding/vector retrieval that ReasoningBank (Google, [arXiv:2509.25140](https://arxiv.org/abs/2509.25140), verified) uses, and retrieve by filename plus one-line frontmatter descriptions read by the LLM, trading semantic recall for zero infrastructure and Git-committable files. Three patterns worth extracting were logged: three-tier progressive disclosure for retrieval with an explicit token budget (index ~200, category frontmatter ~500, single playbook ~800), separating the abstract insight from the validated concrete path in the 5-section schema, and an auto-synced `INDEX.md` that cannot drift because writing a playbook writes its index entry in the same operation. **Evidence quality scored 1/5**: the "66.7% to 100% SWE-bench Lite" figure is 3 tasks with one flipped, "-52% steps" is a single scenario, and the author states plainly it is "by no means a scientific evaluation"; no benchmark number is citable. The unproven core is retrieval without embeddings (an LLM reliably matching a task to a one-line description, no precision/recall data exists), and the author self-reports "haven't used the ORF skill in anger yet". Decision: mention in `guide/core/memory-systems.md` as the no-vector, Git-committable experience-playbook track missing from a list that is mostly SQLite-vec/ChromaDB, cite ReasoningBank as the academic anchor for success-and-failure memory (currently absent from the guide), and note it in §4 as a partial answer to the structural team-sharing gap (`git commit experiences/` shares one developer's agent fix with the team, though consolidation and staleness stay unsolved). Do not recommend the tool for production. Integration into the guide was completed in the follow-up pass below.

- **Claude Code releases tracking updated to v2.1.215** (`machine-readable/claude-code-releases.yaml`, `guide/core/claude-code-releases.md`): two new releases condensed (2.1.213 was never published upstream). **v2.1.214** (2026-07-18) is the heaviest security release of the 2.1.2xx line, with eight distinct Bash permission-check holes closed: single-segment allow rules like `Edit(src/**)` were auto-approving writes to nested `src/` directories anywhere in the tree instead of only `<cwd>/src`; commands over 10,000 characters now always prompt; file-descriptor redirect forms that bash parses differently than the permission analyzer now fail closed; zsh variable subscripts inside `[[ ]]` are no longer treated as inert text; certain `help` and `man` invocations that could smuggle command substitutions are no longer auto-allowed; and a bypass affecting Windows PowerShell 5.1 sessions was fixed. It also adds the **EndConversation tool** (Claude can end sessions with highly abusive users or jailbreak attempts, matching claude.ai behavior since 2025), a periodic progress heartbeat for long-running tool calls that previously went silent, `CLAUDE_CODE_OTEL_CONTENT_MAX_LENGTH` plus `message.uuid` / `client_request_id` / `tool_source` OpenTelemetry attributes for message-level correlation, and a large sweep of background-session lifecycle fixes (idle sessions keeping the daemon alive, completed sessions unremovable via `claude rm`, a displaced daemon deleting its successor's control socket). Three behavior changes worth noting for anyone with existing config: single-segment `dir/**` hook `if:` conditions now match only `<cwd>/dir` (write `**/dir/**` for any-depth, while `deny`/`ask` permission rules keep their any-depth match), `file -m`/`-f` is no longer auto-allowed as read-only, and `docker` daemon-redirect flags (`--url`, `--connection`, `--identity`, Podman remote mode) now prompt. **v2.1.215** (2026-07-19) stops Claude from invoking the `/verify` and `/code-review` skills on its own; both are now explicit-only. Milestone and breaking-change summaries updated in both files.

- **Claude Code releases tracking updated to v2.1.212** (`machine-readable/claude-code-releases.yaml`, `guide/core/claude-code-releases.md`): condensed two new releases. **v2.1.212** (2026-07-16) makes `/fork` copy the conversation into a new background session (the in-session subagent it used to spawn is now `/subtask`), adds a session-wide WebSearch cap (`CLAUDE_CODE_MAX_WEB_SEARCHES_PER_SESSION`, default 200) and a per-session subagent-spawn cap (`CLAUDE_CODE_MAX_SUBAGENTS_PER_SESSION`, default 200), auto-backgrounds MCP calls running past 2 minutes (`CLAUDE_CODE_MCP_AUTO_BACKGROUND_MS`), and ships two security fixes (plan mode no longer auto-runs file-modifying Bash without a prompt; worktree creation no longer follows a committed `.claude/worktrees` symlink outside the repo); it also deprecates the Task tool's `mode` parameter, now ignored (subagents inherit the parent session's permission mode). **v2.1.211** (2026-07-15) adds `--forward-subagent-text` / `CLAUDE_CODE_FORWARD_SUBAGENT_TEXT` for subagent text and thinking in stream-json output, plus two security fixes (permission previews neutralize bidirectional-override and look-alike characters; auto mode no longer overrides a PreToolUse hook's `ask` for unsandboxed Bash). Milestone and breaking-change summaries updated in both files.

- **Market sweep of open-source orchestrators added, CAO documented, consultancy-backed factory cohort introduced** (`guide/ecosystem/agentic-tools.md`, `guide/workflows/spec-first.md`, `guide/workflows/agentic-software-factories.md`, `claudedocs/perplexity-prompt-agentic-software-factories.md`): a July 2026 research pass surfaced eight open-source multi-agent orchestrators (CAO, Mission Control, KanBots, Claw-Kanban, OpenKanban, Open Orchestrator, AI Agent Board, refute-or-promote), all re-verified against the GitHub API rather than the research summary. **Seven of the eight fail the bus-factor test**, with a single contributor holding 95% to 100% of commits; the lone exception is **CAO** ([awslabs/cli-agent-orchestrator](https://github.com/awslabs/cli-agent-orchestrator), Apache-2.0, 41 contributors, top at 20%), now documented as **§4.6** in `agentic-tools.md`. The sharpest illustration of the guide's star-count skepticism is preserved in that section: Mission Control carries 5,763 stars against CAO's 893 (6.4x) and one person wrote 78% of its commits, so sorting the market by stars selects the wrong tool. Provider list taken from CAO's README rather than the research summary, which had it wrong (Antigravity CLI, Hermes Agent, Cursor CLI, not Gemini/Q as reported). **New "consultancy-backed factory" cohort** added to the full-cycle factories section of `spec-first.md`: Thoughtworks AI/works (launched January 2026) and Agent/works (launched June 16, 2026, both confirmed via press releases), Solario/WeScale, Sopra Steria IAKA, Accenture AI Refinery, a category the previous table missed because it listed only VC startups; these lead with governance and sell velocity second, inverting the startup pitch. Solario is flagged hardest, since a platform positioned "Governance Before Scale" documents no enforcement mechanism, no underlying model, no pricing, no named customer. Agent/works' "provable compliance before execution" claim is flagged as the one worth watching (closer to model checking than prompt governance, if real). The unbounded-velocity section of `agentic-software-factories.md` gains the market-level finding: **no maintained open-source orchestrator industrializes adversarial verification** (execute the code to break it); every tool examined falls back to exit codes, pre-push hooks, or LLM-on-LLM review, which makes Fusion's dead-code double-checkout the closest thing to an answer anyone has written, and even Refute-or-Promote's own reference implementation is a one-star playbook abandoned three days after creation. The Perplexity prompt file gained a fourth section (relance #3, the falsifiable challenge that asks a search engine to disprove the "no verified production deployment" claim on the closed platforms) plus an ESN/consultancy axis and a Solario exclusion. All GitHub figures re-derived via `gh api` on 2026-07-16, none taken from the research summary. **Falsifiable-challenge pass run on the closed platforms** (WebSearch, since the Perplexity MCP returns 401): an active attempt to disprove the guide's "no independently verified production case study" claim on Devin, Factory.ai and Blitzy. The claim survived but was sharpened rather than left as-is, because the search surfaced a large volume of named-customer cases the previous wording ignored (Mercedes-Benz 200K lines COBOL 8 months to 8 days, Itaú 70% of vulns, Blitzy Fortune 100 33M lines in 3.5 days, QAD, Builders FirstSource 3x, Factory 550K hours saved). Every one traces to the vendor's own blog or sales page, not to the customer or a neutral party (Mercedes-Benz let Cognition publish the figure and published none of its own). Section 2 of `agentic-software-factories.md` was rewritten to draw the exact distinction (a named logo is an endorsement, not an auditable measurement) rather than imply the platforms have no customers, which a reader who knows those names would rightly reject. The only third-party signals found run against the platforms (three teams documented dropping Devin inside a quarter, field defect rates ~1.5-2x human code), and no independent comparative cost study between a closed factory and the native stack exists, the exact number that would settle the "almost never" judgment.

- **New orientation hub for agentic software factories, closing the dispersion gap** (`guide/workflows/agentic-software-factories.md`, `guide/README.md`, `machine-readable/reference.yaml`, `guide/workflows/spec-first.md`, `guide/ecosystem/agentic-tools.md`): the topic was spread across 7 files that cross-referenced each other without ever converging, so a reader asking "how do I build a software factory with Claude Code" had to read `agentic-tools.md`, `third-party-tools.md`, `spec-first.md`, `methodologies.md`, `ai-ecosystem.md`, `agent-teams.md` and `ultimate-guide.md` in no particular order. The new page is an orientation hub, not a rewrite: all detail stays where it is. It carries a six-level spectrum (single session, `/batch`, native Agent Teams, dynamic-workflows, plan-pipeline, third-party orchestrators, closed factory) with the cost and the upgrade signal for each level, a reading map organized by intent rather than by file, and the **decision tree that did not exist**: when does a closed software factory (Factory.ai, Blitzy, Maleus, Devin) actually beat native Agent Teams plus `/batch` plus dynamic-workflows, which already cover most of the same need at no extra cost. Trees already existed for multi-instance vs single-instance (`ultimate-guide.md:20320`) and for agent teams vs other patterns (`agent-teams.md` section 7), but not for this choice, which is the expensive one. The verdict is stated rather than hedged (for a small team, almost never) and explicitly labelled as this guide's editorial judgment rather than a measured threshold, since no comparative cost study exists to settle it; the reasoning behind it is checkable, namely six sourced production use cases for Agent Teams against zero independently verified deployments with metrics for any closed platform. A self-host branch pointing at OpenHands was added so the choice does not read as binary. The governance checklist extends the four questions at `spec-first.md:970-975` with a fifth drawn from this session's Fusion analysis: is the verification feature the README advertises actually wired into the code path that runs in production, or only imported `import type` and never instantiated. Closes with a case-study callout on unbounded agentic velocity using the measured Fusion figures (727,279 lines in under 4 months, a 19,328-line `executor.ts`, 94% of commits from one identity, dual storage backend in parallel, a 986-line adversarial verification module built, tested and never wired), making the point that agentic velocity without architecture produces debt at a speed the industry has not had to handle before.

- **Fusion evaluated from source, 4/5, integrated as a case study only** (`docs/resource-evaluations/fusion-multi-agent-orchestrator.md`, `docs/resource-evaluations/README.md`): source-level evaluation of [Runfusion/Fusion](https://github.com/Runfusion/Fusion) at commit `8fe122d77` (MIT, pnpm TypeScript monorepo, 12 packages, 18 bundled plugins, `@runfusion/fusion` on npm), a multi-agent orchestrator marketed as "a software factory". Every claim was checked against code rather than documentation, which changed the verdict twice. **The one idea worth taking**: `packages/engine/src/mission-verification.ts` (986 lines) implements double-checkout adversarial verification, where the read-only AI judge is explicitly advisory rather than authoritative (lines 4-6), a real disposable checkout is materialized via `fs.mkdtemp` + `git worktree add --detach` (lines 338-341), and an agent-supplied regression test must **FAIL** on a second disposable checkout at the merge-base before it can pass (line 26, verdict at line 555), which mechanically kills `expect(true).toBe(true)` as a way to turn a task green; three typed verdicts (`pass | fail | inconclusive`, line 63) keep a flaky CI from being read as broken code (line 581). **That module is dead code in production**: `mission-execution-loop.ts` imports it `import type` only (lines 28, 112), the real implementation is imported by three test files and nothing else, `verificationCapability` is never wired at the single production instantiation point (`runtimes/in-process-runtime.ts:543-570`), and the code leaves behavioral assertions failed when it is absent (line 813); 5 commits, untouched since 2026-06-19. Wired-vs-advertised audit of 9 headline features: missions/autopilot (`in-process-runtime.ts:537`), shared branch groups, multi-node (`project-manager.ts:224`), `spawn_agent` and `delegate_task` are real; evals are gated behind `evalsView`, absent from `DEFAULT_ON_EXPERIMENTAL_FEATURES` (`core/src/experimental-features.ts:25`) and therefore off by default; "Signals" and "Connectors" from the README have no referent in code. **Health, the disqualifying number**: first commit 2026-03-25 (under 4 months old), 11,333 commits on main, 32 contributors displayed but gsxdsm plus bot identities account for **10,665 commits, 94%**, second human at 3.3%, and over the last 30 days gsxdsm at 2,203 against 55 for the runner-up. Bus factor 1. Velocity peaked in May (4,328 commits) and is declining (2,617 in June, ~1,900 on July's run rate). **Scale**: 727,279 lines excluding tests and node_modules, `executor.ts` alone at 19,328 lines, plus a dual storage backend maintained in parallel (`sqlite-adapter.ts` + `db.ts` alongside `postgres/`, every store duplicated: `agent-store.ts` at 122.7 KB beside `async-agent-store.ts`, `async-mission-store-queries.ts` at 85.8 KB), which explains the flood of `pg-*` changesets while `ROADMAP.md` still lists that migration as "planned". **Security is weak by default on all three layers**: agent execution defaults to `sandbox.backend = native` with bubblewrap opt-in and Linux-only, the heartbeat path grants write/edit/bash by system prompt (`agent-heartbeat.ts:595`) while the real fail-closed readonly allowlist (`workflow-step-tool-policy.ts:4-25`) only covers workflow-step gate nodes, and plugins run in-process with AI scan and signature verification both optional and off. Decision: **integrate as a case study, do not recommend as a tool**. Three angles carried forward: the double-checkout pattern deserves its own guide section as the concrete answer to the "decorative CI" trap already at `guide/workflows/spec-first.md:979-988` and to Refute-or-Promote (arXiv:2604.19049); Fusion as a market entry in `agentic-tools.md` with an explicit bus-factor caveat; and the involuntary lesson, that a single developer with agents shipping 727K lines in under 4 months also ships documentation describing a product that does not quite exist, tested-but-unwired code, and two storage backends in parallel, which is a case study in **agentic velocity bounded by no architecture** that nobody else is documenting. Two method notes logged: the local RTK token-compression proxy silently truncates git output to 50 lines and produced a false first-commit date on the first pass (re-run through `rtk proxy`), and `import type` erases at compile time so it proves no runtime wiring, a distinction that separated Fusion's advertised verification layer from its actual behavior and is likely a generalized trap across this market. Also produced `claudedocs/perplexity-prompt-agentic-software-factories.md`, a three-stage Perplexity research prompt (market sweep excluding the 35+ tools already covered, adversarial-verification deep dive, negative-experience sweep) calibrated on these findings, with bus factor as the primary elimination criterion.

- **Three missing agent orchestrators/frameworks added: MetaGPT, Symphony, Paperclip** (`guide/ecosystem/agentic-tools.md`, `machine-readable/reference.yaml`): reading Liza's own competitive survey ([mas-survey.md](https://github.com/liza-mas/liza/blob/24b35b90801450fb8b0599358efccdda3810145d/specs/architecture/competition-survey/mas-survey.md)) surfaced three projects the guide had never covered, while confirming that BMAD, gstack, GSD, CrewAI, Ruflo, OpenSpec, Spec Kit, Kiro, LangGraph and AutoGen were already handled. **§3.5 MetaGPT** (69,384 stars, MIT, Python): the original `Code = SOP(Team)` framework with five fixed roles, framed as a reference architecture rather than a dependency because the last tagged release is v0.8.1 from April 2024 and the last commit is January 2026, with team attention moved to the hosted MGX product. **§4.4 Symphony** (25,969 stars, Apache-2.0, Elixir): OpenAI's scheduler that watches a Linear board, creates one workspace per issue, spawns a Codex agent, and collects proof of work (CI status, PR review, complexity analysis, walkthrough video) before landing; notable for shipping [SPEC.md](https://github.com/openai/symphony/blob/main/SPEC.md) as the product and telling readers to have their own agent build the implementation, and carrying an explicit "low-key engineering preview" warning with no tagged release and no commit since June 9, 2026. **§4.5 Paperclip** (73,770 stars, 13,731 forks, MIT, TypeScript): org charts, budgets, approval gates and per-agent cost tracking over any runtime ("if it can receive a heartbeat, it's hired"), created March 2, 2026 and shipping weekly (v2026.707.0), positioned by its own README as "if OpenClaw is an employee, Paperclip is the company", which places it above rather than against Claude Code. Each entry documents where it stops: MetaGPT assumes SOP compliance and retries rather than preventing, Symphony has the agent self-certify with no review loop, and Paperclip governs who may act and how much they may spend but explicitly not how work is done inside a session. Also updated the spectrum diagram with an "agent orchestrator" tier, added three rows plus a staleness caveat to the comparison matrix, added four rows to the situation-to-tool guide, refreshed the stale CrewAI count (52K to 55K), and added `metagpt_tool` / `symphony_tool` / `paperclip_tool` anchors to reference.yaml. All figures re-derived from the GitHub API on 2026-07-15, none taken from the survey.

- **Liza evaluation updated with a fact-check of the project's own competitive survey, and converted to English** (`docs/resource-evaluations/liza-mas-framework.md`): the 3/5 score and the "mention as reference architecture in spec-first.md" decision are unchanged, since both rested on architecture (Go supervisors, circuit breaker, behavioral contract) verified against the repo rather than on the author's comparisons. Added a section documenting two problems with the survey. Its seven-category taxonomy produces a bucket of one ("Behavioral enforcement systems (Liza). One entry.", "Enterprise trust remains unsolved by everyone except Liza"), which is positioning rather than a finding. More measurably, it understates every competitor's traction in the same direction: gstack ~100.7k vs 122,026 actual, Paperclip "14k, just launched" vs 73,770, GSD 37k vs 64,742, CrewAI 45k vs 55,565, BMAD ~45.2k vs 50,631, MetaGPT 64k vs 69,384 (all `gh api`, 2026-07-15). Staleness explains part of it, but not the uniform direction, and the survey itself mixes figures dated a month apart in one matrix (gstack at 2026-05-22, BMAD at 2026-04-20). The practical effect is that its "Liza = Early vs GSD = 37k" row understates a gap that is really 322 against 64,742. Credit recorded where due: the per-competitor analysis is technically argued, and its critique of GSD (LLM-on-LLM orchestration has no hard trust boundary between orchestrator and subagent, versus Go-on-LLM) is reusable independently of Liza. Verdict: treat the survey as a lead list of projects to investigate, never as a source of figures. Two survey claims were checked and confirmed (MetaGPT's release really has been frozen since v0.8.1/April 2024; Symphony really is Apache-2.0, resolving the survey's own "some sources say MIT" hedge) and one marked unverifiable (the ~200-line goal doc that allegedly produced a full three-tier app, whose artifacts the survey admits live in a non-public repo). Confidence downgraded in wording from "Medium (architecture unique and verified)" to note the skewed self-reported comparisons. Separately, the file body was translated from French to English to match the repo's language rule and the 127-of-164 English majority in `docs/resource-evaluations/`; it was still untracked, so no committed content changed language.

- **IA-QA CLI evaluated and rejected (2/5, watch only)** (`docs/resource-evaluations/ia-qa-cli-llm-testing.md`, `docs/resource-evaluations/README.md`): evaluation of `@ia-qa/cli` v1.0.4 (Jean-Christophe Jamet, announced on LinkedIn 2026-07-15), a zero-dependency shell client exposing 148 QA/LLM tools from ia-qa.com, pitched at agents with shell access (Claude Code, Copilot CLI). Scored 3/5 on the announcement, downgraded to **2/5 after hands-on testing**. The 148-tool count is honest (verified against `GET /mcp?full=1`), but the package is 17.8 KB across 3 files and its own header comment states it "carries NO business logic" and runs everything on the hosted server, so every input (prompts, source, PII) is POSTed to a third party with no signup, no data processing agreement, and no retention policy. Measured three primitives against ground truth rather than trusting claims: `count_tokens` is literally `chars/4` and underestimates by **-35% on JavaScript and -23% on accented French** versus real `cl100k_base` (verified with tiktoken), erring in the unsafe direction and propagating into `estimate_llm_cost`, `context_window_check`, and `token_budget_calculator`, with a second error layer for Claude users since cl100k is the GPT tokenizer. `prompt_injection_scan` is regex matching: it caught 3/3 textbook payloads (system override, context exfiltration, DAN) but flagged a security *article about* injections as critical (false positive) and passed base64 and leetspeak payloads as clean (false negatives), unchanged across all three `sensitivity` levels, despite its description advertising "encoding tricks" detection. `hallucination_check` self-declares as word-overlap and non-semantic. Credit recorded where due: the 336-line client is well engineered (`writeSecureTmp` uses `wx` + mode `0o600` against symlink pre-creation, `SECRET_PARAMS` is exact-match with a comment on why substring matching breaks, stderr warning before sending secrets to a non-default server, `--<param>-file` to survive Windows `npx` argv truncation, no install scripts, zero deps), and the server-side tool descriptions are honest about their limits, so the overselling lives in the LinkedIn post rather than in the product. Not integrated: nothing fills a guide gap (`security-hardening.md` covers prompt injection, `third-party-tools.md` covers mcp2cli as the generic MCP-to-CLI solution, `ai-ecosystem.md` covers promptfoo, `ai-unit-economics.md` covers token cost) and recommending it would mean routing reader source through a third-party host. Two teaching points logged for later, unattached to the tool: a CLI advertising "zero dependencies, no signup" can still be a network client (17 KB cannot hold 148 tools, checkable via `npm view`), and `chars/4` token estimation fails on code by roughly a third. Re-evaluate if local execution ships, the server source is published, or a real tokenizer replaces the heuristic. Also corrected the index footer, which claimed "121 évaluations" against 162 files actually on disk.

- **Two teaching points from the IA-QA rejection carried into the guide** (`guide/security/data-privacy.md` §Risk 7, `guide/ops/ai-unit-economics.md` §"Do not estimate tokens by string length"): the tool was rejected at 2/5, but two findings generalized beyond it and were integrated as patterns, deliberately without naming the product (a day-0 free project by a solo dev does not belong by name in a "Known Risks" section; the named analysis stays in the evaluation file, where it is balanced with credit). **Risk 7, the local-looking network client**: a package can advertise "zero dependencies, no signup" truthfully and still POST every input to a server you do not control, because a thin HTTP client genuinely has no dependencies. Documents the arithmetic tell (`npm view <pkg> --json` unpacked size against advertised functionality: 17 KB across 3 files cannot hold 148 analysis tools, it holds a `fetch` call) and a one-liner to read the source from the tarball before running it. The section's core argument is that **MCP mode is categorically worse than CLI mode**: in CLI mode a human picks each input, which is a discipline problem a careful team can hold; in MCP mode the agent picks, and the agent has the codebase in context, so it will hand a proprietary file to a hosted `count_tokens` without anyone approving that specific call. Client-side hardening (temp files in `0600`, secret-param warnings) defends against argv leaks and local attacks, not against an agent deciding what to send. This framing came from a second independent evaluation session run against an unrelated production codebase and is sharper than the data-transfer framing the evaluation opened with. **Token estimation**: `chars/4` measured against real `cl100k_base` at +10% on English prose but **-35% on JavaScript and -23% on accented French**, erring in the unsafe direction (reports that a payload fits when it does not, so a budget guard silently passes what it exists to stop), with cl100k being OpenAI's tokenizer so a Claude-targeted estimate stacks a second error. Includes the subtler second-order variant: counting the raw user message while sending a prompt assembled from that message plus system header, role prefixes, and instruction block, which under-counts by everything the wrapper adds and stays invisible in tests that skip formatting. Both points were confirmed present in shipping production code during the second session (a `chars/4` helper guarding a hard provider limit on French user input, plus the count-the-wrong-string bug), which is what moved them from observation to guide content; that codebase is private, is not cited, and the guide sections use reconstructed examples. Both sections indexed in `machine-readable/reference.yaml` (`data_privacy_local_looking_client`, `ai_unit_economics_token_estimation`), YAML validated and anchors verified against the actual headings; the landing search index was rebuilt with `pnpm build:search` so Cmd+K resolves the two new entries.

- **Local CLI quiz (`quiz/`) category 16 realigned with the live web quiz, README counters corrected** (`quiz/questions/16-agent-harness-context.yaml`, `quiz/questions/17-team-metrics.yaml`, `README.md`, `quiz/README.md`): the bundled standalone CLI quiz tool and the live web quiz at cc.bruniaux.com/quiz had diverged on category 16, the CLI tracked "Team Metrics for AI-Augmented Engineering" (12 questions) while the web quiz already covered "Agent Harness & Context" (40 questions) under the same category number. Per user decision, the CLI now adopts the web's topic for category 16 (40 questions converted from the web's markdown source, `doc_reference` preserved per question), and Team Metrics moves intact to a new category 17. Local CLI quiz total goes from 334 to 374 questions across 17 categories. README.md and quiz/README.md badges/counts updated from the stale 271/159 and "10 Topic Categories" to the real 374/17. Separately, 55 new questions were added directly to the live web quiz (cc.bruniaux.com/quiz, `claude-code-ultimate-guide-landing` repo) covering recent Claude Code releases (v2.1.186-v2.1.204) and recently added guide sections, bringing that quiz to 401 questions across 16 categories; this was pushed by a parallel session during the same work window.

- **Full-guide offline exports refreshed and re-surfaced, EN + FR** (`whitepapers/guide-export.qmd`, `guide-export-fr.qmd`, `README.md`, landing `HeroBanner.astro`): the ~700-page PDF/EPUB export answering issue #60 had drifted (GitHub Release stuck at `guide-export-v3.38.3` since April 4 while `VERSION` was 3.41.1, because the automation cron was dead and the qmd cover version was hard-coded). Bumped both qmd covers to 3.41.1, rebuilt the EN PDF (17.2 MB) + EPUB (715 KB) locally with the Bold Guy Typst template, and published Release `guide-export-v3.41.1` marked latest so the existing landing badge and README links auto-resolve to the current build. Replaced the two low-contrast "full guide" hero badges (grey `#555`, easy to miss) with a dedicated download block on the landing (accent-bordered, `📖 Full guide (offline)`, EN and FR grouped) and expanded the README Downloads section from two EN badges to four EN/FR badges with flag labels. The FR side is now live: `guide/ultimate-guide.fr.md` was re-translated against the current EN guide (25,798 lines, up from 24,039), rendered to a 592-page PDF (16.4 MB) and EPUB (742 KB) with the Bold Guy Typst template, and uploaded to Release `guide-export-v3.41.1`, which now carries all four assets (EN pdf/epub + FR pdf/epub). The `releases/latest/download/guide-export-fr.{pdf,epub}` links resolve (verified 200), so the README and landing FR buttons work.

- **TDD workflow hook-config format corrected** (`guide/workflows/tdd-with-claude.md`): the PostToolUse example used the obsolete flat `{matcher, command}` shape, which current Claude Code silently ignores; replaced with the nested `hooks: [{ type: command, command }]` form. Surfaced while fact-checking a batch of portfolio TDD and security articles against this guide, where the articles already used the correct nested format.

- **Quiz fact-check audit against the live guide tree** (`claude-code-ultimate-guide-landing/src/content/questions/`): a 84-agent fact-check pass over all 346 live quiz questions (cc.bruniaux.com/quiz) against the current guide, official Anthropic docs, and live web search, triggered by a request to cross-reference the quiz with the guide's post-reorg file layout. 70 stale `doc_reference.file` paths were corrected (the guide moved several files into `core/`, `security/`, `roles/`, `ecosystem/`, and `ops/` subdirectories since these questions were written, e.g. `guide/core/architecture.md` to `guide/core/architecture.md`). 11 questions were flagged with a wrong "correct" answer, independently re-verified by 2 skeptic agents each, and 10 of the 11 were confirmed and corrected (option text and explanation rewritten), covering things like the nonexistent `/execute` command, `~/.claude/mcp.json` (Claude Code reads `~/.claude.json`, not that path), `${workspaceFolder}` (a VS Code convention, not supported here), and a `systemMessage`/`hookSpecificOutput.additionalContext` mix-up. Two YAML frontmatter bugs surfaced by the `pnpm build` Zod-schema gate were fixed (unquoted colons inside option values breaking YAML parsing). 64 new question drafts and category-coverage proposals were written to `claudedocs/quiz-audit-2026-07-08/` in the guide repo for manual review; none of those were auto-applied per the task's scope. Build passes across all 346 questions; nothing was committed or pushed in the landing repo.

- **Spec-driven agentic pipelines: BMAD-METHOD, OpenHands, spec-kitty, Agent Orchestrator, and the "AI software factory" category** (`guide/workflows/spec-first.md`, `guide/ecosystem/agentic-tools.md`, `guide/ecosystem/third-party-tools.md`, `docs/resource-evaluations/`): triggered by a competitive-landscape research pass on Maleus (formerly misheard as "Solario" in a meetup transcript), Adrien Maret's Paris-based full-cycle spec-to-deploy platform. Added OpenHands (`agentic-tools.md` §2.4, 79,900+ stars verified via `gh api`) as the open source equivalent to Devin, with its dependency-graph parallel execution (Tier 0/Tier 1 sub-agent spawning) and integrator-merge pattern. Added BMAD-METHOD (50,200+ stars) and spec-kitty (1,400+ stars) to `spec-first.md`'s tool-integration section: BMAD-METHOD's 19+ role-specific planning agents versus spec-kitty's git-worktree isolation with kanban-tracked merge gates and audit trail. Added a new "Full-cycle AI software factories" subsection covering Maleus, Factory.ai, Blitzy ($200M/$1.4B valuation, Northzone-led, May 2026, verified against SiliconANGLE/BusinessWire), and Devin as a distinct commercial category, framed around four governance questions (deterministic gate vs LLM self-grading, stop-the-line escalation, audit-trail traceability, spec staying authoritative after first generation) rather than a feature checklist. Added Agent Orchestrator (`third-party-tools.md`, right after Conductor, 8,100+ stars in 5 months, Apache-2.0) as the open source, cross-platform equivalent to Conductor, 23 supported agent CLIs vs Conductor's 2, plus a PostHog telemetry-by-default note and a correction of a secondary-source claim: the "CI retry twice then escalate" mechanism attributed to the project in cross-referenced research does not appear in its README, architecture doc, or status doc as of July 2026, and was not carried into the guide. Four new resource-evaluation files score BMAD-METHOD (4/5), OpenHands (4/5), spec-kitty (3/5), and Agent Orchestrator (3/5) against the existing 1-5 grid, all star counts and license fields verified live via `gh api` rather than secondary sources.

- **Liza MAS framework added as OSS governance reference architecture** (`guide/workflows/spec-first.md`, `docs/resource-evaluations/liza-mas-framework.md`, `machine-readable/reference.yaml`): the "Full-cycle AI software factories" section listed four closed/managed commercial products (Maleus, Factory.ai, Blitzy, Devin) but no open source counterpart that answers the four governance questions in the open. Added [Liza](https://github.com/liza-mas/liza) (Apache-2.0, 320 stars, single-author, verified via `gh api` 2026-07-12) as that counterpart: Go supervisors that enforce state transitions, role boundaries, merge authority and TDD gates mechanically rather than by prompt, adversarial doer/reviewer pairs per task, an auditable YAML blackboard, and an explicit circuit breaker, the one OSS example that documents the stop-the-line mechanism (governance question 2) I had flagged as rarely documented. Framed strictly as a reference architecture, not a dependency to adopt, given tiny adoption and no third-party production evidence. New evaluation file scores it 3/5 and keeps it distinct from the earlier `liza-mas-token-saving-cli-tools.md` (2026-06-10) that rejected the org's satellite CLIs (scip-search, mdtoc, functional-clusters, stacklit-cli), a different object. Fact-checked and corrected two undercounts in Liza's own README against live API: it cites BMAD "~45.2k stars" (actual 50,374) and CrewAI "45k" (actual 55,377), and its "L4 alongside BMAD/BEADS" positioning is a single IBM-exec quote, not an independent benchmark, both flagged in the evaluation.

- **Empirical backing for deterministic gates + multi-agent cost figures + Keli attribution fix** (`guide/workflows/spec-first.md`, `guide/ops/ai-unit-economics.md`, `docs/resource-evaluations/liza-mas-framework.md`): a Perplexity deep-research pass surfaced peer-review-adjacent evidence that was missing from the governance section. Added *Refute-or-Promote* ([arXiv:2604.19049](https://arxiv.org/abs/2604.19049), Abhinav Agarwal, verified live against arxiv.org) to governance question 1 in spec-first.md: a 31-day adversarial defect-discovery campaign, agents assigned to refute not confirm, mandatory empirical (PoC) gate, ~79% of 171 candidates killed, 4 real CVEs, and the decisive anecdote that ten LLM reviewers unanimously endorsed a Bleichenbacher padding oracle that did not exist, caught only by the empirical gate. This converts the "deterministic gate beats LLM self/peer grading" claim from assertion to sourced evidence. Added multi-agent token-cost orders of magnitude to `ai-unit-economics.md` (3-10x single-agent per naive-multi-agent task, 30-80% clawback via contracts/compression/KV-cache sharing), flagged as vendor-internal and analytical, not peer-reviewed. Corrected a factual error I introduced earlier in the Liza evaluation: Soufiane Keli is VP Software Engineering at Octo Technology (Accenture), not IBM; Perplexity independently confirmed no formal L1-L5 maturity model is published by him or anywhere, reinforcing the "do not cite as external validation" flag. Note: the earlier Liza changelog entry above still says "IBM-exec quote", left as-is as the historical record; the evaluation file carries the correction.

- **machine-readable/reference.yaml sync + BMAD duplication fix** (`machine-readable/reference.yaml`, `guide/core/methodologies.md`, `guide/workflows/spec-first.md`): the additions above had not been indexed. Added 15 new keys (bmad_method_*, spec_kitty_*, openhands_*, ai_software_factories_*) with anchor-verified links. Found and fixed a real duplication risk the user flagged: `methodologies.md` already documents BMAD-METHOD as a Tier 1 methodology (constitution.md, when to use/avoid) but had no link to the newly added installation instructions in `spec-first.md`, and its only source link pointed to a Claude-Code-specific fork (`24601/BMAD-AT-CLAUDE`) rather than the canonical `bmad-code-org/BMAD-METHOD` repo. Added bidirectional cross-links between the two sections and the canonical repo URL with verified star count. Also caught and fixed two stale line-number references in reference.yaml (`resource_evaluations_appendix` pointed to `ultimate-guide.md:20886`, an unrelated llms.txt discussion; the real Appendix C is at line 26294. `resource_evaluations_readme_section` pointed to `README.md:307`, mid-quiz-section; the actual "151 Resource Evaluations" heading is at line 354) and flagged a larger pre-existing gap without fixing it: `docs/resource-evaluations/README.md`'s index table lists 43 rows against 160 actual evaluation files on disk, a discrepancy that predates this session and needs a dedicated audit pass.

- **Edgee Compressor V2 documented, cross-referenced with RTK, plus new prompt-compression/gateway/methodology coverage** (`guide/ecosystem/context-engineering-tools.md`, `guide/ecosystem/mcp-vs-cli.md`, `guide/ops/ai-unit-economics.md`): the existing Edgee entry described the pre-V2 generic "composable edge layer" positioning. Replaced it with the actual three-layer Compressor V2 architecture (brevity, Tool Surface Reduction, tool result trimming) from Edgee's July 2, 2026 blog post, its explicit RTK lineage for the trimming layer, and a sourced critique of the post's methodology: SWE-bench Lite's resolution rate is never measured, the "50%" headline traces closest to brevity's raw aggregate rather than a combined end-to-end measurement, and the n=6/n=8 sign-test sample sizes are flagged against their significance ceiling (a perfect 6-of-6 score is the only outcome that clears p<0.05 at n=6). Added three previously uncovered academic prompt-compression techniques to context-engineering-tools.md §4 (Selective Context, AutoCompressors/Gisting, RECOMP), each flagged research-only vs. production-adopted per source verification. Added LiteLLM and GPTCache to §5 (AI Gateways), and a KV-cache-compression research-frontier note (eviction/quantization/low-rank families, ChunkKV, TurboQuant) to §8. Added Klavis AI/Strata and Arcade.dev to the MCP tool-surface-reduction table in `mcp-vs-cli.md`, both with vendor-reported figures flagged as unverified. Added a new §6 to `ai-unit-economics.md`, "How to read a vendor's cost-reduction claim" (paired vs. unpaired comparisons, sign test vs. paired t-test, the significance ceiling at small n, reading bootstrap confidence intervals, median vs. aggregate, and a checklist), generalizing the Edgee critique into a reusable framework for evaluating any vendor's benchmark claims.

- **Edgee production numbers cross-checked against the vendor's own docs, plus corrected Klavis/Strata and Arcade.dev benchmark figures** (`guide/ecosystem/context-engineering-tools.md`, `guide/ecosystem/mcp-vs-cli.md`): a follow-up WebSearch/WebFetch pass on the Edgee critique above (triggered by cross-checking a Perplexity research summary against primary sources) surfaced a second, separate set of numbers on Edgee's own docs page (`edgee.ai/docs/introduction/why-edgee`, distinct from the blog post): production averages across real customer traffic put brevity at ~6.5% and tool result trimming at ~19%, against the blog's 6-task benchmark figures of ~30% and ~10% respectively, with tool surface reduction at ~25% but still labeled "in development." The same docs page answers the resolution-rate gap with "zero measurable drift on SWE-Bench Verified samples," a claim with no sample size, no definition of "measurable," and no confidence interval, added to the guide as a documented example of an unquantified rebuttal to a statistically grounded critique. Separately, direct WebFetch verification of `edgee-ai/compression-lab`'s README confirmed it contains zero mentions of SWE-Bench Verified, drift, or resolution rate, ruling out that the production claim lives in the benchmark repo itself. Also corrected the Klavis AI/Strata row in `mcp-vs-cli.md` from a vague "+13% accuracy" figure to the actual named benchmark (MCPMark: +15.2% pass@1 vs. the official GitHub MCP server, +13.4% vs. Notion, 85-100x token reduction), and added Arcade.dev's vendor comparison against Composio (7,426 vs. 747,083 tokens across 8 CRM queries) which had previously been described only qualitatively. LLMLingua-2's exact figures (2x-5x compression, 1.6x-2.9x end-to-end latency speedup, ACL 2024 Findings) and ChunkKV's confirmed 26.5% throughput gain (arXiv 2502.00299) were independently verified against primary sources during the same pass.

- **Context engineering pages refreshed against July 2026 research** (`guide/core/context-engineering.md`, `guide/ecosystem/context-engineering-tools.md`, `guide/ecosystem/mcp-servers-ecosystem.md`, `guide/ecosystem/third-party-tools.md`): synced against two dated research passes (context-engineering-concepts-2026-07.md, context-engineering-tools-panorama-2026-07.md). Added the disputed authorship of the term "context engineering" (Karpathy vs. Dex Horthy/12-Factor Agents' "dumb zone"), a refinement note on context rot (NIAH underestimates degradation on semantically ambiguous queries, per the MonitorBench 98.6%→88% data point), a cross-reference from the dynamic-context section to the already-documented Managed Agents brain/hands/session-log architecture (`ai-ecosystem.md` §14) plus the April 2026 Anthropic posts on it, and a new research subsection covering ACON, Less Context Better Agents, AMA-Bench, Agent Memory characterization, ContextBudget, Classifier Context Rot, Context Kubernetes, and Recursive Language Models, each tagged with its actual confidence level (single-paper claim, prototype-only, independently reproduced, etc). Added a new Optical/Visual Context Compression pattern (DeepSeek-OCR lineage) cross-linked to a new **pxpipe** tool profile. Added **Cloudflare Code Mode MCP** (99.9% tool-schema-loading reduction via a two-meta-tool code-execution pattern), **TOON** (Token-Oriented Object Notation, format-dependent gains), and a new "ghost tokens" / context-quality-after-compaction concept (`alexgreensh/token-optimizer`). Refreshed GitHub star counts via the tools' own verification method (`gh api`, 2026-07-07): RTK 446→69,042, Headroom 43,000→57,223 (plus its org move from `chopratejas/headroom` to `headroomlabs-ai/headroom`), context-mode 14,149→18,654 (12→17 supported platforms), cc-statistics 87→109. Added a new MCP protocol roadmap subsection (stateless core, Extensions, Tasks, deprecation policy, per the 2026-07-28 release candidate) and the NSA's June 2026 MCP security guidance to `mcp-servers-ecosystem.md`. Every rapid-growth or self-reported figure (RTK's 2.8x star jump, Headroom's "$700K saved" claim) is flagged with its verification caveat rather than stated as fact, matching the source research's own hedging.

- **Audience pages published on the landing** (`docs/for-product-managers.md`, `for-tech-leads.md`, `for-cto.md`, `for-cio-ceo.md`): the four role pages were only readable on GitHub. The landing build script (`prepare-guide-content.mjs`) now pulls them from `docs/` and serves them at `/guide/for-product-managers/`, `/guide/for-tech-leads/`, `/guide/for-cto/`, and `/guide/for-cio-ceo/`, with a "For Your Role" section on the `/guide/` index, sitemap and RSS entries, and Cmd+K search coverage. Deep links like `ultimate-guide.md#35-team-configuration-at-scale` now resolve to the correct chapter page instead of landing on the chapter index (new `resolveUltimateGuideAnchors` pass, applied to all served pages).

- **Claude Code Releases**: Updated tracking to v2.1.210 (from v2.1.197)
  - v2.1.198 (2026-07-01): subagents now run in the background by default, Claude in Chrome generally available, background agents auto-commit and open draft PRs, Explore agent inherits the session model, `/agents` wizard removed
  - v2.1.199 (2026-07-02): stacked slash-skill invocations load up to 5 skills, transient 429s retried automatically for subscribers, streaming partials preserved on mid-stream errors, subagents return partial work and report API errors to the parent instead of failing silently
  - v2.1.200 (2026-07-03): `AskUserQuestion` no longer auto-continues by default, "default" permission mode renamed "Manual" across CLI/VS Code/JetBrains, background sessions fixed after sleep/wake and stale `daemon.lock` crashes
  - v2.1.201 (2026-07-03): Sonnet 5 sessions no longer use the mid-conversation system role for harness reminders
  - v2.1.202 (2026-07-06): "Dynamic workflow size" setting in `/config`, `workflow.run_id`/`workflow.name` OTel attributes, `/review <pr>` reverted to fast single-pass (use `/code-review <level> <pr#>` for multi-agent)
  - v2.1.203 (2026-07-07): login-expiry warning, manual-mode footer badge, background-agent stability fixes (macOS stall, stale daemon tokens, crash-looping, silent auto-upgrade failure), ~7 MB binary size reduction
  - v2.1.204 (2026-07-08): fixed hook events not streaming during SessionStart hooks in headless sessions
  - v2.1.205 (2026-07-08): `/doctor` becomes a full setup checkup (`/checkup` alias), agent view gains colored state words + classifier-written headlines, auto mode blocks transcript-file tampering and asks before `rm -rf` on unresolved variables, `--json-schema` invalid-schema and `format`-keyword fixes
  - v2.1.206 (2026-07-09): `/doctor` check proposes trimming checked-in `CLAUDE.md`, `/commit-push-pr` auto-allows push to the configured push remote (not just `origin`), background agents upgrade in the background right after an update, `/code-review` findings quality improved on claude-opus-4-8
  - v2.1.207 (2026-07-11): Bedrock/Vertex/Claude Platform on AWS default to Opus 4.8, terminal streaming perf fix for long content, auto mode without opt-in on Bedrock/Vertex/Foundry; breaking for plugins: `${user_config.*}` rejected in shell-form commands (shell-injection fix) and `pluginConfigs` no longer read from project-level settings
  - v2.1.208 (2026-07-13): screen reader mode (`--ax-screen-reader`, `CLAUDE_AX_SCREEN_READER=1`, or `axScreenReader: true`), `vimInsertModeRemaps` for two-key insert-mode sequences like `jj`, `CLAUDE_CODE_PROCESS_WRAPPER` for corporate launchers, false "100% context used" after auto-update fixed, 200-row cap on very large markdown tables
  - v2.1.209 (2026-07-14): fixed `/model` and other dialogs being blocked in `claude agents` background sessions (reverts an overly broad 2.1.208 guard)
  - v2.1.210 (2026-07-14): live elapsed-time counter on the collapsed tool summary line, Agent tool hardened against indirect prompt injection, worktree-isolated subagents no longer able to run git-mutating commands against the main checkout, `ultracode` opt-in no longer fires on webhook payloads or relayed PR comments, auto mode's permission classifier defaults to Sonnet 5 for external sessions; deprecation: `Write(path)`/`NotebookEdit(path)`/`Glob(path)` permission rules now warn at startup, use `Edit(path)` or `Read(path)`

- **Claude Code Releases**: Updated tracking to v2.1.197
  - v2.1.197: ⭐ Claude Sonnet 5 introduced as the default model, native 1M-token context window, promotional pricing $2/$10 per Mtok through August 31
  - v2.1.196: Org default models in `/model`; readable session names; clickable file attachments; security fix for `.mcp.json` servers self-approved via committed settings; streaming idle watchdog on by default
  - v2.1.195: Bug fixes: hook exact-match for hyphenated names, voice dictation, background agent daemons, plugin name mismatch; `CLAUDE_CODE_DISABLE_MOUSE_CLICKS`; Remote provisioning checklist
  - v2.1.193: ⭐ `claude_code.assistant_response` OTel event (review if logging prompts); `autoMode.classifyAllShell`; live bash path autocomplete; auto memory-pressure reaping
  - v2.1.191: ⭐ `/rewind` works after `/clear`; ~37% CPU reduction during streaming; MCP capability discovery retries; 20+ bug fixes
  - v2.1.190: Bug fixes and reliability improvements
  - v2.1.187: ⭐ `sandbox.credentials` blocks credential file reads; org model restrictions in picker/`--model`/`ANTHROPIC_MODEL`; MCP 5-min hang fix; 15+ bug fixes

- **Claude Code Releases**: Updated tracking to v2.1.183
  - v2.1.183: ⭐ auto mode safety (destructive git ops + `git commit --amend` + terraform/pulumi/cdk destroy blocked unless explicitly requested), model deprecation warnings on stderr + agent frontmatter, `attribution.sessionUrl` setting, `/config --help`, 10+ bug fixes (thinking 400 errors, WebSearch in subagents, tmux pane launch, scheduled tasks no longer treated as keyboard input)

- **Claude Code Releases**: Updated tracking to v2.1.181
  - v2.1.174: `wheelScrollAccelerationEnabled` setting, `/model` picker Default model family fix, VS Code usage attribution per-skill/agent/plugin/MCP, 8+ bug fixes (Bedrock GovCloud prefix, background session env inheritance, Fable 5 billing banner)
  - v2.1.175: `enforceAvailableModels` managed setting: constrains Default model to allowlist, blocks user/project settings from widening managed list
  - v2.1.176: session titles in conversation language + `language` setting, `footerLinksRegexes` setting, Bedrock credential caching until Expiration, 15+ bug fixes (availableModels alias enforcement, Fable 5 auto mode fallback, hook `if` path conditions, Linux sandbox symlink, tmux clipboard, Remote Control)
  - v2.1.178: `Tool(param:value)` permission syntax, nested `.claude/` directory improvements, auto mode subagent pre-classification, improved `/doctor`, 10+ bug fixes (subagent transcript, compaction fallback model, MCP disallowedTools server-level specs, vim undo)
  - v2.1.179: fixed mid-stream connection drops, WSL2 mouse-wheel scroll regression (2.1.172), sandbox denyRead/allowRead glob performance, feedback survey capture, welcome banner stacking, 4+ more fixes
  - v2.1.181: `/config key=value` inline syntax, `sandbox.allowAppleEvents`, `CLAUDE_CLIENT_PRESENCE_FILE`, improved streaming + subagent panel, 30+ bug fixes (prompt caching ANTHROPIC_BASE_URL, Write/Edit truncated files on network drives, startup 120ms regression, macOS TUI freeze)

- **Resource evaluations**: evaluated liza-mas token-saving CLI tools and Semble semantic search
  - `liza-mas` roster (scip-search, mdtoc, functional-clusters, stacklit-cli): all score 1-2/5. scip-search (0 stars, day-one release), mdtoc (1 star, generic utility), and functional-clusters (0 stars, framework-internal) rejected. stacklit-cli (2 stars, Go variant of documented stacklit concept) added to watch-list with trigger condition 50+ stars.
  - Semble (MinishLab/semble, ~5k stars, MIT): score 3/5. Integrated as Ollama-free alternative to grepai in `guide/ecosystem/mcp-servers-ecosystem.md` Code Search section. Corrects community claim of "index-free" (Semble builds and caches an index; the differentiator is no Ollama dependency, broader search scope code+docs+config).
  - Eval files: `docs/resource-evaluations/liza-mas-token-saving-cli-tools.md`, `docs/resource-evaluations/semble-code-search.md`

- **Cost Optimization Levers table** (`guide/ultimate-guide.md` §9.13): added a structured overview of the 6 cost levers (monitoring, output compression, model routing, prompt caching, batch processing, semantic pre-indexing) with Native vs. API/SDK columns and cross-links to existing documented sections. Includes RouteLLM citation (lm-sys, ICLR 2025, arXiv 2406.18665: 85% cost reduction on MT-Bench vs always-strong routing).

- **Batch API discoverability** (`guide/ultimate-guide.md` §9.13): added cross-link to Message Batches API section in `core/architecture.md` (50% cheaper async processing), previously only reachable from an architecture deep-dive.

- **machine-readable/reference.yaml**: added `semble_*` entries (upstream, guide, evaluation, purpose, vs_grepai note), `cost_levers_table` pointer (§9.13 new subsection), `batch_api_cost_lever`, `routellm_citation` (arXiv:2406.18665). Updated `updated` date to 2026-06-10, `resource_evaluations_count` to 86.

- **Claude Code releases tracking**: updated from v2.1.168 to v2.1.170
  - v2.1.169 (2026-06-09): `--safe-mode` flag + `CLAUDE_CODE_SAFE_MODE`, `/cd` command, `disableBundledSkills` setting, enterprise MCP policy fix, macOS startup stall fix, 15+ bug fixes
  - v2.1.170 (2026-06-09): ⭐ Claude Fable 5 (Mythos-class model) access, VS Code terminal transcript fix

- **Claude Code releases tracking updated to v2.1.237** (`machine-readable/claude-code-releases.yaml`, `guide/core/claude-code-releases.md`, `mcp-server/content/claude-code-releases.yaml`, `mcp-server/package.json`, landing `src/data/releases.ts`): added the five releases published between 2026-08-14 and 2026-08-19. v2.1.233 removes the todo and task tools (TaskCreate/Get/Update/List, TodoWrite) on Opus 4.8, Sonnet 5, Fable 5, Mythos 5, and newer models behind `CLAUDE_CODE_ENABLE_TODO_TOOLS=1`, reverts the v2.1.232 Bash permission changes for Cygwin-style symlinks and input redirections, and closes the NT `\??\` device-prefix bypass of UNC path validation. v2.1.234 extends that rejection to remote file reads, session restore, CLAUDE.md includes, workflow scripts, and uploads, adds a GitLab merge request badge to the footer and statusline, makes sessions resume themselves when a claude.ai usage limit resets, drops the "Default teammate model" setting, and cuts the built-in `claude-api` skill from roughly 200K tokens to 25K. v2.1.235 adds an optional `spellcheck` setting and makes permission dialogs state what a grant actually covers. v2.1.236 adds `ANTHROPIC_DEFAULT_MODEL` and `notify_when_idle` on cross-session `SendMessage`, and gives macOS wildcard read-deny rules precedence inside allowed read regions. v2.1.237 adds the built-in "Concise" output style. Recorded v2.1.234 as a milestone, added four behavior entries and one security entry to `breaking_summary`, bumped the MCP server package to 1.2.10 and rebuilt it, and regenerated the landing guide search and content indexes. No RSS entry: the landing feed reads `releases.ts` directly, so a manual entry would duplicate.

### Updated

- **Headroom section rewrite** (`guide/ecosystem/context-engineering-tools.md`): corrected wrong URL (`headroom.ai` was an unrelated domain; correct source is `github.com/chopratejas/headroom` with docs at `headroom-docs.vercel.app`). Updated star count to 43,000 (June 2026). Added full deployment mode list (Python lib, TypeScript/npm, HTTP proxy, MCP server, agent wrap). Explained CCR (Compress-Cache-Retrieve) architecture: `{{HEADROOM_TAG_N}}` placeholders + SQLite/HNSW/FTS5 store + cross-agent shared memory. Added output shaper mechanism (cache-prefix-safe brevity instruction + 10% holdout control group). Corrected benchmark scope: published 92% figures are for specific content types under optimal conditions; independent full-session measurement found approximately 47% reduction. Added five known bugs: Issue #714 (5-minute CCR TTL, retrieval failures on long jobs), Issue #1158 (200K context cap for Claude Max users with `headroom wrap`, use MCP instead), Issue #1227 (CORS security, unresolved), Issue #1209 (placeholder stored as original in CCR), Issue #1233 (28% Python syntax failure in CodeAwareCompressor).

- **Table of Contents and tool selection table** (`guide/ecosystem/context-engineering-tools.md`): ToC section 3 updated to list Token Savior. Section 10 "file reads" row updated to include Token Savior alongside tilth and lean-ctx. Confidence header date updated from March 2026 to June 2026.

- Promoted Opus 4.8 (`claude-opus-4-8`) to current/recommended/default Opus across guide, whitepapers, recap cards, machine-readable files, and landing data; demoted Opus 4.6 and 4.7 to previous generation.

- Added Fable 5 (`claude-fable-5`, Mythos-class) to model-lineup and selection tables throughout the guide and whitepapers.

- Updated fast-mode references from "6x price" to "2x price" (verified for Opus 4.8) and corrected the `/fast` cheatsheet entry.

- Marked Opus 4.8 standard pricing as "see official docs" (no published rate); kept 4.6/4.7 rows as previous-generation reference.

- Updated effort API code example (`guide/ultimate-guide.md` §11.1) from `claude-opus-4-7` to `claude-opus-4-8`.

- Added "Escalating to Fable 5" mini-section at §2.5 (model selection guide): decision trigger, practical scenarios, access command, and pricing note.
## [3.41.2] - 2026-06-04

### Security

- **Threat database v2.20.0** (`examples/commands/resources/threat-db.yaml`): monthly update. New CVE: CVE-2026-32211 (Azure DevOps MCP `@azure-devops/mcp`, CVSS 9.1, missing authentication, no patch yet). New attack technique T031 Shadow Escape (Operant AI, May 2026): zero-click data exfiltration via poisoned documents in MCP-connected AI assistants, no user interaction beyond document upload, exfil blends into normal agent traffic. New scanning tools: Golf Scanner (open-source Go CLI, discovers MCP configs across 7 IDEs, 20 security checks, 0-100 risk score) and Microsoft MDASH (multi-model agentic vuln discovery, 100+ AI agents, Defender integration). New defensive resources: NSA AISC MCP Security Design Considerations advisory (May 20, 2026), Five Eyes "Careful Adoption of Agentic AI Services" joint guidance (May 4, 2026), Microsoft Build 2026 MXC SDK + Agent 365 policy controls. Updated: hightower6eu malicious skill count 354 to 677; CVE-2026-39861 description clarified as symlink sandbox escape, fixed_in corrected to 2.1.64. 7 new sources added (151 total).

## [3.41.1] - 2026-06-04

### Added

- **Landing catalog sync** (`examples-data.ts`, `scripts/check-landing-sync.sh`): added 50 missing SKILL.md entries to the landing examples catalog. All standalone skills added since the last manual sync (2026-05-03) are now discoverable on cc.bruniaux.com/examples/. Skills added: ci-all, ci-pipeline, ci-status, ci-tests, commit, ship, pr, review-pr, review-plan, release-notes, land-and-deploy, canary, sandbox-status, git-worktree, git-worktree-clean, git-worktree-remove, git-worktree-status, handoff-create, handoff-resume, handoff-update, session-save, catchup, investigate, diagnose, explain, learn-alternatives, learn-quiz, learn-teach, qa, refactor, optimize, generate-tests, validate-changes, audit-codebase, sonarqube, check-cache-bugs, security, security-audit, security-check, update-threat-db, scaffold, recipe-template, methodology-advisor, autoresearch, routines-discover, plan-pipeline, eval-agents, eval-hooks, plus templates/feature-list.json and workflows/feature-list.json. Catalog grows from 220 to 270 indexed entries. Fixed sync check script pointing at dead pre-Astro HTML files; now reads from examples-data.ts and index.astro directly. Reconciled count: all landing pages now display 270 (was 255/219 inconsistency). Plugin callout corrected from "All 255 templates as plugins" to "180+ core templates as 8 plugins" (accurate).

- **CLI reference full sync** (`guide/ultimate-guide.md` §10.3 CLI Flags Reference + Subcommands): synced against the official `code.claude.com/docs/en/cli-reference` page. Added 14 missing flags: `--bare`, `--bg`, `--exec`, `--effort`, `--name/-n`, `--tmux`, `--debug-file`, `--dangerously-load-development-channels`, `--exclude-dynamic-system-prompt-sections`, `--include-hook-events`, `--prompt-suggestions`, `--replay-user-messages`, `--remote-control/--rc`, `--remote-control-session-name-prefix`. Added 8 missing subcommands: `claude attach`, `claude auto-mode defaults`, `claude daemon status/stop`, `claude logs`, `claude respawn`, `claude rm`, `claude stop`. Fixed 2 pre-existing em dashes in the section.

- **Environment variables full sync** (`guide/core/settings-reference.md` § Environment Variables): synced the env var catalog from v2.1.81 to v2.1.162 against the official `code.claude.com/docs/en/env-vars` page. Added ~90 missing variables across existing categories and three new subsections: OpenTelemetry (15 vars: `OTEL_LOG_*`, `OTEL_METRICS_*`, `CLAUDE_CODE_OTEL_*`, `CLAUDE_CODE_PROPAGATE_TRACEPARENT`), Plugins (`CLAUDE_CODE_PLUGIN_*`, `CLAUDE_CODE_SYNC_PLUGIN_*`), and SDK and Headless (`CLAUDE_CODE_RESUME_*`, `CCR_FORCE_BUNDLE`, `CLAUDE_REMOTE_CONTROL_SESSION_NAME_PREFIX`, etc.). Cloud Providers split into four sub-tables: Bedrock, Bedrock Mantle, Vertex AI (with 12 region overrides), Foundry, Claude Platform on AWS. Promoted `CLAUDE_CODE_MAX_TURNS` from Unverified to official Timeouts category. Fixed `CLAUDE_CODE_SUBPROCESS_ENV_SCRUB` description. Added cross-links from `ultimate-guide.md` §10.3 and Appendix A to the full catalog. Updated `machine-readable/reference.yaml` description to reflect 190+ vars across 17 categories.

- **DeepSec** (`guide/ecosystem/third-party-tools.md` § Security Scanning): documented Vercel Labs' agent-powered application vulnerability scanner. Covers the 5-step pipeline (scan → process → triage → revalidate → export), CLI commands, `--diff` mode for PR gating, distributed execution via Vercel Sandboxes, cost model (Claude Opus 4 with extended thinking, $10–50+ per full scan), false positive rate (~10–20%), plugin system, and security posture recommendations. Updated section intro to cover both config-level and application-level scanning.

- **Built-in Tools Reference** (`guide/core/tools-reference.md`): new page covering all 40 built-in tools. Full tool table by category (file ops, execution, web, agents, tasks, scheduling, MCP, worktrees, control flow) with permission-required column and version notes. Complete `ToolName(specifier)` permission rule format table including the previously missing `Skill(deploy *)` row and corrected `Agent(Explore)` name. Per-tool behavior sections for Bash (working-dir carry-over, env var persistence, 2-min default/10-min max timeout, 30k char output cap), Edit (read-before-edit, exact-match, uniqueness), Glob (100-file cap, no `.gitignore` by default), Grep (ripgrep syntax, `.gitignore`-aware, 3 output modes), Read (images, PDFs with page ranges, Jupyter notebooks), WebFetch (lossy Markdown conversion, 15-min cache, redirect behavior), WebSearch, Write. Mini how-to sections for Monitor (v2.1.98+), Workflow/ultracode (v2.1.154+), `/loop`+ScheduleWakeup, agent teams (TeamCreate/TeamDelete/SendMessage behind `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1`), and Tasks API including `TaskStop` and the v2.1.142 TodoWrite disable-by-default change. Linked from `guide/README.md`, root `README.md`, `machine-readable/reference.yaml`, and `guide/cheatsheet.md`.

- **architecture.md fix** (`guide/core/architecture.md`): removed the outdated claim "Claude Code has exactly 8 core tools"; replaced with framing that names 8 daily-use tools and points to the new complete reference. Updated `Task` to `Agent` (current tool name) and added a note that `TodoWrite` is superseded by the Tasks API since v2.1.16, disabled by default since v2.1.142.

### Documentation

- **Glossary split** (`guide/core/`): separated the previous monolithic glossary file into two focused files. `glossary.md` now covers the 31 official Claude Code terms (Agent teams, Agentic loop, Auto memory, Bare mode, Channel, Compaction, Dispatch, Effort level, Hook, MCP, Non-interactive mode, Permission mode, Project trust, Settings layers, Skill, Subagent, Surface, Teleport, Verification loop, Worktree isolation, and more) in paragraph format with links to guide sections. `community-patterns.md` preserves the previous ~130-term table covering community-coined patterns (Boris Cherny pattern, ACE pipeline, BMAD, gstack, context engineering, vibe coding) alongside AI engineering vocabulary and Claude Code config quick-reference. `guide/README.md` updated with entries for both files.

- **Hooks documentation pass 3**: verified lifecycle diagram exit code is Exit 2 (blocks) in both mermaid and ASCII fallback; confirmed PermissionRequest and SubagentStop nodes present in diagram with correct styles and click links; verified `examples/hooks/README.md` event table covers all 30 events grouped by 8 categories; confirmed quiz question 07-002 states 30 events in 8 groups with correct group enumeration; confirmed `guide/core/settings-reference.md` references the full hook event set via section link rather than a hardcoded count. All items were already correct following passes 1 and 2; this pass documents the final verification.

- **Hooks and skills documentation pass 2** (`guide/ultimate-guide.md`, `machine-readable/reference.yaml`): corrected `Setup` event description (was "environment setup phase at session start", fires only with `--init-only`/`--init`/`--maintenance` in `-p` mode); corrected async hooks limitation (guide incorrectly stated they cannot return `additionalContext`, they can); added `agent_id`/`agent_type` to common input fields table; added `CLAUDE_ENV_FILE` section for SessionStart/Setup/CwdChanged/FileChanged; added Per-Event Reference table covering all 30 events with specific input/output fields; added `model` and `hooks:` to skills frontmatter table; added deprecation notice for `.claude/commands/` (merged into `.claude/skills/` since v2.1.3); updated Common Patterns table to say "Skill (user-invocable)" instead of "Command"; fixed em dash in HumanLayer source link; corrected `MessageDisplay` description and `hooks_async_limitations` in reference.yaml; added `skill_frontmatter_fields` block to reference.yaml. Second pass corrected two factually wrong "When it fires" descriptions in the 30-event table: `PermissionDenied` (now correctly states it only fires when the **auto mode classifier** denies, not on manual user denials, and documents the `retry: true` output); `Elicitation` (was "Claude requests information from user (headless)", now correctly "An MCP server requests user input during a tool call"). Also improved `InstructionsLoaded` (added `.claude/rules/*.md` and lazy-load detail), `CwdChanged`/`FileChanged`/`WorktreeCreate`/`WorktreeRemove` (aligned wording with official spec), and removed an em dash from the Stop/SubagentStop callout.

- **Claude Code Releases**: Updated tracking to v2.1.162 (2026-06-04)
  - v2.1.162: Quieter startup, `claude agents --json` waitingFor, slash-command fill-in, Windsurf renamed Devin Desktop, 25+ bug fixes
  - v2.1.161: OTEL custom dimensions, agents done/total, /mcp unused connectors collapsed, parallel tool-call isolation, 20+ bug fixes
  - v2.1.160: `ultracode` replaces `workflow` keyword (breaking), security prompts for startup files and build-tool configs, Edit after grep, 20+ bug fixes
  - v2.1.159: Internal infrastructure improvements (no user-facing changes)

### Added

- **`hooks-events-reference.md`** (`guide/core/hooks-events-reference.md`): new comprehensive reference for all 30 Claude Code hook events. Covers matcher field per event type (different events match on different fields), exit code 2 behavior for all 30 events, decision control format per event (top-level `decision` vs `hookSpecificOutput` vs path return), key input fields per event, handler configuration fields for all 5 types (command, http, mcp_tool, prompt, agent), `asyncRewake` field, `CLAUDE_ENV_FILE` availability, `terminalSequence`, path placeholders, and common gotchas (Stop hook 8-block cap, `UserPromptSubmit` 30s default, `WorktreeCreate` replaces git entirely, and more).
- **`eval-agents` skill** (`examples/skills/eval-agents/SKILL.md`): new audit skill for Claude Code agent fleets. Scores agents on 5 criteria (name, description specificity, model tier, tools scoping, system prompt quality) out of 15 pts with a +1 hardening bonus. Detects description overlap between agents that causes non-deterministic orchestrator dispatch, flags missing `tools:` fields (unconstrained session tool inheritance), identifies human-in-the-loop anti-patterns that break headless pipelines, and checks model-task alignment using the haiku/sonnet/opus matrix. Follows the same interactive review pattern as `eval-hooks` and `eval-rules`.

### Changed

- **`eval-hooks` skill updated** (`examples/skills/eval-hooks/SKILL.md`, `~/.claude/skills/eval-hooks/SKILL.md`): fixed event count from 26 to 30 in the scoring criterion; added reference to `hooks-events-reference.md` in the matcher section; added `asyncRewake` edge case.
- **`eval-rules` skill updated** (`examples/skills/eval-rules/SKILL.md`): added user-level rules (`~/.claude/rules/`) to Key Concepts and Step 1 discovery, documented brace expansion support in `paths:` globs, noted symlink support as a named edge case, added `InstructionsLoaded` hook tip for debugging load issues, removed all em dashes from template output examples.
- **`eval-skills` skill updated** (`examples/skills/eval-skills/SKILL.md`): full valid frontmatter table (agentskills.io spec + Claude Code extensions), string substitution placeholder reference, `xhigh`/`max` effort level added to inference engine, scoring raised to 16 pts, removed stale `skills-ref` CLI pre-check section.
- **73 example skills audited and corrected** (`examples/skills/`): removed U+2014 em dashes from ~30 files (hook-enforced ban); removed unsupported `tags:` field from all 7 talk-pipeline sub-skills; fixed `allowed-tools` comma-without-brackets format in 10 files (design-patterns, eval-rules, eval-hooks, plan-pipeline, all 7 talk-pipeline stages); corrected 4 effort mismatches (review-pr and talk-pipeline/orchestrator bumped to `high`, security-check and validate-changes bumped to `medium`); added `when_to_use:` trigger phrasing to 18 skills; added `allowed-tools: Read Grep Glob` to methodology-advisor; scoped `Bash(ccboard*)` on ccboard.

### Fixed

- **Broken URLs corrected across 11 files**: `florian.bruniaux.com/guides` replaced with `cc.bruniaux.com/whitepapers/` in `docs/for-cto.md`, `llms.txt`, `machine-readable/llms.txt`, `machine-readable/reference.yaml`, `mcp-server/content/llms.txt`, `mcp-server/content/reference.yaml`, `CLAUDE.md`, `AGENTS.md`. Also fixed `quiz.html` → `/quiz/` and `cheatsheet.html` → `/cheatsheet/` in all three `llms.txt` files (no Vercel redirect existed for those `.html` paths).

### Documentation

- **Hooks documentation completed and corrected across 6 files**: fixed a factual bug in the lifecycle diagram (`PreToolUse` was labeled `Exit 1: block`, the correct blocking exit code is 2); aligned the hook-event count from 27/19 to 30 across `guide/ultimate-guide.md` §7, `machine-readable/reference.yaml`, `quiz/questions/07-hooks.yaml`, `guide/core/settings-reference.md`, and `examples/hooks/README.md`; added the 3 previously missing events (`PostToolBatch`, `UserPromptExpansion`, `MessageDisplay`) to all event tables; corrected `PreCompact` and `TaskCreated` Can-Block fields (both were marked No, both are Yes); added the `mcp_tool` hook type and the `asyncRewake` field to the §7 type list and the configuration table; added `terminalSequence` to the universal JSON output fields; added a `/hooks` menu description in §7.2; enriched the lifecycle diagram with `PermissionRequest` and `SubagentStop` nodes; updated stale line-number anchors in `reference.yaml`; and extended the `examples/hooks/README.md` events table from 17 to 30 events grouped by category.

- **Ruflo entry refreshed** (`guide/ecosystem/third-party-tools.md`): npm name corrected to `ruflo` (was `claude-flow`), agent counts updated to 98 agents and 30 skills, dual install paths documented (plugin-lite vs full CLI), agent federation section added (zero-trust cross-machine collaboration, absent from the entire guide before this update), plugin marketplace (33 plugins) and web surfaces (flo.ruv.io, goal.ruv.io) noted. Resource evaluation `docs/resource-evaluations/074-ruflo-multi-agent-orchestration.md` updated with a dated English update block reflecting the stable rebrand and federation capability; score revised from 3/5 to 4/5.
- **Claude Code Releases**: Updated tracking to v2.1.158 (2026-05-30)
  - v2.1.158: Auto mode on Bedrock, Vertex, Foundry for Opus 4.7/4.8 (`CLAUDE_CODE_ENABLE_AUTO_MODE=1`)
  - v2.1.157: Plugin auto-loading from `.claude/skills`, `claude plugin init`, mid-session worktree switching, 20+ bug fixes
  - v2.1.156: Opus 4.8 thinking-blocks crash fix (hotfix)
  - v2.1.154: Opus 4.8 with high effort default and fast mode at 2x rate / 2.5x speed
  - v2.1.154: Dynamic workflows — Claude orchestrates tens to hundreds of background agents in one session
  - v2.1.154: Lean system prompt now default for all models except Haiku/Sonnet/Opus 4.7+
  - Breaking (2.1.154): `CLAUDE_CODE_OPUS_4_6_FAST_MODE_OVERRIDE` deprecated (removed 2026-06-01)
  - Breaking (2.1.154): `/simplify` reworked to cleanup-only review
- **Claude Code Releases**: Updated tracking to v2.1.153 (2026-05-28)
  - `/model` now saves as default for new sessions (IDE parity); `s` in picker = current session only
  - `skipLfs` for plugin marketplace git sources; status line commands get `COLUMNS`/`LINES` env vars
  - `claude agents` autocomplete includes built-in skills + slash commands; PR column improvements
  - Breaking: `modelPicker:setAsDefault` keybinding renamed to `modelPicker:thisSessionOnly`
  - 25+ bug fixes including stateful MCP reconnect loop, API gateway credential leak, Agent tool worktree output discard

### Added

- **Real-world token benchmarks in context-engineering.md** (`guide/core/context-engineering.md`, 2026-05-27): New "Real-World Session Benchmarks" subsection in Section 15 with practitioner-sourced data. Per-turn ranges by task type (10-30K simple question, 100-300K feature, 300K-1M+ heavy investigation) and per-session ranges (100-300K quick fix, 500K-2M complete PR, 5M-20M+ long session with compaction). Sourced from community discussion (May 2026, Max 200 / Opus 4.7 at high effort).
- **`claude-crusts` added to observability.md** (`guide/ops/observability.md`, 2026-05-27): Added to external monitoring tools table and decision guide. One-command context pollution scanner by Abinesh-L.
- **`tokens/feature` KPI added to team-metrics.md** (`guide/ops/team-metrics.md`, 2026-05-27): New metric row in AI-specific metrics table. Average tokens consumed per merged feature, crossed with ticket boundaries. Complements tokens/request for team-level reporting.

- **Whitepapers WP12 expanded** (`whitepapers/fr/12-agent-engineering.qmd` and `whitepapers/en/12-agent-engineering.qmd`, 2026-05-27): New section "L'Écosystème des Agents en 2026" / "The Agent Ecosystem in 2026" added to both FR and EN versions. Covers terminal coding agents (Codex CLI, Hermes Agent, Aider), autonomous agents (Devin, SWE-agent, claude -p), multi-agent frameworks (CrewAI, LangGraph, AutoGen/MAF), and a decision matrix with situation-to-tool mapping. Fiche récap updated with a sixth bullet. Cross-ref to guide/ecosystem/agentic-tools.md.

- **New page: Agent Tools Beyond Claude Code** (`guide/ecosystem/agentic-tools.md`, 2026-05-27): Comprehensive coverage of the agent tool field, organized in five sections. Section 1 covers terminal coding agents (Codex CLI at 86K stars, Hermes Agent formerly OpenClaw at 170K stars, Aider at 45K stars, Goose cross-ref). Section 2 covers autonomous coding agents (Devin with cloud sandbox and ACU billing, SWE-agent Princeton NeurIPS 2024, Claude Code headless cross-ref). Section 3 covers multi-agent frameworks (CrewAI 52K stars, LangGraph 33K stars, AutoGen/Microsoft Agent Framework). Section 4 covers orchestration tooling (Conductor Gemini methodology, Conductor Microsoft YAML CLI, Hermes Control Room community template). Section 5 is a decision framework with a full comparison matrix (10 tools across 7 dimensions) and a situation-to-tool guide. Cross-refs added to ai-ecosystem.md (Section 11, Section 11.3), third-party-tools.md (Multi-Agent Orchestration), and guide/README.md navigation.

### Security

- **New section 1.6 in security-hardening.md**: Third-Party Command Wrappers & Shell Interceptors. Covers the attack surface of token-saving wrappers (RTK and similar), shell function overrides (oh-my-zsh plugins), completion frameworks (Fig, Warp), and how to audit each. Includes supply chain hygiene for CLI tools (`brew pin`, `cargo --locked`, checksum verification), minimal shell setup for sensitive sessions, and context separation (no production credentials in agent sessions).

---

## [3.41.0] - 2026-05-27

### Security

- **Threat Database v2.19.0** (`examples/commands/resources/threat-db.yaml`, 2026-05-27): 6 new CVEs, 1 new campaign, 2 new scanning tools
  - CVE-2026-44112/44113/44115/44118 (OpenClaw "Claw Chain": TOCTOU sandbox escape chain, CVSS up to 9.6, fixed in OpenClaw 2026.4.22; 65K-180K servers exposed)
  - CVE-2026-20205 (Splunk MCP Server token disclosure in _internal index logs, CVSS 7.2, fixed in 1.0.3)
  - CVE-2026-2256 (MS-Agent v1.5.2 by ModelScope, regex blacklist bypass in Shell tool enables critical RCE via prompt injection)
  - New campaign: Claw Chain (four chained OpenClaw CVEs for data theft + privilege escalation + persistence)
  - New scanning tools: Aguara (189-rule 100% offline static scanner, GitHub garagon/aguara) and SkillRisk (free browser-based scanner)
  - Updated `minimum_safe_versions`: openclaw bumped from 2026.1.29 to 2026.4.22
  - 8 new sources added

### Documentation

- **Claude Code Releases**: Updated tracking from v2.1.150 to v2.1.152 (2026-05-27)
  - `/code-review --fix` applies review findings to working tree; `/simplify` now invokes it
  - `disallowed-tools` frontmatter for skills/commands; `/reload-skills` command
  - `MessageDisplay` hook event for transforming/hiding assistant message text
  - Auto mode no longer requires opt-in; `--fallback-model` session-level fallback
  - 35+ bug fixes

### Added

- **stacklit, scip-search, lilmd** (`guide/ecosystem/context-engineering-tools.md`, `guide/workflows/search-tools-mastery.md`, 2026-05-27): Three community CLI tools added to the guide. stacklit generates a machine-readable repo index (~250 tokens vs 50K+ for manual exploration) and auto-configures Claude Code/Cursor/Aider; documented in context-engineering-tools.md section 3 alongside RTK/context-mode. scip-search queries pre-built SCIP symbol indexes with millisecond cold starts, no MCP required, worktree-compatible; positioned as a stateless alternative to Serena for CI and ephemeral environments. lilmd provides Markdown TOC with inclusive line ranges for targeted section reads, filling a gap in documentation navigation. Both scip-search and lilmd added to search-tools-mastery.md with decision tree, setup priority, and a new Extended Toolkit section; title updated from "4-Tool Symphony" to "6-Tool Toolkit".

- **Section 2.10 Prompt Engineering Patterns** (`guide/ultimate-guide.md`, new `## 2.10`): Four techniques for closing the gap between well-structured prompts and reliably accurate outputs. Few-shot prompting: message-pair format for tool-use tasks, null-handling example strategy, false-positive calibration with near-miss examples, limits of few-shot vs schema constraints. Validation retry loop: three-attempt budget with per-field error feedback, hallucination cycle detection (`is_hallucination_cycle`), graceful degradation to human review queue. Self-review contamination: 15-30% self-preference bias, independent review instance pattern for high-stakes extraction. Inline reasoning for triage: `reasoning` field in output schema as verification handle, vague reasoning as escalation signal.

- **Section 2.11 Structured Outputs & Schema Design** (`guide/ultimate-guide.md`, new `## 2.11`): Confidence calibration with labeled validation sets, bucket-based accuracy vs confidence measurement (`calibrate_confidence`), per-field review thresholds (vendor 0.70, date 0.80, financial amount 0.95), accuracy vs confidence plot interpretation (Platt scaling for systematic overconfidence/underconfidence). Calibration baseline requires 200+ labeled examples per field for statistically actionable buckets.

- **`context: fork` documentation** (`guide/ultimate-guide.md`, Skills frontmatter table): New row documenting `context: fork` as a CC-only field that runs the skill in an isolated subagent where only the final response returns to the parent context. Documents the known limitation: `context: fork` is ignored when the skill is invoked via the `Skill` tool in agent code and only activates as a slash command.

- **Message Batches API cross-reference** (`guide/ultimate-guide.md`, section 9.9): Added note to Batch Operations intro pointing to `client.messages.batches` for cost-optimized bulk API processing (up to 100 requests, 50% cost reduction vs synchronous).

- Renumbered existing sections: `## 2.10 Data Flow & Privacy` to `## 2.12`, `## 2.11 Under the Hood` to `## 2.13`. TOC and quick-jump line updated accordingly.

- **Anthropic API Patterns for Architects** (`guide/core/architecture.md`, new `## Anthropic API Patterns for Architects`): Three production-critical API patterns. Message Batches API: 50% cost reduction, 24-hour processing window, 100-request batches, per-request error isolation, retry economics at scale, use-case decision matrix (sync vs streaming vs batch). `tool_choice` parameter: four modes (auto/any/specific/none), forced structured output pattern via tool invocation, `stop_reason` guard. Strict mode JSON schema: `output-schema-2025-02-19` beta header, constrained decoding guarantees, nullable fields to prevent hallucination, extensible enums with companion `*_detail` field, `detected_pattern` for auditable classification pipelines.

- **`max_turns` guidance** (`guide/core/architecture.md`, agentic loop section): New `#### Controlling loop depth with max_turns` subsection. Recommended ranges (5 for simple retrieval, 20-30 for research, 50+ for extended workflows), `stop_reason == "max_turns"` check, and rationale for per-task-type configuration in multi-agent pipelines.

- **Attention Mechanics & Reliability** (`guide/core/context-engineering.md`, new `## 17. Attention Mechanics & Reliability`, 238 lines): Lost-in-the-middle mechanics (Liu et al. 2023, arXiv:2307.03172, U-shaped curve, 27% vs 98% NIAH accuracy gap). Primacy/recency placement (sandwich pattern, per-section pass for documents above 50K tokens). Context window size misconception (degradation begins around 50-70K tokens regardless of window size). Persistent facts block (verbatim inclusion, prompt-cache compatible, 500-token ceiling). Scratchpad pattern (synthetic assistant message, programmatic state updates, scratchpad vs rolling summary distinction). Rolling context summaries (65% trigger threshold, facts extraction before summarizing).

- **Production Reliability Patterns** (`guide/workflows/production-reliability.md`, new file, 558 lines): Escalation design (three canonical triggers: explicit request, policy gap, inability to progress), programmatic escalation signals vs LLM confidence scores, frustration vs explicit escalation distinction, rule-based routing from structured output fields. Circuit breaker (CLOSED/OPEN/HALF_OPEN state machine, per-document isolation). Structured error propagation (`StructuredAgentError` with `is_retryable`, `error_category`, `alternative_approach`). Partial results with coverage annotations (`well-supported`/`partially-supported`/`gap`). Structured human handoff (`HandoffPayload` with `recommended_next_action`). Source conflict resolution (temporal difference vs factual conflict, `publication_date` as mandatory field). Anti-patterns section.

- **Advanced Orchestration Patterns** (`guide/workflows/agent-teams.md`, new `## Advanced Orchestration Patterns`, 422 lines): Hub-and-spoke coordinator (coordinator decomposes/dispatches/aggregates, never does domain work). Programmatic prerequisites (state-flag gate, phase-based dispatch with `PipelinePhase` enum). Dynamic subagent selection (`DynamicSelector` with economy/performance/balanced routing). Research space partitioning (explicit topic assignment per agent, exclusion lists). Crash recovery manifest (`PipelineManifest` with `checkpoint()` and `mark_item_complete()`, `RecoverableOrchestrator`). Iterative refinement loop (numeric `target_quality` and `max_iterations` hard budget). Narrow task decomposition (SPEC test: Specific, Programmatically Evaluable, Explicit scope, Constrained).

- **Advanced MCP Tool Design** (`guide/ecosystem/mcp-servers-ecosystem.md`, new `## Advanced MCP Tool Design`, 251 lines): `isRetryable` as application-level convention via `structuredContent` (not native MCP spec). `isError: false` + empty vs `isError: true` semantics table with JSON examples. MCP Resources vs Tools formal comparison (6-dimension table, Python implementation, ResourceLink bridge). Tool naming conflicts with system prompt keywords (naming rules, domain-prefix convention). Task-scoped tool profiles (exploration/analysis/execution phases, role-based access, `verify_fact` subagent pattern).

### Added

- **Memory Systems canonical reference page** (`guide/core/memory-systems.md`, ~2,500 lines): Consolidates all memory content previously scattered across 15+ locations in 6+ files. Covers three tracks: Native Stack (CLAUDE.md, Auto Memory v2.1.59+, Auto Dream, Agent Memory frontmatter, session vs persistent), Cross-Session Tools (claude-mem, agentmemory, ICM, Kairn, doobidoo, OpenMemory MCP, 7 others with master comparison table), and Team Sharing (Trinity pattern, Mem0 Cloud MCP, Zep/Graphiti, Notion MCP approach, structural gap analysis). Adds net-new content not previously in the guide: agentmemory BM25+vector+graph RRF architecture, five architecture patterns, multi-agent coordination patterns (MCP blackboard, leases+signals, A2A), memory poisoning/prompt injection risk (Section 7.1), SAMEP protocol, decision flowchart (Mermaid), 18-row decision matrix, LongMemEval benchmarks, ACT-R decay model, 6 open problems.
  - `machine-readable/reference.yaml`: 30 new entries under `deep_dive:` (memory_systems_guide through memory_systems_open_problems)
  - `guide/README.md`: New row in Core Reference table
  - `guide/learning-path/03-memory.md`: New "Going Further" section (~30 lines) covering Auto Memory, cross-session tools, and team sharing with links
  - `guide/ecosystem/context-engineering-tools.md`: Section 7 updated to point to canonical page, adds three-tier model summary
  - `guide/diagrams/02-context-and-sessions.md`: Memory Hierarchy diagram click URLs updated to memory-systems.md
  - `guide/ultimate-guide.md`: Seven sections reduced to summaries with cross-references (CLAUDE.md memory, Auto Memory + Auto Dream, claude-mem, doobidoo, Kairn, ICM, MCP Memory Stack patterns); two sections (Agent Memory, Session vs Persistent) received "See also" links

### Added

- **Interactive MCP or CLI quiz** (`cc.bruniaux.com/mcp-or-cli/`): 6-question quiz giving a personalized recommendation (MCP-First, CLI-First, or Hybrid Workflow). Scoring weights across six dimensions: user type, auth model, model tier, observability requirements, CLI landscape, and team scale. Results include a match percentage, actionable tips, and a link to the relevant guide section. Added to the More dropdown in the landing nav.

- **"The API wrapper pattern" section** (`guide/ecosystem/mcp-vs-cli.md`): New section clarifying that most production MCP servers wrap existing REST or GraphQL APIs, confirmed by official documentation from Notion ("converted MCP tool calls into HTTP API calls to Notion's public API"), Sentry ("middleware to the upstream Sentry API"), Slack ("a wrapper around an external API, like Slack"), and GitHub ("integrates with GitHub via the GitHub API"). Explains what MCP adds on top of the raw API (OAuth token management, LLM-tuned schemas, centralized hosting, usage attribution) and sharpens the decision criterion: if a service authenticates via API key and you don't need centralized observability, a CLI calling the same API is functionally equivalent.

### Documentation

- **MCP vs CLI guide updated (`guide/ecosystem/mcp-vs-cli.md`)**: Three additions. (1) "Per-server recommendation" table: 18 popular MCP servers each with a concrete verdict (Use MCP / Use CLI / Depends), the named CLI alternative, and a one-line reason. Services with mature CLIs the model knows from training (GitHub, GitLab, git, docker, aws-cli, terraform, semgrep, filesystem) lean CLI. Services requiring OAuth or with no CLI (Sentry, Slack, Notion, Google Drive, Figma, Linear, Context7) lean MCP. Playwright and Kubernetes are context-dependent. Includes a callout linking to the interactive quiz at cc.bruniaux.com/mcp-or-cli/. (2) "MCP vs Skills" section clarifying that skills (markdown workflow instructions) and MCP (execution/auth connectivity) address different layers, not alternatives. OAuth 2.1 subsection explains why MCP is the only option for enterprise SaaS APIs that require browser redirects or server-held refresh tokens. (3) Updated mcp2cli Tooling table entry from watch-list status (1.2K stars, 8 days old) to current state (~1.9K stars, Show HN Best of March 2026, independently benchmarked by Firecrawl/Scalekit/CircleCI). Updated "Last updated" date. Added `mcp-vs-cli.md` pointer block to `machine-readable/reference.yaml` (8 new entries). Added `third_party_mcp2cli_evaluation` and `third_party_mcp2cli_score` to `reference.yaml` (2 previously missing entries).

- **Claude Code Releases**: Updated tracking to v2.1.150
  - v2.1.149: `/usage` per-category breakdown (skills, subagents, plugins, per-MCP-server cost), GFM task list checkboxes render natively, Enterprise `allowAllClaudeAiMcps` setting, two security fixes (PowerShell `cd` permission bypass, sandbox worktree write allowlist), 20+ bug fixes (`/diff` keyboard scrolling, transcript view freeze, slash-command arg hints, `/config` phantom changes, `/insights` crash, otelHeadersHelper path-with-spaces)
  - v2.1.150: Internal infrastructure improvements (no user-facing changes)

### Added

- **Auto mode documentation expanded across 4 files**: Comprehensive update covering two-layer architecture (input probe + Sonnet 4.6 transcript classifier), three classifier categories (scope escalation, untrusted infrastructure, prompt injection), Anthropic's production numbers (94% detection, 17% FNR), independent stress-test findings (arXiv 2604.04978: 81% FNR on adversarial workloads, 92.9% FNR gap on file edits exempt from classification), escalation mechanism (3 consecutive or 20 total blocks), red spinner signal, `autoMode.allow/soft_deny/environment` with `"$defaults"` sentinel, and when-to-use taxonomy.
  - `guide/ultimate-guide.md`: Section rewritten from ~30 to ~80 lines
  - `guide/cheatsheet.md`: Auto mode row added to permission modes table
  - `whitepapers/fr/03-securite.qmd`: New "Mode Auto: délégation et limites réelles" subsection; sandbox Modes bullet fixed (was conflating sandbox auto-allow with auto mode permission feature); PermissionDenied hook updated
  - `whitepapers/en/03-security.qmd`: Same changes in English

- **Pinning Opus 4.6 (Community Hack)** (`guide/ultimate-guide.md`): Added subsection in the OpusPlan Mode area documenting three ways to force Opus 4.6 instead of 4.7 (settings.json direct, OpusPlan hybrid via `ANTHROPIC_DEFAULT_OPUS_MODEL`, per-session `/model`). Documents the trade-offs: losing `xhigh`/`max` effort levels and the newer knowledge cutoff. Added cross-reference from the pricing section.

- **Copilot instructions file** (`.github/copilot-instructions.md`): Points Copilot users to `/CLAUDE.md` as the source of truth and reminds contributors to update `CHANGELOG.md`.
- **YouTube Skills for Claude Code** (`README.md`, `guide/ultimate-guide.md`): Added [youtube-skills](https://github.com/ZeroPointRepo/youtube-skills) to the community resources and Awesome Lists sections — 12 skills for YouTube search, transcripts, chapters, and content analysis.

### Fixed

- **`scripts/generate-guide-exports.sh` — PDF build fails with Typst 0.14+** (`font fallback list must not be empty`). Pandoc's default Typst template leaves `mainfont`/`monofont` empty unless they are set via metadata, and Typst 0.14 made an empty font list a hard error (it was tolerated in 0.13, which is the version bundled with current Quarto on macOS). Added `-V mainfont="Libertinus Serif"` and `-V monofont="DejaVu Sans Mono"` to the `pandoc` invocation — both fonts are available out of the box on macOS and on Ubuntu (`fonts-libertinus` is pulled in by the `pandoc` apt package, `fonts-dejavu` is preinstalled). Verified end-to-end on Ubuntu 25.10 with pandoc 3.1.11 + standalone Typst 0.14.2: PDF builds successfully (556 pages, 8.4 MB) from `guide/ultimate-guide.md` v3.40.0.

### Documentation

- **METR 2026 update integrated in `guide/roles/adoption-approaches.md`**: Added note on METR Study 2 outcome (February 2026, abandoned due to selection bias when 30-50% of participants refused to work without AI). Partial data from the 10 developers common to both studies showed results consistent with Study 1. Newer participants showed a narrower gap (-4%, IC -15% to +9%) and some subgroups improved by up to +18 percentage points relative to Study 1's -19% baseline. METR qualifies this partial data as "very weak evidence." Source: metr.org/blog/2026-02-24-uplift-update/.

- **Agentic Metrics section (new in `guide/ops/team-metrics.md`)**: New section "Agentic Metrics: What DORA Doesn't Measure" covering three metric groups. (1) RCT-verifiable metrics with published baselines: task completion time (METR -19%, arXiv 2507.09089), PR cycle time (DeputyDev -31.8%, arXiv 2509.19708), pass rate with executable test oracle (c-CRAB: Claude Code 32.1%, union of four tools 41.5%, arXiv 2603.23448). (2) Agentic pipeline metrics: spec quality score, validation contract pass rate (Factory.ai Missions), agent task completion rate, code review recall (Code Review Bench Martian: Augment 62.8% recall, Copilot 53.3%, 200,000+ open-source PRs), cost per completed task. (3) Agent governance metrics from Strata Identity Research 2026 and CSA/Zenity 2026 (53% organizations experienced an agent incident in 12 months, 58% took more than 5 hours to detect). Includes the heavy-user review time contradiction (Digital Applied Q1 2026: heavy users spend 14-16h/week reviewing AI-generated code vs 11.4h average), and pass^k pattern for non-deterministic test suites. Table of Contents updated accordingly.

- **Harness Engineer formal framework in `guide/roles/ai-roles.md` (§10)**: Extended the Harness Engineer section with a new subsection documenting the three formal properties from arXiv 2605.18747 "Code as Agent Harness" (May 2026): executability (harness runs and objectively verifies code), inspectability (every agent step is traceable; gen_ai.client stable, gen_ai.agent experimental in OTel GenAI SIG as of May 2026), and statefulness (continuity between sessions and calls). Includes Martin Fowler citation ("A raw model is not an agent. It becomes one when connected to a harness.") and list of the nine prod-grade harness components.

- **Agent Harness Engineering (new page `guide/core/agent-harness.md`)**: New reference page covering the nine-component framework (while-loop engine, context management, tool registry, sub-agent management, built-in skills, session persistence, dynamic prompt assembly, lifecycle hooks, permission enforcement) and the three foundational properties from arXiv 2605.18747 (executability, inspectability, statefulness). Includes the Lethal Trifecta security model (Willison), CI/CD agentic patterns comparison (GitHub Agentic Workflows / AWS Bedrock AgentCore / GitLab Duo), digital twin testing landscape by service (Slack-Mock, Mockoon, WireMock), OTel GenAI observability stack (gen_ai.client stable, gen_ai.agent experimental as of May 2026), test distribution anti-pattern (70% effort on deterministic / <5% on LLM reasoning), and creator-verifier pattern (+12 to +26% correctness improvement). 8 new anchors added to `machine-readable/reference.yaml`.

- **L0-L5 Shapiro Scale in `guide/roles/adoption-approaches.md`**: New section "The L0-L5 Scale: Where Is Your Team?" documenting the six-level framework by Dan Shapiro (CEO Glowforge, January 2026, factorydark.com) with correct attribution. Includes adoption data (Stack Overflow 2025 n=49,000+: 84% declared adoption but 77% don't use vibe coding, 31% use agents — estimated L3+ penetration under 10%), the J-curve from McElheran/Yang/Kroff/Brynjolfsson 2025 (-1.33 TFP point at short-term, Census Bureau data), METR RCT calibration (n=16, 246 tasks, +19% measured slowdown vs -20% perceived, 39-point perception gap), DeputyDev longitudinal cohort (arXiv 2509.19708: 4% month 1, 83% month 6, 60% steady-state, -31.8% PR cycle time), and level-specific investment guidance.

- **Three new roles in `guide/roles/ai-roles.md`**: Added sections 17 (Spec Engineer), 18 (Agent Identity Architect), 19 (AI Eval Engineer) with full responsibilities, required skills, entry paths, and salary estimates. Updated Career Decision Matrix and salary benchmark table. Old sections 17-20 renumbered to 20-23. New roles added to `machine-readable/reference.yaml`.

- **SDD 2026 findings in `guide/workflows/spec-first.md`**: New section "SDD vs TDD vs BDD" with comparative table on governing artifacts, Factory.ai Missions architecture (orchestrator + workers + adversarial validators, 81 problems caught pre-merge on documented Slack clone generating 34% of implementation work), multi-file pass@1 failure rates, and spec drift as the primary open problem.

- **Context Engineering: ACE-v2 operational layer (Sections 10-14)**: Extended `guide/core/context-engineering.md` with five new sections covering the operational mechanisms that close the gap between Level 4 and Level 5 in the maturity model. (1) Signal taxonomy and causal attribution: five-category friction taxonomy (syntactic/semantic/procedural/alignment/performance) replacing the flat `errors × 3 + retries × 2` score, plus a YAML event schema and per-pattern tracking dict. (2) Loop closure: PR-based Curator mechanism generating config-change PRs with diff, canary A/B results, friction evidence, and suggestion escalation; multi-timescale operation (real-time/weekly/quarterly); signal locality trade-offs (local cron vs pushed store vs hosted env). (3) Ejection: automated detection of dormant rules and negative-ROI skills for archival — three heuristics: activation threshold, ROI tracking, profile overlap. (4) Constitutional and self-consistency audits: pre-PR rule conflict check against an explicit `constitution.md`, plus a weekly check verifying that ACE documentation claims match the measured state. (5) Multi-dev profile reconciliation: detection of rules present in more than 50% of individual profiles with hoist-to-shared-config proposals; Bash script included. Old sections 10-12 renumbered to 15-17. ACE disambiguation (vs arXiv:2510.04618 inference-time technique) added to Section 6 and glossary. Five new anchors added to `machine-readable/reference.yaml`. Cross-link added in `guide/roles/ai-roles.md`. Landing `/context-engineering/` updated with ACE Operations category. Landing `/context/` result screen updated with two new deep links.

- **Landing nav and banner**: Replaced "Learning" with "Context" in main nav; reordered More dropdown (AI Roles, Methodologies, Ecosystem, Releases, Compare, Diagrams, Team Metrics, Glossary, FAQ, RSS Feed); updated announcement banner to highlight Agent Harness Engineering, ACE-v2, and new AI roles; fixed banner deep link from `/guide/core/agent-harness` to `/guide/agent-harness/` (guide files served flat by prepare-guide-content.mjs).

- **Quiz category 16 "Agent Harness & Context"**: 35 new questions covering Agent Harness Engineering (9-component framework, Lethal Trifecta, CI/CD patterns, creator-verifier +12 to +26%, Safe Outputs toolchain, OTel GenAI status), Context Engineering (L0-L5 maturity scale, ACE-v2 signal taxonomy, loop closure PR curation, ejection thresholds, constitutional audits, self-consistency check, multi-dev profile reconciliation), and the three new AI roles (Spec Engineer, Agent Identity Architect, AI Eval Engineer). Quiz total 271 to 306 questions.

- **Claude Code Releases**: Updated tracking to v2.1.146 (2026-05-21)
  - v2.1.146: `/simplify` renamed to `/code-review` with optional effort level; auto mode no longer suppresses AskUserQuestion; Windows PowerShell regression fix; 15+ bug fixes
  - v2.1.145: `claude agents --json` for scripting; `/plugin` previews before install; security fix for Bash permission-prompt bypass; MCP paginated resources fix; 20+ bug fixes
  - v2.1.144: /resume lists background sessions alongside interactive ones; /model session-only by default; "extra usage" → "usage credits"; 75s startup hang fixed; 40+ bug fixes

### Changed

- **Commands migrated to skills — redirect stubs + full reference update**: All 51 files in `examples/commands/` are now redirect stubs pointing to their canonical `examples/skills/<name>/SKILL.md` equivalents, following the Claude Code 2.1.3 skills-commands unification. Existing GitHub URLs remain valid. `threat-db.yaml` copied to `examples/skills/update-threat-db/threat-db.yaml` (original kept until MCP server Chantier 2). Updated `machine-readable/reference.yaml` (26 keys), `llms.txt`, `machine-readable/llms.txt`, `README.md`, `scripts/install-templates.sh` (install_command → install_skill redirect + subdir format), `scripts/check-landing-sync.sh` (excludes stubs from template count), `scripts/generate-template-catalog.py`, `scripts/resync-reference-yaml.py`. New script: `scripts/generate-command-stubs.py` (idempotent stub generator). Landing `cc.bruniaux.com`: updated `guide-search-entries.ts` (26 deep links), `learning/index.astro`, `security-data.ts`, `guide-content-entries.ts`, and all template count references (181 → 255). Remaining in Chantier 2: MCP server rebuild + threat-db.yaml original deletion. Remaining in Chantier 3: guide prose, quiz YAML, whitepapers, and `.claude/` internal paths.

- **`tools/audit-prompt.md` updated to v5.2 for CC 2.1.3 skills model**: Dimension 4 fallback bash now counts `.claude/skills/` alongside agents/commands; Dimension 7 workflow detection checks `skills/$cmd/SKILL.md` (both project and global) in addition to `commands/$cmd.md`; security-check install command fixed (output file was `security-check.md`, now correctly `SKILL.md`); Dimension 8 argument-hint note clarifies that skills use `effort:` field instead. Version footer bumped to v5.2.

- **`tools/onboarding-prompt.md` guide line count corrected**: "22K+ lines" → "25K+ lines" to match current `guide/ultimate-guide.md` size.

### Fixed

- **Mass broken-link repair across guide and examples** (`guide/ultimate-guide.md`, `guide/ultimate-guide.fr.md`, `guide/security/security-hardening.md`, `guide/cowork.md`, `guide/ops/observability.md`, `guide/ops/ai-traceability.md`, `guide/ops/devops-sre.md`, `examples/CATALOG.md`, and 15+ additional example files): Fixed 230+ broken internal relative paths caused by guide reorganization from flat structure to nested subdirectories (`guide/roles/`, `guide/core/`, `guide/ecosystem/`, `guide/security/`, `guide/ops/`). Fixes applied: `../core/` refs in `guide/`-root files corrected to `core/`; `../examples/` in `guide/security/` and `guide/ops/` corrected to `../../examples/`; `../../examples/` in `guide/ultimate-guide.md` corrected to `../examples/`; bare `ai-ecosystem.md`, `observability.md`, `production-safety.md`, `sandbox-isolation.md` refs prefixed with their subdirectory; `../guide/` in `examples/agents/` and `examples/plugins/` corrected to `../../guide/`; all 181 CATALOG.md links had `examples/` prefix stripped (file lives in `examples/`); corrupted `](` in `security-hardening.md` MCP safe list footer repaired. Added `https://quarto.org` to `.lycheeignore` to suppress CI network flakiness. Staged `docs/resource-evaluations/2026-05-18-skillsight-packmind.md` to resolve dead internal reference in `third-party-tools.md`.

- **Monthly link checker deployed to cc-copilot-bridge landing** (`cc-copilot-bridge-landing/.github/workflows/link-check.yml`): Monthly cron + `workflow_run` on deploy + `workflow_dispatch` crawling `ccbridge.bruniaux.com`. Validated end-to-end: clean run on first try, zero broken links.

- **Monthly link checker deployed to ccboard landing** (`ccboard-landing/.github/workflows/link-check.yml`): Monthly cron + `workflow_run` on deploy + `workflow_dispatch` crawling `ccboard.bruniaux.com`. Validated end-to-end: clean run on first try, zero broken links.

- **Monthly link checker deployed to portfolio** (`portfolio-florian/.github/workflows/link-check.yml`): Monthly cron + `workflow_dispatch` crawling `florian.bruniaux.com`. No `workflow_run` trigger (Vercel deploy, not trackable from GitHub Actions). Excluded `npmjs.com` (bot-protection 403 false positive). Validated end-to-end: clean run confirms zero broken links.

- **Monthly link checker deployed to cowork landing** (`claude-cowork-guide-landing/.github/workflows/link-check.yml`): Monthly cron (1st of month, 08:00 UTC) crawling `cowork.bruniaux.com`. Triggers on deploy success and `workflow_dispatch`. Fixed one pre-existing 404 in `src/data/i18n.ts` (`01-getting-started.en.md` → `01-getting-started.md`). Validated end-to-end: clean run confirms zero broken links.

- **CI link checker now creates issues on broken links** (`claude-code-ultimate-guide-landing/.github/workflows/link-check.yml`): The lychee step was missing `id: lychee`, so `steps.lychee.outputs.exit_code` was always undefined and the issue-creation condition `null != 0` evaluated to false — broken links were silently ignored. Added `id: lychee` to the step. Validated end-to-end: a deliberate broken link triggered issue #6 automatically, then was removed. At least 5 past "fix broken link" commits confirm this silent failure had real impact.

- **Broken links fixed across guide and FR translation** (`guide/ultimate-guide.md`, `guide/ultimate-guide.fr.md`, `guide/cheatsheet.md`, `guide/ecosystem/mcp-servers-ecosystem.md`, `examples/workflows/database-branch-setup.md`, `examples/config/CONTRIBUTING-ai-disclosure.md`): Fixed 10+ dead URLs detected by the new link checker: `florian.bruniaux.com/guides` redirected to `cc.bruniaux.com/whitepapers/`, `platform.claude.com/docs/model-deprecations` corrected to full path `/docs/en/release-notes/model-deprecations`, `neon.tech/docs/guides/branching` updated to `neon.com/docs/introduction/branching`, `docs.sentry.io/integrations/mcp/` corrected to `docs.sentry.io/product/sentry-mcp/`, and `ai-traceability.md` path fixed. Added `.lycheeignore` for 26 historical dead references that credit real sources. Added HTTP 202 to accepted codes in lychee workflow (europarl.europa.eu returns 202). All fixes applied in both EN and FR translation files.

- **Link checker added to main guide repo** (`.github/workflows/link-check.yml`): Monthly cron (1st of month, 08:00 UTC) scanning `guide/**/*.md` and `examples/**/*.md`. Two-step detection: (1) lychee for HTTP external links — accepts 200, 202, 206, 302, 403, 429; excludes social media, localhost, template patterns, file://; (2) `markdown-link-check` for internal relative file links (pointer errors) — ignores HTTP/anchors since those are already covered. Each step creates its own GitHub issue on failure.

- **Link checker added to StarMapper** (`starmapper/.github/workflows/link-check.yml`): Monthly cron scanning `starmapper.bruniaux.com`. SHA-pinned actions (Dependabot active). Validated via `workflow_dispatch` — clean run confirmed.

### Added

- **Skillsight documented** (`guide/ecosystem/third-party-tools.md`): Added new "Skills Observability" section (#15 in TOC) covering Skillsight (PackmindHub/skillsight, v0.2.1, Apache 2.0) by Cédric Teyton (Packmind). Documents both ingestion modes (OTLP direct push from Claude Code and Loki pull from Grafana Cloud), full settings.json snippet for Claude Code configuration, 5-step setup workflow, and three mandatory deployment caveats (default JWT_SECRET/ADMIN_PASSWORD must be overridden — no boot warning; PUBLIC_BASE_URL required for CORS safety and correct onboarding snippet; Drizzle migrations not automatic at startup). Updated Known Gaps table (skills usage analytics filled), Recommendations by Persona table (team skills adoption row added), and cross-reference to Packmind ContextOps (#076). Resource evaluation: `docs/resource-evaluations/2026-05-18-skillsight-packmind.md` (3/5 — integrate with caveats; promote to 4/5 when boot-time default detection, separate encryption key, and automatic migrations are shipped).

- **`/goal` command documented** (`guide/ultimate-guide.md` §9.17, `guide/cheatsheet.md`, `whitepapers/en/00-series-introduction.qmd`, `whitepapers/en/01-effective-prompts.qmd`, `whitepapers/fr/00-introduction-serie.qmd`, `whitepapers/fr/01-prompts-efficaces.qmd`): Expanded the existing stub into a full deep-dive covering the evaluator model architecture (separate Haiku model, condition-based termination vs `/loop`'s time-based), three-element goal formulation (measurable end state + verification mechanism + constraints), `/goal clear` and `/goal status` management commands, anti-patterns (vague objectives, judgment-heavy tasks, production data), permission boundary clarification, context rot warning (~20 turns), and the Orchestrator + `claude -p` mitigation pattern. Added `/goal` to the agentic capabilities table in both introduction whitepapers (EN + FR). Added `/goal` section to the Automation sections of both `01-effective-prompts` (EN) and `01-prompts-efficaces` (FR), including callout memo entries. Added `/goal` row to the "Features Méconnues" table in the cheatsheet.

- **Graphify internals and skill mechanics documented** (`guide/ecosystem/third-party-tools.md`): Added "Under the hood" table explaining the 7 hidden cache files in `graphify-out/` (`.graphify_ast.json` = tree-sitter AST, `.graphify_chunk_XX.json` = AI-processed batches, `.chunk_manifest_XX.json` = per-chunk file lists for `--update` targeting, `.graphify_semantic.json` = post-dedup embeddings, `cache/` = content hashes). Added `--update` mechanics explanation (hash comparison, per-chunk re-processing, zero API cost for unchanged files). Expanded MCP server section with large-graph guidance (5 MB threshold, skill-only vs MCP token cost tradeoff). Added "How Claude uses the installed skill" section documenting the 3-step resolution order: GRAPH_REPORT.md first, targeted graph.json sections, then MCP tools at scale.

- **Graphify documented** (`guide/ecosystem/third-party-tools.md`): Added new "Knowledge Graph" section (#13 in TOC) covering Graphify (safishamsi/graphify, v0.8.9, MIT, PyPI: `graphifyy`). Documents the full init workflow (`graphify .` → `graphify install --platform claude` → `--update` for incremental rebuilds), the 3 core output files (graph.html, GRAPH_REPORT.md, graph.json), query commands, god nodes/surprising connections/confidence tagging analysis features, MCP server mode, file support across 31 languages plus PDFs/videos, team workflow via committed `graphify-out/`, privacy model (code local via tree-sitter, docs go to AI API), and the double-y PyPI naming trap. Updated frontmatter description, TOC, and Recommendations by Persona table.

- **Step by Token documented** (`guide/ecosystem/ai-ecosystem.md` §16, `guide/roles/learning-with-ai.md`): Added section covering Dimitri Mérault's free 21-chapter interactive guide to LLM mechanics (stepbytoken.com). Covers all 4 parts (model anatomy, training and alignment, production, advanced topics) with a Claude Code-specific chapter relevance table highlighting context windows (ch9), agents and MCP (ch11), prompt engineering (ch12), hallucinations (ch13), extended reasoning/thinking tokens (ch17), and KV cache (ch18). Also added cross-reference link in the External Resources section of the learning-with-ai guide.

- **Four new token/cost tracking tools documented** (`guide/ecosystem/third-party-tools.md`): Added Claude Code Usage Monitor (~7,955 stars, real-time burn-rate predictions, highest-starred tool in category), claude-spend (one-shot `npx claude-spend` check), cc-statistics (cross-agent dashboard covering Claude Code + Gemini CLI + Codex + Cursor), and claude-context-optimizer (context heatmaps, wasted context detection, git-aware ROI reports). Added explanatory note on the Layer 4 billing blind spot: API-level gateways cannot intercept Claude Max/Pro subscription traffic; local file-parsing tools work billing-mode-agnostically.

- **context-mode documented** (`guide/ecosystem/context-engineering-tools.md` §3): New subsection covering context-mode (mksglu/context-mode, ~14,149 stars, ELv2), the MCP server with output sandbox compression, SQLite+FTS5 session tracking with BM25 retrieval post-`/compact`, and the "Think in Code" pattern. Includes comparison with RTK and Headroom. Platform count: 12 supported platforms including Claude Code plugin, Gemini CLI, Cursor, Kiro, Zed.

- **mem0 documented as ICM alternative** (`guide/ecosystem/context-engineering-tools.md` §7): Added mem0 (mem0ai/mem0, ~55,228 stars) as a provider-agnostic, cloud-portable alternative to ICM. Includes decision guide table (ICM vs mem0 by use case), token overhead figure (~10-15%/turn), and architectural differentiation (ICM local-first/Claude-specific vs mem0 multi-provider/portable).

- **KV Cache section expanded with Claude Code-specific prompt caching mechanics** (`guide/ecosystem/context-engineering-tools.md` §8): New subsections covering: KV tensor mechanics (Key-Value matrices in VRAM, ~500MB-1GB for 100K-token Opus prefix), Claude Code request ordering (system prompt, tool definitions, CLAUDE.md as message content, conversation history), rationale for CLAUDE.md placement (shared system prompt cache across all users), production 96% hit rate, cache anti-patterns (timestamps in system prompt, mid-session tool changes), Plan Mode cache-stable design (EnterPlanMode/ExitPlanMode rather than removing tools), and compaction vs `/clear` cache continuity. Added "Self-Hosted KV Cache Infrastructure" subsection header to separate Claude-specific content from vLLM/SGLang content.

- **"Think in Code" pattern documented** (`guide/core/context-engineering.md` §8): New named subsection covering the pattern coined by context-mode v1.0.64 and independently described by Contieri as "Ask for the Analyst, Not the Analysis." Documents the problem (30+ file reads for an exploratory task), the pattern (write and run a script, read only the result), three bash examples, when to apply it, and relationship to sub-agents.

- **Graduated Context Offloading documented** (`guide/core/context-engineering.md` §8): New named subsection covering the three-tier cascade from LangGraph's Deep Agents SDK: Tier 1 (large tool outputs over 20K tokens offloaded to filesystem with path+preview injected), Tier 2 (accumulated tool call arguments dropped when context hits mid-point), Tier 3 (lossy message history summarization as last resort). Includes Claude Code-equivalent PostToolUse hook implementation in Python that transparently intercepts large bash outputs and writes them to temp files. Summary table and highest-leverage sequence updated to include both new patterns.

- **MECW (Maximum Effective Context Window) documented** (`guide/core/context-engineering.md` §2): New subsection establishing that the effective ceiling is approximately 92% of the advertised limit (185K for Claude Opus 4's 200K window) before accuracy degrades. Covers the context rot mechanism (30%+ degradation in mid-window positions), the signal-to-noise argument against naive 1M window reliance, and planning targets per model.

- **lean-ctx section rewritten with measured benchmarks** (`guide/ecosystem/third-party-tools.md`): Replaced simulated benchmark figures with measured data from a TypeScript/T3 monorepo (2455 files, 7063-node graph): 57.8% overall compression, 86% savings rate on ctx_read, schema.prisma 2364L → ~200 tokens (99%), cache re-reads at 13 tokens. Updated install command to the official curl script + `lean-ctx setup`. Added RTK vs lean-ctx two-layer comparison table (RTK = CLI output, lean-ctx = file reads + session memory), monitoring commands, and cross-reference to context-engineering.md §12. Replaced Caution warning with a measured maintenance note.

- **Token Compression Tools section added** (`guide/core/context-engineering.md` §12): New section covering the two-layer token compression stack for Claude Code. Layer 1 (RTK): CLI output compression via PreToolUse hook, 60-90% savings on git/cargo/npm. Layer 2 (lean-ctx): file read compression via tree-sitter AST, 10 ctx_read modes with selection guide (signatures/map/full/diff/lines:N-M), cache mechanics, CCP cross-session memory, and measured benchmarks. Includes savings distribution table (85% of lean-ctx savings from file reads vs <1% from shell), per-mode guidance for when to use each, and decision criteria by project type. TOC updated to add §11 Research Patterns and §12 Token Compression Tools.

- **lean-ctx referenced in machine-readable index** (`machine-readable/reference.yaml`): Added 5-key entry for lean-ctx (yvgude/lean-ctx, 1 366 stars) under Third-Party Tools — local-first Rust CLI for context compression (60-95% token reduction claimed). Status: watch list, not yet integrated (breaking changes frequent, recent security fixes). Most direct RTK competitor identified in the context engineering tool landscape.
- **mcp2cli referenced in machine-readable index** (`machine-readable/reference.yaml`): Added 5-key entry for mcp2cli (knowsuchagency/mcp2cli, ~1 900 stars, Show HN Best March 2026) — CLI bridge that lazy-loads MCP/OpenAPI/GraphQL tool schemas so LLM context only receives tool list and on-demand help strings instead of full schema injection each turn. 96-99% schema-token reduction benchmarked independently by Firecrawl, Scalekit, and CircleCI. Key nuance: 4+ unrelated forks share the same name; knowsuchagency is the reference implementation. Scoped to dev/single-tenant; not a replacement for enterprise MCP gateways with per-user OAuth and audit logs.
- **Context Compression section added to Third-Party Tools** (`guide/ecosystem/third-party-tools.md`): New section between Token & Cost Tracking and Session Management, documenting lean-ctx (4-dimension Rust compression CLI: file read modes, shell modules, CCP session cache, SQLite property graph; watch-list status with caveats) and mcp2cli (Python CLI bridge solving MCP schema injection via lazy loading; independently benchmarked 32× token reduction on GitHub MCP server; naming collision warning for the 4+ unrelated forks). Table of Contents and frontmatter description updated.

### Changed

- **Skills–Commands unification (CC 2.1.3)**: All educational content updated to reflect that `.claude/commands/` is merged into `.claude/skills/`. The 3-way Agent/Skill/Command model is now a 2-way Agent/Skill model with invocation modes (`disable-model-invocation: true` for user-only, default for model-invocable). Affected: `guide/cheatsheet.md`, `guide/ultimate-guide.md` §5/§6, `whitepapers/fr+en` WP02/04/07, recap cards c04/m09/m10/01-commandes (FR+EN), landing docs mirrors, landing Q&A, machine-readable index. New editorial reference: `claudedocs/pedagogy-skills-merger.md`.

### Security

- **Threat database updated to v2.18.0** (`examples/commands/resources/threat-db.yaml`, `guide/security/security-hardening.md`): 7 new entries covering threats discovered after 2026-05-11:
  - **CVE-2026-42559** (RMCP Rust SDK DNS rebinding, CVSS 8.8, fixed in 1.4.0) — official Rust SDK for MCP lacked Host header validation, enabling DNS rebinding attacks; fixed in rmcp 1.4.0 (2026-05-14)
  - **CVE-2026-35568** (MCP Java SDK DNS rebinding, CVSS 7.6 v4, fixed in 1.0.0) — Java SDK variant of the same DNS rebinding class affecting all official SDK implementations
  - **CVE-2026-39313** (mcp-framework HTTP DoS, CWE-770, fixed in 0.2.22) — unlimited request body size in mcp-framework HTTP transport allows single-request memory exhaustion crash by unauthenticated attacker
  - **CVE-2026-25723** (Claude Code file-write sandbox bypass, fixed in 2.0.55) — piped sed/echo commands escaped project sandbox due to missing command-chain validation
  - **CVE-2026-33068** (Claude Code permission mode bypass, fixed in 2.1.53) — settings.json resolved before workspace trust dialog, allowing `bypassPermissions` to auto-approve all tool calls from malicious repos
  - **ADVISORY-CC-2026-002** (Claude Code 50-subcommand deny-rule bypass, fixed in 2.1.90) — all configured deny rules silently dropped when command chain exceeded 50 subcommands; discovered by Adversa after Claude Code source briefly exposed on npm
  - **T030 TrustFall** (Adversa, 2026-05-08) — malicious repos with crafted .claude/settings.json or .mcp.json auto-spawn attacker MCP servers when developer accepts folder trust dialog; affects Claude Code, Gemini CLI, Cursor CLI, Copilot CLI; Anthropic declined to fix
  - Updated `minimum_safe_versions`: claude-code 2.1.34 → **2.1.90**, added rmcp 1.4.0, mcp-java-sdk 1.0.0, mcp-framework 0.2.22
  - Added 7 new sources: CVE-2026-42559, CVE-2026-35568, CVE-2026-39313, VentureBeat six-exploits article, Adversa TrustFall, AWS+Cisco MCP security blog

### Documentation

- **Four new guide sections: agentic SDK vocabulary, MCP error taxonomy, tool description patterns, context research patterns**:
  - **Agentic Loop API Vocabulary** (`guide/core/architecture.md` §1): new subsection naming `stop_reason` values (`end_turn`, `tool_use`, `max_tokens`) with loop pseudocode showing how each state maps to loop control flow, `tool_use` block structure (`id`, `name`, `input`), and `fork_session` explained as independent branch pattern analogous to git branching
  - **Hub-and-Spoke Orchestration** (`guide/core/architecture.md` §4): new subsection covering the dominant multi-agent pattern with ASCII diagram, coordinator responsibilities (decompose, pass context explicitly, aggregate, decide cross-cutting questions), worker isolation properties, and the critical rule that context is never inherited automatically between sub-agents — includes correct vs incorrect parallel task design example
  - **MCP Error Handling & Reliability** (`guide/ecosystem/mcp-servers-ecosystem.md` Production Deployment §): new subsection covering the `isError` flag (why returning `isError: true` matters vs plain error strings), four-category error taxonomy (transient/validation/business/permission) with recovery strategies per category, and Python implementation pattern with explicit category tagging
  - **MCP Tool Description Design Patterns** (`guide/ecosystem/mcp-servers-ecosystem.md` Production Deployment §): new subsection covering overlapping-description misrouting with bad/good examples, three-part description anatomy (what/what-input/decision-boundary), naming convention table (verb vs noun vs scope vs granularity suffixes), anti-patterns (generic verbs, missing boundary, boolean flags that change semantics), and `input_examples` as complement to descriptions
  - **Research Patterns: What the Literature Shows** (`guide/core/context-engineering.md` §11): new numbered section covering four research findings — Lost-in-the-Middle effect (Liu et al. 2023, Stanford) with practical positioning implications, progressive summarization risks (silent confidence with degrading accuracy, 2-pass limit recommendation), stratified sampling for calibration (stratum table by context length and instruction density), and claim-source mapping for provenance tracking in multi-step agents

- **Claude Code Releases**: Updated tracking to v2.1.143 (from v2.1.141)
  - v2.1.143: Plugin dependency enforcement (claude plugin disable/enable with transitive deps), projected context cost in /plugin marketplace, worktree.bgIsolation: "none" setting, PowerShell -ExecutionPolicy Bypass by default, stop hook block cap (warns after 8 blocks), 30+ bug fixes
  - v2.1.142: Fast mode upgraded to Opus 4.7 by default, new claude agents dispatch flags (--add-dir, --settings, --mcp-config, --model, --effort, --permission-mode), root-level SKILL.md plugin surfacing, /plugin shows LSP servers, MCP_TOOL_TIMEOUT fix for remote servers, daemon cleanup on brew upgrade, 25+ bug fixes

- **claude-red offensive security skill library documented** (`guide/ultimate-guide.md` §Skills): new subsection "claude-red: Offensive Security Skill Library" covering SnailSploit/Claude-Red (58 skills across 13 attack surface categories). Documents three usage patterns — direct session read, `--system-file` at launch, and project-level `.claude/skills/` symlink — with emphasis on the one-shot no-install approach. Introduces the targeted prompt pattern for matching skills to a specific tech stack (Next.js/Prisma/Clerk example), and includes ethical/legal scope note.

- **Skills and Subagents section added to guide** (`guide/ultimate-guide.md` §5.1): new subsection "Skills and Subagents" documenting that subagents don't inherit skills automatically, built-in agents (Explorer, Plan, Verify) can't access skills at all, custom subagents need explicit `skills:` frontmatter field, and skills load at agent start (not on-demand). Includes frontmatter example. Based on Anthropic certification course module 05.

- **examples/skills — frontmatter cleanup (15 skills)**: added missing `allowed-tools` to guide-recap, issue-triage, landing-page-generator, pr-triage, release-notes-generator, skill-creator, cyber-defense-team, ccboard, rtk-optimizer; removed unsupported fields (`tags`, `category`, `keywords`, `context`, `agent`, `usage`, `args`) from ccboard, issue-triage, landing-page-generator, pr-triage, release-notes-generator, skill-creator, rtk-optimizer, token-audit, voice-refine, audit-agents-skills, mcp-integration-reference; fixed YAML list format (comma-separated → space-delimited) in git-ai-archaeology and audit-agents-skills; added `effort: medium` to git-ai-archaeology; moved `version` to `metadata.version` in rtk-optimizer, cyber-defense-team, audit-agents-skills, mcp-integration-reference. Note: `token-audit/skill.md` uses lowercase filename — spec requires exactly `SKILL.md`.

- **eval-skills improved** (`examples/skills/eval-skills/SKILL.md`): added `argument-hint` to frontmatter, fixed `allowed-tools` format (comma-separated → space-delimited), added "Pre-Check" section documenting `skills-ref validate` CLI, added complete list of valid vs unsupported frontmatter fields, added note about `allowed-tools` format requirement, added `model` as a valid Claude Code extension field, fixed per-skill output template from `/15` to `/14`.

- **Anthropic programmatic billing split documented** (`guide/ultimate-guide.md` §9.13, §9.3, §2.2, §10.4; `machine-readable/reference.yaml`): new section covering the June 15, 2026 billing change that separates interactive and programmatic usage into distinct buckets. Documents affected tools (`claude -p`, Agent SDK, GitHub Actions, third-party harnesses), credit amounts per plan, the `ANTHROPIC_API_KEY` billing trap, pre-June-15 audit steps, and decision framework for teams running automated workflows. Cross-references added in §2.2 (Cost Awareness), §9.3 (CI/CD), and §10.4 (Troubleshooting). 13 new entries in `reference.yaml`.

- **Agent Skills open standard — platform count corrected to 35+** (`machine-readable/reference.yaml`, `guide/ultimate-guide.md:7602`): updated from stale "26+" / "30+" counts based on official agentskills.io client showcase verified 2026-05-14 (35 named tools: added OpenHands, Amp, Letta, Junie, Firebender, OpenCode, Mux, Kiro, Snowflake Cortex Code, Ona, Laravel Boost, Emdash, TRAE, fast-agent, nanobot, VT Code, Qodo, Agentman, Mistral Vibe, Workshop, Command Code, pi, Piebald, Google AI Edge Gallery)

- **Claude Code releases updated to v2.1.141** (`machine-readable/claude-code-releases.yaml`, `guide/core/claude-code-releases.md`):
  - v2.1.141: hook `terminalSequence` output field, `claude agents --cwd`, Rewind "Summarize up to here", `CLAUDE_CODE_PLUGIN_PREFER_HTTPS`, `ANTHROPIC_WORKSPACE_ID`, 50+ bug fixes
  - v2.1.140: `Agent` tool `subagent_type` case/separator-insensitive matching, plugin folder conflict warnings, 13 bug fixes

### Security

- **Threat database updated to v2.17.0** (2026-05-11): +10 new sources, +6 new CVEs, +2 new attack techniques, +1 defensive resource
  - New CVEs: CVE-2025-66335 (Apache Doris MCP SQL injection), CVE-2025-53107 (Git MCP Server command injection), CVE-2026-22252 (LibreChat STDIO RCE), CVE-2026-22688 (WeKnora STDIO RCE), CVE-2025-54994 (@akoskm/create-mcp-server-stdio RCE), CVE-2026-26030 (Microsoft AI agent framework tool-chaining RCE)
  - New attack techniques: T028 (Zero-Click RCE via Prompt Injection — Cymulate, Cursor/AWS Kiro/Codex), T029 (AGENTS.md Supply Chain File Injection — NVIDIA research)
  - New sources: Cymulate Zero-Click RCE research (May 2026), Microsoft "Prompts Become Shells" blog (CVE-2026-26030), NVIDIA AGENTS.md injection, OX Security full STDIO CVE advisory, Forcepoint X-Labs IPI payloads, Stormshield retrospective
  - New defensive resource: OWASP Agentic AI Skills Top 10 GitHub project

### Documentation

- **Recap cards synced to guide v3.40.0** (Track C): mass version bump 3.38.1 to 3.40.0 across all 109 recap cards (52 FR + 52 EN c/m/t series, 5 EN old-format). Priority content additions to 5 cards (m09, m11, m12, m13, t12 FR+EN): /goal, /scroll-speed, hook exec form args[], continueOnBlock, PostToolUse updatedToolOutput, worktree.baseRef breaking change, alwaysLoad MCP option. Whitepapers WP09+WP10 (FR+EN) version bump 3.38.1 to 3.40.0.

- **Feature backfill v2.1.120-v2.1.139** (`guide/ultimate-guide.md`, `guide/cheatsheet.md`, `machine-readable/reference.yaml`): documented 21 missing features from 6 weeks of releases:
  - Hooks: `args[]` exec form, `continueOnBlock` (PostToolUse), `effort.level`/`$CLAUDE_EFFORT` in stdin JSON, `hookSpecificOutput.updatedToolOutput` for all tools (was MCP-only)
  - Skills: `${CLAUDE_EFFORT}` variable in skill content
  - Worktrees: `worktree.baseRef` (`fresh`|`head`) with breaking change notice (v2.1.133)
  - MCP: `alwaysLoad` server config option, `CLAUDE_PROJECT_DIR` env injection
  - Auto mode: `settings.autoMode.hard_deny` unconditional block rules
  - CLI: `/goal`, `/scroll-speed` commands; `claude project purge`, `claude ultrareview CI`, `claude plugin prune/details`; `--plugin-url`, `--channels` console auth, `--plugin-dir .zip`
  - Env vars: `CLAUDE_CODE_SESSION_ID`, `CLAUDE_CODE_DISABLE_ALTERNATE_SCREEN`, `CLAUDE_CODE_PACKAGE_MANAGER_AUTO_UPDATE`

- **Agent View documented** (§9.17, `guide/ultimate-guide.md`): added native session manager introduced in v2.1.139 — `claude agents`, `/bg`, `claude --bg [task]`, peek + inline reply. Contextualized vs tmux/Conductor/third-party tools. Updated `claude agents` subcommand description in CLI reference.

- **Piebald added** (`guide/ecosystem/third-party-tools.md`): new entry in "Alternative UIs" section — cross-platform (Windows/macOS/Linux/Web), free, multi-provider (Claude/Copilot/Bedrock/Qwen), explicit hooks + AGENTS.md compatibility. Added cross-ref in Multi-Agent Orchestration table. Covers the Windows GUI gap absent from all other listed tools.

- **Claude Code Releases**: Updated tracking to v2.1.139 (2026-05-12)
  - v2.1.139: Agent view (Research Preview), /goal command, hook args exec form + continueOnBlock, 40+ bug fixes
  - v2.1.137: [VSCode] Fixed extension failing to activate on Windows
  - v2.1.136: settings.autoMode.hard_deny for unconditional auto mode blocking rules; CLAUDE_CODE_ENABLE_FEEDBACK_SURVEY_FOR_OTEL for enterprises; fixed MCP servers disappearing after /clear in VS Code/JetBrains/Agent SDK; MCP OAuth concurrent refresh token race fixed; 40+ UI/terminal fixes (plan mode write blocking, extended thinking 400 fix, --resume with underscores, WSL2 image paste fallback)

- **§9.25 Harness Engineering extended**: added §9.25.1 through §9.25.5 covering OpenAI Codex team patterns: AGENTS.md as ~100-line TOC, knowledge boundary principle ("what the agent can't see doesn't exist"), docs/ knowledge base structure with exec plans and doc-gardening agent, ephemeral per-worktree observability stack, taste invariants with agent-readable linter messages, anti-entropy via background cleanup agents with QUALITY_SCORE.md, layered domain architecture enforced by linters (Types→Config→Repo→Service→Runtime→UI), and high-throughput merge philosophy. Source: Ryan Lopopolo, OpenAI Engineering blog, Feb 11, 2026. Resource evaluation: `docs/resource-evaluations/2026-02-11-openai-harness-engineering.md` (score 5/5).

- **Claude Code Releases**: Updated tracking to v2.1.133 (2026-05-08)
  - v2.1.133: worktree.baseRef setting (fresh|head) — default fresh reverts 2.1.128 EnterWorktree behavior (breaking), hooks receive effort level via effort.level JSON + $CLAUDE_EFFORT, subagent skills discovery fix, parallel sessions 401 race fix, MCP OAuth proxy fix
  - v2.1.132: CLAUDE_CODE_SESSION_ID in Bash subprocess env, CLAUDE_CODE_DISABLE_ALTERNATE_SCREEN opt-out, MCP stdio memory growth fix (10GB+ RSS), 20+ terminal/TUI fixes (SIGINT shutdown, --resume emoji crash, fullscreen blank, JetBrains scroll, mouse wheel speed, / paste swallow, context_window counts, Alt+T macOS, MCP 0-tool silent failure)
- **Claude Code Releases**: Updated tracking to v2.1.131 (2026-05-06)
  - v2.1.131: VS Code extension Windows activation fix (hardcoded createRequire build path), Mantle auth fix (missing x-api-key header)
  - v2.1.129: --plugin-url flag for session-scoped plugin .zip from URL, CLAUDE_CODE_PACKAGE_MANAGER_AUTO_UPDATE for Homebrew/WinGet, Ctrl+R all-projects history restored (pre-2.1.124), skillOverrides setting now works
  - v2.1.129: 1h cache TTL downgrade fix, OAuth refresh race fix, Bash(mkdir *) allow rules fix, /context token waste fix (~1.6k per call), 20+ additional bug fixes
- **Claude Code Releases**: Updated tracking to v2.1.128 (2026-05-05)
  - EnterWorktree creates branch from local HEAD — unpushed commits no longer dropped
  - --plugin-dir accepts .zip plugin archives; --channels works with console (API key) auth
  - /mcp shows tool count per server; parallel bash tool call fix (failing read-only no longer cancels siblings)
  - Sub-agent prompt cache fix (~3x cache_creation reduction); 1M-context false "Prompt is too long" fixed
  - 35+ additional bug fixes (MCP stdio corrupted args, MCP images dropped, clipboard whitespace)

- **New tool: Spec Completeness Audit** — `tools/spec-completeness-audit.md`, self-contained prompt auditing how well a project is specified for safe agent delegation. Scores /100 across 5 layers (Behavioral 15pts, Interface 20pts, Architectural 30pts, Lifecycle 20pts, Cultural 15pts). Layer 3 weighted highest (most commonly missing, hardest to detect). Output: per-layer risk tier 🟢/🟡/🔴, silent-fill prediction ("what the agent will invent"), delegation verdict (Safe/Supervised/Risky/Unsafe), and 3 quick wins with templates. Based on Hamidreza Saghir's "Your coding agent is under-specified" (May 2026). `tools/README.md` updated.

- **New tool documentation: Graphify** — added `### Graphify (Codebase Knowledge Graphs)` section in §8.2 (after claude-mem). Covers: three-pass extraction (AST local + faster-whisper + Claude subagents), Leiden clustering, `graphify-out/` output structure, install commands, team git workflow, comparison vs GrepAI and vs claude-mem. Decision Matrix updated to 5-layer stack (added Layer 2: Structural Graph → Graphify). Stats: 42K stars, MIT, v0.7.4. Token efficiency claims flagged as self-reported/unverified. Source: github.com/safishamsi/graphify.

- **New tool documentation: Caveman** — added `### Caveman (Compressed AI Responses)` section in §9.13 Cost Optimization (before RTK section). Covers: 4 compression modes (lite/full/ultra/wenyan), install via plugin marketplace or curl installer, companion tools (caveman-compress, caveman-commit, caveman-review, caveman-stats, caveman-shrink), honest token numbers (4-10% whole-session savings vs 75% prose-only claim), when not to use. Stats: 53K stars, MIT, created 2026-04-04. Source: github.com/juliusbrussee/caveman.

- **Harness engineering concepts integrated from Learn Harness Engineering course (HumanLayer/Anthropic, 2026)**: three new sections across existing workflow files, two new templates, two cross-reference notes
  - `guide/workflows/spec-first.md`: new subsection "Feature List: Machine-Readable Scope Control" — triple structure (behavior, shell verify command, state), one-way state machine (not_started → active → blocked → passing), WIP=1 rule, evidence field, connection to handoff pattern
  - `guide/workflows/tdd-with-claude.md`: new subsection "The Verification Gap" — failure mode where agent declares done before verification, three-layer stack (lint/tests/e2e), independent evaluator principle, Anthropic game experiment citation (https://www.anthropic.com/engineering/harness-design-long-running-apps)
  - `guide/workflows/task-management.md`: new section "Session Lifecycle Protocol" — 10-step table (START through HANDOFF), progress.md as continuity artifact with inline template, connection to existing handoff triad
  - `guide/core/methodologies.md`: one-sentence cross-ref added after Verification Loops callout
  - `guide/security/production-safety.md`: one-sentence cross-ref added after Verification Paradox
  - New templates: `examples/workflows/feature-list.json`, `examples/hooks/bash/verification-gate.sh`
  - Claims: only VERIFIED sources cited (Anthropic engineering blog, OpenAI harness-engineering post); illustrative percentages from course dropped

- **New section §9.25 Harness Engineering**: five-subsystem model (Instructions, Tools, Environment, State, Feedback), verification gap pattern, WIP=1 principle, 10-step session lifecycle, feature_list.json schema with evidence field, init.sh bootstrap contract, progress.md session handoff. Source: Learn Harness Engineering (HumanLayer, 2026). TOC updated (also adds 9.23 and 9.24 entries that were missing). Templates: `examples/templates/feature-list.json`, `examples/claude-md/agent-progress.md`.

- **Whitepapers P2 polish** (FR + EN): WP00, WP06 final consistency pass
  - WP00 (Introduction): "9 whitepapers" → "12 livres blancs / 12 technical whitepapers" (body now matches footer); Peak Hours callout added (March 2026, faster drain 5am–11am PT weekdays); /ultrareview updated to v2.1.114+ with CI subcommand note; /usage added to essential commands list
  - WP06 (Privacy): ZDR local cache caveat added (cache may persist 30 days locally despite 0-day server retention); Constitutional AI governance section added (priority table: safe > ethical > Anthropic compliance > helpful, with team implications)

- **Whitepapers P1 major features update** (FR + EN): WP04, WP01, WP02, WP05, WP08 updated
  - WP04 (Architecture): bfs/ugrep replace Glob/Grep in native builds (v2.1.117); hook `type: "mcp_tool"` integration (v2.1.118); Triple Harness Incident postmortem (march-april 2026) callout; wp-version 1.1.0→1.2.0
  - WP01 (Effective Prompts): 9 new commands added — /proactive, /team-onboarding, /undo, /recap, /reload-plugins, /tui, /focus, /keybindings, /terminal-setup; `claude project purge` CLI subcommand
  - WP02 (Customization): alwaysLoad MCP config (v2.1.121); /config persistence to ~/.claude/settings.json (v2.1.119); ${CLAUDE_EFFORT} skill variable (v2.1.120); custom named themes (v2.1.118); type: "mcp_tool" hooks; PostToolUse output replacement (v2.1.121); version 3.38.1→3.40.0, wp-version 1.1.0→1.2.0
  - WP05 (Team): claude ultrareview CI subcommand (v2.1.120); ${CLAUDE_EFFORT} in team skills; PostToolUse output replacement for observability; version 3.38.1→3.40.0, wp-version 1.3.0→1.4.0
  - WP07 (Reference Guide): same 9 new commands + claude project purge added to commands tables
  - WP08 (Agent Teams): Opus 4.6→4.7 (7 targeted updates); API change: Agent tool no longer accepts `resume` → use SendMessage({to: agentId}); /branch (v2.1.78+) documented; /ultrareview as managed review alternative; stability fixes (v2.1.114 permission dialog crash, v2.1.121 memory leaks); version 3.38.1→3.40.0, wp-version 1.3.0→1.4.0

- **Whitepapers P0 critical update** (FR + EN): WP06, WP03, WP07 updated for factual accuracy
  - WP06 (Privacy): Risk 6 added (Claude Desktop silent native messaging host install — Chrome/Brave/Edge/Arc, GitHub #53864/#51949); Risk 4 added (`/bug` sends full conversation, 5-year retention, `DISABLE_BUG_COMMAND=1`); existing Risk 4 renumbered to Risk 5; 4-tier retention model (Consumer/Opt-out/Team+Enterprise+API/ZDR); encryption-at-rest disclosure + HIPAA BAA note; 3-destination data flow (Anthropic/Statsig/Sentry) with opt-out env vars; version 3.38.1 → 3.40.0, wp-version 1.1.0 → 1.2.0
  - WP03 (Security): threat-db version reference v2.1.0 → v2.16.0; "Menaces Récentes" section updated v2.11.0→v2.16.0 with T010-T027 attack techniques and 10 new CVEs (CVE-2026-0755, CVE-2026-25725, CVE-2026-25253, CVE-2025-35028, CVE-2025-15061, CVE-2026-3484, CVE-2026-33032, ADVISORY-MCP-STDIO-2026-001, CVE-2025-69256, CVE-2026-6494)
  - WP07 (Reference Guide): `/effort` levels corrected (was `low/medium/high/xhigh`, now `xlow/low/default/high/xhigh/max`); `/usage` added to commands tables (v2.1.118); `/cost` and `/stats` annotated as aliases for `/usage`

- **Whitepapers updated** (FR + EN): WP00, WP01, WP03, WP04, WP07 updated for v3.40.0 content
  - WP00 (Introduction): agentic capabilities table — added Auto mode Max, `/ultrareview`, xhigh effort Opus 4.7 rows
  - WP01 (Effective Prompts): slash commands table — added `/ultrareview` and `/less-permission-prompts`; glob pattern behavior note; plan file naming note in Decision Tree; Memo callout updated
  - WP03 (Security): v2.1.111 glob pattern behavior (read-only no longer prompts); `/less-permission-prompts` allowlist workflow; Auto mode flag removal note
  - WP04 (Architecture): new "xhigh effort level" subsection (FR + EN); comparison table updated for Opus 4.7 as flagship
  - WP07 (Reference Guide): effort enum updated to include xhigh; `/effort` command table extended; new commands table rows for `/ultrareview` and `/less-permission-prompts`; permission modes callout updated; footer updated

---

## [3.40.0] - 2026-05-03

### Soft Flurry consistency pass

- **Deprecated commands annotated** : `/cost` and `/stats` annotated as aliases for `/usage` (v2.1.118) across guide top-level, cheatsheets cards, recap cards, and machine-readable files. Not removed — preserves backward compatibility for users still typing `/cost`.
- **Counters harmonized** : templates (181 per CATALOG.md generator), quiz (271), CVEs (28+ per Threat DB v2.15.0), malicious skills (655), Mermaid diagrams (real count). Single source of truth: `examples/CATALOG.md` for templates, Threat DB for CVEs.
- **Opus 4.7 + xhigh propagated** : targeted edits in ultimate-guide.md, diagrams, landing components, and cheatsheets cards.
- **Threat DB v2.15.0 propagated** : `src/data/security-data.ts` in landing site updated with version, 5+ new CVEs (CVE-2026-30623, CVE-2026-40933, CVE-2026-33224, CVE-2025-69256, CVE-2026-6494, CVE-2026-33032), attack techniques T026 and T027.
- **Broken `threat-db.yaml` link fixed** : README was pointing to `machine-readable/threat-db.yaml` (non-existent); corrected to `examples/commands/resources/threat-db.yaml`.
- **3 SoT files resynchronized** : `CLAUDE.md` (VERSION 3.34.1 → 3.40.0), `llms-full.txt` (embedded cheatsheet block 3.34.4 → 3.40.0), `reference.yaml` (updated date).
- **Recap cards rebuilt** : 5 delivered cards (01, 03, 04, 06, 25) updated + wp-version bumped minor + PDFs regenerated.
- **Announcement banner** : BANNER_ID bumped to reset dismissed state for all visitors, new message highlighting Routines + Opus 4.7.
- **9 new commands added** to machine-readable index: `/usage`, `/recap`, `/effort`, `/tui`, `/focus`, `/less-permission-prompts`, `/ultrareview`, `/proactive`, `/undo`.

- **Security**: Updated threat database to v2.16.0 (2026-05-03)
  - 6 new CVEs: CVE-2026-35021 (Claude Code CLI command injection), CVE-2026-39861 (Claude Code RCE, Sonar research), CVE-2026-30625 (Upsonic RCE), CVE-2026-7593 (command-executor-mcp 0-day), CVE-2026-7591 (astro-mcp-server), CVE-2026-5059 (aws-mcp-server second 0-day)
  - 2 new campaigns: ClawHub Crypto Swarm (30 skills hijacking agents as $FLY miners), Hugging Face + ClawHub malware via indirect prompt injection
  - 1 new scanning tool: Cisco AI Agent Security Scanner for IDEs (VS Code extension, April 21)
  - 12 new sources, 3 new minimum_safe_version entries, 1 new IOC (onlyflies.buzz)

- **Resource Evaluation**: Sandcastle (`@ai-hero/sandcastle`) — score 3/5 (Watch)
  - Evaluation file: `docs/resource-evaluations/083-sandcastle-agent-orchestration.md`
  - Added to Known Gaps table in `guide/ecosystem/third-party-tools.md` (programmatic sandboxed orchestration)
  - Not integrated: v0.5.x maturity, TypeScript-only barrier, Docker/Podman hard dependency, separate API key model
  - Revisit trigger: v1.0 release or Sequential Reviewer bug + issue #191 (subscription auth) resolved

- **MCP Ecosystem**: Added Sentry MCP Server entry to `guide/ecosystem/mcp-servers-ecosystem.md`
  - New validated server under DevOps & Infrastructure (observability loop: alert → diagnosis → patch)
  - Full entry: key features, setup, Claude Code config, query syntax reference, quality score (8.5/10), limitations table, alternatives comparison
  - Cross-references existing reference file at `examples/skills/mcp-integration-reference/references/sentry-mcp.md`
  - Updated file header (February → May 2026), DevOps category count (2 → 3 servers)

- **Claude Code Releases**: Updated tracking to v2.1.126
  - /model picker lists models from gateway's /v1/models endpoint (ANTHROPIC_BASE_URL gateway support)
  - claude project purge [path] — delete all Claude Code state for a project
  - claude auth login accepts pasted OAuth code for WSL2/SSH/container environments
  - Windows: PowerShell 7 from MS Store/MSI/.NET global tool now detected, treated as primary shell
  - Security: Fixed allowManagedDomainsOnly/allowManagedReadPathsOnly ignored in managed-settings
  - 40+ bug fixes: image paste crash >2000px, Stream idle timeout after sleep, CJK text on Windows, OAuth timeout, Agent SDK hang on malformed tool names

- **Claude Code Releases**: Updated tracking to v2.1.123 (v2.1.120 through v2.1.123)
  - v2.1.120: Windows PowerShell fallback (no Git Bash required), claude ultrareview CI subcommand, ${CLAUDE_EFFORT} in skills
  - v2.1.121: alwaysLoad MCP config, plugin prune, PostToolUse output replacement for all tools, critical memory leak fixes
  - v2.1.122: ANTHROPIC_BEDROCK_SERVICE_TIER, PR URL in /resume search, Vertex AI/Bedrock fixes, image resize fix
  - v2.1.123: OAuth 401 hotfix when CLAUDE_CODE_DISABLE_EXPERIMENTAL_BETAS=1

- **Peak Hours behavior** (guide, section "Subscription Plans & Limits"): Documented the March 26, 2026 Anthropic change — session limits now drain faster during weekdays 5am–11am PT due to GPU capacity constraints. Added practical workaround (shift compute-heavy tasks to off-peak hours). Source: MacRumors, The Register, TechRadar coverage of the official Anthropic change.

- **Data Privacy guide** (security): Added Risk 6 — Claude Desktop browser integration silent native messaging host installation. Covers what gets installed, which browsers are affected, what native messaging actually does vs. the consent failure issue, how to audit and remove the files, and the Claude Desktop/Claude Code CLI conflict bug (GitHub #51949, #53864). Factual, no "spyware" framing, includes command-line audit and cleanup steps.

- **Claude Code Releases**: Updated tracking to v2.1.119
  - /config settings now persist to ~/.claude/settings.json with override precedence
  - --from-pr accepts GitLab MR, Bitbucket PR, and GitHub Enterprise URLs
  - --print honors agent tools:/disallowedTools: frontmatter; --agent honors permissionMode
  - Security: blockedMarketplaces enforces hostPattern/pathPattern; 30+ bug fixes

- **Threat Database** (security): Updated to v2.15.0 (2026-04-24). Added 5 new CVEs from OX Security MCP STDIO chain (CVE-2026-30623 LiteLLM, CVE-2026-40933 Flowise, CVE-2026-33224 Bisheng, CVE-2025-69256 Serverless Framework, CVE-2026-6494 Red Hat AAP MCP). Added attack techniques T026 (Claudy Day session hijack) and T027 (Claude Code Supply Chain Memory Poisoning). Added 9 new sources including IBM X-Force agentic AI report, Straiker 94% prompt injection study, InfoSecurity 10 in-the-wild IPI payloads. Added litellm to minimum_safe_versions.

- **Known Issues** (major update): Added "Triple Harness Incident (Mar-Apr 2026)" resolved entry, covering three independent harness/prompt changes that degraded output quality: default effort high to medium (March 4, reverted April 7), thinking tokens cleared per-turn bug (March 26, fixed April 10 in v2.1.101), verbosity system prompt (April 16, reverted April 20 in v2.1.116). Source: Anthropic official postmortem and Boris Cherny HN comments (April 23, 2026). Updated Last Updated date.

- **Ultrareview section** (guide): Added `/ultrareview <PR#>` syntax, clarified diff-only scope (not full codebase), added Scope row to Ultraplan vs Ultrareview comparison table

- **Claude Code Releases**: Updated tracking to v2.1.118
  - Vim visual mode (`v`) and visual-line mode (`V`) with selection and operators
  - `/cost` and `/stats` merged into `/usage` (both old commands remain as shortcuts)
  - Custom named themes from `/theme` or `~/.claude/themes/`; plugins can ship themes
  - Hooks can invoke MCP tools directly via `type: "mcp_tool"` in hook config
  - `DISABLE_UPDATES` env var; `wslInheritsWindowsSettings` policy; 15+ bug fixes

- **Built-in Commands Reference** (major update): Added 26 missing commands to the reference table introduced in v2.1.108–v2.1.117
  - `/recap`, `/effort`, `/tui`, `/focus`, `/undo`, `/proactive`, `/less-permission-prompts`, `/team-onboarding`, `/terminal-setup`, `/reload-plugins`
  - `/config`, `/model`, `/context`, `/cost`, `/doctor`, `/release-notes`, `/copy`, `/resume`, `/loop`, `/mcp`, `/memory`, `/plugin`, `/keybindings`, `/setup-bedrock`, `/setup-vertex`, `/ultrareview`
- **`/recap` dedicated section**: How it works (triggers on return, not on exit), configuration options (`/config`, `CLAUDE_CODE_ENABLE_AWAY_SUMMARY`), telemetry-disabled compatibility, version history
- **Cheatsheet**: Added `/recap`, `/effort`, `/tui`, `/focus`, `/less-permission-prompts` to Essential Commands table

- **Claude Code Releases**: Updated tracking to v2.1.117
  - Default effort changed to `high` for Pro/Max subscribers on Opus 4.6 and Sonnet 4.6 (was `medium`)
  - Fixed Opus 4.7 sessions computing `/context` against 200K instead of 1M context window
  - Native macOS/Linux builds: Glob/Grep replaced by embedded `bfs`/`ugrep` (faster, no round-trip)
  - `/model` selections persist across restarts; startup header shows model source pin
  - 15+ bug fixes: OAuth 401 refresh, WebFetch hang on large HTML, HTTP 204 crash, NO_PROXY under Bun, Bedrock Opus 4.7 thinking disabled

- **README.md**: Updated date badge (Apr 22, 2026), Quick Start with Learning Path entry, repo structure with `learning-path/` and `examples/CATALOG.md`, "5 unique gaps" updated from 4

- **Learning Path (NEW)**: Added structured 7-module learning path for beginners
  - `guide/learning-path/README.md` — Meta guide with 7 modules, 3 learning tracks, time estimates
  - `guide/learning-path/01-installation.md` — Installation and first run (15 min)
  - `guide/learning-path/02-core-loop.md` — Interaction loop and context management (45 min)
  - `guide/learning-path/03-memory.md` — CLAUDE.md and configuration (1 hour)
  - `guide/learning-path/04-agents.md` — Creating specialized agents (1.5 hours)
  - `guide/learning-path/05-skills.md` — Building reusable skills (1.5 hours)
  - `guide/learning-path/06-hooks.md` — Automation hooks and events (1 hour)
  - `guide/learning-path/07-advanced.md` — Multi-agent orchestration (2-3 hours)
  - Each module: theory + hands-on exercises + validation steps
  - Mirrors competitor structure while maintaining unique depth in security/architecture
  - Integrates with `/self-assessment` and `/lesson-quiz` skills for interactive learning
  - Time estimate: 8-11 hours for complete path + optional deep dives

- **Template Catalog System (NEW)**: Auto-generated metadata-driven catalog for 181 templates
  - `examples/CATALOG.md` — Auto-generated index organized by complexity, time, domain (813 lines)
  - `scripts/generate-template-catalog.py` — Catalog generation tool (validation + filtering + auto-links)
  - `docs/template-metadata-schema.md` — Complete metadata specification with examples
  - `.claude/hooks/validate-template-metadata.sh` — Pre-commit validation hook for template metadata
  - `examples/README.md` — Updated with catalog information and metadata overview
  - Template counts: 23 agents, 52 commands, 64 skills, 37 hooks, 3 workflows, 2 scripts (181 total)
  - Metadata fields: name, description, complexity (beginner/intermediate/advanced), time (5min–4+ hrs), domain, prerequisites, status, keywords
  - Catalog regenerated via: `python3 scripts/generate-template-catalog.py --output examples/CATALOG.md`
  - Pre-commit hook auto-validates new/modified templates for proper metadata
  - Enables filtering by: beginner-friendly, time estimate, domain, keywords
  - Supports future integrations: auto-documentation generation, skill assessments, learning path mapping

- **Claude Code Releases**: Updated tracking to v2.1.116
  - `/resume` up to 67% faster on 40MB+ sessions; handles dead-fork entries more efficiently
  - Thinking spinner shows inline progress ("still thinking", "thinking more", "almost done thinking")
  - Security: sandbox auto-allow no longer bypasses dangerous-path check for `rm`/`rmdir` targeting `/`, `$HOME`, or critical directories
  - Agent frontmatter `hooks:` now fire when running as main-thread agent via `--agent`; `/config` search matches option values; many terminal, scrolling, and UI bug fixes

- **third-party-tools.md**: Added abtop — Rust TUI for monitoring Claude Code & Codex CLI agent fleets (htop-style: tokens, context %, rate limits, orphan ports, subagent tree, tmux integration, 584+ stars, MIT)

- **ultimate-guide.md § 5.4**: Added Example 4 — Tally Form Builder Skill, documenting the MCP wrapping pattern with deferred tool loading, OAuth flow, block chaining, and known limitations
- **examples/README.md**: Updated all section counts (agents 23, commands 52, hooks 37, skills 68, scripts 17, github-actions 6, integrations 3, config 6, memory 1) and added context-engineering folder to structure table
- **README.md, llms-full.txt, landing**: Updated template count from 246 → 247 across all counters (guide README badge, mermaid diagram, tree, comparison table, landing hero, features, FAQ, examples page)

- **ultimate-guide.md § 9.9**: Added "macOS Batch Automation: Shell + AppleScript" subsection — batch PPTX→PDF conversion via Keynote, with the shell-open-then-AppleScript pattern to avoid error -1719
- **examples/scripts/pptx-to-pdf.sh**: New utility script — recursive PPTX→PDF conversion on macOS using Keynote + AppleScript, no external dependencies

- **ultimate-guide.md**: Added Claude Opus 4.7 documentation throughout
  - Pricing table updated with Opus 4.7 ($5/$25, April 2026), tokenizer note (1.0–1.35x tokens), Mythos Preview mention
  - Model aliases: `opus` now resolves to Claude Opus 4.7
  - Effort levels: new `xhigh` level documented (Opus 4.7+, v2.1.114+); default for Claude Code raised to xhigh
  - Permission modes: Auto mode section added for Max subscribers (v2.1.114+)
  - /ultrareview section added (cloud parallel code review, v2.1.114+, 3 free for Pro/Max)
  - Adaptive Thinking evolution timeline updated with Opus 4.7 entry
  - API examples updated to use `claude-opus-4-7` model ID
  - Ultraplan table: model updated from Opus 4.6 to Opus 4.7
  - Cache min tokens table: Opus 4.7 added (4,096 token threshold)
- **cheatsheet.md**: Effort levels updated for Opus 4.7 (xhigh default, full level list)

- **third-party-tools.md**: New "Security Scanning" section with AgentShield (102-rule `.claude/` config scanner, A–F grading, GitHub Action, MIT); ToC updated; Known Gaps table updated to mark automated config scanning as filled
- **security-hardening.md**: Section 3.3 split into config-level (AgentShield) and code-level (security-auditor agent) scanning with cross-reference

- **audit-prompt.md v5.1**: context-evaluator.ai referenced in "Deepen Your Audit" block and Section 8 table as a zero-install LLM-native alternative for Dimension 1 (Memory and Context)
- **context-audit-prompt.md v1.1**: context-evaluator.ai added to Section 9 Related Resources
- **threat-db.yaml v2.14.0**: 5 new CVEs/advisories (CVE-2026-33032 MCPwn critical actively exploited, CVE-2026-27944, CVE-2025-56404, CVE-2026-30615, ADVISORY-MCP-STDIO-2026-001), T025 "Comment and Control" attack technique, 2 new scanning tools (Snyk Agent Scan, Straiker MCP Security), 9 new sources
- **security-hardening.md**: Added CVE-2026-33032 (nginx-ui MCPwn CVSS 9.8 actively exploited) and ADVISORY-MCP-STDIO-2026-001 (OX Security systemic STDIO flaw) to CVE table and alerts
- **Claude Code Releases**: Updated tracking to v2.1.114 (v2.1.113 + v2.1.114)
  - v2.1.113: Native Claude Code binary spawning via per-platform optional dependency
  - v2.1.113: sandbox.network.deniedDomains to block specific domains under wildcard allowedDomains
  - v2.1.113: Security hardening — macOS dangerous paths for rm, Bash deny rules match exec wrappers, find -exec no longer auto-approved
  - v2.1.113: Keyboard improvements, /loop Esc cancels wakeups, subagents fail after 10min, many bug fixes
  - v2.1.114: Fixed crash in permission dialog when agent teams teammate requested tool permission

## [3.39.1] - 2026-04-16 (2)

### Documentation

- **Claude Code Releases**: Updated tracking to v2.1.111
  - Claude Opus 4.7 xhigh effort level; Auto mode for Max subscribers no longer requires --enable-auto-mode
  - /ultrareview skill for cloud-based parallel multi-agent code review
  - /less-permission-prompts skill auto-generates allowlist from transcript history
  - Plan files named after prompts; read-only bash glob patterns no longer prompt
  - Many bug fixes (iTerm2+tmux tearing, LSP diagnostics, /resume tab-complete, /clear session name)
  - Reverted v2.1.110 non-streaming fallback retry cap

## [3.39.1] - 2026-04-16

### Added

- **context-evaluator** (`guide/ecosystem/third-party-tools.md` Configuration Quality section): New entry for the Packmind OSS tool that evaluates CLAUDE.md / AGENTS.md quality using 17 AI evaluators (13 error + 4 suggestion). Includes the zero-install web version at context-evaluator.ai, the Caliber comparison table, and cross-ref to the 2 patterns extracted from its source.

- **Runtime Prompt Logging** (`guide/core/skill-design-patterns.md`): New pattern: write the full evaluator prompt to disk as a blocking `await` BEFORE invoking the AI provider. Survives provider crashes, never throws, always-on (not gated by a debug flag). Observed in PackmindHub/context-evaluator (MIT).

- **Adaptive Unified/Parallel Mode** (`guide/core/skill-design-patterns.md`): New pattern: estimate combined token count of input files before launching agents. Below 100K tokens, one unified agent handles all files (cross-file contradiction detection). Above threshold, each file gets an independent parallel agent. Concrete threshold decision with `canUseUnifiedMode()`. Observed in PackmindHub/context-evaluator (MIT).

- **context-evaluator evaluation** (`docs/resource-evaluations/context-evaluator-evaluation.md`): Score 4/5. Documents all 4 patterns identified in the source read, integration decisions, and delta vs Caliber.

- **Credits: context-evaluator** (`guide/core/credits.md`): New entry for PackmindHub/context-evaluator (MIT). Covers Pattern 7 (Runtime Prompt Logging) and Pattern 8 (Adaptive Unified/Parallel Mode).

## [3.39.0] - 2026-04-16

### Added

- **Skeptical Reviewer Pattern** (`guide/ultimate-guide.md` §9.20 Agent Teams): New subsection documenting the four-agent pipeline design where a dedicated "skeptical reviewer" sub-agent filters false positives from parallel audit agents. Includes false-positive criteria, evidence requirement rule, KEEP/REJECT log pattern, and connection to Swarm Mode. Inspired by the Packmind playbook-audit open-source skill (Apache 2.0, Cédric Teyton).

- **MCP Reference File Pattern** (`guide/ecosystem/mcp-servers-ecosystem.md`): New section "Documenting an MCP for Claude: The Reference File Pattern" explaining how a `references/<mcp-name>.md` file injected before any MCP call reduces query failures from syntax gotchas, non-obvious parameter semantics, and rate limit behavior. Includes the three content types, file structure, and link to the fork-ready template.

- **`examples/skills/mcp-integration-reference/SKILL.md`**: Fork-ready template skill demonstrating the MCP reference file pattern. Five-step structure: read reference file, gather scope, fetch data, group and analyze, generate report. Designed to be adapted for any MCP server (Sentry, Datadog, PagerDuty, Linear, etc.).

- **`examples/skills/mcp-integration-reference/references/sentry-mcp.md`**: Complete Sentry MCP reference file template. Covers available tools with full parameter semantics, DDSQL-equivalent query syntax gotchas, pagination approach, known noise exclusion patterns, and five working query examples. Serves as the canonical example of what a good MCP reference file looks like.

- **`guide/core/credits.md`**: New file centralizing attributions for patterns borrowed from open-source engineering work. Current entries: Packmind (6 patterns, Apache 2.0, Cédric Teyton) and Anthropic skill-creator. Linked from README and cited inline at each pattern section.

- **`guide/core/skill-design-patterns.md`**: New reference file covering 6 architectural patterns for multi-agent and multi-file skills: Shared Ground Truth Injection, Pre-filtered References via Frontmatter Paths, Detection-Only Scope Boundary, Input-Handler Dispatch, Versioned Sub-directories for Tool-Version Coupling, and Two-Tier Standards. Each pattern includes the problem it solves, the pattern structure, token trade-offs, and when to apply it. Linked from README.

- **Handoff Triad Pattern** (`guide/ultimate-guide.md` §2 Session Handoff Pattern): New subsection after the existing handoff template documenting the three-command protocol (`create`, `resume`, `update`) with per-section merge rules. Key addition: append-only Work Done log creates an auditable history across sessions. Includes the merge rules table and link to fork-ready templates.

- **`examples/commands/handoff/create-handoff.md`**: Fork-ready template for session handoff creation. Generates `claudedocs/handoffs/handoff_YYYYMMDD_HHMMSS.md` with 8 structured sections. Includes explicit rules: append-only Work Done, `path:line` format for file references, 600-word target for quick loading.

- **`examples/commands/handoff/resume-handoff.md`**: Fork-ready template for loading a handoff document. Parses all sections, summarizes understanding in 3-5 bullets, and requires explicit user confirmation before starting work.

- **`examples/commands/handoff/update-handoff.md`**: Fork-ready template implementing the full merge rules table (keep/append/replace per section). Includes the fallback to new-file creation when no existing handoff is found, and per-step confirmation output.

- **Recipe Template: Context Validation Checkpoints** (`guide/ultimate-guide.md` §6.3 Command Template): New subsection after the existing command template documenting the checkpoint pattern: a checklist of preconditions Claude must verify before executing recipe steps. Prevents mid-step failures in one-way operations.

- **`examples/commands/recipe-template.md`**: Fork-ready template demonstrating the Context Validation Checkpoints pattern. Includes the checkpoints section, numbered recipe steps with per-step validation, error handling table, and adaptation notes.

- **Plans and Specs as Committed Artifacts** (`guide/core/skill-design-patterns.md`): New section (M4 pattern) documenting the practice of committing plan/spec pairs under `.claude/` as dated markdown files (`YYYY-MM-DD-<slug>.md` + `YYYY-MM-DD-<slug>-design.md`). Covers why it beats session-only plans (grep-able, resume-able, captures rationale), when to use it, and the naming convention. Inspired by the Packmind `.claude/plans/` convention (Apache 2.0).

- **`examples/scripts/statusline.py`**: Fork-ready context bar script for Claude Code's `statusCommand` setting. Displays a color-coded progress bar (green/yellow/red), context percentage, git branch, and model name. Key insight documented with inline comments: subtracts 32,000 tokens from the total context window to compute the effective input window (output buffer reservation). Adapted from Packmind's `.claude/statusline.py` (Apache 2.0).

- **`machine-readable/reference.yaml`**: Added 20+ entries for all Packmind pattern integrations: `skill_design_patterns_*` (7 patterns), `mcp_reference_file_*`, `skeptical_reviewer_*`, `handoff_triad_*`, `recipe_template_*`, `statusline_*`, and `credits_guide`.

### Changed

- **`tools/audit-prompt.md` v5.0 — orchestrator architecture** (`tools/audit-prompt.md`): Rewrote from a flat 130+ checkbox checklist into an 8-dimension weighted orchestrator (100 pts). The prompt now delegates each domain to a specialized skill or command if installed (eval-skills, eval-rules, token-audit, audit-agents-skills, security-check), with inline bash fallback when not available. New dimensions: Memory & Context (20 pts, delegates to `/token-audit`), Rules Hygiene (10 pts, delegates to `/eval-rules`), Skills Quality (10 pts, delegates to `/eval-skills`), Agents/Commands Quality (10 pts, delegates to `/audit-agents-skills`), Security Posture (20 pts, delegates to `/security-check`), MCP Ecosystem (10 pts), Workflow Commands (10 pts), Freshness & Best Practices (10 pts). Phase 1 replaces 3 separate bash blocks with one unified inventory scan. Phase 3 produces an 8-row scorecard instead of a flat findings table. Added `--include-global` scope flag, "Deepen Your Audit" section with install commands for all delegated skills, and 10 new glossary terms (Context Budget, Rules auto-loaded, paths: frontmatter, effort: field, argument-hint, Hook Profiles, Threat Database, Cache Bug #40524, managed-settings.d/, Routines). Version updated from 4.0 (guide v3.37.6) to 5.0 (guide v3.38.17+).

### Fixed

- **Architecture.md broken image** (`guide/core/architecture.md`): Replaced missing `./images/claude-code-architecture-overview.jpeg` (file never committed) with a Mermaid flowchart showing Claude Code as an orchestration layer over Claude models and the development environment. Attribution to Mohamed Ali Ben Salem preserved as a text link. Fixes [#25](https://github.com/FlorianBruniaux/claude-code-ultimate-guide/issues/25).

## [3.38.17] - 2026-04-16

### Added

- **Context engineering: Structural Metadata Files** (`guide/core/context-engineering.md`): New subsection in Section 4 documenting the pattern of separating rules context (CLAUDE.md) from structural context (code-map.yaml). Covers the two-type distinction, five standard sections, pointer registration table, auto-generation approach, and a production example from a ~1,300-file TypeScript codebase (Méthode Aristote).

- **`examples/context-engineering/code-map-template.yaml`**: Generic starter template for structural metadata files — small auto-generated YAML (~1K tokens) capturing codebase shape: architecture layers with file counts, component domains, nested CLAUDE.md inventory, project stats, key paths. Separate from rules/config context.

- **`examples/context-engineering/context-bench.sh`**: Benchmark script measuring impact of structural metadata files. `--budget` compares token cost across three loading strategies (no code-map / always-on / on-demand). `--probe` tests what % of structural questions are answerable from code-map.yaml without filesystem traversal. `--compare` diffs two code-map versions over time.

- **`examples/skills/eval-rules/SKILL.md`**: Skill for rules-focused audit — resolves `paths:` globs against real project files, flags dead or over-broad patterns, interactive rule-by-rule review with in-place edit support.

- **`examples/commands/routines-discover.md`**: Slash command `/routines-discover` surfacing actionable Routine candidates. Audits five angles (scheduled maintenance, event-driven reactions, alert response, cross-system sync, release automation), outputs ranked use case cards with trigger type, input/output, value estimate, and blockers sorted by value-to-effort ratio.

- **Security hardening** (`.claude/settings.json`, `.claude/hooks/`): Applied the guide's own recommendations to this repo. Added `permissions.deny` blocking `.env*`, `*.pem`, `credentials*`, `id_rsa*`, `id_ed25519*`, `secrets/**`. Added `PreToolUse` hook wiring `dangerous-actions-blocker.sh` for Bash, Edit, Write.

- **`examples/commands/scaffold.md`**: Coaching command that asks 4-5 targeted questions to determine whether a use case calls for agent, command, skill, hook, or rule — generates a ready-to-use template for the chosen component type.

- **`scripts/update-cc-releases.sh`**: Extended release tracking to three sources. Added Source 2 (weekly docs digest `code.claude.com/docs/en/whats-new/YYYY-wN.md`) for Desktop/Web/Cloud features not in the GitHub CHANGELOG. Added Source 3 (reference links to Help Center and GitHub releases).

### Changed

- **`examples/context-engineering/ci-drift-check.yml`**: Extended CI trigger section with commented code-level path triggers (`prisma/schema.prisma`, API router dirs) and note on `DRIFT_WARN_ONLY` for gradual gate introduction.

- **`guide/ultimate-guide.md`**: Added `/eval-rules` to audit tools callout (three tools: `audit-agents-skills`, `eval-skills`, `eval-rules`).

- **`CLAUDE.md` split into `@docs` references**: Reduced from 618 lines to 274 lines (-56%). Extracted four reference sections into `docs/` files loaded on demand via `@refs`.

### Documentation

- **Context management** (`guide/ultimate-guide.md`): Added "bad compact" antipattern callout and updated context rot threshold for 1M context window (Anthropic internal data: 300-400K tokens, task-dependent).

- **Claude Code Releases**: Updated tracking to v2.1.110 — `/tui` command, Push notification tool, `--resume/--continue` for scheduled tasks, `/focus` command, `autoScrollEnabled` config, 30+ bug fixes.

- **Routines (Cloud Automation)** (`guide/ultimate-guide.md` §6.1): Documented April 14, 2026 Routines launch. API trigger (dedicated HTTP POST endpoint, bearer token, returns `session_url`), GitHub event trigger (17 event types, PR filters, requires Claude GitHub App), per-plan daily run limits (Pro 5/day, Max 15/day, Team/Enterprise 25/day).

- **`guide/ecosystem/ai-ecosystem.md` §15**: Project Glasswing & Claude Mythos Preview — defensive security initiative with 11 launch partners, automated vulnerability discovery, thousands of high-severity CVEs found in OpenBSD/FFmpeg/Linux kernel.

- **Threat Database v2.13.0**: 6 new CVEs, 2 new attack techniques (T023 Lies-in-the-Loop, T024 Prompt Poaching), 2 new scanning tools (ClawArmor, ClawSec), 2 new research papers.

## [3.38.16] - 2026-04-15

### Documentation

- **Claude Code Releases**: Updated tracking to v2.1.109
  - v2.1.108: ENABLE_PROMPT_CACHING_1H env var (1-hour cache TTL), /recap session context feature, built-in slash commands discoverable via Skill tool, /undo alias for /rewind, /resume defaults to current directory
  - v2.1.109: Improved extended-thinking indicator with rotating progress hint

## [3.38.15] - 2026-04-14

### Documentation

- **Claude Code Releases**: Updated tracking to v2.1.107
  - v2.1.105: PreCompact hook blocking, EnterWorktree path parameter, plugin background monitors, /proactive alias for /loop, WebFetch strips CSS/JS, /doctor with status icons and f-to-fix, skill descriptions cap raised to 1,536 chars, multiple bug fixes
  - v2.1.107: Show thinking hints sooner during long operations

## [3.38.14] - 2026-04-10

### Documentation

- **Claude Code Releases**: Updated tracking to v2.1.101
  - /team-onboarding command — generates teammate ramp-up guide from local Claude Code usage
  - OS CA certificate store trusted by default (enterprise TLS proxies work without extra config; CLAUDE_CODE_CERT_STORE=bundled to revert)
  - /ultraplan and remote-session features auto-create default cloud environment (no web setup required first)
  - 40+ bug fixes: --resume context loss on large sessions, Bedrock SigV4 auth 403, sub-agents in worktrees denied file access, RemoteTrigger run action, Grep ENOENT self-heal, hardcoded 5-min timeout removed, LSP command injection fix

## [3.38.13] - 2026-04-10

### Documentation

- **Claude Code Releases**: Updated tracking to v2.1.98
  - Interactive Vertex AI setup wizard from login screen (GCP auth, project/region config, model pinning)
  - Monitor tool for streaming events from background scripts; CLAUDE_CODE_PERFORCE_MODE for Perforce workflows
  - Bash security hardening: 8+ permission bypass fixes (backslash flags, compound commands, env-var prefixes, /dev/tcp redirects)
  - Subprocess PID namespace sandboxing on Linux; LSP clientInfo support; --exclude-dynamic-system-prompt-sections for cross-user caching

## [3.38.12] - 2026-04-09

### Documentation

- **Output Styles** (`guide/ultimate-guide.md` §9.7, `guide/cheatsheet.md`, `guide/core/settings-reference.md`, `machine-readable/reference.yaml`, `examples/styles/`): Full documentation of the built-in Output Styles product feature — previously undocumented as a first-class feature. Covers three built-in modes (Default, Explanatory, Learning), activation via `/config` or `outputStyle` in `settings.json`, custom styles via `.claude/styles/`, token cost impact, and the deprecation history of `/output-style` (Oct 2025). Added `outputStyle` setting expansion in settings-reference, corrected stale `/output-style` slash command row, added entry to `reference.yaml`, added to cheatsheet "Features Méconnues" table, and created `examples/styles/custom-style-template.md` with usage notes and `keep-coding-instructions` myth correction.

## [3.38.11] - 2026-04-09

### Documentation

- **Claude Code Releases**: Updated tracking to v2.1.97
  - Focus view toggle (`Ctrl+O`) in NO_FLICKER mode with prompt, tool summary, and response
  - `refreshInterval` status line setting + `workspace.git_worktree` JSON field
  - 30+ bug fixes: NO_FLICKER (15 fixes), /resume (6 fixes), MCP 50 MB/hr buffer leak, permissions hardening, 429 exponential backoff

## [3.38.10] - 2026-04-08

### Added

- **Claude Managed Agents section** (`guide/ecosystem/ai-ecosystem.md`): New §14 covering Anthropic's cloud-hosted agent platform launched April 8, 2026. Includes: three-way decision table (Messages API vs Managed Agents vs Claude Code), architecture diagram (Brain/Hands/Memory decoupling via Mermaid), multi-agent coordination diagram (orchestrator + specialist threads), real-world use cases (Notion, Rakuten, Asana, Sentry), full Next.js integration pattern (API route with SSE streaming + React hook), decision checklist (when to reach for each layer), research preview features (outcomes/self-evaluation, memory, multi-agent), cost model with per-model pricing table and optimization patterns, `ant` CLI reference, SDK support matrix (8 languages), engineering background (pets vs cattle, assumption decay, interface stability). ToC updated.

## [3.38.9] - 2026-04-08

### Added

- **codesight entry** (`guide/ecosystem/third-party-tools.md`): New "Project Context Bootstrapping" section covering codesight — a zero-dependency CLI that compiles structured codebase context (routes, schema, deps, blast radius) via AST analysis and exposes it as a wiki knowledge base or 11 MCP tools. Includes command reference, MCP configuration, wiki token comparison table, CI integration snippet, and explicit caveats (self-reported benchmarks, TypeScript-only AST, `--init` CLAUDE.md overwrite risk). Score 3/5 — category gap documented, tool maturity to be reassessed at 90 days. TOC and description frontmatter updated.

## [3.38.8] - 2026-04-08

### Added

- **Ultraplan documentation** (`guide/ultimate-guide.md`, `guide/cheatsheet.md`, `machine-readable/reference.yaml`): Full coverage of the Ultraplan feature (research preview, v2.1.91+). New `### Ultraplan` subsection in Section 2.3 Plan Mode covering: concept (async cloud planning via multi-agent Opus 4.6), 3 activation methods (`/ultraplan`, keyword, local plan handoff), terminal status indicators, browser review interface (inline comments, emoji reactions, outline sidebar), dual execution paths (cloud → PR, teleport → terminal), requirements (GitHub only, not Bedrock/Vertex/Foundry, incompatible with Remote Control), and comparison table vs Plan Mode vs OpusPlan. Also added cross-reference in Section 9.16 Session Teleportation, and `/ultraplan` command in the cheatsheet quick commands table and Plan Mode section.

- **`git-ai-archaeology` skill** (`examples/skills/git-ai-archaeology/`): New skill that analyzes AI config evolution in any git repository. Reconstructs the chronology of AI adoption by reading git history — first commits per `.claude/` path, monthly commit distribution with ASCII charts, major PRs by category (MCP integrations, skills/hooks/agents, code review automation), optional CHANGELOG AI mentions, and maturity phases synthesis. Read-only, produces a single markdown report. Ported from `boldguy` repo.

## [3.38.7] - 2026-04-08

### Documentation

- **Claude Code releases tracking updated to v2.1.96** (`machine-readable/claude-code-releases.yaml`, `guide/core/claude-code-releases.md`): Added v2.1.94 (Bedrock Mantle support, high effort default for API/enterprise users, plugin skill stable naming, Slack MCP compact header) and v2.1.96 (hotfix for Bedrock auth regression with AWS_BEARER_TOKEN_BEDROCK).

## [3.38.6] - 2026-04-06

### Documentation

- **1M context beta retirement deadline added** (`guide/core/claude-code-releases.md`): New row in the API Ecosystem breaking changes table — `context-1m-2025-08-07` beta header retired April 30, 2026 for Sonnet 4.5/4. Requests exceeding 200K tokens will error after that date; migrate to Sonnet 4.6 or Opus 4.6.

- **`/powerup` added to Essential Commands** (`guide/ultimate-guide.md`): The interactive animated lessons command (v2.1.90) was absent from the main guide's Essential Commands bash block. Added after `/help` as both are discovery-oriented entry points.

- **`showThinkingSummaries` note added** (`guide/ultimate-guide.md`): Documented that thinking summaries are off by default in interactive sessions since v2.1.89, with the opt-in path (`"showThinkingSummaries": true` in settings.json). Added near the `cleanupPeriodDays` settings reference.

- **French translation pipeline documented** (`CLAUDE.md`): Added "French Guide Translation + Export" section covering `scripts/translate-guide.py` (Claude Haiku batch translation), `guide/ultimate-guide.fr.md` output, and related workflow.

### Added

- **Threat database update v2.12.0** (`examples/commands/resources/threat-db.yaml`): 4 new CVEs (CVE-2026-5058 aws-mcp-server 0-day CVSS 9.8, CVE-2026-31951 LibreChat OAuth exfiltration, CVE-2026-34742 Go MCP SDK DNS rebinding, CVE-2026-5323 a11y-mcp SSRF), 1 new attack technique (T022 NomShub IDE remote tunnel persistence via indirect prompt injection in Cursor), 2 new scanning tools (SandyClaw dynamic sandbox + Semgrep MCP integration), 1 new defensive resource (arXiv 2604.03070 empirical study: 1,708 issues found across agent skill ecosystem), 9 new sources, 2 new minimum safe version entries (go-mcp-sdk 1.4.0, a11y-mcp 1.0.6).

- **`/token-audit` skill** (`examples/skills/token-audit/`, also installed in `~/.claude/skills/`): Runnable skill that executes the full token audit — measures fixed-context overhead per component, classifies rules files (ALWAYS/SOMETIMES/RARELY), audits hook stdout per invocation, and produces a prioritized action plan with savings estimates. Includes RAG break-even assessment.

- **Token Audit Workflow** (`guide/core/context-engineering.md` §10): New section with step-by-step workflow to measure and reduce fixed context overhead — shell commands to inventory all loaded components, token budget calculator, signal/noise classification framework (ALWAYS/SOMETIMES/RARELY), hook overhead analysis, action plan template, and a reusable audit prompt. Includes honest RAG assessment (break-even analysis before committing to vector infrastructure).

- **Guide export script**: `scripts/generate-guide-exports.sh` — generates the full `guide/ultimate-guide.md` (~25K lines) as EPUB (488K) and PDF (2.9 MB) via pandoc + Typst. Outputs to `dist/`. Supports `--epub`, `--pdf`, `-o DIR`, `-v` flags. Auto-detects Typst from Quarto's bundled binary. PDF pre-processing strips internal anchor links for Typst compatibility.

### Updated

- **`examples/commands/check-cache-bugs.md`**: Updated to reflect Anthropic's fixes (Bug 1 fixed v2.1.91, Bug 2 fixed v2.1.90) and extended with ArkNill community findings (B4 microcompact silent context stripping, B5 tool result budget cap 200K). Output format now includes version-conditional FIXED status. Bug 3 (attribution header) still active — workaround unchanged.

## [3.38.5] - 2026-04-04

### Documentation

- **Claude Code Releases**: Updated tracking to v2.1.92
  - Interactive Bedrock setup wizard from login screen (AWS auth, region, credential verification, model pinning)
  - `forceRemoteSettingsRefresh` policy setting — fail-closed managed settings enforcement
  - Per-model and cache-hit breakdown in `/cost` for subscription users
  - `/release-notes` now an interactive version picker
  - Linux sandbox `apply-seccomp` helper fix (npm + native builds)
  - Removed `/tag` and `/vim` commands

### Quiz

- **Quiz expanded from 271 to 334 questions (+63 questions, 16 categories)**: Comprehensive update covering v3.34.10 → v3.38.3 guide changes.
  - **New category `16-team-metrics.yaml`** (12 questions): DORA 4 metrics + 2024 benchmarks, 2025 DORA archetype shift (7 archetypes, 8 dimensions), SPACE framework 5 dimensions, Velocity Trap, AI-specific metrics (CFR by code origin, review time comparison), Bug Escape Rate formula, vanity metrics to drop, 4-question test, 5-person vs 25-person stack, implementation roadmap.
  - **`07-hooks.yaml`** (+8 questions): `defer` permission value, multi-hook precedence (deny > defer > ask > allow), session-scoped hooks, bypassPermissions safety invariant, Setup/Elicitation/ElicitationResult events, conditional `if` field, PostCompact event.
  - **`09-advanced-patterns.yaml`** (+8 questions): Loop Guardrails (MAX_ITERATIONS=8), Dedicated Reviewer 1:4 ratio, Iterative Retrieval WHY/WHAT pattern, cache prefix hierarchy (tools > system > messages), 20-block lookback degradation, RPI workflow Gate 1, Opus 4.6 min token threshold (4,096), Context Chaining vs Ralph Loop.
  - **`06-commands.yaml`** (+8 questions): /powerup animated lessons, /loop, /branch + --fork-session, argument-hint frontmatter, /investigate//qa//canary, --bare, --channels, --console.
  - **`03-memory-settings.yaml`** (+6 questions): Agent Memory 3 scopes, managed-settings.d/, ${CLAUDE_PLUGIN_DATA} persistent storage, MEMORY.md hard limits (200-line/25KB/200-file), `effort` frontmatter field, MEMORY.md management.
  - **`12-architecture.yaml`** (+5 questions): Context Rot n² structural nature, JIT vs RAG retrieval, MMD drift detection, Goldilocks altitude problem, MCP tool count limits (<10 servers, <80 tools).
  - **`13-security.yaml`** (+3 questions): bypassPermissions protected paths, Cache Bug 2 (87-118K tokens/resume), CLAUDE_CODE_ATTRIBUTION_HEADER/Bug 3 marginal impact.
  - **`14-privacy-observability.yaml`** (+3 questions): CLAUDE_CODE_SUBPROCESS_ENV_SCRUB, sandbox.failIfUnavailable, X-Claude-Code-Session-Id nginx passthrough.
  - **`11-learning-with-ai.yaml`** (+3 questions): Team-Level Steering Metrics (2 levels), Velocity Trap warning, Monday ritual.
  - **`15-ai-ecosystem.yaml`** (+2 questions): Google Antigravity agent-first IDE, AGENTS.md Compound Learning (+4% human-curated vs -3% LLM-generated).
  - **`05-skills.yaml`** (+3 questions, already applied): Skills 2.0 taxonomy, Skill Lifecycle 3 phases, Skill Evals.
  - **`02-core-concepts.yaml`** (+2 questions): BMAD criterion (high-complexity + stable requirements), FDD criterion (feature teams + parallel delivery).
  - **Stale fixes (7 questions updated)**: 07-001 (exit code 2 stderr-only), 07-002 (17→27 hook events), 07-004 (if field), 02-001 (auto-compact mechanism), 03-001 (managed-settings.d/), 12-002 (TodoWrite→Tasks API), 12-004 (Claude 3.5 Sonnet→Sonnet 4.6).

## [3.38.4] - 2026-04-03

### Fixed

- **`guide/diagrams/04-architecture-internals.md` — Master Loop rendering bug**: Two backward edges (`G --> C` and `J --> A`) were creating giant black arrow artifacts in Mermaid renderers (dagre layout engine routes long cycle-breaking edges around the entire diagram). Fixed by enclosing the inner tool-execution loop inside a `subgraph AGENT_LOOP` so `F --> C` renders as a contained cycle within the box. Outer conversation loop now routes `J -->|Yes| B` (rebuild prompt) instead of `J -->|Yes| A`, which is also semantically more accurate. Removed the separate "Parse tool calls" node by merging into "Execute tools in parallel" (reflects `StreamingToolExecutor` reality). Description updated to explicitly name the two nested loops.

### Documentation

- **`guide/diagrams/04-architecture-internals.md` — System Prompt Assembly**: Updated to reflect two-zone architecture confirmed by source analysis. Diagram now shows the `BOUNDARY MARKER` separating STATIC zone (`cacheScope: 'global'`, shared across all users) from DYNAMIC zone (per-session cache). Added note that MCP instructions are always recomputed and uncached (confirmed in source: "servers connect/disconnect between turns"). Added `machine-readable` source footnote with 2026-03-31 confirmation date.

## [3.38.3] - 2026-04-03

### Documentation

- **New page `guide/ops/team-metrics.md`** (~400 lines): Complete framework for measuring and piloting AI-augmented tech teams. Covers DORA (4 metrics with 2024 benchmarks + 2025 archetype shift), SPACE framework, AI-specific metrics (contribution metrics, AI PR review quality), product metrics (time-to-value, feature adoption, Bug Escape Rate), recommendations by team size (5-person vs 25-person), vanity metrics to drop, the 4-question decision test, and tooling guide (LinearB, Faros.ai, GitHub Analytics, Axify).
- **`guide/roles/learning-with-ai.md` extended**: Added "Team-Level Steering Metrics" subsection in the "For Tech Leads & Engineering Managers" section — Level 1 (DORA delivery health), Level 2 (AI adoption quality), the Velocity Trap warning, and a Monday ritual (3 numbers, 5 minutes).
- **`guide/README.md` updated**: New entry for `ops/team-metrics.md` in the Operations section.
- **Claude Code Releases**: Updated tracking to v2.1.91 — MCP tool result size override via `_meta` annotation (up to 500K), `disableSkillShellExecution` setting, plugin `bin/` executable support, Edit tool shorter `old_string` anchors.

- **`guide/core/context-engineering.md` expanded with 8 new sections** (+198 lines): Added "Context Engineering vs. Context Optimization" (synthesis/reasoning separation, engineering vs. optimization distinction); "Why Context Rot is Structural, Not Accidental" (n² attention architecture, JIT retrieval vs. RAG pre-loading, Memory tool beta, CoT caveat for long agentic tasks); "The Goldilocks problem: altitude" in Project Configuration (productive altitude between too vague and too granular, with worked examples); "Community skill libraries" in Skills vs. Rules (anthropics/claude-code-skills, ibelick/ui-skills); MCP tool count limits in Progressive Disclosure (<10 servers, <80 total tools); "Context Chaining" pattern in Context Lifecycle (curated session-to-session summaries, distinct from Ralph Loop); "Context Drift Detection" in Quality Measurement (cosine distance, share of drifted features, MMD, thresholds table, when to use); PRP methodology cross-reference added to Cross-References.

- **`argument-hint` frontmatter field documented**: Added `argument-hint` to the skill frontmatter table (`guide/ultimate-guide.md` line ~7336), the Variable Interpolation section (new tip + example showing the picker UX), and the Command Template 6.3 (frontmatter block). Also updated `guide/cheatsheet.md` (command minimal example), `whitepapers/recap-cards/fr/m09-slash-commands.qmd` (`$ARGUMENTS` section), `whitepapers/recap-cards/fr/m10-skills.qmd` (frontmatter table), and Appendix A.2/A.3 templates. The field shows placeholder text in the slash command menu when a command/skill accepts `$ARGUMENTS`.

### Examples

- **`argument-hint` added to 29 command templates**: All `examples/commands/` files that use `$ARGUMENTS` but were missing `argument-hint` have been patched (28 root commands + 3 learn/ commands). Hints reflect the actual argument signatures documented in each command body. Only `audit-agents-skills.md` already had the field.

## [3.38.2] - 2026-04-02

### Documentation

- **`/powerup` documented across learning surfaces**: Added `/powerup` (interactive animated lessons, v2.1.90) to `guide/cheatsheet.md` (Essential Commands table), `guide/roles/learning-with-ai.md` (new "Start Here" subsection), `whitepapers/fr/09-apprendre-avec-ia.qmd` (Slash Commands pour l'Apprentissage), `whitepapers/en/09-learning-with-ai.qmd` (Slash Commands for Learning), `whitepapers/recap-cards/fr/01-commandes-essentielles.qmd` (Commandes Slash Core), and `landing/src/content/docs/guide/roles/learning-with-ai.md` (Slash Commands for Learning).
- **Hook events expanded to complete 27-event list**: The Event Types table previously listed 22 events. Added the 5 missing events (`Setup`, `PostCompact`, `InstructionsLoaded`, `Elicitation`, `ElicitationResult`) and restructured all 27 events into 7 logical groups (Lifecycle, Agent actions, Permissions, Compaction, Multi-agent, Configuration, File system, User interaction) for easier scanning.
- **Session-scoped hooks documented**: Added new "Session-Scoped Hooks" subsection explaining that hooks can be registered ephemerally at runtime without writing to `settings.json`. Clarifies that this is the mechanism skills use to register temporary callbacks during their invocation.
- **`bypassPermissions` safety invariant documented**: Added a protection table listing the paths and files Claude Code always prompts before modifying even in `bypassPermissions` mode (`.git/`, `.claude/`, shell configs, `.gitconfig`, `.mcp.json`, `.claude.json`). Also clarified that content-specific `allow` rules survive `bypassPermissions`.
- **MEMORY.md file limits documented**: Added concrete enforcement limits to the Auto-Memories section (200-line cap, 25 KB max per file, 200-file directory cap) with a table explaining truncation behavior and the warning appended when limits are exceeded.

### Maintenance

- **`machine-readable/reference.yaml` synced**: Updated `updated` date to 2026-04-02, expanded `hook_events` from 4 to 27 complete events organized in 8 groups, added `hooks_session_scoped` pointer (line 9507), `permissions.bypass_safety_invariant` pointer (line 1076) with protected paths list, and `auto_memories_file_limits` pointer (line 5020) with limit detail string.
- **README.md stats updated**: Templates count 225 → 228, guide lines 22K+/23K+ → 24K+ (24,734 lines), date badge synced to Apr 2, 2026.

### Fixed

- **Hooks documentation gaps (fact-checked vs official docs)**: Added missing `defer` value to `permissionDecision` options, added multi-hook precedence rule (`deny > defer > ask > allow`, v2.1.89+), clarified that exit code 2 silently discards stdout/JSON (only stderr is forwarded to Claude), and added a dedicated `defer` semantics block explaining its headless-only usage with `stop_reason: "tool_deferred"` and `--resume`.

## [3.38.1] - 2026-04-02

### Documentation

- **Claude Code Releases**: Updated tracking to v2.1.90
  - /powerup command — interactive animated lessons with live demos
  - Fixed session-crashing infinite loop in rate-limit dialog
  - Fixed --resume prompt-cache miss regression (since v2.1.69)
  - PowerShell tool hardened: trailing & bypass, debugger hang, TOCTOU
  - SSE transport linear-time for large frames; per-turn JSON.stringify eliminated

### Changed

- **BMAD selection criterion corrected**: Replaced "Enterprise 10+ teams" with "High-complexity projects with stable requirements" across all docs. The real driver is project complexity + requirement stability, not headcount. BMAD is usable solo or at any team size — and becomes a liability when specs change mid-project. Updated `guide/core/methodologies.md`, `guide/ultimate-guide.md`, `whitepapers/fr/07-guide-reference.qmd`, `whitepapers/en/07-reference-guide.qmd`, `landing/src/pages/methodologies/index.astro`, `landing/src/data/methodology-quiz.ts`. Added explicit "when to avoid: evolving requirements" warning throughout.

- **FDD selection criterion corrected**: Replaced "Large teams 10+" with "Feature teams, parallel delivery" — FDD is organized around feature ownership and parallel delivery structure, not raw headcount. Updated same files.

### Added

- **`/methodology-advisor` command**: New slash command that reads the codebase silently (contributors, test maturity, spec files, LLM signals, file count) and asks only 3 targeted questions to recommend one of 8 methodology stacks — with contextual quick start using real project paths. Available in `examples/commands/methodology-advisor.md`.

- **Methodology Quiz (landing)**: New `/methodologies/` page on `cc.bruniaux.com`. Interactive 12-question quiz recommends one of 8 methodology stacks based on team size, project stage, session style, test maturity, and more. Full decision matrix with Combination Patterns table, two-axis map, and 8 stack cards with quick-start prompts. Linked from home page Methodologies section, header nav, footer, and sitemap.

- **Methodology Map**: Added 2D positioning diagram to `guide/core/methodologies.md` (between Decision Tree and The 15 Methodologies sections). Maps all 20 methodologies on Spec-First/Code-First (Y) vs Lean/Enterprise (X) axes, with quadrant labels and reading guide. Synced to landing guide reader.

- **WP09 update (v3.27.6 → v3.38.1)**: Updated both FR (`09-apprendre-avec-ia.qmd`) and EN (`09-learning-with-ai.qmd`) whitepapers to integrate v3.37.0–v3.38.1 changes: (1) Agent Adoption Curve — 7-level maturity scale from Nicolas Martignole/Back Market, inserted as new "Où en Êtes-Vous?" section after the Three Patterns diagnosis; (2) "Job is now the spec" reframing (Larridin/Kanitkar) — developer as producer/director, mastery = spec-writing quality, added in Augmented Pattern section; (3) JiT Tests as comprehension exercise — Meta production results (4x hardening tests, 70% review load reduction), brief mention in Augmented Pattern advanced techniques. Added 2 new source entries in Practitioners table.

- **WP01 update (v3.27.6 → v3.38.1)**: Updated both FR (`01-prompts-efficaces.qmd`) and EN (`01-effective-prompts.qmd`) whitepapers to integrate v3.37.0–v3.38.1 changes: new slash commands (`/investigate`, `/qa`, `/canary`, `/land-and-deploy`, `/review-pr` enhanced, `/session-save`), `/loop` and `/branch` workflow tools, `effort` frontmatter field for skills/commands, and `showThinkingSummaries: false` default note in Thinking Modes section. Added "New Workflows v3.37+" section in both files.

- **WP02 update (v3.27.6 → v3.38.1)**: Updated both FR (`02-personnalisation.qmd`) and EN (`02-customization.qmd`): Agent Memory 3-scope table (user/project/local), `effort` field in Skills frontmatter, `${CLAUDE_PLUGIN_DATA}` persistent storage section, `managed-settings.d/` enterprise governance section.

- **WP03 update (v3.27.6 → v3.38.1)**: Updated both FR (`03-securite.qmd`) and EN (`03-security.qmd`): v2.1.78 security fixes (silent sandbox disable, MCP deny bypass, protected dirs writable in bypassPermissions), Hook Profiles env-based gating (minimal/standard/strict), conditional `if` field for hooks, PermissionDenied hook event, heartbeat dead-man switch with timeout table, threat intelligence update (T021 IDEsaster, GhostClaw, CVE-2026-33010, CVE-2026-27825/27826, Cisco DefenseClaw, Ferrok).

- **WP04 update (v3.27.6 → v3.38.1)**: Updated both FR and EN `04-architecture.qmd`: auto-compact precise mechanism (6-7% buffer + micro-compaction), streaming tool execution (10 parallel), Advanced Tool Use Patterns table (PTC/Dynamic Filtering/Tool Use Examples), Agent Memory 3 scopes, knowledge cutoffs table (Sonnet 4.6/Opus 4.6/Haiku 4.5).

- **WP05 update (v3.27.6 → v3.38.1)**: Updated both FR (`05-equipe.qmd`) and EN (`05-team.qmd`): `--bare` flag (headless CI mode), `--channels` permission relay, Hook Profiles, AGENTS.md Compound Learning (Gloaguen et al. 2026 empirical data), Instinct-Based Continuous Learning, Dedicated Reviewer Teammate (1:4 ratio, Addy Osmani), Loop Guardrails (MAX_ITERATIONS=8).

- **WP06 update (v3.27.6 → v3.38.1)**: Updated both FR and EN `06-privacy.qmd`: `CLAUDE_CODE_SUBPROCESS_ENV_SCRUB` env var, `sandbox.failIfUnavailable` setting, `X-Claude-Code-Session-Id` header with nginx passthrough example.

- **WP07 update (v3.27.6 → v3.38.1)**: Updated both FR (`07-guide-reference.qmd`) and EN (`07-reference-guide.qmd`): Agent Memory 3-scope table, `effort` field, 4 new hook events (CwdChanged/FileChanged/TaskCreated/PermissionDenied), conditional `if` hook filter, TaskOutput deprecation (v2.1.83+), 7 new slash commands, 4 new CLI flags (--bare/--channels/--console/--fork-session), knowledge cutoffs table, `managed-settings.d/` and `${CLAUDE_PLUGIN_DATA}` callout, Settings Reference pointer.

- **WP08 update (v3.27.6 → v3.38.1)**: Updated both FR and EN `08-agent-teams.qmd`: Iterative Retrieval for Sub-Agents (WHY/WHAT pattern, 3-cycle max), AGENTS.md Compound Learning (human-curated +4% vs LLM-generated -3%/+20% cost), Loop Guardrails, Dedicated Reviewer Teammate, token budgeting per agent, loop-monitor template, Ralph Loop disambiguation.

- **Recap cards content update (v3.37.0 → v3.38.1)**: Targeted content additions to 5 priority cards (FR + EN): m16 (Guardrails section — MAX_ITERATIONS, Dedicated Reviewer 1:4, token budget 85% pause), m17 (Iterative Retrieval — WHY/WHAT pattern, 3-cycle max), c04 (`effort` field in Skills, `${CLAUDE_PLUGIN_DATA}` for Plugins), t15 (`CLAUDE_CODE_SUBPROCESS_ENV_SCRUB`), t16 (`sandbox.failIfUnavailable`).

- **`/audit-whitepapers` command**: New diagnostic command that audits all whitepapers (FR + EN) and recap cards (FR + EN) for version freshness, FR/EN parity, and metadata quality. Scores each document out of 100 across 4 phases (version gap 40pts, content staleness 20pts, parity 20pts, metadata 20pts) with A-F grading. Supports `--fix` (frontmatter patch suggestions), `--verbose` (all criteria), `--wp-only`, `--cards-only`. Feeds into `/update-whitepapers` for systematic updates.

### Fixed

- **Cache bugs audit — Bug 2 root cause corrected** (2026-04-01): JSONL writer strips DTD records before write (not position mismatch on restore); severity upgraded HIGH with concrete session data (87-118K tokens/resume, 300-400K/session at 3-4 resumes). Engineering fix redirected to the writer. Updated in `check-cache-bugs.md`, `known-issues.md`, `claudedocs/cache-bugs-audit-2026-03-31.md`.
- **ultimate-guide.md — prompt caching section**: Added "Known cache bugs (v2.1.69+)" callout with workarounds for Bug 2 (avoid --resume) and Bug 3 (CLAUDE_CODE_ATTRIBUTION_HEADER=false), link to known-issues.md and /check-cache-bugs.
- **check-cache-bugs command**: Added missing YAML frontmatter (`name` + `description` fields) — command was not recognized by Claude Code slash command system (reported by genesiscz in CC#40524)
- **check-cache-bugs + known-issues: Bug 2 mechanism corrected** (per fivedollarfridays CC#40524): root cause is session JSONL writer stripping `deferred_tools_delta` records before write, not position mismatch on restore. On --resume, full DTD re-announcement shifts all message positions → 0% cache ratio on every resume. Concrete evidence: 87-118K tokens rebuilt per resume, 300-400K/session with 3-4 resumes. Severity upgraded from MEDIUM to HIGH.
- **known-issues + check-cache-bugs: Bug 3 severity recalibrated** (per jmarianski, original RE analyst): "marginal impact" on session tokens in practice — system prompt is small relative to total context. Bug 2 has larger measurable cost for heavy users.
- **check-cache-bugs background section**: Corrected cost impact estimate from "10-20x" to "2-5x on input tokens" (early community estimates conflated system prompt portion with total session cost); added source-verified mechanism details for all three bugs
- **known-issues.md**: Added Section 0 documenting prompt cache bugs (CC#40524) with per-bug root cause, workaround, concrete JSONL data for Bug 2, and link to /check-cache-bugs audit command

### Documentation

- **Source analysis corrections (2026-03-31)**: Applied 4 targeted corrections to the guide based on source-level analysis, each verifiable by observable behavior
  - **Knowledge cutoffs**: Added model knowledge cutoff table (Sonnet 4.6 = Aug 2025, Opus 4.6 = May 2025, Haiku 4.5 = Feb 2025) to the Model Aliases section
  - **Auto-compact precision**: Replaced the inconsistent "~80%" description with the accurate mechanism (triggers when remaining context drops below a fixed buffer, ~6-7% of window); reconciled conflicting "75% vs 80%" mentions in the guide
  - **Micro-compaction**: Added description of the lightweight pre-compaction pass that selectively compresses older tool results before full auto-compact runs
  - **Streaming tool execution**: Added note explaining that concurrency-safe tools (Read, Grep, Glob) can start executing while the model is still generating, and run in parallel (up to 10 concurrent)
  - **Internal reference**: Created `claudedocs/source-code-analysis-2026-03-31.md` (gitignored) with full findings from 6-agent source analysis covering 512K lines — serves as future documentation reference when features ship officially

- **CC release v2.1.89**: Updated Claude Code releases tracking to v2.1.89 (previous session incorrectly labeled this v2.1.88; v2.1.88 does not appear in release notes)
  - `"defer"` permission decision for `PreToolUse` hooks — headless pause + `-p --resume` re-evaluation
  - PermissionDenied hook for auto mode classifier denials (return `{retry: true}` to retry)
  - `CLAUDE_CODE_NO_FLICKER=1` env var for flicker-free alt-screen rendering
  - Named subagents in `@` mention typeahead; `MCP_CONNECTION_NONBLOCKING=true` for `-p` mode
  - **Breaking**: Thinking summaries now off by default (`showThinkingSummaries: true` to restore)
  - Massive bugfix batch: CRLF on Windows, StructuredOutput cache (50% failure rate), memory leaks, crashes, voice mode, autocompact thrash circuit breaker

### Meta

- **Stats sync**: Updated guide stats across all LLM-indexing files — 24,600+ lines (was 24,200+), 226 templates (was 217); `reference.yaml` date updated to 2026-03-30

### Documentation

- **CC releases v2.1.83–v2.1.87**: Integrated 9 guide updates from the weekly watch covering hooks, enterprise settings, MCP, and Windows
  - **Hooks events table**: Added `CwdChanged`, `FileChanged`, and `TaskCreated` hook events (§7.1)
  - **Conditional hooks `if` field**: New section explaining `if` filter syntax for reducing subprocess overhead (§7.2, v2.1.85+)
  - **PreToolUse headless AskUserQuestion**: Added pattern for satisfying interactive prompts from CI/CD pipelines via `updatedInput` (§7.2, v2.1.85+)
  - **`managed-settings.d/` drop-in directory**: New enterprise governance section documenting per-team policy fragments (§16, v2.1.83+)
  - **`sandbox.failIfUnavailable`**: Added with compliance recommendation to prevent silent unsandboxed fallback (§16, v2.1.83+)
  - **`CLAUDE_CODE_SUBPROCESS_ENV_SCRUB`**: Added env var for stripping cloud credentials from subprocesses (§16, v2.1.83+)
  - **PowerShell native tool (Windows)**: New section documenting opt-in preview tool for Windows-native `.ps1` execution (§7.3, v2.1.84+)
  - **`X-Claude-Code-Session-Id` header**: Added proxy/observability section with nginx and Envoy examples (§19, v2.1.86+)
  - **MCP `headersHelper` env vars**: Added multi-server authentication pattern using `CLAUDE_CODE_MCP_SERVER_NAME`/`URL` (§8.3, v2.1.85+)
  - **`TaskOutput` deprecation**: Added deprecation notice in Tasks API section and updated 3 plan command templates to use `Read` instead (v2.1.83+)
- **`/loop` command**: Added dedicated section (§6.1) documenting recurring interval automation — syntax, use cases from Boris Cherny, stopping mechanism; added in v2.1.71
- **Session forking**: Added dedicated section (§6.1) for `/branch` and `--fork-session` — when to fork vs restart, workflow with `/rename`, v2.1.77 history
- **Claude in Chrome**: Added subsection in §9.5 (Tight Feedback Loops) documenting the Chrome browser extension — setup, capabilities table, `--chrome`/`--no-chrome` flags, why visual feedback matters
- **auto-compact + memory capture conflict**: Added note in Session vs. Persistent Memory section explaining that `autoCompactEnabled: false` is required for PostToolUse-based capture tools (claude-mem etc.) to avoid losing history mid-session; includes two mitigation options
- **claude-mem**: Updated all coverage to v10.6.3 (up from v9.1.1)
  - `guide/ultimate-guide.md` Section 8.2: expanded architecture diagram with full session lifecycle table, observation type taxonomy (DISCOVERY/CHANGE/FEATURE/BUGFIX), skills table (mem-search/smart-explore/make-plan/do/timeline-report)
  - Added security warning: `GET /api/settings` exposes API keys in plain text — localhost-only mitigation explained
  - Fixed Gemini model name: "Flash" → "Flash Lite" with Flash vs Flash Lite quality tradeoff note
  - `examples/plugins/claude-mem.md`: added Bun runtime dependency note, skills table, security callout on default config, updated cost tables with Gemini Lite column
  - `docs/resource-evaluations/claude-mem-evaluation.md`: updated version stats to v10.6.3

## [3.38.1] - 2026-03-30

### Security

- `examples/commands/resources/threat-db.yaml`: updated to v2.11.0 — 3 new CVEs, 1 new attack technique (T021 IDEsaster), 1 new scanning tool (Ferrok)
  - **CVE-2026-33010** (critical): mcp-memory-service CORS misconfiguration allowing cross-origin memory theft; fix: upgrade to 10.25.1
  - **CVE-2026-33946** (medium): MCP Ruby SDK session hijacking via insufficient SSE session binding; fix: upgrade to 0.9.2
  - **CVE-2026-27597** (critical): agentfront enclave JavaScript sandbox escape (CWE-94); fix: upgrade to 2.11.1
  - **T021 IDEsaster**: 30+ chained vulnerabilities across AI coding IDEs (Cursor, Windsurf, GitHub Copilot, Zed.dev) enabling data theft and RCE — 24 CVEs assigned
  - **Ferrok**: new MCP security scanner mapping to OWASP MCP Top 10 (2026) framework
  - `minimum_safe_versions`: added mcp-memory-service (10.25.1), mcp-ruby-sdk (0.9.2), agentfront-enclave (2.11.1)

### Documentation

- **Claude Code Releases**: Updated tracking to v2.1.87
  - Fixed messages in Cowork Dispatch not getting delivered

- **Claude Code Releases**: Updated tracking to v2.1.86
  - X-Claude-Code-Session-Id header for API proxies
  - Jujutsu (.jj) and Sapling (.sl) added to VCS exclusion lists
  - Reduced @ mention token overhead (no more JSON-escaping)
  - Improved prompt cache hit rate for Bedrock/Vertex/Foundry
  - Read tool compact line-number format with deduplication
  - Fixed marketplace plugin scripts failing on macOS/Linux since v2.1.83

- `README.md`: added StarMapper section with world map visualization of stargazers (replaces inline badge with dedicated section, added both near top and bottom of page).

### Added
- `docs/resource-evaluations/community-signals-benchmark-march-2026.md`: evaluation of two synthesized FR-language reports on Claude Code community signals and competitor benchmark for March 2026 (score 3/5). Two factual errors detected: "Auto Mode" as a permission mode (does not exist) and Channels attributed to Claude Code (they are ClawdBot). All other identified gaps were already covered.
- `guide/ultimate-guide.md` §1.4: added Permission Fatigue anti-pattern section with decision table (right mode per situation). Community signals confirm this is a top friction point: users approve prompts without reading then reach for `--dangerously-skip-permissions` on non-sandboxed machines.

### Fixed
- `guide/ultimate-guide.md` §Subscription Plans: removed expired Spring Break promotion note (ran March 13-27, 2026).

- `guide/workflows/agent-teams.md` §8 Best Practices: added AGENTS.md for Compound Learning section covering what to document, the empirical case for human-curated vs LLM-generated files (Gloaguen et al., 2026: -3% success / +20% cost for LLM-generated, +4% for developer-written), and maintenance rules. Added Loop Guardrails section (MAX_ITERATIONS=8, mandatory reflection prompt, kill/reassign criteria). Added Dedicated Reviewer Teammate section (Opus 4.6, read-only, auto-trigger on TaskCompleted, 1:4 ratio). Added token budgeting per agent to Cost Optimization (hard limits, 85% pause threshold). Credit: Addy Osmani — O'Reilly AI CodeCon, March 2026.
- `guide/ultimate-guide.md` §11 CLAUDE.md size guidelines: extended Gloaguen et al. citation to include task success rate data (-3% for LLM-generated, +4% for developer-written) previously missing from the cost-only note at line 16924.
- `guide/ultimate-guide.md` §Fresh Context Pattern (Ralph Loop): added disambiguation note clarifying two distinct community usages — Geoffrey Huntley's original context rotation pattern vs the multi-agent atomic task iteration variant popularized in 2026.
- `docs/resource-evaluations/080-addy-osmani-code-agent-orchestra.md`: evaluation of Addy Osmani's O'Reilly AI CodeCon article on multi-agent orchestration (score 3/5, 5 integration items identified).
- `guide/ecosystem/ai-ecosystem.md` §13 Autonomous Research Loops: documents the autoresearch pattern from [karpathy/autoresearch](https://github.com/karpathy/autoresearch) (57K stars, March 2026). Covers the core loop (measure → change → re-measure → keep/revert), the `program.md` behavior contract, ML-to-code-quality adaptation table, safety properties via git rollback, and when to use/avoid the pattern.
- `examples/commands/autoresearch.md`: new command template implementing the autoresearch loop for code quality. Four modes: scan (propose loops), scaffold (generate measure.sh + direction.txt + files.txt), run (autonomous iterations), status (all loops overview). Includes `program.md` writing guide and ML vs code quality comparison table.

- `examples/commands/resources/threat-db.yaml`: updated to v2.10.0 (2026-03-27). New entries: CVE-2026-27825 (mcp-atlassian unrestricted file write, chains with CVE-2026-27826 for MCPwnfluence RCE, CVSS 9.1), CVE-2025-59834 (ADB MCP Server command injection, critical). New attack techniques: T019 (Marketplace Ranking Manipulation — ClawHub Convex public mutation exploit reached 3,900 executions across 50+ cities), T020 (Agentic Tool Chain Reasoning Layer Attack — CrowdStrike). New scanning tools: Cisco DefenseClaw (open-source, Skills Scanner + MCP Scanner + a2a-scanner + CodeGuard + AI BoM, 2026-03-27), hackmyagent (community red-team toolkit), ClawNet (Silverfort OpenClaw plugin), ESET AI Skills Checker. New defensive resources: TrueFoundry MCP Gateway, Cisco DefenseClaw. 7 new sources added. Updated CVE-2026-27826 notes with MCPwnfluence chain context.

### Fixed
- Fixed 52 broken links across 22 guide files: all `./ultimate-guide.md#anchor` and `../ultimate-guide.md#anchor` patterns converted to bare `#anchor` format so the landing build script resolves them to the correct split chapter. 20 anchors also corrected (stale section numbers, renamed headings, double-hyphens). Fixed `/en/github-actions` → `./github-actions.md` and `/en/gitlab-ci-cd` → plain text in `workflows/code-review.md`. Fixed malformed link text in `workflows/design-to-code.md`. Files: core/ (architecture, methodologies), ecosystem/ (ai-ecosystem, context-engineering-tools, third-party-tools), ops/ (ai-traceability, devops-sre, observability), roles/ (agent-evaluation, learning-with-ai), security/ (production-safety, security-hardening), workflows/ (agent-teams, code-review, design-to-code, dual-instance-planning, github-actions, search-tools-mastery, skeleton-projects, task-management, team-ai-instructions).

## [3.38.0] - 2026-03-27

### Added
- `guide/ultimate-guide.md` §7.6 Hook Profiles: environment-variable-based hook gating (minimal/standard/strict) for scaling hooks across teams without one-size-fits-all enforcement. Per-hook level assignment via `HOOK_REQUIRED_LEVEL` env prefix. Credit: Everything Claude Code (Affaan Mustafa).
- `guide/ultimate-guide.md` §9.24 Instinct-Based Continuous Learning: lightweight observation capture at Stop hook (not UserPromptSubmit), confidence scoring, decay model, and promotion pipeline from instincts to CLAUDE.md rules or skills. Credit: Everything Claude Code v2.
- `guide/workflows/agent-teams.md` §9 Iterative Retrieval for Sub-Agents: max-3-cycles retrieval budget for sub-agents lacking context. WHY/WHAT separation pattern for sub-agent task prompts. Credit: Everything Claude Code longform guide.
- `guide/security/production-safety.md` Rule 6 Autonomous Loop Safety: heartbeat dead-man switch with process-group kill (not just parent). PostToolUse heartbeat writer + separate watchdog script. Timeout tuning table by task type. Credit: Everything Claude Code Security Guide.
- `examples/agents/loop-monitor.md`: new agent template for monitoring unattended autonomous sessions. Detects stalls (no activity > threshold), token runaway (high rate vs baseline), and repeated action loops (same call N times). Haiku model, read-only, pairs with watchdog.
- `examples/commands/session-save.md`: new command template for structured session handoff. Captures decisions, modified files, current status, and ordered next steps into a timestamped Markdown file.

## [3.37.8] - 2026-03-27

### Changed
- `guide/ultimate-guide.md`: expanded Auto Dream section with full technical depth — server-side feature flag (`tengu_onyx_plover`), exact system prompt quote, Sleep-time Compute academic foundation (Berkeley + Letta), phase 2 grep-not-read strategy, configuration JSON, performance benchmark (913 sessions / 9 min), before/after MEMORY.md line counts, `/dream` bug status (issues #38461/#38426, PR #39299), 3 quality gaps (identity/accuracy/transparency) from issue #38493 with concrete examples, community implementations (dream-skill, ai-dream), guidance on when Auto Dream is redundant vs. useful.

## [3.37.7] - 2026-03-27

### Documentation

- **Claude Code Releases**: Updated tracking to v2.1.85
  - Conditional `if` field for hooks (filter by permission rule syntax)
  - `CLAUDE_CODE_MCP_SERVER_NAME`/`_URL` env vars for headersHelper multi-server support
  - PreToolUse hooks can now satisfy AskUserQuestion headlessly
  - Fixed `/compact` context-exceeded on very large conversations
  - Improved scroll performance (WASM yoga-layout → TypeScript)

## [3.37.6] - 2026-03-26

### Added
- `/investigate` command (`examples/commands/investigate.md`): root-cause debugging. Iron Law enforcement, 5-phase workflow, failure pattern table (6 modes), 3-strike escalation, blast radius gate. Inspired by gstack/investigate.
- `/qa` command (`examples/commands/qa.md`): browser QA testing with diff-aware scoping. 3 tiers, 7-category issue taxonomy × 4 severities, PASS/WARN/FAIL health scores, fix-verify loop. Inspired by gstack/qa.
- `/canary` command (`examples/commands/canary.md`): post-deploy monitoring. Baseline capture, 10-min loop, transient tolerance (2+ checks), 4 alert levels, curl-based platform-agnostic. Inspired by gstack/canary.
- `/land-and-deploy` command (`examples/commands/land-and-deploy.md`): merge-to-verify pipeline. Pre-flight → CI wait → merge → platform detection (Fly/Render/Vercel/Netlify/Heroku/Railway) → canary verify → revert. Inspired by gstack/land-and-deploy.
- `guide/core/settings-reference.md`: complete settings.json and env vars reference (1,284 lines, v2.1.81).

### Changed
- `/review-pr` enhanced: scope drift detection (plan vs diff cross-ref), Fix-First heuristic, LLM Output Trust Boundary review category. Inspired by gstack/review/checklist.md.
- `IDEAS.md`: deferred gstack patterns captured (autoplan, office-hours, freeze/unfreeze, retro, design-review, benchmark).

### Changed

- **update(guide/section-1.6)**: rewrite "Migrating from Other AI Coding Tools" with March 2026 fact-checked data (closes #12). GitHub Copilot: agent mode GA, MCP GA, full codebase context, multi-model selection, updated pricing tiers (Free/$10/$39 Pro+). Cursor: agent mode GA, Background Agents, MCP Apps v2.6. Windsurf: pricing raised to $20 (Cognition AI acquisition), Cascade still core. Zed: Zeta2 autocomplete, subagents, up to 1M token context, MCP with OAuth. Removed all factually false claims ("suggestions only", "current file", "weak debugging") and replaced with honest differentiators (terminal-native, persistent context system, headless/CI mode, agent orchestration). Added pricing comparison table. Fixed cc-copilot-bridge tier naming (Pro+ -> Pro, $10/mo).

### Added

- **`/investigate` command** (`examples/commands/investigate.md`): root-cause debugging command. Enforces the Iron Law (no fixes before root cause). 5-phase workflow: collect symptoms, read code, check recent changes, reproduce, pattern analysis. Includes known pattern table (race conditions, null propagation, state corruption, integration failure, config drift, stale cache), 3-strike escalation rule, blast radius gate (>5 files touched → confirm), and structured DEBUG REPORT output. Inspired by [gstack](https://github.com/garrytan/gstack) `/investigate`.

- **`/qa` command** (`examples/commands/qa.md`): systematic browser QA testing with diff-aware scoping. 3 tiers (quick/standard/exhaustive). Identifies affected routes from `git diff --name-only` and tests those pages first. Issue taxonomy: 7 categories (visual, functional, UX, content, performance, console, accessibility) × 4 severities (critical/high/medium/low). Fix-then-verify loop with atomic commits per fix. PASS/WARN/FAIL health score per category. Ship readiness verdict. Browser-agnostic. Inspired by gstack `/qa`.

- **`/canary` command** (`examples/commands/canary.md`): post-deploy monitoring. Baseline capture mode (`--baseline`), continuous monitoring loop (default 10 min), 4 alert levels (CRITICAL/HIGH/MEDIUM/LOW), transient tolerance (2+ checks before alerting), CANARY REPORT output, baseline update offer after healthy deploy. curl-based, no browser daemon required. Inspired by gstack `/canary`.

- **`/land-and-deploy` command** (`examples/commands/land-and-deploy.md`): complete merge-to-verify pipeline picking up where `/ship` leaves off. Pre-flight → CI wait → pre-merge readiness gate → merge → platform detection (Fly.io, Render, Vercel, Netlify, Heroku, Railway) → deploy polling → production health check → deploy report. One critical safety gate before merge; revert always available. Inspired by gstack `/land-and-deploy`.

- **`/review-pr` enhanced** (`examples/commands/review-pr.md`): 3 new sections: (1) **Scope Drift Detection** — searches `~/.claude/plans/` for branch plan file, cross-references stated scope vs actual diff; (2) **Fix-First Heuristic** — AUTO-FIX (dead code, N+1, stale comments, magic numbers) vs ASK (security, race conditions, design decisions); (3) **LLM Output Trust Boundary** in Agent 3 — flags AI-generated values written to DB without validation. Inspired by gstack `/review` + `review/checklist.md`.

- **Settings Reference** (`guide/core/settings-reference.md`, 1,284 lines): new comprehensive reference for all `settings.json` keys and environment variables. Covers 60+ settings organized into 13 sections (Core, Plans/Memory, Permissions, Hooks, MCP, Sandbox, Plugins, Model, Display/UX, Auth, Attribution, Worktrees, AWS/Cloud) plus 100+ environment variables across 13 categories. Cross-references official docs, JSON schema, and community research. Unverified settings marked `⚠️ Unverified`; schema-only keys marked `📋 Schema only`. Includes full permission rule syntax, complete config example, and quick-reference table.

- **CLI Flags Reference expanded** (`guide/ultimate-guide.md` ~l.21833): replaced minimal 23-flag flat table (36% coverage) with comprehensive structured reference. 50+ flags across 13 categories (Session & Context, Model, Output, Permissions, System Prompt, Agent, MCP, Workspace, Budget, Integration, Init, Debug, Settings Override), 10 subcommands (`claude auth`, `claude doctor`, `claude mcp`, `claude plugin`, `claude remote-control`, `claude setup-token`, `claude update`, `claude install`, `claude agents`), and startup environment variables table. Short form aliases documented throughout.

- **Agent Memory section** (`guide/ultimate-guide.md` §4.5, ~113 lines): dedicated section expanding scattered mentions into a cohesive reference. Covers the three memory scopes (`user` / `project` / `local`) with storage paths and selection guide, 200-line injection limit and overflow handling via topic-specific files, recommended MEMORY.md structure, prompting patterns, and comparison table against CLAUDE.md and auto-memory. Sections §4.5-§4.6 renumbered to §4.6-§4.7.

- **Advanced Tool Use Patterns section** (`guide/core/architecture.md` §7, ~125 lines): new section covering four Anthropic API features GA since February 2026. Programmatic Tool Calling (PTC) — multi-tool orchestration in one inference pass; Dynamic Filtering — pre-processing raw HTML before context injection (official benchmarks: +13.3pp BrowseComp for Sonnet 4.6); Tool Use Examples — `input_examples` field lifting tool accuracy from 72% to 90%; Claude Code relevance table (CLI vs Agent SDK). The ~37% PTC token reduction marked as community-reported.

- **Context Engineering Tools page** (`guide/ecosystem/context-engineering-tools.md`): ecosystem map for token/context optimization tools. Covers output compression (RTK, Headroom), prompt compression (LLMLingua), AI gateways (Edgee, Portkey), RAG optimization, KV cache infrastructure (vLLM PagedAttention, SGLang RadixAttention), LLMOps observability (Langfuse, LangSmith, Arize Phoenix, TruLens), and core concepts (MVC, Context Rot, Semantic Priming Hypothesis).

- **Auto Dream section** (`guide/ultimate-guide.md` ~l.4945): community-discovered memory consolidation feature. 4-phase process (Orient, Gather Signal, Consolidate, Prune & Index), trigger conditions (24h + 5 sessions), access via `/memory`. Unofficial status caveated.

- **Glossary** (`guide/core/glossary.md`): 130+ alphabetical term definitions — Claude Code-specific concepts, community-coined patterns, AI engineering vocabulary. Includes Config hierarchy (Local > Project > Global), Boris Cherny attribution, Desloppify (@peteromallet), BMAD, Ralph Wiggum Loop (Geoffrey Huntley), 56% Reliability Warning.

### Documentation

- **Claude Code Releases**: Updated tracking to v2.1.84 — PowerShell tool for Windows (opt-in preview), `TaskCreated` hook, `WorktreeCreate` hook HTTP support, global system-prompt caching with ToolSearch, `allowedChannelPlugins` managed setting, idle-return prompt after 75+ min, deep links open in preferred terminal, MCP tool descriptions capped at 2KB, bare `#123` no longer auto-linked.

- **Claude Code Releases**: Updated tracking to v2.1.83 — `managed-settings.d/` drop-in directory, `CwdChanged`/`FileChanged` hook events, transcript search in Ctrl+O, `CLAUDE_CODE_SUBPROCESS_ENV_SCRUB=1`, fixed `--mcp-config` bypassing managed policy, fixed macOS exit hang, `sandbox.failIfUnavailable`.

### Fixed

- **"Slop" attribution** (`guide/ultimate-guide.md`): added Simon Willison attribution (2024) before the Desloppify section.
- **Glossary corrections** (`guide/core/glossary.md`): fixed Config hierarchy direction, Boris Cherny title, Desloppify author, BMAD expansion, Ralph Wiggum Loop attribution, auto-compaction threshold values, 4 alphabetical ordering issues.
- **`paths:` array bug in rules frontmatter** (`guide/ultimate-guide.md`): replaced failing `paths:` YAML array syntax with `globs:` field in both code examples. Added warnings referencing GH#17204.

## [3.37.5] - 2026-03-23

### Added
- **Resource Evaluation + Integration — Veille CC Releases 2.1.77-2.1.81** (score 3/5): Weekly release summary covering 5 releases (March 17-20, 2026). Releases already tracked in claude-code-releases.yaml/md. Audit revealed 5 gaps in thematic sections: `StopFailure` hook added to Event Types table (`ultimate-guide.md`), `rate_limits` statusline field documented with JSON schema (`ultimate-guide.md`), `${CLAUDE_PLUGIN_DATA}` persistent storage documented in Plugin System section (`ultimate-guide.md`), `--bare` mode added to GitHub Actions CI example (`ultimate-guide.md`), `sandbox.filesystem` settings block (allowWrite/denyRead/allowRead) added to `guide/security/sandbox-native.md`.

### Security
- **Threat database updated to v2.9.0** (`examples/commands/resources/threat-db.yaml`): 1 new malicious author (`sakaen736jih`, 199 automated skills, Bitdefender/Particula), 5 new CVEs (CVE-2026-4192 quip-mcp-server RCE, CVE-2026-4198 mcp-server-auto-commit injection, CVE-2026-33252 MCP Go SDK CSRF, CVE-2026-4270 AWS API MCP path traversal, CVE-2026-27826 MCP Atlassian SSRF), 2 new campaigns (ClickFix OpenClaw, Fake CLI Prerequisites via openclawcli.vercel.app), 2 new IOCs (malicious domains), 1 new scanning tool (AquilaX), 1 new defensive resource (42crunch), 9 new sources. ClawHavoc stats updated (341 → 1,184+ malicious skills by March 1, 2026).

### Fixed
- **`eval-skills` skill — removed non-official `tags` frontmatter criterion**: `tags` is not a supported field in the Claude Code skill spec. The skill was incorrectly scoring it as a quality criterion (1pt) and listing it in the parse step. Removed `tags` from frontmatter, scoring table, and parse instructions. Scoring total adjusted from 15 to 14 pts with updated thresholds (≥80% = ≥11/14, 60-79% = 8-10/14). Added an explicit note warning against using `tags`. Reported by community via Alexandre Aubert.

## [3.37.4] - 2026-03-23

### Added
- **Resource Evaluation + Integration — Harman "Just-in-Time Catching Test Generation at Meta"** (arxiv 2601.22832, score 4/5): JiTTests are ephemeral, LLM-generated tests triggered at PR submission that fail by design to surface regressions. Production-verified at Meta (4x over hardening tests, 70% reduction in human review load). Integrated into `guide/core/methodologies.md` (new JiTTesting subsection) and `guide/workflows/tdd-with-claude.md` (forward link from Mutation Testing).
- **Resource Evaluation + Integration — Caliber config quality tool** (score 3/5): CLI tool scoring AI agent config quality 0-100 (61 deterministic checks, local-only). Integrated into `guide/ecosystem/third-party-tools.md` as new "Configuration Quality" section.
- **Resource Evaluation — Larridin "Building AI-Native Engineering Teams"** (Kanitkar, score 4/5): Producer role concept, "job is now the spec" reframing, and two anti-patterns (no parallel implementation subagents; provide full plan text to agents). Integration target: `guide/roles/`.
- **Resource Evaluation — Anthropic weekly watch March 16-23, 2026** (score 3/5): Three gaps identified for integration — `thinking.display: "omitted"` (extended thinking section), model capabilities API fields, `--bare` vs `-p` CI/CD tradeoffs.

### Changed
- **Claude Code releases tracking** updated to v2.1.81 — `--bare` flag for scripted `-p` calls, `--channels` permission relay, worktree auto-resume fix, MCP tool call collapsing.
- **README** — dynamic star history chart added.
- **`guide/ecosystem/mcp-vs-cli.md`** — historical arc intro paragraph (browser → IDE+MCP → CLI agents, 2022-26).

- **Resource Evaluation — Anthropic weekly watch March 16-23, 2026** (`docs/resource-evaluations/2026-03-23-veille-hebdo-anthropic-16-23-mars.md`): Score 3/5. Perplexity synthesis covering CC 2.1.81, Python SDK v0.85/v0.86, and two Platform API entries. CC releases already tracked. Three actionable gaps identified: (1) `thinking.display: "omitted"` absent from extended thinking section — multi-turn API pattern for chain continuity without full thinking text transmission; (2) model capabilities API fields (`GET /v1/models` now returns `capabilities` object + `max_input_tokens`) absent from guide — enables runtime-dynamic model selection; (3) `--bare` vs standard `-p` tradeoffs missing from CI/CD scripting section. 81k study and Python SDK items out of scope.

- **Resource Evaluation + Integration — Caliber (rely-ai-org/caliber)** (`docs/resource-evaluations/caliber-config-quality-tool.md`): Score 3/5. CLI tool that scores AI agent config quality (0-100, deterministic, 61 checks, local-only), generates tailored configs via codebase fingerprinting, and detects drift between code and CLAUDE.md using git-based signals. Early-stage (released March 2026, 65 stars at eval). Full source code audit conducted. Integrated into `guide/ecosystem/third-party-tools.md` as a new "Configuration Quality" section between Configuration Management and Engineering Standards Distribution — a gap not covered by any existing tool in the guide.

- **Guide update: Configuration Quality section in `third-party-tools.md`** (`guide/ecosystem/third-party-tools.md`): New section added for Caliber. Includes full scoring rubric table (6 categories), delta comparison vs AIBlueprint/Packmind, code examples, security note (write access to CLAUDE.md), and cross-refs. ToC updated, Recommendations by Persona updated.

- **Claude Code Releases**: Updated tracking to v2.1.81 — `--bare` flag for scripted `-p` calls (skips hooks/LSP/plugins, API key only), `--channels` permission relay (forward tool approvals to phone), worktree session auto-resume fix, MCP read/search collapsing into "Queried {server}" line, plan mode hides "clear context" by default, fixed concurrent sessions re-authenticating on OAuth refresh, fixed Node.js 18 crash

- **Resource Evaluation + Integration — Harman "Just-in-Time Catching Test Generation at Meta" (arxiv 2601.22832)** (`docs/resource-evaluations/2026-03-22-harman-jittesting-meta-arxiv.md`): Score 4/5. Industrial paper by Mark Harman (Meta), Jan 30 2026. JiTTests are ephemeral, LLM-generated tests triggered at PR submission — they fail by design to surface regressions, then are discarded. Production-verified: 4x improvement over hardening tests, 70% reduction in human review load, 4 serious failures caught out of 41 candidates at Meta's 100M+ LoC codebase. Integrated into `guide/core/methodologies.md` (new JiTTesting subsection after CDD, with practical approximation pattern for Claude Code today) and `guide/workflows/tdd-with-claude.md` (forward link from Mutation Testing advanced pattern).

- **Resource Evaluation — Larridin "Building AI-Native Engineering Teams" (Kanitkar)** (`docs/resource-evaluations/larridin-ai-native-teams-kanitkar.md`): Score 4/5. Practitioner playbook from Ameya Kanitkar (Co-founder & CTO, Larridin), Jan 2026. Key contributions not yet covered in the guide: "job is now the spec" mindset reframing, Producer role concept for AI-native team coordination, team structure advice (small in-office teams, flow management for teammates), and anti-patterns section with two specific operational constraints (never dispatch parallel implementation subagents; never let agent read plan files — provide full text instead). Context engineering, Ralph Wiggum, and Docker sandboxes already documented. Model version specifics (GPT 5.2) flagged as unverifiable. Integration target: `guide/roles/` and adoption section of ultimate guide.

- **README: Star History chart added** (`README.md`): Dynamic star growth chart from star-history.com embedded before the Contributing section. Shows the repo trajectory since January 2026 (0 → 2K+ stars). Renders live on GitHub via the star-history.com SVG API.

- **Resource Evaluation — Arnaud Gaches "MCP vs CLI" (Dev with IA)** (`docs/resource-evaluations/arnaud-gaches-mcp-vs-cli-devwithia.md`): Score 2/5. Community synthesis from the Dev with IA Slack/LinkedIn (1500+ devs). Key contributions: three-phase historical arc (browser 2022-23 → IDE+MCP 2024-25 → CLI agents 2025-26), update on MCP token cost (author claims unused servers now inject 0 tokens), model-size heuristic (frontier models → CLI, small local models → MCP), enterprise case for MCP Remote (centralized updates, observability). Scored 2/5 for lack of verifiable sources and unclear attribution. Applied: historical arc intro added to `guide/ecosystem/mcp-vs-cli.md`.

- **Guide update: historical arc intro in `mcp-vs-cli.md`** (`guide/ecosystem/mcp-vs-cli.md`): Two-sentence context paragraph added at the top explaining the interface evolution (browser → IDE+MCP → CLI agents, 2022-26) that frames why the MCP vs CLI question exists. Sourced from Arnaud Gaches community synthesis evaluation.

## [3.37.3] - 2026-03-20

- **New skill: `eval-skills`** (`examples/skills/eval-skills/SKILL.md`): Skills-only audit tool with integrated effort-level inference engine. Discovers all SKILL.md files + flat skill files in `.claude/skills/`, scores each across 6 criteria (15 pts: name, description quality, allowed-tools scope, effort field, content structure, tags), infers appropriate `effort` level from content signals (mechanical → `low`, bounded analysis → `medium`, adversarial/architectural → `high`), flags mismatches between declared and inferred effort, and outputs a copy-paste ready patch block for missing/wrong effort fields. Portable across projects — drop in `.claude/skills/` and run `/eval-skills`. Guide updated with comparison vs `/audit-agents-skills` in the Validating Skills section.

- **New skill: `smart-explore`** (`examples/skills/smart-explore.md`): Progressive code exploration using tree-sitter AST — structure first, drill second. Three approaches: (A) no-setup discipline with grep-based signature extraction, (B) tree-sitter CLI + lightweight Python script (50-150 tokens per file vs 2,000-5,000 for full reads), (C) MCP server options (mcp-server-tree-sitter for general use, code-review-graph for PR reviews, jCodeMunch for symbol lookup). Inspired by Alex Newman (Claude-MEM) + validated by Aider repo map pattern at 40k+ stars. Honest benchmarks: ~86% token reduction for module exploration, ~90% for feature-finding tasks.

- **Resource Evaluation — Tree-Sitter Progressive Code Exploration** (`docs/resource-evaluations/tree-sitter-progressive-code-exploration.md`): Score 4/5. Ecosystem evaluation of 5 tools implementing the AST-based progressive exploration pattern: jCodeMunch-MCP (~1,200 stars, 10-25% realistic savings, commercial $79+), mcp-server-tree-sitter/wrale (~270 stars, raw AST queries, Feb 2026), code-review-graph (~2,000 stars, 6.8x average for PR reviews, MIT), CodeRLM (192 stars, Claude autonomy problem), Aider repo map (reference implementation, 40k+ stars). Pattern fills genuine gap in guide (command savings via RTK are documented; code reading savings were not). Primary recommendation: code-review-graph for teams doing PR reviews (MIT, marketplace), mcp-server-tree-sitter for raw AST access, Approach B (script, no MCP) for solo workflows.

- **New guide section: Progressive Code Exploration (Smart Explore)** (`guide/ultimate-guide.md`): 110-line section added near the RTK token efficiency section. Explains the structure-first → target → cross-reference pattern with worked examples, CLAUDE.md snippet, and comparison table (RTK vs smart-explore vs grepai). Honest benchmarks: 86-92% token reduction for module exploration. Three approaches: no-setup grep discipline, tree-sitter CLI + Python script (50-150 tokens per file vs 2,000-5,000 for full reads), MCP server options. Skill file reference: `examples/skills/smart-explore.md`.

- **Resource Evaluation — Yagr (Y)our (A)gent (G)rounded in (R)eality** (`docs/resource-evaluations/2026-03-20-yagr-etienne-lescot.md`): Score 2/5. Watch list. Autonomous automation agent (n8n-as-code execution layer) that generates durable n8n workflows from natural language. Core differentiator is auditability: the workflow persists as an inspectable artifact instead of a disposable script. Scored down due to single-source evidence (author's own LinkedIn + README), star count misattribution (500+ stars belong to n8n-as-code, not Yagr itself), and unverified deploy claim. Re-evaluate in ~3 months if community traction materializes.

- **Claude Code releases tracking updated to v2.1.80** (`machine-readable/claude-code-releases.yaml`, `guide/core/claude-code-releases.md`): `rate_limits` field in statusline for Claude.ai rate limit usage (5h + 7d windows), `source: 'settings'` plugin marketplace (inline declarations in settings.json), `effort` frontmatter for skills/slash commands, `--channels` research preview (MCP servers push messages), fixed `--resume` dropping parallel tool results, ~80MB memory reduction on startup for large repos.

- **Fix: `.fastembed_cache/` added to `.gitignore`**: Prevents the FastEmbed model cache directory from being committed accidentally (generated by grepai/fastembed tooling).

- **Fix: `smart-suggest.sh` typo** (`examples/hooks/bash/smart-suggest.sh`): Corrected "mandato ry" → "mandatory" in the Tier 0 comment block.

## [3.37.2] - 2026-03-19

- **RSS Feed added to cc.bruniaux.com** (`landing: src/pages/rss.xml.ts`, `src/data/rss-entries.ts`): Unified RSS feed at `/rss.xml` merging Claude Code CLI releases and guide content updates (guide releases, new pages, new cards, new whitepapers). Auto-discovery `<link>` tag in all page heads, RSS icon in footer and "More" nav dropdown, mention in announcement banner. Dedicated `rss-entries.ts` data file for manual guide entries. Workflow integrated in `/release` (step 6.5 auto-drafts entry) and `/update-infos-release` (step 4.5 for notable CC releases). Post-push hook in landing repo reminds to update `rss-entries.ts`. README updated with RSS link.

- **Footer links fixed and expanded** (`landing: src/components/global/Footer.astro`): Architecture and Data Privacy now link to in-site guide reader (`/guide/core/architecture/`, `/guide/security/data-privacy/`) instead of GitHub raw files. Added missing pages: Recap Cards, AI Roles, Context, Ecosystem, FAQ.

- **Sitemap updated** (`landing: src/pages/sitemap/index.astro`): RSS Feed entry added in Reference section.

- **Fix — `/release` command updated with RSS step** (`.claude/commands/release.md`): Step 6.5 added — auto-drafts an `rss-entries.ts` entry from CHANGELOG after every release (patch included). Ensures feed stays current without manual effort.

- **Fix — Hook format updated to new matcher+hooks[] structure** (`examples/config/settings.json`, `examples/claude-md/learning-mode.md`, `~/.claude/settings.json`): Claude Code now requires hooks to use `{"matcher": "...", "hooks": [{...}]}` instead of the old flat `{"matcher": "...", "command": "..."}` format. Updated all example files and global settings accordingly.

- **New guide sections: Cross-Model Review, Lightweight Role-Switch, Task Sizing** (`guide/ultimate-guide.md`): Three gaps filled from resource evaluation gap analysis. (1) Cross-model review pattern after SE-CoVe section: generate with one model, review with another, with cost-effective patterns table and custom agent template. (2) Lightweight role-switch review as simpler alternative to SE-CoVe for everyday development. (3) Consolidated task sizing guidance in "Mixing Unrelated Tasks" section with splitting heuristic table and cross-reference to spec-first workflow.

- **Resource Evaluation -- Ischenko "You're probably using Claude Code wrong"** (`docs/resource-evaluations/ischenko-claude-code-workflow-quality.md`): Score 2/5 (marginal, do not integrate). LinkedIn article proposing 7 workflow patterns (reality checks, author/reviewer separation, project-aware reviews, requirements artifacts, TDD, small tasks, human elevation) with copy-paste prompt templates. 75-85% overlap with existing guide content (SE-CoVe, spec-first.md, tdd-with-claude.md, exploration-workflow.md). Headline "30% quality improvement" claim has no methodology. Only non-redundant element: the 7 prompt templates, which are formatting convenience rather than new insight. Two independent gaps surfaced for future work: multi-model review pattern (near zero coverage in guide) and consolidated task sizing section.

- **Claude Code releases tracking updated to v2.1.79** (`machine-readable/claude-code-releases.yaml`, `guide/core/claude-code-releases.md`): `--console` flag for `claude auth login` (API billing auth), Show turn duration toggle in `/config`, VSCode `/remote-control` command + AI-generated session tab titles, fixed `claude -p` hanging without explicit stdin, enterprise 429 retry fix, SessionEnd hooks on `/resume` session switch, ~18MB startup memory improvement.

- **Resource Evaluation — Multi-Session Management Landscape** (`docs/resource-evaluations/082-multi-session-management-landscape.md`): Score 4/5. Landscape overview of 13 tools across 4 categories for managing multiple Claude Code sessions across multiple projects. Monitoring dashboards: ccm (212 stars, TUI + mobile WebUI), sniffly (1 170 stars, analytics), claude-code-dashboard (token/cost per session). Remote access: vibetunnel (4 276 stars), cc-hub (color themes + file diffs). Orchestrators: claudio (22 stars, isolated worktrees + 14 color themes + planning modes), multi-agent-shogun (1 082 stars, tmux fan-out hierarchy). Sound/notifications: no packaged per-project audio solution — DIY via `settings.local.json` + `afplay` hook per project. Recommends integrating a "Multi-Session Management" section in the guide's third-party tools coverage.

- **Resource Evaluation — obra/Superpowers** (`docs/resource-evaluations/obra-superpowers-evaluation.md`): Score 5/5. Full software development methodology suite (95k+ stars, 7.5k forks, verified via GitHub API). 7 context-aware skills: brainstorm-first spec gate, implementation planning, subagent-driven development with two-stage review, mandatory TDD enforcement, code review, git worktrees, branch lifecycle. Available on official Claude Code plugin marketplace. Integrated in 4 locations: Plugin Ecosystem section in `third-party-tools.md` (alongside gstack), obra row upgrade in `ultimate-guide.md` skills.sh table, cross-reference in `tdd-with-claude.md`, cross-reference in `spec-first.md`.

- **Resource Evaluation — ManoMano "Project Aegis"** (`docs/resource-evaluations/2026-03-19-manomano-project-aegis-serena.md`): Score 3/5. ManoMano engineering team benchmarked AI coding agents internally and identified Serena MCP as a must-have for large codebase navigation. Serena (oraios/serena) uses LSP for deterministic symbol-level navigation (find_symbol, get_symbols_overview, session memory) — distinct from GrepAI's embedding approach. Guide already covers Serena extensively (8+ files, `ultimate-guide.md:10527`, `search-tools-mastery.md`). Specific gap confirmed: no Serena entry in `mcp-servers-ecosystem.md` (only GrepAI listed under Code Search), creating a discoverability inconsistency. Recommended action: add formal Serena entry to ecosystem file with cross-link to search-tools-mastery.md.

## [3.37.1] - 2026-03-18

- **Threat database updated to v2.8.0** (`examples/commands/resources/threat-db.yaml`): 7 new entries covering March 2026 threats. **New campaigns**: GhostClaw (malicious npm `@openclaw-ai/openclawai`, GhostLoader RAT with SOCKS5 proxy + clipboard monitor, 178 downloads) and Fake OpenClaw Installer (Stealth Packer + GhostSocks via malicious GitHub repos indexed by Bing AI). **New malicious packages**: `@openclaw-ai/openclawai` and `ambar-src` (~50K downloads, evasion techniques). **New CVE**: CVE-2026-24910 (Bun runtime v<1.3.5, lifecycle scripts bypass origin validation). **New attack techniques**: T017 Shadow MCP (employees deploying unvetted MCP servers without IT oversight) and T018 AI Search Result Poisoning (AI-generated search results recommending malicious repos). **New scanning tools**: Jozu Agent Guard (zero-trust AI runtime, non-bypassable policies, 2026-03-17) and MCP Sentinel (RSAC 2026, request/arg scanning for sensitive data). `minimum_safe_versions` updated with `bun: 1.3.5`.

- **Claude Code releases tracking updated to v2.1.78** (`machine-readable/claude-code-releases.yaml`, `guide/core/claude-code-releases.md`): StopFailure hook event, ${CLAUDE_PLUGIN_DATA} persistent plugin state, effort/maxTurns/disallowedTools frontmatter for plugin agents, streaming line-by-line, 3 security fixes (silent sandbox disable, MCP deny rules bypass, protected dirs writable in bypassPermissions mode).

- **Skill descriptions improved — 19 skills updated** (`examples/skills/`): cleaner, action-oriented descriptions with explicit "Use when" triggers. Selective merge from @popey (Tessl) PR #9: kept improved `description:` lines while preserving full reference documentation in template skills.

- **Fix — MCP vs CLI token overhead claim updated** (`guide/ecosystem/mcp-vs-cli.md`): corrected outdated token cost figures following v2.1.7 MCP Tool Search (lazy loading). "Token cost of MCP schemas" section rewritten with lazy loading mechanics and measured 85% reduction benchmark (55K → 8.7K for 5-server setup). Credit: Antoine Salesse.

- **Resource Evaluation #081 — Rippletide Code** (`docs/resource-evaluations/081-rippletide-code-rule-enforcement.md`): hook-native runtime rule enforcement for Claude Code (score 3/5, integrate with caveats). Addresses the CLAUDE.md degradation problem: rules ignored after 40+ entries, lost after context compaction.

- **New self-assessment section — Agent Adoption Curve** (`guide/roles/learning-with-ai.md`): 7-level maturity scale (0-6) for developers to self-locate on the Claude Code sophistication spectrum, adapted from Nicolas Martignole (Back Market) maturity framework.

- **New guide section §5.5 — Registry-based Discovery: ctx7 CLI** (`guide/ultimate-guide.md`): Context7's CLI companion (`npx ctx7`) for automated skill discovery and MCP setup. Resource evaluation: `docs/resource-evaluations/2026-03-17-context7-cli.md` (score 4/5).

- **Resource Evaluations #079 + #080** (`docs/resource-evaluations/`): Fabro workflow orchestration (3/5, Watch) and Goose by Block update (4/5) with stats refresh (15.4k → 33k stars), Recipes section, and subagent orchestration documentation.

- **Doc audit — stats sync**: corrected stale counts. Templates unified to 217. Guide lines: "22K" → "23K+". Quiz: 311 → 271.

## [3.37.0] - 2026-03-17

- **ICM v0.5.0 — setup guide + session starter template**: corrected `icm init` documentation (3 explicit modes: `--mode mcp`, `--mode hook`, `--mode skill` — not a single interactive command); fixed CLI syntax (`--importance` is an enum `critical|high|medium|low`, not a float; no `memory` subcommand); added `examples/memory/icm-session-starter.md` ready-to-use onboarding prompt to paste at the start of any session.

- **New guide section — MCP vs CLI Decision Guide** (`guide/ecosystem/mcp-vs-cli.md`): full comparison of MCP servers vs CLI tools across 4 decision dimensions (user type, model capability, observability needs, schema stability), decision matrix by situation, token cost analysis, tooling overview (RTK, MCPorter, mcp2cli), and practitioner quotes. Cross-linked from `mcp-servers-ecosystem.md`. Landing page published at `cc.bruniaux.com/ecosystem/mcp-vs-cli/` with 4 decision cards, 15-row collapsible guidance table, practitioner quotes section, and tooling micro-section. `check-landing-sync.sh` extended with section 7 for MCP vs CLI sync tracking.

- **Resource evaluations (3)**: mcp2cli (3/5, MCP/OpenAPI/GraphQL to runtime CLI, 96-99% token savings claim, 8-day-old tool with structural mismatch against Claude Code native MCP architecture — watch list + document schema overhead insight); MCPorter by Steinberger (3/5, TypeScript MCP toolkit with auto-discovery, CLI generation and TS codegen — useful companion for testing MCP servers and hook scripts); CircleCI MCP vs CLI blog (3/5, inner loop / outer loop decision framework, 6-question guide, directional browser automation benchmark — worth borrowing the vocabulary, not the benchmark numbers).

- **WP10 v1.2.0 — Marc Sélince feedback (DAF/finance)**: 6 corrections FR+EN on `10-budget-ia.qmd` / `10-ai-budget.qmd`. New `## Pour le DAF/CFO` section (ROI + OpEx/CapEx framing, replaces placeholder callout). New `## Freins COMEX au-delà du coût` Q&A section (vendor dependency, IP risk, lock-in pricing). §3.1 reframed "Attraction et rétention des top performers" (market tight for seniors/experts, not all profiles). §3.2 CTO: new "ROI des heures d'ingénieur" sub-point (LLMs on mechanical code free engineering time for architecture). §4.1 Budget: option 4 added (replace paid tool with OS equivalent for net-zero pilot), "200-500$/mois" figure removed from discretionary budget.

- **Recap cards — EN translations created + FR fixes**: 57 EN recap cards created from scratch (`whitepapers/recap-cards/en/`) by translating all FR cards. FR cards batch-updated: `guide-version` and `version` fields bumped `3.32.1` → `3.36.0` across all 57 FR cards. Factual fixes: T19 (context window) corrected "1M beta, API only" → "1M GA for Max/Team/Enterprise CC plans (v2.1.75, no header needed)"; T01 (essential commands) updated with `/plan`, `/effort`, `/branch`, `/rename`, `/loop`, `/voice`, `/fast`, removed non-existent `/cost`, corrected keyboard shortcuts. `docs/for-cto.md` updated: "whitepapers coming soon" → links to `florian.bruniaux.com/guides` in all 4 occurrences.

- **Fix dead link** (`guide/ultimate-guide.md` §3.5): Packmind anchor `../ecosystem/third-party-tools.md#packmind` corrected to `ecosystem/third-party-tools.md#packmind` (wrong `../` prefix was resolving outside `guide/`).

- **Whitepapers v2.2 — Guide content sync (7 WPs updated)**: synced WP content with guide v3.27.6 → v3.36.0 delta.
  - **WP00** (v1.2.0): 1M context corrected "beta" → GA (v2.1.75); 7 major features table added (Tasks API, Auto-memories, Agent Teams, LSP Tool, Remote Control, MCP Elicitation)
  - **WP03** (v1.1.0): PreToolUse security fix callout (v2.1.77 — `"allow"` bypassed enterprise `deny`); `allowRead` sandbox parameter added
  - **WP05** (v1.2.0): Native Code Review section (Research Preview, Teams/Enterprise) — multi-agent, 3 trigger modes, `REVIEW.md`, ~$15-25/PR pricing
  - **WP07** (v1.1.0): 12 new slash commands, 7 new hook events, extended CLI flags, Remote Control section, 1M GA correction
  - **WP08** (v1.2.0): Identity drift after compaction pattern added (UserPromptSubmit hook + agent-identity.txt re-injection)
  - **WP09** (v1.1.0): Review bottleneck inversion section; Regulatory Exposure section (EU AI Act GPAI/high-risk, FDA AI/ML Guidance)
  - WP02: no hook events section in scope; WP01/WP04/WP06/WP10: no gaps identified

- **Cheatsheet + reference.yaml maintenance**: date updated February → March 2026 in `guide/cheatsheet.md`; "Command not found" fix updated to use native installer (`curl | sh`); `machine-readable/reference.yaml` `updated` field bumped to 2026-03-17.

- **Whitepapers v2 — Reviewer corrections** (6 relecteurs: Edouard, Mat, Nicolas, Marc, Anthony, Emmanuel): 8-phase correction plan applied across 10 whitepapers (WP00–WP10) FR+EN.
  - **Phase 1 — Factual errors**: npm "deprecated" → "not recommended" (WP00), native installer added as primary install method (WP00 EN), context window 200K vs 1M clarified (WP00 FR+EN), Claude Max ratio corrected to range 1.5-3% FR / 1-1.6% EN (WP10), sub-agents vs agent teams difference correctly stated as P2P messaging + coordination tools, not context isolation (WP08 EN)
  - **Phase 2 — Accents + articles + typos**: ~200+ accent corrections across WP08 FR (977 lines); anglicisms corrected in WP02 FR (on-demand, per-project, Memories, Feature opt-in); table row reformulated in WP00 FR; accents restored in WP02 FR (~10 passages)
  - **Phase 3 — Malformed sentences**: "chez dans une fintech" fixed, meta-sentence "This is the single definition..." removed (WP08 FR+EN); "Multiple Claude instances..." rewritten as complete sentence (WP05 FR+EN); Turnkey Quickstart explained (WP05 FR+EN)
  - **Phase 4 — Anglicisms + clarifications**: tmux noted as external tool, not built-in (WP08 FR+EN); "OUI →" residue fixed in WP05 EN; user-level/project-level translated (WP05 FR)
  - **Phase 6 — WP08 structural corrections**: "~30K lines" clarified as "~30K lines ≈ 1M tokens"; continuous merge definition improved; note added that solo Claude Code agent is a full autonomous agent, not a chatbot
  - **Phase 7 — WP10 restructuration**: executive summary added (5 key metrics); learning curve duplication removed; BCG 2025 source improved; pricing note "March 2026" added; "5-10 people in 2020" reformulated without unsourced claim; "Beyond engineering teams" section expanded with 3 concrete use cases; CFO/DAF and change management placeholder callouts added

- **Resource Evaluation #078 + integration** (`guide/ultimate-guide.md`): HumanLayer — "Skill Issue: Harness Engineering for Coding Agents" (March 12, 2026). Score 3/5. "Harness Engineer" concept already covered in `guide/roles/ai-roles.md §10` (Martin Fowler source); ETH Zürich study already integrated. Two genuine gaps filled: (1) **Silent Success hook pattern** — asymmetric hook behavior (exit 0 = silence, exit 2 = re-engage agent) named and documented with example before §7.3; (2) **CLI vs MCP training-data argument** — familiar CLIs (git/grep/jq) are already in model weights, CLAUDE.md usage examples often beat a verbose MCP server for standard tools; added after MCP Tool Search section.

## [3.36.0] - 2026-03-17

### Documentation

- **Resource Evaluation #076**: Addy Osmani — "Stop Using /init for AGENTS.md" (Feb 23, 2026). Score 3/5. Secondary synthesis of ETH Zürich paper (already evaluated). Verified: ETH Zürich claims confirmed. Unverified: Lulla et al. (ICSE JAWs 2026) and ACE framework (ICLR 2026) — no findable academic source. Arize AI concept verified, specific numbers uncorroborated. Integration: added discoverability filter + anchoring risk concepts to §3.1, added research note (ETH Zürich), added `/init` warning in commands table.

- **Resource Evaluation #077 + integration** (`guide/roles/learning-with-ai.md`): "Comprehension Debt" article (LinkedIn, March 14, 2026). Score 3/5. Integrated: (1) "comprehension debt" as emerging term after Vibe Coding section, (2) review bottleneck inversion framing — juniors can now generate code faster than seniors can audit, (3) new "Regulatory Exposure" subsection for tech leads covering EU AI Act active dates (GPAI Aug 2025, high-risk Aug 2026) and FDA AI guidance (Jan + Jun 2025). Confirmed by Perplexity research.

- **Claude Code Releases**: Updated tracking to v2.1.77
  - Opus 4.6 default max output raised to 64k tokens; upper bound for Opus 4.6 and Sonnet 4.6 raised to 128k tokens
  - Security fix: `PreToolUse` hooks returning `"allow"` could bypass enterprise `deny` permission rules
  - `allowRead` sandbox setting; `/branch` replaces `/fork`; `/copy N` for Nth-latest response
  - Breaking: `Agent` tool `resume` parameter removed — use `SendMessage({to: agentId})` instead
  - Fixed auto-updater GBs memory leak; fixed `--resume` truncating recent history

- **Claude Code Releases**: Updated tracking to v2.1.76
  - MCP elicitation support — servers request structured input mid-task via interactive dialog
  - New hooks: `Elicitation`, `ElicitationResult`, `PostCompact`
  - `-n`/`--name` CLI flag for session display name; `worktree.sparsePaths` for monorepo sparse checkout
  - `/effort` slash command; fixed ToolSearch deferred tools losing schemas after compaction
  - Auto-compact circuit breaker (stops after 3 failures); fixed `Bash(cmd:*)` rules with `#` in args

- **Resource evaluation** (rejected, no file): LinkedIn post "Five Levels of Context Engineering" by Matthew Alverson (via Addy Osmani) — score 1/5, rejected. Content is a pedagogical reformulation of concepts already covered with more rigor in `guide/core/context-engineering.md`. Alverson's 5-level taxonomy is not empirically grounded and not widely cited in the literature. Evaluation surfaced 3 real gaps now addressed (see Added section). Better primary sources identified: Anthropic Engineering Blog (Sept 2025), MCP Maturity Model (Mitra, Nov 2025).

- **Resource evaluation** (no file — text digest): Anthropic weekly recap March 9-15, 2026 (5 Claude Code releases, Code Review launch, 1M GA, Spring Break promo, corporate news) — score 4/5. Two gaps actioned: (1) Code Review product feature added as `guide/workflows/code-review.md`; (2) 1M context status updated from beta to GA in `guide/ultimate-guide.md` lines 2021-2070. Source reliability note: digest incorrectly attributes Claude Code changelog to `anthropics/anthropic-sdk-python` (correct repo: `anthropics/claude-code`); Code Review pricing ($15-25/PR) verified against official docs.

- **Resource evaluation** (`docs/resource-evaluations/eval-claude-1m-context-window-jp-caparas.md`): JP Caparas article on 1M token context window — score 2/5, do not integrate. Central claim (flat pricing, no surcharge above 200K tokens) is factually wrong; invalidates the competitive pricing analysis. Fact-check table, comparative analysis vs guide, and independent action items (verify 1M GA status, potential update to guide lines 2028-2070 on beta/GA status).

### Changed

- **External support section — clarified positioning** (`docs/for-cto.md`, `docs/for-tech-leads.md`, `docs/for-cio-ceo.md`): Brown Bag Lunch, talks, and speaker/panelist slots (1-3h) explicitly marked as free and done for networking/challenge purposes. Training/consulting missions framed as open-but-not-actively-sought with "contact for availability and potentially pricing" wording. Contact link updated to `florian.bruniaux.com` across all three files.

### Fixed

- **`/release` skill — 3 correctness gaps** (`.claude/commands/release.md` Step 4): (1) Quiz count command fixed: `grep -c '  - id:'` was returning per-file counts and taking only the last file's value — replaced with `grep -r '  - id:' quiz/questions/ | wc -l` to sum across the entire directory. (2) `llms-full.txt` now documents all 4 occurrences requiring update (Metadata block, "For Learning" URL text, "Template Library" section heading, repo tree comment) — previously only Metadata fields were listed, causing silent drift. (3) Verification gate added after Step 4: bash block prints all three llms files' key fields side-by-side against expected values before the commit, making any mismatch visible immediately.

### Added

- **Resource evaluation #078: claude-swarm-monitor** (`docs/resource-evaluations/078-claude-swarm-monitor.md`): TUI dashboard (Rust + Ratatui) for monitoring multi-agent Claude Code workflows across git worktrees. Score 3/5 — watch-list. Unique angles: JSONL-native session file monitoring (distinct from agent-chat's SSE approach) and Docker stack visibility per worktree. Not integrated into guide yet — 10 stars, Linux-only, sub-agent tracking claim unverified. Re-evaluate at 50+ stars or confirmed macOS production use.

- **Packmind — Engineering Standards Distribution** (`guide/ecosystem/third-party-tools.md`, `guide/ultimate-guide.md`, `guide/ecosystem/mcp-servers-ecosystem.md`): Added Packmind (score 4/5, eval #076) as a new "Engineering Standards Distribution" section in third-party-tools. Tool distributes CLAUDE.md + slash commands + skills across repos and agents (Claude Code, Cursor, Copilot, Windsurf) from a single playbook, ships an MCP server, Apache-2.0 CLI self-hostable. Added cross-reference paragraph at end of ultimate-guide.md §3.5 (Team Configuration at Scale) linking the per-project `.claude/rules/` pattern to org-scale tooling. Added Packmind MCP server entry in mcp-servers-ecosystem.md Orchestration section.

- **3 new AI roles** (`guide/roles/ai-roles.md`): Added MLOps Engineer (§14), AI Developer Advocate (§15), and AI Orchestration Engineer (§16) as full role profiles. Includes responsibilities, required skills, salary benchmarks, entry paths, and key distinctions from adjacent roles. Sections 14→17 renumbered accordingly. Removed "Orchestration engineer" from "What's Not a Role Yet" — job postings at Vista Equity, Zapier, Heidi Health, and Adobe confirm it's now a real title. Career Decision Matrix and Salary Benchmarks updated with all 3 roles. Based on Perplexity market research (March 2026).

- **Failure-triggered context drift pattern** (`guide/core/architecture.md` §Session Degradation Limits): New subsection documenting a distinct degradation mode from compaction drift — repeated tool failures accumulate error noise that dilutes the original intent without filling the context window. Pattern: re-inject core task instructions on every command failure via `PostToolUse` hook, not just after `/compact`. Source: Nick Tune (2026-03-01). Resource evaluation: `docs/resource-evaluations/2026-03-16-nick-tune-workflow-dsl-ddd.md` (score 3/5 — 1 of 3 patterns integrated).

- **Identity re-injection after compaction** (`guide/ultimate-guide.md` §7.5 + `examples/hooks/bash/identity-reinjection.sh`): New hook pattern from Nick Tune (Feb 2026). Solves agent identity drift after context compaction in long sessions — `UserPromptSubmit` hook reads transcript, detects missing identity marker in last assistant message, re-injects `.claude/agent-identity.txt` as `additionalContext`. Configurable via `CLAUDE_IDENTITY_FILE` and `CLAUDE_IDENTITY_MARKER` env vars. `reference.yaml` updated with `identity_reinjection_hook` + `identity_reinjection_example` keys.

- **Security audit hardening — 3 patterns** (`examples/commands/security-audit.md`, `examples/agents/security-auditor.md`): (1) Pre-step added to `/security-audit`: asks dev/staging/prod before running — avoids false positives on debug flags and CORS `*` in local dev. (2) Anti-false-positive rule in Phase 2 (secrets scan): mandates running `git log --all -p` and checking `.gitignore` before raising any secret finding — no more findings based on pattern matching alone. (3) Paywall/billing checklist added to `security-auditor.md` under A04 Insecure Design: server-side limit enforcement, subscription status from DB, webhook signature verification, billing bypass endpoints, race conditions on resource creation.

- **Resource evaluation: VicKayro — claude-security-audit** (`docs/resource-evaluations/2026-03-16-vickairo-claude-security-audit.md`): Score 2/5. Single-file `/security-audit` command, OWASP Top 10 (2021) + 16 sections, MIT, 60 stars (18 days old). Substantial overlap with existing `security-audit.md`, `security-auditor.md`, and `security-hardening.md`. Genuine gaps: paywall/billing audit section (not covered anywhere), environment context pre-step (dev/staging/prod before auditing), and stricter anti-false-positive pattern for secrets (mandate `git log --all -p` proof before raising finding). Decision: extract 3 patterns into existing commands silently, no guide mention, revisit at 200+ stars.

- **Resource evaluation: Nick Tune — Hook-Driven Dev Workflows** (`docs/resource-evaluations/2026-03-16-nick-tune-hook-driven-workflows.md`): Score 3/5. Covers hooks-as-workflow-engine pattern: typed state machine (Zod), per-state SubagentStart context injection, agent respawn for fresh context windows, identity re-injection after compaction, JSON workflow persistence. Key gap confirmed: guide lacks identity re-injection after compaction + per-state SubagentStart injection. Tiered integration: identity re-injection → §7.5 now; SubagentStart injection → agent-teams.md (3-4 weeks); full state machine guide deferred 60-90 days (1 week of author testing, needs community validation). Prerequisites: CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1, Opus 4.6, Node.js + TypeScript.

- **1M context window status update** (`guide/ultimate-guide.md` lines ~2021-2070): Updated from "beta" to GA for Max/Team/Enterprise Claude Code plans (v2.1.75, March 13 2026). Preserved distinction: direct API use still requires tier 4 / custom rate limits. Pricing table updated to reflect standard rates for plan users.

- **Code Review feature** (`guide/workflows/code-review.md` + cross-reference in `guide/ultimate-guide.md`): New workflow guide for Anthropic's Code Review research preview (Teams/Enterprise). Covers: multi-agent architecture and severity levels (🔴/🟡/🟣), full setup flow (admin URL `claude.ai/admin-settings/claude-code`, GitHub App permissions, 3 trigger modes — once/every push/manual), `@claude review` manual trigger, `REVIEW.md` schema with example, pricing model ($15-25 avg, billed via extra usage outside plan, spend cap at `claude.ai/admin-settings/usage`), analytics dashboard, and cross-links to manual CLI workflows + GitLab CI/CD. Verified against official docs at `code.claude.com/docs/en/code-review`.

- **Context engineering guide — 3 additions** (`guide/core/context-engineering.md`):
  - **"Most failures are context failures"** framing added to §1 Why It Matters — reframes troubleshooting from "the AI is bad" to "what's missing from context"
  - **Static vs. Dynamic context** — new subsection distinguishing CLAUDE.md (static) from runtime tool outputs and agent context (dynamic); includes reference to Anthropic's September 2025 engineering post on agent context engineering
  - **Maturity assessment §9** — Level 0-5 self-assessment grid grounded in Claude Code patterns (no CLAUDE.md → flat config → structured → modular → measured → full system); includes "what to do at each level" action table

- **Spring Break promotion note** (guide line ~2395): Documented Anthropic's March 13-27, 2026 promotion — 2x usage limits outside 5-11am PT (peak hours) and all weekends, bonus usage doesn't count against weekly limits, applies to Free/Pro/Max/Team. Includes CET timezone conversion for European users (2x from midnight-13h and 19h-24h France time). Source: Anthropic support article.

- **Smart-Suggest ROI script** (`examples/scripts/smart-suggest-roi.py`): Python stdlib-only analyzer for the `smart-suggest` UserPromptSubmit hook. Correlates suggestion log (`~/.claude/logs/smart-suggest.jsonl`) with session JSONL files to estimate command acceptance rate. Detects 4 acceptance signals: slash command tags, Skill tool use, Agent tool use, and text mention in next 5 user messages. Reports: summary, tier breakdown (Enforcement/Discovery/Contextual/Custom), top suggested/followed commands, never-followed list, and daily trend chart. CLI: `--since Nd`, `--no-sessions` (fast mode), `--json`, `--log PATH`.
- **ICM (Infinite Context Memory)**: New MCP memory server section after Kairn (~line 11365) — Rust single binary, zero deps, Homebrew install, dual architecture (episodic decay Memories + permanent knowledge graph Memoirs), 9 typed relation types, auto-extraction 3 layers, 14 editor clients. Score 3/5 — recommended as Rust-native alternative when Python dependency management is a friction point. Includes explicit license callout (Source-Available, free ≤20 people) and vendor-reported benchmark flags.
- **Comparison matrix update**: Added ICM column to MCP memory stack matrix (Runtime + License rows added for all tools)

## [3.35.0] - 2026-03-13

### Added

- **`guide/workflows/github-actions.md`** — 5 production-ready patterns for GitHub Actions CI/CD with `anthropics/claude-code-action` (6.2k stars, v1.0): on-demand PR review via `@claude` mention, automatic review on every push, issue triage and labeling, security-focused review on sensitive paths (`auth/**`, `payments/**`), scheduled weekly repo health check. Includes cost control table (Haiku vs Sonnet per pattern), concurrency setup, fork safety (`pull_request_target` guard), Bedrock/Vertex auth alternatives. Cross-linked from guide §9.3 and `guide/workflows/README.md`.

- **`guide/workflows/rpi.md`** — RPI: Research → Plan → Implement. 3-phase feature development with explicit GO gates: Research → `RESEARCH.md`, Plan → `PLAN.md`, Implement → working code. Slash command templates (`/rpi:research`, `/rpi:plan`, `/rpi:implement`), worked example (rate limiting on Express API), and comparison matrix vs Plan-Driven, TDD, Spec-First. Best for features where discovering a wrong assumption late is expensive.

- **`guide/workflows/changelog-fragments.md`** — Changelog Fragments workflow: one YAML fragment per PR, written at implementation time, validated by CI, assembled at release. 3-layer enforcement: CLAUDE.md workflow rule + `UserPromptSubmit` hook (3-tier: enforcement → discovery → contextual) + independent CI migration check. Documents the `UserPromptSubmit` tier pattern as a reusable architecture for any mandatory workflow step.

- **`examples/hooks/bash/smart-suggest.sh`** — `UserPromptSubmit` behavioral coach hook: Tier 0 enforcement (changelog fragment required before PR, plan-before-code), Tier 1 discovery (test-loop, retex, dupes, monitoring loop, security audit, release), Tier 2 contextual (code review, debugging, architecture, session resume). Max 1 suggestion per prompt, dedup guard, ROI logging to `~/.claude/logs/smart-suggest.jsonl`, silent exit on no match.

- **`guide/core/known-issues.md`** — "LLM Day-to-Day Performance Variance" section: session-to-session quality variance (shorter responses, conservative suggestions, edge-case refusals) documented as expected behavior, not a bug. 4 root causes: probabilistic inference, MoE routing variance, infrastructure variance, context sensitivity. Observable signals table and ruling-out checklist.

- **`examples/scripts/test-prompt-caching.ts`** — Standalone TypeScript script (zero deps, native fetch) to verify Anthropic prompt caching on any API key. Runs 3 identical calls, checks write/read metrics. Documents 4 undocumented production gotchas: `anthropic-beta: prompt-caching-2024-07-31` header required for Claude 4.x, effective threshold ~2048+ tokens, cached tokens excluded from `input_tokens`, new nested `cache_creation` object format.

- **`cc-sessions discover` documentation** — "Session Pattern Discovery" subsection in §2.x: `discover` subcommand n-gram mode (local, ~3s) vs `--llm` mode (semantic via `claude --print`), 20% rule decision framework (CLAUDE.md rule / skill / command), install instructions. Cross-reference added after the 20% rule callout in §5.1.

- **`examples/scripts/cc-sessions.py`** — Synced from 498-line stale copy to full 1225-line version from `~/bin/cc-sessions`: complete `discover` subcommand, incremental cache, Jaccard deduplication, all filtering logic. GitHub source header added.

- **GitHub repo [FlorianBruniaux/cc-sessions](https://github.com/FlorianBruniaux/cc-sessions)** — v1.0.0 published with curl install instructions.

### Updated

- **`guide/ultimate-guide.md`** — Two additions: cross-reference callout to `github-actions.md` in CI/CD section; "Fighting Vibe Code Degradation" subsection covering desloppify ([peteromallet/desloppify](https://github.com/peteromallet/desloppify)) — scan → next → fix → resolve loop as a Claude Code skill, early-stage (Feb 2026, ~2K stars), token cost caveat.

- **`examples/commands/resources/threat-db.yaml`** — v2.7.0 (2026-03-13). +5 threat sources: CVE-2026-26118 Azure MCP Server SSRF (THN/Tenable), OpenClaw agentic AI risk (ReversingLabs), Taskflow Agent scanner (GitHub Security Lab), OpenAI Codex Security research preview, DryRun Security 87% vulnerability rate in AI-built PRs.

- **`CLAUDE.md`** — "Behavioral Rules" section: 5 rules from observed session friction: always update CHANGELOG.md, exhaustive first pass, absolute paths, closing checklist, bias toward action.

- **`examples/scripts/README.md`** — cc-sessions entry updated with `discover` subcommand examples, GitHub repo link, curl install instructions.

- **`machine-readable/reference.yaml`** — Added `cc_sessions_github`, `cc_sessions_discover`, `changelog_fragments_*`, `smart_suggest_hook`, `rpi_*` entries.

## [3.34.11] - 2026-03-13

### Updated

- **`guide/ultimate-guide.md`** (§ Cost Optimization → Strategy 6): Added `#### How Claude Code Handles Caching Automatically` subsection (~75 lines) covering the mechanics that were previously a single undocumented footnote. New content: (1) **Cache prefix hierarchy** — `tools → system → messages` ordering and why the first two layers almost always hit; (2) **20-block lookback** — the long-session cache degradation trap and why `/compact` restores hit rates; (3) **Minimum token thresholds by model** — eligibility table for Opus/Sonnet/Haiku families (1,024–4,096 tokens), correcting the previously circulating false "32,000 token maximum" claim; (4) **Tool result size and cache economics** — why compact tool outputs reduce both cache write and read costs proportionally across the entire session; (5) **Monitoring in custom pipelines** — `cache_creation_input_tokens` / `cache_read_input_tokens` response fields, hit rate calculation formula, and why no dedicated CC cache monitoring tool currently exists; (6) **Practical rules** — CLAUDE.md stability, pre-emptive `/compact` timing, avoiding dynamic content in stable sections.

## [3.34.10] - 2026-03-13

### Added

- **Quiz expanded: 277 → 311 questions (+34)** — 33 new questions covering topics added since the last quiz audit, across 9 categories: `modelOverrides`/`autoMemoryDirectory` settings (v2.1.73-74), tool-qualified deny format `Read(file_path:*.env*)`, CLAUDE.md HTML comment hiding (v2.1.72), `spinnerVerbs`/`spinnerTipsOverride` terminal personalization, team config at scale (N×M×P fragmentation, 59% token reduction), `/loop`/`/simplify`/`/batch`/`/stats`/`/rename` commands (v2.1.63-71), `WorktreeCreate`/`WorktreeRemove`/`TeammateIdle`/`TaskCompleted` hook events (v2.1.50 + v2.1.32+), auto-rename-session hook pattern, Git MCP vs GitHub MCP (12 local tools vs remote Copilot-required), Context Engineering 150% ceiling + ACE pipeline, Plan-Validate-Execute 3-command workflow, dual-instance planning (Jon Williams, $100-200/month), `isolation: "worktree"` in agent frontmatter, simplified effort levels ○◐● (v2.1.72, max removed), Fast mode (2.5x faster/6x price), `model` parameter restored on Agent tool (v2.1.72), `/context` actionable suggestions (v2.1.74), METR RCT 2025 (19% slower on large codebases), Borg "Echoes of AI" RCT 2025 (30.7% faster, no maintainability regression), Contribution Metrics platform feature (+67% PRs/day), enterprise governance 4 guardrail tiers (Starter/Standard/Strict/Regulated), MCP governance workflow + YAML registry, native sandbox OS primitives (macOS Seatbelt vs Linux bubblewrap), `dangerouslyDisableSandbox` escape hatch, RTK (60-92% token reduction, TOML Filter DSL), Google Antigravity (agent-first IDE). 1 question corrected: `12-architecture-internals/002` updated to reflect Tasks API replacing TodoWrite (v2.1.16+).
- **Quiz counters synced**: `machine-readable/reference.yaml` (`quiz_count: 311`), `llms.txt` + `llms-full.txt` + `machine-readable/llms.txt` (`Quiz Questions: 311`).

## [3.34.9] - 2026-03-13

### Added

- **`guide/workflows/gstack-workflow.md`** — New workflow guide (140 lines) documenting the "Cognitive Mode Switching" pattern: switching between specialist roles across the ship cycle (strategic gate → architecture → paranoid review → release → browser QA → retrospective). Reference implementation: [gstack](https://github.com/garrytan/gstack) by Garry Tan (YC CEO). Covers the 6 gears table, the pre-implementation strategic gate concept ("are we building the right thing?"), `/browse` non-MCP native browser architecture (persistent Chromium daemon, ~100ms/cmd vs MCP), full cycle demo, and when to use vs Plan Pipeline.

- **`examples/commands/plan-ceo-review.md`** — New command template for the strategic product gate. Three modes: SCOPE EXPANSION (find the 10-star product), HOLD SCOPE (make the plan bulletproof), SCOPE REDUCTION (strip to MVP). Includes full prompt template, concrete example (photo upload → smart listing creation), and integration notes. Inspired by gstack's `/plan-ceo-review` skill.

- **`examples/commands/plan-eng-review.md`** — New command template for the engineering architecture gate. Forces diagram generation (architecture, sequence, state machine), sync/async boundary decisions, failure mode inventory, trust boundary map, and test matrix before implementation. Includes Mermaid diagram examples and integration notes. Inspired by gstack's `/plan-eng-review` skill.

### Updated

- **`guide/workflows/README.md`**: Added Cognitive Mode Switching entry to Development Workflows section. Added two rows to Quick Selection Guide: "Strategic gate before coding" and "Non-MCP browser automation".

- **`guide/ecosystem/third-party-tools.md`** (Plugin Ecosystem section): Added gstack as the first entry under a new "Notable skill packs" subsection, with cross-reference to the workflow guide.

## [3.34.8] - 2026-03-12

### Added

- **`examples/hooks/bash/smart-suggest.sh`** — Production-ready `UserPromptSubmit` hook implementing a 3-tier behavioral coaching architecture (Tier 0: enforcement, Tier 1: discovery, Tier 2: contextual). Features: max 1 suggestion per prompt, dedup guard (never suggests a command already in the prompt), JSONL ROI logging to `~/.claude/logs/smart-suggest.jsonl`, and silent exit on no match. Includes changelog fragment enforcement as the canonical Tier 0 example (conditional "if PR-intent without fragment-mention" pattern), plus 10 additional patterns across all three tiers. Directly reusable as a starting point for any project-level behavioral enforcement hook.

- **`guide/workflows/changelog-fragments.md`** — New workflow guide documenting the 3-layer changelog fragment enforcement pattern: (1) CLAUDE.md workflow rule for autonomous fragment creation by Claude, (2) `UserPromptSubmit` hook with tier-priority system for pre-prompt interception, (3) CI gate with two independent jobs (fragment validation + migration flag check). Explains why each layer is necessary, how they compose without conflicting, and how to adopt the pattern independent of the TypeScript implementation.

### Updated

- **`guide/ultimate-guide.md`** (§ Release Notes Generation): Added `### Changelog Fragments: Per-PR Enforcement Pattern` subsection covering the 3-layer approach with fragment YAML example, hook snippet, and assembly command. Positioned as an alternative to commit-based release notes generation, with links to the workflow guide and hook example.

- **`guide/workflows/README.md`**: Added Changelog Fragments entry to Development Workflows section with key topics (CLAUDE.md rule, UserPromptSubmit 3-tier hook, conditional suggestion pattern, independent CI migration check). Added to Quick Selection Guide under "Enforce mandatory workflow steps".

## [3.34.7] - 2026-03-12

### Added

- **`guide/diagrams/11-context-engineering.md`** — 4 new Mermaid diagrams covering context engineering: 3-layer context system (global/project/session scopes), context budget and adherence degradation curve (95%→45% zones + path-scoping fix), monolithic vs modular CLAUDE.md architecture (anti-pattern vs path-scoped approach), and rule placement decision tree.

- **`guide/diagrams/12-enterprise-governance.md`** — 3 new Mermaid diagrams covering enterprise governance: 4-tier risk model (Starter/Team/Production/Regulated with controls per tier), MCP governance approval workflow (sequenceDiagram: submit → audit → classify → registry → deploy → monitor), and data classification matrix (PUBLIC/INTERNAL/CONFIDENTIAL/RESTRICTED with access rules).

### Updated

- **`guide/diagrams/01-foundations.md`**: Added Plan Mode and dontAsk as two new permission mode subgraphs (was showing 3/5 modes, now all 5 CLI permission modes are documented).

- **`guide/diagrams/04-architecture-internals.md`**: Added Control Flow Tools as a 6th tool category (EnterPlanMode/ExitPlanMode, EnterWorktree/ExitWorktree, AskUserQuestion). Count updated 5→6.

- **`guide/diagrams/05-mcp-ecosystem.md`**: Added clarifying note that local + user scopes both live in `~/.claude.json` (separate configuration keys), not in separate files. Description updated "4 different locations" → "4 priority levels (3 actual files)".

- **`guide/diagrams/07-multi-agent-patterns.md`**: Fixed disconnected B2 node — now properly connected as a third branch off the pattern-selection flow.

- **`guide/diagrams/09-cost-and-optimization.md`**: Replaced hardcoded USD prices with relative ratios (Haiku ~5x cheaper than Sonnet, Opus ~5x more than Sonnet) and added disclaimer pointing to anthropic.com/pricing.

- **`guide/diagrams/README.md`**: Updated diagram count 41→48, extended navigation table with files 11 and 12, added two new use-case navigation sections ("govern Claude Code across my team", "improve Claude's context adherence").

## [3.34.6] - 2026-03-12

### Added

- **`guide/workflows/rpi.md`** — New RPI (Research → Plan → Implement) workflow guide (560 lines). 3-phase feature development pattern with explicit validation gates: GO/NO-GO gate after Research, plan approval gate before any code is written, and per-step test gates during implementation. Includes full RESEARCH.md and PLAN.md templates, 3 slash command templates (`/rpi:research`, `/rpi:plan`, `/rpi:implement`), worked example (API rate limiting), comparison table vs dual-instance/spec-first/TDD/direct, and troubleshooting section. Inspired by community patterns from claude-code-best-practice.

- **LLM Day-to-Day Performance Variance** (`guide/core/known-issues.md`): New section documenting session-to-session output variance as expected behavior (not a bug). Covers root causes (MoE routing variance, infrastructure variance, probabilistic inference, context sensitivity), observable signals table (response length, refusals, code style, creativity, verbosity), clear distinction from the Aug-Sep 2025 infrastructure bugs, and 5 mitigation strategies (constrain prompts, fresh context, reformulate and retry, compare against known-good prompt, calibrate by task type).

### Updated

- **`guide/ultimate-guide.md`** (§ Quick Decision Tree): Added RPI entry — "Feasibility is unknown → workflows/rpi.md"
- **`machine-readable/reference.yaml`**: Added 8 new entries — `rpi_workflow`, `rpi_when_to_use`, `rpi_phase1_research`, `rpi_phase2_plan`, `rpi_phase3_implement`, `rpi_slash_commands`, `rpi_vs_other_workflows`, `known_issues_llm_variance`

## [3.34.5] - 2026-03-12

### Added

- **Blast-Radius Pattern** (grepai section, §8.2): Named pre-refactoring workflow using `grepai trace callers/callees` to enumerate all affected call sites before touching a widely-used function. Run before the refactor, not after compile errors. Includes 3-step bash example.

- **Pre-structural indexing** (§9.13 Token-Saving Techniques): New technique #6 documenting the concept of building a codebase structural index before starting a session. Replaces 5-10 sequential file reads with 1 graph query (~75% fewer tool calls for discovery tasks). Includes CodeXRay setup example (`npx codexray`, `cxr watch`).

- **Dead code & circular dependency detection** (§9.13): Documents three structural analysis patterns — dead code detection (`grepai trace callers` returning zero results), circular dependency identification, and hotspot analysis — as token optimization strategies. References CodeXRay and Claudette as alpha-stage community implementations with grepai as the stable alternative.

## [3.34.4] - 2026-03-12

### Documentation

- **Claude Code Releases**: Updated tracking to v2.1.74 (2026-03-12)
  - v2.1.74: `/context` actionable suggestions, `autoMemoryDirectory` setting, memory leak fix in streaming buffers, managed policy `ask` rules bypass fix, `SessionEnd` hook timeout fix
  - v2.1.73: `modelOverrides` setting, deadlock fix for skill hot-reload, subagent model downgrade fix on Bedrock/Vertex/Foundry, Opus 4.6 as default on 3P providers, `/output-style` deprecated

## [3.34.3] - 2026-03-11

### Added

- **MCP Server v1.1.0**: 4 new tools for tracking official Anthropic Claude Code docs
  - `init_official_docs()` — fetch and store a local baseline snapshot (runs once)
  - `refresh_official_docs()` — update the "current" snapshot without touching the baseline
  - `diff_official_docs()` — compare baseline vs current at section level, zero network calls
  - `search_official_docs(query)` — search official docs, loads only matching sections
- **Local cache architecture**: 4 files in `~/.cache/claude-code-guide/` (index + content, baseline + current). Diff reads only lightweight index files (~50KB), never the full 1.2MB doc. Atomic writes via `.tmp` + rename to prevent corruption.
- **5 new slash commands** (`/ccguide:init-docs`, `/ccguide:refresh-docs`, `/ccguide:diff-docs`, `/ccguide:search-docs`, `/ccguide:daily`) — documented in `ultimate-guide.md` and added to `.claude/commands/ccguide/`
- **`/ccguide:daily`** orchestrates the full daily workflow: refresh → diff official docs → guide/CC digest in one shot

## [3.34.2] - 2026-03-11

### Documentation

- **Claude Code Releases**: Updated tracking to v2.1.72 (2026-03-09)
  - Restored `model` parameter on Agent tool for per-invocation model overrides
  - Fixed SDK `query()` prompt cache invalidation — up to 12x input token cost reduction
  - CLAUDE.md HTML comments now hidden from Claude when auto-injected
  - Simplified effort levels: low/medium/high (removed max), new symbols ○ ◐ ●
  - `ExitWorktree` tool added; `CLAUDE_CODE_DISABLE_CRON` env var; `/plan` optional description

## [3.34.1] - 2026-03-11

### Added

- **`guide/workflows/og-image-generation.md`** — New workflow guide for generating dynamic OG images at build time using Satori and resvg in Astro 5. Covers setup, font format requirements (woff1 only), static file shadowing gotcha, dynamic stat counting from content directories, testing with opengraph.xyz / LinkedIn Post Inspector, and three design variants (stats grid, personal branding, terminal badge). Includes CI size check pattern.

- **`examples/scripts/og-image-astro.ts`** — Production-ready template for `src/pages/og-image.png.ts`. Drop into any Astro 5 project. Auto-serves at `/og-image.png`, counts content files dynamically, includes stat card component, author signature, and inline comments on every gotcha.

## [3.34.0] - 2026-03-11

### Added

- **Context Engineering Configurator** (`cc.bruniaux.com/context/`) — Interactive multi-step configurator that generates a personalized CLAUDE.md starter kit. 5-screen flow: profile (team size, AI tools), current state (existing CLAUDE.md, rules files), stack (language, frontend), results (generated artifacts + maturity assessment). Features: generated CLAUDE.md preview with copy-to-clipboard, Profile YAML for team setups, maturity badge (Level 1-5), personalized next-steps roadmap, localStorage persistence. Vanilla JS, no framework. Nav: added "Context" to landing header dropdown.

- **`guide/core/context-engineering.md`** — New consolidated reference (1,188 lines) covering all context engineering concepts. 8 sections: (1) What is Context Engineering (Karpathy's definition, prompt vs. context engineering distinction, three-layer model); (2) The Context Budget (token math, 150-instruction ceiling, HumanLayer 15-25% adherence data, path-scoping efficiency, overload signs); (3) Configuration Hierarchy (global/project/session split, decision tree for rule placement, override semantics); (4) Modular Architecture (path-scoping, skills vs. rules distinction, progressive disclosure, anti-pattern: monolithic CLAUDE.md); (5) Team Assembly (N×M×P problem, profile YAML, assembly workflow, CI drift detection, module library structure); (6) Context Lifecycle (instruction debt, update loop, knowledge feeding, ACE pipeline, session retrospective); (7) Quality Measurement (self-evaluation questions, canary checks, adherence tracking, context debt score formula); (8) Context Reduction Techniques (path-scoping -40-50%, negative constraints +15-25%, rule compression, deduplication, archive pattern).

- **`examples/context-engineering/`** — 10 production-ready templates: `README.md` (overview + quick start), `profile-template.yaml` (developer profile for context assembly), `skeleton-template.md` (CLAUDE.md skeleton with filled placeholders), `assembler.ts` (~240-line TypeScript script for profile-based assembly with @import resolution, dry-run support, token estimation), `eval-questions.yaml` (20 self-evaluation questions across 4 dimensions), `canary-check.sh` (5-check behavioral regression script), `ci-drift-check.yml` (weekly GitHub Actions drift detection with auto-issue creation), `context-budget-calculator.sh` (measures always-on token cost), `rules/knowledge-feeding.md` (proactive context update protocol), `rules/update-loop-retro.md` (session retrospective template).

- **`tools/context-audit-prompt.md`** — Self-contained context audit prompt (543 lines) following `audit-prompt.md` pattern. Scores context engineering setup /100 across 8 dimensions: Size & Budget (15 pts), Structure (15 pts), Path-Scoping (12 pts), Rule Quality (15 pts), Freshness (12 pts), Team Readiness (10 pts), Conflict Detection (11 pts), Knowledge Loop (10 pts). Includes 3 bash scan phases, report format with context budget breakdown, 5-level maturity ladder, and ready-to-use paste improvements.

- **`src/data/context-data.ts`** (landing) — TypeScript data file with all configurator types, option arrays (team size, AI tools, stack, frontend), maturity level definitions (5 levels: Starter/Modular/Team-Ready/Measured/Adaptive), and template generators (`generateClaudeMd`, `generateProfileYaml`, `calculateMaturityLevel`).

### Updated

- **`guide/README.md`** — Added `core/context-engineering.md` row to Core Reference table.
- **`machine-readable/reference.yaml`** — Added 24 context engineering entries with paths to guide, examples, tools, and landing configurator.
- **`src/components/global/Header.astro`** (landing) — Added "Context" to moreLinks dropdown.

## [3.33.1] - 2026-03-10

### Updated

- **RTK documentation updated to v0.28.0** — Synced RTK coverage across `guide/ultimate-guide.md`, `guide/ecosystem/third-party-tools.md`, `machine-readable/reference.yaml`, and global `~/.claude/{CLAUDE.md,RTK.md}`. New content: TOML Filter DSL (declarative filters without Rust, 33+ built-in filters, `.rtk/filters.toml` project-local and `~/.config/rtk/filters.toml` global lookup chain); `rtk rewrite` command (v0.25.0 single source of truth for hook rewrites, migration note: `rtk init --global` required after upgrade); new modules — `rtk docker compose`, `rtk mypy`, `rtk aws`, `rtk psql`, `rtk cargo nextest`, `rtk gt` (Graphite CLI), `rtk wc`; `rtk gain -p` per-project savings; `rtk init --global` with settings.json auto-patch; `exclude_commands` config; SHA-256 hook integrity verification; hook outdated warning.

## [3.33.0] - 2026-03-10

### Fixed

- **`guide/security/enterprise-governance.md` — Accuracy review pass** — 6 correctness issues fixed after adversarial critique: (1) Non-existent hooks removed from all tier `settings.json` configs (`dependency-guard.sh`, `compliance-pre-check.sh`, `pii-detector.sh`, `compliance-session-init.sh` were referenced but never existed in `examples/hooks/bash/`); (2) `compliance-audit-logger.sh` in Regulated tier replaced with real `session-logger.sh`; (3) Fabricated Claude Code API removed — `CLAUDE_SETTINGS` env var and `claude run-headless` subcommand don't exist; replaced with an honest CI pipeline validation pattern; (4) `date -d '30 days ago'` (GNU coreutils only) fixed to cross-platform with macOS/Linux `$OSTYPE` check; (5) Customer PII reclassified from CONFIDENTIAL to RESTRICTED — Enterprise plan (ZDR) alone doesn't satisfy GDPR/CCPA; (6) All `// comment` lines inside JSON code blocks removed (invalid JSON, breaks copy-paste).

### Added

- **Enterprise AI Governance section** (`guide/security/enterprise-governance.md`) — New guide covering org-level governance for teams deploying Claude Code at scale. 6 sections: (1) Local vs Shared governance split (risk matrix, decision framework); (2) AI Usage Charter — lean template covering approved tools, data classification, use case boundaries, approval matrix; (3) MCP Governance Workflow — approval pipeline (request → review → approve → deploy), YAML registry format, enforcement hook; (4) Guardrail Tiers — 4 pre-configured tiers (Starter/Standard/Strict/Regulated) with ready-to-copy `settings.json` and `CLAUDE.md` additions; (5) Policy Enforcement at Scale — config distribution, onboarding checklist, compliance audit script, role-based guardrails, CI/CD gates; (6) Audit & Compliance — what SOC2/ISO27001 auditors actually ask, audit trail setup, AI Governance Committee minimal structure. Audience: tech leads, engineering managers, security officers. Complements security-hardening.md (individual dev security) and production-safety.md (6 prod rules).

- **MCP Registry Template** (`examples/scripts/mcp-registry-template.yaml`) — Ready-to-use YAML format for tracking approved MCP servers at org level. Includes approved/pending/denied sections, version bump policy, risk classification (LOW/MEDIUM/HIGH), data scope classification (PUBLIC/INTERNAL/CONFIDENTIAL/RESTRICTED), and expiry dates.

- **Governance Enforcement Hook** (`examples/hooks/bash/governance-enforcement-hook.sh`) — SessionStart hook validating active MCP configuration against org's approved registry, checking deny rules for secret files, and detecting dangerous `permissions.allow` overrides. Warns without blocking (governance-first, not friction-first).

- **AI Usage Charter Template** (`examples/scripts/ai-usage-charter-template.md`) — Org-level charter template covering approved tools, data classification (4 levels), approved/prohibited use cases, MCP server governance, code review and attribution requirements, accountability roles, incident response, and compliance mapping (SOC2/ISO27001/HIPAA/PCI DSS/GDPR).

### Documentation

- **`guide/roles/adoption-approaches.md`** — Added "Enterprise Rollout (50+ developers)" section with 3-phase rollout approach (Foundation/Adoption/Optimization), common rollout mistakes at scale, and pointer to enterprise-governance.md for compliance programs.

- **`guide/ops/observability.md`** — Added "Manager Audit Checklist" section with weekly spot-check bash queries (files accessed outside project scope, destructive commands run) and a monthly compliance report script.

- **`guide/ops/ai-traceability.md`** — Added "Evidence Collection for Auditors" subsection under §7.3 Enterprise/Compliance — practical table mapping auditor questions to evidence sources and generation commands.

- **`guide/security/production-safety.md`** — Added cross-reference to enterprise-governance.md in See Also section.

- **`guide/security/security-hardening.md`** — Added cross-reference to enterprise-governance.md with explicit scope boundary ("this guide = individual MCP vetting; that guide = org-level policy"), plus MCP registry template reference.

- **`guide/README.md`** — Added enterprise-governance.md entry in Security section.

- **`machine-readable/reference.yaml`** — Added 22 entries for enterprise governance guide, templates, and hooks.

### Changed

- **GEO/SEO optimization — llms.txt, llms-full.txt, guide meta descriptions** — Phase 1 (repo): `machine-readable/llms.txt` updated (v3.8.0→3.32.2, 87→238 templates, 9.6K→22.7K lines); `llms.txt` created at repo root (convention llmstxt.org — AI crawlers expect root); `llms-full.txt` created (~20KB: full cheatsheet, 238-template catalog, 10 Q&A FAQ); `mcp-server/content/llms.txt` synced. Phase 2 (landing): `public/llms.txt` synced, `public/llms-full.txt` created; stale root `robots.txt` (wrong sitemap URL, missing 6 AI bots) and `sitemap.xml` (6 URLs only) deleted — `public/` versions are canonical. Phase 3 (landing): JSON-LD counts fixed (113→238 in `examples/index.astro`, description sync in `index.astro`); `twitter:site` + `twitter:creator` added to `Layout.astro`; CVE stat 19→24 in security page; `lastmod` added to all sitemap entries in `astro.config.mjs`. Phase 4 (README): invisible HTML keyword comment replaced with visible 5 Q&A mini-FAQ (GEO crawlers + humans). Phase 5 (guide section): 13 `CHAPTERS` descriptions rewritten in `scripts/prepare-guide-content.mjs` (source of truth for Starlight frontmatter) — avg 40→150 chars, now include specific agent names, hook event types, MCP server names, pattern names.

### Documentation

- **README navigation indexes synced with disk** (11 files) — Full audit revealed 40+ missing entries accumulated over time. `examples/README.md`: agents 9→16 (+2 collections), commands 26→31, hooks 31→34, skills 15→17, config 5→8, claude-md 6→7, scripts 13→16, integrations 4→1; 3 new sections: Rules (5), Team Config (3), Templates (1). `guide/README.md`: diagrams 40→41, +5 missing guide files (ai-roles, production-safety, remarkable-ai, sandbox-native, search-tools-cheatsheet), workflows 6→18. `guide/workflows/README.md`: new "Multi-Agent & Advanced" section (agent-teams, agent-teams-quick-start, dual-instance-planning, event-driven-agents, plan-pipeline, task-management), Quick Selection Guide extended, date updated. `examples/hooks/README.md`: +3 hooks (auto-rename-session, security-gate, velocity-governor). `examples/scripts/README.md`: +6 scripts (bridge-plan-schema.json, migrate-arguments-syntax.sh/.ps1, rtk-benchmark, sync-claude-config, sonnetplan). `guide/diagrams/README.md`: frontmatter 40→41. `docs/resource-evaluations/README.md`: 72→115. `README.md` root: resource evals 84→115.

### Changed

- **`tools/onboarding-prompt.md` updated for guide v3.32.2** — 7 changes: (1) "Who This Is For" table enriched (sandbox modes, Plan-Validate-Execute, Skills 2.0 taxonomy, threat DB mentioned by goal); (2) version refs `v3.23.0+` and `v3.21-3.22` updated to `v3.32.2+` / `v3.21-3.32` (6 occurrences); (3) 5 new adaptive triggers documented (`permission|allow|deny → permission_modes`, `memory|persist|session → memory_files`, `template|structure|format → skill_template`, `validation|checklist|deploy → agent_validation_checklist`, `plan|pipeline → plan_pipeline_workflow`); (4) time option "📖 2+ hours" added to the time profile question; (5) fallback roadmap `learn_security` enriched with `permission_modes`; (6) quiz count 274 → 271, per-profile subtotals removed (inconsistent), guide lines 11K+ → 22K+; (7) localization status updated (v3.23.0 → v3.32.2, `plan_pipeline` added in topics, quiz 274 → 271).

- **`tools/audit-prompt.md` updated — Version 3.0** (`tools/audit-prompt.md`) — 6 changes: (1) Opus 4.5 → Opus 4.6 (3 occurrences: intro note, Thinking Mode checklist, glossary); (2) Context Zones corrected: `Green (0-50%) / Yellow (50-70%) / Red (70%+)` → precise thresholds `< 70% optimal, 75% auto-compact, 85% handoff, 95% force handoff`; (3) `sed` line numbers updated with values from `reference.yaml` (deep_dive keys) + maintenance comment; (4) 4 new checklist categories added before "2.2 Calculate Health Score": **Rules Templates** (`.claude/rules/`, auto-loaded), **Sandbox & Permissions** (modes, `permissions.deny`), **Security Commands** (`/security-check`, `/security-audit`, threat-db), **Plan-Validate-Execute Pipeline** (`/plan-start`, `/plan-validate`, `/plan-execute`, ADR loop); (5) 4 new glossary entries: **Rules**, **Permission Modes**, **Sandbox**, **Plugins**; (6) footer `January 2026 | Version 2.9` → `March 2026 | Version 3.0`.

- **`machine-readable/reference.yaml` — Onboarding Matrix v2.1.0** (`machine-readable/reference.yaml`) — 5 changes: (1) metadata `version 2.0.0 → 2.1.0`, `last_updated → 2026-03-09`, new changelog entry v2.1.0; (2) 3 new deep_dive keys: `skills_taxonomy: 6718` (§5.0 Two Kinds of Skills), `skills_evals: 6954` (§5.Y Skill Evals), `session_auto_rename: 859` (distinct from `session_naming_guide: 815`); (3) quiz count `264 → 271` (4 occurrences: `quiz_count`, `unique` array, `code_landing.features`, comment); (4) adaptive triggers `plan|pipeline[|validate|execute]` added in 3 profiles: `optimize.power_60min`, `build_agents.power_60min`, `learn_everything.power_120min` → topic `plan_pipeline_workflow`; (5) version refs `v3.21-3.22 → v3.21-3.32` in profile notes (4 occurrences).

### Documentation

- **`/loop` command added to Commands Table §10.1** (`guide/ultimate-guide.md`) — `/loop [interval] [prompt]` runs a prompt or slash command on a recurring interval (e.g. `/loop 5m check the deploy`). v2.1.71+. Was already in cheatsheet (v3.32.2), now present in the reference table.

- **Voice keybindings documented §10.2** (`guide/ultimate-guide.md`) — new "Voice Input" subsection in Keyboard Shortcuts: push-to-talk default binding (`Space`), `voice:pushToTalk` rebindable in `~/.claude/keybindings.json` (v2.1.71+), example config included.

- **Claude Code Security note enriched §7.4** (`guide/ultimate-guide.md`) — added Mozilla Firefox validation context (March 2026): Opus 4.6 scanned ~6,000 C++ files in Firefox's JS engine, surfaced 22 confirmed vulnerabilities (14 high severity) in two weeks. Reinforces the "limited research preview" note with production evidence.

- **Pipelex + MTHDS added** (`guide/ecosystem/third-party-tools.md`) — new entry in "External Orchestration Frameworks" for Pipelex, Python runtime of the open MTHDS standard. Declarative DSL (`.mthds` files) for creating typed, git-versionable, multi-LLM AI methods. Integrates natively with Claude Code via `/plugin marketplace add mthds-ai/skills`. 623 stars (MIT, created May 2025). Status "Watch" — MTHDS standard not yet validated at scale. Architectural note distinguishing Pipelex (DSL for pipelines) from Ruflo/AthenaFlow (agent orchestration).

- **Diagrams updated — 3 files** (`guide/diagrams/`) — Mermaid diagrams updated following releases v2.1.59–v2.1.69 and documentation corrections v3.29–v3.31. (1) `02-context-and-sessions.md`: Memory Hierarchy goes from 5 to 6 types — addition of **Native Auto-Memory** (`~/.claude/projects/*/memory/MEMORY.md`, v2.1.59+) between Subdirectory CLAUDE.md and In-Conversation Context, cross-session scope, distinct green style from ephemeral types. (2) `03-configuration-system.md`: Hooks Event Pipeline enriched with 3 new events — `InstructionsLoaded` (v2.1.69+, session start), `UserPromptSubmit` (before PreToolUse, exit 2 = feedback), `Stop / SessionEnd` (renamed) — and a note on the HTTP type (POST JSON, v2.1.63+). (3) `05-mcp-ecosystem.md`: Official Servers goes from 3 to 5 entries — added `git-mcp` (official Anthropic, 12 git tools) and `github-mcp` (official GitHub, full platform).

### Changed

- **`/pr-triage` skill — Phase 4 Worktree Setup** (`examples/skills/pr-triage/SKILL.md`) — porting the worktree pattern developed on Méthode Aristote to the guide's generic template. The skill goes from 3 to 4 phases: Phase 4 is opt-in, accessible from a navigation menu after Phase 1 (without going through Phase 2/3). Integrated content: 30min cache-check on Phase 1 data, automatic filtering of draft PRs and bots (Dependabot, renovate, snyk), grouped display by author, multiSelect selection via AskUserQuestion, sequential execution per PR with structured status codes (CREATED / EXISTING / FETCH_FAILED / GITIGNORE_MISSING / ALREADY_CHECKED_OUT / CREATE_FAILED), automatic `node_modules` symlink if present (Node.js), `.worktreeinclude` convention to copy local config files into each worktree, git pull `--ff-only` for existing worktrees with guided rebase fallback, final summary with next steps `cd .worktrees/<branch> && claude`. Phase 4 edge cases added (5 cases). Related table and frontmatter description updated (3-phase → 4-phase, `worktree` tag).

## [3.32.2] - 2026-03-09

### Documentation

- **Cheatsheet updated** (`guide/cheatsheet.md` + landing `cheatsheet/index.astro`) — 4 new commands from releases v2.1.59–v2.1.71: `/loop [interval] [prompt]` (recurring scheduler, e.g. `/loop 5m check the deploy`), `/stats` (usage chart + streak), `/rename [name]` (name a session), `/copy` (interactive picker to copy a code block). New shortcut `Ctrl+F` (kills all background agents, double press). `/loop` added to "Hidden Features" with version v2.1.71. Landing version synced 3.29.2 → 3.32.0.

## [3.32.1] - 2026-03-08

### Added

- **`auto-rename-session.sh` hook template** (`examples/hooks/bash/auto-rename-session.sh`) — SessionEnd hook that automatically generates a descriptive title for each session. Reads the session JSONL directly, extracts the first 3 user messages, calls `claude -p --model claude-haiku-4-5-20251001` to generate a 4-6 word title (`verb + subject` format), falls back to the cleaned first message if Haiku is unavailable. Updates the slug in the native JSONL (for `/resume`) and in `sessions-index.jsonl`. Output via `/dev/tty` to bypass Claude Code's JSON parsing.

### Documentation

- **"Session Auto-Rename" section updated** (`guide/ultimate-guide.md`) — now presents two complementary approaches: Approach A (CLAUDE.md instruction, mid-session renaming via `/rename`, zero tooling) and Approach B (SessionEnd hook, title generated by Haiku post-session, direct JSONL reading). Removed the "Why not a hook?" paragraph which was incorrect since the introduction of session data access via JSONL.

## [3.32.0] - 2026-03-06

### Added

- **Plan-Validate-Execute Pipeline** (`guide/workflows/plan-pipeline.md`) — new complete 3-command workflow for AI-first teams: `/plan-start` (5 phases: PRD analysis, design, technical decisions, dynamic research team, metrics), `/plan-validate` (2 layers: inline structural checks + specialist agents triggered by triggers), `/plan-execute` (isolated worktree, TDD scaffolding, parallel execution by levels, quality gate with smoke test, PR creation and merge, cleanup). Includes: "non-prescriptive" philosophy (say what, never how), first principles "No Bandaids, No Workarounds" (state-of-the-art always, build time irrelevant, zero workaround), ADR learning loop (Watching → Emerging → Confirmed → CLAUDE.md promotion), CLAUDE.md discipline (120-line limit, pointer strategy to sub-files, dynamic loading), context management (`/clear` between each command). Cost profile: $2-10 for a typical Tier 2 feature with compounding over time.

- **`/plan-start` command** (`examples/commands/plan-start.md`) — 5-phase slash command with dynamic agent pool (12 roles, trigger-based selection). Includes: interactive PRD analysis with 3 buckets (missing/ambiguous/compliance), design analysis (screen inventory, states catalog, animation specs, ARIA accessibility), technical analysis with automatic resolution of ADR-confirmed decisions, scope assessment (Tier 0 Solo → Tier 4 Full Spectrum), parallel multi-agent research monitored via TaskOutput, synthesis by `planning-coordinator`, commit plan + ADRs + metrics. Auto-transition to `/plan-validate` if no ambiguities.

- **`/plan-validate` command** (`examples/commands/plan-validate.md`) — independent validation in 2 layers. Layer 1 inline structural (format, dependencies, file existence, ADR consistency, CLAUDE.md compliance). Layer 2 specialists triggered by triggers (security-reviewer Opus, db-migration-reviewer Opus, performance-reviewer, design-system-reviewer, ux-reviewer, cross-platform-reviewer, integration-reviewer Opus — 0 to 8 agents depending on the plan). ADR-aware auto-fix phase: Bucket A (auto-resolution via ADR/PATTERNS/first principles, ~95%), Bucket B (human input → new rule → future auto-resolution). Structured persistence of issues in metrics JSON. Auto-transition to `/plan-execute` if everything auto-resolved.

- **`/plan-execute` command** (`examples/commands/plan-execute.md`) — complete execution through to merged PR. Isolated worktree → TDD scaffolding (failing tests first) → parallel execution by levels (one agent per task, commit per task) → drift detection → quality gate (lint + types + tests) → integration smoke test (probe GraphQL, scan container logs, plan-defined commands) → PRD reconciliation + plan archival → PR squash merge → post-merge metrics → worktree cleanup. Up to 3 auto-fix attempts by debug agent before human escalation.

- **`planning-coordinator` agent** (`examples/agents/planning-coordinator.md`) — Opus synthesis agent, read-only. Receives reports from all research agents, reads existing ADRs, resolves conflicts between agents (ADR precedence → agent stake → human escalation), builds the task graph (layers, TDD markers, atomic granularity), verifies plan completeness (PRD coverage, security findings addressed, acyclicity). Spawned automatically when 2+ research agents are selected. Does not research — synthesizes.

- **`integration-reviewer` agent** (`examples/agents/integration-reviewer.md`) — Opus runtime validation agent, read-only + WebFetch. Validates what compiles but fails at runtime: connection parameters (ports, protocols, hostnames across environments), async/sync consistency (missing awaits, sync call in async context), env var completeness (`.env.example`, CI/CD, k8s manifests, startup validation), API library correctness (installed version vs API used via WebFetch), OTEL pipeline (configured exporter, cross-service context propagation, sampling). Triggered in `/plan-validate` when new services, libraries, or OTEL config are in scope.

## [3.31.0] - 2026-03-06

### Added

- **Skills 2.0 — Taxonomy, Evals and Lifecycle** (`guide/ultimate-guide.md` §5.0, §5.X, §5.Y) — 3 new blocks: Capability Uplift vs Encoded Preference taxonomy, Skill Lifecycle (Catch Regressions + Spot Outgrowth + retirement checklist), Skill Evals (Benchmark Mode / A/B Testing / Trigger Tuning). "What Makes a Good Skill?" table enriched (Expected Lifespan column). `guide/cheatsheet.md` + `machine-readable/llms.txt` updated. 3 new landing quiz questions (019-021). Sources: ainews.com, mexc.co, claudecode.jp — March 2026.

- **Featured Community Plugins — Vitals + SE-CoVe** (`guide/ultimate-guide.md` §8.5) — Vitals (chopratejas/vitals, v0.1 alpha): hotspot detection using `git churn × structural complexity × coupling centrality` formula, Claude semantic diagnostics, zero dependencies. SE-CoVe (vertti/se-cove-claude-plugin, v1.1.1): 5-step Chain-of-Verification pipeline (Baseline → Planner → Executor → Synthesizer → Output), verifier without access to the initial solution. Evaluation: `docs/resource-evaluations/vitals-codebase-health-plugin.md` (3/5). `machine-readable/reference.yaml` entries updated.

### Documentation

- **Memory system — 3 corrections** (`guide/ultimate-guide.md`): Auto-Memories version corrected (v2.1.32+ → v2.1.59+, confirmed 2026-02-26), context thresholds unified (<70% optimal / 75% auto-compact / 85% handoff / 95% force), WHAT/WHY/HOW framework added (§3.1 Minimum Viable CLAUDE.md) with Next.js example and anti-pattern "do not auto-generate your CLAUDE.md".

## [3.30.2] - 2026-03-05

### Documentation

- **Conductor section enriched** (`guide/ecosystem/third-party-tools.md:376`) — section rewritten from 5 generic bullets to 6 structured subsections, verified against official changelog (conductor.build). Added: workspace status system (backlog → done, v0.35.0), Next Workspace button for agent queue navigation (v0.36.4), turn-by-turn diff viewer (v0.22.0), Manual Mode built-in editor replacing VSCode for quick edits (v0.37.0), full GitHub/CI integration details (Actions tab v0.33.2, failing CI → Claude auto-fix v0.12.0, PR workflow with `⌘⇧P`), Linear deeplinks, Codex support alongside Claude, Melty Labs attribution. Community workflow pattern added: 5+ parallel features across multiple repos, BMAD + Conductor combo for spec-driven development (user-reported, unverified claim clearly marked).

- **Claude Code Releases tracking**: Updated to v2.1.69 (from v2.1.66)
  - v2.1.69: InstructionsLoaded hook, 4 security fixes (nested skills/symlink bypass/trust dialog/sandbox), 15+ memory leak fixes, Voice STT 20 languages, ${CLAUDE_SKILL_DIR}, /reload-plugins
  - v2.1.68: ultrathink keyword re-introduced, Opus 4.6 medium effort default, Opus 4/4.1 removed from first-party API


### Added

- **OpenClaw security hardening — personal documentation (boldguy/obsidian)** — 4 files created after security audit (score 5/10 → target 8+/10). (1) `securisation-openclaw.md`: complete 5-level guide — gateway bind loopback + 32-char token, exec allowlist + filesystem denied paths, memory-lancedb reconfigured with local Ollama (nomic-embed-text, `dimensions: 768` required because `config.ts:66-72` throws for non-OpenAI model without this field), Cloudflare Access Zero Trust on `webhook.bruniaux.com`, iMessage DM Policy (pairing or allowlist), hardened docker-compose. (2) `checklist-openclaw.md`: 5 checkable sections (pre-install, network, sandbox, memory/data, channels) + monthly monitoring. (3) `scripts/verify-openclaw-security.sh`: bash script with 8 automated checks (port binding, JSON config, Ollama, active OpenAI connections, injection session scan, built-in audit, FileVault). (4) `rapport-audit-openclaw.md`: Addendum section with additional findings (Ollama local support verified in `config.ts:10,147`, community 3-tier guide, DM Policy modes). Key audit finding: `memory-lancedb` sends embeddings to OpenAI by default — reconfigure with `baseUrl: "http://localhost:11434/v1"` + `dimensions: 768` to stay 100% local.

### Fixed

- **Remote Control §9.22 — iOS bugs documented and workarounds** (`guide/ultimate-guide.md:20075`) — troubleshooting enriched following field testing (iPhone, March 2026). Confirmed bug: QR code scan opens the Claude app but the session does not appear in the list (Research Preview, reproducible on iOS, documented by MacStories). Two reliable workarounds added: (1) `claude.ai/code` in Safari — session visible directly, (2) URL copied from terminal and pasted in Safari. Explanatory note added in troubleshooting table with MacStories reference.

### Added

- **Entire CLI enrichment (6 sections, 4 files)** — integration of production analysis issue #802 (Méthode Aristote) into the guide. Content added: (1) `guide/ops/ai-traceability.md` — complete "workflow without vs with Entire" diagram showing the 7 hooks and what they capture (UserPromptSubmit, PreToolUse, PostToolUse, Stop...), actual checkpoint structure (`entire/checkpoints/v1/` with metadata.json + full.jsonl + prompt.txt + context.md), orphan branch diagram (no common ancestor = zero merge conflict), Go/No-Go table with measurable thresholds (< 10 MB/session, push < 5s, < 100 MB/week) and 2h spike commands. (2) `guide/ecosystem/ai-ecosystem.md` — Claude → Gemini agent handoffs diagram with context preservation (reasoning trace, touched files, decisions, rejected approaches), "no cold start" explanation. (3) `guide/ecosystem/third-party-tools.md` — delta table vs existing setups (7-day JSONL vs permanent checkpoints, absent human/AI attribution vs % per line, silent handoffs vs auto-passed context). (4) `guide/security/security-hardening.md` — approval gate flow diagram (policy check → low risk auto-OK / high risk → reviewer transcript + diffs → approve/reject → immutable audit trail). Source: [github.com/methode-aristote/app/issues/802](https://github.com/methode-aristote/app/issues/802).

- **`issue-triage` skill** (`examples/skills/issue-triage/`) — 3-phase issue backlog management for maintainers: automated audit of all open issues (categorization, Jaccard duplicate detection against open + 20 recent closed, risk classification Red/Yellow/Green, staleness 30/90-day thresholds, cross-reference to open PRs), opt-in deep analysis via parallel agents (full body + comments, duplicate verification, missing-info detection, effort estimate), and validated triage actions with mandatory `AskUserQuestion` gate (comment / label / close with close-reason). Jaccard algorithm is self-contained at runtime (no external library: normalize → tokenize → set intersection/union → threshold 0.60). Cross-referenced with `/pr-triage` for PR-side backlog management.

- **`pr-triage` skill** (`examples/skills/pr-triage/`) — 3-phase PR backlog management for maintainers: automated audit of all open PRs (size classification, overlap detection, cluster analysis, staleness, CI status, PR-issue linking), opt-in deep review via parallel `code-reviewer` agents, and validated comment posting with mandatory `AskUserQuestion` gate. Stack-agnostic (Node/TS, Python, Rust, Go checklists included), cross-platform clipboard (pbcopy/xclip/wl-copy/clip.exe), and cross-referenced with `/review-pr` for single-PR use cases.

- **External Orchestration Frameworks** (`guide/ecosystem/third-party-tools.md`, new section) — new category architecturally distinct from existing multi-instance tools (Gas Town, multiclaude). Documented distinction: launching multiple Claude Code instances in parallel vs. replacing/augmenting the internal orchestration layer with a full runtime. Two tools covered: (1) **Ruflo** (formerly claude-flow, 18.9k stars) — most adopted framework, hierarchical queen + workers swarms, 60+ specialized agents, Q-Learning router, 42+ skills, 17 hooks, SQLite persistence. Install recommendation via `npx ruflo@latest` (not curl|bash). Performance claims (84.8% SWE-Bench, 352x WASM) marked unverified, ongoing rebrand documented. (2) **Athena Flow** — different architecture (hooks → UDS → NDJSON → Node.js runtime → TUI), intercepts hook events rather than augmenting the agent layer. First workflow: autonomous Playwright E2E test builder. Status "Watch — not recommended yet" (project too recent, source audit missing). Complete evaluations: `docs/resource-evaluations/073-athena-flow-workflow-runtime.md` (2/5 Watch) and `074-ruflo-multi-agent-orchestration.md` (3/5 Pertinent).

- **For Tech Leads & Engineering Managers** (`guide/roles/learning-with-ai.md`, new §12) — dedicated section for tech leads and engineering managers, a blind spot identified through resource evaluation (Mathieu Eveillard, "Génération LLM"). The guide only covered the individual perspective; this section addresses organizational responsibility. Content: 4-week onboarding model (week 1 without AI for calibration before the tool masks gaps, validated by Create Future 2025: structured training → 14-42% → 35-65% time savings), 5 real growth metrics vs. velocity, 3 scalable mentoring models (pair rotations, 15min/week architecture hot seat, collective CLAUDE.md), AI team policy template for shared `CLAUDE.md`, 6 team-level warning signs with specific responses, quick checklist. New "Team & Organizational Research" section in sources (Create Future 2025, Stanford Digital Economy 2025, LeadDev, Stack Overflow Gen Z). Evaluation file created: `docs/resource-evaluations/2026-03-04-eveillard-generation-llm.md`.

- **Compound Engineering patterns** (`guide/ultimate-guide.md`, 4 insertions) — portable patterns from Every.to's compound-engineering plugin (Kieran Klaassen, prod-tested on Cora), previously absent from the guide. (1) **Named Perspective Agents**: distinction between persona roleplay (anti-pattern, prohibited §3.x) and named perspective (DHH = fat models + thin controllers + pragmatic REST condensed into one token), with caveat on drift between Claude versions. (2) **Swarm vs Sequential**: comparison table of the two multi-agent coordination modes, decision rule (Swarm = independent + thoroughness, Teams = sequential dependencies). (3) **Skill Quality Gates**: 9-criteria checklist going beyond frontmatter validation (`/audit-agents-skills`). (4) **Brainstorm-before-planning + documentary hierarchy**: `docs/brainstorms/ → docs/plans/` workflow before coding, table of 5 directories with their distinct roles (CLAUDE.md = rules, solutions/ = solved problems, brainstorms/ = thinking, plans/ = active plans, todos/ = ephemeral tasks). Formal evaluation: `docs/resource-evaluations/2026-03-04-compound-engineering-every-to.md` (4/5 HIGH VALUE).

- **Session Auto-Rename pattern** — behavioral instruction in `~/.claude/CLAUDE.md` that makes Claude automatically rename sessions after 2-3 exchanges, without any hook or script. Format `[action] [subject]` (e.g. "fix auth middleware", "refactor hook system"), max 50 chars, action verb first. Useful for finding sessions via `/resume` when multiple are running in parallel. Documented limitation: the WebStorm terminal tab cannot be renamed (ANSI sequences filtered by JetBrains). Template: `examples/claude-md/session-naming.md`. Guide: new "Session Auto-Rename" subsection in §1.3 Session Continuation. Template counter 175→176.

- **Design Reference File pattern** (`examples/claude-md/design-reference-file.md`) — field pattern from Boris Paillard / mixt.care evaluation (March 2026). Principle: keep `brand-book.html` and `ui-kit.html` at the project root as permanent context files — Claude Code reads them before any UI generation, ensuring design system consistency across sessions without re-prompting. Content: CLAUDE.md activation snippet, 4 complete prompts (brand-book with integrated WCAG, Tailwind ui-kit, WCAG 2.1 color audit + color blindness simulation, vanilla JS Intersection Observer scroll animations), palette example with CSS semantic roles (mixt.care), WCAG correction notes (e.g. copper #B87333 fails for normal text → fix to #9B5F20). Evaluation: `docs/resource-evaluations/075-paillard-design-system-first-website.md` (3/5).

- **Straude** (`guide/ecosystem/third-party-tools.md`, Token & Cost Tracking section) — complete entry for straude.com, a social dashboard for tracking Claude Code usage with leaderboard and streaks. Includes: functional description, table of data transmitted to the server (costs, tokens, models, hostname), security analysis based on direct source code inspection (`npm pack straude@0.1.9`), verdict (no malware, reservations about maturity and lack of privacy policy), `--dry-run` recommendation on first use. Complete evaluation: `docs/resource-evaluations/straude-evaluation.md`. Entries added in `machine-readable/reference.yaml`.

## [3.30.1] - 2026-03-04

### Documentation

- **Claude Code Releases**: Updated tracking to v2.1.66
  - v2.1.66: Reduced spurious error logging
  - v2.1.63: HTTP hooks (POST JSON to URL), project configs shared across git worktrees, `/simplify` & `/batch` bundled commands, major memory leak wave fixed
  - v2.1.62: Prompt suggestion cache fix
  - v2.1.61: Windows config file corruption fix

### Added

- **Native LSP documented** (`guide/ultimate-guide.md`, `guide/cheatsheet.md`, landing cheatsheet) — complete section on Claude Code's native LSP support (v2.0.74+, December 2025). Content: performance gain explanation (50ms vs 45s for codebase navigation, 900x), activation via `ENABLE_LSP_TOOL=1` or `~/.claude/settings.json`, table of 11 supported languages with install commands (`tsserver`, `pylsp`, `gopls`, `rust-analyzer`, `kotlin-language-server`, `sourcekit-lsp`...), `.lsp.json` configuration for timeouts. Enriched cheatsheet: LSP line with perf stat + activation note. Sources: [aifreeapi.com/en/posts/claude-code-lsp](https://aifreeapi.com/en/posts/claude-code-lsp), Perplexity fact-check March 2026.

- **`docs/solutions/` pattern documented** (`guide/ultimate-guide.md` §CLAUDE.md as Compounding Memory) — complementary pattern to CLAUDE.md for capturing solved problems between PRs, inspired by the [Compound Engineering (Every.to)](https://every.to/guides/compound-engineering) framework. Clear distinction: CLAUDE.md = behavioral rules, `docs/solutions/` = solved problems with full context. Includes example structure with 3 illustrative files (auth, iOS StoreKit, Kotlin coroutines).

- **Voice Mode documented** (`guide/ultimate-guide.md`, `guide/cheatsheet.md`) — native feature rolling out (~5% of Pro/Max/Team/Enterprise users). `/voice` to activate, hold `Space` to speak, release to send. Can be mixed with text input in the same prompt. Free transcription, does not count toward rate limits. 4 places updated: quick commands table §1.3, built-in commands table §6.1, voice workarounds section §11 (switching from superwhisper/MacWhisper workaround to native feature), cheatsheet (commands + shortcuts + hidden features). Source: [Charly Wargnier / LinkedIn](https://www.linkedin.com/posts/charlywargnier_voice-mode-is-officially-coming-to-claude-ugcPost-7434514836211863552-JvKw).

- **Smart Concierge + Retex system** — porting the system developed on Méthode Aristote to this project. `UserPromptSubmit` hook (`smart-suggest.sh`) that analyzes each prompt in natural language and suggests 0 or 1 relevant tool (max 1 per prompt, silent on slash commands, dedup if the tool is already in the prompt, ROI log in `~/.claude/logs/smart-suggest.jsonl`). 22 patterns in 2 tiers adapted to this project's tools: Tier 1 discovery (retex, whitepaper-density/journalist/coherence, pdf-generator, sync, security-audit, audit-repo-docs, boldguy-linkedin-answer, guide-recap, park, update-whitepapers), Tier 2 contextual (release, changelog, version, code-reviewer, debugger, audit-agents-skills, update-threat-db, audit-prose, release-notes-generator, security-check).
- **`/retex` command** — captures lessons learned (dead ends, bugs, rollbacks) in `.claude/memories/retex-*.md` with global index `retex-index.md`. Structure: what happened, root cause, prevention rule, tags, severity, scope. Direct mode (`/retex "description"`) and interactive mode.
- **`retex-review.md` rule** — auto-loaded at each session, displays the 3 most recent retex at startup, inline contextual surfacing if a pattern matches an existing prevention rule (max 1 warning per type per session).

## [3.30.0] - 2026-03-03

### Added

- **10 advanced patterns documented** — systematic audit of 10 patterns identified from expert practitioners, fact-checked via 9 Perplexity searches (March 2026). 5 new files created, 4 existing files enriched, 3 sections added to the main guide.

  **New files**:
  - `examples/agents/plan-challenger.md` — adversarial agent for challenging plans before implementation (+52.8% security, +80% bug detection, sources: DrillAgent/nsfocusglobal.com, milvus.io)
  - `examples/agents/adr-writer.md` — automatic ADR generation agent with C1/C2/C3 criticality matrix, `mcp-adr-analysis-server` MCP reference (tosin2013/GitHub)
  - `examples/commands/audit-codebase.md` — codebase scoring command in 7 categories (Secrets, Security, Dependencies, Structure, Tests, Imports, AI Patterns), 3 severity levels, progression plan by tiers 5→8→10 (inspired by Variant Systems open-source plugin)
  - `examples/rules/first-principles.md` — session invariants template: Contract/Working Set/Noise model, measurable thresholds ("80% minimum" > "good coverage"), context decay mitigation
  - `guide/workflows/event-driven-agents.md` — complete "event → agent" workflow: Linear-Driven Agent Loop (Galarza, Feb 2026), generic webhook pattern, events×agents table, guardrails (idempotency, rate limiting, circuit breaker)

  **Main guide modifications** (`guide/ultimate-guide.md`):
  - §3.1 — new "Modular Context Architecture" subsection: CLAUDE.md-as-index (<100 lines), `paths:` frontmatter for conditional loading, 3-tier architecture root→rules/→skills/ (undocumented official feature)
  - §9.3 — new "Deployment Automation" subsection: Vercel building blocks (3 required variables), Infisical as open-source Vault alternative, deploy skill, non-negotiable guardrails (staging-first, confirmation hook, rollback)
  - §9.12 (worktrees) — new "Coordinating Parallel Worktrees: Task Dependencies" subsection: manual analysis of touched files, explicit `blockedBy`, decision matrix, `coderabbitai/git-worktree-runner` reference, clarification: auto-detection does not exist

  **Workflow modifications**:
  - `guide/workflows/iterative-refinement.md` — "Community Patterns & Known Limitations" section: Ralph Loop (nathanonn.com), Auto-Continue Skill (mcpmarket.com), Stop Hooks integration, post-3-iterations escalation strategy, caveats GitHub issues #28489 and #28843
  - `guide/workflows/agent-teams.md` — nuance of >5 agents anti-pattern: context window table 10K/50K/100K+, model-per-role (desired feature, not supported by API March 2026), Gartner 40% enterprise prediction 2026

- **SonnetPlan hack documented** (`guide/ultimate-guide.md` §OpusPlan Mode) — budget Sonnet→Haiku variant via `ANTHROPIC_DEFAULT_OPUS_MODEL` + `ANTHROPIC_DEFAULT_SONNET_MODEL` remap: `sonnetplan()` shell function, Plan/Act routing, unreliable self-report caveat, GitHub issue link [#9749](https://github.com/anthropics/claude-code/issues/9749). New template `examples/scripts/sonnetplan.sh` with installation instructions and verification note (status bar vs self-report).

- **Auto-memory documented as 3rd native memory system** (`guide/ultimate-guide.md` §Session vs Persistent Memory) — transition from 2 to 3 systems (session / native auto-memory / Serena MCP), new 5×4 table, dedicated "Auto-Memory (native, v2.1.59+)" section with MEMORY.md path and `/memory` management. Correction: the old description linked `/memory` to CLAUDE.md (inaccurate) and ignored the native system. "When to use which" guidance updated.
- **`/memory` and `/copy` — command descriptions updated** (`guide/ultimate-guide.md` §Command Reference) — `/memory`: corrected to auto-memory + MEMORY.md (v2.1.59+). `/copy`: enriched with interactive code block picker and "Always copy full response" option (v2.1.59+).

- **`/batch` highlighted** (`guide/cheatsheet.md`, `whitepapers/fr/07`, `whitepapers/fr/08`, `whitepapers/en/07`, `whitepapers/en/08`) — `/batch` = 5-30 parallel agents in isolated Git worktrees, each opens a PR. Dedicated sections in whitepapers 07 (table /batch vs manual agent teams) and 08 (native alternative). Cheatsheet updated with `/simplify` + `/batch`.

- **skills.sh security audits** (`guide/ultimate-guide.md` §Skills Marketplace) — new "Security Audits (February 2026)" subsection: 3 independent partners (Socket static analysis 97% F1, Snyk mcp-scan 0% false positives, Gen Agent Trust Hub continuous monitoring), 4 risk levels (Safe/Low/High/Critical), post-install monitoring, mental model "skill = executable dependency". Trade-offs updated: removed "Early stage" warning, added ✅ automated audits + continuous monitoring. 3 source references added (Vercel changelog, Snyk blog, Gen/PRNewswire). Source: [Vercel, Feb 17 2026](https://vercel.com/changelog/automated-security-audits-now-available-for-skills-sh).

## [3.29.2] - 2026-03-02

### Added
- **`/simplify` command documentation** (`guide/ultimate-guide.md` §6.1) — dedicated section for the v2.1.63 bundled command: official description (over-engineering, redundant abstractions), 3 analyzed dimensions (reuse/quality/efficiency), targeted usage examples (`/simplify focus on error handling`), positioning table vs linters/formatters.
- **`/batch` command documentation** (`guide/ultimate-guide.md` §6.1) — dedicated section for the v2.1.63 bundled command: processing multiple items in a single invocation.
- **Built-in Commands table updated** — `/simplify` and `/batch` added §6.1 and §1.3. Sources: official GitHub release notes + Perplexity.

## [3.29.1] - 2026-03-02

### Added

- **Git MCP Server + GitHub MCP Server** (`guide/ultimate-guide.md` §8.2 MCP Server Catalog) — Git MCP Server (official Anthropic): 12 tools for local Git operations (git_status, git_diff, git_commit, git_log, git_create_branch…), `uvx` setup, multi-repo config, comparison vs Bash, typical workflows. GitHub MCP Server (official GitHub): Issues, PRs, Projects, Code search, Enterprise — remote mode via `api.githubcopilot.com/mcp/` (Copilot required) + self-hosted PAT-only. Fix documented for the `Incompatible auth server: does not support dynamic client registration` error: `gh auth token` + `Authorization: Bearer` header in `~/.claude.json`, expired token maintenance note.
- **Resource evaluation: MCP servers watch** (`docs/resource-evaluations/2026-03-02-mcp-servers-veille.md`) — 3 servers evaluated post-challenge + fact-check: GitHub MCP 4/5 (integrated), Exa 2/5 (rejected, unverifiable stars), Graphiti 2/5 (rejected, Kairn already covers the need).
- **Tool comparison table extended to 5 tools** (`guide/ultimate-guide.md` §Migration from Other Tools) — added Windsurf and Zed, fixed Cursor pricing.
- **Subscription quotas: "Claude Code prompts / 5h" column** (`guide/ultimate-guide.md` §Subscription Plans & Limits) — Pro ~10-40, Max 5x ~50-200, Max 20x ~200-800.
- **Resource evaluation: benchmark AI coding tools Feb 2026** (`docs/resource-evaluations/benchmark-ai-coding-tools-feb2026.md`) — score 3/5, 2 items integrated.
- **Claude Code v2.1.63 release tracking** — `machine-readable/claude-code-releases.yaml` + `guide/core/claude-code-releases.md`: v2.1.61–v2.1.63 (HTTP hooks, worktree config sharing, `/simplify` + `/batch`, `ENABLE_CLAUDEAI_MCP_SERVERS`).
- **HTTP hooks documentation** (`guide/ultimate-guide.md` §7.2) — `"http"` type (v2.1.63+): POST JSON → JSON response, config example with `allowedEnvVars`.
- **Resource evaluation W09-2026** (`docs/resource-evaluations/weekly-intel-2026-W09.md`) — score 4/5, 3 items integrated.
- **Section 9.23 — Configuration Lifecycle & The Update Loop** (`guide/ultimate-guide.md`) — continuous improvement loop, `detect-friction.sh` script, skills lifecycle, "The Update Loop" pattern.
- **Observability: Reading for Quality, Not Just Quantity** (`guide/ops/observability.md`) — 3 qualitative patterns with `jq` commands.
- **MCP Server: 3 new tools** — `compare_versions`, `get_threat`/`list_threats`, `search_examples` (8 → 12 tools total).
- **Terminal Personalization Settings** (`guide/ultimate-guide.md` §3.3) — `spinnerVerbs`, `spinnerTipsOverride`, complete example `examples/config/settings-personalization.json`.

### Added

- **Tool comparison table extended to 5 tools** (`guide/ultimate-guide.md` §Migration from Other Tools) — comparison table extended from 3 to 5 tools: added Windsurf (Cascade multi-agents, Wave 13, credit-based $15/mo) and Zed (native Rust, Ollama offline, token-based $10/mo + list price +10%). New rows: inline autocomplete, offline/local models, best for. Factual fix: Cursor pricing corrected from "$20/month flat" → credit-based (since June 2025, $20 included + overages).

- **Subscription quotas: "Claude Code prompts / 5h" column** (`guide/ultimate-guide.md` §Subscription Plans & Limits) — token budgets table enriched with a practical "Claude Code prompts/5h" column: Pro ~10-40, Max 5x ~50-200, Max 20x ~200-800. Warning note completed: ~50 active windows monthly cap + sub-agents/1M context impact on consumption.

- **Resource evaluation: benchmark AI coding tools Feb 2026** (`docs/resource-evaluations/benchmark-ai-coding-tools-feb2026.md`) — evaluation of a comparative 5-tool benchmark (Claude Code, Cursor, Windsurf, Zed, Copilot Workspace), text copied without source URL. Score 3/5 (relevant, selective integration). 2 net items integrated: prompts/5h quotas + comparison table extension. 4 recommendations rejected (already covered).

- **Claude Code v2.1.63 release tracking** — `machine-readable/claude-code-releases.yaml` + `guide/core/claude-code-releases.md` updated with v2.1.61, v2.1.62, v2.1.63 (HTTP hooks, worktree config sharing, `/simplify` + `/batch` bundled commands, `ENABLE_CLAUDEAI_MCP_SERVERS` env var, wave of memory leak fixes)

- **HTTP hooks documentation** (`guide/ultimate-guide.md` §7.2 Creating Hooks) — new hook type `"http"` (v2.1.63+): POST JSON to a URL, receives JSON in return. Added to the Configuration Fields table, descriptive bullet point, and complete config example with `allowedEnvVars`

- **Resource evaluation W09-2026** (`docs/resource-evaluations/weekly-intel-2026-W09.md`) — evaluation of the Anthropic/Claude Code weekly watch report (Feb 24 – Mar 1, 2026): score 4/5, 3 items integrated (v2.1.63 releases, HTTP hooks, Haiku 3 deadline note already present), 3 items rejected (Cowork, DoW, Vercept)

- **Section 9.23 — Configuration Lifecycle & The Update Loop** (`guide/ultimate-guide.md`) — continuous improvement loop for Claude Code configurations: friction detection from JSONL logs (`detect-friction.sh` script), skills lifecycle management (semantic versioning, deprecation, CI staleness check GitHub Actions), "The Update Loop" pattern (observe → analyze → delta update → canary test), handoff integration, DSPy/TextGrad mentions
- **Observability: Reading for Quality, Not Just Quantity** (`guide/ops/observability.md`) — new subsection in "Analyzing Session Data": 3 qualitative patterns (repeated reads, tool failures, high edit frequency) with ready-to-use `jq` commands, linked to §9.23

- **Git MCP Server + GitHub MCP Server** (`guide/ultimate-guide.md` §8.2 MCP Server Catalog) — two new servers documented in the MCP catalog:
  - **Git MCP Server** (official Anthropic, `mcp-server-git`): 12 tools for local Git operations (git_status, git_diff, git_commit, git_log, git_create_branch, etc.), `uvx` setup, multi-repo config, Git MCP vs Bash comparison, typical workflows. Status: early dev.
  - **GitHub MCP Server** (official GitHub, `github/github-mcp-server`): full GitHub platform access (Issues, PRs, Projects, Code search, Enterprise), remote MCP via `api.githubcopilot.com/mcp/` (Copilot required) + self-hosted PAT-only. Documented fix for the `Incompatible auth server: does not support dynamic client registration` error: inject token via `gh auth token` + manual header in `~/.claude.json`. Expired maintenance token note included.

- **Resource evaluation: MCP servers watch** (`docs/resource-evaluations/2026-03-02-mcp-servers-veille.md`) — evaluation of a watch report on 3 MCP servers (GitHub MCP, Exa, Graphiti). Final post-challenge scores: GitHub MCP 4/5 (integrated), Exa 2/5 (rejected, unverifiable stars 220 vs claim 3.1k), Graphiti 2/5 (rejected, heavy stack, Kairn already covers the need). Git MCP 5/5 (CRITICAL, previous evaluation) integrated simultaneously.

- **MCP Server: 3 new tools** — compare_versions, get_threat/list_threats, search_examples
  - `compare_versions(from, to?)` — diff between two Claude Code CLI versions: all releases in the range, aggregated highlights, aggregated breaking changes
  - `get_threat(id)` — lookup CVE (e.g. `CVE-2025-53109`) or attack technique (e.g. `T001`) from the threat database v2.4.0
  - `list_threats(category?)` — browse the threat-db: global summary with counts (no category) or detailed list by section (`cves`, `authors`, `skills`, `techniques`, `mitigations`, `sources`)
  - `search_examples(query, limit?)` — semantic search across 175 templates by intent (e.g. `"hook lint"`, `"agent code review"`) — complementary to `get_example` (exact name) and `list_examples` (category)
  - `mcp-server/IDEAS.md` — future ideas documented: `get_quiz`, `get_methodology`, `get_workflow`, resource `diff`, prompt `security-review`
  - Total: 8 tools → 12 tools (+ 3 resources + 1 prompt)

- **Terminal Personalization Settings** — documentation `spinnerVerbs` + `spinnerTipsOverride` in `guide/ultimate-guide.md` §3.3 Settings & Permissions
  - New section "Terminal Personalization Settings" (line 4978): JSON examples for `spinnerVerbs` (replace/add mode) and `spinnerTipsOverride` (with `excludeDefault: true`)
  - `settings.json` available keys enriched: added `spinnerVerbs`, `spinnerTipsOverride`, `plansDirectory`, `enableAllProjectMcpServers`
  - Link to complete example in the guide section
  - New file `examples/config/settings-personalization.json` — 183 lines, 19 custom verbs, 113+ tips in 13 categories (Context, Shortcuts, Prompting, Models, Plan Mode, Memory, Golden Rules, MCP, Tasks, CI/CD, Cost, Debug, Remote, Worktrees, Security, Hooks, Agents, Resources)
  - `machine-readable/reference.yaml`: new entry `spinner_personalization` + line number fix `permissions_deny_tool_qualified` (4978→5008)
  - Source: LinkedIn post on spinner verbs (evaluation score 3/5, gap confirmed from eval #070)

- **Tool-qualified deny format documentation** — new section in §3.3 Settings & Permissions (`guide/ultimate-guide.md`)
  - Permission Patterns table enriched: `Read(file_path:*.env*)`, `Edit(file_path:*.pem)`, `Write(file_path:*.key)`, `Bash(command:*rm -rf*)`
  - New section "Tool-qualified deny format" with complete example inspired by real production configs (strangebee, aristote): `Read(file_path:...)` syntax vs simple `".env"` format, glob patterns, note on known `permissions.deny` limitation (GitHub #4160)
  - Reference section §10.3 Permission Patterns updated with the 3 new lines
  - Source: comparative analysis of 3 production `.claude/` configs (StrangeBee/TheHive, Méthode Aristote, ccboard)

- **Resource evaluations** — 2 new evaluations in `docs/resource-evaluations/`
  - `069-claude-code-best-practice-repo-eval.md` — Evaluation of repo `shanraisshan/claude-code-best-practice` (score 4/5): bug fixed line 5646 (official agent fields misclassified as "community patterns"), interesting patterns identified
  - `070-claude-code-best-practice-dot-claude-eval.md` — Evaluation of `.claude/` config from the same repo (score 4/5): self-evolving agent pattern, Command→Agent→Skills architecture, `allowed-tools` wildcard scoping

### Fixed

- **MCP Server v1.0.3 — content path bug** (`mcp-server/src/lib/content.ts`)
  - ENOENT at production startup: `CONTENT_DIR` resolved `../../content` from `dist/` (2 levels), landing in `node_modules/` instead of the package root
  - Fix: `../content` (1 level) — tsup bundles everything flat in `dist/`, so 1 level is sufficient
  - Published on npm: `claude-code-ultimate-guide-mcp@1.0.3`

- **Bug line 5646 `guide/ultimate-guide.md`** — agent frontmatter fields `skills`, `background`, `isolation`, `memory` were incorrectly labeled "community patterns / not official spec". Replaced by complete official table verified against `code.claude.com/docs/en/sub-agents`. Fields concerned: `model`, `tools`, `disallowedTools`, `permissionMode`, `maxTurns`, `skills`, `mcpServers`, `hooks`, `memory`, `background`, `isolation`, `color` — all official.

### Changed

- **`ccboard/.claude/settings.json`** — added `permissions.deny` with tool-qualified format (14 rules): protection for sensitive files (`.env*`, `.pem`, `.key`, `credentials`, `secrets`) and destructive commands (`rm -rf`, force-push, reset --hard). Config went from `budget`-only to complete security config.

- **Boris Cherny / Lenny's Newsletter integration** — 3 insights from Head of Claude Code interview (Feb 19, 2026, Lenny's Newsletter)
  - `guide/ultimate-guide.md` l. 2350 — Empirical "80% Plan Mode" ratio: Boris Cherny starts ~80% of his tasks in Plan Mode, blockquote in the "When to Use Plan Mode" table
  - `guide/ultimate-guide.md` l. 4285 — New section "Build for the Model 6 Months Out" in CLAUDE.md compounding memory: strategic principle for designing workflows in anticipation of future models
  - `guide/ultimate-guide.md` l. 5492 — New section "Boris Cherny's 3 Principles for AI Teams" (end of §3.5): underfund projects, unlimited tokens first, go faster — management advice verified Business Insider
  - `docs/resource-evaluations/2026-02-25-boris-cherny-lenny-newsletter-podcast.md` — Complete evaluation (4/5, technical-writer challenge, Perplexity fact-check)

- **Remote Control (Mobile Access) — Section 9.22** — New section in `guide/ultimate-guide.md` documenting the Remote Control feature (Research Preview, v2.1.51+, Pro/Max only)
  - Two activation modes: `claude remote-control` CLI subcommand and `/rc` slash command
  - QR code + session URL connection workflow, `/mobile` command for app download
  - Community-sourced limitations: slash commands (`/new`, `/compact`) don't work in remote UI (undocumented in official Anthropic docs)
  - Advanced patterns: tmux multi-session workaround (bypass 1-session limit), VM/cloud persistent architecture
  - Security considerations, alternatives comparison (happy.engineering, OpenClaw, SSH, ngrok)
  - Section 9 Recap updated with Remote Control checklist item
  - TOC entry added: `[9.22 Remote Control (Mobile Access)]`

- **`guide/cheatsheet.md`** — Dedicated "Remote Control" section + Hidden Features entry
  - New section with full workflow: commands, QR/URL/app connection, limitations table, tmux pattern, auto-enable
  - Added to Hidden Features: v2.1.51 Remote Control
  - CLI flags table: `remote-control` subcommand
  - Slash commands table: `/remote-control`, `/rc`, `/mobile`

- **`guide/security/security-hardening.md`** — Part 7: Remote Control Security
  - Architecture diagram (outbound-only HTTPS relay model)
  - Threat model: session URL leak, RCE surface, corporate policy, persistent exposure
  - Community perspective (senior dev security concerns)
  - Best practices + enterprise considerations
  - Comparison table: Remote Control vs SSH, ngrok, VPN+SSH

- **`machine-readable/reference.yaml`** — Remote Control entries
  - Slash commands: `/remote-control`, `/rc`, `/mobile`
  - CLI: `remote-control` subcommand
  - Deep dive: `remote_control: 18843` line reference

- **`docs/resource-evaluations/2026-02-25-claude-code-remote-control.md`** — Resource evaluation (score 4/5)
  - Full fact-check, community feedback (FR Slack), 9 press articles found
  - Challenge section with risk analysis
  - Original insights: slash command limitation, tmux pattern, security concerns

### Documentation

- **Claude Code Releases**: Updated tracking to v2.1.56 (v2.1.52 → v2.1.56)
  - v2.1.56: VSCode extension crash fix on Windows
  - v2.1.55: BashTool EINVAL fix on Windows
  - v2.1.53: Stability release — Windows panics/crashes, WebAssembly crashes (Linux x64/Windows x64/ARM64), Remote Control shutdown fix

## [3.29.0] - 2026-02-24

### Changed

- **docs/resource-evaluations/agents-md-empirical-study-2602-11988.md** — Added "Community Reception" section
  - Key nuance: the `/init` command generates an LLM-generated context file → -3% performance (not "delete your CLAUDE.md")
  - Link to Charly Wargnier's post (LinkedIn, 72 reactions) as an example of community simplification
  - Note on posts paraphrasing the study without added value (do not cite as independent sources)

## [3.29.0] - 2026-02-24

### Added

- **guide/ultimate-guide.md §5.5** — Design Intelligence: UI UX Pro Max skill
  - Most popular repository in the ecosystem (33.7k stars, 3.3k forks, MIT, v2.2.1)
  - BM25 offline design reasoning engine on ~400 local JSON rules (67 UI styles, 96 palettes, 57 typographies)
  - Compatible with 14 AI assistants (Claude Code, Cursor, Copilot, Windsurf…)
  - Installation guide, workflows, usage examples

- **guide/ops/observability.md** — Complete MLflow Tracing section (~120 lines)
  - CLI mode (zero Python) + SDK mode with API wrapping
  - LLM-as-judge for automatic quality regression
  - Exact token counts vs ~15-25% variance from hooks
  - Complete setup: tracking URI, auto-tracing, evaluation with GPT-4o judge
  - Decision guide: when MLflow vs ccusage vs OpenTelemetry

- **guide/diagrams/06-development-workflows.md** — "AI Fluency — High vs Low Fluency Paths" diagram
  - 41st Mermaid diagram in the guide
  - Based on Anthropic AI Fluency Index (9,830 conversations analyzed)
  - Visualizes the gap between 30% high-fluency vs 70% low-fluency users

- **guide/ultimate-guide.md** — 3 empirical callouts from Anthropic AI Fluency Index
  - Rev the Engine pattern: users who challenge reasoning are 5.6× more likely to catch errors
  - CLAUDE.md: only 30% explicitly define collaboration terms before starting
  - Source: Swanson et al., "The AI Fluency Index", Anthropic (2026-02-23)

- **guide/ultimate-guide.md** — New docs v2.1.47-v2.1.50
  - `WorktreeCreate`, `WorktreeRemove`, `ConfigChange` hook events with bash examples
  - `last_assistant_message` field in Stop/SubagentStop hooks
  - `--from-pr` flag documentation + auto-link sessions PR
  - Repo-Level Plugin Policy via `--add-dir` (settings.json `extraKnownMarketplaces`, `enabledPlugins`)
  - LSP `startupTimeout` configuration (v2.1.50+)

- **docs/resource-evaluations/** — 4 new evaluations (83 → 84 files)
  - `2026-02-23-agentsview-session-analytics.md` — AgentsView score 3/5
  - `2026-02-23-anthropic-ai-fluency-index.md` — AI Fluency Index score 4/5
  - `2026-02-23-veille-cc-releases-2144-2150.md` — CC releases watch
  - `ui-ux-pro-max-skill.md` — UI UX Pro Max skill score 4/5

### Documentation

- **Claude Code Releases**: Updated tracking to v2.1.52
  - v2.1.51: `claude remote-control` subcommand, BashTool login shell perf, SDK account env vars, /model human-readable labels
  - v2.1.52: VSCode crash fix on Windows

### Changed

- **README.md** — 41 diagrams (was 40), 84 evaluations (was 78)
- **machine-readable/reference.yaml** — Entries added for new content
- **guide/diagrams/README.md** — Added the 41st AI Fluency diagram

### Version Bump

- Bumped guide version: 3.28.1 → 3.29.0
- Reason: new MLflow observability section, UI UX Pro Max, AI Fluency diagram + empirical callouts, 4 resource evaluations

### Added

- **guide/ultimate-guide.md §9.21** — New section "Legacy Codebase Modernization" (4-step workflow validated by independent research)
  - Trigger: Anthropic COBOL article (Feb 23, 2026) + IBM -13% drop same day (worst day since Oct. 2000)
  - Workflow: Discovery → Risk Analysis → Strategic Planning → Incremental Implementation
  - Concrete prompt patterns for each phase, realistic expectations table (-25% to -88% depending on context)
  - Stats verified via Perplexity: 220B COBOL lines (IBM), ~95% ATM (Reuters/industry), 93% accuracy COBOL→Java (arXiv Apr. 2025)
  - Documented anti-patterns: big bang migration, no parallel run, skip discovery, blind trust on business logic
  - Sources: arXiv 2504.11335, AWS EKS case study (Jul. 2025), WJAETS 2025, Airbnb case (6 weeks vs 1.5 years)
  - Resource evaluation: score 2/5 maintained (marketing article without technical depth) — workflow integrated via independent research

- **Anthropic AI Fluency Index (Feb 23, 2026)** — Integration of official Anthropic research (9,830 conversations analyzed) in 3 targeted points + diagram
  - **§2.3 Rev the Engine** — Empirical callout: 5.6× more error catches for users who question reasoning (justifies plan review)
  - **§3.1 CLAUDE.md Best Practices** — 30% callout: only 30% of users explicitly define collaboration terms → CLAUDE.md structurally fills this gap
  - **§9.11 Common Pitfalls** — "⚠️ Artifact Paradox" callout: polished artifacts (code, files) → −5.2pp gap identification, −3.7pp fact-checking, −3.1pp questioning (with 5 concrete countermeasures)
  - **guide/diagrams/06-development-workflows.md** — 5th diagram: "AI Fluency — High vs Low Fluency Paths" (Bold Guy flowchart, standard palette, click hrefs + ASCII fallback), total diagrams: 40 → **41**
  - **docs/resource-evaluations/2026-02-23-anthropic-ai-fluency-index.md** — Evaluation file (score 4/5, complete fact-check with exact article citations)
  - **machine-readable/reference.yaml** — 16 `ai_fluency_*` entries + `ai_fluency_diagram`, `resource_evaluations_count` 83→84, `mermaid_diagrams.description` updated

- **docs/resource-evaluations/2026-02-23-agentsview-session-analytics.md** — AgentsView evaluation (score 3/5, to integrate in 2-4 weeks)
  - Local web app (Go + Svelte 5 + SQLite FTS5) for search + analytics of Claude Code, Codex, Gemini CLI sessions
  - Confirmed gap: no existing tool in the guide combines FTS + visual analytics (heatmaps, velocity) in a local web UI
  - Barriers: 4-day-old repo (created Feb 19, 2026), 49 stars at time of evaluation
  - Author credibility: Wes McKinney (creator of pandas)
  - Integration plan: `guide/ops/observability.md` External Monitoring Tools section + mention in `guide/ecosystem/third-party-tools.md`
  - Initial score 4/5 → challenged to 3/5 (adoption not established) + placement corrected to `observability.md`

- **guide/ultimate-guide.md §5.5** — New entry "Design Intelligence: UI UX Pro Max" in Community Skill Repositories
  - Most popular design skill in the ecosystem (33.7k stars, 3.3k forks, MIT, v2.2.1)
  - Covers: 67 UI styles, 96 palettes, 57 typographies, 99 UX guidelines, 100 industry rules
  - Documentation of the Design System Generator (BM25 Python engine, offline) with exact commands
  - Master + Override pattern for multi-page projects documented with end-to-end workflow
  - 3 installation options (Claude Marketplace, CLI `uipro-cli`, manual git clone)
  - Security note updated post-source-audit (Feb 2026): no npm preinstall/postinstall scripts, Python engine 100% offline (stdlib + local CSV/JSON, zero network calls)
  - Evaluation: `docs/resource-evaluations/ui-ux-pro-max-skill.md` (score 4/5, traction verified via gh CLI, clean source audit)

- **machine-readable/reference.yaml** — Entry `ui_ux_pro_max` with URL, line number, stats

- **guide/ultimate-guide.md** — 7 sections added following Anthropic weekly watch Feb 17-23, 2026 (eval: `docs/resource-evaluations/2026-02-22-veille-hebdo-anthropic-17-23-fev.md`, score 3/5)

  **P1 — Prompt caching + missing env vars**
  - §1.7 Cost Optimization — Strategy 6: prompt caching API (`cache_control`, cache write/read pricing, break-even, 4 max breakpoints)
  - §Appendix Environment Variables — `CLAUDE_CODE_DISABLE_1M_CONTEXT` (v2.1.50+) and `CLAUDE_CODE_SIMPLE` (v2.1.50+) added to the main table

  **P2 — Model deprecations + agents**
  - §1.7 Pricing Model — Warning box: `claude-3-haiku-20240307` deprecated Feb 19, 2026, retirement April 20, 2026, migration to `claude-haiku-4-5-20251001`
  - §4.2 Frontmatter Fields — `background: true` (non-blocking, v2.1.49+) and `isolation: "worktree"` (isolated spawn, v2.1.50+) added to table
  - §4.4 Best Practices — New section "Background Agents": behavior, management (ctrl+f, double ESC/ctrl+C), default vs background mode comparison
  - §4.4 Best Practices — New section "`claude agents` CLI": command + annotated output example (v2.1.50+)

  **P3 — Native worktree isolation + security cross-ref**
  - §9.11 Git Worktrees — New subsection "Claude Code Native Worktree Features": `--worktree`/`-w` flag, declarative `isolation: "worktree"`, `WorktreeCreate`/`WorktreeRemove` hooks with complete `settings.json` example
  - §7.4 Security Hooks — Cross-ref callout to `security-hardening.md#claude-code-as-security-scanner-research-preview`

- **docs/resource-evaluations/2026-02-22-veille-hebdo-anthropic-17-23-fev.md** — Anthropic weekly watch evaluation file Feb 17-23, 2026 (score 3/5, partial integration)

- **README.md + CLAUDE.md** — Guide stats update: `~19K lines` → `~20K lines` (20,440 lines)

- **guide/diagrams/09-cost-and-optimization.md + guide/ultimate-guide.md §2.5** — Budget modifier for model selection decision flow
  - The "Model Selection Decision Flow" diagram implicitly assumed unlimited budget (Max/API) — blind spot flagged by the community
  - Added a **Budget modifier table**: Max/API → Opus plan + Sonnet impl; Pro/Teams Standard → Sonnet plan + Haiku impl (mechanical tasks)
  - Community pattern documented: *Sonnet for Plan → Haiku for Implementation* on Teams Standard $25/mo
  - ASCII version updated with the budget modifier
  - Note added in Decision Table §2.5 for the same modifier
  - Source: Frédéric Camblor feedback (community)

- **guide/ultimate-guide.md — §2.7 Configuration Decision Guide** (new section, ~73 lines)
  - Unified view "which mechanism for what?" for the 7 configuration mechanisms (CLAUDE.md, rules, commands, hooks, agents, skills, MCP)
  - **Semantic Roles table** — conceptual role → mechanism mapping in 6 lines
  - **Mechanism Comparison table** — 7 mechanisms with loading timing, optimal usage, token cost, reliability
  - **Decision Tree** — binary tree covering all 7 mechanisms in priority order
  - **56% Reliability Warning** — Gao 2026 stat + practical implications + safe CLAUDE.md/skill pattern
  - **Common Mistakes table** — 4 common anti-patterns with corrections
  - Sections 2.7→2.11 renumbered (Structured Prompting, Semantic Anchors, Data Flow, Under the Hood)
  - TOC, quick-jump bar, and 3 backlinks (§2.6, §3.4, §5.1) updated
  - `reference.yaml`: 4 new entries with anchors and line numbers

### Research

- **Resource Evaluation: fp.dev** (score 2/5 — watchlist)
  - fp.dev = agent-native local-first issue tracker for Claude Code (issues as git-committable `.md`, skills `/fp-plan` `/fp-implement` `/fp-review`, diff viewer)
  - Real differentiator vs Tasks API: committable issues in the repo. But insufficient adoption + Apple Silicon only + partial overlap with native Tasks API
  - File: `docs/resource-evaluations/2026-02-22-fp-dev-issue-tracker.md`
  - **Known Gap added** in `guide/ecosystem/third-party-tools.md`: "Agent-native issue tracking (markdown-based, git-committable)"
  - **Watch List**: re-evaluate when GitHub stars visible + release cadence + practitioner prod write-up

## [3.28.1] - 2026-02-22 (security patch)

### Security

- **Threat Database v2.1.0 → v2.2.0** — 2 new CVEs, 5 new scanning tools, 1 new attack technique
  - **CVE-2026-0755** (Critical, CVSS 9.8) — gemini-mcp-tool RCE via command injection; LLM-generated args passed to shell without validation; no auth, network-reachable; **no fix as of 2026-02-22**
  - **SNYK-PYTHON-MCPRUNPYTHON-15250607** (High) — mcp-run-python SSRF via overly permissive Deno sandbox allowing localhost access
  - **T010 Attack Technique** — Agent-to-Agent Communication Injection: attacker injects malicious instructions into Slack/GitHub/ticketing channels monitored autonomously by AI agents
  - **5 new scanning tools catalogued**: Proximity (open-source), Enkrypt AI MCP Scanner, Cisco MCP Scanner (behavioral analysis), NeuralTrust MCP Scanner, MCPScan.ai
  - **Defensive resource**: Anthropic Claude Code Security (AI-powered codebase scanner, launched 2026-02-21)
  - **4 new sources**: Lakera "Agent Skill Ecosystem" audit (4310 OpenClaw skills), Penligent AI CVE-2026-0755, Snyk mcp-run-python SSRF, THN Anthropic CC Security
- **guide/security/security-hardening.md** — CVE table updated with CVE-2026-0755 and mcp-run-python SSRF entries + critical warning note (no patch available)

## [3.28.1] - 2026-02-22

### Added

- **Visual Diagrams Series** — 40 Mermaid interactive diagrams in new `guide/diagrams/` directory (10 thematic files)
  - Files: 01-foundations, 02-context-and-sessions, 03-configuration-system, 04-architecture-internals, 05-mcp-ecosystem, 06-development-workflows, 07-multi-agent-patterns, 08-security-and-production, 09-cost-and-optimization, 10-adoption-and-learning
  - Each diagram: Mermaid (GitHub-native rendering) + ASCII fallback in `<details>` + source link
  - Consistent Bold Guy palette across all diagrams (6-color system)
  - Cross-linked from `visual-reference.md`, `guide/README.md`, and `reference.yaml`
  - Covers: 4-layer model, master loop, memory hierarchy, model selection, MCP rug pull attack, 3-layer defense, multi-agent topologies, TDD/spec-first/plan-driven workflows, UVAL protocol, trust calibration

- **guide/ultimate-guide.md — Managing Large MCP Server Sets** (section 8.3)
  - Documented problem: loading too many servers globally degrades Claude's tool selection
  - Recommended pattern: minimal global config (2-3 servers) + per-project `.mcp.json`
  - Mention of community tool cc-setup (TUI registry with health checks)
- **guide/workflows/plan-driven.md — Section "Advanced: Custom Markdown Plans (Boris Tane Pattern)"** (+169 lines)
  - 3-phase workflow: Emphatic Research → Annotation Cycle → Mechanical Implementation
  - Comparison table `/plan` native vs custom `.md` (selection criteria)
  - Annotation Cycle diagram with loop, guard prompt and exit criteria
  - Phase 1: why emphatic language changes Claude's behavior
  - Phase 2: Aristote-ready plan.md structure, exit criteria, Boris Tane quote
  - Phase 3: mechanical mindset, terse feedback
  - Complementary techniques table (cherry-picking, scope trimming, revert & re-scope)
  - Source: Boris Tane (Engineering Lead @ Cloudflare), Feb 2026
- **guide/ultimate-guide.md — AI Code Disclosure Policy** (section 3.5)
  - Threshold >10 consecutive lines = mandatory declaration
  - PR template: "What the AI did / What I did"
  - Graduated enforcement by level (junior → senior)
  - "Hidden vibe coding" anti-pattern documented
- **guide/ultimate-guide.md — claude-mem with Gemini** (section claude-mem)
  - Gemini 2.5 Flash alternative: $14/month vs Haiku $102/month (-86%)
  - Configuration instructions via localhost:37777 dashboard
  - Model comparison table with measured monthly cost (400 sessions/month)
- **guide/ultimate-guide.md — critical claude-mem gotchas** (section claude-mem)
  - Hooks coexistence: before/after JSON, silent overwrite risk documented
  - Fail-open v9.1.0+: worker down doesn't block Claude Code, restart instructions
- **guide/core/methodologies.md**: cross-reference to Boris Tane Pattern from Plan-First section
- **machine-readable/reference.yaml**: 4 new entries (`annotation_cycle_pattern`, `custom_markdown_plans`, `boris_tane_source`, `boris_tane_author`)
- **docs/resource-evaluations/boris-tane-how-i-use-claude-code.md**: formal evaluation (score 4/5, fact-check, integration decision)
- **docs/resource-evaluations/aristote-ai-instructions-patterns.md**: Méthode Aristote production patterns analysis (24 ai-instructions files)
- **guide/security/security-hardening.md — Part 4: Integration** (+104 lines)
  - **4.1 PR Security Review Workflow**: 3-agent pipeline (security-auditor → data flow trace → security-patcher), ready-to-use prompts
  - Table by change type (API endpoint, DB query, auth, file upload, third-party lib) with risk levels
  - Git `pre-push` hook to alert on sensitive files (auth, payment, token, session)
  - **Claude Code Security (Research Preview)**: presentation of Anthropic feature on waitlist, comparison with Security Auditor Agent
- **examples/agents/security-patcher.md**: new agent (companion to security-auditor)
  - Limited scope: applies patches identified by security-auditor, never autonomously
  - Explicit separation of responsibilities: auditor detects, patcher fixes
  - Proposes patches for human review, applies nothing without approval
- **examples/hooks/bash/security-gate.sh**: new PreToolUse hook
  - Detects application security anti-patterns before writing to source files
  - Complements `dangerous-actions-blocker.sh` (system ops) — focuses on application code
  - Exit 0 = allow, Exit 2 = block with contextual message
- **guide/workflows/pdf-generation.md**: "Output Formats & Commands" diagram (+48 lines)
  - 3-column ASCII table (format / command / output) with distinction between standard vs styled PDF
  - EPUB commands, live preview, batch loop with error summary
- **examples/skills/pdf-generator.md**: generation pipeline diagram (+28 lines)
  - ASCII diagram SOURCE → Quarto → template → Typst → PDF with output size annotations
- **docs/resource-evaluations/2026-02-22-boris-cherny-worktree-tips-reddit.md**: evaluation of Boris Cherny Reddit/Twitter (Claude Code creator) — 5 worktree tips, 40.2K views
- **docs/resource-evaluations/2026-02-22-guillaume-moigneu-worktree-linkedin.md**: evaluation of Guillaume Moigneu LinkedIn (Solution Architect @ Upsun) — built-in git worktree support

- **guide/ops/observability.md — 3 new monitoring sections** (+214 lines)
  - **Activity Monitoring**: audit of Claude Code actions via session JSONL — which files were read, commands executed, URLs fetched. Ready-to-use `jq` queries. Table of sensitive patterns (.env, rm -rf, external WebFetch)
  - **External Monitoring Tools**: comparison table ccusage / claude-code-otel / Akto / MLflow / ccboard with decision guide and install examples
  - **Proxying Claude Code**: why Proxyman/Charles fail (Node.js ignores system proxies), 4 solutions: `NODE_EXTRA_CA_CERTS`, `ANTHROPIC_API_URL`, mitmproxy (recommended), minimal Python proxy
- **docs/resource-evaluations/ccboard-activity-module-plan.md**: complete plan for the ccboard Activity module (Tab 10)
  - Rust data models (`ToolCall`, `FileAccess`, `BashCommand`, `NetworkCall`, `Alert`)
  - JSONL stream parser with destructive/sensitive detection
  - SQLite schema + lazy cache strategy (invalidation by mtime)
  - TUI layout with 5 sub-tabs (Files/Commands/Network/Alerts/Timeline)
  - Web API endpoints (`GET /api/activity/:session_id/...`)
  - 7 alert rules with severities
  - 5 implementation phases with checklists
- **machine-readable/reference.yaml**: 6 new entries (`activity_monitoring`, `external_monitoring_tools`, `proxying_claude_code`, `ccboard_activity_plan`...)

## [3.28.0] - 2026-02-21

### Added

- **Section 2.5 — Model Selection & Thinking Guide**: canonical section consolidated in `guide/ultimate-guide.md`
  - 4-column decision table (Task / Model / Effort / Estimated cost per task)
  - Effort levels with concrete examples of calibrated prompts (low/medium/high/max)
  - Model-per-agent patterns: planner (Opus), implementer (Haiku), architecture-reviewer (Opus)
  - "When Thinking Helps vs. Wastes Tokens" table
  - Cross-refs to OpusPlan, Rev the Engine, Cost Awareness
- **3 new agent templates** (`examples/agents/`)
  - `planner.md` — Opus, read-only, strategy before implementation
  - `implementer.md` — Haiku, mechanical execution, escalation note to Sonnet for business logic
  - `architecture-reviewer.md` — Opus, critical read-only review, verification protocol before assertion
- **7 new quiz questions** (09-037 → 09-043) in `quiz/questions/09-advanced-patterns.yaml`
  - Covers: model selection by task, `model:` frontmatter, `effort` parameter, Adaptive Thinking Opus 4.6

### Changed

- **3 redundant tables replaced** by cross-refs to Section 2.5:
  - Tactical Model Selection Matrix (Section 4)
  - Cost-Effective Model Selection (Section 12)
  - Model Selection Matrix (Section 9.13)
- **Effort levels enriched** (Section 9 Adaptive Thinking): concrete prompt examples added + cross-ref to 2.5
- **Sections 2.6→2.10 renumbered** to make room for new 2.5 (former Mental Model 2.5 → 2.6, etc.)
- **Cheatsheet**: condensed Quick Model Selection table added (3 lines + cross-ref)
- **`examples/README.md`**: agents count 6 → 9, 3 new lines in table
- **`machine-readable/reference.yaml`**: stale line numbers fixed, 4 new entries

## [3.27.9] - 2026-02-21

### Documentation

- **Claude Code Releases**: Updated tracking to v2.1.50
  - `WorktreeCreate`/`WorktreeRemove` hook events; `isolation: worktree` in agent definitions
  - `claude agents` CLI command; `CLAUDE_CODE_DISABLE_1M_CONTEXT` env var
  - Opus 4.6 fast mode now has full 1M context window
  - Major memory leak fixes + headless mode startup performance improvements

### Added

- **Talk Preparation Pipeline** — 6-stage skill pipeline: raw material → conference talk → Kimi slides
  - New workflow guide: `guide/workflows/talk-pipeline.md` (REX vs Concept modes, stage-by-stage guide, design patterns, real-world example)
  - New skill templates: `examples/skills/talk-pipeline/` (7 SKILL.md files + 2 templates)
    - Stage 1: Extract (source → structured summary, type auto-detection)
    - Stage 2: Research (REX only — git archaeology, changelog analysis, verified timeline)
    - Stage 3: Concepts (numbered, scored catalogue — HIGH/MEDIUM/LOW)
    - Stage 4: Position (angles, titles, descriptions, peer feedback draft + mandatory CHECKPOINT)
    - Stage 5: Script (5-act pitch, slide spec, Kimi prompt for AI slide generation)
    - Stage 6: Revision (master concept table, Q&A cheat-sheet, glossary)
    - Orchestrator (runs full pipeline from one invocation, routes by mode)
  - Generic Kimi template: `stage-5-script/templates/kimi-prompt-template.md` (dark theme, orange accent, WCAG AA)
  - Peer feedback template: `stage-4-position/templates/feedback-draft.md` (3 formats: Slack, email, LinkedIn)
  - Design patterns documented: skill chaining + file-based state, tool permission scoping, human-in-the-loop gate, AI-to-AI handoff (Claude → Kimi), dual execution modes
  - `reference.yaml`: 16 entries for talk pipeline components
  - `guide/workflows/README.md`: Talk Pipeline entry under Design & Content + Quick Selection Table

- **Resource evaluation**: Mergify "Cross-System Support Investigator" (score 4/5)
  - Production case study: Claude Code + 5 MCP servers (Datadog, Sentry, PostgreSQL, Linear, GitHub) for support ticket triage
  - Architecture pattern: Claude Code as operational orchestrator with parallel fan-out across MCP adapters
  - Results (self-reported): triage 15 min → <5 min; 75% first-pass accuracy
  - Integrated in `guide/ultimate-guide.md` §8.4 → new "Production Case Study" subsection with architecture diagram
  - Evaluation archived: `docs/resource-evaluations/2026-02-20-mergify-cross-system-support-investigator.md`

/- **Resource evaluation**: "Evaluating AGENTS.md" — ETH Zürich arXiv 2602.11988 (score 4/5)
  - First empirical study on repository-level context files (AGENTS.md/CLAUDE.md) effectiveness
  - Developer-written context files: **+4% agent success rate**; LLM-generated: **-3%** vs no context file
  - Inference cost penalty: **+20-23% in all cases** when file contains non-essential information
  - Mechanism: agents follow all instructions faithfully, even irrelevant ones → broader exploration, longer reasoning chains
  - Recommendation: include only build/test commands + project-specific tooling; style guides → separate docs
  - Benchmark: AGENTbench (138 instances, 12 repos) + SWE-bench Lite; 4 coding agents (Claude Code, Codex, Qwen Code)
  - Source: Gloaguen, Mündler, Müller, Raychev, Vechev — ETH Zürich, February 2026
  - Evaluation archived: `docs/resource-evaluations/agents-md-empirical-study-2602-11988.md`

### Changed

- `guide/ultimate-guide.md`: Added empirical research backing to CLAUDE.md Token-Saving Techniques section (~l.13393-13411)
  - New callout: context files with non-essential info add +20-23% inference cost regardless of line count (Gloaguen et al., 2026)
  - New research note after "Keep CLAUDE.md concise" best practice: +4% (dev-written) / -3% (LLM-generated) with mechanism explanation and tooling recommendation

- `guide/workflows/spec-first.md`: New "Task Granularity" section — vertical slices + PRD quality checklist
  - Vertical slice definition: thin, end-to-end unit for exactly one user behavior; one agent session = one slice
  - 6-dimension PRD quality checklist (Problem Clarity, Testable Criteria, Scope Boundaries, Observable Done, Requirements Clarity, Terminology)
  - Concrete example: over-scoped task vs properly-sized vertical slice
  - Inspired by Allan Hill (Fractional CTO) — [evaluation](docs/resource-evaluations/2026-02-19-allanhillgeek-decomposition-agentic-dev.md) (3/5)

- `guide/core/methodologies.md`: Expanded ATDD section with agentic application
  - Added 3-step agent workflow: Gherkin → failing tests → implementation
  - Gherkin example for "password reset" feature
  - Practical note: how to pass Gherkin file to Claude Code as task contract

- `machine-readable/reference.yaml`: 3 new index entries (`spec_task_granularity`, `spec_prd_checklist`, `atdd_with_agents`)

- **Resource evaluation**: Sylvain Chabaud — Spec-to-Code Factory (score 3/5)
  - Multi-agent pipeline BREAK→MODEL→ACT→DEBRIEF with 6 tooled validation gates (Node.js)
  - "No Spec No Code" + "No Task No Commit" invariants enforced via hooks — enforcement pattern not documented in the guide
  - Transparent token budget per phase (~900K total) — unique concrete estimate in the ecosystem
  - Mention added in `guide/core/methodologies.md` (SDD Tools table) and `guide/workflows/spec-first.md` (See Also)
  - Evaluation archived: `docs/resource-evaluations/sylvain-chabaud-spec-to-code-factory.md`

- **New Section 3.5**: Team Configuration at Scale — Profile-Based Module Assembly pattern
  - Covers N×M×P fragmentation problem (N devs × M tools × P OS) with modular solution
  - Architecture: profiles YAML + shared modules + skeleton template + TypeScript assembler script
  - Measured results: 59% context token reduction (380 → 185 lines avg, 5-dev production team)
  - CI drift detection via GitHub Actions daily check
  - 5-step replication guide + trade-offs table (when NOT to use)
  - Inserted between Section 3.4 (Precedence Rules) and Section 4 (Agents)

- **New workflow**: `guide/workflows/team-ai-instructions.md` — step-by-step setup guide
  - 6 phases: Audit → Extract Modules → Create Profiles → Assembler Script → CI Integration → Onboarding
  - Scaling thresholds: 1-2 devs (shared CLAUDE.md) → 3-5 (modules only) → 5+ (full profile assembly)
  - Troubleshooting table for common issues

- **New templates**: `examples/team-config/` — ready-to-use Profile-Based Assembly templates
  - `profile-template.yaml`: developer profile with core + conditional modules
  - `claude-skeleton.md`: CLAUDE.md template with `{{MODULE:*}}` and `{{#if}}` placeholders
  - `sync-script.ts`: TypeScript assembler with module resolution, conditional blocks, drift detection

- **reference.yaml**: 9 new entries for `team_ai_instructions_*` (section, workflow, templates, pattern, token savings)

## [3.27.8] - 2026-02-19

### Added

- **New GitHub Actions workflow**: `examples/github-actions/claude-code-review.yml` — prompt-based code review pattern
  - Uses `anthropics/claude-code-action@v1` with OAuth token support (API key as fallback)
  - Triggers on PR open/sync/ready + `/claude-review` on-demand comment
  - Scoped `allowed_tools`: read-only (Read, Glob, Grep + GitHub PR inspection/review tools)
  - Externalized prompt via `prompt_file:` — iterate on criteria without touching workflow YAML
- **New prompt template**: `examples/github-actions/prompts/code-review.md`
  - Anti-hallucination protocol: verify before reporting, no invented line numbers
  - Structured severity tiers: 🔴 MUST FIX / 🟡 SHOULD FIX / 🟢 CAN SKIP
  - 4-step workflow: gather context → analyze → verify → structured review output
  - Stack-agnostic with explicit "Stack Context" customization hook

- **Resource evaluation**: SKILLMIND/Boris Cherny workflow practices (score 2/5)
  - LinkedIn post by @stasbel (64K followers) sharing SKILL.md file attributed to Boris Cherny (Claude Code creator)
  - 6 workflow orchestration practices + 6 task management items + 3 core principles
  - Key concept: `tasks/lessons.md` self-improvement loop (Claude captures corrections as rules, reviewed each session)
  - Score 2/5: majority of content already covered in guide; novel delta = lessons.md naming convention vs PROGRESS.md
  - Evaluation file: `docs/resource-evaluations/2026-02-19-stasbel-skillmind-boris-cherny-workflow.md`

- **Resource evaluation**: Augment Context Engine MCP (score 3/5)
  - Cloud-hosted semantic code search MCP (launched Feb 6, 2026); indexes up to 500K files across repos/wikis
  - Self-published benchmark: 80% quality improvement on 300 Elasticsearch PRs (Claude Opus 4.5, not 4.6 as stated on product page)
  - Relevant as cloud alternative to grepai: managed, multi-repo, no local setup, but paid ($20+/month) and cloud-hosted
  - Evaluation file: `docs/resource-evaluations/2026-02-19-augment-context-engine-mcp.md`

- **Resource evaluation**: LinkedIn "Context Engineering" post (score 2/5)
  - Promotional LinkedIn post on "prompt engineering is dead, context engineering is king" — marginal relevance
  - Evaluation file: `docs/resource-evaluations/2026-02-19-linkedin-context-engineering-augment.md`

- **Resource evaluation**: LinkedIn activity-7428930570451083264 (inaccessible)
  - Could not fetch — LinkedIn authentication required
  - Evaluation file: `docs/resource-evaluations/2026-02-19-linkedin-activity-7428930570451083264.md`

### Changed

- `examples/github-actions/README.md`: added entry for prompt-based workflow (⭐ Recommended), updated directory tree
- `guide/ultimate-guide.md`: Added `tasks/lessons.md` variant to Fresh Context Pattern (Ralph Loop) section
  - Lightweight alternative for interactive sessions: Claude updates lessons.md with behavioral rules after each user correction
  - Reviewed at session start for compounding improvement effect
  - Clarifies distinction from PROGRESS.md (task state) vs lessons.md (behavioral rules)
- `CLAUDE.md`: Added Whitepaper Generation section (PDF + EPUB commands, stack documentation)

### Documentation

- **Claude Code Releases**: Updated tracking to v2.1.47 (from v2.1.45)
  - v2.1.47: VS Code plan preview auto-updates, `ctrl+f` kills all background agents, `last_assistant_message` hook field, 70+ bug fixes
  - v2.1.46: claude.ai MCP connectors support, orphaned process fix on macOS

## [3.27.7] - 2026-02-19

### Added

- **Resource evaluation**: Borg et al. "Echoes of AI" RCT (arXiv:2507.00788)
  - 2-phase blind controlled experiment, 151 participants (95% professional developers)
  - AI users 30.7% faster (median), habitual users ~55.9% faster
  - No significant maintainability impact for downstream developers — first RCT to explicitly target this question
  - Fact-checked against primary source; v2 (Dec 2025) confirmed via Perplexity
  - Co-authored by Dave Farley ("Continuous Delivery")
  - Evaluation file: `docs/resource-evaluations/2026-02-19-echoes-of-ai-maintainability-study.md`

### Changed

- `guide/roles/learning-with-ai.md`: Added Borg et al. 2025 RCT citation in Productivity Research bibliography (revised to factual/neutral wording after technical-writer audit)
- `guide/roles/learning-with-ai.md`: Added "On maintainability fear" note in "Why Some Teams Get Results" section — the real risks are skill atrophy and over-delegation, not downstream quality degradation
- `guide/ultimate-guide.md`: Added downstream maintainability nuance blockquote in §1.7 Trust Calibration — defect rates ≠ maintenance burden (Borg et al. 2025 blind RCT)
- `machine-readable/reference.yaml`: Added 4 entries — `productivity_rct_metr`, `productivity_rct_echoes`, `productivity_maintainability_empirical`, `trust_calibration_maintainability_nuance`
- Landing `faq/index.astro`: Updated "How much should I trust AI-generated code?" — added maintainability nuance (HTML visible answer + JSON-LD structured data)

## [3.27.6] - 2026-02-18

### Added
- New subsection "200K vs 1M Context: Performance, Cost & Use Cases" with MRCR benchmark table, cost-per-session table, decision guide, and key facts
- Community findings from Reddit/HN/blogs: Gemini comparison, "70% context → new session" workaround, real-world use case limits
- HN community validation reference: Opus 4.6 retrieves 49/50 spells across ~733K tokens (Harry Potter test)
- `machine-readable/reference.yaml`: 5 new entries for Sonnet 4.6 + context window comparison

### Changed
- Pricing table: Sonnet 4.6 now listed as default model (replaced Sonnet 4.5)
- Context Management section: updated to mention 1M beta with link to comparison subsection
- `threat-db.yaml` v2.1.0: added CVE-2026-23744 (MCPJam RCE), hightower6eu publisher (314+ malicious skills), Slopsquatting technique T009, Mcpwn scanner, OWASP Agentic AI Top 10 2026, new sources (VirusTotal, SentinelOne, Immersive Labs, arXiv)
- `cheatsheet.pdf`: updated binary

### Fixed
- Beta header corrected: `interleaved-thinking-2025-05-14` → `context-1m-2025-08-07` (different feature, deprecated on Opus 4.6)
- Sonnet 4.6 long-context pricing: added premium tier ($3→$6 / $15→$22.50 above 200K — applies to all models)
- Cost estimates recalculated: Sonnet 4.6 @ 1M ~$4.13 (was $2.25), Opus 4.6 @ 1M ~$6.88 (was $8.75)
- Restored Opus 4.6 MRCR 93% @ 256K with confirmed source (independent analysis of Anthropic data)
- Added usage tier 4 requirement (1M context not available on tiers 1–3)
- Clarified premium pricing applies to all tokens in request once input exceeds 200K (not just excess)

## [3.27.5] - 2026-02-17

### Documentation

- **Claude Code Releases**: Updated tracking to v2.1.45
  - Claude Sonnet 4.6 model support
  - `spinnerTipsOverride` setting for customizable spinner tips
  - SDK `SDKRateLimitInfo` / `SDKRateLimitEvent` for rate limit tracking
  - Fixed Agent Teams on Bedrock/Vertex/Foundry; memory improvements for large outputs

## [3.27.4] - 2026-02-17

### Added

- **Review Plan command template** (`examples/commands/review-plan.md`)
  - Structured plan review across 4 axes: architecture, code quality, tests, performance
  - Inspired by Garry Tan's (YC CEO) Plan Mode prompt, adapted for Claude Code's native config system
  - Includes BIG CHANGE / SMALL CHANGE modes, numbered issues with lettered options, "do nothing" option
  - Uses AskUserQuestion for structured interaction
- **Rules templates** (`examples/rules/`) — new directory
  - `architecture-review.md`: system design, dependencies, data flow, scaling, security
  - `code-quality-review.md`: organization, DRY violations, error handling, tech debt, engineering balance
  - `test-review.md`: coverage gaps, test quality, edge cases, failure modes
  - `performance-review.md`: database access, memory, caching, complexity

- **AI Kill Switch & Containment Architecture** (`guide/security/security-hardening.md` §3.5)
  - Three-level kill switch mapped to Claude Code mechanisms (scoped revocation → velocity governor → global hard stop)
  - Ready-to-use `velocity-governor.sh` hook example (rate-limiter for runaway agents)
  - Regulatory context: EU AI Act (Aug 2025), CoSAI AI Incident Response Framework V1.0, governance-containment gap stats
  - Sources: Fortune Dec 2025, CDOTrends Jan 2026, OASIS/CoSAI Nov 2025
- **AI-specific incident cross-reference** (`guide/ops/devops-sre.md`)
  - Added pointer from "When NOT to Use Claude" to security-hardening.md for AI incidents (prompt injection, MCP compromise, agent exfiltration)

- **Git Worktree command suite** (`examples/commands/`)
  - `git-worktree.md`: Overhauled — symlink `node_modules` by default, background verification, `--fast`/`--isolated` flags, companion command links
  - `git-worktree-status.md`: New — check background verification tasks (type check, tests, build)
  - `git-worktree-remove.md`: New — safe removal with branch cleanup, merge verification, DB teardown
  - `git-worktree-clean.md`: New — batch cleanup of stale/merged worktrees

### Updated

- **Claude Code Releases**: Updated tracking v2.1.42 → v2.1.44
  - v2.1.44: Auth refresh error fix
  - v2.1.43: AWS auth refresh timeout (3min), structured-outputs beta header fix on Vertex/Bedrock, non-agent markdown warnings fix
- **`reference.yaml`**: Added 12 new entries (review-plan, rules templates, git-worktree suite, security kill switch), updated resource evaluations count 67 → 74
- **Template count**: 113 → 116 (review-plan command, git-worktree-status/remove/clean commands, rules templates) — updated across README, CLAUDE.md, reference badges
- **Commands count**: 23 → 26 (git-worktree-status, git-worktree-remove, git-worktree-clean)

## [3.27.3] - 2026-02-16

### Updated

- **Claude Code Releases**: Updated tracking v2.1.41 → v2.1.42
  - v2.1.42: Startup optimization (deferred Zod schema), prompt cache hit rate improvement (date outside system prompt), Opus 4.6 effort callout, `/resume` and image error UX fixes

## [3.27.2] - 2026-02-15

### Added

- **YAML frontmatter on 90 markdown files** across `guide/` and `examples/`
  - Schema A (title, description, tags): 24 guide top-level + 15 workflow files
  - Schema B (name, description): 20 command templates (matches existing convention)
  - Schema C (title, description, tags with claude-md): 5 claude-md templates
  - Schema D (title, description, tags): 7 READMEs + 19 miscellaneous example files
  - Controlled tag vocabulary: 15 domains, 11 content types, 9 features
  - 18 files with existing frontmatter correctly skipped
  - Enables machine-readable metadata for navigation, SSG, SEO, and LLM consumption

## [3.27.1] - 2026-02-15

### Added

- **Grepai MCP documentation** (`guide/ecosystem/mcp-servers-ecosystem.md`)
  - New "Code Search & Analysis" section (~130 lines): semantic search, call graph tracing, setup guide
  - Privacy: fully local (Ollama + nomic-embed-text), zero data exfiltration
  - Token efficiency comparison: grepai 2-3K tokens vs Grep+Read 15K for same results
  - Cross-referenced from `reference.yaml`

- **2 new resource evaluations** (both scored 2/5 — not integrated)
  - `system-prompts-opus-4-6-update.md`: Re-evaluation of x1xhlol system prompts repo (Opus 4.6 update), still redundant
  - `2026-02-14-simone-ruggiero-qmd-token-savings-medium.md`: qmd token savings tool (Medium article), claims unverifiable, redundant with grepai

- **2 new hook templates** (`examples/hooks/bash/`)
  - `rtk-baseline.sh`: SessionStart hook — saves RTK gain baseline for delta tracking
  - `session-summary.sh`: SessionEnd hook — auto-displays session summary (inspired by Gemini CLI)

- **Watch list entry**: o16g (Outcome Engineering) — emerging framework by Cory Ondrejka (ex-VP Google/Meta)

### Changed

- **RTK documentation overhaul** (v0.7.0 → v0.16.0, 446 stars, rtk-ai org)
  - Updated 15+ files across guide + landing: org migration (rtk-ai/rtk), removed fork distinction
  - Added: Python, Go, Homebrew, hook-first install, `rtk init`, `rtk tree`, `rtk learn`
  - Removed outdated ls/grep warnings (bugs resolved in v0.16.0)
  - Evaluation score: 4.5/5 → 5/5 (446 stars, [700+ Reddit upvotes](https://www.reddit.com/r/ClaudeAI/comments/1r2tt7q/))
  - Landing site updated: Homebrew install, new command grid (cargo/python/go), removed name collision warning
  - `~/.claude/CLAUDE.md`: replaced fork install with cargo/Homebrew

- **Exports deprecated** — Moved `kimi.pdf` and `notebooklm.pdf` to `exports/deprecated/` (generated from ~9K line v1.x era, guide now ~19K lines)

### Fixed

- **Fact-check corrections across 22 files** (866 insertions, 308 deletions)
  - CVEs: 22→18 (7 files: README, CHANGELOG, SECURITY, competitive-analysis, etc.)
  - Resource evaluations: 56→67 (README), 55→67 (reference.yaml), 14→68 (CLAUDE.md)
  - Templates: 111→120 (badges), breakdown 22 commands→23, 18 hooks→30
  - Quiz questions: 257→264 (README, CLAUDE.md, reference.yaml, ai-ecosystem)
  - Guide lines: 11K→19K (competitive-analysis, CLAUDE.md, ai-ecosystem, audit-cheatsheet-prompt)
  - CLAUDE.md: version 3.9.9→3.27.0, evaluations 14→68, quiz 257→264
  - MCP ecosystem: updated date Jan→Feb 2026, added Code Search TOC entry

- **README positioning fact-check** (4 files, 21 edits)
  - Template count: 120/123 → **108** (ground truth recount: hooks 30→31, workflows 2→3, multi-provider removed)
  - Ratio: 14× → **24×** (19,000 ÷ 784 = 24.2×, added "16 specialized guides" context)
  - everything-claude-code stars: 31.9k → **45k+** (verified 2026-02-15)
  - Commands count in README: 20→23 (aligned with examples/README.md)
  - Added missing entries to `examples/README.md`: `session-summary-config.sh` (hook), `memory-stack-integration.md` (workflow)

## [3.27.0] - 2026-02-12

### Added

- **Watch List** (`docs/resource-evaluations/watch-list.md`)
  - Public tracker for resources monitored but not yet integrated (tools, MCP servers, articles, libraries)
  - Event-driven re-evaluation (trigger-based, not time-based) to avoid stale dates
  - 3 sections: Active Watch, Graduated, Dropped
  - Initial entries: ICM (MCP, pre-v1), System Prompts (x1xhlol, redundant with official sources)
  - Cross-referenced from `mcp-servers-ecosystem.md` (Monitor workflow) and `resource-evaluations/README.md`
  - Added to `reference.yaml` as `resource_evaluations_watchlist`
  - Replaces private `claudedocs/` watch list (deleted)

- **Entire CLI Integration** (launched Feb 2026 by Thomas Dohmke, ex-GitHub CEO, $60M funding)
  - Comprehensive coverage across 7 guide files: ai-traceability, third-party-tools, observability, ai-ecosystem, ultimate-guide, security-hardening, cheatsheet
  - **Replaces deprecated git-ai** (404 repo) in AI Traceability Guide with production-ready alternative
  - **Fills "Session replay" gap** documented in Known Gaps with rewindable checkpoints
  - Governance layer documentation for compliance use cases (SOC2, HIPAA, FedRAMP)
  - Agent handoff workflows for multi-agent orchestration (Claude → Gemini)
  - Session portability alternative to native `--resume` limitations
  - Quick reference added to community tools section
  - Formal resource evaluation created (docs/resource-evaluations/entire-cli.md) with 5/5 critical scoring

### Fixed

- **Corrected git-ai references** (ai-traceability.md section 5.1) - repo is 404, replaced with Entire CLI

## [3.26.0] - 2026-02-11

### Added

- **Security Threat Intelligence Database** (`examples/commands/resources/threat-db.yaml` v2.0.0)
  - Comprehensive threat DB compiled from Perplexity Deep Research across 15 sources
  - **63 malicious skills** catalogued (ClawHavoc 341 skills, Snyk ToxicSkills, PyPI supply chain)
  - **18 CVEs** tracked with component, severity, fixed_in version, and mitigation
  - **4 campaigns** documented: ClawHavoc (AMOS), ToxicSkills, PyPI MCP reverse shell, Postmark npm squatter
  - **IOCs**: 6 C2 IPs, exfiltration endpoints, malicious GitHub repos, malware hashes
  - **17 malicious skill patterns** for wildcard matching (prefix-based scanning)
  - **10 minimum safe versions** quick reference for MCP servers
  - **8 attack techniques** taxonomy (T001-T008) mapped to campaigns
  - **6 scanning tools** documented (mcp-scan, skills-ref, Garak, MCP Fortress, SafeDep vet, Koi Clawdex)
  - **5 defensive resources** (SAFE-MCP framework, VirusTotal integration, Docker MCP Gateway, Snyk AI-BOM, Bitsight TRACE)
  - Sources: Koi Security, Snyk, JFrog, Flatt Security, SentinelOne, Cymulate, Checkpoint, Bitsight, SafeDep, SAFE-MCP

- **New Slash Command**: `/security-check` (`examples/commands/security-check.md`)
  - Quick (~30s) configuration security check against known threats database
  - 7 phases: Load threat DB → MCP audit → Skills/agents audit → Hook security → Memory poisoning → Permissions → Exposed secrets
  - Outputs CRITICAL/HIGH/MEDIUM/LOW findings with exact fix commands

- **New Slash Command**: `/security-audit` (`examples/commands/security-audit.md`)
  - Full 6-phase security audit with scored posture assessment (/100, grades A-F)
  - Phases: Config (via /security-check) → Secrets scan → Injection surface → Dependencies → Hook security → Posture score
  - Includes benchmark against security-hardening.md recommendations

- **New Slash Command**: `/update-threat-db` (`examples/commands/update-threat-db.md`)
  - Research & update the threat intelligence database via Perplexity searches
  - 6 phases: Assess current state → 4 targeted searches → Deduplicate → Update YAML → Cascade to guides → Summary report
  - Designed for monthly maintenance or post-advisory updates

- **Threat DB Badge** in README: red badge linking to security-hardening.md showing CVE and malicious skill counts

- **Resource Evaluation**: "AI Fatigue is Real" by Siddhant Khare (`docs/resource-evaluations/siddhant-khare-ai-fatigue.md`)
  - Score: 3/5 — Time-boxing tactics, nondeterminism stress recognition

### Changed

- **README**: Commands count updated 18→22, 3 new security commands listed in examples library
- **CLAUDE.md**: Slash commands table updated with `/security-check`, `/security-audit`, `/update-threat-db`
- **reference.yaml**: 4 new entries (security_check_command, security_audit_command, security_threat_db, security_update_threat_db)
- **Learning Guide Enhancement**: AI fatigue symptom recognition integrated into `guide/roles/learning-with-ai.md`
  - Red Flags Checklist, Productivity Reality, UVAL Protocol sections updated

### Fixed

- **Extended Thinking Documentation**: Corrected `effort` parameter documentation based on [official Anthropic docs](https://platform.claude.com/docs/en/build-with-claude/effort)
  - API syntax, scope clarification, official descriptions, control table, effort and tool use subsection

## [3.25.0] - 2026-02-10

### Added

- **New Mental Model Section**: "From Chatbot to Context System" (§2.5)
  - Addresses critical gap identified by [Robin Lorenz](https://www.linkedin.com/in/robin-lorenz-54055412a/) ([comment](https://www.linkedin.com/feed/update/urn:li:activity:7426936437746352128?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7426936437746352128%2C7426941635306987520%29))
  - AI Engineer, 17-agent orchestration in production
  - Four-layer framework unifying CLAUDE.md, skills, hooks, and project memory
  - Comparison table: What each layer does, when to set up (Week 1-3 + Ongoing)
  - Before/After examples: Chatbot mode vs Context system mode
  - Cross-references to §3.1 (Memory Files), §5 (Skills), §7 (Hooks), §9.10 (Continuous Improvement)
  - Location: guide/ultimate-guide.md line 2636 (after "You Are the Main Thread", before "Communicating Effectively")
  - **Impact**: Presents CLAUDE.md/skills/hooks/memory not as independent features but as layers of a unified context system
  - **Concept**: "Stop treating it like a chatbot. Give it structured context. Changes everything." — Robin Lorenz

### Changed

- **Mistake #8 Rewritten**: "Not Using CLAUDE.md" → "Treating Claude Code Like a Chatbot" (§1.8)
  - Expanded scope: From single-feature warning to systematic context building approach
  - Fix now includes: CLAUDE.md + Skills + Hooks (3-layer solution instead of 1)
  - Cross-reference to new §2.5 section for full framework
  - Location: guide/ultimate-guide.md line 1274

- **Key Mindset Shift Updated**: Section 1.6 comparison table
  - Before: "conversational coding partner, not an autocomplete tool"
  - After: "structured context system, not a chatbot or autocomplete tool"
  - Added cross-reference to §2.5 for context system framework
  - Location: guide/ultimate-guide.md line 849

- **Quick Self-Check Enhanced**: Added cross-reference to CLAUDE.md checklist item
  - Checklist item now links to §2.5 for context on why CLAUDE.md matters
  - Location: guide/ultimate-guide.md line 1290

- **Continuous Improvement Mindset**: Added cross-reference to new §2.5 section
  - Links the "fix the system that produces the code" philosophy to the 4-layer framework
  - Location: guide/ultimate-guide.md line 12086 (after Nick Tune quote, before §9.11)

## [3.24.0] - 2026-02-10

### Added

- **Resource Evaluation**: nao framework (`docs/resource-evaluations/nao-framework.md`)
  - Evaluated open-source framework for building analytics agents
  - Score: 3/5 (Moderate - Useful Complement)
  - Identified critical gap: Agent evaluation not documented in guide
  - Technical challenge by technical-writer agent adjusted score from 2/5 to 3/5
  - All technical claims fact-checked (TypeScript 58.9%, Python 38.5%, stack verified)

- **New Guide Section**: Agent Evaluation (`guide/roles/agent-evaluation.md`, ~3000 tokens)
  - **Why Evaluate Agents**: Quantify quality, compare configurations, build feedback loops
  - **Metrics to Track**: Response quality, tool usage, performance, user satisfaction
  - **Implementation Patterns**: Logging hooks, unit tests, A/B testing, feedback loops
  - **Example**: Analytics agent with built-in metrics collection
  - **Tools & References**: nao framework as reference, Claude Code hooks integration
  - Addresses critical gap identified in nao evaluation
  - Navigation: After `guide/ultimate-guide.md` Section 4 (Agents)

- **AI Ecosystem Update**: Section 8.2 Domain-Specific Agent Frameworks (`guide/ecosystem/ai-ecosystem.md`)
  - New subsection after "Multi-Agent Orchestration Systems"
  - **nao (Analytics Agents)**: Database-agnostic framework with built-in evaluation
  - Transposable patterns: Context builder architecture, evaluation hooks, database integrations
  - Links to new `guide/roles/agent-evaluation.md` for implementation details
  - Location: guide/ecosystem/ai-ecosystem.md lines 1612-1638

- **Template**: Analytics Agent with Evaluation (`examples/agents/analytics-with-eval/`, 5 files)
  - **README.md**: Complete setup, usage, troubleshooting (production-ready)
  - **analytics-agent.md**: SQL query generator with evaluation criteria and safety rules
  - **hooks/post-response-metrics.sh**: Automated metrics logging (safety, performance, errors)
  - **eval/metrics.sh**: Analysis script for aggregating collected metrics
  - **eval/report-template.md**: Monthly evaluation report template
  - Demonstrates patterns from `guide/roles/agent-evaluation.md` in complete implementation
  - Includes safety checks (destructive operations), performance monitoring, feedback loops

### Changed

- **Agent Evaluation Guide**: Updated template reference (line 434)
  - Changed "(coming soon)" to "with hooks, scripts, and report template"
  - Added reference to complete template in "Example" section (line 277)
  - All links verified and functional

- **Landing Site**: Templates count synchronized
  - Updated index.html: 110 → 114 templates
  - Updated examples/index.html: 110 → 114 templates
  - Reflects addition of analytics-with-eval template (5 new files)

## [3.23.5] - 2026-02-10

### Added

- **Prompt Template**: `claudedocs/prompts/analyze-claude-mem-integration.md`
  - Comprehensive 6-phase analysis framework for claude-mem integration
  - Designed for Aristote project (EdTech, Next.js/tRPC/Prisma)
  - Audit current memory stack (Serena, grepai, 9 hooks)
  - Cost/ROI estimation ($3.75/month API, 50-100x ROI factor)
  - Integration plan with hooks synergy (activity-logger, serena-sync)
  - Go/No-Go decision criteria

## [3.23.4] - 2026-02-09

### Added

- **Agent Anti-Patterns Section** (§9.17): Critical guidance on proper agent usage
  - Citation from Dex Horty: "Subagents are not for anthropomorphizing roles, they are for controlling context"
  - Wrong vs Right table: Anthropomorphizing (Frontend Agent) vs Context Control (scope-focused agents)
  - When to use agents (good reasons): Context isolation, parallel processing, scope limitation
  - When NOT to use agents (bad reasons): Fake teams, roleplaying, mimicking human org structure
  - Section location: guide/ultimate-guide.md line 3662

### Changed

- **Agent Terminology Refactoring** (Breaking conceptual change): Systematic replacement of role-based language with scope-focused terminology
  - **Section renames**: "Split-Role Sub-Agents" → "Scope-Focused Agents" (line 3709)
  - **Agent definitions**: "Specialized role" → "Context isolation tool" (Skills vs Agents table, line 5490)
  - **Custom agent examples** (3 refactored):
    - code-reviewer: "You are a senior code reviewer" → "Perform comprehensive code reviews with isolated context"
    - debugger: "You are a systematic debugger" → "Perform systematic debugging with isolated context"
    - backend-architect: "You are a senior backend architect" → "Analyze backend architecture with isolated context"
  - **Prompt examples** (8+ refactored): All agent prompts now specify scope boundaries with explicit context
    - Before: "Security Agent: Check for vulnerabilities"
    - After: "Security Scope: Check for vulnerabilities (context: auth, input validation code)"
  - **Production examples**: Pat Cullen's Multi-Agent Code Review, Fountain case study (line 5335, 16623)
  - **Workflow files**: agent-teams-quick-start.md, agent-teams.md, tdd-with-claude.md, iterative-refinement.md
  - **Terminology replacements**:
    - "Specialized agents" → "Scope-focused agents"
    - "Expert personas" → "Context boundaries"
    - "Multi-domain expertise" → "Multi-scope analysis"
    - "Diversify expertise" → "Diversify analysis angles"
  - **Example agents** (5 files in examples/agents/): All refactored to use functional language instead of role-based personas

### Fixed

- **Methodologies**: Added clarification note to BMAD description about role-based naming (guide/core/methodologies.md line 49)

## [3.23.3] - 2026-02-09

### Added

- **Opus 4.6 Integration**: Comprehensive documentation update for Claude Opus 4.6 features (Feb 2026)
  - **Adaptive Thinking**: Replaced budget-based thinking with dynamic depth calibration
    - Effort parameter: `low|medium|high|max` (API only, default: high)
    - API syntax: `thinking: {"type": "adaptive", "effort": "high"}`
    - CLI: Same Alt+T toggle (no per-request control)
    - Deprecation: `budget_tokens` no longer functional on Opus 4.6
    - Section: Extended Thinking (line 9911), API Breaking Changes (line 10044)
  - **Fast Mode** (`/fast` command, v2.1.36+): 2.5x faster responses, 6x price
    - CLI: `/fast` command (toggle, persists across sessions)
    - API: `speed: "fast"` + beta header `fast-mode-2026-02-01`
    - Pricing: $30/$150 per 1M tokens (vs $5/$25 standard)
    - Added to Commands Table (line 16279), Pricing Model (line 1722)
  - **Pricing Tiers**: Updated pricing table with Opus 4.6 three-tier model
    - Standard: $5/$25 per 1M tokens (200K context)
    - 1M Context Beta: $10/$37.50 per 1M tokens (requests >200K)
    - Fast Mode: $30/$150 per 1M tokens (2.5x speed)
  - **API Breaking Changes**: Documented removed and deprecated features
    - `assistant-prefill` removed (use system prompts instead)
    - `budget_tokens` deprecated (use adaptive thinking)
- **Auto-Memories** (v2.1.32+): Automatic context capture across sessions
  - Opt-in feature, per-project storage
  - Automatically identifies: decisions, preferences, patterns, known issues
  - Separate from CLAUDE.md (personal vs team-level)
  - Comparative table: CLAUDE.md vs auto-memories (line 3999)
  - Section: Memory Files (line 3986)
- **Context Management**: "Summarize from here" feature (v2.1.32+)
  - Right-click message → summarize from that point forward
  - More precise than full `/compact`
  - Added to Context Recovery Strategies (line 1470)
- **Debug Command** (`/debug`, v2.1.30+): Systematic troubleshooting
  - Added to Commands Table (line 16280)
  - Purpose: Error investigation and debugging workflows
- **Agent Teams Enhancements** (v2.1.32+)
  - Hook events: `TeammateIdle` and `TaskCompleted` in events table (line 6972)
  - Agent frontmatter: `memory` field for pre-populated context (line 4849)
  - Enables persistent agent context without repeating project details
- **Xcode Integration** (Feb 2026): Native Claude Agent SDK support
  - Xcode 26.3 RC+ includes built-in Claude assistant
  - Same harness as Claude Code CLI
  - Section: IDE Integration (line 10834)
- **Session Cross-Folder Migration** (Feb 2026): Documentation for resume limitations and workarounds
  - **Architecture explanation**: Why `--resume` is limited to current working directory
  - **Manual migration workflow**: Filesystem operations for moving/forking sessions
  - **Risk documentation**: Secrets, paths, MCP mismatches explicitly warned
  - **Community tool mention**: Jim Weller's claude-migrate-session skill (with 0 adoption caveat)
  - **GitHub issue tracking**: Issue #1516 for native cross-folder support
  - Section: Session Resume Limitations & Cross-Folder Migration (observability.md:117)
  - FAQ entry: "Can I continue a session from a different project folder?" (ultimate-guide.md:~18312)
  - Resource evaluation: docs/resource-evaluations/weller-session-migration-skill.md
  - Reference: machine-readable/reference.yaml (session_resume_limitations, session_migration_*)
  - Clarified: Claude Agent SDK ≠ Claude Code (shared framework, different products)
- **machine-readable/reference.yaml**: 24 new entries
  - Auto-memories, fast mode, debug command, Opus 4.6 features
  - Hook events (TeammateIdle, TaskCompleted)
  - Agent memory field, Xcode integration, adaptive thinking
  - Updated: 2026-02-09
- **llms.txt Standard Documentation** (Section 9.18.4): AI-optimized documentation indexing
  - **Concept explanation**: llms.txt as documentation discovery standard for LLMs
  - **Format and structure**: Plain text index at `/llms.txt` or `/machine-readable/llms.txt`
  - **Complementarity with MCP**: Clarifies llms.txt (static index) vs Context7 MCP (runtime lookup)
  - **Implementation examples**: Minimal and advanced patterns with line numbers
  - **CLAUDE.md integration**: How llms.txt and CLAUDE.md serve different purposes
  - **Repository example**: References this guide's own `machine-readable/llms.txt` implementation
  - Section: Documentation Formats for Agents (line 14544)
  - Resource: docs/resource-evaluations/wasp-fullstack-essentials-eval.md (score 3/5)
  - Source: llmstxt.org specification (official standard)
  - Gap addressed: Repository had llms.txt file without conceptual documentation
- **Background Tasks Workflow** (Section 9.5): Fullstack development patterns with Ctrl+B
  - **When to background**: 5 scenarios (dev server, test watcher, build, migration, docker)
  - **Fullstack workflow pattern**: Dev server backgrounded while iterating on frontend
  - **Real-world example**: API + frontend iteration maintaining tight feedback loops
  - **Context rot prevention**: `/tasks` monitoring strategies
  - **Limitations**: No foreground command, session-scoped tasks, output visibility
  - **Teleportation integration**: Background tasks not transferred, restart required
  - **Disable flag**: `CLAUDE_CODE_DISABLE_BACKGROUND_TASKS` environment variable (v2.1.4+)
  - Section: Background Tasks for Fullstack Development (line 11057)
  - Resource: docs/resource-evaluations/wasp-fullstack-essentials-eval.md (score 3/5)
  - Gap addressed: Ctrl+B documented as feature, now complete workflow strategy
- **Chrome DevTools MCP Server** (mcp-servers-ecosystem.md): Debugging and inspection capabilities
  - **Official Anthropic server**: Chrome DevTools Protocol integration
  - **Use case**: Debugging web apps, runtime inspection, complements Playwright MCP
  - **Key features**: Console access, network monitoring, DOM inspection, JS execution, profiling
  - **Comparison table**: Chrome DevTools (debugging) vs Playwright (testing)
  - **Setup and limitations**: Manual Chrome launch with remote debugging port
  - Section: Browser Automation (line 418)
  - Statistics: 3 browser servers (was 2), 6 official servers (was 5)
  - Resource: docs/resource-evaluations/wasp-fullstack-essentials-eval.md (score 3/5)
  - npm: @modelcontextprotocol/server-chrome-devtools
- **Convention-Over-Configuration for AI** (Section 9.18.1): Framework selection impact
  - **Problem**: Custom architectures require extensive CLAUDE.md documentation
  - **Solution**: Opinionated frameworks reduce agent cognitive load through conventions
  - **Comparison table**: Custom vs opinionated architectures (file organization, routing, testing)
  - **Framework examples**: Next.js, Rails, Phoenix, Django with convention benefits
  - **Real-world impact**: Fewer mistakes, faster boilerplate, smaller CLAUDE.md files
  - **Trade-offs**: Faster onboarding vs architectural flexibility
  - **CLAUDE.md connection**: Convention-over-config directly reduces token requirements
  - Section: Convention-Over-Configuration for AI Agents (line 14380)
  - Resource: docs/resource-evaluations/wasp-fullstack-essentials-eval.md (score 3/5)
  - Gap addressed: Existing AX framework concept reinforced with framework angle

### Changed

- **Pricing Model**: Updated default model from "Sonnet 3.5" to "Sonnet 4.5" (line 1720)
- **Model References**: 8 mentions "Opus 4.5" updated to "Opus 4.6" or context-appropriate version
  - Status line example, Trinity pattern description, TDD workflow, benchmarks
- **Comparative Tools Table**: Corrected PowerPoint capability
  - Before: "No PPTX output capability"
  - After: "Limited PPTX (via Claude in PowerPoint add-in, research preview)"
  - Note: Claude in PowerPoint exists but limited to add-in (line 17251)

### Security

- **CVE Update**: Added Claude Code v2.1.34 security fix to security-hardening.md
  - Critical sandbox bypass vulnerability patched
  - Recommendation: **Upgrade to v2.1.34+ immediately**
  - Details undisclosed pending broader adoption
  - Added to CVE Summary table (guide/security/security-hardening.md)

### Documentation

- **Fact-Checking**: All Opus 4.6 details verified via Perplexity Pro
  - Pricing confirmed: $5/$25 (standard), $10/$37.50 (1M), $30/$150 (fast)
  - Adaptive thinking syntax validated: effort parameter, API examples
  - Fast mode behavior confirmed: 2.5x speed, 6x cost, persistent toggle
  - Auto-memories verified: opt-in, per-project, cross-session recall
  - Sources: Anthropic official docs, pricepertoken.com, eesel.ai, help.apiyi.com

- **Templates**: Session handoff template based on Robin Lorenz's context engineering approach
  - Structured handoff at 85% context to prevent auto-compact degradation
  - Research-backed rationale (LLM performance drop 50-70% at high context)
  - Complete workflow: metadata, completed work, pending tasks, blockers, next steps, essential context
  - File: `examples/templates/session-handoff-lorenz.md`

### Changed

- **Architecture**: Auto-compaction confidence upgraded 50% → 75% (Tier 3 → Tier 2)
  - Added platform-specific thresholds: VS Code (~75% usage), CLI (1-5% remaining)
  - Added performance impact research section with 6+ sources
  - Performance benchmarks: 50-70% accuracy drop on complex tasks (1K → 32K tokens)
  - Research sources: Context Rot (Chroma), Beyond Prompts (UseAI), Claude Saves Tokens (Golev)
  - Added Lorenz's proactive thresholds: 70% warning, 85% handoff, 95% force handoff
  - File: `guide/core/architecture.md` Section 3.2
- **Context Management**: Added research-backed proactive thresholds
  - Replaced generic "Check context before resuming (>75%)" with specific 70%/85%/95% ladder
  - Added performance degradation warnings with research links
  - Clarified auto-compact triggers: ~75% (VS Code), ~95% (CLI) with quality impact
  - File: `guide/ultimate-guide.md` (lines ~734, ~3582)

### Documentation

- **Resource Evaluation**: Lorenz session handoffs post (score 4/5)
  - Initial score 2/5 → upgraded to 4/5 after Perplexity validation
  - 3 research queries validated core claims (auto-compact degradation, LLM performance, handoff best practices)
  - Technical-writer challenge identified 4 critical gaps in initial assessment
  - Integration: architecture.md + ultimate-guide.md + template created
  - File: `docs/resource-evaluations/lorenz-session-handoffs-2026.md`
- **Ecosystem**: Added awesome-claude-skills (BehiSecc) to curated lists
  - 62 skills taxonomy across 12 categories (Development, Design, Documentation, Testing, DevOps, Security, Data, AI/ML, Productivity, Content, Integration, Fun)
  - Positioned as complementary to awesome-claude-code (skills-only focus vs full ecosystem)
  - Distinct from ComposioHQ/awesome-claude-skills (different maintainer, taxonomy approach)
  - Referenced in guide section 8.5 (line 9721), Further Reading (line 17520), README.md, reference.yaml
  - Evaluation: `docs/resource-evaluations/awesome-claude-skills-github.md` (score 3/5)

## [3.23.2] - 2026-02-08

### Documentation

- **Claude Code Releases**: Updated tracking v2.1.33 → v2.1.37
  - v2.1.37: Fixed /fast availability after /extra-usage
  - v2.1.36: Fast mode now available for Opus 4.6
  - v2.1.34: Security fix for sandbox-excluded commands bypass + agent teams crash fix

### Added

- **Workflows**: Agent Teams Quick Start Guide (`guide/workflows/agent-teams-quick-start.md`)
  - Practical 8-10 min guide vs 30 min full documentation
  - 5-minute setup walkthrough (prerequisites → first test)
  - 4 copy-paste patterns for real projects (Guide pre-release review, landing sync, multi-file doc updates, RTK security PR review)
  - Decision matrix with 10+ scenarios (when YES, when NO, when MAYBE)
  - Success metrics framework (convergence rate, unique insights, false positive rate, time saving, bug catch rate)
  - Minimal workflow template (bash + prompt examples)
  - Red flags section (when NOT to use agent teams to avoid waste)

- **Slash Commands**: `/audit-agents-skills` command for quality auditing of agents, skills, and commands
  - 16-criteria framework (Identity 3x, Prompt 2x, Validation 1x, Design 2x)
  - Weighted scoring: 32 points max for agents/skills, 20 points for commands
  - Production readiness grading (A-F scale, 80% threshold for production)
  - Fix mode with actionable suggestions for failing criteria
  - Project-level command (`.claude/commands/`) + distributable template (`examples/commands/`)
- **Skills**: `audit-agents-skills` advanced skill with 3 audit modes
  - Quick Audit: Top-5 critical criteria (fast pass/fail)
  - Full Audit: All 16 criteria per file with detailed scores
  - Comparative: Full + benchmark analysis vs reference templates
  - JSON + Markdown dual output for CI/CD integration
  - Externalized scoring grids in `scoring/criteria.yaml` for programmatic reuse
- **Templates**: Added 3 audit infrastructure files
  - Command template: `examples/commands/audit-agents-skills.md` (~350 lines)
  - Skill template: `examples/skills/audit-agents-skills/SKILL.md` (~400 lines)
  - Scoring grids: `examples/skills/audit-agents-skills/scoring/criteria.yaml` (~120 lines, 16 criteria × 3 types)

### Documentation

- **Resource Evaluations**: Added Gur Sannikov "Claude Code as Embedded OS" evaluation (4/5 - High Value)
  - Score: 4/5 (ADR workflow gap + native capabilities checklist + community validation)
  - Decision: Integrate 4 sections across 3 guide files
  - Gap addressed: ADR-driven development pattern, capabilities onboarding checklist, dynamic model switching
  - Integration: ADR workflow (methodologies.md), Native Capabilities Audit (architecture.md), Dynamic Model Switching (cheatsheet.md), Community Validation (architecture.md)
  - Community validation: Cursor power user adopting Agent Skills standard (validates "less scaffolding, more model" philosophy)
  - Source: [LinkedIn post](https://www.linkedin.com/posts/gursannikov_claudecode-embeddedengineering-aiagents-activity-7423851983331328001-DrFb) (2026-02-01)
- **Resource Evaluations Index**: Updated count from 24 to 55 evaluations
- **Slash Commands**: Added comprehensive documentation for `/insights` command (Section 6.1) with architecture deep dive
  - **Architecture Overview** subsection (7-stage pipeline: session filtering, transcript summarization, facet extraction, aggregated analysis, executive summary, report generation, facet caching)
  - **Facets Classification System**: 6 dimensions documented (13 goal types, 12 friction categories, 6 satisfaction levels, 4 outcome states, 7 success categories, 5 session types)
  - **Performance optimization**: Caching system explanation (facets/<session-id>.json for incremental analysis)
  - **Interpretation guidance**: How facets categories help understand report recommendations
  - **Source attribution**: Zolkos Technical Deep Dive (2026-02-04) as architecture reference
- **Agent/Skill Quality**: Added 2 strategic references in ultimate-guide.md
  - After Agent Validation Checklist (line 4951): Automated audit call-out with methodology reference
  - After Skill Validation (line 5495): Beyond spec validation note explaining quality scoring extension
- **Resource Evaluations**: Added Mathieu Grenier agent/skill quality evaluation (3/5 - Moderate Value)
  - Score: 3/5 (real-world observations, identifies automation gap, aligns with LangChain 2026 data)
  - Decision: Integrate selectively via audit tooling creation
  - Gap addressed: Guide had conceptual best practices but no automated enforcement
  - Industry context: 29.5% deploy agents without evaluation (LangChain Agent Report 2026)
  - Integration: Created `/audit-agents-skills` command + skill + criteria YAML
- **Resource Evaluations**: Added Zolkos /insights deep dive evaluation (4/5 - High Value)
  - Score: 4/5 (comprehensive technical architecture, fills guide gap, complementary with usage documentation)
  - Decision: Integrate architecture + facets classification system
  - Integration: Architecture overview added to Section 6.1 (~800 tokens)
  - Complementarity: Zolkos (internal architecture) + Guide (external usage) = complete documentation
- **Resource Evaluations Index**: Updated count from 23 to 24 evaluations (added Grenier entry)

## [3.23.1] - 2026-02-06

### Documentation

- **Claude Code Releases**: Updated tracking to v2.1.33 (2026-02-06)
  - Agent teams fixes (tmux sessions, availability warnings)
  - `TeammateIdle` and `TaskCompleted` hook events for multi-agent workflows
  - Agent frontmatter: `memory` field (user/project/local scope), `Task(agent_type)` sub-agent restriction
  - Plugin name in skill descriptions and `/skills` menu
  - VSCode: Remote sessions, branch/message count in session picker
  - Multiple stability fixes and improved error messages

## [3.23.0] - 2026-02-06

### Changed

- **Adaptive Onboarding Architecture v2.0.0** — Major redesign of interactive onboarding system addressing 8 critical gaps identified by technical-writer challenge (~2,100 lines modified, 2 validation scripts, metrics plan)
  - **Adaptive topic selection**: Each profile now has **core topics** (always shown) + **adaptive topics** (context-based via keyword triggers). Claude analyzes user messages (e.g., "I work in a team and use git") to surface relevant v3.21-3.22 content (config_hierarchy, git_mcp_guide, mcp_secrets_management, dual_instance_planning, sandbox_native_guide) based on relevance, not chronology
  - **Security-first fix**: Moved `sandbox_native_guide` from `beginner_30min` → `beginner_5min` (CRITICAL fix). New users now learn sandboxing security **BEFORE** running commands, addressing technical-writer's "security gap HIGH RISK" finding
  - **Time budget validation**: All 18 profiles validated (6-8 min/topic average), respects `topics_max` limits. Prevents overwhelming users (e.g., power_30min: 4 topics max, not 6). Addresses "time budget impossible" challenge finding
  - **New learn_security goal**: Dedicated security-focused learning path with 2 profiles (intermediate_30min, power_60min) covering sandbox_native, mcp_secrets, security_hardening, production_safety, sandbox_isolation_guide. Fills gap for security-conscious users
  - **V3.21-3.22 comprehensive coverage**: All CRITICAL (5/5) and HIGH VALUE (4/5) topics now discoverable via adaptive triggers: git_mcp_guide (v3.22.0), config_hierarchy (v3.21.0), mcp_secrets_management (v3.21.0), dual_instance_planning (v3.22.0), sandbox_native_guide (v3.21.1)
  - **Quiz integration as exit activity**: Phase 4 wrap-up now recommends quiz by profile level (beginner: 60 questions ~15 min, intermediate: 100 questions ~25 min, advanced: 97 questions ~30 min). Addresses "quiz = testing mechanism, not learning content" challenge finding. 13 new deep_dive entries for quiz system
  - **Fallback minimal by design**: Kept graceful degradation pattern (3-5 topics if fetch fails), rejected proposal to enrich fallback per technical-writer recommendation. Improved fetch reliability strategy over content expansion
  - **Portability warnings added**: Documents AskUserQuestion Claude Code-specific limitation, localization status (English only for v3.21-3.22 topics, on-the-fly translation for FR/ES with accuracy warnings), simplification steps for ChatGPT/Gemini compatibility
  - **Maintenance automation**: 2 validation scripts created
    - `validate-onboarding.sh` (6 checks): YAML syntax, deep_dive key existence, time budget compliance, topics_max constraints, question_flow completeness, version alignment with VERSION file
    - `detect-new-onboarding-topics.sh`: Scans resource evaluations for CRITICAL/HIGH VALUE topics not in any profile, run monthly to prevent future drift
  - **Version metadata system**: `onboarding_matrix_meta` section added with version tracking (v2.0.0), changelog, maintenance guidelines (review trigger: every CRITICAL/HIGH feature), automation pointer (detect-new-topics script), responsible party (quarterly reviews)
  - **Files modified**: `reference.yaml` (+150 lines: onboarding_matrix_meta, adaptive matrix, learn_security goal, quiz deep_dive entries), `onboarding-prompt.md` (+80 lines: adaptive logic Phase 1/2, learn_security in Phase 1.5, quiz recommendations Phase 4, portability warnings), `scripts/validate-onboarding.sh` (350 lines), `scripts/detect-new-onboarding-topics.sh` (200 lines), `claudedocs/adaptive-onboarding-design.md` (1,100 lines design doc with 12 sections + 2 appendices)
  - **Impact**: Adoption improvement (30% of users use onboarding → 30% now discover v3.21-3.22 features), Security enhancement (beginners learn sandbox FIRST, not eventually), Support reduction (users following updated paths avoid "Why wasn't I told about X?" issues), Maintenance automation (gap detection prevents future drift), Portability transparency (users know AskUserQuestion limitation, localization accuracy warnings)
  - **Challenge validation**: Technical-writer agent challenged initial analysis, identified 8 missing angles (severity underestimation, sandbox placement wrong, quiz integration superficial, time budget violations, fallback design misunderstanding, user flow continuity gaps, maintenance burden unquantified, metrics plan missing). All 8 addressed in v2.0.0 design
  - **Effort**: 95 min actual (85 min estimated, +10 min for comprehensive testing/localization check)
  - **Credits**: Technical-writer agent (challenge phase identifying 8 critical gaps, adaptive architecture recommendation, time budget validation requirement, quiz UX correction, fallback graceful degradation insight), user request for onboarding sync verification

## [3.22.1] - 2026-02-05

### Documentation

- **Claude Code Releases**: Updated tracking to v2.1.32 (2026-02-05)
  - ⭐ **Opus 4.6 is now available**
  - ⭐ **Agent teams research preview** — Multi-agent collaboration for complex tasks (experimental, token-intensive)
  - ⭐ **Automatic memory recording and recall** — Claude now automatically records and recalls memories as it works
  - **"Summarize from here"** — Message selector allows partial conversation summarization
  - Skills from `.claude/skills/` in `--add-dir` directories now auto-load
  - Multiple fixes: `@` file completion paths, bash heredoc JS template literals, Thai/Lao vowel rendering
  - [VSCode] Fixed slash commands executing incorrectly, added conversation loading spinner

## [3.22.0] - 2026-02-04

### Documentation

- **Claude Code Releases**: Updated tracking to v2.1.31 (2026-02-04)
  - v2.1.31 (2026-02-03): Session resume hint, PDF/bash/LSP fixes, system improvements
  - v2.1.30 (2026-02-02): PDF page range support (`pages` parameter), pre-configured OAuth for MCP (Slack), `/debug` command, git log/show flags, task tool metrics
  - Notable features: PDF pages parameter for large documents (>10 pages), built-in OAuth for servers without Dynamic Client Registration, new troubleshooting command, reduced motion accessibility mode

### Added

- **Dual-Instance Planning Pattern (Jon Williams)** — Vertical separation workflow (planner/implementer) as complement to horizontal scaling (Boris pattern), addressing solo dev and budget-conscious audience gap (~1,100 lines, scored 4/5 High Value after technical-writer challenge)
  - **New section: Alternative Pattern: Dual-Instance Planning** (`guide/ultimate-guide.md:12884-13230`, ~350 lines) — Comprehensive documentation covering when to use dual-instance pattern (solo devs, spec-heavy work, $100-200/month vs $500-1K Boris pattern), setup instructions (2 Claude instances with distinct roles: Claude Zero planner/reviewer never touches code, Claude One implementer executes approved plans), complete 5-phase workflow (planning with interview-based requirements clarification → human review checkpoint → implementation → verification by planner → archive), Plans/ directory structure (Review/Active/Completed as Kanban-style workflow), comparison table Boris horizontal scaling vs Jon vertical separation (8 dimensions: scaling axis, primary goal, monthly cost, entry barrier, audience, context pollution, accountability, tooling, coordination, best for), cost analysis (2 instances sequential vs 1 instance with correction loops, breakeven at ≥2 corrections), agent-ready plan best practices (file paths + line numbers reduce implementation time), limitations and tips (when not to use, overhead management), see also links
  - **New workflow file: dual-instance-planning.md** (`guide/workflows/dual-instance-planning.md`, ~750 lines) — Complete workflow guide with TL;DR, when-to-use checklist, detailed setup (directory structure, role enforcement in first messages), 5-phase workflow with concrete JWT authentication example (~500 lines showing plan structure, human approval, implementation, verification, archival), ready-to-use plan template (Summary, Requirements Clarified, Files to Create with line numbers, Files to Modify with before/after, Implementation Steps, Success Criteria, Security Checklist, Risks & Mitigation, Questions for Implementer, Estimated Effort Breakdown), cost analysis breakdown (simple/medium/complex features, monthly budget estimates for light/moderate/heavy users, breakeven calculations), tips and troubleshooting (role enforcement via CLAUDE.md, context pollution prevention, plan drift solutions, bash aliases for directory movement automation)
  - **Resource evaluation** (`docs/resource-evaluations/jon-williams-dual-instance-pattern.md`, ~300 lines) — Scored 4/5 (High Value, initially 2-3/5 corrected after technical-writer challenge), fact-check 100% (10 claims verified: author role/date, transition context, model used, workflow steps, directory structure, all verified via primary LinkedIn source), challenge results documented (score underestimation due to LinkedIn origin bias, gap identification for vertical vs horizontal scaling, audience gap for $100-200/month budget, pattern recognition of two-phase commit engineering principle, cost analysis gap filled), risk assessment if not integrated (80% probability audience gap, 90% probability pattern missing, quantified impact), lessons learned (don't undervalue practitioner sources, pattern orthogonality matters, challenge agents catch bias)
  - **Machine-readable index** (`reference.yaml`, +15 entries) — Added: dual_instance_planning (12884), dual_instance_workflow, dual_instance_overview, dual_instance_setup, dual_instance_complete_workflow, dual_instance_plan_template, dual_instance_cost_analysis, dual_instance_comparison (13074 Boris vs Jon table), dual_instance_source (LinkedIn URL), dual_instance_author (Jon Williams Product Designer UK), dual_instance_date (2026-02-03), dual_instance_pattern (vertical separation description), dual_instance_cost ($100-200/month), dual_instance_audience (solo devs spec-heavy quality over speed); Updated: resource_evaluations_count (46→47)
  - **References updated**: `guide/workflows/plan-driven.md` See Also section (+1 link to dual-instance-planning.md with description "Advanced: Use two Claude instances planner + implementer for quality-focused workflows"), `README.md` evaluation count harmonized (46/45/44 inconsistencies → 47 across 4 locations)
  - **Gap filled**: Vertical separation (planner ↔ implementer) pattern — 0% documented, only Boris horizontal scaling (5-15 parallel instances) → 100% comprehensive with workflow/template/cost analysis; Solo dev budget ($100-200/month) — underserved by $500-1K Boris pattern → complete alternative with lower entry barrier; Agent-ready plan structure — implicit in /plan mode → explicit best practice teaching (file paths, line numbers, acceptance criteria); Human-in-the-loop persistent planning approval — single /plan approval → persistent review checkpoint workflow (Review/Active/Completed directories); Cost analysis 2 instances vs correction loops — not documented → breakeven calculations, monthly budget estimates, decision criteria
  - **Impact**: Audience expansion (solo devs, product designers, spec-heavy workflows now served), Cost accessibility (lower barrier $100-200 vs $500-1K enables adoption), Quality improvement (separation of concerns reduces implementation errors via two-phase commit pattern), Pattern complementarity (vertical + horizontal scaling strategies documented, not competing choices), Practical tooling (bash aliases, directory structure, plan template ready to use)
  - **Source**: [Jon Williams LinkedIn post](https://www.linkedin.com/posts/thatjonwilliams_ive-been-using-cursor-for-six-months-now-activity-7424481861802033153-k8bu) (Product Designer UK, Feb 3 2026, transition from Cursor 6 months to Claude Code with Opus 4.5)
  - **Credits**: Jon Williams (pattern practitioner), technical-writer agent (challenge phase: 2-3/5 → 4/5 score revision, identified undervaluation due to source bias, gap analysis for vertical separation, audience gap quantification, engineering pattern recognition two-phase commit), fact-check validation (100% verified via primary source)


- **Git MCP Server (Official) Documentation** — Integration of Anthropic's official Git MCP server addressing version control automation gap (~1600 words, scored 5/5 CRITICAL after technical-writer challenge)
  - **New section: Version Control (Official Servers)** (`guide/ecosystem/mcp-servers-ecosystem.md:102-255`) — Comprehensive documentation covering official Git MCP server (12 tools: git_status, git_log, git_diff, git_commit, git_add, git_reset, git_branch, git_create_branch, git_checkout, git_show, git_diff_unstaged, git_diff_staged), 3 installation methods (uvx one-liner, pip, Docker), multi-repo configuration, advanced log filtering (ISO 8601, relative dates "2 weeks ago", absolute dates), context_lines parameter for token efficiency, IDE integrations (Claude Desktop, VS Code, Zed, Zencoder with one-click install buttons), quality score 8.5/10, limitations & workarounds (early development API changes, no interactive rebase/reflog/bisect)
  - **Decision Matrix: Git MCP vs GitHub MCP vs Bash Tool** (`guide/ecosystem/mcp-servers-ecosystem.md:212-255`) — Comprehensive comparison table (11 operations: local commits, branch management, diff/log analysis, PR creation, issue management, CI/CD checks, interactive rebase, reflog recovery, git bisect, multi-tool pipelines), decision tree workflow, 7 workflow examples with justifications (feature development, commit history analysis, code review preparation, cleanup commits, recover lost commits, bug hunting, automated release flow)
  - **Machine-readable index** (`reference.yaml`, +11 entries) — Added: git_mcp (description), git_mcp_guide (line pointer), git_mcp_tools (12 tools list), git_mcp_install (uvx command), git_mcp_decision_matrix (line pointer), git_mcp_repo (GitHub URL), git_mcp_score (8.5/10), git_mcp_status (early development), git_mcp_advanced_filtering (date formats), git_mcp_use_cases (5 use cases); Updated: reference.yaml updated timestamp (2026-02-03)
  - **Gap filled**: Official Git server documentation — mentioned in official servers table (line 29) but 0% documented → 100% comprehensive with use cases/config/decision matrix; Git vs GitHub vs Bash tool clarity — confusion not addressed → decision tree + comparison table + 7 workflow examples; Multi-repo workflows — not documented → configuration example with multiple instances; Token efficiency strategies — general advice → specific git_diff context_lines parameter, structured output benefits quantified
  - **Impact**: Workflow automation (AI-assisted commits, branch creation, log analysis without Bash tool), Token efficiency (structured output, context_lines control vs parsing text), Cross-platform safety (MCP vs direct Bash Git commands), Multi-tool composition (Git MCP + GitHub MCP pipelines documented), Developer experience (decision tree prevents tool selection confusion)
  - **Source**: [Official Git MCP Server](https://github.com/modelcontextprotocol/servers/tree/main/src/git) (MIT License, 77,908+ stars parent repo), Anthropic MCP ecosystem
  - **Credits**: Anthropic (official server), technical-writer agent (challenge phase: 3/5 → 5/5 score revision, placement critique, decision matrix requirement), fact-check validation (100% verified: 12 tools, installation methods, date filtering, IDE integrations, early development status, MIT license)

### Fixed

- **Ctrl+R Keybinding Documentation** — Corrected incorrect "Retry" label to accurate "Search command history" in 5 locations
  - **Guide corrections** (`guide/cheatsheet.md:39`, `guide/ultimate-guide.md:358,15508,15521,16032`) — Updated from "Retry last operation"/"Retry last"/"Retry" to "Search command history"/"Search history"/"Search" reflecting official `history:search` action (Global context) and `historySearch:next` (HistorySearch context)
  - **Verification method** — Tested against official keybindings documentation (`~/.claude/keybindings.json` schema) and CLI behavior confirmation
  - **Resource evaluation** (`docs/resource-evaluations/sankalp-claude-code-experience.md`) — Sankalp's blog (Dec 27, 2025) correctly identified guide error, scored 2/5 (marginal overlap but accurate Ctrl+R identification), evaluation documents correction workflow + CLI test results
  - **Impact** — Users now have accurate keybinding documentation matching actual behavior (search command history similar to shell Ctrl+R reverse-i-search)
  - **Credits** — Sankalp (@dejavucoder) for identifying error in [blog post](https://sankalp.bearblog.dev/my-experience-with-claude-code-20-and-how-to-get-better-at-using-coding-agents/), verification via official keybindings schema

## [3.21.1] - 2026-02-02

### Added

- **Native Sandboxing Comprehensive Documentation** — Integration of official Anthropic sandboxing documentation (v2.1.0+) addressing critical security gap (~1800 words missing content, scored 5/5 CRITICAL)
  - **New guide: sandbox-native.md** (`guide/security/sandbox-native.md`, ~3000 lines) — Complete technical reference covering OS primitives (Seatbelt for macOS, bubblewrap for Linux/WSL2), filesystem isolation (read all/write CWD), network isolation (SOCKS5 proxy with domain filtering), sandbox modes (Auto-allow vs Regular permissions), escape hatch (`dangerouslyDisableSandbox`), security limitations (domain fronting, Unix sockets privilege escalation, filesystem permission escalation), open-source runtime (`@anthropic-ai/sandbox-runtime`), platform support (macOS ✅, Linux ✅, WSL2 ✅, WSL1 ❌, Windows planned), decision tree (Native vs Docker vs Cloud), configuration examples (Strict/Balanced/Development), best practices, troubleshooting
  - **Enhanced: sandbox-isolation.md** (`guide/security/sandbox-isolation.md`, +800 lines) — Added Section 4 "Native Claude Code Sandbox" with architecture diagram, OS primitives comparison, quick start guide, configuration example, Native vs Docker decision tree, security limitations summary, deep dive reference; Updated TL;DR table (Native CC repositioned #2 with enriched details); Updated Comparison Matrix (Native CC enriched with kernel isolation, overhead, setup details); Sections renumbered (4→5 Cloud Sandboxes, 5→6 Comparison Matrix, 6→7 Safe Autonomy, 7→8 Anti-Patterns)
  - **Enhanced: architecture.md** (`guide/core/architecture.md:523`, +80 lines) — Added Section 5.1 "Native Sandbox (v2.1.0+)" in Permission & Security Model with architecture diagram (sandbox wrapper flow), OS primitives table, isolation model (filesystem/network/process), sandbox modes, security trade-offs table (Native vs Docker), security limitations, when-to-use guide, deep dive reference
  - **Resource evaluation** (`docs/resource-evaluations/native-sandbox-official-docs.md`, ~600 lines) — Scored 5/5 (CRITICAL), official Anthropic documentation, gap analysis quantified (~1800 words missing), fact-check 100% (11 claims verified), technical-writer agent challenge (3/5 → 5/5 score revision), risks of non-integration documented (security incidents, adoption friction, configuration errors)
  - **Production templates** (3 files):
    - `examples/config/sandbox-native.json` — Native sandbox configuration (denylist mode, domain allowlist, denied credentials paths, excluded commands)
    - `examples/commands/sandbox-status.md` — `/sandbox-status` command for sandbox inspection (platform check, config display, recent violations, open-source runtime)
    - `examples/hooks/bash/sandbox-validation.sh` — PreToolUse hook for production sandbox validation (strict mode, platform-specific checks, exit 2 blocking)
  - **Machine-readable index** (`reference.yaml`, +24 entries) — Added: sandbox_native_guide, sandbox_native_why, sandbox_native_os_primitives, sandbox_native_filesystem, sandbox_native_network, sandbox_native_modes, sandbox_native_escape_hatch, sandbox_native_security_limits, sandbox_native_opensource, sandbox_native_platforms, sandbox_native_decision_tree, sandbox_native_config_examples, sandbox_native_best_practices, sandbox_native_troubleshooting, sandbox_runtime_oss, sandbox_runtime_npm, sandbox_official_docs, sandbox_comparison_native_docker, sandbox_native_evaluation, sandbox_native_score, sandbox_native_config_template, sandbox_status_command, sandbox_validation_hook; Updated: sandbox_safe_autonomy (320→486), sandbox_anti_patterns (372→538), sandbox_comparison_matrix (306→469)
  - **Gap filled**: Native sandbox technical details (OS primitives, network proxy, security limitations) — 0% documented → 100% comprehensive; Trade-off Docker microVM vs Native process-level — not quantified → detailed comparison matrix; Open-source runtime — 0% mentioned → complete walkthrough with GitHub/npm links; Platform incompatibility (WSL1, Windows) — not documented → explicit status + migration guidance
  - **Impact**: Security (domain fronting/Unix sockets/filesystem attacks documented with mitigations), Production readiness (templates enable safe autonomous workflows), Developer experience (decision tree helps choose Native vs Docker vs Cloud), Community (open-source runtime enables audits/contributions)
  - **Source**: [Official Anthropic Documentation](https://code.claude.com/docs/en/sandboxing), [Open-source runtime](https://github.com/anthropic-experimental/sandbox-runtime), Claude Code v2.1.0+ feature
  - **Credits**: Anthropic (official documentation), technical-writer agent (challenge phase identified under-scoring), fact-check validation (100% verified claims)

## [3.21.0] - 2026-02-02

### Added

- **Configuration Management & Backup** — Two major new sections addressing critical gap in Claude Code configuration strategy (1,591 lines added, 3 templates, 22 reference entries)
  - **Section 3.2.1 "Version Control & Backup"** (`guide/ultimate-guide.md:4085`) — 611 lines covering configuration hierarchy (global → project → local), Git strategies for both project `.claude/` and global `~/.claude/`, backup strategies comparison (Git remote, cloud sync, cron, third-party tools), multi-machine sync workflows (Git, cloud storage, hybrid), security considerations, disaster recovery procedures, community solutions (brianlovin/claude-config + Martin Ratinaud approach)
  - **Documented `.claude/settings.local.json`** — Previously undocumented feature for machine-specific overrides (gitignored) now explained with hierarchy precedence rules and use cases
  - **Section 8.3.1 "MCP Secrets Management"** (`guide/ultimate-guide.md:8113`) — 293 lines covering security principles, three practical approaches (OS Keychain with encryption at rest, .env + .gitignore with template substitution, Secret Vaults for enterprise), secrets rotation workflow, pre-commit detection hook, verification checklist, best practices summary
  - **Template: sync-claude-config.sh** (`examples/scripts/sync-claude-config.sh`) — 350-line automation script with 5 commands (setup, sync, backup, restore, validate), .env parsing + envsubst for variable substitution, Git repo creation with symlinks, validation checks (secrets not in Git, file permissions), optional cloud backup support
  - **Template: pre-commit-secrets.sh** (`examples/hooks/bash/pre-commit-secrets.sh`) — 163-line Git hook detecting 10+ secret patterns (OpenAI, GitHub, AWS, Anthropic, JWT, etc.), whitelist system for false positives, skip files (*.md, *example*, *template*), clear error messages with remediation steps, blocks commits if secrets detected
  - **Template: settings.local.json.example** (`examples/config/settings.local.json.example`) — 145-line template for machine-specific overrides with examples (skip expensive checks on laptop, local MCP endpoints, personal permissions, machine-specific hooks)
  - **Resource Evaluation: Martin Ratinaud Configuration Management** (`docs/resource-evaluations/ratinaud-config-management-evaluation.md`) — Scored 5/5 (CRITICAL), 294-line evaluation with content summary, comparative analysis, 3× Perplexity fact-checks, technical-writer agent challenge, integration plan. Source: [LinkedIn post](https://www.linkedin.com/posts/martinratinaud_claudecode-devtools-buildinpublic-activity-7424055660247629824-hBsL) by Martin Ratinaud (11 years experience, "Claude Code Max Addict", 504 sessions validation)
  - **Community Validation**: GitHub Issue [#16204](https://github.com/anthropics/claude-code/issues/16204) "Proactive migration guidance for backup/restore workflows", brianlovin/claude-config repo with sync.sh script, claudebot backup tool (third-party)
  - **Machine-readable index**: 22 new entries in `reference.yaml` (config_hierarchy, config_git_strategy_project, config_git_strategy_global, config_backup_strategies, config_multi_machine_sync, config_security_considerations, config_disaster_recovery, config_community_solutions, config_github_issue, config_brianlovin_repo, config_ratinaud_approach, config_ratinaud_evaluation, mcp_secrets_management, mcp_secrets_principles, mcp_secrets_os_keychain, mcp_secrets_env_file, mcp_secrets_vaults, mcp_secrets_rotation, mcp_secrets_pre_commit, mcp_secrets_verification, mcp_secrets_best_practices, sync_claude_config_script, pre_commit_secrets_hook, settings_local_example)
  - **Gap filled**: Version control strategy for `~/.claude/` (previously undocumented), MCP secrets storage workflows (theory → practice), multi-machine sync (project-level documented, global-level missing), disaster recovery procedures (0 → complete coverage), team onboarding for `~/.claude/` setup
  - **Impact**: Security (pre-commit hook prevents secret leaks), Productivity (multi-machine sync saves 80% reconfiguration time), Team coordination (onboarding workflow for consistent setup), Disaster recovery (backup strategies protect against config loss)
  - **Credits**: Martin Ratinaud (504 sessions, symlinks approach), brianlovin/claude-config (community sync.sh example), GitHub community (Issue #16204 request), Perplexity (3× fact-check searches validating gap and community demand)
- **Resource Evaluation: Alan Engineering "Tour Eiffel Paradigm"** (scored 5/5, CRITICAL) — Integration of paradigm shift framework from Alan Engineering team (Charles Gorintin, CTO + Maxime Le Bras, Talent Lead) validating production-scale AI transformation (`docs/resource-evaluations/alan-tour-eiffel-paradigm.md`)
  - **Source**: LinkedIn Newsletter "Intelligence Humaine" (Feb 2, 2026, 3,897 followers), French healthtech company (15K+ companies, 300K+ members, €500M raised, heavily regulated industry)
  - **Key frameworks**: (1) Eiffel Tower Principle — AI tools transform what's architecturally possible (like elevators enabled Eiffel Tower shape), not just acceleration, (2) Ralph Wiggum Programming — agentic loops where engineers become architects/editors, (3) **Verification Paradox** — 99% AI success makes human vigilance fragile for 1% errors, need automated guardrails, (4) Precision as Currency — clear spec definition (WHAT/WHERE/HOW) is new engineer superpower, (5) Ambition Scaling — pursue previously impossible goals enabled by tools
  - **Production Safety Rule 7** added (`guide/security/production-safety.md:639-791`): "The Verification Paradox" — when AI reliability crosses 95%, shift from manual review to automated guardrails (tests, types, lints, CI/CD gates). Anti-patterns vs Better Approaches table, 3 implementation options (automated stack, verification contracts, pre-merge checklist), integration with Rules 2/3/6
  - **Practitioner Insight** added (`guide/ecosystem/ai-ecosystem.md:2133-2168`): Alan Engineering section after Addy Osmani, following existing format (credentials, content summary, alignment table with guide references, production-scale context). Interview mention of Stanislas Polu (Dust co-founder) citing Mirakl achievement (75% employees → agent builders)
  - **Machine-readable index** updated (`reference.yaml`): Added `practitioner_alan`, `practitioner_alan_source`, `verification_paradox`, `verification_paradox_source` entries
  - **README.md counters harmonized**: Fixed evaluation count inconsistencies (37/35/38 → 41 across 5 locations: line 18 intro, line 74 mermaid diagram, line 118 structure, line 163 features, line 427 details)
  - **Challenge phase**: Technical-writer agent reviewed 6 proposed integrations, rejected 4 (Quick Start paradigm shift, Mental Model refactoring, methodologies.md deep dive, XML Prompting precision) for dilution/duplication concerns, approved 3 (production-safety, ai-ecosystem, reference.yaml)
  - **Language note**: Original article in French, concepts and Henri Bergson quote ("L'intelligence est la faculté de fabriquer des outils à faire des outils") translated for guide
- **Multi-IDE Configuration Sync Pattern** — Documented strategies for maintaining consistent AI instructions across multiple coding tools (Claude Code, Cursor, Copilot) in `guide/ecosystem/ai-ecosystem.md:1256-1329`
  - **Problem statement**: Table comparing config files (CLAUDE.md, .cursorrules, AGENTS.md, .github/copilot-instructions.md) — without sync, each drifts independently causing inconsistent AI behavior
  - **Solution 1**: Native @import (recommended for Claude Code solo usage) — no build step, maintained by Anthropic, but Cursor doesn't support it
  - **Solution 2**: Script-based generation for multi-IDE teams — source of truth in `docs/ai-instructions/` compiled into tool-specific configs via bash/node sync scripts
  - **AGENTS.md Support Status**: Clarified Claude Code does NOT natively support AGENTS.md ([GitHub issue #6235](https://github.com/anthropics/claude-code/issues/6235), 171 comments, open as of Feb 2026) — workaround via symlink documented
  - **Compatibility matrix**: AGENTS.md standard supported by Cursor, Windsurf, Cline, GitHub Copilot (see [AI Coding Agents Matrix](https://coding-agents-matrix.dev))
  - **Machine-readable index**: Added `ai_ecosystem_multi_ide_sync` and `agents_md_support_status` entries to `reference.yaml`
- **Resource Evaluation: Addy Osmani LinkedIn Post** (scored 2/5, Marginal - Tracking mention only) — Post about Anthropic study (17% comprehension gap) evaluated but not integrated due to 100% overlap with primary source already documented (`docs/resource-evaluations/addy-osmani-linkedin-anthropic-study.md`)
  - **Content**: LinkedIn post (Feb 1, 2026, 246K reach) citing Shen & Tamkin 2026 study on AI-assisted learning
  - **Key claims verified**: 17% comprehension gap, 2-minute productivity gain, "thinking partner vs code vending machine" framing
  - **Overlap**: 100% with arXiv:2601.20245 already cited 3× in `guide/roles/learning-with-ai.md` (lines 114, 868, 890)
  - **Decision**: Minimal integration (1-2 line tracking mention) to document mainstream diffusion timeline without content duplication
  - **Challenge phase**: Technical-writer agent confirmed score 2/5 content but noted 3/5 ecosystem context (authority messager + diffusion milestone)
  - **New criterion documented**: "Influencer Amplification" pattern for future evaluations (reach >100K + timeline awareness)
- **Resource Evaluation: "Beyond Vibe Coding" Book** (scored 3/5, Pertinent - Minimal integration) — Comprehensive O'Reilly book by Addy Osmani evaluated for 90%+ overlap with existing guide content (`docs/resource-evaluations/beyond-vibe-coding.md`)
  - **Content**: 6-chapter book (Intro/Principles/Advanced Techniques/CLI Agents/Production/Future Trends) published 2025, paid format ($B0F6S5425Y Amazon), freemium web content at beyond.addy.ie
  - **Key frameworks**: The 70% Problem (AI accelerates 70%, final 30% needs rigor), Context Engineering as RAM metaphor, Critique-Driven Development, MCP as "USB-C for AI", Multi-Agent Orchestration
  - **Overlap analysis**: 14 aspects compared — 10/14 already covered 100% (Vibe Coding, Context Engineering, MCP, Multi-Agent, Plan Mode, TDD, Spec-First, Visual Context, Production Safety)
  - **Gap identified**: Critique-Driven Development framework not explicitly documented (conceptually covered via code review workflows), Few-Shot Prompting technique, Cost-Benefit Analysis Framework
  - **Cross-validation**: Osmani's "80% Problem" article already evaluated 3/5 (ai-ecosystem.md:2024), "Good Spec" article already integrated 4/5 (workflows/spec-first.md)
  - **Decision**: Tracking mention (3-5 lines in ai-ecosystem.md:2024) + cross-ref citations (1-2 lines in 4-5 overlapping sections) + "Context as RAM" metaphor note (methodologies.md:192)
  - **Rationale**: Book = external validation/synthesis, but guide already more comprehensive (11K lines vs paid book). Rejected full integration (paid resource, 90% duplication, 2 Osmani articles already integrated)

## [3.20.8] - 2026-02-01

### Updated

- **RTK (Rust Token Killer) Evaluation** — Major update from v0.2.0 to v0.7.0 (score upgraded from 4/5 to 4.5/5, +0.43 points) (`docs/resource-evaluations/rtk-evaluation.md`)
  - **All critical gaps resolved**: pnpm support (v0.6.0), npm/vitest (v0.6.0), git arg parsing bug fixed (v0.7.0), grep/ls broken commands fixed (v0.7.0), GitHub CLI support (v0.6.0), Cargo commands (v0.6.0), analytics system (`rtk gain` v0.4.0, `rtk discover` v0.7.0), auto-rewrite hook for Claude Code PreToolUse (v0.7.0)
  - **Evolution**: 5 major releases in 9 days (2026-01-23 → 2026-02-01) with 10+ community PRs merged (FlorianBruniaux contributions integrated upstream)
  - **Architecture maturity**: 24 command modules (was 12), 9 filtering strategies (50-99% reduction), SQLite token tracking (`~/.local/share/rtk/history.db`), configuration system (`~/.config/rtk/config.toml`), ARCHITECTURE.md documentation
  - **Community growth**: 17 stars (+113% from 8), 2 forks (+200% from 0), 1 open issue, 2+ contributors (active development)
  - **Score breakdown**: Accuracy +1 (3→4, bugs fixed), Comprehensiveness +1 (4→5, full stack coverage), Production Readiness +1 (3→4, architecture docs), Community +1 (2→3, growth trajectory)
  - **Token reduction**: 72.6% (git only, v0.2.0) → 89.4% (full stack estimate, v0.7.0) with 85% command coverage (was 40%)
  - **Recommendation updated**: "GOOD (4/5) - git-only, bugs, experimental" → "EXCELLENT (4.5/5) - production-ready for early adopters, full modern dev stack (git, pnpm, npm, cargo, gh)"
  - **Fork status**: Fork (FlorianBruniaux/rtk) no longer needed — all features merged upstream, use `pszymkowiak/rtk` v0.7.0 directly

## [3.20.7] - 2026-02-01

### Added

- **Addy Osmani Spec-Writing Evaluation** (scored 4/5, High Value) — Integration of ["How to write a good spec for AI agents"](https://addyosmani.com/blog/good-spec/) by Addy Osmani (former Head of Chrome Developer Experience at Google, 14 years Chrome team, O'Reilly author)
  - **Resource evaluation**: Systematic 5-point assessment with fact-checking (Perplexity verified credentials, all claims sourced) and technical-writer agent challenge phase (corrected initial 3/5 → 4/5 score) (`docs/resource-evaluations/addy-osmani-good-spec.md`)
  - **Gaps filled**: Modular prompts strategy, operational boundaries framework (Always/Ask First/Never), command spec templates, anti-pattern documentation for monolithic CLAUDE.md
  - **Integration priority**: High (within 1 week) — addresses daily user pain points (context pollution, spec clarity, operational decision-making)
- **Spec-First Workflow: 4 New Sections** (~180 lines added to `guide/workflows/spec-first.md`, 327 → 507 lines total)
  - **"Modular Spec Design"** (line 322): Pattern for splitting large CLAUDE.md files into focused domain files (CLAUDE-auth.md, CLAUDE-api.md, etc.). When to split (>200 lines threshold), 3 split strategies (feature-based, role-based, workflow-based), implementation pattern with @file references
  - **"Operational Boundaries"** (line 372): Three-tier boundary system (Always/Ask First/Never) mapped to Claude Code permission modes (auto-accept/default/plan mode). Decision framework table, API development example, quarterly review guidelines
  - **"Command Spec Template"** (line 432): Template for executable command specifications (testing, build, deployment, database commands) with expected outputs and error handling. Examples: `pnpm test`, `pnpm build`, `pnpm db:migrate` with safety checks
  - **"Anti-Pattern: Monolithic CLAUDE.md"** (line 472): Explains cognitive load problem (>200 lines = context pollution), real-world before/after example (387 lines → 7 focused files, 61% context reduction), migration checklist
- **Reference Index**: 8 new entries in `machine-readable/reference.yaml` (spec_first_workflow, spec_modular_design, spec_operational_boundaries, spec_command_template, spec_anti_monolithic, spec_osmani_source, spec_osmani_evaluation, spec_osmani_score)
- **README.md**: Incremented resource evaluations count (35 → 36 assessments)
- **Fresh Context Pattern**: New "Session-per-Concern Pipeline" variant — dedicates a fresh session to each quality dimension (plan → test → implement → security review → perf → code review) instead of looping the same task. References OpusPlan and TDD. (`guide/ultimate-guide.md:1595`)
- **Resource Evaluation #19: dclaude** (Patrick Debois) — Dockerized Claude Code wrapper evaluated at 2/5 (Marginal). Fills a narrow gap (Linux + Docker Engine without Docker Desktop) but uses standard containers with host Docker socket mount — weaker isolation than Docker Sandboxes' microVMs. Footnote added in `guide/security/sandbox-isolation.md` Limitations subsection. (`docs/resource-evaluations/dclaude-docker-wrapper.md`)
- **Resource Evaluation #20: 10 Tips from Inside the Claude Code Team** (paddo.dev / Boris Cherny thread) — Scored 4/5 (High Value). 4 integrations in ultimate-guide.md:
  - **Prompting as Provocation** (section 2.6.1): 3 challenge patterns — Gatekeeper, Proof Demand, Reset — treating Claude as a peer to convince rather than an assistant to direct (`guide/ultimate-guide.md:3029`)
  - **Model-as-Security-Gate** hook pattern: Route permission requests to Opus 4.5 via PreToolUse hook for intelligent security screening beyond static rules (`guide/ultimate-guide.md:6907`)
  - **Boris Cherny team patterns**: Skills as institutional knowledge (/techdebt, context dumps, BigQuery agents), CLI-over-MCP rationale, re-plan when stuck, Claude writes its own rules (`guide/ultimate-guide.md:11822`)
  - **Worktree shell aliases**: za/zb/zc navigation + dedicated analysis worktree tip (`guide/ultimate-guide.md:10717`)

## [3.20.6] - 2026-02-01

### Added

- **agentskills.io Open Standard integration** (scored 4/5) — Agent Skills follow the [agentskills.io](https://agentskills.io) specification, created by Anthropic, supported by 26+ platforms (Cursor, VS Code, GitHub, Codex, Gemini CLI, Goose, Roo Code, etc.)
  - SKILL.md frontmatter table now distinguishes spec fields (`name`, `description`, `allowed-tools`, `license`, `compatibility`, `metadata`) from Claude Code-only extensions (`context`, `agent`) (`guide/ultimate-guide.md:5180`)
  - `skills-ref validate` / `skills-ref to-prompt` CLI tool added to skill creation workflow (`guide/ultimate-guide.md:5188`)
  - Skill Portability section in Goose comparison (`guide/ecosystem/ai-ecosystem.md:1876`)
  - 16 new reference.yaml entries (spec, CLI, anthropics/skills repo, SafeDep threat model, blog)
- **Agent Skills Supply Chain Risks** — New section 1.2 in security-hardening.md based on SafeDep threat model (8-14% of public skills have vulnerabilities). 4 mitigations: review SKILL.md, validate with skills-ref, pin versions, audit scripts/ (`guide/security/security-hardening.md:121`)
- **anthropics/skills** (60K+⭐) added to README Complementary Resources table
- **Resource Evaluations**: Skill Doctor GitHub Action (2/5, marginal), agentskills.io specification (4/5, high value) (`docs/resource-evaluations/skill-doctor-github-action.md`, `docs/resource-evaluations/agentskills-io-specification.md`)

## [3.20.5] - 2026-01-31

### Added

- **Visual Reference**: 4 new high-value ASCII diagrams (16 → 20 total)
  - **#17 TDD Red-Green-Refactor Cycle** — Cyclic loop showing the iterative nature of TDD
  - **#18 UVAL Protocol Flow** — 4-step learning framework (Understand → Verify → Apply → Learn) with failure backtrack paths
  - **#19 Security 3-Layer Defense** — Prevention/Detection/Response overview with adoption path by team size
  - **#20 Secret Exposure Timeline** — Emergency response actions by time window (15min/1h/24h) with severity guide
- **README.md**: Added Visual Reference to Core Documentation table

## [3.20.4] - 2026-01-31

### Added

- **30 New Quiz Questions** (227 → 257 total) across 11 categories
  - **Advanced Patterns** (+8): Mechanic Stacking, Permutation Frameworks, "You Are the Main Thread", Task Lists as Diagnostic, Anti-hallucination occurrence rule, Multi-Agent PR Review, Comprehension Debt, CLAUDE.md compounding memory
  - **MCP Servers** (+3): MCP Apps (SEP-1865), `auto:N` lazy loading, Semgrep top score (9.0/10)
  - **Architecture** (+3): Tasks API (replaces TodoWrite), Tasks API N+1 overhead, TeammateTool experimental status
  - **Reference** (+3): `--from-pr` flag, `$ARGUMENTS` bracket syntax breaking change, Myths vs Reality
  - **Hooks** (+2): Async hook `async: true` config, async hook limitations
  - **Learning with AI** (+2): Addy Osmani's 80% Problem failure modes, vibe coding context overload symptoms
  - **Security** (+2): Docker sandbox isolation, GitHub Issue Auto-Creation Bug (#13797)
  - **AI Ecosystem** (+3): LM Studio bridge cost savings, external orchestrators (Gas Town/multiclaude/agent-chat), skeleton project audit areas
  - **Memory & Settings** (+2): 8 verification domains, Fresh Context Pattern
  - **Agents** (+1): AGENTS.md vs Skills invocation reliability (100% vs 53-79%)
  - **Privacy** (+1): Co-Authored-By vs Assisted-By traceability
  - Difficulty distribution: 4 junior, 4 intermediate, 14 senior, 8 power
  - Also fixed pre-existing "14 categories" → "15 categories" in landing quiz page

### Changed

- **README.md**: Quiz badge updated (227 → 257), quiz section updated
- **Landing site**: All quiz counts updated (index.html, quiz/index.html, learning/index.html, CLAUDE.md)

## [3.20.3] - 2026-01-31

### Added

- **Competitive Analysis: 9 Gaps Filled from claudelog.com** — Systematic veille against claudelog.com (313 pages, InventorBlack/r/ClaudeAI)
  - **Section 9.19: Permutation Frameworks** (~180 lines, `guide/ultimate-guide.md`)
    - CLAUDE.md-driven systematic variation testing (define dimensions → generate variants → implement → evaluate)
    - Step-by-step implementation with practical API design example (REST vs GraphQL vs tRPC)
    - Anti-patterns table, integration with TDD/Plan Mode/Skeleton Projects
  - **Skeleton Projects Workflow** — `guide/workflows/skeleton-projects.md` (NEW, 208 lines)
    - 4-phase workflow: Find & Evaluate → Fork & Customize → Expand to MVP → Document
    - Sub-agent evaluation pattern for skeleton auditing (Security + Architecture + DX)
    - Expansion timeline (Day 1 → Week 1 → Month 1) with common pitfalls
  - **Task Lists as Diagnostic Tool** (~50 lines, `guide/ultimate-guide.md`)
    - Divergence patterns table: too broad, too narrow, wrong priorities, missing/extra tasks
    - Diagnostic workflow using TaskList as instruction clarity sanity check
  - **Rev the Engine** (~45 lines, `guide/ultimate-guide.md`)
    - Multi-round planning pattern (3 rounds: initial → challenge → finalize → execute)
    - Integrated after OpusPlan in Plan Mode section
  - **Mechanic Stacking** (~30 lines, `guide/ultimate-guide.md`)
    - 5-layer intelligence stack: Plan Mode → Extended Thinking → Rev → Split-Role → Permutation
    - Decision matrix matching stack depth to decision impact (Low → Critical)
  - **Split-Role Sub-Agents** (~60 lines, `guide/ultimate-guide.md`)
    - Multi-perspective analysis pattern with custom agent YAML templates
    - Security Expert + Performance Analyst + UX/API Reviewer example
  - **"You Are the Main Thread" Mental Model** (~30 lines, `guide/ultimate-guide.md`)
    - CPU scheduler analogy: developer as orchestrator, Claude instances as worker threads
    - ASCII diagram with 4 practical implications
  - **Continuous Context Update** (~40 lines, `guide/ultimate-guide.md`)
    - Proactive CLAUDE.md enrichment during dev sessions (not just reactive error capture)
    - Discovery type → CLAUDE.md section mapping table
  - **Smart Hook Dispatching** (~80 lines, `guide/ultimate-guide.md`)
    - Single dispatcher routing events by file type and tool to specialized handlers
    - Handler directory structure with language-specific hooks (TypeScript, Python, Rust, SQL)
  - **Reference updates**: `machine-readable/reference.yaml` (+17 entries)
    - `permutation_frameworks`, `rev_the_engine`, `mechanic_stacking`, `split_role_sub_agents`,
      `task_lists_diagnostic`, `main_thread_orchestrator`, `continuous_context_update`,
      `smart_hook_dispatching`, `skeleton_projects_workflow`
  - **Workflows README**: Updated `guide/workflows/README.md` with Skeleton Projects entry + Quick Selection Guide

### Changed

- **README.md**: Guide line count updated (15K → 16K), version bumped to 3.20.3
- **Guide line count**: 15,771 → 16,293 (+522 lines)

---

- **Sandbox Isolation for Coding Agents** — `guide/security/sandbox-isolation.md` (NEW), `machine-readable/reference.yaml`, `guide/ultimate-guide.md`
  - Score: 4/5 (High Value — official Docker docs + verified vendor documentation)
  - Source: [docs.docker.com/ai/sandboxes/](https://docs.docker.com/ai/sandboxes/) (Docker Desktop 4.58+, Jan 2026)
  - New guide file: Docker Sandboxes (microVM isolation, network policies, custom templates, supported agents)
  - Alternatives landscape: Fly.io Sprites, Cloudflare Sandbox SDK, E2B, Vercel Sandboxes, native CC sandbox
  - Comparison matrix (6 solutions, 7 criteria) + decision tree (Mermaid flowchart)
  - Safe autonomy workflows: Docker Sandbox + `--dangerously-skip-permissions` pattern, CI/CD sketch
  - Anti-patterns table (6 entries)
  - Cross-reference added after `--dangerously-skip-permissions` warning (ultimate-guide.md:3953)
  - 18 new `sandbox_*` entries in reference.yaml
  - Evaluation: `docs/resource-evaluations/docker-sandboxes-isolation.md`

- **Claude Code releases tracking: v2.1.27** — `machine-readable/claude-code-releases.yaml`, `guide/core/claude-code-releases.md`
  - `--from-pr` flag to resume sessions linked to GitHub PR number/URL
  - Sessions auto-linked to PRs when created via `gh pr create`
  - Context management fixes for Bedrock/Vertex gateway users
  - Landing synced: banner + timeline card in index.html

- **Contribution Metrics (Anthropic blog, Jan 29 2026)** — `guide/ultimate-guide.md`, `machine-readable/reference.yaml`
  - Score: 4/5 (High Value — official source with harder metrics superseding Aug 2025 data)
  - Source: [claude.com/blog/contribution-metrics](https://claude.com/blog/contribution-metrics)
  - New subsection after Anthropic Internal Study: +67% PRs merged/engineer/day, 70-90% AI-assisted code
  - Contribution Metrics dashboard: public beta, Team & Enterprise plans (GitHub integration)
  - Methodological note: PR-based measurement vs Aug 2025 self-reported surveys
  - ROI cross-reference added in cost optimization section
  - Evaluation: `docs/resource-evaluations/026-contribution-metrics-blog.md`

- **Learning guide: Shen & Tamkin RCT integration** — `guide/roles/learning-with-ai.md`
  - Source: [arXiv:2601.20245](https://arxiv.org/abs/2601.20245) (Shen & Tamkin, Anthropic Fellows, Jan 2026)
  - Score: 3/5 (Relevant - Useful complement, high overlap with existing content)
  - Added RCT data point in §3 "Reality of AI Productivity": 17% skill reduction (n=52, Cohen's d=0.738, p=0.01), no significant speed gain, only ~20% delegation users finished faster
  - Added new Red Flag: "Perception gap" — AI users rate tasks easier while scoring lower
  - Added full reference in §12 Sources (Academic Research) with 6 interaction patterns summary
  - Also added METR RCT (arXiv:2507.09089) in Productivity Research sources

## [3.20.1] - 2026-01-30

### Added

- **Resource Evaluation: Vercel AGENTS.md vs Skills Eval** — `docs/resource-evaluations/025-vercel-agents-md-vs-skills-eval.md`
  - Score: 3/5 (Pertinent — confirms existing CLAUDE.md architecture)
  - Source: [Jude Gao (Vercel), Jan 27 2026](https://vercel.com/blog/agents-md-outperforms-skills-in-our-agent-evals)
  - First quantified benchmark: eager context (AGENTS.md) 100% vs lazy invocation (skills) 53-79%
  - Key finding: skills auto-invoked only 56% of the time by coding agents
  - Compression benchmark: 40KB → 8KB docs index with zero performance loss
  - Double challenge: technical-writer + system-architect agents (unanimous 3/5)
  - Fact-check: 13/13 claims verified
  - Conflict of interest noted: Vercel operates both skills.sh and the AGENTS.md codemod

### Changed

- **CLAUDE.md sizing** (ultimate-guide.md:3527): Added Vercel 8KB compression benchmark as evidence for 4-8KB target
- **Memory Loading insight** (ultimate-guide.md:4082): Added warning about 56% skill invocation rate — critical instructions should use CLAUDE.md/rules, not skills
- **Skills trade-offs** (ultimate-guide.md:5652): Added invocation reliability caveat with source

## [3.20.0] - 2026-01-30

### Added

- **Code Review Automation: Multi-Agent PR Review** — Production-grade review patterns from Pat Cullen & Méthode Aristote
  - **Resource evaluation**: `docs/resource-evaluations/017-pat-cullen-final-review.md`
    - Score: 5/5 (Critical - Must integrate immediately)
    - Source: [Pat Cullen's Final Review Gist](https://gist.github.com/patyearone/c9a091b97e756f5ed361f7514d88ef0b) (Jan 28, 2026)
    - Multi-agent workflow with 3 specialized agents: Consistency Auditor, SOLID Analyst, Defensive Code Auditor
    - Anti-hallucination safeguards: pre-flight check (git log Co-Authored-By detection), verification protocol, occurrence rule
    - Production patterns: reconciliation step, severity classification (🔴🟡🟢), auto-fix convergence loop
    - Fact-checked: All claims verified, workflow production-ready (used regularly by author)
  - **Enhanced `/review-pr` command**: `examples/commands/review-pr.md` (+150 lines: 80 → 230)
    - Simple template PRESERVED (lines 1-80) for beginners
    - NEW "Advanced: Multi-Agent Review" section (line 81+)
    - Pre-flight check: `git log --oneline -10 | grep "Co-Authored-By: Claude"` to avoid repeating suggestions
    - Multi-agent specialization: 3 parallel agents (Consistency, SOLID, Defensive)
    - Anti-hallucination rules: verify patterns with Grep/Glob before recommending (occurrence rule: >10 = established)
    - Reconciliation: prioritize existing project patterns, skip with documented reasoning
    - Severity classification: 🔴 Must Fix (blockers) / 🟡 Should Fix / 🟢 Can Skip
    - Auto-fix loop: review → fix → re-review → converge (max 3 iterations)
    - Conditional context loading: stack-agnostic table (DB queries → check indexes, API routes → check auth, etc.)
  - **Enhanced `code-reviewer` agent**: `examples/agents/code-reviewer.md` (+219 lines: 72 → 291)
    - NEW "Anti-Hallucination Rules" section (line 75)
      - Verification protocol: Use Grep/Glob before claiming patterns exist
      - Occurrence rule: >10 occurrences = established, 3-10 = emerging, <3 = not established
      - Read full file context (not just diff lines)
      - Uncertainty markers: ❓ To verify / 💡 Consider / 🔴 Must fix
    - NEW "Conditional Context Loading" section
      - Detailed table: if diff contains X → load context Y → use tools Z
      - Stack-agnostic patterns (imports → check package.json, DB queries → check schema, etc.)
    - NEW "Defensive Code Audit" section
      - Silent catches detection: empty catch blocks, console-only catches
      - Hidden fallbacks detection: chained fallbacks (a || b || c), optional chaining with fallback
      - Unchecked nulls detection: property access without validation
      - Ignored promise rejections: async calls without .catch()
    - NEW "Severity Classification System" with justification requirements
    - Enhanced output format with evidence-based findings
    - Attribution: Méthode Aristote production code review patterns
  - **Enhanced iterative refinement workflow**: `guide/workflows/iterative-refinement.md` (+133 lines: 389 → 522)
    - NEW "Review Auto-Correction Loop" section (line 347)
    - Pattern: review → fix → re-review → converge (with visual diagram)
    - Safeguards: max iterations, quality gates (tsc/lint), protected files, change threshold, rollback capability
    - Example session: 3 iterations with 🔴 Must Fix → 🟡 Should Fix → 🟢 Can Skip convergence
    - Comparison: one-pass review vs convergence loop (when to use each)
    - Integration with multi-agent review
    - Convergence criteria: 5 conditions (no issues, max iterations, change threshold, quality gate failure, manual stop)
    - Anti-patterns table: infinite loop, scope creep, breaking fixes, protected file changes, context loss
  - **Enhanced ultimate guide**: `guide/ultimate-guide.md` (+28 lines, ~line 4623)
    - NEW "Production Example: Multi-Agent Code Review" after existing Code Review Prompt
    - 3 specialized agent roles: Consistency, SOLID, Defensive Code Auditor
    - Key patterns beyond generic Split Role: pre-flight check, anti-hallucination (Grep/Glob verification), reconciliation, severity classification, convergence loop
    - Production safeguards: full file context, conditional loading, protected files, quality gates
    - Attribution: Pat Cullen's Final Review Gist + implementation references
  - **Reference updates**: `machine-readable/reference.yaml` (+3 entries)
    - `review_pr_advanced: "examples/commands/review-pr.md:81"`
    - `review_anti_hallucination: "examples/agents/code-reviewer.md:75"`
    - `review_auto_fix_loop: "guide/workflows/iterative-refinement.md:347"`
  - **Impact**: Transforms basic `/review-pr` template into production-grade multi-agent system
    - Beginner-friendly: simple template preserved (lines 1-80)
    - Advanced users: comprehensive patterns for critical code review
    - Anti-hallucination safeguards prevent false suggestions
    - Defensive code audit catches silent failures (empty catches, hidden fallbacks, unchecked nulls)
    - Convergence loop ensures quality through iterative refinement
  - **Design principles**: Enrich existing files (no fragmentation), no breaking changes (review-pr.md not renamed), complete attribution (Pat Cullen + Méthode Aristote), audience-aware (simple → advanced progression)

## [3.19.0] - 2026-01-30

### Added

- **Practitioner Insight: Addy Osmani (Google Chrome Team)** — Added to AI Ecosystem Practitioner Insights
  - **New entry**: `guide/ecosystem/ai-ecosystem.md` line ~2024 "Addy Osmani (Google Chrome Team)" (~32 lines)
    - "The 80% Problem in Agentic Coding" synthesis (January 28, 2026)
    - Three new failure modes: overengineering, assumption propagation, sycophantic agreement
    - Comprehension debt concept (distinct from technical debt)
    - Productivity paradox data: +98% PRs, +91% review time, no workload reduction
    - Alignment table mapping Osmani concepts to existing guide sections
  - **Reference updates**: `machine-readable/reference.yaml` — 4 new entries
    - `practitioner_addy_osmani: "guide/ecosystem/ai-ecosystem.md:2024"`
    - `practitioner_osmani_source: "https://addyo.substack.com/p/the-80-problem-in-agentic-coding"`
    - `eighty_percent_problem`, `comprehension_debt_secondary`
  - **Resource evaluation**: `docs/resource-evaluations/024-addy-osmani-80-percent-problem.md`
    - Score: 3/5 (Pertinent) — Useful synthesis, but 90% overlap with existing content
    - Minimal integration approach (32 lines vs rejected 250 lines proposal)
    - Fact-check: 6 stats verified, 1 Stack Overflow stat found incorrect
    - Challenge by technical-writer agent validated downgrade from 4/5 to 3/5
    - Transparent note: "secondary synthesis, primary sources already documented"

- **Hook Execution Model Documentation** — New comprehensive section documenting async vs sync hooks (v2.1.0+)
  - **New section**: `guide/ultimate-guide.md` line ~6075 "Hook Execution Model (v2.1.0+)" (~97 lines)
    - Synchronous vs Asynchronous execution explained
    - Configuration examples with `async: true` parameter
    - **Decision matrix**: 15 use cases (formatting, linting, type checking, security, logging, notifications, etc.)
    - Performance impact analysis (example: -5-10s per session with async formatting)
    - Limitations of async hooks (no exit code feedback, no additionalContext, no blocking)
    - Version history (v2.1.0 introduction, v2.1.23 cancellation fix)
  - **Reference updates**: `machine-readable/reference.yaml` — 7 new entries
    - `hooks_execution_model: 6075` (section pointer)
    - `hooks_async_support`, `hooks_async_use_cases`, `hooks_sync_use_cases`
    - `hooks_decision_matrix: 6091`, `hooks_async_limitations`, `hooks_async_bug_fix`
  - **Resource evaluation**: `docs/resource-evaluations/melvyn-malherbe-async-hooks-linkedin.md`
    - Score: 1/5 (Low - Reject) — Marketing post without technical value
    - **Gap identified**: Async hooks behavior not explicitly documented in guide
    - Fact-checked via Perplexity Deep Research (comprehensive 5K+ token report)
    - Challenge by technical-writer agent validated rejection + gap discovery
    - LinkedIn post (Jan 30, 2026) from Melvyn Malherbe redirects to commercial product (mlv.sh/ccli → codelynx.dev)
  - **Practical migration guide**: `claudedocs/aristote-hooks-migration-prompt.md` (400+ lines)
    - Real-world example: Méthode Aristote project with 7 hooks analyzed
    - 3 hooks migrated to async (auto-format, activity-logger, notification) for -12.75s/session gain
    - 4 hooks kept sync (dangerous-actions-blocker, typecheck-feedback, post-release-doc-update, git-context)
    - Step-by-step migration plan with verification checklist
    - Complete modified configuration in `claudedocs/aristote-hooks-migration.json`
  - **Impact**: Critical documentation gap filled — async hooks introduced in v2.1.0 but execution model never explicitly documented
    - Users can now optimize hook performance by migrating non-critical hooks to async
    - Decision matrix provides clear guidance on when to use sync vs async
    - Real-world case study demonstrates 30-40% reduction in blocked time per session
  - **Discovery method**: Resource evaluation workflow successfully identified gap through:
    1. LinkedIn post analysis (low technical value)
    2. Perplexity Deep Research confirming async hooks exist
    3. Guide audit revealing missing documentation
    4. Technical-writer agent challenge validating findings

## [3.18.2] - 2026-01-30

### Added

- **Practitioner Insights** — Peter Steinberger (PSPDFKit Founder, Moltbot Creator)
  - Added new practitioner insight in `guide/ecosystem/ai-ecosystem.md` documenting model-agnostic workflow patterns
  - **Patterns documented**: Stream monitoring, multi-project juggling (3-8 concurrent projects), fresh context validation, iterative exploration
  - **Source**: [Shipping at Inference-Speed](https://steipete.me/posts/2025/shipping-at-inference-speed) (Dec 2025 blog post)
  - **Evaluation**: Score 3/5 (Relevant - Useful complement)
    - Complete evaluation in `docs/resource-evaluations/steinberger-inference-speed.md`
    - Fact-checked GPT-5.2 claims (confirmed real, Dec 2024 release)
    - Validated PSPDFKit credentials (60+ employees, Dropbox/DocuSign/SAP clients)
  - **Alignment with guide**: Validates existing patterns (Fresh Context Section 2.2, Multi-Instance Section 9.13, Iterative Refinement workflows)
  - **Scope**: Model-agnostic patterns only, zero model comparisons (Codex/Opus excluded as per evaluation decision)
  - **Note**: Patterns originate from non-Claude workflow (Moltbot/GPT-5.2); validation in Claude Code context recommended
  - **Files modified**:
    - `guide/ecosystem/ai-ecosystem.md`: New entry after Matteo Collina (~26 lines, H3 format with alignment table)
    - `docs/resource-evaluations/steinberger-inference-speed.md`: Complete evaluation with challenge agent review
    - `docs/resource-evaluations/README.md`: Index updated (15→16 evaluations)
    - `machine-readable/reference.yaml`: Added `practitioner_steinberger` references (line 1997)

## [3.18.1] - 2026-01-30

### Changed

- **Claude Code Releases Tracking** — Updated to v2.1.25
  - **v2.1.25** (2026-01-30): Fixed beta header validation for Bedrock/Vertex gateway users
  - **v2.1.23** (2026-01-29): Customizable spinner verbs, mTLS/proxy fixes, terminal performance improvements
  - **Files updated**:
    - `machine-readable/claude-code-releases.yaml`: Updated latest version, added 2 new releases
    - `guide/core/claude-code-releases.md`: Synchronized with YAML, added detailed release notes
  - **Landing sync**: Updated Claude Code version badge v2.1.22 → v2.1.25

## [3.18.0] - 2026-01-28

### Added

- **MCP Servers Ecosystem Documentation** — New `guide/ecosystem/mcp-servers-ecosystem.md` (893 lines) documenting validated community MCP servers
  - **8 validated production-ready servers**:
    - **Playwright MCP** (Microsoft): Browser automation with accessibility trees (Quality: 8.8/10)
    - **Semgrep MCP** (Semgrep Inc.): Security scanning SAST/secrets/supply chain (Quality: 9.0/10)
    - **Kubernetes MCP** (Red Hat): Cluster management in natural language (Quality: 8.4/10)
    - **Context7 MCP**: Official framework documentation lookup (Quality: 7.2/10)
    - **Linear MCP**: Project management integration (Quality: 8.6/10)
    - **Vercel MCP**: Deployment and logs integration (Quality: 8.0/10)
    - **Browserbase MCP**: Headless browser infrastructure (Quality: 7.8/10)
    - **MCP-Compose**: Multi-server orchestration (Quality: 7.0/10)
  - **Evaluation framework**: 5 criteria (GitHub stars ≥50, release <3 months, docs, tests, unique use case)
  - **Production deployment guide**: Security checklist, quick start stack, performance metrics
  - **Ecosystem evolution**: Linux Foundation standardization, MCPB format, Advanced MCP Tool Use, MCP Apps
  - **Monthly watch methodology**: Template for maintaining guide with ecosystem updates
  - **Quality scoring system**: 5 dimensions (Maintenance, Documentation, Tests, Performance, Adoption) normalized to /10
  - **Files modified**:
    - `guide/ultimate-guide.md`: Added Community MCP Servers section with comparison table and quick start
    - `guide/README.md`: Added mcp-servers-ecosystem.md to docs table
  - **Impact**: Fills critical gap in guide - community MCP servers were previously undocumented

## [3.18.0] - 2026-01-28

### Added

- **Known Issues Tracker** — New `guide/core/known-issues.md` (285 lines) documenting verified critical bugs
  - **GitHub Issue Auto-Creation Bug**: Verified Issue #13797 (Dec 2025), 17+ confirmed accidental public disclosures
    - Security/privacy risk: Private project details exposed in public anthropics/claude-code repo
    - Affected versions: v2.0.65+
    - Status: ACTIVE as of Jan 28, 2026
    - Workarounds documented: Explicit repo specification, manual approval, pre-execution verification
    - Examples: #20792, #16483, #16476, #17899, #16464 ("wrong repo", "delete this")
  - **Excessive Token Consumption**: Issue #16856 (Jan 2026), 20+ reports of 4x+ faster consumption
    - Affected versions: v2.1.1+ (reported, published Jan 7, 2026)
    - Corrected version: Report claimed v2.0.61 (doesn't exist), real bug is v2.1.1
    - Anthropic status: "Not officially confirmed as bug" (investigating)
    - Possible causes: Holiday bonus expiration (Dec 25-31) + potential underlying issues
    - Workarounds: Monitor with /context, shorter sessions, disable auto-compact, reduce MCP tools
  - **Model Quality Degradation** (Aug-Sep 2025): ✅ RESOLVED
    - Official Anthropic postmortem: 3 infrastructure bugs (traffic misrouting, output corruption, XLA:TPU miscompilation)
    - Not intentional model degradation (community theories debunked)
    - All bugs fixed by mid-September 2025
    - Source: https://www.anthropic.com/engineering/a-postmortem-of-three-recent-issues
  - **Stats verified via GitHub API** (Jan 28, 2026): 5,702 open issues (not 4,697 reported), 527 invalid labels (not 263), 80+ releases
  - **Fact-checking methodology**: Perplexity Pro (4 searches) + direct GitHub API queries (gh api, gh search issues, gh issue view)
  - **References**: Official links to GitHub issues, Anthropic postmortem, The Register article
  - **Impact**: Critical security awareness for users, actionable workarounds, transparent issue tracking
  - **Files modified**:
    - `guide/README.md`: Added known-issues.md to docs table
    - `machine-readable/reference.yaml`: 4 new entries (known_issues, github_bug:16, token_consumption:136, model_quality:231)
    - `docs/resource-evaluations/023-community-discussions-report-jan2026.md`: Full evaluation process (score 2/5, partial integration)

- **RTK (Rust Token Killer) integration** — Command output optimization tool for 72.6% token reduction
  - **New documentation**: `docs/resource-evaluations/rtk-evaluation.md` (comprehensive evaluation, score 4/5)
  - **Guide integration**: Section 9.13 Cost Optimization → new "Command Output Optimization with RTK" subsection
  - **Benchmarks verified**:
    - `rtk git log`: 92.3% reduction (13,994 → 1,076 chars)
    - `rtk git status`: 76.0% reduction (100 → 24 chars)
    - `rtk find`: 76.3% reduction (780 → 185 chars)
    - Average across working commands: 72.6% reduction
  - **Integration templates**:
    - `examples/claude-md/rtk-optimized.md`: CLAUDE.md template for manual RTK usage
    - `examples/skills/rtk-optimizer/SKILL.md`: Auto-suggestion skill for high-verbosity commands
    - `examples/hooks/bash/rtk-auto-wrapper.sh`: PreToolUse hook for automatic RTK wrapping
  - **Upstream contributions**: `claudedocs/rtk-pr-proposals.md` with 7 PR proposals (grep fix, ls fix, npm support)
  - **Limitations documented**: grep broken (v0.2.0), ls worse (-274%), low adoption (8 stars), early-stage
  - **Use cases**: Git workflows, file finding, large file reading (avoid: ls, grep, small outputs)
  - **Impact**: Proven 72.6% token reduction for git operations, validates preprocessing optimization strategy
  - **Reference**: https://github.com/pszymkowiak/rtk

### Fixed

- **Corrected "mgrep" misattribution in Everything Claude Code evaluation**
  - **Issue**: Incorrectly claimed Everything Claude Code contained "mgrep (50% token reduction)" tool
  - **Reality**: No such tool exists in affaan-m/everything-claude-code repository (verified via WebFetch)
  - **Confusion**: Mixed up mgrep (mixedbread-ai semantic search) with non-existent token reduction tool
  - **Files corrected**:
    - `docs/resource-evaluations/015-everything-claude-code-github-repo.md`: Removed 14 erroneous mgrep mentions
    - `machine-readable/reference.yaml:724`: Removed "mgrep (50% token reduction)" from unique patterns
    - `guide/ultimate-guide.md:14821`: Replaced with verified patterns (hookify, strategic compaction)
    - `CHANGELOG.md`: Updated v3.17.0 and v3.15.0 entries
  - **Verified patterns now documented**: hookify, pass@k metrics, sandboxed subagents, strategic compaction skills
  - **Impact**: Maintains guide credibility, prevents user confusion, ensures accuracy of ecosystem documentation

## [3.17.1] - 2026-01-27

### Added

- **Repository Structure diagram** in README.md
  - Interactive Mermaid diagram (graph LR layout) with 6 main directories
  - High-contrast colors (dark backgrounds + white text) for readability
  - ASCII art fallback in collapsible section for detailed structure
  - Shows key metrics: 15K lines guide, 86 templates, 227 questions, 22 evaluations

### Changed

- **README V3** — Merged best elements from two versions (README.md + README-new.md)
  - Kept "WHY vs HOW" positioning and quiz prominence from new version
  - Restored cc-copilot-bridge, Learning Paths by role, AI Assistants section from old version
  - Removed excessive competitor references (8 mentions → 2-3 in Ecosystem only)
  - Complementary positioning instead of "graduate to everything-claude-code"
  - Final size: 491 lines (vs 474 original)

- **Quiz links** — Now points to online version first
  - Primary: https://florianbruniaux.github.io/claude-code-ultimate-guide-landing/quiz/
  - Secondary: Local ./quiz/ for offline use

- **Core Documentation table** — Added 4 missing guides
  - AI Ecosystem (Complementary AI tools & integration patterns)
  - AI Traceability (Code attribution & provenance tracking)
  - Search Tools Cheatsheet (Grep, Serena, ast-grep, grepai comparison)
  - Learning with AI (Use AI without becoming dependent)

- **Ecosystem section** — Added direct link to AI Ecosystem Guide for integration patterns

### Removed

- **README-new.md** — No longer needed after V3 merge

## [3.17.0] - 2026-01-27

### Added

- **Tasks API field visibility limitations** (Gang Rui analysis, 2026-01-27)
  - **guide/ultimate-guide.md:3133**: Added 3 rows to comparison table (description visibility, metadata visibility, multi-call overhead)
  - **guide/ultimate-guide.md:3195**: New subsection "⚠️ Tasks API Limitations (Critical)" (~40 lines)
    - Field visibility constraint table (TaskList vs TaskGet)
    - Impact analysis: 11x API overhead for 10 tasks, no metadata scanning, session resumption friction
    - Cost example with bash code block
    - 3 workaround patterns: Hybrid approach (recommended), subject-as-summary, selective fetching
    - Source attribution: Community practitioner feedback (Gang Rui, Jan 2026)
  - **guide/workflows/task-management.md:223**: New subsection "⚠️ Field Visibility Limitations" (~35 lines)
    - TaskList field visibility details (id, subject, status, owner, blockedBy only)
    - Workflow adjustment examples (DON'T vs DO patterns)
    - Cost awareness: quantified overhead for N tasks
    - Mitigation strategies: subject field usage, concise descriptions, markdown files for plans
  - **guide/cheatsheet.md:398**: Added limitation note (~3 lines)
    - Warning: TaskList shows limited fields
    - Workaround pointer: use TaskGet per task for descriptions/metadata
    - Actionable tip: store key info in subject field
  - **machine-readable/reference.yaml:143-146**: Added 4 new entries
    - tasks_api_limitations: 3195 (line reference to new subsection)
    - tasks_api_field_visibility: inline summary
    - tasks_api_cost_overhead: formula for overhead calculation
    - tasks_api_workarounds: 3210 (line reference to workaround patterns)
  - **docs/resource-evaluations/016-gang-rui-tasks-api-limitations.md**: New evaluation (score 5/5 CRITICAL)
    - Comprehensive fact-check (8/8 claims verified)
    - Challenge phase with technical-writer agent (score adjusted 4→5)
    - Integration details with exact line numbers for all 6 modified files
  - **Score justification**: Breaks recommended workflow, 11x-51x cost overhead, metadata invisibility affects all custom fields
  - **Impact**: Prevents user frustration, maintains guide credibility, transparent cost implications

### Changed

- **everything-claude-code stats update** (31.9k stars, 2026-01-27)
  - Updated star count from 16k → 31.9k across all files (`CHANGELOG.md`, `machine-readable/reference.yaml`, `guide/ultimate-guide.md`)
  - Added unique patterns documentation: hookify (conversational hooks), pass@k metrics, sandboxed subagents, strategic compaction
  - Created comprehensive evaluation: `docs/resource-evaluations/015-everything-claude-code-github-repo.md` (Score 5/5 CRITICAL)
  - Added new "Production Config Collections" section in guide (line ~14768)
  - Positioning clarified: Complementary to Ultimate Guide (production configs vs educational content)

## [3.16.0] - 2026-01-27

### Added

- **TeammateTool & Myths vs Reality Documentation** (`guide/ultimate-guide.md`, `guide/cheatsheet.md`, `machine-readable/reference.yaml`, `docs/resource-evaluations/`)
  - **guide/ultimate-guide.md:3294**: New section "TeammateTool (Experimental)" (~60 lines)
    - Capabilities: Multi-agent coordination, team messaging, swarm patterns
    - Operations table: spawnTeam, discoverTeams, requestJoin, approveJoin
    - Execution backends (in-process, tmux, iTerm2) with auto-detection
    - Pattern examples: Parallel Specialists, Swarm Pattern
    - Limitations: 5-minute heartbeat timeout, feature flags non-documented, experimental status
    - When to use vs when NOT to use guidance
    - 3 community sources cited (kieranklaassen gist, GitHub Issue #3013, claude-sneakpeek)
    - Warning: Unstable, no official Anthropic support
  - **guide/ultimate-guide.md:15257**: New appendix "Appendix D: Myths vs Reality" (~160 lines)
    - Myth #1: "Hidden features with secret flags" → Reality: Progressive rollout, not secrets
    - Myth #2: "Tasks API = autonomous agents" → Reality: Coordination, not autonomy
    - Myth #3: "100x faster than competitors" → Reality: Honest comparison, no marketing hyperbole
    - Section: "What Makes Claude Code Actually Special" (documented strengths with sources)
    - Section: "How to Spot Reliable Information" (red flags checklist, trusted sources)
    - Contribution process for new myths
  - **guide/cheatsheet.md**: New section "Hidden Features (But Official!)" (~15 lines)
    - Lists 5 under-utilized features: Tasks API, Background Agents, TeammateTool, Session Forking, LSP Tool
    - Pro tip: "Read the CHANGELOG—these aren't secrets!"
    - Placed after "File References" for visibility
  - **machine-readable/reference.yaml**: 12 new entries
    - teammatetool: 3294 (line reference)
    - teammatetool_status, teammatetool_capabilities, teammatetool_sources (4 entries)
    - appendix_c_resource_evaluation: 15214
    - appendix_d_myths_vs_reality: 15257
    - myths_hidden_features, myths_tasks_api_autonomous, myths_100x_faster, myths_reliable_sources (4 line references)
  - **docs/resource-evaluations/2026-01-27-claude-code-hidden-feature-social-post.md**: New evaluation (307 lines)
    - Score: 1/5 (Reject - Marketing misinformation)
    - Fact-check: 5 claims verified (3 false, 2 partially true)
    - Technical writer challenge: 3/5 → 1/5 (score revised down after critique)
    - Decision: Reject source, but document real gaps (TeammateTool, Myths section) with official sources only
    - 12 sources consulted (official CHANGELOG, community gists, Perplexity search, GitHub Issues)
  - **Total documentation**: ~235 lines across guide files
  - **Resources evaluated**: Social media post (rejected), community gists (validated)
  - **Key facts verified**:
    - TeammateTool: Real feature, partially feature-flagged, community-discovered
    - Tasks API (v2.1.16+): Official, public, documented in CHANGELOG
    - CLAUDE_CODE_ENABLE_TASKS: Migration flag (revert to old system), not activation flag
    - No "hidden features": All public features documented in official CHANGELOG
- **MCP Apps (SEP-1865) Documentation** (`guide/core/architecture.md`, `guide/ultimate-guide.md`, `machine-readable/reference.yaml`)
  - **guide/core/architecture.md:656**: New section "MCP Extensions: Apps (SEP-1865)" (~150 lines)
    - Technical architecture (2 primitives: tools with UI metadata + UI resources via `ui://` scheme)
    - Communication flow diagram (MCP Client → Server → Sandboxed Iframe)
    - Multi-layered security model (sandbox, pre-declared templates, auditable JSON-RPC, user consent, content blocking)
    - Complete SDK documentation (`@modelcontextprotocol/ext-apps`): connect, ontoolresult, callServerTool, updateModelContext
    - Platform support matrix (6 clients: Claude Desktop, Cowork, VS Code, ChatGPT, Goose, CLI)
    - CLI relevance analysis (indirect: ecosystem understanding, MCP server dev, hybrid workflows)
    - 5 official example servers (threejs, map, pdf, system-monitor, sheet-music)
    - Production adoption table (9 tools at launch: Asana, Slack, Figma, Amplitude, Box, Canva, Clay, Hex, monday.com)
    - Relationship to prior work (MCP-UI, OpenAI Apps SDK)
    - Decision tree for MCP server developers (when to use Apps vs traditional tools)
    - 6 resource links (spec, SDK, blogs, VS Code announcement)
  - **guide/ultimate-guide.md:6509**: New section "MCP Evolution: Apps Extension" (~90 lines)
    - Context gap problem (before/after comparison)
    - What are MCP Apps (4 interface types: dashboards, wizards, viewers, monitors)
    - Available interactive tools table (9 tools with capabilities)
    - Platform support matrix with access instructions
    - CLI relevance (indirect benefits + hybrid workflow example)
    - Technical foundation (co-authoring, SDK, "build once deploy everywhere")
    - Cross-reference to architecture.md for deep dive
    - 3 resource links (MCP blog, Claude blog, spec)
  - **guide/ultimate-guide.md:7522**: Table update "Plugin vs. MCP Server"
    - Added "Interactive UI" row: Plugin (No) | MCP Server (Yes via MCP Apps)
    - Extended rule of thumb: MCP Apps = "What Claude can show"
    - Note clarifying CLI relevance and cross-reference to 8.1
  - **machine-readable/reference.yaml**: 8 new entries
    - mcp_apps_architecture, mcp_apps_evolution (line references)
    - mcp_apps_spec, mcp_apps_blog_mcp, mcp_apps_blog_claude, mcp_apps_sdk (external links)
    - mcp_apps_announcement_date: "2026-01-26"
    - mcp_apps_cli_relevance: "Indirect (ecosystem understanding, MCP server dev, hybrid workflows)"
  - **docs/resource-evaluations/mcp-apps-announcement.md**: New evaluation (159 lines)
    - Score: 4/5 (High Value - Integrate within 1 week)
    - 4 criteria evaluated (Relevance: 4/5, Reliability: 5/5, Applicability: 3/5, Completeness: 4/5)
    - Technical review challenge (2/5 initial → 4/5 revised after ecosystem analysis)
    - Fact-check with Perplexity (9 claims verified)
    - Decision justification and integration tracking
  - **Total documentation**: ~240 lines across 3 guide files
  - **Resources evaluated**:
    - https://blog.modelcontextprotocol.io/posts/2026-01-26-mcp-apps/
    - https://claude.com/blog/interactive-tools-in-claude
  - **Key facts verified**:
    - First official MCP extension (co-authored OpenAI + Anthropic + MCP-UI creators)
    - SDK stable 2026-01-26
    - 9 interactive tools at launch (Asana, Slack, Figma, Amplitude, Box, Canva, Clay, Hex, monday.com)
    - Platform support: Claude Desktop (claude.ai/directory, Pro/Max/Team/Enterprise), VS Code Insiders, ChatGPT rolling out, Goose
    - Claude Code CLI: Not applicable (text-only terminal, no iframe rendering)
    - Indirect CLI benefits: Ecosystem understanding, MCP server development option, hybrid Desktop→CLI workflows
- **Migration Scripts for v2.1.19 Breaking Change** (`examples/scripts/`)
  - `migrate-arguments-syntax.sh`: Bash migration script for macOS/Linux users
  - `migrate-arguments-syntax.ps1`: PowerShell migration script for Windows users
  - Automated detection and conversion of `$ARGUMENTS.0` → `$ARGUMENTS[0]` in custom commands
  - Dry-run mode with preview, automatic backups, safe batch processing

### Changed

- **Updated $ARGUMENTS Syntax Documentation** (Claude Code v2.1.19 breaking change)
  - `guide/ultimate-guide.md` (7 occurrences): Updated all custom command examples to use bracket syntax `$ARGUMENTS[0]` or shorthand `$0`, `$1`
  - Added migration note in § 6.2 Variable Interpolation explaining breaking change and migration path
  - `guide/cheatsheet.md`: Updated command template to show new syntax
  - All examples now demonstrate both bracket notation and shorthand alternatives

## [3.14.0] - 2026-01-26

### Added

- **NotebookLM MCP Integration Documentation** (`guide/ecosystem/ai-ecosystem.md`, `guide/ultimate-guide.md`)
  - **§ 4.1 NotebookLM MCP Integration** (~240 lines): Complete installation and usage guide
    - Detailed tool breakdown table: 16 tools across 3 profiles (minimal/standard/full)
    - Multi-account authentication workflow (authuser parameter for secondary Google accounts)
    - Share links library building pattern (isolated Chrome profile, no auto-sync)
    - Query notebooks with persistent conversation context (session_id)
    - Comparison table: MCP integration vs Web UI
    - Troubleshooting guide and example onboarding workflow
  - **§ 4.2 Advanced Features (Full Profile)** (~110 lines)
    - `remove_notebook`: Clean up library, fix duplicates
    - `re_auth`: Switch Google accounts without full cleanup
    - `cleanup_data`: Complete MCP reset with preserve_library option
    - Manual browser control: state inspection, actions, element waiting
  - **§ 4.3 Browser Options** (~70 lines)
    - Complete options reference: headless, timeout, viewport, stealth mode
    - Stealth mode configuration: typing speed (160-240 WPM), random delays, mouse movements
    - Usage examples: debug visually, custom timeouts, disable stealth for speed
  - **§ 4.4 Session Management** (~60 lines)
    - Session lifecycle: automatic creation, 15min timeout, 10 max concurrent
    - Manual session control: resume specific sessions, force new sessions
    - List active sessions with message counts and age
  - **§ 4.5 Library Management Best Practices** (~90 lines)
    - Naming conventions and topics strategy (specific vs broad)
    - Metadata refinement workflow: add → use → refine → archive
    - Search and discovery patterns (keyword search, smart selection)
    - Notebook lifecycle management
  - **guide/ultimate-guide.md**: Updated Complementary Tools table with "MCP integration" mention
  - **Total**: ~630 lines of comprehensive MCP documentation covering all 16 tools
- **Resource Evaluations Public Documentation** (`docs/resource-evaluations/`)
  - New tracked directory with 14 community resource evaluations (gsd, worktrunk, boris-cowork-video, astgrep, etc.)
  - Standardized filenames (removed date prefixes for stable linking)
  - Comprehensive methodology documentation with scoring grid (1-5 scale)
  - Index table with all evaluations, scores, and integration decisions
  - Working documents (prompts, private audits) remain in `claudedocs/` (gitignored)
  - New workflow section in CLAUDE.md documenting evaluation process
  - Transparency: Contributors can now see why resources were integrated/rejected
- **Task Management Workflow** (`guide/workflows/task-management.md`)
  - Comprehensive 775-line guide for Claude Code's task management system
  - Complete API reference: TaskCreate, TaskUpdate, TaskGet, TaskList, TaskDelete
  - 5 practical workflows: startup → feature work → bug fixing → code review → cleanup
  - Best practices: when to use tasks, granularity guidelines, status lifecycle
  - Anti-patterns section: over-tasking, status confusion, orphaned tasks
  - Integration with other workflows (TDD, Plan-Driven, GSD)
  - Quick reference added to cheatsheet
- **Ultimate Guide Task Management Integration** (`guide/ultimate-guide.md:10786-10930`)
  - New §9.18 "Task Management System" section (145 lines)
  - Core concepts, tool reference, practical patterns
  - Links to full workflow guide for details
- **Appendix C: Resource Evaluation Process** (`guide/ultimate-guide.md:15034`)
  - New appendix section documenting systematic evaluation methodology
  - 5-point scoring system (Critical → Low) with decision criteria and timelines
  - List of 14 documented assessments organized by categories (methodologies, tools, content, research)
  - Transparency explanation: why resources are integrated (3+), mentioned (2), or rejected (1)
  - Links to full methodology in `docs/resource-evaluations/README.md`
  - Browse all evaluations link to `docs/resource-evaluations/` directory

### Changed

- **guide/core/methodologies.md:55**: Corrected GSD evaluation link
  - Old: `../claudedocs/resource-evaluations/gsd-evaluation.md` (private)
  - New: `../docs/resource-evaluations/gsd-evaluation.md` (public)
- **machine-readable/reference.yaml**: Added resource evaluations metadata
  - New section: resource_evaluations_directory, count (14), methodology link
  - Added references: appendix (line 15034), README section (line 278)
  - Corrected gsd_evaluation path from private claudedocs to public docs
- **README.md**: Updated documentation metrics for accuracy and landing site synchronization
  - Guide length: ~10K → ~15K lines (actual: 15,053 lines)
  - Reading time: ~3 hours → ~4 hours (reflects actual guide size)
  - Security hooks: 15+ → 18 (precise count)
  - Templates count: maintained at 86 (consistent with check-landing-sync.sh logic)
  - Repository Structure section: updated ultimate-guide.md from "~13,425 lines" to "~15K lines"
  - Added **Resource Evaluations** section (14 assessments) with methodology links
  - All changes verified with `./scripts/check-landing-sync.sh` for full synchronization

## [3.13.0] - 2026-01-26

### Added

- **Boris Cherny mental models integration** (from YouTube interview analysis)
  - **CLAUDE.md as Compounding Memory** (`guide/ultimate-guide.md:3254`)
    - New philosophy section: "You should never have to correct Claude twice for the same mistake"
    - 4-step cycle: error → rule → read → never repeated
    - Compounding effect visualization (5 → 20 → 50 rules over time)
    - Boris's practical example: 2.5K tokens grown over months
    - Anti-pattern warning: no preemptive documentation
    - Mental model shift: configuration file → organizational learning system
  - **Plan-First Discipline** (`guide/core/methodologies.md:61`)
    - New "Foundational Discipline" section (between Tier 1 and Tier 2)
    - Core principle: "Once the plan is good, the code is good" (Boris quote)
    - Decision table: when to plan first vs when to skip
    - 3-phase workflow: exploration → validation → execution
    - Benefits quantified vs "just start coding"
    - CLAUDE.md integration example for team planning policy
  - **Verification Loops architectural pattern** (`guide/core/methodologies.md:214`)
    - Extended beyond TDD to general architectural principle
    - 8 verification domains table (frontend, backend, types, style, performance, accessibility, security, UX)
    - Boris quote: "An agent that can 'see' what it has done produces better results"
    - Implementation patterns: hooks, browser extensions, test watchers, CI/CD gates
    - Anti-pattern: blind iteration without feedback mechanism
  - **Boris direct quotes in case study** (`guide/ultimate-guide.md:10743`)
    - 4 key insights: multi-clauding, CLAUDE.md compounding, plan-first, verification loops
    - Opus 4.5 ROI explanation: higher per-token cost but fewer corrections = net savings
    - Supervision model description: "tending to multiple agents" vs sequential execution
    - YouTube source citation added alongside InfoQ article
  - Resource evaluation saved in `claudedocs/resource-evaluations/boris-cowork-video-eval.md` (score: 3/5 - relevant, moderate improvement)
  - Source: [YouTube - I got a private lesson on Claude Cowork & Claude Code](https://www.youtube.com/watch?v=DW4a1Cm8nG4)
- **Advanced Worktree Tooling section** (`guide/ultimate-guide.md:10748`)
  - New section "Advanced Tooling for Worktree Management (Optional)" in §9.17 Multi-Instance Workflows
  - Pattern validation: 3 independent teams created worktree wrappers (incident.io, GitHub #1052, Worktrunk)
  - **"Do I Need Worktrunk?" self-assessment** (`guide/ultimate-guide.md:10762`)
    - 3 quick questions (volume, multi-instance, team context)
    - Decision matrix: 4 user profiles (Beginner, Casual, Power user, Boris scale)
    - Quick alias alternative for "Casual user" profile (2 min setup, -79% typing vs vanilla git)
    - Bottom line guidance: "80% of readers should start with vanilla git or alias"
    - Prevents tool adoption without need assessment (YAGNI principle applied to tooling)
  - Benchmark table: Worktrunk vs vanilla git vs custom wrappers (6 operations compared)
  - Option 1: Worktrunk CLI (1.6K stars, Rust, multi-platform, CI/LLM integration, project hooks)
  - Option 2: DIY custom wrappers (bash/fish examples from production teams)
  - Progressive recommendation: Learn fundamentals → Add wrapper → Scale to multi-instance
  - Philosophy: "Tools amplify knowledge. Master git patterns before adding convenience layers."
  - ROI evidence: incident.io measured 18% improvement (30s) on API generation time with worktree workflow
  - Fact-checked analysis: 4 sources analyzed (Worktrunk GitHub, incident.io blog, Anthropic best practices, GitHub issue #1052)
  - Resource evaluation saved in `claudedocs/resource-evaluations/worktrunk-evaluation.md` (score: 3/5 - relevant, useful complement)
  - Total additions: ~260 lines (121 original + 139 self-assessment)
- **machine-readable/reference.yaml**: Added `advanced_worktree_tooling: 10748`, `worktree_tooling_self_assessment: 10762`, and updated line references for all sections after worktrees
- **GSD (Get Shit Done) methodology mention** (`guide/core/methodologies.md:47-55`)
  - Added to Tier 1: Strategic Orchestration alongside BMAD
  - Meta-prompting 6-phase workflow (Initialize → Discuss → Plan → Execute → Verify → Complete)
  - Fresh 200k-token contexts per task to avoid context rot
  - Note: Core concepts overlap with existing patterns (Ralph Loop, Gas Town, BMAD)
  - Resource evaluation saved in `claudedocs/resource-evaluations/gsd-evaluation.md` (score: 2/5 - marginal/redundant)
  - Source: https://github.com/glittercowboy/get-shit-done (7.5k stars, created Dec 2025)
- **ClawdBot FAQ enrichment** (`guide/ultimate-guide.md:14375,14385`)
  - Added community adoption analysis link (5,600+ social mentions on X/Twitter)
  - Updated final note with adoption metrics and real-world use case examples
  - Link to comprehensive community analysis: https://docs.google.com/document/d/1Mz4xt1yAqb2gDxjr0Vs_YOu9EeO-6JYQMSx4WWI8KUA/preview
  - Resource evaluation saved in `claudedocs/resource-evaluations/2026-01-25-clawdbot-twitter-analysis.md` (score: 2/5 - marginal, partial integration)
- **MCP architecture visual diagram** (`guide/core/architecture.md:513`, SVG)
  - 7-layer security model showing LLM/MCP Server/Tools separation
  - Visual representation of "No Data Access" (LLM layer) and "Hidden From AI" (Real Systems layer)
  - Beginner-friendly introduction to MCP architecture with color-coded security boundaries
  - Design inspired by Dinesh Kumar's LinkedIn visualization, recreated as original work under Apache-2.0
  - Includes workflow diagram (5 steps: User Asks → LLM Thinks → MCP Controls → Tools Execute → Safe Result)
  - Golden rule banner: "LLM Thinks → MCP Controls → Tools Execute → Data Locked"
- **machine-readable/reference.yaml**: Added `architecture_mcp_visual` (SVG diagram reference)

### Changed

- **README.md**: Updated templates count from 83 to 86 (badge and description text)
  - Reflects addition of 3 new evaluation documents in `claudedocs/resource-evaluations/`
  - Actual template count: 86 files in `examples/` directory

## [3.12.1] - 2026-01-25

### Added

- **Bridge Script: Claude Code → doobidoo → LM Studio** (`examples/scripts/bridge.py`)
  - Python CLI for executing Claude Code plans locally via LM Studio
  - Cost optimization: Plan with Opus (~$0.50-2), execute free locally (80-90% savings)
  - Architecture: Claude Code stores plans in doobidoo SQLite → bridge reads → LM Studio executes
  - 5 components: DoobidooReader, LMStudioClient, Validator, StepExecutor, PlanExecutor
  - JSON Schema for plan validation (`examples/scripts/bridge-plan-schema.json`)
  - 4 validation types: json, syntax_check, contains_keys, non_empty
  - Failure handling: retry_with_context, skip, halt strategies
  - CLI: `--health`, `--list`, `--plan ID`, `-v` verbose mode
  - Documentation in ultimate-guide.md §11.2 "Local Execution Bridge" (line 14079)
- **examples/scripts/README.md**: New documentation for all utility scripts
- **machine-readable/reference.yaml**: Added bridge_script, bridge_schema, bridge_guide entries

### Changed

- **.gitignore**: Added `__pycache__/` and `*.pyc` for Python artifacts

## [3.12.0] - 2026-01-25

### Added

- **External orchestration systems documentation** (`guide/ecosystem/ai-ecosystem.md:808`)
  - Gas Town (Steve Yegge): Multi-agent workspace manager using Claude Code instances
  - multiclaude (dlorenc): Self-hosted multi-agent Claude Code spawner (383 stars, active development)
  - agent-chat (Justin Abrahms): Real-time monitoring UI for orchestrator communications (v0.2.0)
  - Architecture patterns for transposing monitoring to native Claude Code workflows
  - Security and cost warnings for experimental orchestration systems
  - Decision matrix: when to use orchestrators vs single Claude Code sessions
- **machine-readable/reference.yaml**: Added `external_orchestrators` section with structured data
  - Programmatic access to Gas Town, multiclaude, agent-chat metadata
  - Links to guide sections, GitHub repos, author attribution
- **guide/ops/observability.md:117**: Cross-reference to multi-agent orchestration monitoring
  - Architecture pattern for custom implementations (hooks + SQLite + SSE)
  - Comparison table: external orchestrator monitoring vs native Claude Code monitoring

## [3.11.7] - 2026-01-25

### Added

- **Vibe Coding: Context Overload Anti-Pattern** (`guide/ultimate-guide.md:8746`)
  - New subsection in §9.8 Vibe Coding documenting the "context overload" anti-pattern
  - Identifies symptoms: big-bang context dumps, 5K+ line prompts, performance degradation
  - Phased context strategy: Exploration (plan mode) → Implementation (focused) → Fresh start (handoffs)
  - Unifies 3 existing patterns (plan mode, fresh context, session handoffs) under explicit framework
  - Attribution to Jens Rusitschka ("Vibe Coding, Level 2", Jan 2026)
  - Practical workflow examples with bash commands
  - Cross-references to §2.2 (Fresh Context Pattern, line 1525), §2.3 (Plan Mode, line 2100)
  - Total additions: ~60 lines
- **machine-readable/reference.yaml**: Added `vibe_coding_context_overload`, `vibe_coding_context_overload_source`, `vibe_coding_phased_strategy`
- **guide/roles/learning-with-ai.md:96**: Added cross-reference from "Vibe Coding Trap" to new anti-pattern section

- **Product Manager FAQ entry** (`guide/ultimate-guide.md:14335`)
  - Minimal FAQ entry (28 lines) addressing PM workflows with Claude Code
  - Distinction between code-adjacent PMs (technical validation) and non-coding PMs (strategy/research)
  - Tool stack example from Stilyan Mitrev (Head of Product, StableLab): Granola, Wispr Flow, ChatPRD, v0
  - Reality check: "emerging area with limited community validation" (1 practitioner report, tool not adopted long-term)
  - Guidance: CLI appropriate for technical PMs, Claude Desktop better for non-technical workflows
  - Cross-references: AI Ecosystem Guide, Cowork Guide, Design-to-Code Workflow
  - Source: [LinkedIn article (Jan 23, 2026)](https://www.linkedin.com/pulse/how-i-currently-ai-product-manager-stilyan-mitrev-ycvvf/)
  - Decision: Minimal integration (proportional to source), invite community contribution
  - Reference YAML: Added `faq_product_managers: 14335`

- **MCP architecture visual diagram** (`guide/core/architecture.md:513`, SVG)
  - 7-layer security model showing LLM/MCP Server/Tools separation
  - Visual representation of "No Data Access" (LLM layer) and "Hidden From AI" (Real Systems layer)
  - Beginner-friendly introduction to MCP architecture with color-coded security boundaries
  - Design inspired by Dinesh Kumar's LinkedIn visualization, recreated as original work under Apache-2.0
  - Includes workflow diagram (5 steps: User Asks → LLM Thinks → MCP Controls → Tools Execute → Safe Result)
  - Golden rule banner: "LLM Thinks → MCP Controls → Tools Execute → Data Locked"
- **External orchestration systems documentation** (`guide/ecosystem/ai-ecosystem.md:808`)
  - Gas Town (Steve Yegge): Multi-agent workspace manager using Claude Code instances
  - multiclaude (dlorenc): Self-hosted multi-agent Claude Code spawner
  - agent-chat (Justin Abrahms): Real-time monitoring UI for orchestrator communications
  - Architecture patterns for transposing monitoring to native Claude Code workflows
  - Security and cost warnings for experimental orchestration systems
- **machine-readable/reference.yaml**: Added `external_orchestrators` section with Gas Town, multiclaude, agent-chat
- **machine-readable/reference.yaml**: Added `architecture_mcp_visual` (SVG diagram reference)
- **guide/ops/observability.md**: Cross-reference to multi-agent orchestration monitoring

## [3.11.7] - 2026-01-25

### Added

- **ClawdBot vs Claude Code FAQ** (`guide/ultimate-guide.md:14263`)
  - New Appendix B: FAQ section addressing community confusion between ClawdBot and Claude Code
  - Comprehensive comparison table (9 dimensions): interface, audience, use cases, pricing, architecture
  - Decision tree: when to choose each tool, when to use both together
  - Early warning note in "Before You Start" section (line 33) to alert readers immediately
  - Community misconceptions addressed: different architectures, complementary not competitive
  - Resources: ClawdBot website, GitHub repo, setup guides
  - Context: Jan 2026 buzz on X/Reddit created confusion ("dominated X timeline over 1-2 months")
  - Related: ClawdBot is self-hosted chatbot for messaging apps (personal automation, smart home); Claude Code is CLI for developers (terminal/IDE, code generation)
  - Total additions: +76 lines in guide, +3 lines in reference.yaml

- **Architecture Diagrams as Context (Advanced Pattern)** (`guide/ecosystem/ai-ecosystem.md:1379`)
  - Pattern documentation for using architecture diagrams in OOP codebases
  - MCP tools reference: Archy MCP, Mermaid MCP, Blueprint MCP (ArcadeAI)
  - ACM 2024 research validation for LLM OOP limitations
  - Recommended workflow: Serena → Archy MCP → Manual inline Mermaid
  - Use cases: OOP codebases >20 modules, Java/Spring projects with deep polymorphism
  - Source: [LinkedIn discussion (Jan 2026)](https://www.linkedin.com/posts/tigraff_uml-claude-wibecoding-activity-7420595633826258944-gGO5)
  - Evaluation report: `claudedocs/resource-evaluations/uml-oop-diagrams-eval.md`

- **AI Traceability & Attribution Guide** (`guide/ops/ai-traceability.md`)
  - Comprehensive documentation on AI code attribution and disclosure (~500 lines)
  - LLVM "Human-in-the-Loop" policy (January 2026): `Assisted-by:` trailer standard
  - Ghostty mandatory disclosure pattern (August 2025)
  - Fedora contributor accountability framework (RFC 2119 language)
  - git-ai tool: checkpoint tracking, AI Code Halflife metric (3.33 years median)
  - PromptPwnd security vulnerability documentation
  - Four-level disclosure spectrum: None → Minimal → Standard → Full
  - Policy comparison matrix across LLVM, Ghostty, Fedora
  - Implementation guides for solo dev, team, and enterprise contexts
  - Source: [Vibe coding needs git blame](https://quesma.com/blog/vibe-code-git-blame/) (Piotr Migdał)

- **AI Disclosure Templates** (`examples/config/`)
  - `CONTRIBUTING-ai-disclosure.md`: Section template for CONTRIBUTING.md
  - `PULL_REQUEST_TEMPLATE-ai.md`: PR template with AI disclosure checkboxes
  - Based on Ghostty, LLVM, and Fedora policies

- **Cross-references added**
  - `guide/ultimate-guide.md:9256`: Link to AI Traceability Guide after Co-Authored-By section
  - `guide/roles/learning-with-ai.md:85`: Related note after Vibe Coding Trap
  - `guide/security/security-hardening.md:476`: PromptPwnd reference in See Also
  - `guide/README.md`: New entry in contents table

- **Reference YAML expansion** (`machine-readable/reference.yaml`)
  - 14 new entries for AI traceability topics
  - Template locations for disclosure files

- **Architecture Diagrams as Context (Advanced Pattern)** (`guide/ecosystem/ai-ecosystem.md:1379`)
  - Pattern documentation for using architecture diagrams in OOP codebases
  - MCP tools reference: Archy MCP, Mermaid MCP, Blueprint MCP (ArcadeAI)
  - ACM 2024 research validation for LLM OOP limitations
  - Recommended workflow: Serena → Archy MCP → Manual inline Mermaid
  - Use cases: OOP codebases >20 modules, Java/Spring projects with deep polymorphism
  - Source: [LinkedIn discussion (Jan 2026)](https://www.linkedin.com/posts/tigraff_uml-claude-wibecoding-activity-7420595633826258944-gGO5)
  - Evaluation report: `claudedocs/resource-evaluations/uml-oop-diagrams-eval.md`

## [3.11.6] - 2026-01-24

### Added

- **Plugin System Section 8.5 major update** (`guide/ultimate-guide.md:7092-7280`)
  - **CRITICAL FIX**: Corrected plugin structure (`.claude-plugin/plugin.json` not root `plugin.json`)
  - Added `.mcp.json`, `.lsp.json`, `hooks/hooks.json` to directory structure
  - Added skill namespacing documentation (`/plugin-name:skill`)
  - Added warning about common mistake (components outside `.claude-plugin/`)
  - Added link to official Anthropic docs: code.claude.com/docs/en/plugins
  - Source: [Anthropic Official Plugin Docs](https://code.claude.com/docs/en/plugins)

- **Community Marketplaces subsection** (`guide/ultimate-guide.md:7246`)
  - **wshobson/agents**: 67 plugins, 99 agents, 107 skills (verified Jan 2026)
  - **claude-plugins.dev**: 11,989 plugins, 63,065 skills indexed
  - **claudemarketplaces.com**: Auto-scan GitHub for marketplaces
  - Popular plugins with install counts: Context7 (~72k), Ralph Wiggum (~57k), Figma MCP (~18k), Linear MCP (~9.5k)
  - Curated lists: awesome-claude-code (20k+ stars)
  - Installation examples for wshobson/agents
  - Sources: [wshobson/agents](https://github.com/wshobson/agents), [claude-plugins.dev](https://claude-plugins.dev), [Firecrawl analysis](https://www.firecrawl.dev/blog/best-claude-code-plugins)

- **Plugin ecosystem YAML index expansion** (`machine-readable/reference.yaml:137-164`)
  - `plugins_official_docs`: Official Anthropic plugin documentation URL
  - `plugins_official_reference`: Plugin reference docs URL
  - `plugins_official_marketplaces`: Marketplace docs URL
  - `plugins_wshobson_agents`: Stats and URL (67/99/107)
  - `plugins_registry_claude_plugins_dev`: Registry stats (11,989/63,065)
  - `plugins_registry_claudemarketplaces`: Auto-scan description
  - `plugins_popular`: Top 4 plugins with install counts
  - `plugins_awesome_list`: 20k+ stars curated list
  - `plugins_community_marketplaces: 7246`: New section line number

- **Resource evaluation: Nick Jensen plugins article** (`claudedocs/resource-evaluations/2026-01-24-nick-jensen-plugins.md`)
  - Initial score 3/5 → Challenge 4/5 → Perplexity verification 2/5 (Marginal)
  - Rejected as direct source: outdated stats (63/85/47 vs 67/99/107), unverified onboarding claim
  - Perplexity research revealed better primary sources (Anthropic docs, wshobson README, claude-plugins.dev)
  - Lesson: Blog posts often cite outdated data; verify against primary sources
  - Decision: Integrate primary sources instead of article

- **First plugin example: SE-CoVe (Chain-of-Verification)** (`examples/plugins/se-cove.md`)
  - Software Engineering adaptation of Meta's Chain-of-Verification methodology for Claude Code
  - Research foundation: Meta AI paper (arXiv:2309.11495), ACL 2024 Findings
  - 5-stage pipeline: Baseline → Planner → Executor → Synthesizer → Output
  - Critical innovation: Verifier operates without draft code access (prevents confirmation bias)
  - Performance metrics from research (Llama 65B): +23-112% accuracy depending on task, ~2x token cost
  - When to use: Critical code review, architectural decisions, complex debugging (when correctness > speed)
  - When NOT to use: Trivial changes, tight token budgets, exploratory coding
  - Installation via `/plugin marketplace add vertti/se-cove-claude-plugin` then `/plugin install chain-of-verification`
  - Limitations documented: Reduces hallucinations (not eliminates), model-specific (Llama 65B tested), task-dependent performance
  - Plugin System gap filled: First concrete example for Section 8.5 (previously theoretical docs only)
  - Sources: [GitHub repo](https://github.com/vertti/se-cove-claude-plugin) v1.1.1, [arXiv paper](https://arxiv.org/abs/2309.11495), [ACL Anthology](https://aclanthology.org/2024.findings-acl.212/)

- **Plugin system YAML index entries** (`machine-readable/reference.yaml:124-132`)
  - `plugins_system: 6863` (existing section reference)
  - `plugins_commands: 6876` (command table reference)
  - `plugins_marketplace: 6890` (marketplace management reference)
  - `plugins_recommended: "examples/plugins/"` (new directory)
  - `plugins_se_cove: "examples/plugins/se-cove.md"`
  - `chain_of_verification: "guide/core/methodologies.md:165"` (methodology reference)
  - `chain_of_verification_paper: "https://arxiv.org/abs/2309.11495"`
  - `chain_of_verification_acl: "https://aclanthology.org/2024.findings-acl.212/"`

- **Resource evaluation documentation** (`claudedocs/resource-evaluations/2026-01-24-se-cove-plugin.md`)
  - Complete evaluation workflow: Fetch → Gap Analysis → Technical Writer Challenge → Fact-Check (Perplexity) → Documentation
  - Fact-check findings: Marketing claim "28% improvement" contextualized (task-specific: 23-112%, omitted 2x cost and -26% output)
  - Curation policy established: Academic validation + Claims fact-checked + Trade-offs disclosed
  - Approach B (Neutral Academic) validated: Cite paper metrics, not marketing claims
  - Template for future plugin evaluations (reusable workflow)
  - Tools used: WebFetch (LinkedIn, GitHub, arXiv), Perplexity Pro (paper verification), Task (technical-writer challenge)
  - Confidence assessment: High (methodology), Medium (generalization), Low (marketing accuracy)

- **Claude Reflect System documentation** (`guide/ultimate-guide.md:5161`, ~135 lines)
  - New subsection: "Automatic Skill Improvement: Claude Reflect System"
  - Repository: [haddock-development/claude-reflect-system](https://github.com/haddock-development/claude-reflect-system)
  - Marketplace: [Agent Skills Index](https://agent-skills.md/skills/haddock-development/claude-reflect-system/reflect)
  - Pattern documented: Self-improving skills via feedback analysis (complementary to Claudeception)
  - Two modes: Manual (`/reflect [skill-name]`) + Automatic (Stop hook)
  - 8-step workflow: Monitor → Parse → Classify → Propose → Review → Backup → Apply → Commit
  - Safety features table: User review gate, Git backups, syntax validation, confidence levels, locking
  - Security warnings table: 4 risks (Feedback Poisoning, Memory Poisoning, Prompt Injection, Skill Bloat) with mitigations
  - Installation instructions: Git clone + Stop hook configuration (Bash/PowerShell)
  - Use case example: Terraform validation skill evolution
  - Activation commands: `/reflect-on`, `/reflect-off`, `/reflect [skill]`, `/reflect status`
  - Comparison table: Claudeception (generation) vs Reflect System (improvement)
  - Recommended combined workflow: Bootstrap → Iterate → Refine → Curate
  - Timeline example: 8-week skill evolution (80% → 95% accuracy)
  - Resources: GitHub, Agent Skills, YouTube tutorial, Anthropic Memory Cookbook
  - Academic sources: Anthropic Memory Cookbook, adversarial attacks research

- **Skill lifecycle YAML index entries** (`machine-readable/reference.yaml:113-123`)
  - `skill_lifecycle: 5118` (section start)
  - `claude_reflect_system: 5161` (main section)
  - `claude_reflect_system_repo: https://github.com/haddock-development/claude-reflect-system`
  - `claude_reflect_system_agent_skills: https://agent-skills.md/skills/...`
  - `skill_improvement_pattern: 5161`
  - `skill_improvement_how_it_works: 5169`
  - `skill_improvement_safety: 5188`
  - `skill_improvement_security_warnings: 5237`
  - `skill_improvement_comparison: 5263` (Claudeception vs Reflect)
  - `skill_improvement_workflow: 5275` (combined workflow)

- **Resource evaluation: Self-improve skill pattern** (`claudedocs/resource-evaluations/2026-01-24_self-improve-skill.md`)
  - Investigation workflow: Repository search (failed) → Pattern validation via Perplexity (success)
  - Findings: Announced plugin unavailable, but pattern validated by Claude Reflect System
  - Score: 2/5 (announced resource) → REJECT with REDIRECT to proven alternative
  - Decision rationale: Availability > Announcement, Verification > Claims, Alternatives > Gaps
  - Tools used: GitHub search (failed), Perplexity Pro (found alternative), WebSearch (baseline)
  - Curation policy reinforced: Only document publicly accessible resources with verified functionality
  - Research foundation: Anthropic Memory Cookbook, Agent Skills Index
  - Evaluation status: COMPLETE with HIGH confidence

### Changed

- **README.md**: Templates count 82 → 83 (added SE-CoVe plugin)
  - Badge updated: `Templates-82` → `Templates-83`
  - "Examples Library" section updated (line 228)
  - Ecosystem table updated (line 377)
  - New **Plugins** subsection added after Skills (line 238)

## [3.11.5] - 2026-01-23

### Added

- **skills.sh marketplace documentation** (`guide/ultimate-guide.md:5172`, `guide/ecosystem/ai-ecosystem.md:1284`)
  - New subsection in Section 5.5: "Skills Marketplace: skills.sh"
  - Vercel Labs project (launched Jan 21, 2026): centralized skill discovery + one-command install
  - 200+ skills, leaderboard with 35K+ installs (vercel-react-best-practices top skill)
  - Format 100% compatible with `.claude/skills/` structure
  - Installation: `npx add-skill <owner/repo>` → copies to `~/.claude/skills/`
  - Supported agents: 20+ (Claude Code, Cursor, GitHub Copilot, Windsurf, etc.)
  - Top skills by category: Frontend (vercel-react, web-design), Database (supabase-postgres), Auth (better-auth), Testing (TDD)
  - Status documented: Community project (Vercel Labs, not official Anthropic), early stage
  - Trade-offs: Centralized discovery vs GitHub distribution, multi-agent focus vs Claude Code specific
  - Cross-reference added to `guide/ecosystem/ai-ecosystem.md` Section 11.3 (Skills Distribution Platforms)
  - Complementary resources table updated in README.md
  - YAML index entries:
    - `skills_marketplace: 5172`
    - `skills_marketplace_url: https://skills.sh/`
    - `skills_marketplace_github: vercel-labs/agent-skills`
    - `skills_marketplace_install: npx add-skill <owner/repo>`
    - `skills_marketplace_top_skills` (5 entries with install counts)
    - `skills_marketplace_status: Community (Vercel Labs), launched Jan 21, 2026`

## [3.11.4] - 2026-01-23

### Added

- **Matteo Collina practitioner insight** (`guide/ecosystem/ai-ecosystem.md:1243`)
  - Node.js TSC Chair's perspective on AI-assisted development
  - "Bottleneck shift" thesis: judgment becomes the limiting factor, not typing speed
  - Key quote: "The human in the loop isn't a limitation. It's the point."
  - Context: Response to Arnaldi's "The Death of Software Development" (January 2026)
  - Data points: Review time +91% (CodeRabbit), 96% devs don't trust AI code (Sonar 2026)
  - Cross-reference added to `guide/roles/learning-with-ai.md` Practitioner Perspectives
  - YAML index entries: `practitioner_matteo_collina`, `practitioner_collina_source`

- **Claude Code releases tracking update** (`machine-readable/claude-code-releases.yaml`, `guide/core/claude-code-releases.md`)
  - Added v2.1.17: Fix for crashes on processors without AVX instruction support
  - Added v2.1.16: ⭐ New task management system with dependency tracking, VSCode native plugin management, OAuth remote session browsing
  - Added v2.1.15: npm installations deprecated (migrate to native installer), React Compiler performance improvements
  - New milestone: v2.1.16 (task management system)
  - New breaking change: npm installations deprecated

### Changed

- Updated landing site releases section with 3 new versions (v2.1.15-v2.1.17)
- Fixed landing release descriptions to match official CHANGELOG (v2.1.12, v2.1.11 corrections)
- Release count: 39 → 42

## [3.11.3] - 2026-01-23

### Added

- **Verification Loops pattern** (`guide/core/methodologies.md:145`)
  - Formalized pattern for autonomous iteration with tests as termination condition
  - Official Anthropic guidance: "Tell Claude to keep going until all tests pass"
  - Implementation options: Stop hooks, multi-Claude verification, explicit "DONE" markers

- **Eval Harness documentation** (`guide/core/methodologies.md:161`)
  - Definition: Infrastructure running evaluations end-to-end
  - Link to Anthropic source: "Demystifying Evals for AI Agents"

- **everything-claude-code ecosystem entry** (`machine-readable/reference.yaml`)
  - Added affaan-m/everything-claude-code (31.9k stars as of 2026-01-27, created 2026-01-18)
  - Author: Affaan Mustafa (Anthropic hackathon winner - Zenith project)
  - Unique patterns: hookify (conversational hooks), pass@k metrics, sandboxed subagents, strategic compaction
  - Plugin ecosystem: One-command installation, skill creator from git history
  - Comprehensive evaluation (Score 5/5): `docs/resource-evaluations/015-everything-claude-code-github-repo.md`
  - Caveats documented: hackathon win was indirect, Node.js hooks not officially recommended

- **deep_dive index entries** (`machine-readable/reference.yaml`)
  - `verification_loops`: guide/core/methodologies.md:145
  - `verification_loops_source`: Anthropic Best Practices link
  - `eval_harness`: guide/core/methodologies.md:161
  - `eval_harness_source`: Demystifying Evals link

- **Subscription Token Limits documentation** (`guide/ultimate-guide.md:1933-1995`)
  - Detailed token budgets by plan: Pro ~44K, Max 5x ~88-220K, Max 20x ~220K+ per 5-hour window
  - Opus/Sonnet consumption ratio (8-10×) explicitly documented
  - Clarification that "hours" = processing time, not direct token conversion
  - Link to `ccusage` community monitoring tool
  - Historical note on October 2025 undocumented limit reductions
  - **Sources**: Perplexity research (Jan 2026), Anthropic support docs, Reddit/GitHub community reports

- **Goose comparison section** (`guide/ecosystem/ai-ecosystem.md:1116-1204`)
  - New section "11.1 Goose: Open-Source Alternative (Block)"
  - Technical comparison table: Claude Code vs Goose on 7 criteria
  - GitHub stats: 15,400+ stars, 350+ contributors, Apache 2.0 license
  - Use cases and trade-offs with honest advantages/limitations
  - Hardware requirements by LLM type (cloud vs local models)
  - Quick start installation commands
  - Updated Table of Contents

- **machine-readable/reference.yaml**: Additional entries
  - `subscription_token_budgets: 1948`
  - `subscription_opus_ratio: 1946`
  - `subscription_monitoring: 1985`
  - `ai_ecosystem_goose: "guide/ecosystem/ai-ecosystem.md:1116"`
  - `ai_ecosystem_goose_comparison: "guide/ecosystem/ai-ecosystem.md:1132"`

- **Practitioner Insights section** (`guide/ecosystem/ai-ecosystem.md:1209-1241`)
  - New section "11.2 Practitioner Insights" for external validation
  - Dave Van Veen (PhD Stanford, Principal AI Scientist @ HOPPR)
  - Validates guide patterns: TDD, git worktrees, manual commits, planning phase
  - Academic credential: Co-author "Agentic Systems in Radiology" (ArXiv 2025)
  - Clarification: "English is the new programming language" attributed to Karpathy/Reddy, not Van Veen
  - Updated Table of Contents with new section

- **machine-readable/reference.yaml**: Practitioner insights entries
  - `practitioner_insights: "guide/ecosystem/ai-ecosystem.md:1209"`
  - `practitioner_dave_van_veen: "guide/ecosystem/ai-ecosystem.md:1213"`
  - `ecosystem.practitioner_insights.dave_van_veen` with full metadata

- **OCTO Technology reference** (`guide/roles/learning-with-ai.md:907`)
  - Added to "Practitioner Perspectives" section in Sources & Research
  - Article: "Le développement logiciel à l'ère des agents IA"
  - Key insights: pairs as minimal team unit (bus factor), bottleneck shifts to functional requirements
  - Caveat: managerial focus, useful context for team leads

### Changed

- **Subscription limits section** (`guide/ultimate-guide.md`) rewritten with concrete data
- **reference.yaml**: Updated line numbers for `subscription_limits` (1914 → 1933) and `ai_ecosystem_context_packing` (1114 → 1208)

### Research

- **Comprehensive fact-check** of everything-claude-code repository
  - Verified "Anthropic hackathon winner" claim (true for Zenith project, indirect for this repo)
  - Confirmed 16k+ stars growth in 5 days via GitCharts
  - Validated technical concepts (eval-harness, verification-loops) exist in Anthropic docs
  - Found "strategic-compact" term not in official sources (not adopted)
  - Confirmed Node.js hooks not recommended vs native shell

---

## [3.11.2] - 2026-01-22

### Added

- **Context Packing Tools section** (`guide/ecosystem/ai-ecosystem.md:1114`)
  - New section "12. Context Packing Tools" documenting gitingest, repo2txt usage patterns
  - Clarifies when to use external context extraction vs native Claude Code file access
  - Updated Table of Contents with sections 11 (AI Coding Agents Matrix) and 12
  - **machine-readable/reference.yaml**: Added `ai_ecosystem_context_packing` entry

- **Addy Osmani AI Coding Workflow reference** (`guide/core/methodologies.md:313`)
  - Added "My AI Coding Workflow in 2026" article to SDD & Spec-First sources
  - Validates spec-first, TDD, git checkpoints workflow patterns

- **MCP Tool Search documentation** (`guide/core/architecture.md`)
  - New section "MCP Tool Search (Lazy Loading)" with complete technical details
  - Explains how Claude Code uses Anthropic's Advanced Tool Use API feature (v2.1.7+)
  - Includes ASCII diagram of Tool Search flow
  - Documents 85% token reduction benchmark and accuracy improvements
  - Configuration guide for `ENABLE_TOOL_SEARCH=auto:N` syntax
  - Simon Willison quote on context pollution resolution
  - **Sources**: Anthropic Engineering blog, Scott Spence documentation, Perplexity verification
  - **machine-readable/reference.yaml**: Added `tool_search`, `tool_search_config`, `tool_search_deep_dive` entries

### Changed

- **Release notes enrichment** (`guide/core/claude-code-releases.md`)
  - v2.1.7: Added 85% token reduction stats, accuracy improvements, Anthropic blog link
  - v2.1.9: Added `auto:N` configuration examples and cross-reference to architecture.md

### Fixed

- **Template count**: Corrected from 83 to 82 (actual count in examples/)

---

## [3.11.1] - 2026-01-22

### Added

- **Agent Vibes TTS Integration** (`examples/integrations/agent-vibes/`)
  - **8 documentation files, 2,400+ lines**: Complete text-to-speech integration guide
  - **Integration guide** (`README.md`): Quick start with decision matrix, 30-second overview, architecture diagram, essential commands
  - **Installation guide** (`installation.md`): 18-minute step-by-step procedure across 5 phases (bash 5.x, dependencies, Agent Vibes, Piper TTS, French voices)
  - **Voice catalog** (`voice-catalog.md`): Detailed catalog of 15 voices (4 French models with 128 total speakers via multi-speaker models)
  - **Troubleshooting guide** (`troubleshooting.md`): Solutions for 7 common issues with diagnostic script
  - **Workflow** (`guide/workflows/tts-setup.md`): 18-minute guided workflow with decision scoring system and 5 checkpointed phases
  - **Custom hook example** (`examples/hooks/bash/tts-selective.sh`): Selective TTS activation (errors only) with pattern matching
  - **Project template** (`examples/claude-md/tts-enabled.md`): CLAUDE.md template for TTS-enabled projects with team guidelines
  - **Key features**:
    - Offline TTS with Piper (no cloud dependency)
    - French voice support (4 models: tom, siwis, upmc, mls-124speakers)
    - Mute hierarchy system (project override → project mute → global mute)
    - Provider auto-detection (macOS Say, Piper TTS)
    - Audio effects pipeline (reverb, echo, background music)
  - **Documentation**: Added section 5.1 "Text-to-Speech Tools" in `guide/ecosystem/ai-ecosystem.md` (80+ lines with tables, quick start, recommendations)

### Changed

- **Template count**: 71 → 83 (+12 templates including integration docs, hook, workflow, CLAUDE.md template)
- **README.md**: Updated badges (71→83), template counts (66→83, 74→83), version footer (3.11.0→3.11.1)
- **guide/README.md**: Added TTS workflow reference and ai-ecosystem.md section update
- **machine-readable/reference.yaml**: Added 8 TTS-related entries (tts_integration_guide, tts_installation, tts_voice_catalog, tts_troubleshooting, tts_workflow, tts_ai_ecosystem, tts_hook_example, tts_claude_md_template)
- **.gitignore**: Added audio file exclusions (*.wav, *.mp3, *.onnx)

### Context

- **Use case**: Add audible narration to Claude Code for multitasking during code reviews, debugging, or long-running operations
- **Target audience**: Developers wanting TTS feedback without cloud dependencies, preference for high-quality French voices
- **Methodology**: Community MCP server (Agent Vibes v3.0.0) + Piper TTS + offline voice models from Hugging Face

---

## [3.11.0] - 2026-01-21

### Added

- **Skill: Design Patterns Analyzer** (`examples/skills/design-patterns/`)
  - **9 files, 5,690 lines**: Comprehensive GoF design patterns analyzer with stack-aware suggestions
  - **SKILL.md** (450 lines): Main instructions with 3 operating modes (Detection, Suggestion, Evaluation)
  - **reference/** (2,140 lines): Complete documentation for 23 GoF patterns
    - `patterns-index.yaml`: Machine-readable index with metadata (difficulty, frequency, confidence)
    - `creational.md`: 5 patterns (Singleton, Factory Method, Abstract Factory, Builder, Prototype)
    - `structural.md`: 7 patterns (Adapter, Bridge, Composite, Decorator, Facade, Flyweight, Proxy)
    - `behavioral.md`: 11 patterns (Observer, Strategy, State, Command, etc.)
  - **signatures/** (1,420 lines): Detection and suggestion rules
    - `stack-patterns.yaml`: 8 stacks detection + native alternatives (React, Angular, NestJS, Vue, Express, RxJS, Redux, ORMs)
    - `detection-rules.yaml`: Grep patterns and heuristics for 23 patterns
    - `code-smells.yaml`: Mapping from 15+ code smells to suggested patterns
  - **checklists/** (450 lines): Quality evaluation system (5 criteria: Correctness, Testability, SRP, Open/Closed, Documentation)
  - **Key features**:
    - Detects 23 Gang of Four design patterns in TypeScript/JavaScript codebases
    - Stack-aware detection (analyzes package.json, tsconfig.json, config files)
    - Prefers stack-native alternatives (e.g., React Context over Singleton, RxJS over manual Observer)
    - Code smell detection with refactoring suggestions
    - Quality scoring (0-10 with weighted criteria)
  - **Documentation**: Added comprehensive example in guide section 5.4 (149 lines) with usage patterns, stack-native recommendations table, detection methodology, and integration examples
  - **Tested on**: Méthode Aristote codebase (Next.js 15.5 + React 19 + tRPC + Prisma)
    - Found: Factory Method (8.2/10), Observer via EventSource (9.1/10), Strategy-like patterns, Repository via Prisma
    - Suggested: React Context instead of Singleton, Strategy pattern for switch statements
    - Identified: Large service files (2,396 and 2,221 lines) requiring extraction

### Changed

- **Template count**: 65 → 66 (added design-patterns skill)
- **examples/README.md**: Added design-patterns entry with ⭐ marker
- **machine-readable/reference.yaml**: Added design_patterns_skill entries (line numbers, location, modes, coverage)

### Context

- **Use case**: Analyze existing patterns, suggest refactoring with stack-native patterns, evaluate pattern implementation quality
- **Target audience**: Developers working on TypeScript/JavaScript projects wanting to detect anti-patterns and improve architecture
- **Methodology**: Glob → Grep → Read pipeline for detection, stack-aware suggestions prioritizing framework idioms

---

## [3.10.0] - 2026-01-21

### Added

- **Section 9.18: Codebase Design for Agent Productivity** (~1809 lines)
  - **Based on**: [Agent Experience Best Practices](https://marmelab.com/blog/2026/01/21/agent-experience.html) by François Zaninotto (Marmelab, Jan 21, 2026)
  - **Additional validation**: Netlify AX framework (2025), Speakeasy implementation guide, ArXiv papers on agent context engineering
  - **9.18.1 Paradigm Shift**: Traditional vs AI-native codebase design, Agent Experience (AX) framework, when to invest in AX
  - **9.18.2 Domain Knowledge Embedding**: CLAUDE.md advanced patterns, code comments (what vs how), Architecture Decision Records (ADRs)
  - **9.18.3 Code Discoverability**: Complete terms vs abbreviations, synonyms in comments, JSDoc tags, directory READMEs
  - **9.18.4 Token Efficiency**: Split large files (500 line guideline), remove obvious comments, verbose flags for debug output
  - **9.18.5 Testing for Autonomy**: Why TDD is more critical for agents, tests written manually (not delegated), browser automation, coverage as guardrail
  - **9.18.6 Conventions & Patterns**: Standard design patterns agents know, "boring tech" advantage, ADRs for custom architectures
  - **9.18.7 Guardrails & Validation**: Hooks as anti-pattern validators, "tainted code" philosophy, PR reviews, validation layers
  - **9.18.8 Serendipity & Cross-References**: Module cross-references, self-documenting commands, embedded technical docs
  - **9.18.9 Usage Instructions**: Doc blocks with examples, Context7 MCP for official docs, sensible defaults
  - **9.18.10 Decision Matrix**: When to optimize for agents vs humans, agent-friendly codebase checklist (33-point), quick wins
- **Section 3.1 enrichment**: Added cross-reference to Section 9.18 for advanced domain knowledge patterns
- **Section 9.11 new subsection**: "Codebase Structure Pitfalls" with ❌/✅ patterns and cross-reference to Section 9.18
- **Table of Contents**: Added Section 9.18 entry
- **Section 9 Recap**: Added "Codebase Design for Agents" item to quality awareness checklist
- **machine-readable/reference.yaml**: Added `codebase_design_agents` entry with line number and source attribution

### Changed

- **VERSION**: Bumped from 3.9.11 to 3.10.0 (minor version bump for major new section)
- **Guide size**: Increased from ~11,560 lines to 13,425 lines (+1,865 lines, +16.1%)

### Context

- **Gap identified**: Guide lacked comprehensive codebase design patterns for agent productivity
- **Timing**: Article published 2 days ago (Jan 21, 2026), validated by Netlify AX research and ArXiv papers
- **Target audience**: Teams extensively using Claude Code (>50% commits by agents), greenfield projects
- **Complementary sources**: Netlify "Agent Experience" research, Speakeasy API DX guide (includes AX patterns)

---

## [3.9.11] - 2026-01-21

### Added
- **Production Safety Rules Guide** (`guide/security/production-safety.md`): Comprehensive production safety rules for teams deploying Claude Code in production environments
  - Port Stability: Prevent accidental port changes breaking local dev/Docker/deployed configs
  - Database Safety: Backup enforcement via PreToolUse hooks to prevent data loss
  - Feature Completeness: No TODOs for core functionality rules
  - Infrastructure Lock: Protect docker-compose.yml, Dockerfile, .env.example, terraform/
  - Dependency Safety: Block unapproved npm packages with permission deny rules
  - Pattern Following: Enforce codebase conventions via CLAUDE.md and automated validation
- Cross-references to production-safety.md in `ultimate-guide.md` section 3.1 and `adoption-approaches.md` (Medium/Large teams)
- New deep_dive entry in `machine-readable/reference.yaml` for production safety topics

### Context
- Adapted from community "10 non-negotiable CLAUDE.md rules" (6/10 rules integrated, 4/10 already covered in existing guide)
- Verified gaps using grepai searches: Rule #5 (ports) genuinely absent, Rule #6 (DB) partially covered
- Target audience: 20% production teams (vs 80% learners in main guide)

---

## [3.9.10] - 2026-01-21

### Added

- **Section 9.17: Scaling Patterns - Multi-Instance Workflows** (~390 lines)
  - **Boris Cherny case study**: 259 PRs/30 days with 5-15 parallel Claude instances (InfoQ interview, Jan 2026)
  - **Anthropic internal study**: 132 engineers, +50% productivity, 21.2 consecutive autonomous actions (Aug 2025)
  - **Decision matrix by team size**: Solo (❌) → Startup (⚠️) → Scale-up (✅) → Enterprise (✅)
  - **Cost-benefit analysis**: $240-1000/month with ROI thresholds (3-5% productivity gain to justify)
  - **Git worktrees foundation**: Critical prerequisite for multi-instance isolation (non-negotiable)
  - **Orchestration frameworks**: Headless PM (open-source REST API), Cursor, Windsurf
  - **Progressive implementation**: 3-phase guide (single mastery → dual testing → multi-instance)
  - **Monitoring guidelines**: Merge conflicts, PRs/month, test pass rates, skill atrophy
  - **Anti-patterns**: When NOT to use (legacy monoliths, solo devs, <$500/mo budget, <5 PRs/week)
  - **Primary sources**: InfoQ "Claude Code Creator Workflow" (2026-01-09), Anthropic Research "How AI is Transforming Work" (2025-08)
- **machine-readable/reference.yaml**: 10 new entries for multi-instance topics
  - `multi_instance_workflows`, `boris_cherny_case_study`, `anthropic_study_metrics`
  - `git_worktrees_multi_instance`, `multi_instance_costs`, `orchestration_frameworks`
  - `headless_pm_framework`, `multi_instance_implementation`, `multi_instance_monitoring`
  - `multi_instance_decision_matrix`

### Fixed

- **Table of Contents**: Added missing sections 9.12-9.17 (git, cost, methodologies, prompts, teleportation, multi-instance)
- **Section 9 checklist**: Added multi-instance scaling item to advanced workflows recap

## [3.9.9] - 2026-01-20

### Changed

- **README.md: Ecosystem cross-reference** — Added bidirectional link to Claude Cowork Guide
  - New section "Not a Developer?" (lines 75-81) linking to Cowork Guide for non-technical users
  - Improves ecosystem discovery and audience routing between dev and non-dev guides
  - Cowork Guide also received reciprocal cross-reference (commit ceadd82 in Cowork repo)
- **CLAUDE.md: Version reference update** — Updated current version from 3.9.7 to 3.9.9

### Fixed

- **README.md: Template count correction** — Fixed template count from 69 to accurate count of 65
  - Badge (line 9): 69 → 65
  - Examples Library summary (line 198): 66 → 65
  - Ecosystem table (line 341): 66 → 65
  - Verified with `find examples/ -type f \( -name "*.md" -o -name "*.sh" ... \) ! -name "README.md" | wc -l`
  - Original count of 69 in v3.9.9 release was overcounted by 4 templates

## [3.9.9] - 2026-01-20

### Added

- **DevOps & SRE Guide** — Comprehensive infrastructure diagnosis guide (~900 lines)
  - **New file**: `guide/ops/devops-sre.md` — The FIRE Framework for infrastructure troubleshooting
    - **F**irst Response → **I**nvestigate → **R**emediate → **E**valuate
    - Kubernetes troubleshooting with copy-paste prompts by symptom (CrashLoopBackOff, OOMKilled, ImagePullBackOff, etc.)
    - Solo incident response workflow (designed for 3 AM scenarios)
    - Multi-agent pattern for post-incident analysis
    - IaC patterns: Terraform, Ansible, GitOps workflows
    - Guardrails & team adoption checklist
    - Claude limitations table (what Claude can't do for DevOps)
    - Case studies: Production outage root cause, OpsWorker.ai MTTR reduction
  - **New file**: `examples/agents/devops-sre.md` — DevOps/SRE agent persona (~130 lines)
    - FIRE framework implementation
    - Kubernetes, network, and resource debugging checklists
    - Response templates (assessment, root cause, remediation)
    - Safety rules for production environments
  - **New file**: `examples/claude-md/devops-sre.md` — CLAUDE.md template for DevOps teams (~170 lines)
    - Infrastructure context configuration
    - Environment, service map, access patterns
    - Team conventions and runbook format
    - Customization guides (K8s-heavy, Terraform-heavy, multi-cloud)
  - **Updated**: `guide/ultimate-guide.md` — Added DevOps & SRE Guide reference after Section 5.4
  - **Updated**: `machine-readable/reference.yaml` — Added 11 DevOps/SRE entries
  - **Updated**: `examples/README.md` — Added agent and CLAUDE.md template to indexes
  - **Updated**: `README.md` — Added DevOps/SRE learning path, updated templates count (69)

## [3.9.8] - 2026-01-20

### Added

- **AI Ecosystem: AI Coding Agents Matrix integration** — Comprehensive ecosystem resource
  - **New Section 11** in `guide/ecosystem/ai-ecosystem.md` (~60 lines): "AI Coding Agents Matrix"
    - Interactive comparison of 23 AI coding agents across 11 technical criteria
    - What Is It, Why It's Useful, Complementarity table, Interactive Features, Limitations
    - Positioning: Discovery (Matrix) → Mastery (This Guide)
    - Maintainers: Packmind (Cédric Teyton, Arthur Magne)
  - **Enhanced `machine-readable/reference.yaml`** (lines 397-412):
    - Added: GitHub repo, maintainers, license (Apache-2.0), tech stack (React, Vite, Tailwind)
    - Added: 4 features (11 criteria, sortable/filterable, community-driven, JSON-based)
    - Added: positioning note, data freshness warning
  - **Updated `README.md`** (Section 8: Ecosystem):
    - Converted complementary resources to comparison table (4 projects)
    - Added dedicated paragraph for AI Coding Agents Matrix with use case
    - Positioning: "Use Matrix to discover/compare → Choose Claude Code → Use this guide to master it"
  - Cross-promotion with [coding-agents-matrix.dev](https://coding-agents-matrix.dev/) (updated Jan 19, 2026)

## [3.9.7] - 2026-01-20

### Changed

- **CLAUDE.md: Model Configuration** — OpusPlan workflow recommendation (replaces thinking mode disable)
  - Hybrid intelligence: Opus (planning) → Sonnet (execution)
  - Task breakdown table: doc edits, version sync, restructuring, research, consistency checks
  - Cost optimization: 10-20% Opus planning, 80-90% Sonnet execution
  - Workflow: `/model opusplan` → `Shift+Tab × 2` (plan) → `Shift+Tab` (execute)

## [3.9.6] - 2026-01-20

### Added

- **ultimate-guide.md: Section 5.5 "Infrastructure as Code Skills"** — New community skill repository (~50 lines)
  - Anton Babenko's terraform-skill (creator of terraform-aws-modules, 1B+ downloads)
  - Covers testing, module development, CI/CD, security, patterns
  - Notable for marketplace distribution (.claude-plugin/), structured references, test coverage
  - Source: [GitHub repo](https://github.com/antonbabenko/terraform-skill)

- **ultimate-guide.md: Section 1.7 "Trust Calibration: When and How Much to Verify"** — New section (~155 lines)
  - Research-backed stats table (ACM, Veracode, CodeRabbit, Cortex.io sources)
  - Verification spectrum (boilerplate → security-critical)
  - Solo vs Team verification strategies with workflow diagrams
  - "Prove It Works" checklist (functional, security, integration, quality)
  - Anti-patterns table (6 common mistakes)
  - Attribution to Addy Osmani's "AI Code Review" (Jan 2026)

- **ultimate-guide.md: New pitfall** — "Trust AI output without proportional verification"

- **learning-with-ai.md: Section 3 "The Reality of AI Productivity"** — New section (~55 lines)
  - Productivity curve phases (Wow Effect → Targeted Gains → Sustainable Plateau)
  - High-gain vs low/negative-gain task categorization
  - Team success factors (guidelines, code review, mentorship)

- **reference.yaml**: `trust_calibration` (line 1039), `community_skills_cybersec` (4786), `community_skills_iac` (4871), `vibe_coding_trap` (81)

- **learning-with-ai.md: "The Vibe Coding Trap" section** — New anti-pattern documentation (~15 lines)
  - Term coined by Andrej Karpathy (Feb 2025, Collins Word of the Year 2025)
  - Symptoms checklist + Karpathy's caveat ("throwaway projects" vs production)
  - Links to UVAL Protocol as antidote

- **IDEAS.md: "Vibe Coding Discourse"** — New Watching entry
  - Tracks "developer as architect" narrative evolution
  - Source: Craig Adam "Agile is Out, Architecture is Back" (Medium)

- **learning-with-ai.md: External Resources** — Added [leerob.com/ai](https://leerob.com/ai) link
  - AI fundamentals for engineers (ML, neural networks, transformers, tokenization)
  - Score 3/5 eval: complement utile, not deep integration
  - Source: Lee Robinson (Nov 2024)

### Changed

- **reference.yaml**: Complete line number synchronization (~55 entries updated)
  - Guide grew from ~9900 to 11154 lines; all deep_dive references now accurate
  - Added "Updated 2026-01-20" comment for tracking
  - Major corrections: cost_optimization (8047→8833), interaction_loop (1063→1299), etc.

- **ultimate-guide.md**: Section renumbering — "Eight Beginner Mistakes" moved 1.7 → 1.8
- **learning-with-ai.md**: Three Patterns productivity trajectory table, 70/30 Split research callout, Sources section (+5 sources)
- **learning-with-ai.md**: ToC renumbered (14 sections, was 13)

## [3.9.5] - 2026-01-19

### Added

- **IDEAS.md "Watching" section** — New category for tracking ideas awaiting demand
  - Multi-LLM Consultation Patterns (Gemini/GPT-4 as second opinion)
  - Research done: bash scripts vs Plano (overkill for solo devs)
  - Criteria: implement if 3+ reader requests

### Changed

- **README.md restructuration** — Reduced cognitive load by ~40% (benchmarked)
  - Removed duplicate "5 Rules to Remember" section (content already in "Golden Rules")
  - Added collapsible Table of Contents with 4 learning paths:
    - Beginner Path (TL;DR, Get Started, Golden Rules)
    - Developer Path (By Role, Guide Navigation, Examples)
    - Advanced Path (Audit, Quiz, Ecosystem)
    - Reference (Toolkit, About, Contributing)
  - Simplified "Choose Your Path" section (4 rows → 3, references ToC)
  - Updated TL;DR link from `#5-rules-to-remember` → `#-golden-rules`
  - Net change: +19 lines (757 total), improved navigation

## [3.9.4] - 2026-01-19

### Added

- **Session Teleportation documentation** — New Section 9.16 in Ultimate Guide (~105 lines)
  - Evolution timeline (2.0.24 → 2.1.0)
  - Commands reference (`%`, `--teleport`, `/teleport`, `/tasks`, `/remote-env`, `Ctrl+B`)
  - Prerequisites (GitHub App, clean git state, same account)
  - Workflow example with step-by-step
  - Environment support table (CLI, VS Code, Cursor, Web, iOS)
  - Current limitations (research preview, unidirectional, GitHub only)
  - Troubleshooting table
  - Best practices
  - Environment variables (`CLAUDE_CODE_DISABLE_BACKGROUND_TASKS`)
- Updated Section 9 Recap with "Advanced Workflows" category
- Updated `guide/cheatsheet.md` with teleportation commands
  - Essential Commands: `/teleport`, `/tasks`, `/remote-env`
  - Keyboard Shortcuts: `Ctrl+B`
  - CLI Flags: `--teleport`
- Updated `machine-readable/reference.yaml`
  - New `session_teleportation` deep_dive entry
  - Commands: `/teleport`, `/tasks`, `/remote-env`
  - Shortcuts: `Ctrl+B`
  - CLI: `--teleport`
  - Line numbers updated for sections after 9.15

## [3.9.3] - 2026-01-19

### Added

- **Claude Cowork documentation** — Complete guide for the new agentic desktop feature
  - `guide/cowork.md` (NEW, ~460 lines) — Full documentation
    - Architecture overview (local-first, sub-agents, no code execution)
    - Comparison: Claude Code vs Cowork vs Projects
    - 5 detailed use cases (file org, expenses, reports, travel, meetings)
    - Security best practices (no official docs exist yet)
    - Developer ↔ Non-Developer workflow patterns
    - Known issues & troubleshooting
    - Availability & roadmap
  - `guide/ecosystem/ai-ecosystem.md` Section 9 (~90 lines) — Condensed integration guide
    - Quick comparison table
    - When to use what decision flow
    - Security considerations summary
    - Cross-reference to full guide
  - `guide/ultimate-guide.md` — Cowork subsection in Section 11
    - Comparison table and collaboration pattern
    - Table of Contents updated
  - `machine-readable/reference.yaml` — 8 new deep_dive entries for Cowork
  - Updated `guide/README.md` navigation table
  - Updated main `README.md` AI Ecosystem entry

## [3.9.2] - 2026-01-19

### Added

- **Alternative Providers section** in `guide/ecosystem/ai-ecosystem.md` (~55 lines)
  - Documents existence of community workarounds (ANTHROPIC_BASE_URL, etc.)
  - Clear disclaimer: not tested, not recommended, not supported
  - Reasons to avoid: feature degradation, ToS risks, no support
  - Better alternatives table: Aider for local models, Continue.dev for multi-provider
  - External reading pointers (no step-by-step instructions intentionally)
  - Updated Table of Contents
  - Added `ai_ecosystem_alternative_providers` reference in `reference.yaml`

## [3.9.1] - 2026-01-19

### Added

- **AI Ecosystem: Complementary Tools** — New Section 11 documenting tool complementarity
  - `guide/ultimate-guide.md` Section 11 (~250 lines)
    - 11.1 Why Complementarity Matters — Claude Code strengths vs gaps
    - 11.2 Tool Matrix — Decision guide for when to use which tool
    - 11.3 Practical Workflows — 4 pipelines (Research→Code, Visual→Code, Documentation, Presentation)
    - 11.4 Integration Patterns — Full workflows with budget recommendations
  - `guide/ecosystem/ai-ecosystem.md` (NEW, ~750 lines)
    - Detailed guide for each complementary tool
    - Perplexity AI (research with verified sources)
    - Google Gemini (image understanding → code)
    - Kimi/Moonshot (PPTX generation, 128K context)
    - NotebookLM (doc synthesis + audio overviews)
    - IDE tools (Cursor, Windsurf, Cline)
    - UI Prototypers (v0, Bolt, Lovable)
    - Ready-to-use prompts appendix
    - Cost optimization strategies
  - Updated `guide/README.md` with navigation link
  - Updated main `README.md` navigation table
  - Updated `machine-readable/reference.yaml` with 6 new line number references

### Changed

- **tools/mobile-access.md** - Enhanced with verified data and alternatives
  - Added Architecture Comparison section with 3 ASCII diagrams (ttyd, Happy Coder, Remoto.sh)
  - Restructured comparison table with Type/Pros/Cons/ToS/Stars columns
  - Added Happy Coder section: 7.8K ⭐ (verified 2026-01-19), MIT, Tauri/Expo stack, ToS-safe
  - Added Remoto.sh warning: ToS risk documented (Anthropic §4.2 proxy policy)
  - Added Sources section with all referenced projects
  - Updated footer with data verification date
  - File expanded from 300 to 385 lines

## [3.9.0] - 2026-01-19

### Added

- **Semantic Anchors** — New concept integrated for better LLM prompting
  - Section 2.7 "Semantic Anchors" in `guide/ultimate-guide.md` (~93 lines)
    - Explains how precise vocabulary helps LLMs activate correct patterns
    - Common anchors table (vague → precise) with explanations
    - Integration examples with CLAUDE.md and XML tags
  - `examples/semantic-anchors/anchor-catalog.md` (NEW, ~320 lines)
    - Comprehensive catalog organized by domain (Testing, Architecture, Design, etc.)
    - Before/after examples showing prompt improvement
    - CLAUDE.md template with anchors integrated
  - Source attribution: Alexandre Soyer, [github.com/LLM-Coding/Semantic-Anchors](https://github.com/LLM-Coding/Semantic-Anchors) (Apache-2.0)
  - Section numbering fixed: 2.6 Data Flow → 2.8, 2.7 Under the Hood → 2.9

- **Subscription Plans & Limits** — New section documenting subscription concepts
  - Section "#### Subscription Plans & Limits" in `guide/ultimate-guide.md` (~42 lines)
    - Explains message windows, hybrid counting, weekly caps, model weighting
    - Tier-specific strategies (limited → unlimited quota)
    - Links to official pricing page (concepts only, no volatile numbers)
  - Updated `machine-readable/reference.yaml` with `subscription_limits: 1750`
  - Fixed drifted line numbers in reference.yaml (commands_table, shortcuts_table, etc.)

- **6 new slash commands** (Sprint 1 + Sprint 2 implementation)
  - `examples/commands/catchup.md` - Restore context after `/clear` (137 lines)
    - Git history analysis (last 10 commits, recent diffs)
    - TODO/FIXME scanning across codebase
    - Project state summary with actionable next steps
  - `examples/commands/security.md` - Quick OWASP security audit (149 lines)
    - Secrets detection (API keys, tokens, passwords)
    - Injection vulnerability scanning (SQL, XSS, command)
    - Dependency audit integration
    - Severity-based output (Critical/High/Medium/Low)
  - `examples/commands/refactor.md` - SOLID-based code improvements (195 lines)
    - SOLID violation detection with examples
    - Risk level assessment for each suggestion
    - Atomic commit recommendations
  - `examples/commands/explain.md` - Code explanations with 3 depth levels (174 lines)
    - Simple (TL;DR), Standard, Deep modes
    - Supports files, functions, concepts, flows
    - Example outputs at each level
  - `examples/commands/optimize.md` - Performance analysis and roadmap (195 lines)
    - Runtime, memory, database, bundle analysis
    - Profiling commands per language
    - Prioritized optimization roadmap
  - `examples/commands/ship.md` - Pre-deploy checklist (189 lines)
    - Blocker/High/Recommended categorization
    - Tests, lint, build, secrets, security audit
    - Migration and rollback verification

- **Named Prompting Patterns** section in `guide/ultimate-guide.md` (Section 9.15, ~155 lines)
  - **"As If" Pattern**: Set quality expectations ("Implement as if senior engineer at Google")
  - **Constraint Pattern**: Force creative solutions ("Solve without new dependencies")
  - **"Explain First" Pattern**: Force planning before implementation
  - **"Rubber Duck" Pattern**: Collaborative debugging through questions
  - **Incremental Pattern**: Gradual complexity building
  - **Boundary Pattern**: Define scope and constraints explicitly
  - Combination examples and anti-patterns

- **Mermaid Diagram Generation** section in `guide/ultimate-guide.md` (Section 9.7, ~90 lines)
  - 6 diagram types: Flowchart, Sequence, Class, ER, State, Gantt
  - Prompt templates for each type
  - Visualization tools reference (GitHub, mermaid.live, VS Code)

- **Eight Beginner Mistakes** checklist in `guide/ultimate-guide.md` (Section 1.7, ~70 lines)
  - Based on competitive analysis vs Jo Vinkenroye's Mastery series
  - 8 common mistakes with symptoms and solutions
  - Prevention patterns for each mistake

- **Commands vs Skills vs Agents** enhanced comparison table (Section 5.1, ~50 lines)
  - Detailed comparison across 8 aspects
  - When to use each type with decision criteria
  - Combination patterns for complex workflows

- **Learning with AI guide** for junior developers (`guide/roles/learning-with-ai.md`, ~900 lines)
  - **Quick Self-Check** (L31-81): 5 diagnostic questions to assess AI dependency
  - **Three Developer Patterns** (L82-126): Dependent, Avoidant, Augmented profiles with action paths
  - **UVAL Protocol** (L127-352): Understand → Verify → Apply → Learn framework
  - **Claude Code for Learning** (L353-469): CLAUDE.md configuration, slash commands, hooks
  - **Breaking Dependency** (L470-517): Recovery plan for over-reliant developers
  - **Embracing AI** (L518-709): Onboarding for AI-skeptical developers
  - **30-Day Progression Plan** (L710-769): Week-by-week AI ratio progression
  - **Red Flags Checklist** (L770-850): Warning signs and corrective actions

- **Learning mode templates** (3 new files)
  - `examples/claude-md/learning-mode.md`: CLAUDE.md template for learning-focused development
  - `examples/commands/quiz.md`: /quiz slash command for self-testing
  - `examples/hooks/bash/learning-capture.sh`: Stop event hook for daily learning capture

- **Wireframing & Figma MCP documentation** in `guide/ultimate-guide.md` (+143 lines)
  - Wireframing tools comparison (Excalidraw, tldraw, Frame0, Paper+Photo)
  - Figma MCP Integration with official Anthropic server
  - Image Optimization for Claude Vision with resolution guidelines

### Changed

- **README.md** updates:
  - Lines badge: 9,800+ → 10,500+
  - Templates badge: 56 → 63
  - Commands table: Added 6 new commands
  - Version: 3.8.2 → 3.9.0
  - Added prominent "Visit Website" badge linking to landing page

- **examples/README.md**: Added 6 new commands to Commands table

- **scripts/install-templates.sh**: Updated commands list with new templates

- **guide/ultimate-guide.md**:
  - Table of Contents updated with sections 1.6, 1.7
  - Section 9 Recap enhanced with Communication Patterns checklist
  - Guide expanded by ~385 lines (9,881 → 10,266)

- **Semantic search tools priority**: grepai now recommended over mgrep
  - Sections reordered (grepai first as "Recommended", mgrep as "Alternative")
  - `guide/cheatsheet.md`: MCP Servers table updated
  - Rationale: grepai is fully open-source, runs locally (privacy)

### Stats

- 6 new command files created (~1,039 lines total)
- ~385 lines added to ultimate-guide.md
- Templates count: 56 → 63
- Focus on competitive analysis gaps vs community resources
- Named patterns and beginner-friendly content added

---

## [3.8.2] - 2026-01-17

### Added

- **Landing Site Synchronization System**
  - New script `scripts/check-landing-sync.sh` verifying 4 metrics:
    - Version (`VERSION` vs landing index.html)
    - Templates count (`find examples/` vs landing badges)
    - Quiz questions (`questions.json` vs index.html + quiz.html)
    - Guide lines (with ±500 tolerance)
  - CLAUDE.md updated with sync documentation and expected output
  - Landing site CLAUDE.md created with sync workflow and line numbers

### Fixed

- **Templates count corrected**: 87 → 49 in README.md badges and text
  - Badge count was wrong since original creation
  - Actual count verified with `find examples/ -type f`

---

## [3.8.1] - 2026-01-16

### Added

- **PDF Generation documentation**
  - New workflow guide: `guide/workflows/pdf-generation.md`
  - New skill template: `examples/skills/pdf-generator.md`
  - Covers Quarto + Typst stack, YAML frontmatter, design system, troubleshooting
  - Updated `machine-readable/reference.yaml` with deep_dive entries

### Changed

- **Whitepapers PDF template modernized** (internal)
  - New color palette: Slate + Indigo (WCAG AA compliant)
  - Typography: Inter font, JetBrains Mono for code
  - Cover page redesign: Claude Code logo, minimal white design
  - Fixed nested markdown code blocks (42 blocks using `````markdown`)
  - Added clickable GitHub links for all script references

---

## [3.8.0] - 2026-01-16

### Added

- **TL;DR Quick Start section** in README.md
  - Quick reference table: Cheat Sheet (2 min), Starter CLAUDE.md (30 sec), 5 Rules (1 min)
  - Copy-paste CLAUDE.md template directly in README
  - Optimized for TTFV (Time-to-First-Value) < 5 minutes
  - Prominent badges at top: version, license, Claude Code support

- **French Whitepapers documentation** in README.md
  - New section documenting 8 whitepapers in French (~185 pages total)
  - Learning paths by profile: Junior (25 min), Senior (1h15), Tech Lead (1h15)
  - Files in `whitepapers/` directory using Quarto (.qmd) format

- **CODE_OF_CONDUCT.md** (new file)
  - Contributor Covenant v2.1
  - Standard OSS community guidelines

- **Distribution playbooks** (internal, gitignored)
  - `claudedocs/distribution-playbook.md`: Ready-to-use content for awesome-claude-code PR, Reddit, dev.to, Twitter
  - `claudedocs/github-discussions-setup.md`: Step-by-step GitHub Discussions setup
  - French distribution strategy: Dev With AI Slack, LinkedIn FR

### Changed

- **CONTRIBUTING.md completely rewritten**
  - Added welcome message and contribution types table
  - Clear PR process with checklist
  - Quality checklist before submitting
  - References to GitHub Discussions and Code of Conduct

- **README.md restructured**
  - "Why This Guide" section rewritten for clarity
  - Repository structure updated to include whitepapers/
  - Dev With AI community reference added

### Internal

- Added `claudedocs/` and `whitepapers/` to `.gitignore` (internal docs)

---

## [3.7.1] - 2026-01-15

### Added

- **Intellectual Property Considerations** section in `guide/security/data-privacy.md`
  - Disclaimer about legal advice limitations
  - Key considerations: ownership, license contamination, vendor indemnification, sector compliance
  - Guidance to consult legal counsel for specific situations

---

## [3.7.0] - 2026-01-15

### Added - Session Search v2.1

Major upgrade to the session search utility (`cs`) with new features and bug fixes.

#### New Features

| Feature | Description | Example |
|---------|-------------|---------|
| **Multi-word AND search** | All words must match (was broken in v1) | `cs "prisma migration"` |
| **Project filter** | Filter by project name (substring) | `cs -p myproject "bug"` |
| **Date filter** | Filter by date (today, 7d, YYYY-MM-DD) | `cs --since 7d` |
| **JSON output** | Machine-readable output for scripting | `cs --json "api" \| jq .` |
| **Timeout** | 3-second timeout prevents long searches | Automatic |
| **Clean previews** | XML tags stripped, unicode filtered | No more `<local-command-caveat>` |

#### Performance

| Operation | Time |
|-----------|------|
| Cache lookup | ~16ms |
| Index rebuild | ~6s (239 sessions) |
| Fulltext search | 3-4s (timeout-bounded) |

#### Usage Examples

```bash
cs                          # 10 most recent sessions
cs "Prisma migration"       # Multi-word AND search
cs -p MethodeAristote "api" # Filter by project + keyword
cs --since 7d               # Last 7 days
cs --since today -n 20      # Today's sessions
cs --json "test" | jq .     # JSON for scripting
```

#### Files Modified

- `examples/scripts/session-search.sh` - Script v2.1 (367 lines)
- `guide/ops/observability.md` - Documentation updated with new options

#### Quality Score Progression

| Version | Score | Key Improvements |
|---------|-------|------------------|
| v1.0 | 6/10 | Basic functionality |
| v2.0 | 8/10 | +AND search, +filters, +JSON |
| v2.1 | **9.3/10** | +JSON fix, +clean previews |

---

## [3.6.1] - 2026-01-15

### Fixed - Critical Factual Corrections

Major audit identifying and correcting factual errors that could mislead users about Claude Code's actual behavior.

#### 1. `--add-dir` Flag (Wrong Description → Permissions, Not Context Loading)

**Before**: Documented as "loading directories into context" / "focused context"
**Reality**: Grants tool access to directories outside CWD (permissions only, no token impact)

| File | Correction |
|------|------------|
| guide/ultimate-guide.md | "focused context" → "allow tool access outside CWD" |
| guide/cheatsheet.md | "Add directory" → "Allow access outside CWD" |
| machine-readable/reference.yaml | "limit loaded dirs" → "access dirs outside CWD" |
| quiz/questions/10-reference.yaml | Question + explanation corrected |

#### 2. `excludePatterns` → `permissions.deny` (Never Existed)

**Before**: Documented `excludePatterns` as a valid settings key
**Reality**: Never existed - the correct syntax is `permissions.deny`

| File | Correction |
|------|------------|
| guide/ultimate-guide.md | New syntax + warning |
| guide/security/data-privacy.md | New syntax + deprecation note |
| examples/scripts/audit-scan.sh | Detection + message fixed |
| tools/audit-prompt.md | 3 references corrected |

#### 3. `.claudeignore` Removed (Does Not Exist)

**Before**: Documented as a file exclusion mechanism like `.gitignore`
**Reality**: Not an official feature - use `permissions.deny` instead

| File | Correction |
|------|------------|
| guide/ultimate-guide.md | References → `permissions.deny` |
| guide/security/data-privacy.md | Section removed |
| CHANGELOG.md:1244 | Historical reference corrected |

#### 4. "Selective Context Loading" Myth → Lazy Loading Reality

**Before**: Implied Claude loads entire codebase or selectively loads directories
**Reality**: Claude uses lazy loading - reads files on-demand via Read/Grep tools

| File | Correction |
|------|------------|
| guide/ultimate-guide.md | New section explaining lazy loading |
| guide/cheatsheet.md | "Giant context loads" → "Vague prompts" |
| machine-readable/reference.yaml | "load giant context" → "bloated CLAUDE.md" |

#### 5. Invented CLI Flags (SuperClaude Extension Confusion)

**Before**: `--think`, `--think-hard`, `--ultrathink`, `--headless`, `--learn`, `--uc`, `--web` documented as official CLI flags
**Reality**: These are SuperClaude framework extensions (prompt injection), NOT official Claude Code flags

| Correction Type | Details |
|-----------------|---------|
| `--headless` | Replaced with `-p` (the actual flag for non-interactive mode) |
| `--think` variants | Clarified as "prompt keywords", not CLI flags |
| SuperClaude section | Added warning: "Non-official Extension" |
| Cheatsheet | Think flags table reformatted as prompt keywords |
| Decision tree | "Use --think" → "Use extended thinking prompts" |

#### 6. `@` File Reference Behavior

**Before**: "Claude loads file content automatically"
**After**: "Signals Claude to read files on-demand via tools"

### Added - Session Search Tool (`cs`)

**Problem solved**: After weeks of Claude Code usage, finding past conversations becomes painful:
- `claude --resume` is interactive (no search)
- Sessions accumulate in `~/.claude/projects/`
- No quick way to search "that session where I talked about auth"

**Solution**: `cs` — Zero-dependency bash script for searching and resuming sessions.

```bash
cs                    # List 10 recent sessions (15ms)
cs "authentication"   # Full-text search (400ms)
cs -n 20              # More results

# Output:
# 2026-01-15 08:32 │ my-project │ Implement OAuth flow for...
#   claude --resume 84287c0d-8778-4a8d-abf1-eb2807e327a8
```

**Performance comparison**:

| Tool | List | Search | Deps | Resume cmd |
|------|------|--------|------|------------|
| `cs` (this script) | 15ms | 400ms | None | ✅ Shown |
| claude-conversation-extractor | 230ms | 1.7s | Python | ❌ |
| `claude --resume` native | 500ms+ | ❌ | None | Interactive |

**Files created/modified**:

| File | Description |
|------|-------------|
| `examples/scripts/session-search.sh` | Script in repo (source) |
| `examples/README.md` | Entry in Scripts table |
| `guide/ops/observability.md` | Section "Session Search & Resume" |
| `guide/ultimate-guide.md:505-524` | Examples in "Finding session IDs" |
| `README.md:398-403` | Section "Utility Scripts" |
| `machine-readable/reference.yaml` | `deep_dive.session_search` entry |

**Installation** (local):
```bash
# Copy script
cp examples/scripts/session-search.sh ~/.claude/scripts/cs
chmod +x ~/.claude/scripts/cs

# Add alias to shell
echo 'alias cs="~/.claude/scripts/cs"' >> ~/.zshrc
source ~/.zshrc
```

### Added - Security Documentation

| File | Addition |
|------|----------|
| guide/security/security-hardening.md | Section 1.2 "Known Limitations of permissions.deny" |

**Content**:
- Blocking matrix (Read/Edit/Write/Bash)
- Security gaps documented (GitHub #4160)
- Recommended exhaustive config
- Defense-in-depth strategy

### Files Modified (15 total)

```
guide/ultimate-guide.md
guide/cheatsheet.md
guide/security/data-privacy.md
guide/security/security-hardening.md
guide/ops/observability.md
machine-readable/reference.yaml
examples/scripts/audit-scan.sh
examples/scripts/session-search.sh (NEW)
examples/README.md
tools/audit-prompt.md
quiz/questions/01-quick-start.yaml
quiz/questions/10-reference.yaml
CHANGELOG.md
```

### Root Cause Analysis

The factual errors originated from:
1. **SuperClaude framework confusion**: User had `~/.claude/FLAGS.md` with custom flags that were documented as if official
2. **Assumption propagation**: "selective loading" concept was assumed from other AI tools
3. **Outdated syntax**: `excludePatterns` may have been planned but never implemented

---

## [3.6.0] - 2026-01-15

### Added - Version Sync Infrastructure

Single source of truth for versioning across all documentation.

#### New Files
- **VERSION** - Canonical version file (single source of truth)
- **scripts/sync-version.sh** - Automated version synchronization script
  - `--check` mode for CI validation (exit 1 if mismatch)
  - Auto-fixes all 3.x.x versions across docs
  - macOS/Linux compatible

#### Fixed
- **Version inconsistencies resolved**:
  - guide/cheatsheet.md: 3.5.0 → 3.6.0
  - guide/ultimate-guide.md: 3.0.7, 3.5.0 → 3.6.0
  - machine-readable/reference.yaml: 3.5.0 → 3.6.0

---

### Improved - README.md Navigation & Structure

Documentation alignment and navigation improvements.

#### README.md Updates
- **Repository Structure**: Added guide/workflows/, examples/modes/, examples/config/, examples/memory/
- **Core Documentation**: Added 5 entries (methodologies.md, workflows/, data-privacy.md, security-hardening.md, observability.md)
- **Slash Commands**: Added 4 commands (generate-tests, review-pr, git-worktree, validate-changes)
- **Security Hooks**: Added 2 hooks + link to complete catalog
- **🧭 Not Sure Where to Start?**: Added 6 navigation entries (Workflows, Methodologies, Architecture, Data Privacy, Security Hardening, Observability)
- **By Role Paths**: Enhanced all 4 paths with new resources (Power User +1: Security Hardening)
- **SEO Keywords**: Added 9 keywords (tdd ai, sdd, bdd, methodologies, architecture, workflows, data privacy, ai coding workflows)

#### guide/README.md Updates
- Added security-hardening.md to Contents table

---

## [3.5.0] - 2026-01-14

### Added - Development Methodologies & Workflows

Comprehensive documentation covering 15 structured development methodologies for AI-assisted development (2025-2026), with practical workflow guides.

#### New Files
- **guide/core/methodologies.md** (NEW, ~400 lines) - Complete methodology reference:
  - 15 methodologies organized in 6-tier pyramid (Orchestration → Optimization)
  - BMAD, SDD, TDD, BDD, DDD, ATDD, CDD, FDD, Context Engineering, Eval-Driven, Multi-Agent, Iterative Loops, Prompt Engineering
  - Decision tree for choosing the right approach
  - SDD tools reference (Spec Kit, OpenSpec, Specmatic)
  - Combination patterns by project type
  - Claude Fit ratings for each methodology

- **guide/workflows/** (NEW directory, 4 files, ~700 lines total):
  - **tdd-with-claude.md** - Test-Driven Development workflow with Claude-specific prompting patterns
  - **spec-first.md** - Spec-First Development (SDD) adapted for CLAUDE.md
  - **plan-driven.md** - Effective use of /plan mode
  - **iterative-refinement.md** - Prompt → Observe → Reprompt loops

#### Guide Updates
- **guide/ultimate-guide.md** - Section 9.14 "Development Methodologies" (NEW, ~60 lines):
  - Quick decision tree for workflow selection
  - 4 core workflows summary table
  - 15 methodologies reference table
  - SDD tools overview
  - Combination patterns by situation

#### Navigation Updates
- **guide/README.md** - Contents table updated with methodologies.md and workflows/

### Sources
- Anthropic Engineering Blog (claude-code-best-practices, context-engineering)
- GitHub (Spec Kit official announcement)
- Martin Fowler (SDD essays)
- Fission AI (OpenSpec)
- Specmatic.io
- Community production reports (2025-2026)

### Stats
- 5 new files created (~1,100 lines total)
- 2 files modified (ultimate-guide.md, guide/README.md)
- Focus on practical, actionable workflows over theory

---

## [3.4.0] - 2026-01-14

### Added - Architecture & Internals Documentation

New comprehensive documentation explaining how Claude Code works internally, based on official Anthropic sources and verified community analysis.

#### New Files
- **guide/core/architecture.md** (NEW, ~800 lines) - Complete technical deep-dive:
  - The Master Loop (`while(tool_call)` architecture)
  - The Tool Arsenal (8 core tools: Bash, Read, Edit, Write, Grep, Glob, Task, TodoWrite)
  - Context Management Internals (~200K token budget, auto-compaction)
  - Sub-Agent Architecture (isolated context, max depth=1)
  - Permission & Security Model (interactive prompts + allow/deny + hooks)
  - MCP Integration (JSON-RPC 2.0, treated as native tools)
  - The Edit Tool internals (exact match → fuzzy matching)
  - Session Persistence (--resume, --continue)
  - Philosophy: "Less Scaffolding, More Model"
  - Claude Code vs Alternatives comparison table
  - Sources with explicit confidence levels (Tier 1/2/3)
  - Appendix: What We Don't Know (transparency about gaps)
  - 5 ASCII diagrams (Master Loop, Context Budget, Sub-Agent, Permission Layers, MCP)

#### Guide Updates
- **guide/ultimate-guide.md** - Section 2.7 "Under the Hood" (NEW, ~100 lines):
  - Summary of architecture concepts with ASCII diagram
  - Links to full architecture.md for deep dives
  - Cross-references to existing sections (7-Hooks, 8.6-MCP Security)
  - Updated Table of Contents

- **guide/cheatsheet.md** - "Under the Hood (Quick Facts)" section (NEW):
  - 5-row table with key architecture concepts
  - Link to architecture.md for deep dive

#### Navigation Updates
- **README.md** - Core Documentation table + Repository Structure updated
- **guide/README.md** - Contents table updated with architecture.md
- **machine-readable/reference.yaml** - New `architecture:` section + deep_dive refs
- **machine-readable/llms.txt** - Guide structure + file list updated
- **tools/audit-prompt.md** - Related Resources updated
- **tools/onboarding-prompt.md** - Related Resources updated
- **examples/README.md** - Footer reference added

### Sources
- Tier 1 (Official): anthropic.com/engineering/claude-code-best-practices, code.claude.com/docs
- Tier 2 (Verified): PromptLayer analysis, community observations
- Tier 3 (Inferred): Marked with confidence levels

### Stats
- 1 new file created (architecture.md, ~800 lines)
- 10 files modified (navigation, versioning)
- Focus on transparency about Claude Code internals with source citations

---

## [3.3.1] - 2026-01-14

### Changed
- **IDEAS.md** - Consolidated and curated research topics
  - High Priority: Unified "MCP Security Hardening" (merged 3 overlapping topics)
  - Medium Priority: Kept CI/CD Workflows Gallery + MCP Server Catalog
  - Lower Priority: CLAUDE.md Patterns Library (templates by stack)
  - Discarded: Added 6 topics already covered in guide (prompt engineering, context optimization, task decomposition, agent architecture, case studies, tool comparisons)
  - Technical writer agent validation of all ideas against reference.yaml

### Stats
- IDEAS.md reduced from 12 research topics to 4 actionable items
- Discarded section expanded from 3 to 16 entries with clear justifications
- Focus on actionable research vs theoretical exploration

---

## [3.3.0] - 2026-01-14

### Added - LLM Handbook Integration + Google Agent Whitepaper

This release combines learnings from the LLM Engineers Handbook (guardrails, observability, evaluation) and Google's Agent Whitepaper (context triage, security patterns, validation checklists).

#### Advanced Guardrails
- **examples/hooks/bash/prompt-injection-detector.sh** - PreToolUse hook detecting:
  - Role override attempts ("ignore previous instructions", "you are now")
  - Jailbreak patterns ("DAN mode", "developer mode")
  - Delimiter injection (`</system>`, `[INST]`, `<<SYS>>`)
  - Authority impersonation and base64-encoded payloads
- **examples/hooks/bash/output-validator.sh** - PostToolUse heuristic validation:
  - Placeholder content detection (`/path/to/`, `TODO:`, `example.com`)
  - Potential secrets in output (regex patterns)
  - Uncertainty indicators and incomplete implementations
- **examples/hooks/bash/claudemd-scanner.sh** - SessionStart hook (NEW):
  - Scans CLAUDE.md files for prompt injection attacks before session
  - Detects: "ignore previous instructions", shell injection (`curl | bash`), base64 obfuscation
  - Warns about suspicious patterns in repository memory files
- **examples/hooks/bash/output-secrets-scanner.sh** - PostToolUse hook (NEW):
  - Scans tool outputs for leaked secrets (API keys, tokens, private keys)
  - Catches secrets before they appear in responses or commits
  - Detects: OpenAI/Anthropic/AWS keys, GitHub tokens, database URLs

#### Observability & Monitoring
- **examples/hooks/bash/session-logger.sh** - PostToolUse operation logging:
  - JSONL format to `~/.claude/logs/activity-YYYY-MM-DD.jsonl`
  - Token estimation, project tracking, session IDs
- **examples/scripts/session-stats.sh** - Log analysis script:
  - Daily/weekly/monthly summaries
  - Cost estimation with configurable rates
  - Tool usage and project breakdowns
- **guide/ops/observability.md** - Full observability documentation (~180 lines):
  - Setup instructions, cost tracking, patterns
  - Limitations clearly documented

#### LLM-as-a-Judge Evaluation
- **examples/agents/output-evaluator.md** - Quality gate agent (Haiku):
  - Scores: Correctness, Completeness, Safety (0-10)
  - Verdicts: APPROVE, NEEDS_REVIEW, REJECT
  - JSON output format for automation
- **examples/commands/validate-changes.md** - `/validate-changes` command:
  - Pre-commit validation workflow
  - Integrates with output-evaluator agent
- **examples/hooks/bash/pre-commit-evaluator.sh** - Git pre-commit hook:
  - Opt-in LLM evaluation before commits
  - Cost: ~$0.01-0.05/commit (Haiku)
  - Bypass with `--no-verify` or `CLAUDE_SKIP_EVAL=1`

#### Google Agent Whitepaper Integration
- **guide/ultimate-guide.md Section 2.2.4** - Context Triage Guide (NEW):
  - What to keep vs evacuate when approaching context limits
  - Priority matrix: Critical (current task) → Important (recent decisions) → Evacuate (old context)
  - Recovery patterns for session continuation
- **guide/ultimate-guide.md Section 3.1.3** - CLAUDE.md Injection Warning (NEW):
  - Security risks when cloning unfamiliar repositories
  - Recommendation to use `claudemd-scanner.sh` hook
  - Examples of malicious patterns to watch for
- **guide/ultimate-guide.md Section 4.2.4** - Agent Validation Checklist (NEW):
  - 12-point checklist before deploying custom agents
  - Covers: tool restrictions, output validation, error handling, cost control
  - Based on Google's agent validation framework
- **guide/ultimate-guide.md Section 8.6** - MCP Security (NEW):
  - Tool Shadowing attacks: malicious MCP tools mimicking legitimate ones
  - Confused Deputy attacks: MCP servers tricked into unauthorized actions
  - Mitigation strategies and trust verification patterns
- **guide/ultimate-guide.md Section 3.3.3** - Session vs Memory (NEW):
  - Clarifies session context (ephemeral) vs persistent memory (Serena write_memory)
  - When to use each for long-running projects
  - Recovery patterns after context limits

### Changed
- **examples/hooks/README.md** - Added "Advanced Guardrails" section with all new hooks
- **examples/README.md** - Updated index with all new files
- **guide/README.md** - Added observability.md to contents

### Stats
- 10 new files created
- 8 files modified
- 5 new guide sections added
- Focus: Production LLM patterns + Security hardening + Context management

---

## [3.2.0] - 2026-01-14

### Added
- **guide/security/data-privacy.md** - Comprehensive data privacy documentation (NEW, ~200 lines)
  - TL;DR retention table: 5 years (default) | 30 days (opt-out) | 0 (Enterprise ZDR)
  - Data flow diagram showing what leaves your machine
  - Known risks with MCP database connections
  - Protection measures (excludePatterns, hooks, MCP safety)
  - Quick checklist for immediate action

- **README.md** - Privacy notice encart (3 lines after transparency note)
  - Retention summary with action link
  - Direct link to opt-out and full guide

- **guide/ultimate-guide.md** - Section 2.6 "Data Flow & Privacy" (~45 lines)
  - Data types sent table
  - Retention policies table
  - Link to dedicated guide
  - Updated TOC and quick jump navigation

- **tools/onboarding-prompt.md** - Phase 0.5 Privacy Awareness
  - Privacy notice shown after level assessment
  - Asks user about privacy settings configuration

- **tools/audit-prompt.md** - Privacy configuration checks
  - Phase 1.2: PRIVACY CONFIGURATION bash checks
  - Phase 2.1: Privacy Configuration checklist
  - Glossary: "Data Retention" and "excludePatterns" terms

- **examples/scripts/audit-scan.sh** - PRIVACY CHECK section
  - Human output: .env exclusion check, DB MCP warning, opt-out link
  - JSON output: `"privacy"` object with env_excluded, has_db_mcp, opt_out_link, guide_link

- **examples/scripts/check-claude.sh** - Privacy reminder section
  - Shows retention info and opt-out link during health check

- **examples/hooks/bash/privacy-warning.sh** - SessionStart hook (NEW)
  - Displays privacy reminder box once per terminal session
  - Suppresses with `PRIVACY_WARNING_SHOWN=1` env var

- **guide/cheatsheet.md** - Golden Rule #7 added
  - "Know what's sent — prompts, files, MCP results → Anthropic"

### Stats
- 2 new files created (data-privacy.md, privacy-warning.sh)
- 8 files modified (README, guide, cheatsheet, audit-scan, check-claude, onboarding, audit-prompt)
- Focus on user awareness of data retention and actionable opt-out

## [3.1.0] - 2026-01-13

### Changed
- **Major repository restructuring** - Reorganized 15 root files into 4 thematic directories
  - `guide/` - Core documentation (ultimate-guide.md, cheatsheet.md, adoption-approaches.md)
  - `tools/` - Interactive utilities (audit-prompt.md, onboarding-prompt.md, mobile-access.md)
  - `machine-readable/` - LLM/AI consumption (reference.yaml, llms.txt)
  - `exports/` - Generated outputs (notebooklm.pdf, kimi.pdf)
- **File renaming** for cleaner paths:
  - `english-ultimate-claude-code-guide.md` → `guide/ultimate-guide.md`
  - `cheatsheet-en.md` → `guide/cheatsheet.md`
  - `claude-setup-audit-prompt.md` → `tools/audit-prompt.md`
  - `personalized-onboarding-prompt.md` → `tools/onboarding-prompt.md`
  - `mobile-access-setup.md` → `tools/mobile-access.md`
  - `claude-code-reference.yaml` → `machine-readable/reference.yaml`
- **README.md** - Added "Repository Structure" section with visual tree
- **150+ internal links updated** across all documentation files
- **Deleted** empty `to-ignore/` directory

### Added
- `guide/README.md` - Index for core documentation folder
- `tools/README.md` - Index for interactive utilities folder
- `machine-readable/README.md` - Index for LLM consumption folder
- `exports/README.md` - Index for generated outputs folder

### Stats
- 10 files moved to new locations
- 4 new README.md files created
- 150+ links updated
- Navigation significantly improved

## [3.0.7] - 2026-01-13

### Added
- **mobile-access-setup.md** - Mobile access guide for Claude Code (NEW, WIP/UNTESTED)
  - Problem statement: Claude Code lacks native session relay/sync across devices
  - Solution: ttyd + Tailscale for ToS-safe mobile access
  - Complete setup script with tmux for persistent sessions
  - Security considerations and ToS compliance notes
  - Alternatives comparison (Happy Coder, Claude Code Web, tmux+SSH)
  - Troubleshooting guide
  - Marked as WIP/UNTESTED - community feedback welcome

- **README.md** - Added mobile access guide to navigation table
  - New row: "Want mobile access to Claude Code" → Mobile Access Setup → WIP

### Stats
- 1 new file created (mobile-access-setup.md, ~300 lines)
- 2 files modified (README.md, cheatsheet-en.md version bump)
- Focus on ToS-safe remote access without third-party wrappers

## [3.0.6] - 2026-01-13

### Changed
- **Documentation honesty overhaul** - Removed marketing language and unverified claims
  - **README.md** (~12 edits):
    - Added transparency disclaimer after badges
    - Changed "Transform...superpower" → factual description of content
    - Changed "Our Solution: in hours, not weeks" → honest framing
    - Replaced time estimates with depth categories (Essentials, Foundation, Intermediate, Comprehensive)
    - Fixed "2 seconds" claims → "Quick (~30 seconds)"
    - Corrected privacy claim ("Everything runs locally" → accurate API explanation)
    - Changed "mentor for Claude Code mastery" → "structured learning companion"
  - **english-ultimate-claude-code-guide.md** (~15 edits):
    - Added "Before You Start" disclaimer section at top
    - Removed "Guide Status 100% Complete" table (false certainty)
    - Added qualifying note after context thresholds table
    - "90% of daily usage" → "the ones I use most frequently"
    - "20-30% faster" → subjective productivity indicators
    - "Saves 30-40%" → "Frees significant context space"
    - Removed invented ROI table with fake calculations
    - "Never guesses - always verifies" → with LLM hallucination warning
    - Removed "12,400% ROI" ridiculous claim
    - "90% of tasks" → "most common tasks"
    - "80-90% savings" → "significant (varies by project)"
  - **adoption-approaches.md** (already in 3.0.5):
    - Added disclaimer about Claude Code being young (~1 year)
    - Added "What We Don't Know Yet" section
    - Changed prescriptive language to tentative observations

### Stats
- 3 files modified (README.md, english-ultimate-claude-code-guide.md, cheatsheet-en.md)
- ~30 edits removing invented percentages, times, and marketing claims
- Focus on honest, qualified observations over false authority

## [3.0.5] - 2026-01-13

### Added
- **adoption-approaches.md** - Comprehensive adoption philosophy guide (NEW, ~355 lines)
  - Addresses community feedback: "turnkey setup" vs "autonomous learning" approaches
  - **Decision Tree** for immediate routing based on context (time, team size, uniqueness)
  - **Turnkey Quickstart** (15 min) with 3 verifiable steps
  - **Autonomous Learning Path** with 4 phases + time estimates + line references
  - **Adoption Checkpoints** with pass/fail criteria (Day 1, Week 1, Week 2, Month 1)
  - **Anti-patterns** table with symptoms and solutions
  - **Team Size Guidelines** with config structures for solo/4-10/10+ developers
  - **Scenario Decisions**: CTO evaluation, team disagreements, inherited configs, upgrade triggers
  - **Quick Reference**: daily commands table + cost-conscious model selection
  - Aligns with `claude-code-reference.yaml` patterns (decision trees, line refs, context zones)

### Changed
- **README.md** - Added adoption guide to "Not Sure Where to Start?" navigation table
  - New row: "Choosing turnkey vs. autonomous approach" → Adoption Guide → 5 min

### Stats
- 1 new file created (adoption-approaches.md, ~355 lines)
- 1 file modified (README.md, +1 line)
- Focus on helping users choose the right adoption strategy for their context

## [3.0.4] - 2026-01-13

### Added
- **examples/commands/diagnose.md** - Interactive troubleshooting assistant (NEW)
  - Bilingual support (FR/EN) with automatic language detection
  - 12 problem categories: permissions, MCP servers, config, performance, installation, agents/skills
  - Auto-fetches latest guide from GitHub for up-to-date troubleshooting data
  - Integrates with `audit-scan.sh --json` for environment scanning
  - Structured diagnostic output: root cause → solution → template → reference
  - Common patterns documented: repeated permission prompts, MCP not found, context saturation
  - Usage: Copy to `~/.claude/commands/` then invoke with `/diagnose`

### Changed
- **README.md** - Added `/diagnose` to commands table and navigation
- **examples/README.md** - Added `/diagnose` to commands index
- **cheatsheet-en.md** - Version bump to 3.0.4

### Stats
- 1 new file created (diagnose.md, ~210 lines)
- 3 files modified (README.md, examples/README.md, cheatsheet-en.md)
- Focus on self-service troubleshooting for common Claude Code issues

## [3.0.3] - 2026-01-13

### Enhanced
- **audit-scan.sh v2.0** - Major improvements based on community feedback (2 test projects)
  - **P0.1: MCP Detection globale** - Now detects both project-specific AND global MCPs from `~/.claude.json`
    - Previously only checked `projects[path].mcpServers`, now also checks top-level `mcpServers`
    - Shows separate counts: project MCPs vs global MCPs with their sources
  - **P0.2: MCP documented vs configured** - New feature detecting MCPs mentioned in CLAUDE.md but not actually configured
    - Scans CLAUDE.md files for known MCPs (serena, context7, sequential, playwright, morphllm, magic, filesystem)
    - Warns when MCP is documented but missing from config: "Documented but NOT configured: serena"
    - Helps catch configuration drift
  - **P1.1: +35 integrations detected** - Expanded from ~25 to ~60 packages
    - Chat/Communication: TalkJS, Knock, Stream
    - Maps: MapLibre, Mapbox, Google Maps
    - File Upload: Bytescale, UploadThing, Cloudinary
    - Admin: Forest Admin, Refine
    - Validation: Zod, Yup, Valibot
    - UI Libraries: Chakra UI, Material UI, DaisyUI, Mantine
    - Database providers: Neon, PlanetScale, Vercel Postgres, Upstash, Turso
    - Analytics: Vercel Analytics, Mixpanel, Hotjar, Amplitude
    - Feature flags: Vercel Flags, LaunchDarkly
    - Forms: React Hook Form, Formik
    - Auth: Kinde
    - Payments: LemonSqueezy
    - AI: Vercel AI SDK
    - CMS: Payload CMS
    - State: Jotai
  - **P1.2: Test framework warning** - Now explicitly warns when no test framework detected
    - Checks package.json deps, config files (jest.config.*, vitest.config.*), and test file patterns
    - Shows ❌ "No test framework detected" in quality patterns
  - **P1.3: MCP Recommendations** - Context-aware suggestions based on detected stack
    - context7 recommended for modern frameworks (Next.js, React, Vue, etc.)
    - sequential-thinking for complex architectures (with DB or NestJS/Next.js)
    - playwright for projects without E2E testing
    - serena for TypeScript projects
  - **P2.1: Extended SSoT detection** - Now searches for @refs in codebase even without CLAUDE.md
    - If >5 files contain `@*.md` references, considers SSoT pattern adopted
  - **P2.2: shadcn/ui detection** - Special case handling (not in package.json)
    - Detects presence of `components/ui/` or `src/components/ui/` folders
  - **JSON output enhanced** with new fields:
    - `quality.has_test_framework` (boolean)
    - `mcp.project_servers`, `mcp.global_servers` (separated)
    - `mcp.documented`, `mcp.missing` (doc vs config gap)
    - `mcp.recommendations` (stack-based suggestions)
  - **Human output enhanced**:
    - New "🔌 MCP SERVERS" section with project/global breakdown
    - Warning for documented but unconfigured MCPs
    - Recommendations displayed with 💡 icon

### Fixed
- **audit-scan.sh** - `ALL_DEPS` unbound variable error when running outside Node.js projects
  - Initialized `ALL_DEPS=""` before conditional blocks

### Stats
- 1 file modified (audit-scan.sh, ~200 lines added/modified)
- Integration detection improved from ~25 to ~60 packages
- MCP detection now covers all configuration locations
- Based on feedback from Native Spaces (venue booking) and Méthode Aristote (EdTech) projects

## [3.0.2] - 2026-01-12

### Added
- **personalized-onboarding-prompt.md** - Interactive onboarding prompt (~200 lines)
  - Multilingual support: User chooses preferred language first
  - 3 experience levels: Beginner (🟢), Intermediate (🟡), Power User (🔴)
  - Progressive exploration with deeper/next/skip controls
  - Tailored learning paths per level
  - Optional practical exercises
  - Self-paced interactive Q&A format

- **README.md** - Added onboarding prompt to "Not Sure Where to Start?" table
  - New row: "Want a guided tour" → Personalized Onboarding → ~15 min

### Stats
- 1 new file created (personalized-onboarding-prompt.md, ~200 lines)
- 1 file modified (README.md)
- Focus on accessible, multilingual onboarding experience

## [3.0.1] - 2026-01-12

### Added
- **Custom Statusline Setup** documentation
  - New section in `english-ultimate-claude-code-guide.md` (lines 990-1027)
  - [ccstatusline](https://github.com/sirmalloc/ccstatusline) as recommended solution
  - Enhanced statusline displays: model, git branch, file changes (+/-), context metrics
  - Custom script option with JSON stdin format
  - `/statusline` command reference for auto-generation
  - Added to `cheatsheet-en.md` (lines 130-133)

### Stats
- 2 files modified (english-ultimate-claude-code-guide.md ~38 lines, cheatsheet-en.md ~4 lines)
- Focus on developer experience and terminal customization

## [3.0.0] - 2026-01-12

### Added
- **quiz/** - Interactive CLI quiz to test Claude Code knowledge (MAJOR FEATURE)
  - 159 curated questions across 10 categories (matching guide sections)
  - 4 user profiles: Junior (15q), Senior (20q), Power User (25q), PM (10q)
  - Immediate feedback with explanations and documentation links
  - Score tracking with category breakdown and weak area identification
  - Session persistence to `~/.claude-quiz/` for progress history
  - Replay options: retry wrong questions or start fresh quiz
  - Optional dynamic question generation via `claude -p`
  - Cross-platform: Node.js (works on macOS, Linux, Windows)

- **README.md** - New "Knowledge Quiz" section in navigation
  - Added quiz to "Not Sure Where to Start?" table
  - Collapsible example session showing quiz flow
  - Links to quiz documentation and contribution template

### Files Created
```
quiz/
├── package.json           # Node.js config
├── README.md              # Full documentation with examples
├── src/
│   ├── index.js           # Entry point + CLI args
│   ├── ui.js              # Terminal display
│   ├── prompts.js         # User prompts (inquirer)
│   ├── questions.js       # YAML loading + filtering
│   ├── quiz.js            # Quiz engine
│   ├── score.js           # Score tracking
│   ├── session.js         # Persistence
│   └── dynamic.js         # claude -p generation
├── questions/             # 10 YAML files (159 questions)
└── templates/
    └── question-template.yaml
```

### Stats
- 20+ new files
- 159 questions covering all guide sections
- New learning tool for the community

## [2.9.9] - 2026-01-12

### Enhanced
- **audit-scan.sh** - SSoT refactor warning
  - New `needs_ssot_refactor` flag: true if CLAUDE.md >100 lines with 0 @references
  - Human output shows red warning suggesting SSoT pattern (split into @docs/)
  - JSON output includes `needs_ssot_refactor` in quality section

- **README.md** - Improved Full Audit prompt for incremental suggestions
  - Added IMPORTANT instruction to focus on incremental improvements, not generic advice
  - Health score now penalizes large CLAUDE.md without @refs
  - Quick wins must be domain-specific, not generic
  - If CLAUDE.md exists: suggest 3-5 improvements instead of full template
  - Agents/commands suggestions must not duplicate existing ones

### Stats
- 2 files modified
- Audit now provides targeted, incremental recommendations

## [2.9.8] - 2026-01-12

### Enhanced
- **audit-scan.sh** - Enhanced stack detection with detailed breakdown
  - Now detects: runtime, framework, test runner, bundler, database/ORM
  - Generic integration detection from package.json (auth, payments, AI, monitoring, etc.)
  - Works without jq (grep-based fallback for all JSON parsing)
  - Stack recap shown at top of human output
  - JSON output includes full `stack` object with all detected components

- **README.md** - Updated Full Audit prompt
  - Now requests Stack Recap as first output item
  - CLAUDE.md template increased from ~60 to ~100 lines
  - Added integration-aware suggestions in output description

### Fixed
- **audit-scan.sh** - jq fallback now works for MCP detection in ~/.claude.json

### Stats
- 2 files modified (audit-scan.sh ~150 lines added, README.md prompt updated)
- Detects 25+ common integrations (Clerk, Stripe, OpenAI, Sentry, etc.)

## [2.9.7] - 2026-01-12

### Enhanced
- **README.md** - Deep Audit now context-aware
  - Full Audit command now reads project's README.md, CLAUDE.md, and .claude/CLAUDE.md
  - Claude analyzes business domain to provide tailored recommendations
  - Domain-specific suggestions (EdTech → session agents, E-commerce → inventory commands)
  - Privacy notice: all data stays local, nothing sent back to repo

### Stats
- 1 file modified (README.md)
- Deep Audit now provides personalized, domain-aware recommendations

## [2.9.6] - 2026-01-12

### Fixed
- **audit-scan.sh** - Count files recursively in subfolders
  - Commands in subfolders (e.g., `commands/tech/`, `commands/product/`) now counted
  - Split into `count_md_files()` for .md and `count_script_files()` for hooks (.sh/.js/.py/.ts)
  - Excludes README.md from counts
  - Bug found: Was reporting 0 commands when 10 existed in subfolders

### Stats
- 1 file modified (audit-scan.sh, ~15 lines)
- Critical fix for accurate extension counting

## [2.9.5] - 2026-01-12

### Added
- **README.md** - Deep Audit section with one-liner commands
  - New row in "Not Sure Where to Start?" table
  - `🔬 Deep Audit` section with two options:
    - Quick Version (~10 sec): Single curl pipe to Claude
    - Full Audit (~30 sec): Downloads YAML reference + scan for comprehensive analysis
  - Outputs: Health score, prioritized findings, CLAUDE.md template, suggested extensions

### Stats
- 1 file modified (README.md, ~35 lines added)
- Focus on one-command personalized audit experience

## [2.9.4] - 2026-01-12

### Added
- **examples/modes/** - New folder for behavioral modes
  - `MODE_Learning.md` - Complete Learning Mode ready to copy to `~/.claude/`
  - `README.md` - Installation guide with SuperClaude framework reference
- **examples/README.md** - Updated with modes folder and templates

### Stats
- 2 new files created (MODE_Learning.md, modes/README.md)
- 1 file modified (examples/README.md)
- Focus on making SuperClaude Learning Mode plug-and-play

## [2.9.3] - 2026-01-12

### Added
- **README.md** - LLM Reference section with curl one-liner
  - New row in "Not Sure Where to Start?" table
  - `🤖 LLM Reference` section with instant curl command
  - Use cases: ChatGPT/Claude/Gemini context, system prompts, `@` reference
  - Clarification that YAML points to line numbers in full guide for deep dives
- **english-ultimate-claude-code-guide.md** - Learning Mode documentation (~136 lines)
  - SuperClaude Behavioral Modes overview table
  - Complete Learning Mode installation guide (4 steps)
  - Usage examples with `--learn`, `--learn focus:X`, `--learn batch` flags
  - Offer format examples (standard and token-efficient)
  - Integration matrix with other modes
  - Priority rules and example session
- **claude-code-reference.yaml** - Learning mode additions
  - `deep_dive` refs: superclaude_modes, learning_mode
  - `decide` section: learning flag
  - `cli` section: --learn, --learn focus:X, --no-learn flags

### Stats
- 3 files modified (README.md, english-ultimate-claude-code-guide.md, claude-code-reference.yaml)
- ~150 lines added across files
- Focus on LLM context sharing and SuperClaude Learning Mode documentation

## [2.9.2] - 2026-01-12

### Added
- **claude-code-reference.yaml** - Machine-optimized LLM index (~2K tokens)
  - **Decision tree** as first section (most used lookup)
  - **Prompting formula** (WHAT/WHERE/HOW/VERIFY pattern)
  - **38 deep_dive line references** to english-ultimate-claude-code-guide.md
  - 22 sections covering: commands, shortcuts, CLI flags, context management, memory files, MCP servers, think levels, cost optimization, anti-patterns, troubleshooting
  - Flat YAML structure (max 1 level nesting) for optimal LLM parsing
  - ~97% token reduction vs full guide (2K vs 70K tokens)
- **README.md** - Added LLM Reference row in Core Documentation table
- **llms.txt** - Added Machine-Optimized Reference section with YAML file description

### Stats
- 1 new file created (claude-code-reference.yaml, 282 lines)
- 2 files modified (README.md, llms.txt)
- Use case: Claude Code self-reference for fast user question answering

## [2.9.1] - 2026-01-12

### Fixed
- **Cheatsheet completeness audit** (cheatsheet-en.md, ~15 lines modified)
  - **Missing commands added**:
    - `/execute` - Exit Plan Mode (counterpart to `/plan`)
    - `/model` - Switch model (sonnet/opus/opusplan)
  - **Missing keyboard shortcuts added**:
    - `Ctrl+R` - Retry last operation
    - `Ctrl+L` - Clear screen (keeps context)
  - **Missing CLI flags added**:
    - `-c` / `--continue` - Continue last session
    - `-r` / `--resume <id>` - Resume specific session
    - `--headless` - Non-interactive (CI/CD)
  - **Missing maintenance command added**:
    - `claude update` - Check/install updates
  - **Inconsistency fixed**:
    - Removed false `/resume` slash command from Context Recovery Commands
    - Replaced with correct CLI flags (`claude -c`, `claude -r <id>`)
  - **Clarification**:
    - `/status` vs `/context` descriptions clarified (session state vs detailed token breakdown)
  - Cheatsheet version: 2.8 → 2.8.1

### Stats
- 1 file modified (cheatsheet-en.md)
- Audit coverage improved from ~36% to ~85% of documented commands
- Format preserved: 377 lines, 1-page printable maintained

## [2.9.0] - 2026-01-12

### Fixed
- **MCP detection bug in audit-scan.sh** (~60 lines modified)
  - **Root cause**: Script searched for `~/.claude/mcp.json` which doesn't exist
  - **Actual location**: Claude Code stores MCP config in `~/.claude.json` under `projects.<path>.mcpServers`
  - **Solution**: Multi-source detection with priority:
    1. `~/.claude.json` → `projects.<cwd>.mcpServers` (most common)
    2. `./.claude/mcp.json` (project-level)
    3. `~/.claude/mcp.json` (legacy global)
  - JSON output now includes detailed `mcp` section (configured, count, servers, source)
  - Human output shows server count and source location
- **Bug `0\n0` in `claude_md_refs`** (~8 lines)
  - **Root cause**: `grep -c ... || echo "0"` could produce double output
  - **Solution**: Rewritten `count_pattern()` function to properly capture and return count

### Changed
- **audit-scan.sh** enhanced (~50 lines)
  - Added `MCP_SOURCE` variable to track where MCP config was found
  - Added `MCP_COUNT` variable for server count
  - Global `mcp.json` message changed from error to info (not required)
  - JSON output restructured with separate `mcp` object
- **claude-setup-audit-prompt.md** updated (~40 lines)
  - Phase 1.1: Now checks `~/.claude.json` instead of `~/.claude/mcp.json`
  - Phase 1.2: Complete MCP detection rewrite covering all 3 locations
  - Glossary: Updated MCP definition to explain config locations
  - Version: 2.8 → 2.9

### Stats
- 2 files modified (audit-scan.sh, claude-setup-audit-prompt.md)
- Bug impact: Scripts now correctly detect MCP servers (was showing "No MCP" even when configured)
- Tested: Verified on Méthode Aristote project with 9 MCP servers

## [2.8.0] - 2026-01-11

### Added
- **Verified CLI commands and flags from Medium article analysis** (~61 lines)
  - **Section 1.1 "Updating Claude Code"** (lines 210-241)
    - `claude update` command - Check and install available updates
    - `claude doctor` command - Verify auto-updater health and system integrity
    - Maintenance commands reference table with usage guidance
    - Update frequency recommendations (weekly, before major work, after system changes)
    - Alternative npm update method documented
  - **Section 10.1 Built-in Commands** (line 7746)
    - `/output-style` - Change response format (concise/detailed/code)
    - `/feedback` - Report bugs or send feedback to Anthropic (renamed from `/bug`)
  - **Section 10.3 CLI Flags Reference** (lines 7837, 7848)
    - `--json-schema <schema>` - JSON Schema for structured output validation
    - `--max-budget-usd <amount>` - Maximum API spend limit (with `--print` only)
  - **Section 10.4 Quick Diagnostic Guide** (lines 7893-7913)
    - Symptom-based troubleshooting table with 8 common scenarios
    - Quick Fix + Prevention columns for rapid issue resolution
    - 5-step diagnosis flow (context → connectivity → configuration → permissions → doctor)
    - Covers: context overflow, rate limits, MCP issues, permission prompts, session corruption

- **README.md navigation improvements** (~50 lines)
  - Decision Helper table after Quick Start (6 user personas with direct links)
  - Moved Audit section to prominent position after Quick Start
  - Reframed AI admission from apologetic to professional tone
  - Added Prerequisites section (Node.js, API key, cost estimate)
  - Outcome-based Guide Navigation ("After this, you can...")
  - Consolidated PDFs/DeepWiki into collapsible `<details>` section
  - Shortened Windows disclaimer (5 lines → 1 line)
  - Added GitHub Actions section to Production-Ready Examples
- **examples/README.md catalog completion**
  - Added `github-actions/` folder to Structure table (3 CI/CD workflows)
  - Added `workflows/` folder to Structure table (database branch setup)
  - Complete Templates Index with all 9 example categories

### Changed
- **Verification methodology improvements**
  - All additions verified via `claude --help` output or direct user testing
  - Rejected 6+ unverified elements from Medium article (false positives and non-existent commands)
  - Avoided documenting 16 already-present elements (prevented redundancy)
  - Maintained guide credibility by only adding 100% confirmed features
- **README.md restructured** for better first-time user experience
  - Clear decision support for new users ("Not Sure Where to Start?")
  - Audit tool more discoverable (moved from buried position)
  - Professional AI disclosure without being apologetic

### Stats
- Guide expanded from 8,787 to 8,848 lines (+61 lines, +0.7%)
- 6 sections modified (Installation, Commands Table, CLI Flags, Troubleshooting, README, examples/README)
- Focus on maintenance commands, structured output, rapid diagnostics, and navigation UX
- Verification ratio: 7 confirmed additions / 22 rejected claims (~32% valid from source article)
- README improvements: Decision Helper, Audit visibility, GitHub Actions showcase

## [2.7.0] - 2026-01-11

### Added
- **Audit optimization with bash scanning** (~350 lines across 4 files)
  - **examples/scripts/audit-scan.sh** (NEW, ~230 lines)
    - Fast Claude Code setup scanner with dual output modes
    - JSON output (`--json`) for Claude processing
    - Human-readable output (default) with color-coded results (✅/❌/⚠️)
    - Scans: global config (~/.claude/), project config (./CLAUDE.md, .claude/), extensions (agents/commands/skills/hooks/rules)
    - Tech stack auto-detection (Node.js, Python, Go, Rust, PHP via manifest files)
    - Quality pattern checks: security hooks (PreToolUse), SSoT references (@refs), MCP servers
    - Performance: ~80% faster than file-reading approach (~2s vs ~30s)
    - Token efficiency: ~90% reduction (~500 tokens vs ~5000 tokens)
  - **claude-setup-audit-prompt.md Phase 1-2 rewrite** (~120 lines modified)
    - Phase 1.1 "Quick Configuration Scan" replaced file reads with bash commands
    - Phase 1.2 "Quality Pattern Checks" uses grep/wc/find for targeted validation
    - Phase 1.3 references external audit-scan.sh for comprehensive scanning
    - Added "Efficient Guide Reference Lookup" with sed line range extraction
    - Reduced audit time estimate from ~5-10 minutes to ~2-3 minutes
    - Version updated: 2.1 → 2.2
  - **examples/README.md scripts section** (~20 lines)
    - Added `scripts/` folder to structure table
    - Scripts table documenting 3 utility scripts (audit-scan.sh, check-claude.sh, clean-reinstall-claude.sh)
    - Usage examples for both JSON and human-readable output modes
  - **README.md "Audit Your Setup" section rewrite** (~60 lines)
    - Two-option approach: Quick Bash Scan (2 seconds) vs Claude-powered audit (2-3 minutes)
    - Performance comparison: "~80% faster scanning and 90% fewer tokens"
    - Option 1: Direct script execution with curl download example
    - Option 2: Claude-powered analysis referencing audit prompt
    - Clear usage instructions for both `--json` and default modes

### Changed
- **Version alignment** across documentation
  - README.md: Version 2.6 → 2.7
  - english-ultimate-claude-code-guide.md: Already at 2.7
  - claude-setup-audit-prompt.md: Version 2.1 → 2.2

### Stats
- 1 new file created (audit-scan.sh, ~230 lines)
- 4 files modified (claude-setup-audit-prompt.md, examples/README.md, README.md, CHANGELOG.md)
- Performance improvement: 80% faster scanning, 90% token reduction
- Focus on efficiency, developer experience, and programmatic auditing
- Script supports both human-readable and machine-readable (JSON) output

## [2.6.0] - 2026-01-11

### Added
- **Section 8.5: Plugin System** (~245 lines, comprehensive documentation)
  - **Plugin System fundamentals** (lines 4836-5073)
    - What are plugins: packaged agents, skills, commands, domain-specific tooling
    - Plugin commands table: install, enable, disable, uninstall, update, validate
    - Marketplace management: add, list, update, remove marketplaces
    - Using plugins workflow from marketplace to session usage
    - Plugin session loading with `--plugin-dir` flag for testing
  - **When to Use Plugins** decision matrix
    - Team workflows: Share standardized agents/skills via private marketplace
    - Domain expertise: Pre-built security, accessibility, performance plugins
    - Repeating patterns: Package custom workflows for reuse
    - Community solutions: Leverage community expertise
  - **Creating Custom Plugins** guide
    - Directory structure with manifest (plugin.json)
    - Example security-audit plugin manifest
    - Validation command: `claude plugin validate ./my-plugin`
  - **Plugin vs. MCP Server** comparison table
    - Plugin = "How Claude thinks" (workflows, specialized agents)
    - MCP Server = "What Claude can do" (tools, external systems)
    - Clear guidance on when to use which
  - **Security Considerations** section
    - Before installing: trust source, review manifest, test in isolation
    - Red flags: network access without reason, obfuscated code, no documentation
  - **Example Use Cases** with real workflows
    - Team Code Standards Plugin (private marketplace)
    - Security Audit Suite (community plugin)
    - Accessibility Testing (a11y plugin with WCAG compliance)
  - **Troubleshooting** guide
    - Plugin not found after install
    - Plugin conflicts resolution
    - Plugin not loading in session
- **Keyboard Shortcut: `Esc×2` double-tap** (line 7487)
  - Added to Section 10.2 Keyboard Shortcuts table
  - Clarifies double-tap pattern: Rewind to previous checkpoint (same as `/rewind`)
  - Resolves inconsistency between TL;DR mention and shortcuts table
- **Plugin command** in Section 10.1 Commands Table (line 7696)
  - `/plugin` command: Manage Claude Code plugins (Config category)
- **Plugin flag** in Section 10.3 CLI Flags Reference (line 7782)
  - `--plugin-dir`: Load plugins from directory (repeatable flag)

### Changed
- **Table of Contents updated** (line 147)
  - Added [8.5 Plugin System](#85-plugin-system) entry
- **Section 8 Quick Jump navigation enhanced** (line 4530)
  - Added Plugin System link to quick navigation bar
- **TL;DR Power Features table** (line 80)
  - Added "Plugins: Community-created extension packages" row
- **Version alignment** across documentation
  - english-ultimate-claude-code-guide.md: Version 2.5 → 2.6
  - README.md: Version 2.5 → 2.6

### Stats
- Guide expanded from 8,545 to 8,787 lines (+242 lines, +2.8%)
- Plugin System section: ~245 lines of comprehensive documentation
- 1 keyboard shortcut clarified (Esc×2)
- 2 command/flag additions (/plugin, --plugin-dir)
- Focus on extensibility and community-driven functionality
- Zero loss of existing functionality

## [2.5.0] - 2026-01-11

### Removed
- **Content cleanup and optimization** (~1048 lines removed, -10.9%)
  - **DeepSeek Integration section** (~200 lines, lines 9123-9321)
    - Third-party provider documentation not specific to Claude Code
    - Replaced reference in configuration table with generic "Alternative auth token"
  - **Git Archaeology Pattern** (~250 lines, lines 8834-9081)
    - General Git technique, not Claude Code-specific
  - **Emergency Hotfix Checklist** (~140 lines, lines 8695-8832)
    - Generic development workflow, not specific to Claude Code
  - **Maturity Model & Success Metrics** (~95 lines, lines 8544-8691)
    - Gamification content that added weight without Claude Code value
  - **Prompt Templates** (~105 lines, lines 8437-8542)
    - Generic prompt templates not specific to Claude Code
  - **Task-specific checklists** (Bug Fix, Feature, Code Review, Refactoring)
    - General development checklists, not Claude Code workflows
  - **Community Resources fictional dates** (table column removed)
    - Removed "Last Updated" column with fictional future dates (Apr 2025, Oct 2025, Jul 2025, Aug 2025)
    - Reduced from 5 to 3 essential awesome-lists

### Changed
- **Health Check Scripts externalized** to `examples/scripts/`
  - Replaced ~90 lines of inline PowerShell/Bash scripts with links
  - Created `examples/scripts/check-claude.sh` (macOS/Linux health check)
  - Created `examples/scripts/check-claude.ps1` (Windows health check)
  - Main guide now references external scripts for maintainability
- **Clean Reinstall Scripts externalized** to `examples/scripts/`
  - Replaced ~75 lines of inline reinstall procedures with links
  - Created `examples/scripts/clean-reinstall-claude.sh` (macOS/Linux reinstall)
  - Created `examples/scripts/clean-reinstall-claude.ps1` (Windows reinstall)
  - Improves separation of concerns (guide vs utilities)
- **Nick Tune reference condensed**
  - Reduced from ~40 lines to 3 lines with link only
  - Kept attribution but removed excessive detail
- **Daily Workflow & Checklists streamlined**
  - Removed generic checklists (Bug Fix, Feature, Code Review, Refactoring)
  - Kept only Claude Code-specific parts (Daily Workflow, Prompt Quality)
- **Table of Contents cleaned**
  - Removed obsolete references to A.8 (Prompt Templates) and A.9 (Success Metrics)
  - Fixed document structure coherence

### Fixed
- Version consistency across documentation (2.4 aligned)
- Code block balance verification (673 markers, properly balanced)
- Removed broken internal references to deleted sections

### Stats
- Document reduced from 9,593 to 8,545 lines (-1,048 lines, -10.9%)
- 4 new script files created in examples/scripts/ (~350 lines externalized)
- Focus shifted to Claude Code-specific content only
- Improved maintainability through script externalization
- Zero loss of essential Claude Code functionality

## [2.4.0] - 2026-01-10

### Added
- **Database Branch Isolation with Git Worktrees** (~540 lines across 3 files)
  - **examples/commands/git-worktree.md** enhanced (~90 lines added)
    - Database provider auto-detection (Neon, PlanetScale, Local Postgres, Supabase)
    - Suggested commands for DB branch creation per provider
    - `.worktreeinclude` setup documentation for .env copying
    - "When to Create Database Branch" decision table
    - Cleanup commands including DB branch deletion
    - Common mistakes section expanded with DB-related pitfalls
  - **examples/workflows/database-branch-setup.md** (NEW, ~350 lines)
    - Complete provider-specific setup guides (Neon, PlanetScale, Local Postgres)
    - TL;DR section for 90% use case (Neon quick start)
    - Provider comparison table with branching capabilities
    - 3 isolation patterns: Cloud branching, Local schema, Shared DB
    - Decision tree for choosing DB isolation strategy
    - Real-world workflow examples with commands
    - Troubleshooting section with common issues
    - Prerequisites and CLI installation per provider
  - **english-ultimate-claude-code-guide.md** Section 9.12 enhanced (~95 lines)
    - "Database Branch Isolation with Worktrees" new subsection
    - Problem/Solution framing for schema conflicts
    - Provider detection explanation
    - "When to create DB branch" decision table
    - Complete workflow example with Neon
    - Prerequisites for all major providers
    - Links to detailed workflow guide
  - **Source attribution**: [Neon database branching](https://neon.tech/docs/guides/branching) and [PlanetScale branching workflows](https://planetscale.com/docs/concepts/branching)

### Changed
- **Guide statistics updated**
  - Guide expanded from 9,700+ to 9,592 lines (optimized structure, net -108 lines)
  - Content reorganized for better progressive disclosure
  - Reduced redundancy through single source of truth pattern
- **Documentation architecture improved**
  - Command reference (git-worktree.md) kept concise and scannable
  - Detailed workflows separated into dedicated guide
  - Clear separation: Quick Reference → Complete Tutorial

### Stats
- 1 new file created (workflows/database-branch-setup.md, ~350 lines)
- 3 files modified (git-worktree.md +90, guide +95, examples/README.md)
- Focus on database isolation patterns for modern dev workflows
- Maintenance-friendly: Single source of truth for provider commands

## [2.3.0] - 2026-01-10

### Added
- **DeepTo Claude Code Guide integration** (~800 lines across 5 sections)
  - **Image Processing** (Section 2.3.2, lines 377-445)
    - Direct image input via paste/drag-drop in terminal
    - Screenshot analysis, UI debugging, error message analysis
    - Best practices for image-based workflows
    - Supported formats: PNG, JPG, GIF, WebP, screenshots
  - **Session Continuation and Resume** (Section 2.3.4, lines 447-560)
    - `claude --continue` / `-c` to resume last session
    - `claude --resume <id>` / `-r <id>` for specific sessions
    - Use cases table: long-term projects, research, interrupted work, daily workflows
    - Context preservation across terminal sessions
    - Integration with MCP Serena for persistent memory
  - **XML-Structured Prompts** (Section 2.6, lines 1582-2148)
    - Semantic organization using `<instruction>`, `<context>`, `<code_example>`, `<constraints>`, `<output>` tags
    - Benefits table: disambiguation, role clarity, example isolation, constraint definition
    - 3 practical examples: code review, feature implementation, bug investigation
    - Advanced patterns: nested tags, multiple examples, conditional instructions
    - Integration with CLAUDE.md and Plan Mode
    - Template library for common scenarios
  - **ccusage CLI Tool** (Section 3.5.3, around line 970)
    - Detailed cost analytics and tracking
    - Model-specific breakdowns (Haiku/Sonnet/Opus)
    - Token usage analysis and optimization insights
    - Installation and usage instructions
  - **Unix Piping Workflows** (Section 9.3.3, line 4490)
    - Feeding content to Claude via stdin pipes
    - Output format options (text, json, markdown)
    - Build script integration patterns
    - CI/CD pipeline examples (linting, testing, security)
    - Automated analysis and report generation
  - **DeepTo Guide reference** added to README.md Resources section
    - Listed alongside zebbern, Claudelog, and ykdojo guides
    - Brief description covering all integrated concepts
  - **Source attribution** included in all new sections
    - Proper credit to https://cc.deeptoai.com/docs/en/best-practices/claude-code-comprehensive-guide
    - Following same attribution format used for other community guides

### Changed
- **Guide statistics updated**
  - Guide expanded to approximately 9,700+ lines (+800 lines from DeepTo integration)
  - Enhanced coverage of context management, structured prompting, and automation
- **README.md Resources section enhanced**
  - Added DeepTo Claude Code Guide to Related Guides

### Stats
- 0 new files created (documentation enhancement only)
- 3 files modified (README.md, english-ultimate-claude-code-guide.md, CHANGELOG.md)
- Focus on advanced prompting techniques, cost optimization, and automation workflows
- Integration of community best practices from DeepTo guide

## [2.2.0] - 2026-01-10

### Added
- **ykdojo/claude-code-tips reference integration** (~300 lines, 6 tips)
  - Added to References section in README.md (2 locations: Key inspirations + Related Guides)
  - Added to Learning Sites table in guide (Section 10.3.3, lines 8277, 8500)
  - Listed as peer guide alongside Claudelog and zebbern
  - **Tip 1: Undocumented Commands** integrated in Section 10.1 Commands Table
    - `/usage` - Check rate limits and token allocation
    - `/stats` - View usage statistics with activity graphs
    - `/chrome` - Toggle native browser integration
    - `/mcp` - Manage Model Context Protocol servers
  - **Tips 3+4+8: Keyboard Shortcuts** integrated in Section 10.2
    - Restructured with 2 categories: "Session Control" + "Input & Navigation"
    - `Ctrl+A` - Jump to beginning of line
    - `Ctrl+E` - Jump to end of line
    - `Ctrl+W` - Delete previous word
    - `Ctrl+G` - Open external editor for long text
    - `Ctrl+B` - Run command in background
  - **Tip 5: Session Handoff Pattern** new subsection in Section 2.2 (lines 1252-1308)
    - Complete template with 5 sections (Accomplished, Current State, Decisions, Next Steps, Context)
    - When-to-use table with 5 scenarios (end of day, context limit, switching focus, interruption, debugging)
    - Storage location: `claudedocs/handoffs/handoff-YYYY-MM-DD.md`
    - Pro tip: Ask Claude to generate handoff automatically
  - **Tip 12: GitHub Actions CLI Debugging** new subsection in Section 9.3 (lines 4445-4500)
    - Quick investigation workflow with `gh run` commands
    - Common commands table: list, view, view logs, watch, rerun
    - Practical example combining `gh` with Claude Code
    - Pro tip: Pipe failed logs directly to Claude for analysis
  - **Additional topics worth exploring** section added (lines 8516-8522)
    - 6 non-integrated but pertinent topics from ykdojo listed
    - Voice transcription workflows (superwhisper/MacWhisper)
    - Tmux for autonomous testing
    - cc-safe security tool
    - Cascade multitasking method
    - Container experimentation with Docker
    - Half-clone technique for context trimming

### Changed
- **Guide statistics updated**
  - Guide expanded from 8,505 to 8,929 lines (+424 lines, +5.0%)
  - Word count increased from ~31,280 to 33,219 words (+1,939 words, +6.2%)
  - Reading time updated: "~3 hours" → "~2h15min" (more precise estimate)
- **Version alignment** across documentation
  - english-ultimate-claude-code-guide.md: Version 2.1 → 2.2
  - README.md: Version 2.1 → 2.2
  - CHANGELOG.md: New release 2.2.0 documented

### Stats
- 0 new files created (documentation enhancement only)
- 3 files modified (README.md, english-ultimate-claude-code-guide.md, CHANGELOG.md)
- Guide grew by 424 lines (5.0% growth from v2.1.0)
- Focus on productivity techniques and terminal efficiency
- Integration of battle-tested workflows from Y.K. Dojo

## [2.1.0] - 2026-01-10

### Added
- **Production-ready slash commands** in examples/commands/ (~25 KB)
  - **pr.md** (5.8 KB) - PR creation with scope analysis
    - Complexity scoring algorithm (code files × 2 + tests × 0.5 + directories × 3 + commits)
    - Scope coherence detection (related vs unrelated changes)
    - Semi-automatic split suggestions with git commands
    - Conventional commit format enforcement
    - Complete PR template with TLDR + description + test checklist
  - **release-notes.md** (7.2 KB) - Generate release notes in 3 formats
    - CHANGELOG.md format (Keep a Changelog standard)
    - GitHub Release / PR body format
    - User announcement format (tech-to-product language transformation)
    - Database migration detection (Prisma, Sequelize, Django, Alembic)
    - Semantic versioning determination from commit types
  - **sonarqube.md** (11.3 KB) - Analyze SonarCloud quality issues for PRs
    - Environment variable configuration ($SONARQUBE_TOKEN, $SONAR_PROJECT_KEY)
    - Bash script wrapper to handle zsh authentication issues
    - Node.js analysis script for grouping issues by rule and severity
    - Executive summary with top violators and action plan
    - Severity mapping (BLOCKER/CRITICAL → 🔴, MAJOR → 🟡, MINOR/INFO → 🔵)
- **Production-ready hooks** in examples/hooks/bash/ (~6.5 KB)
  - **dangerous-actions-blocker.sh** (5.2 KB) - PreToolUse security hook
    - Blocks destructive commands (rm -rf /, fork bombs, dd if=, mkfs)
    - Blocks git force push to main/master branches
    - Blocks npm/pnpm/yarn publish without confirmation
    - Detects secrets in commands (password=, api_key=, token= patterns)
    - Protects sensitive files (.env, credentials.json, SSH keys, .npmrc)
    - Path validation with $ALLOWED_PATHS environment variable
    - Generic implementation using $CLAUDE_PROJECT_DIR with fallback to pwd
  - **notification.sh** (1.3 KB) - Notification hook with contextual macOS alerts
    - 5 contextual sound mappings (success, error, waiting, warning, default)
    - Keyword-based context detection (completed/done → Hero.aiff, error/failed → Basso.aiff)
    - Non-blocking background execution
    - Native macOS notifications with osascript
    - Multi-language support (English/French keywords)
- **Comprehensive hooks documentation**
  - **examples/hooks/README.md** (12.4 KB) - Complete hook system guide
    - Available hooks table with 6 hook examples across events
    - Hook events reference (PreToolUse, PostToolUse, UserPromptSubmit, Notification, SessionStart, SessionEnd, Stop)
    - Configuration guide with settings.json examples and matcher patterns
    - Creating custom hooks template with environment variables
    - Best practices (short timeout, fail gracefully, minimal logging)
    - Advanced examples (git context enrichment, activity logger, migration detector)
    - Troubleshooting section (permission issues, timeout errors, jq installation)
- **README.md improvements** for better discoverability
  - Moved "What's Inside" section to line 24 (immediately after intro, before "About This Guide")
  - Added examples/ row to table: "Production-ready commands, hooks, agents | Browse as needed"
  - **DeepWiki interactive documentation explorer** section
    - Link to https://deepwiki.com/FlorianBruniaux/claude-code-ultimate-guide/1-overview
    - 4 bullet points explaining features (natural language queries, contextual navigation, semantic search, on-demand summaries)
    - Tagline: "Perfect for quick lookups when you don't want to read the full 7500+ lines"
  - **Ready-to-Use Examples** section with comprehensive tables
    - Commands table: 6 commands with purpose and highlights (/pr, /release-notes, /sonarqube, /commit, /review-pr, /git-worktree)
    - Hooks table: 4 hooks with events and purposes (dangerous-actions-blocker, notification, security-check, auto-format)
    - Link to examples/README.md for full catalog
- **Guide documentation extensions** (english-ultimate-claude-code-guide.md)
  - **Section 1.3 "Quick Actions & Shortcuts"** expanded (~80 lines)
    - New subsection "Shell Commands with `!`" with 9 concrete examples
      - Quick status checks (!git status, !npm run test, !docker ps)
      - View logs (!tail -f, !cat package.json)
      - Quick searches (!grep -r "TODO", !find . -name "*.test.ts")
    - Comparison table: when to use `!` vs asking Claude
    - Example workflow showing both approaches
    - New subsection "File References with `@`" with usage patterns
      - Single file, multiple files, wildcards, relative paths
      - "Why use `@`" section: precision, speed, context, clarity
      - Comparative example showing with/without `@`
  - Section 10 TL;DR updated with "Copy ready-to-use templates → examples/ directory"
  - Appendix updated with note redirecting to examples/ for production-ready templates

### Changed
- **examples/README.md** updated with new entries
  - Commands table: Added /pr, /release-notes, /sonarqube rows
  - Hooks table: Added dangerous-actions-blocker.sh, notification.sh rows
  - Added note: "See hooks/README.md for complete documentation"
- **README.md restructured** for immediate content comprehension
  - "What's Inside" moved from line 72 to line 24 (48 lines higher)
  - Removed duplicate "What's Inside" section (was at old location)
  - Removed duplicate DeepWiki reference from Resources section
  - Optimal information architecture: Title → Author → What's Inside → About
- **Guide statistics updated**
  - Guide expanded from 7,668 to 8,505 lines (+837 lines, +10.9%)
  - Word count updated to approximately 31,280 words
  - Reading time remains 3 hours (comprehensive read-through)

### Stats
- 6 new files created (~43 KB total)
  - 3 slash commands (pr.md, release-notes.md, sonarqube.md)
  - 2 bash hooks (dangerous-actions-blocker.sh, notification.sh)
  - 1 comprehensive documentation (hooks/README.md)
- 3 files modified (README.md, english-ultimate-claude-code-guide.md, examples/README.md)
- Guide grew by 837 lines (10.9% growth from v2.0.0)
- Focus on production-ready templates and improved documentation discoverability
- All commands and hooks fully generic (no project-specific references)

## [2.0.0] - 2026-01-10

### Added
- **Section 9.12: Git Best Practices & Workflows** (~400 lines)
  - Commit message best practices with Conventional Commits format
  - Git amend workflow with safety rules and verification process
  - Branch management patterns and naming conventions
  - Rewind vs Revert decision tree for different scenarios
  - **Git Worktrees comprehensive documentation**
    - Parallel branch development without context switching
    - Setup process and directory structure
    - Claude Code integration patterns
    - CLAUDE.md memory file strategies for worktrees
    - Best practices and troubleshooting guide
    - Cleanup procedures
- **Section 9.13: Cost Optimization Strategies** (~350 lines)
  - Model selection matrix (Haiku/Sonnet/Opus use cases and costs)
  - OpusPlan mode (Opus for planning, Sonnet for execution)
  - Token-saving techniques (concise CLAUDE.md, targeted @references, proactive compacting)
  - Agent specialization for efficiency
  - Cost tracking with /status command and budget alerts
  - Economic workflows (Haiku for tests, Sonnet for implementation)
  - Token calculation reference with real pricing examples
  - Cost vs productivity trade-offs analysis
  - ROI calculations and cost-effectiveness metrics
- **examples/commands/git-worktree.md** - Slash command template
  - Systematic worktree setup workflow
  - Directory selection priority logic (.worktrees/ vs worktrees/)
  - Safety verification (.gitignore checks)
  - Auto-detection of package managers (pnpm, cargo, poetry, go)
  - Baseline test verification
  - Complete quick reference table
- **8 TL;DR/Recap sections** for improved navigation and learning journey
  - Section 2 TL;DR (Core Concepts) - 2 minute overview of mental model
  - Section 3 TL;DR (Memory & Settings) - 90 second memory hierarchy guide
  - Section 4 TL;DR (Agents) - 60 second quick start guide
  - Section 7 TL;DR (Hooks) - 60 second event system overview
  - Section 9 TL;DR (Advanced Patterns) - 3 minute pattern categories breakdown
  - Section 10 TL;DR (Reference) - 1 minute navigation table
  - Subsection 2.2 Quick Reference (Context Management zones)
  - Section 9 Recap Checklist (Pattern mastery verification before Section 10)
- **Format Enhancements** for better readability
  - Collapsible tables using `<details>` tags for dense content (MCP Server Catalog)
  - C-style comment format (`/*──────*/`) for multi-OS installation commands
  - Quick navigation anchor links at top of all 10 major sections
- **zebbern/claude-code-guide reference** in README Resources
  - New "Related Guides" section grouping zebbern and Claudelog as peer guides
  - Positioned prominently after Official docs section
  - Added context: "Comprehensive reference & troubleshooting guide with cybersecurity focus"

### Changed
- **Updated statistics** throughout documentation
  - Guide expanded from 7,481 to 7,668 lines (+187 lines, +2.5%)
  - Word count: 27,471 words (27K+)
  - Reading time estimate: 2.5 hours → 3 hours (more accurate for full guide)
  - README: "4000+ lines" → "7500+ lines, 27K+ words"
  - PDF Kimi reading time: 2.5 hours → 3 hours
- **Version alignment** across all files to 2.0
  - english-ultimate-claude-code-guide.md: Version 1.0 → 2.0
  - README.md: Version 1.0 → 2.0
  - claude-setup-audit-prompt.md: Version 1.0 → 2.0
  - cheatsheet-en.md: Already 2.0
- **Date updates** to January 2026
  - All "Last updated" fields across documentation
  - Status Overview Table dates (Jan 2025 → Jan 2026)
  - Pricing model reference date (January 2026)
  - Footer timestamps in all major files

### Fixed
- Removed duplicate Claudelog reference from "Frameworks & Tools" section (was in both Key inspirations and Resources)
- Improved organization of Resources section with clearer categorization

### Stats
- Guide now 7,668 lines (from 6,250 lines in v1.2.0)
- Added 187 lines of TL;DR/navigation content
- ~23% growth from v1.2.0
- Focus on user experience optimization and learning journey enhancement
- Major version bump reflects structural documentation paradigm shift (learning-focused TL;DRs throughout)

## [1.2.0] - 2025-01-10

### Added
- **Section 1.6: Migration Patterns** (~230 lines)
  - Complete guide for transitioning from GitHub Copilot to Claude Code
  - Cursor to Claude Code migration strategies
  - Hybrid workflow recommendations (when to use which tool)
  - Week-by-week migration checklist
  - Common migration issues and solutions
  - Success metrics and productivity indicators
- **Section 2.2: Cost Awareness & Optimization** (~220 lines)
  - Detailed pricing model breakdown (Sonnet/Opus/Haiku)
  - Cost optimization strategies (5 actionable patterns)
  - Real-world cost examples and ROI calculations
  - Budget tracking and cost-conscious workflows
  - Cost vs. value analysis (when to optimize, when not to)
  - Red flags for cost waste indicators
- **Section 9.3: Release Notes Generation** (~280 lines)
  - Command-based release notes automation
  - CI/CD integration for automated changelog
  - Interactive workflow for manual control
  - Three output formats (CHANGELOG.md, GitHub Release, User Announcement)
  - Best practices and common issues
  - Complete examples with real commit history
- **Section 10.4: Enhanced Troubleshooting** (~170 lines added)
  - MCP server connection issues (Serena, Context7, Sequential)
  - Permission pattern matching problems
  - Timeout handling strategies
  - Platform-specific installation issues (Windows, macOS, Linux)
- **Appendix A.10: Emergency Hotfix Checklist** (~140 lines)
  - Step-by-step hotfix protocol (8 phases)
  - Time-based decision matrix (<5 min to >30 min)
  - Claude Code hotfix-specific commands
  - Hotfix anti-patterns and best practices
  - Communication templates for incident updates
- **Appendix A.11: Git Archaeology Pattern** (~250 lines)
  - 6 archaeology patterns (mysterious code, feature evolution, bug introduction)
  - Claude-optimized git commands for investigation
  - Real-world examples (workarounds, breaking changes, dead code)
  - Archaeology prompt template
  - Finding domain experts via git history
- Enhanced Windows disclaimer in README (more visible, actionable)
- Updated `claude-setup-audit-prompt.md` with new checklist items
  - Cost Awareness evaluation criteria
  - Migration Patterns assessment
  - Release Notes automation check
  - Emergency procedures documentation
  - Git archaeology usage patterns

### Changed
- Improved Windows support visibility in README
  - Changed from small note to prominent callout box
  - Added specific areas of concern (PowerShell, paths, batch files)
  - Clear call-to-action for Windows contributors
  - Status indicator for platform support

### Stats
- Guide expanded from ~4955 lines to ~6250 lines (~26% growth)
- Added ~1300 lines of high-value, practical content
- 6 major new sections addressing real-world developer needs
- Focus on cost optimization, migration, and production scenarios

## [1.1.0] - 2025-01-10

### Added
- Comprehensive Windows compatibility support
  - PowerShell hook templates
  - Windows-specific paths throughout documentation
  - PowerShell profile setup instructions
  - Batch file alternatives where applicable
- Windows disclaimer in README (author on macOS, Windows untested)
- DeepWiki exploration link for interactive repository discovery
- `llms.txt` file for AI indexation

### Changed
- Installation instructions now prioritize npm (cross-platform)
- Cheatsheet updated with dual-platform paths (macOS/Linux + Windows)
- Audit prompt includes Windows paths

## [1.0.0] - 2025-01-09

### Added
- Complete Claude Code guide (4700+ lines)
  - Section 1: Quick Start
  - Section 2: Core Concepts (Context Management, Plan Mode, Rewind)
  - Section 3: Memory & Settings (CLAUDE.md, .claude/ folder)
  - Section 4: Agents (Custom AI personas, Tool SEO)
  - Section 5: Skills (Reusable knowledge modules)
  - Section 6: Commands (Custom slash commands)
  - Section 7: Hooks (Event-driven automation)
  - Section 8: MCP Servers (Serena, Context7, Sequential, Playwright)
  - Section 9: Advanced Patterns (Trinity, CI/CD, Vibe Coding)
  - Section 10: Reference (Commands, Troubleshooting, Checklists)
  - Appendix: Templates Collection
- 1-page printable cheatsheet (`cheatsheet-en.md`)
- Setup audit prompt (`claude-setup-audit-prompt.md`)
- PDF versions for offline reading
- NotebookLM audio deep dive

### Documentation
- README with quick start guide
- Table of contents with anchor links
- Quick links by topic
- Who Is This For section

## [0.1.0] - 2025-01-08

### Added
- Initial repository structure
- License (CC BY-SA 4.0)
- .gitignore for common patterns

<!-- git-ai test: 2026-06-26 -->