[GH-ISSUE #565] Assert CLI/MCP parity and derive CLI failure classification from the contract #289

New issue

Closed

opened 2026-10-15 18:23:30 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 18:23:30 +00:00

Owner

Originally created by @morluto on GitHub (Oct 5, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/565

Remaining scope

The original claim that fifteen MCP operations lack CLI counterparts is not established: native commands such as trace-native-values are present. Audit reachability against the canonical contract and assert intentional adapter coverage. CLI failure classification remains a hand-maintained status list. Derive actual failure outcomes from shared semantics; partial or truncated evidence is not automatically an operation failure. Verify equivalent observable results and errors, rather than merely matching catalog counts.

Verification

Exercise representative valid and malformed producer data through the consumer boundary and assert the resulting observations, unknowns, or actionable failure. Keep CLI/MCP behavior aligned where applicable.

This scope was refreshed after removal of replay and permission plumbing and merge of PR #538; implementation is being addressed in the boundary root-cause cleanup.

Originally created by @morluto on GitHub (Oct 5, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/565 ## Remaining scope The original claim that fifteen MCP operations lack CLI counterparts is not established: native commands such as trace-native-values are present. Audit reachability against the canonical contract and assert intentional adapter coverage. CLI failure classification remains a hand-maintained status list. Derive actual failure outcomes from shared semantics; partial or truncated evidence is not automatically an operation failure. Verify equivalent observable results and errors, rather than merely matching catalog counts. ## Verification Exercise representative valid and malformed producer data through the consumer boundary and assert the resulting observations, unknowns, or actionable failure. Keep CLI/MCP behavior aligned where applicable. This scope was refreshed after removal of replay and permission plumbing and merge of PR #538; implementation is being addressed in the boundary root-cause cleanup.

bsakaguchi

2026-10-15 18:23:30 +00:00