feat(claude-code-settings): add missing top-level keys

[zachmayer]

Five settings that Claude Code reads are missing from claude-code-settings.json. The schema's top-level additionalProperties is true, so today they validate silently: editors offer no completion for them, and strict validation can't be turned on for a settings file that uses them.

All five are documented in the Claude Code settings reference and are referenced by the Claude Code 2.1.261 binary.

Key	Type	Default	Docs
autoContinueAtUsageLimit	boolean	true	https://code.claude.com/docs/en/settings-reference#autocontinueatusagelimit
crossSessionInbound	string enum: accept, hold, refuse	unset	https://code.claude.com/docs/en/settings-reference#crosssessioninbound
enableWorkflows	boolean	unset	https://code.claude.com/docs/en/settings-reference#enableworkflows
promptSuggestionEnabled	boolean	true	https://code.claude.com/docs/en/settings-reference#promptsuggestionenabled
switchModelsOnFlag	boolean	true	https://code.claude.com/docs/en/settings-reference#switchmodelsonflag

The crossSessionInbound values come from https://code.claude.com/docs/en/cross-session-messaging#control-inbound-messages.

Descriptions follow the conventions already in this file: enum values explained inline in the description (as in autoUpdatesChannel) rather than via non-standard enumDescriptions, with a trailing docs URL. default is set only where the docs state one; enableWorkflows and crossSessionInbound are documented as unset by default, so neither gets a default.

Tests

• src/test/claude-code-settings/modern-complete-config.json — all five keys
• src/test/claude-code-settings/enum-coverage.json — crossSessionInbound: "hold"
• src/test/claude-code-settings/managed-settings.json — crossSessionInbound: "refuse", matching the managed-settings example in the docs

Together with "accept" in modern-complete-config.json, all three enum values are exercised.

Negative tests:

• src/negative_test/claude-code-settings/invalid-enum-values.json — crossSessionInbound: "maybe"
• src/negative_test/claude-code-settings/wrong-property-types.json — a non-boolean for each of the four booleans

Checks run

npm clean-install
node ./cli.js check --schema-name=claude-code-settings.json   # pre-checks + Ajv validation pass
node ./cli.js coverage --schema-name=claude-code-settings.json # 8 passed, 0 failed, 0 warned
npm run prettier                                               # all matched files use Prettier code style
npm run typecheck
npm run eslint

I also compiled the schema with Ajv directly and asserted each new constraint bites: the three valid crossSessionInbound values validate, "maybe" does not, and each boolean rejects a non-boolean. 12/12 as expected.

pre-commit was not run locally; the only hooks are Prettier (run above via npm run prettier) and codespell, which I ran over the changed files with no findings.

[github-actions]

Thanks for the PR!

This section of the codebase is owned by @domdomegg, @bogini, @sarahdeaton, and @ant-kurt - if they write a comment saying "LGTM" then it will be merged.