Gap (verified 2026-06-16, rung 2). Work items can be ARCHIVED but archived items are then unreachable and unrestorable from the product UI:
archivedAt IS NULL (e.g. workItemRepository.ts ×30+; the /issues forest reads listWorkItems/listRootIssues), so an archived item vanishes from every surface with no way to find it again.components/issues/actions/WorkItemActionsMenu.tsx:96 fires an inline archive with an Undo toast that calls unarchiveWorkItem — and its own comment (:20) says that toast is "the only restore path until an archived-items view ships." Dismiss the toast / navigate away and the item can never be brought back from the UI.The BACKEND for restore already exists and is unused by any durable surface: workItemsService.unarchiveWorkItem (gated assertCanEdit, writes an unarchived revision), the DELETE /api/work-items/[id]/archive route, workItemRepository.unarchive (clears archivedAt), and the unarchive_work_item MCP tool (Story 7.8.14). What is missing is a way to (a) SEE archived items and (b) RESTORE them from that view.
Mirror (Jira). Jira has a dedicated, admin-gated Archived issues view where archived work is listed and restored (single + bulk). Motir mirrors Jira → this surface is a real gap, not a scope cut. (Note: Motir's archive is single-node "Linear shape" — children stay live — so the archived view is a FLAT list, not a tree.)
This story adds the archive-management surface: a discoverable, paginated archived work items view + a per-item Restore action wired to the shipped unarchiveWorkItem path. Design + backend read-path + frontend + E2E.
archived revision).waitForResponse on the unarchive write (200) → the item returns to active views and its activity shows "restored".