Add a persistent operation center for long-running work #7

Outcome

Long-running work should remain visible after navigation and restart. The user must know the target, current step, outcome, and safe next action.

Priority: P1 · Product

Scope

• Add an operation list and detail view for catalog refresh, connection checks, previews, allocations, publishing, and warehouse execution.
• Display pinned store/project/page, current step, last progress, timestamps, and verified or uncertain outcome.
• Drive retry, cancel, reconcile, and open-result controls from engine policy rather than UI guesses.
• Preserve operation visibility across route changes and app restarts. Link relevant editor and history views.

Acceptance criteria

• Navigating away and back does not lose progress or detach work from its original store.
• Reopening after interruption shows the persisted operation state and available recovery action.
• Cancellation availability and limits are clear.
• Unsafe retries are disabled with a concrete explanation.
• A timeout never appears as verified success or as proof that no remote effect occurred.

Validation

Exercise running, stalled, cancelled, failed, uncertain, reconciled, and completed states. Kill the worker during fixture operations and verify restored UI state.

Dependencies

• Unify operation policy, durable state, and remote-effect reconciliation #4 — Unify operation policy, durable state, and remote-effect reconciliation