carlos / platform Public

The moves rehearsal runbook (moves Phase 1 Plan 7, branch moves-phase1-7) needs three kinds of evidence after every run:

• a move's detail=1 answer from the console: the reports, evidence keys, log keys and timings;
• the log entry bodies under the move's log prefix;
• the stopped-*.json reports.

No carlos command prints any of these today. carlos move status prints the flat view only. So the runbook reads the login token from ~/.carlos/credentials and calls the API with curl, and it reads log bodies straight from the deployment bucket with an AWS profile.

Ask: a flag such as carlos move status --detail [--json], operators only, that prints the detail answer and the log entries (bodies included) through the console. Rehearsal operators would then need no bucket credentials and no hand-built API calls. Any new sentences go through copy review.