feat(claude-code): update placemat for Claude Code v2.1.288

[dommango]

Summary

Daily sync of the Claude Code placemat from v2.1.287 → v2.1.288, per claude-code/PIPELINE.md.

• npm dist-tags.latest (2.1.288) cross-checked against the official changelog at https://code.claude.com/docs/en/changelog — confirmed, dated 2026-10-02.
• Content changes applied, sourced directly from the vendor changelog text:
  • CLI: claude project purge [path] renamed to claude purge [path]; old form still works and prints a notice (added as a note, row id kept as a permalink).
  • Skills: /code-review gained --max-findings <n>|all (note added to the existing row).
  • Keys & Shortcuts: new Ctrl F (find a session by name) and Alt ↑ / Alt ↓ (jump between groups) in claude agents.
  • Env Vars: new CLAUDE_CODE_DISABLE_STRUCTURED_OUTPUTS.
• changelog.html gets a new CC v2.1.288 entry (October 2026 group now spans v2.1.287–v2.1.288, 2 releases).
• Header .release-tag, .print-head, and footer "Content synced" date bumped to v2.1.288 / 2026-10-02 on index.html (and the previously-stale footer date on changelog.html fixed to match).
• No new rows fell into the slash / settings / hooks inventory categories, so sources.json → inventory did not need re-extraction this run.

Other v2.1.288 changelog items (mod API additions, numerous internal fixes to VSCode/Cloud sessions/Claude Tag/auto-mode/MCP plumbing, etc.) were reviewed and left out as not mapping to any of the eight placemat cards, consistent with "a card with no verified content stays short."

Checklist

• node scripts/build-changes.js claude-code — regenerated changes.json + feed.xml
• node tests/placemat.test.js claude-code — 54 passed, 0 failed
• Per-page parity: release tag / print-head / footer sync date all agree (v2.1.288, 2026-10-02)
• No class="new" or <!-- added:vX.Y.Z --> written
• No existing i- row ids changed

Test plan

• node scripts/build-changes.js claude-code && node tests/placemat.test.js claude-code
• Merge gate: code-review skill run against this diff, verdict posted as a PR comment, merge via GitHub MCP once clean and CI is green

🤖 Generated with Claude Code

https://claude.ai/code/session_01YBdQyYHVgFH8G95MUGoZCU

---

Generated by Claude Code

[dommango]

Merge-gate code-review verdict (Step 10, independent of the Step 8 self-review)

First pass (commit ea2e677) found one finding:

• claude-code/sources.json: PIPELINE.md Step 5 requires re-extracting sources.json → inventory and bumping inventory.fetched whenever a sync adds new rows; this PR added four rows (claude purge rename, /code-review --max-findings, two new claude agents keybindings, CLAUDE_CODE_DISABLE_STRUCTURED_OUTPUTS) without touching sources.json.

Fix (commit 4e1af19): re-fetched commands.md, settings-reference.md and hooks.md, diffed them against the tracked inventory, and confirmed no new slash command, settings key, or hook/MCP field exists — this release's placemat-relevant content is a CLI rename, a flag, two keybindings and an env var, none of which the inventory schema (slash/settings/hooks only) tracks. Bumped inventory.fetched to 2026-10-02 with a note recording that check.

Re-review (commits ea2e677 + 4e1af19): clean — no findings. Verified the fix is a genuine resolution (not a rationalization), re-ran node scripts/build-changes.js claude-code --check and node tests/placemat.test.js claude-code (54/54 passed), and re-checked per-page parity, row-id permalink stability, notes-button counts, and the no-class="new" rule.

Verdict: clean. Proceeding to merge once CI is green.

---

Generated by Claude Code