Motir

Estimate: 50m · Type: design · Depends on: 2.8.1

DESIGN prerequisite the 2.8.4 Delete UI assumed but that does not exist. 2.8.1 designed the delete-confirm dialog AND drew the ⋯ actions menu STATICALLY (panels 0–1: Edit details · Copy link · — · Archive · Delete…, danger Delete row, permission-collapse) — but it did NOT design (a) the Archive action flow (its confirm / optimistic / toast — the notes call it "inline / lightweight" + out of scope), (b) the archived-item state (does an archived item show a banner? leave the list/board? how is it restored — note there is NO un-archive today), or (c) where the ⋯ menu attaches on each surface (detail header / issues-list row / board card — NONE has an actions menu today). The Delete dialog's "Archive instead" link (2.8.1) also has no defined target flow.

Produce the THREE-file design asset under design/work-items/ (design-notes.md + <name>.mock.html + <name>.png) covering: the ⋯ menu placement + interaction states on detail / list-row / board-card; the Archive click flow (reversible single-node, canEdit-gated — mirror Jira/Linear) and the resulting archived-item state (filtered / banner / restore — flag the missing un-archive as a rung-1 scope question); and how it composes with the already-designed Delete row + "Archive instead". Reuse shipped primitives (Popover/Modal/Button/Pill) + --el-*/shape tokens; no new primitive.

Acceptance criteria

• design-notes.md + mock.html + .png under design/work-items/, naming every primitive, exact copy, and --el-*/shape token role.
• Specifies the ⋯ menu on detail/list/board, the Archive flow + archived state (+ restore/un-archive decision per the mirror), and the "Archive instead" target.
• Mirror-checked vs Jira/Linear (archive vs delete; reversible single-node archive).

Context refs

• design/work-items/delete-confirm.mock.html + design-notes (2.8.1 — the menu it extends + the Delete row); workItemsService.archiveWorkItem (reversible single-node); no un-archive / no hard delete today. Blocks 2.8.9 + 2.8.4.