chore(compat): CC 2.1.183-191 survey - schema watch moves to SchemaStore #5814

[tigers1997]

Summary

Follow-up to #84. Resurveys upstream anthropics/claude-code across the 13-day gap; the headline finding is that the schema-sync watch target moves.

Schema gate moved. A fresh SchemaStore PR #5814 (sync→v2.1.177, 84→134 properties, opened 2026-06-13, not draft, awaiting code-owner LGTM) supersedes the long-idle #5723 (still draft, untouched since 2026-05-24 — 32 days). The upstream-gate-playbook watch target switches to #5814 OR #5723 OR successor — either merge unblocks. Two further targeted PRs also open and awaiting LGTM: #5822 (seven UI/notification keys — out of territory) and #5833 (targeted attribution.sessionUrl for CC 2.1.183 — in territory).

Versions surveyed. Six present in CHANGELOG: 2.1.183, 2.1.185, 2.1.186, 2.1.187, 2.1.190, 2.1.191. (2.1.184, 2.1.188, 2.1.189 NOT in CHANGELOG — skipped or internal-only per the verbatim-pull discipline.)

New in-territory settings.json keys (held pending the merge)

Key	CC version	Future home
sandbox.credentials	2.1.187	templates/safety/settings-patch.json // sandbox block (hardening: blocks sandboxed cmds from reading credential files / secret env vars)
attribution.sessionUrl	2.1.183	templates/git-workflow/settings-patch.json (privacy opt-in: omits claude.ai session link from commit/PR text in web + Remote Control sessions; #5833 is the targeted schema-side patch)

Out of territory: respondToBashCommands (CC 2.1.186) — per-user behavior pref (default-true: ! bash commands auto-prompt Claude), not a project-level scaffolded default.

Permission-rule syntax

2.1.186 adds Agent(type) deny rules and Agent(x,y) allowed-types restrictions for named-subagent specs — same Tool(param:value) form already parked from 2.1.178 in PR #84. No shipped template uses either; parking decision stands.

No-impact verifications (greps clean)

• Hook-matcher comma-separated silent-fail (CC 2.1.191, e.g. "Bash,PowerShell") — all shipped templates use pipe-separated regex (Write|Edit|NotebookEdit), no comma form anywhere.
• Skill-frontmatter case-insensitivity (CC 2.1.186: kebab+snake+camel all accepted) — shipped skills are kebab-case.
• Auto-mode git/iac destructive-command block (CC 2.1.183: git reset --hard, git checkout -- ., git clean -fd, git stash drop, plus terraform/pulumi/cdk destroy unless the specific stack is asked) — classifier-tier gate, orthogonal to the bash-pattern-based block-dangerous-bash.sh PreToolUse guard. No overlap to harden.
• Subagent depth-tracking fix (CC 2.1.187: resumed subagents restore original spawn depth, forks count toward the depth cap) — further validates the 5-level cap surfaced in 2.1.181 and lifted into shipped wording in PR chore(compat): CC 2.1.176–181 survey + lift held subagent-nesting wording #84.

Env mention-only

• CLAUDE_CLIENT_PRESENCE_FILE (CC 2.1.181, mobile-push suppression marker — missed in the 2.1.176-181 survey, captured here)
• CLAUDE_CODE_RETRY_WATCHDOG (CC 2.1.186, replaces unbounded retry; CLAUDE_CODE_MAX_RETRIES capped at 15 in the same release)
• CLAUDE_CODE_MCP_TOOL_IDLE_TIMEOUT (CC 2.1.187, overrides the new 5-minute remote-MCP-call abort)

Sync gate status

tested_up_to stays pinned at 2.1.150 per the no-lone-bumps rule. The bump bundles with the next release after either #5814 or a successor merges.

Issue #14920 (per-skill plugin disable) re-checked: still open, 13 community comments, no Anthropic engagement, last update 2026-03-31 (86 days stale). skillOverrides plugin-skill carve-out remains the documented manual workaround.

Claude Code compat: 2.1.116–2.1.150 (unchanged).

Test plan

• python3 configure.py --check clean (12 modules, 85 files, compat 2.1.116–2.1.150)
• bash test/cc-manifest/test-whats-new.sh PASS
• python3 -c "import config_schema" clean (compat dict imports as expected)
• CI check green
• CI verdict-gate green
• CI license/cla green

🤖 Generated with Claude Code

[claude]

VERDICT: PASS

This is a documentation-only chore PR: it appends an 80-line compat-survey comment block to the CLAUDE_CODE_COMPAT section of config_schema.py and adds a matching ## Unreleased CHANGELOG entry for the CC 2.1.183–2.1.191 survey window. No functional code changes, no new template keys shipped (both sandbox.credentials and attribution.sessionUrl are explicitly documented as HELD pending the SchemaStore gate), no third-party code introduced, and no scope creep.

[tigers1997]

Superseded by #92.

That PR's survey covers 2.1.183–2.1.241 — this PR's window (2.1.183–191) plus the 50 releases after it — and rewrites the same CLAUDE_CODE_COMPAT comment block, so the two conflict by construction (this one already reports CONFLICTING against main).

It also resolves what this PR was waiting on. The schema gate has moved again since it was written:

• #5723 (the long-idle draft) was closed unmerged.
• #5814 (the watch target this PR switched to) also did not land.
• #5867 (sync → v2.1.195, merged 2026-07-03) and #6131 (sync → v2.1.220, merged 2026-07-27) did land, which is what clears the no-lone-bumps rule.

So tested_up_to moves 2.1.150 → 2.1.220 in #92, and the keys held pending a schema sync (fallbackModel, disableBundledSkills, plus agent, claudeMdExcludes, skillListing*, sandbox.credentials, worktree.symlinkDirectories) are now schema-validated and promoted to opt-in stubs.

Nothing from this PR's 80-line comment block is lost — its findings are folded into the longer survey. Closing and deleting the branch; reopen if you want anything back.