[ICEY16360]

Approved issue: #676

What

Adds Restore and Make permanent to the Memories bulk-action bar, so a selection can be brought back from archived (or lifted to permanent) in one command. The backend already supports both: bulk_update_memory_status accepts any status, treats a change into active/permanent as a restore for epoch-bump purposes, and only bumps for rows whose status actually changes.

Changes

• packages/dashboard/src/components/MemoryBrowser/MemoryBrowser.tsx: handleBulkRestore / handleBulkPermanent mirroring handleBulkArchive (confirm → bulkUpdateMemoryStatus → clear selection → refetch), plus Restore and Make permanent buttons next to Archive. Confirm dialogs mirror the Archive one, including the singular/plural template.
• packages/dashboard/src-tauri/tests/db_mutations.rs: bulk_restore_mixed_selection_changes_and_bumps_only_actually_changed_rows — a mixed selection (archived→active and permanent→active that change, active→active no-ops, including one project path with no changes at all) asserts only the transitioning rows change, only their paths bump the epoch, and a restore queues no memory mutations.
• packages/docs/src/content/docs/reference/dashboard.md: the bulk-select line now lists restore and make permanent.

No production Rust change — the approved shape is frontend plus a test of the existing command.

Harness coverage (required)

• OpenCode 1: covered — shared dashboard over the shared context.db
• OpenCode 2: covered — same dashboard
• Pi: covered — same dashboard; Pi shares the store
• OMP: covered — same dashboard
• Rust module: covered — new integration test in db_mutations.rs exercises bulk_update_memory_status's no-op guard and epoch semantics (no production Rust change)

---

Summary by cubic

Adds Restore and Make permanent to the Memories bulk-action bar, so a selection can be brought back from archived or lifted to permanent in one command, alongside the existing Archive and Delete.

• The backend already supports both via bulk_update_memory_status; only frontend, tests, and docs change.
• Confirm dialogs mirror the Archive flow; Restore warns when selected permanent memories would lose never-expire status.
• All bulk actions are disabled while a reload is in flight, so the dialogs never act without fresh statuses.
• Selection is pruned whenever a refetch drops selected rows from the visible list, so bulk actions never act on rows the user can no longer see.
• New integration tests cover restore-to-active and make-permanent: only rows that actually change status bump the epoch, and neither queues memory mutations.
• The bulk-action bar now wraps on narrow windows, and the dashboard docs list the new actions.

^{Written for commit 32bada9. Summary will update on new commits.}

Confidence Score: 5/5

The PR appears safe to merge; no actionable issues remain in the reviewed changes.

Summary

Adds confirmed bulk Restore and Make permanent actions, with tests and updated docs.

• People can restore selected memories or make them permanent in one confirmed action.
• Selections drop memories that disappear from the loaded list.

_{Reviews (5) · Last reviewed commit: "fix(dashboard): gate archive and delete ..." · Reviewed by Greptile}

[cubic-dev-ai]

All reported issues were addressed across 3 files

<sub>Reply with feedback, questions, or to request a fix.

View guided diff | Re-trigger cubic</sub>

[magic-alfonso]

This is ready to merge once it applies cleanly: it now conflicts with master in packages/dashboard/src/components/MemoryBrowser/MemoryBrowser.tsx. Could you rebase it onto the current master? Once the conflict is resolved and the checks pass, I'll merge it.

[ICEY16360]

@cubic review

[cubic-dev-ai]

@cubic review

@ICEY16360 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

1 issue found across 4 files

<sub>Reply with feedback, questions, or to request a fix.

View guided diff | Re-trigger cubic</sub>

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="packages/dashboard/src/components/MemoryBrowser/MemoryBrowser.tsx">

<violation number="1" location="packages/dashboard/src/components/MemoryBrowser/MemoryBrowser.tsx:738">
P2: Restore and Make permanent are disabled while lists reload, but Archive and Delete stay enabled. During that window the selection can still include rows the pruning effect is about to drop, so those two actions act on rows the user can no longer see, which the new comment says should not happen. Either disable all four bulk buttons during the reload, or state in the comment that only the two new actions are gated.</violation>
</file>