statuslisted

# Status Report where the work stands in language a person can act on. The engine's JSON is the input to your answer, never the answer itself. ## Gather Run the status command and read the whole JSON document before writing a word: ``` "${CLAUDE_PLUGIN_ROOT}/bin/sbe" status --json ``` When `scope.storesInspected.dossiers` names a discovered dossier, also run `"${CLAUDE_PLUGIN_ROOT}/bin/sbe" status --team --json` and read its `findings` and `changes` for the per-dossier detail the single-project report rolls up into one summary. Also run `"${CLAUDE_PLUGIN_ROOT}/bin/sbe" task list` to see the live task ownership. An open task tells the user which files are currently claimed for editing and by what work, which matters to anyone deciding what to touch next. If either command fails, report the failure plainly, say what you could still observe, and recommend `"${CLAUDE_PLUGIN_ROOT}/bin/sbe" doctor --json` as the next action. See `${CLAUDE_PLUGIN_ROOT}/docs/CLI.md` for what each command covers. ## Reframe, do not relay Lead with the guided shape, in plain sentences, each sourced from a named field rather than a paraphrase of the rendered text: 1. **Where you are**: the five sections, `brokenClaims`, `mergeBlockers`, `activeConflicts`, `missingEvidence`, `soundEvidence`, read in that order; the first one holding an item names the stage. All five empty: read `notes` for the clean or NO-DATA line behind that, and `scope.storesInspected` for what was searched. 2. **Wh