A remove pair for task edges

What it does

Asks for a ruling on task-list edges, which are add-only today: add a remove pair (remove_blocks and remove_blocked_by), or refuse self-edges and cycles when an edge is written.

Source

ganja-code-e788 (a remove pair for task edges; an open question).

The bead is closed when this issue is published, with its external reference pointing here (#38).

File and line references in this issue are to main as of 75a7a92.

Against the three criteria

• Direction (README): The README names the team model as a pillar of the product (README.md:6-8).
• Today's terminal users: A wrong edge or a cycle is undone today only by deleting a task. A self-edge is accepted on purpose.
• Evidence: The lead's 2026-09-03 ruling — keep edges add-only and document the cost — has landed; what stays open is the choice above.

Depends on

Nothing.

Verdict

• Verdict: park
• Reopens: when a do slot frees up in this theme (one slot is open; the captain chose to keep it waiting; its order against #73 is not set).
• Exception to the probe rule: no.
• Date: 2026-09-19
• Verdict ticket: #40

Theme: #53

Read README.md:6-8 and verdict ticket #40 first; this issue is a parked design question rather than an implementation task. It becomes actionable only after the team chooses between remove pairs and edge validation, with the chosen behavior and scope recorded clearly enough to implement and verify.