Yeachan-Heo 1a2fa1581e Keep status JSON machine-readable for automation ...

The global --output-format json flag already reached prompt-mode responses, but
status and sandbox still bypassed that path and printed human-readable tables.
This change threads the selected output format through direct command aliases
and resumed slash-command execution so status queries emit valid structured
JSON instead of mixed prose.

It also adds end-to-end regression coverage for direct status/sandbox JSON
and resumed /status JSON so shell automation can rely on stable parsing.

Constraint: Global output formatting must stay compatible with existing text-mode reports
Rejected: Require callers to scrape text status tables | fragile and breaks automation
Confidence: high
Scope-risk: narrow
Directive: New direct commands that honor --output-format should thread the format through CliAction and resumed slash execution paths
Tested: cargo build -p rusty-claude-cli
Tested: cargo test -p rusty-claude-cli -- --nocapture
Tested: cargo test --workspace
Tested: cargo run -q -p rusty-claude-cli -- --output-format json status
Tested: cargo run -q -p rusty-claude-cli -- --output-format json sandbox
Not-tested: cargo clippy --workspace --all-targets -- -D warnings (fails in pre-existing runtime files unrelated to this change)

2026-04-05 16:41:02 +00:00

..

cli_flags_and_config_defaults.rs

Keep status JSON machine-readable for automation

2026-04-05 16:41:02 +00:00

mock_parity_harness.rs

feat(runtime): hardened MCP lifecycle with phase tracking and degraded-mode reporting

2026-04-04 00:42:43 +09:00

resume_slash_commands.rs

Keep status JSON machine-readable for automation

2026-04-05 16:41:02 +00:00