[ScriptedAlchemy]

#4527 has merged into #4485's release branch. This PR now targets release-please--branches--master--components--tracedecay.

Merge this PR with a merge commit, then retarget its direct child #4530 to the same release branch while #4485 remains open. Continue the stack in order: #4530, #4531, #4529, #4534, #4541. Auto-merge remains disabled.

Fixes #4434.

Why

sync.full_sync_escalation_files.v1 and sync.max_concurrent_syncs.v1 were listed, writable settings that no sync execution consumer read. They also remained required inputs when a resolved snapshot was materialized, so simply deleting their registry rows would break existing configuration.

Changes

• Remove both runtime fields, defaults, materialization reads, active registry definitions, inventory entries, and public key exports.
• Record their literal keys in the existing RETIRED_CORE_SETTING_KEYS_V1 authority. Project open already runs registry convergence before runtime pinning; saved defaults and overrides now converge into an immutable child revision while retaining unrelated values, provenance, and readable history.
• Keep the released-key census and historical SQL fixture intact. Current settings lists omit both keys; reads and Set/Unset/Batch writes reject them with the existing unknown-setting validation result.
• Add behavior coverage for discovery and write refusal, runtime pinning without the retired keys, persisted default/override convergence, history preservation, and reconvergence.

Caller audit

On the parent commit, exact field/key references were confined to runtime declarations/defaults/materialization, registry/default definitions, domain exports/inventory, and released configuration evidence. Generic discovery and mutation paths obtain supported definitions from ConfigurationRegistry, so there is no separate generated SDK/dashboard setting inventory to update.

The actual owners remain unchanged: scheduler concurrency uses background_reconcile_admission and MAX_CONCURRENT_RECONCILE_WORKTREES; capture/reuse decisions come from the scheduler's Git-tree/source-change reconciliation and full-capture fallback. Watcher opt-in, linked-worktree admission, timing/capacity, read-refresh/cooldown, and code-index worker budgets retain their existing owners.

Validation

Canonical Bazel validation on integrated parent commit c9de607ed5626290e105d4f131da459dc250e7a3:

• Configuration unit tests: 40 passed, with formatting checks for configuration, domain, and global-db. Invocation 753c6565-2612-455f-ba61-d4bb0e20acdf.

• Global-db configuration tests: 60 passed, including all three persisted retirement regressions, with the nonzero-test helper. Invocation 1a94cea4-f8ed-4ba7-8a01-acb7c89d21b6.

• Scoped Clippy for the configuration and global-db unit-test targets passed: 4467346f-ead4-4303-b202-ffe4eddd81b8.

• Maintained Bazel target-generation check passed: all 60 generated BUILD files are current (46bfaca8-36a0-4561-91ba-c94d49c08f9e).

• All checks above used canonical Bazel targets with fresh Linux test results. Hosted checks remain independently required.

Stack

Based on #4527 (fix/privacy-structured-key-coverage). This layer contains only the configuration retirement and its regression coverage.

[changeset-bot]

⚠️ No Changeset found

Latest commit: e460a8c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.