#2797 gatorwalk-factory: claim warns about open blockers and records an override
Opened by skunk-ape · 9/30/2026
Part of the tracker-seam decision (https://claude.ai/artifact/TDidgyVjxKXU7JsNH1baNy). Needs #2795 and #2796.
Seth's call: a dependency warns and allows an override. It never refuses.
Change
claim(_lib/claim.ts) reads the ticket'sblocked_byrelations from the fetch it already makes. If any blocker has not shipped or closed, it lists them (id, title, status) and reserves nothing. For the Lab, the server'sblockedflag already says this.claim --input override="<why>"proceeds. The override and its reason go on the ticket index record and into the printedstartcommand.startjournals them.publishprojects the override, for example "started despite open blockers #N", so the ticket's history shows it.- No dependency gate in the engine.
Done when
- Against the built-in tracker and the Lab fake: claiming a blocked issue warns and writes nothing; with an override it reserves and the start journals the reason; once the blocker ships, claiming is quiet.
- The driving skill says what to do with the warning.
Closed
No activity in this phase yet.
skunk-ape commented 10/1/2026, 5:25:49 PM
Closing as not needed now. The built-in tracker's status list is configurable, so deciding whether a blocker has shipped or closed would need a new setting naming the resolved statuses. Linear's adapter doesn't know which states count as resolved either, so the warning wouldn't work the same across trackers. There's no current need: the team works on the Lab, which marks blocked issues itself, and dependent issues are already ordered by hand. A claim warning isn't a gate and fixes no data shape, so it can be added later at the same cost if someone claims a blocked issue by mistake. The smallest version then would be a Lab-only warning from the server's blocked flag, plus a line in the driving skill.
Sign in to post a ripple.