You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reconnect MCP after replacing the executable. Existing databases need no migration.
Open existing workspaces once before moving them. Move the ignored .repoplane/workspace-id
with the directory, retain the original state directory, and update the workspace path.
Legacy workspaces moved before their first upgraded startup can use --workspace-origin
once with the former canonical absolute path. Normal later moves need no origin option.
Memo and checkpoint updates now preserve omitted fields. Supply id, expected_revision,
and only the changed fields; explicit empty optional strings and arrays clear those values.
Added
Pin legacy workspace IDs in private .repoplane/workspace-id files so directory moves keep
memos, checkpoints, and other records with the same state directory, without rewriting records.
Add one-time --workspace-origin adoption for legacy directories moved before upgrading.
Conflicting or corrupt saved IDs fail closed; MCP discovery explains continuity and recovery.
Fixed
Failed service initialization no longer pins a workspace ID before legacy adoption can be
retried. Publish complete, synced IDs without overwriting another opener's identity, and
reject oversized or damaged files rather than accepting truncated content.
Legacy adoption resolves existing parent aliases even when the old workspace has moved,
keeping Windows short paths and junctions in the original canonical record namespace.
Content-only memo edits inherit memo kind and topic identity. Updates preserve discovery
metadata, temporal evidence, evidence refs, and successor links instead of dropping them.
Invalid memo transitions name the affected field and explain recovery. Ordinary update errors
must not be bypassed by retiring or superseding the record; successor creation remains the
explicit path for intentional identity, kind, or schema changes.
Source-list replacement rejects omitted values. An explicit empty array remains the way to
clear a list.
Align README usage, CLI help, both MCP tool surfaces, and repo-memory recovery instructions
with workspace continuity and partial updates.