Inspect Revision Loop readiness

<!-- 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: concise-relay -->

Output contract: Relay requested CLI fields or output faithfully; preserve warnings/errors and only the explanations required below. 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: machine-local; no repository or Story required. Use explicit arguments or SFlow-returned paths; never search $HOME or infer a repository. 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. Require exactly one explicit action: capabilities, activation, or attachments. Do not infer a mutating action from a question.
2. For capabilities, run singularity-flow revision capabilities --json. This is a machine-local, read-only description of the installed execution profile.
3. For attachments, run singularity-flow revision attachments capabilities --json. This describes supported intake only; it does not require or register a Story attachment.
4. For activation, run singularity-flow workspace current --json. Use only a returned repositoryPath as cwd, then run singularity-flow revision activation --json. If no repository is selected, report that exact prerequisite and stop; never search for one.
5. Relay the result and stop. eligible: true means only that this installed guarded profile passed its declared checks; it grants no publication, approval, merge, or deployment authority. Never preview/register/remove attachments, create a Candidate, execute a revision, modify opt-in configuration, publish, approve, commit, or push.