| name | status |
| description | Use when a Make It Real run needs a read-only status summary of setup, hooks, Kanban state, active work, blockers, or verification evidence. |
Make It Real Status
Summarize the current harness state without changing implementation.
Dashboard Boundary
The browser dashboard is read-only observability. It may show the next recommended Claude Code command, evidence paths, and Kanban status.
State changes belong to Claude Code conversation, Make It Real hooks, and internal engine gates. Do not add browser buttons for approval, launch, retry, reconcile, or Done transitions.
Procedure
- Read hook status, run directory, board lanes, active claims, mailbox/blockers, runtime state, and latest verification evidence.
- Start with
makeitreal-engine status "${CLAUDE_PROJECT_DIR:-$PWD}" when the plugin binary is available.
- Treat status as control-plane read-only. It may refresh generated
preview/ dashboard artifacts when config enables dashboard refresh, but it must not mutate board/run/approval/config/evidence state.
- If
dashboardRefresh.dashboardUrl is present and dashboard auto-open is enabled, run makeitreal-engine dashboard open "$RUN_DIR" --project-root "${CLAUDE_PROJECT_DIR:-$PWD}" so the browser dashboard appears for the operator.
- Report the stable operator summary fields:
phase, blueprintStatus, headline, blockers, nextAction, evidenceSummary, dashboardRefresh, and dashboardUrl.
- Separate verified facts from suspected causes.
- Identify the next actionable workflow command: setup, plan, launch, or verify.
Operator Report
Lead with the operator-facing phase, blockers, evidence summary, dashboard URL,
and next public action. Keep raw engine fields, JSON envelopes, run ids, hashes,
contract ids, and HARNESS codes in an advanced diagnostic note only when the user
asks or troubleshooting requires it. Do not lead with raw engine fields.
Zoom-Out Guidance
Status is the operator's zoom-out surface. It should answer:
- current phase;
- why blocked, if blocked;
- missing artifact, evidence, approval, or contract;
- one next action using only public commands;
- whether the browser dashboard was refreshed or intentionally skipped.
When plan generation failed with responsibility ambiguity, surface suggestedBoundaries as review guidance: proposed owner, allowed paths, contract ID, and verification command. Do not convert those suggestions into board mutations from status.
Phase Contract
Status may report planning-required, approval-required, launch-ready, running, verifying, human-review, failed-fast, rework-required, blocked, or done.
Use only public next actions in the user-facing report:
/mir:setup/mir:plan <request>/mir:config- Conversational Blueprint review recorded by the current Claude Code session
/mir:plan approve as the explicit/scriptable control/mir:launch/mir:status/mir:verify/mir:doctor
Output
Keep the report short: current phase, completed items, active blockers, and the next command to run.
