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
{{ message }}
Repository navigation
[MM-31] Add legacy memory dry-run migration, export, and rollback #811
Provide dry-run migration and reports for legacy memory/context state, mixed-version operation, complete export/delete, upgrade/downgrade, and rollback.
Acceptance criteria
Dry-run is side-effect free and reports every planned change.
Migration is idempotent and crash resumable.
Old/new mixed state remains readable.
Export/delete cover profile, proposals, episodes, manifests, archive refs, working state, and caches.
Rollback drill restores a working prior version without data loss.
Required tests
Dry-run/idempotency
mixed state
crash/restart
upgrade/downgrade
export/delete completeness
Benchmark
Migration performance and post-migration lifecycle/continuity smoke; no quality comparison needed.
Superseded by #1615 (automatic long-term memory lifecycle, SQLite-based; accepted by maintainers 2026-07-30, PR ① #1770 merged). This MM-31 work item never landed outside draft PR #820 and is replaced by the #1615 design and its LongMemEval/MSC evaluation plan.
Activity
Astro-Han commentedon Aug 2, 2026
Superseded by #1615 (automatic long-term memory lifecycle, SQLite-based; accepted by maintainers 2026-07-30, PR ① #1770 merged). This MM-31 work item never landed outside draft PR #820 and is replaced by the #1615 design and its LongMemEval/MSC evaluation plan.