mesalogo
bf8ece0590
Complete the pending Supervisor changes with opt-in execution, incremental automatic reviews, and activity history. Preserve saved preferences and plans, skip model calls for unchanged input, and keep full replay and cancellation limitations explicit. Update both release versions, bilingual notes, feature matrices, migration fixtures, and validation evidence. Clear stale browser errors after a successful close retry. Focused validation passed 690 tests across 35 files, plus notes verification, typecheck, and lint; full CI and native release acceptance remain pending. No local production build or packaging was run. Release note: Enable Supervisor to review work, trace story graphs, and inspect manual or automatic activity without repeating model calls for unchanged input. Desktop 0.13.12 and Agent 0.13.3 also prepare idle remote Runtime cleanup and retirement of replaced Agents; update Desktop before the Host environment. Database upgrades require a pre-upgrade backup for rollback.
3.7 KiB
Desktop 0.13.12 and Agent 0.13.3 Preparation
Prepared on 2026-09-23 on main. This record describes a local candidate, not a
published release. Desktop notes are in resources/release-notes.json; Agent
notes are in resources/agent-release-notes/0.13.3.md. Both are bilingual drafts
awaiting approval with the exact candidate commit before tagging.
Scope
- Desktop baseline:
v0.13.11, including all nine subsequent commits through83a48a4and the reviewed working-tree changes. - Agent baseline:
agent-v0.13.2. The Agent changes reclaim idle Runtimes and drain displaced Agents; the Desktop Continue path restores conversation history when reopening a Runtime. - Desktop package and both root lockfile versions are
0.13.12.agent-runtime-lock.jsonis0.13.3. Agent package tooling derives the minimum Desktop version frompackage.json. Node, OpenCode, and Continue locks are unchanged at24.19.0,1.18.29, and1.5.47. - Both feature matrices were reviewed and updated for versions, Supervisor default-off behavior, implemented reviews/graphs/activity/incremental input, remaining supervision work, and release acceptance limits.
Local Validation
npm run release:notes:verify, npm run typecheck, and npm run lint passed
after the final source changes. Focused runs cover 35 distinct test files and
690 passing tests; 403 tests were excluded by the IPC/App name filter.
| Group | Files | Passing Tests |
|---|---|---|
| Supervisor, settings, bridge, and release-note suites passing in the initial run | 14 | 157 |
| Database, migration, activity I/O, note storage, menu, and sidebar suites after fixes | 6 | 209 |
IPC/App filtered by supervision|Supervisor|heartbeat|application enable|graph navigation |
2 | 16 |
| Agent CLI, daemon, Runtime backend, Desktop ACP, transport, and connection manager | 7 | 207 |
| Usage, duration, workspace, Markdown, and Supervisor Electron layout | 6 | 101 |
The initial focused run had 25 failures: 22 synthetic legacy database fixtures retained schema-46 objects, two menu assertions assumed Supervisor was enabled, and one browser close retry left its earlier error visible. Fixtures now remove the new objects before simulating older versions, menu tests follow the saved enabled preference, and a successful browser close clears its scoped error. All affected suites passed on rerun. Production migration behavior was not changed to accommodate synthetic fixtures.
The Electron layout test uses production components with isolated fixtures, including 1440, 1024, and 390 pixel widths and light/dark themes. It is not a packaged-app probe or a real-user database acceptance test.
No real model requests were made during this preparation. Existing development evidence records eight requests on the shared Linux x64 Host for remote lifecycle checks and three for incremental review. The remote evidence does not repeat Continue real-Host validation, the complete signed installation flow, or the native architecture matrix. See remote lifecycle evidence and incremental review evidence.
Pending Release Work
The user requested no further full local suite. Full main-branch CI validation and its production build remain required before tagging; native Desktop and Agent packaging and publication verification remain pending. No local production build or package was run. No push, tag, remote synchronization, or publication was performed during preparation. Approval must identify the exact candidate commit and both bilingual note files before either release tag is created.