claude
cd6549fa51
The other half of the stage-0 rule. actionAct intercepts task_status ahead of both ecosystem clients, because the board is Maven's own store and reaching a capability registry would answer a question about his task list with a gap. Three answers besides the move, and none of them guesses. No match says so. More than one match asks which, since closing the wrong task marks work he never finished as done. No task named asks which too, because the router claims the turn without the referent and the list lives here. Matching is normalised containment either direction, over the same store.NormalizeTaskText key capture dedupes on — he shortens what he said as often as he pads it. Deliberately not fuzzy: a ranked best guess always returns exactly one answer, and the one thing this has to be able to say is that it is not sure. A candidate he says is done takes both legal store moves. The store refuses candidate → done, and saying it out loud IS the confirmation the candidate was waiting for. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SoL7EBdYC5Mhz3DJd49GJy