rtmx-ai / rtmx / 28056614958

83%

push

github

feat(mcp): add set_status tool — status writeback with provenance (REQ-MCP-011) (#128)

The MCP surface exposed claim/release (orchestration) and verify (closed-loop
completion) but no way to set a requirement's status — to reopen a regressed
requirement, mark work started, or park a blocked one. Consumers worked around
it by editing .rtmx/database.csv directly (a second writer to the database).

Add a `set_status` mutation tool (req_id, status, agent_id, optional reason)
mirroring the claim/release authorization model. It deliberately REJECTS
COMPLETE: completion is verify-driven (tests decide closure), so letting an agent
mark its own work COMPLETE would reintroduce a self-grading loop. PARTIAL /
MISSING / NOT_STARTED are permitted.

- internal/adapters/mcp: tool definition, dispatch case, toolSetStatus impl.
- set_status_test.go: happy path + persistence, COMPLETE refused, missing
  agent_id refused, unknown req errors.
- server_test.go: tool count 10 -> 11 (4 mutation tools).
- .rtmx: REQ-MCP-011 + spec, reciprocal block on REQ-MCP-005.

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

46 of 54 new or added lines in 1 file covered. (85.19%)

16521 of 19920 relevant lines covered (82.94%)

29.8 hits per line