An archive chip on the card, where the card is
Every card in backlog/, to-do/ and done/ gets a ⌸ chip at the end of its footer row — the tray's own glyph — arming on the first click and archiving on the second, through the routes and the ARCHIVE_FROM guard that already existed. In-progress and review cards do not get one: the board offers what it will do. Committed by hand after the run that wrote it ended mid-turn without committing. The work is the agent's; the suite passes on it (875 tests) and it is unchanged from what the run left staged.
This commit is contained in:
@@ -108,6 +108,16 @@ out of every column, never deleted, Status set to `Archived`. The toast says
|
||||
without an undo in the same breath. Cards in the working stages
|
||||
(in-progress, review) cannot be archived; finish or walk them back first.
|
||||
|
||||
The same action sits on the card, for the common tidy-up the length of the
|
||||
board is too far to drag: a **⌸** chip at the right-hand end of the footer
|
||||
row, wearing the tray's own glyph, arming on the first click and firing on
|
||||
the second. It is there on exactly the cards the tray accepts — a working
|
||||
card has no chip at all rather than one that refuses — and it is one
|
||||
action, not two: the same request, the same ⌘Z toast, the same count on
|
||||
the tray. Which stages may be archived from is answered once, by the
|
||||
server that enforces it, and sent with the state; the drag gesture and the
|
||||
chip both read that answer.
|
||||
|
||||
Archiving is a move, so it commits like one: under `BOARD_COMMIT_MOVES`
|
||||
the rename into `tasks/archive/` lands in a single `board: <n> → archived
|
||||
(<name>)` commit naming both paths, and ⌘Z commits its own way back. That
|
||||
|
||||
Reference in New Issue
Block a user