[Copilot]

Summary

Make ordinary settings changes directly editable with Save while preserving revision checks, authorization, and the exact submitted request identity. Keep independent scope drafts intact, adopt refreshed values for clean scopes, and publish verified PATCH values into the selected project's read snapshot before clearing its proposal. Project writes also publish their derived automation revision while readback is pending.

Verification

• Updated the branch from master.
• All 67 focused settings state-machine, mutation, and DOM tests pass.
• The native Bazel transcript-ingest suite passes all 207 tests, including the Codex PostCompact cold-restart journey. The failed CI assertion (zero retained messages instead of four) did not reproduce either in isolation or in the full suite.
• Enable warnings in that hook fixture so its existing fail-open assertion can observe daemon-call failures; lifecycle, production behavior, assertions, and time limits are unchanged.
• Formatting, diff checks, and commit-message validation pass.
• Full hosted CI passed on 98bacf30f3737fdd3b8ae22770547cec7a9ea66e: all 169 Linux test targets, Dashboard, strict Clippy, feature gates, repository gates, and the shipped Linux CLI build. The branch was current with master at final review.

Fixes #4222

[changeset-bot]

⚠️ No Changeset found

Latest commit: 98bacf3

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

[ScriptedAlchemy]

Cross-referenced #4222 and pushed 9f8e9fb to fix two reload defects.

A newer payload observed while a draft was dirty could be ignored by the reducer. Explicit reload then reset from the old stored authority and relied on a query effect that might not run again for the already-cached newer object, leaving the next Save conflicted. Reload now dispatches the successfully fetched authority directly.

The uncertain-write warning/lock also cleared as soon as reload started. It now stays in place until the authority read succeeds; failed reads preserve the conflict/uncertainty, and duplicate pending reloads are guarded.

Both new DOM regressions failed against the submitted code and pass after the fix. Validation: settings Vitest suite — 7 files / 99 tests passed; dashboard tsc --noEmit passed; git diff --check and pinned-pnpm conventional commit lint passed. The published tree exactly matches the locally tested tree.

[ScriptedAlchemy]

Pushed fixes for all three settings findings. Saving a resource now settles only that scope, preserving other drafts and their original CAS revisions. Refresh advances clean resources independently while edited/pending resources retain their base. A verified PATCH publishes only its saved resource into the canonical query before the proposal clears, so the visible saved value does not revert while readback is pending; selected-project data is protected from profile-global worker responses and delayed saves remain tied to their original project. Verification: all 105 settings tests passed (99 existing plus six regressions; five were reproduced failing before the fix), TypeScript checking and the production build passed, and diff/commitlint passed. Browser automation was unavailable; DOM interactions were verified through the existing Vitest/RTL suite.