2 Commits

Author	SHA1	Message	Date
Kaoru0822	96d1f0f3fb	fix(cli): refuse scenario steps on passive native UI observation (#2712) ... observe-native-ui and capture-native-ui-scenario were registered in one loop with a shared option schema and description. The passive command therefore advertised `--steps` ("Observe or run a scenario"), accepted any value, and then dispatched observe_native_ui without it, so a caller who selected the wrong command never learned that no scenario ran. Register each command against its own contract. Observation declares only the passive scope options, so `--steps` is rejected as an unknown flag; the scenario command keeps its JSON step decoding and validation. Each command now has its own description. Fixes #2674 Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-13 06:59:33 -07:00
morluto	4a6073810a	fix(contracts): align CLI/MCP boundary contracts (#946) ... * fix(cli): validate native scenario and preserve JSON paths * fix(process): reject invalid UTF-8 JSON inputs * fix(cli): retain missing JSON path diagnostics * test(cli): cover relative brace and bracket JSON paths * test(cli): reject missing native scenario steps * fix(mcp): advertise reserved process environment key * fix(process): reject NUL in process scenario values * fix(process): advertise NUL input constraints to MCP * fix(cli): report scenario input schema issues * fix(contracts): align CLI and MCP input validation * fix(mcp): document semantic output constraints * fix(mcp): describe process journal compatibility * docs: regenerate catalog after schema grouping * docs: regenerate catalog after main merge * fix(cli): preserve JSON and native UI input diagnostics * test(mcp): reuse advertised tool schemas in managed flow	2026-10-08 00:03:36 +08:00