chore(compat): survey CC 2.1.133-2.1.146; track SchemaStore PR #5706

CHANGELOG.md

@@ -4,6 +4,7 @@ All notable changes to this project. Format: [Keep a Changelog](https://keepacha
 
 ## Unreleased
 
+- **chore(compat): survey Claude Code 2.1.133–2.1.146; track SchemaStore PR #5706.** Resurveyed the upstream CHANGELOG and the SchemaStore catalog after a 9-day gap. The original gating PR #5665 (sync to v2.1.138) was closed 2026-05-19 with comment "Superseded by #5706 which syncs to v2.1.143" — net win for batching since #5706 also picks up `worktree.bgIsolation`, `subagentStatusLine`, `statusLine.hideVimModeIndicator`, `sandbox.failIfUnavailable`, five env vars (`ANTHROPIC_WORKSPACE_ID`, `CLAUDE_CODE_OPUS_4_6_FAST_MODE_OVERRIDE`, `CLAUDE_CODE_PLUGIN_PREFER_HTTPS`, `CLAUDE_CODE_POWERSHELL_RESPECT_EXECUTION_POLICY`, `CLAUDE_CODE_STOP_HOOK_BLOCK_CAP`), and the hook `args: string[]` + `continueOnBlock` keys move out of the "future sync" bucket and into the same merge gate. Eleven configurator-territory keys total in #5706; live-verified against the PR's head-branch schema 2026-05-21. Two later items remain held for a future sync PR (hook output `terminalSequence` from 2.1.141; Stop/SubagentStop input `background_tasks` + `session_crons` from 2.1.145). **No template changes; no `tested_up_to` bump yet** — deferred to the post-#5706 unblock batch per the "no lone tracking bumps" rule. `CLAUDE_CODE_COMPAT` rationale comment refreshed to capture the resurvey window. Also: `/simplify` was renamed to `/code-review` in 2.1.146 — configurator ships `/review` (slash command) + `code-reviewer` (agent name), so no collision.
 - **docs: drop legacy `/brainstorm` + `/write-plan` references after superpowers v5.1.0.** `superpowers` v5.1.0 (2026-04-30) removed the `/brainstorm`, `/write-plan`, and `/execute-plan` slash commands — they were deprecated stubs and users must now invoke the skills directly (or just describe the work; the SessionStart bootstrap auto-routes). Configurator references updated: `configure.py` "Next steps" output now says "describe what you want to build" instead of "invoke /brainstorm"; `docs/11-getting-started.md` walkthrough swaps the explicit `> /brainstorm` prompt for plain-English intent and adds an inline note about the v5.1.0 removal; `docs/10-plugin-ecosystem.md` install snippet drops `claude /brainstorm`; `templates/recommend-plugins/recommended-plugins.md` row reframes the gate as skill-driven. Historical CHANGELOG entries unchanged (they reference what was current at the time).
 - **feat: MCP drift monitor — SessionStart hook + `.cc-manifest.json` baseline + manifest-aware `/verify-setup` Check #4.** cc-configure now stays alive between runs: every scaffold/retrofit writes `.claude/.cc-manifest.json` snapshotting the `.mcp.json` server set; a new SessionStart hook (`.claude/hooks/sessionstart-drift-check.sh`, installed by the `mcp` module) compares manifest vs. live `.mcp.json` on `startup`/`resume` and emits one stdout line if servers were added or removed since the last cc-configure run; the line points to `/verify-setup`, whose Check #4 was rewritten to enumerate per-server purpose, cost class, profile-split fit, and a supply-chain vetting nudge (parses `npx`/`uvx` package coordinates and recommends the user invoke the available Sonatype MCP tools — `getComponentVersion`, `getLatestComponentVersion`, `getRecommendedComponentVersions` — before keeping any new MCP). Manifest writer is unconditional (runs even when the `mcp` module isn't selected, so a forward-looking baseline always exists); hook is module-gated. New `[ MANIFEST WARNINGS ]` block surfaces unreadable `.mcp.json` without ever locking in a corrupt baseline. New test directories: `test/cc-manifest/` (5 tests + e2e lifecycle), `test/sessionstart-drift-check/` (9 hook-behavior fixtures). New verify-setup spec-presence test pins the Check #4 anchors. Spec + plan: `docs/superpowers/specs/2026-05-13-cc-configure-mcp-drift-monitor-design.md` and `docs/superpowers/plans/2026-05-13-cc-configure-mcp-drift-monitor.md` (gitignored, local-only working artifacts).
 

config_schema.py

@@ -358,6 +358,17 @@
                                 # themes/monitors; CLAUDE_CODE_SESSION_ID exposed in
                                 # Bash subprocess env; no other configurator-
                                 # territory schema additions.
+                                # 2026-05-21 resurvey of 2.1.133-2.1.146: eleven
+                                # configurator-territory keys + five env vars held
+                                # in SchemaStore PR #5706 (sync to v2.1.143;
+                                # supersedes the closed #5665). Bump deferred until
+                                # #5706 merges and the unblock batch ships per the
+                                # "no lone tracking bumps" rule. Two further items
+                                # (terminalSequence hook output from 2.1.141;
+                                # background_tasks/session_crons hook input from
+                                # 2.1.145) need a future sync PR. No live breakage:
+                                # /simplify → /code-review rename in 2.1.146 does
+                                # not collide with the configurator's /review.
 }