After an upgrade, hosts kept the call-rule skill and MCP entry an older
release wrote, so models were still told to call MemHub_ask and the other
removed tools, and WorkBuddy kept listing them from its tool-list cache.
- Stamp every managed MCP entry with ONE_MEMORY_MCP_TOOLSET, a tool
contract version kept beside the tool list (mcp-toolset.ts). WorkBuddy
fingerprints the stdio transport, env included, so a new stamp makes it
restart the server and drop the cached list. An entry without the
current stamp reads as stale in skill drift; verify still passes it.
- HostPermissions.refreshInstalledHosts runs the existing repoint and
stale-sync planners for every host this data dir installed, leaves
user-edited skills alone, emits allowlisted host_refresh.* diagnostics
(host ids and counts only), and records the build it completed in
host-permissions/host-refresh.json so it runs once per build.
- The Runtime calls it as it starts (covering App and `memhub upgrade`),
and Desktop calls it after an embedded Runtime is up.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Every 1.0.4 home must pass the offline SDK cutover, but the runtime
service could start Core on a home whose migration failed, so it served
legacy. Callers also asked Core for the memory authority before many
calls and kept v1 data-plane branches that only ever 409 on SDK.
Migration and startup:
- Write every migration step to logs/sdk-migration.log (content-free
JSON lines) from Desktop, CLI, the runtime service and Core.
- Migrate before the runtime service spawns Core; Core refuses a legacy
home with sdk_migration_required.
- Desktop shows a dialog that reveals the log and opens a GitHub issue,
then quits. CLI install/upgrade no longer roll back to a version
without the gate; start/restart/status/doctor name the log.
- Cycle the service when the migration status is unreadable so no
pre-upgrade Runtime keeps serving.
SDK only:
- Web, host-bridge and CLI call v2 only; drop the authority query.
- Delete Core's v1 data plane, the Reader and /api/v2/memory-authority.
- Fix MCP memory write on v2, MemHub_conversations, memhub recall and
status, v2 call events and WorkBuddy delivery reports.
- Remove dead features: matters, boundary peek/ack, memory plan/apply,
the legacy library and its v1 operations.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
alvinfeiandClaude Opus 5.5