Who may release another member's task claim

What it does

Asks for a ruling: may any member release another member's task claim, or only the current owner and the lead? Whichever is chosen is pinned with a test.

Source

ganja-code-8q4r (may a member release another member's task claim; 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 release writes an empty owner without checking the caller (crates/ganja-core/src/teammate/tasklist.rs:297-300), so any member can take another's task in two calls, while the tool description presents release as the lead's reassignment move.
• Evidence: Known from the code; no report of a member taking another's task is recorded.

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 #74 is not set).
• Exception to the probe rule: no.
• Date: 2026-09-19
• Verdict ticket: #40

Theme: #53

Start with the release path in crates/ganja-core/src/teammate/tasklist.rs:297-300 and the team model described in README.md:6-8. Review verdict ticket #40 for the parked decision and inspect the existing tests around task claims. Done means the chosen release authority is recorded in a test and the issue's ruling is settled.