Observed 2026-08-12 on the ida board: the orchestrator two-hop-closed a ready-for-implementer ticket (in-progress→done) while the sweep had already dispatched and bound a worker to it. Both sessions completed independent solutions (a manifest waiver and a behavior scenario) — the race surfaced only because the worker posted afterwards (ida#1584 trail, ida#1589 report).
board-transition.sh treats 'already in-progress' as the only conflict signal and carries no claim token; a live registry binding on the ticket is not consulted. Direction: a state transition on a ticket with a live worker binding should be refused for everyone except the binding owner (the board-bind live-owner rule from 7.46.7 gives the liveness predicate — host+boot survival — to reuse). Orchestrator-side interim discipline is recorded on ida#1589.
Observed 2026-08-12 on the ida board: the orchestrator two-hop-closed a ready-for-implementer ticket (in-progress→done) while the sweep had already dispatched and bound a worker to it. Both sessions completed independent solutions (a manifest waiver and a behavior scenario) — the race surfaced only because the worker posted afterwards (ida#1584 trail, ida#1589 report).
board-transition.sh treats 'already in-progress' as the only conflict signal and carries no claim token; a live registry binding on the ticket is not consulted. Direction: a state transition on a ticket with a live worker binding should be refused for everyone except the binding owner (the board-bind live-owner rule from 7.46.7 gives the liveness predicate — host+boot survival — to reuse). Orchestrator-side interim discipline is recorded on ida#1589.