fix: preserve staged Agent configuration update

This commit is contained in:
鲨鱼辣椒 committed 2026-10-13 17:32:31 +08:00
1 parent 5a8b8d75e5
commit 2b2f7b96b0
6 files changed
+67 -6

No files matched your search

@@ -72,3 +72,11 @@
- Original operation IDs, expected revisions, journal state, explicit retry/discard and duplicate-click guards are unchanged. There are no Main/shared/backend changes or real cloud apply/retry/discard. README reflects current application copy.
- Pinned corepack pnpm10.33.4 verification: 98 unit tests across 5 focused suites passed; Renderer typecheck passed; 10 changed source/test files ESLint passed; build:vite passed. Updated browser Host-IPC fixture E2E passed (1); the 375px screenshot was reviewed and the modal fits. Tests verify original ID reuse after network failure and preserve 401/403/409/422/429 explanations.
- Compared all 66 Main/preload/utility/resources/package artifact files to immutable live Main7c: exact hash equality, with no missing/extra files. This enables a Renderer-only temporary-app update. That update is the next authorized step; current inputs and UI remain protected, with no reuse of previous one-time input-discard approvals.
## Concurrent trial update reconciliation
- Initial immutable stage application-message-20261013-5dd70a31 was prepared for clean source5a8b8d7. Activation was safely held first by a visible dialog, then a nonempty input; no symlink/pointer/runtime mutation was performed by this task. Later the exact predecessor guard refused because another authorized task switched the compatible file payload.
- The separate remove-subagent trial task6d9a8e32 staged source2e5411c, containing only the subagent-selector removal and supporting committed product/test/README updates; its peer Scope/Intent/Promotion were read-only and compatible. The human explicitly approved immediate refresh in that chat, but the root could not use its CUA window and left the stage as files-activated-awaiting-cua-refresh, with global pointer still289. No foreign task source/docs/stage were changed here.
- Imported only source2e5411c's committed product/test/README diff into this owned worktree, retaining our application copy and all prior knowledge/home/account updates. Relative to staged2e, owned product delta remains exactly the five application files. No copied foreign task records.
- Combined verification:99 unit tests/6 suites, typecheck, changed-imported-file ESLint, full build:vite passed. All66 Main/resources/package files again match immutable7c exactly. Initial application fixture/screenshot evidence remains applicable to unchanged application paths.
- Runtime source reconciliation will bind a fresh task-owned overlay to both old current-pointer289 and the exact staged-but-not-acknowledged2e predecessor. All input/lease/dialog/user-interaction/focus guards remain, with no input-discard or business-action authorization inferred. Peer stage remains intact; successful activation must establish new own compound-build proof rather than claiming the peer's activation was verified.