AgentBoard's claim engine hands the next queued card to whichever worker asks for one. Version 1.24.0 corrects what the skill tells agents about which columns that draws from: the board's own declaration decides, so a staging column now stays staged.
What's new in v1.24.0
- Breaking: a worker that passes no role is now held to the columns the board declares claimable. It used to scan every column. A board that declares no
claimable_by_rolesanywhere behaves exactly as before; on a board that declares one, passcolumns=[...]to reach anything outside the declared set. - A card parked in a staging column is no longer claimed out from under its pin. Staging a card and then setting its build pins was a race the staging side kept losing, because the card was claimable the moment it existed. Set the pins in the create call, or park the card in a column the board does not declare.
- The old remedy is gone from the recipes. The skill used to advise clearing a worker's role to widen a claim that was returning nothing. That is now a dead end, and both
set-up-claim-lanesandparallelize-a-plan-with-depssay what actually widens it. - An explicit `columns=[...]` still overrides the gate. Naming a staging column is a deliberate act by a caller that knows the board, so the change closes the implicit scan and leaves the explicit request alone.
The column that says who may claim a card is now the column that decides.
Upgrade from the OPVS marketplace to @opvs-ai/agentboard 1.24.0. Boards that declare no claim lanes need no migration; the claim grammar is in the docs at https://opvs.ai/skills/agentboard