hermes - 💡(How to fix) Fix Protocol violations (rc=0 without complete/block) don't increment failure_limit counter

When a worker process exits with rc=0 without calling kanban_complete or kanban_block, the dispatcher correctly emits a protocol_violation event, but does NOT increment the task's failure counter. This means failure_limit never triggers for this failure mode, and the card re-dispatches indefinitely.

Fix / Workaround

Summary

When a worker process exits with rc=0 without calling kanban_complete or kanban_block, the dispatcher correctly emits a protocol_violation event, but does NOT increment the task's failure counter. This means failure_limit never triggers for this failure mode, and the card re-dispatches indefinitely.

Repro

1. Set failure_limit: 2 in config.yaml
2. Dispatch a card whose worker consistently exits rc=0 without calling complete/block
3. Observe: dispatcher emits protocol_violation each cycle, failure counter stays at 0, card re-dispatched indefinitely

Observed

Card t_9250007f accumulated 69 dispatch cycles with failure_limit=2 configured. Never auto-blocked. Had to be manually blocked.