Inspect governed work

<!-- sflow-copilot-pause -->

Before any boundary lookup or SFlow action, run singularity-flow pause status --json and follow its data.agentInstruction. If data.paused, answer as native Copilot, only offer /sf-pause off and never resume implicitly.

<!-- sflow-output-contract: guided-actions -->

Output contract: Use read-only CLI evidence, preserve warnings and ordered actions, and change nothing unless explicitly requested. Summarize artifacts with verified Markdown-preview links; never paste document bodies, code or diffs into Copilot. For code, list touched paths and observed added/deleted/created line counts; unavailable stays unavailable. Use existing evidence, not extra calls solely for display. Summaries, links and opened previews are not human review or approval. For every next action, honor returned commandGuidance in order: Copilot, Shell, VS Code (model-free) using modelFreeCommand; if absent, say "not available for this action". Missing Copilot: "no verified equivalent". Never invent routes.

<!-- sflow-execution-boundary -->

Boundary: no Story required; cwd=opened Git root or verified repositoryPath from singularity-flow workspace current --json; refuse if neither resolves; never search $HOME/parents. Use exact CLI-returned paths. repositoryPath is command cwd, not a prefix for absolute file paths. Never rebase paths or strip .git/worktrees. Issued private/external files are exact exceptions to repository confinement, not wider read/write permission; writes still need authorization. Resolve relative paths only against their declared base. On failure, preserve the path and error; never search or recreate it.

1. For an explicit Work ID, run singularity-flow status <WORK-ID> --for-agent --json in the Boundary repository without requiring or changing the active Story. Without an ID, run singularity-flow session status --json; if selection is ambiguous, show candidates and stop.
2. Route the requested view to the exact applicable read command: singularity-flow progress, singularity-flow documents list, singularity-flow wm show-prompt, singularity-flow report, singularity-flow nextsteps, singularity-flow change show <WORK-ID> --shadow --json, or singularity-flow proof status|gaps|signals <WORK-ID> --json. For comprehension, use singularity-flow comprehension regions|check|graph --work-id <WORK-ID> --json; for an exact trace use singularity-flow comprehension explain clause|file|symbol|change|refusal|generation|test <SUBJECT> --work-id <WORK-ID> --json. For Story history use singularity-flow comprehension replay [all|phase <PHASE>|kind <EVENT-KIND>] --work-id <WORK-ID> --json; do not confuse it with or invoke SGOS Process replay. Never infer the subject, phase, or event kind. For an exact predicate explanation use singularity-flow proof explain <WORK-ID> <PREDICATE-ID> --json; never infer the predicate ID. Describe comprehension, shadow Passport, and GDP-M3 proof output as untrusted observe-only diagnostics; never claim that any grants authority. Signals never satisfy predicates or gates. Missing Candidate, proof, AST, or World Model remains an explicit non-blocking gap. With no view, show status, progress, generated artifacts, approvals, warnings, and next actions.
3. Preserve exact artifact paths, hashes, identities, self-approval warnings, model/token availability, and pending-publication state.
4. Do not prepare, publish, submit, approve, reject, synchronize, or edit files. Offer /sf-continue for an explicitly reviewed mutation.