Same class as the `/workspace/repo` path and the ZeroClaw tool names: the
skills were written alongside the platform and never compared to it again.
Both found by reading the source of truth before writing a check against
it.
1. `decompose-int-items` showed `PLAN_COMPLETE: INT-01..05`. An id is
strictly `INT-<digits>`, so the range form is rejected outright — the
plan pass records nothing while every item stays open. A live planner
emitted exactly that line. Now one id per line.
2. `workspace-repo-commit-protocol` said the task-card parser advances
mission state on the INT id in the commit subject. Nothing in the
platform reads commit messages; the parser reads `run_events` — the
agent's turn output. An agent that believed it could commit with the id
and never emit `COMPLETED: INT-NN`, leaving the mission open on an item
it had finished. The convention is kept, the mechanism corrected.
`no_skill_shows_a_marker_the_parser_would_reject` runs the real parser
over every marker in every skill's fenced blocks, negative-controlled
against the range form.
Co-Authored-By: Claude Opus 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_018i9Ten1LU4jUr5d7TAWda9