Skip to content

[MM-31] Add legacy memory dry-run migration, export, and rollback #811

Closed

Description

@bug-superman

MM-31: Add legacy memory dry-run migration, export, and rollback

Parent

#771

Checkpoint

MC-9 Core release candidate

What to build

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.

Blocked by

Rollout and rollback

Versioned backup and explicit rollback command are mandatory before migration apply.

Activity

  1. Astro-Han commented on Aug 2, 2026

    @Astro-Han
    Contributor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions