Inspect telemetry

<!-- 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: 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 context questions, run singularity-flow context xray <WORK-ID> --json. For token questions, run singularity-flow tokens report <WORK-ID> --json. Omit <WORK-ID> only when governed Story work is active. Otherwise run singularity-flow telemetry status --json.
2. Show the qualified state (captured, partial, unavailable, conflict, or disabled), SFlow-owned launch counts, capability mode, and pending generations. Do not expose host paths or raw event content.
3. If disclosure is required, explain that /sf-telemetry cannot accept it on the contributor's behalf. Ask before running singularity-flow telemetry enable --confirm "ENABLE LOCAL USAGE" --json; quote the metadata-only disclosure first.
4. If a completed generation is pending, ask before running singularity-flow telemetry reconcile [PHASE] --json; reconciliation commits and pushes only the sanitized record.
5. Run singularity-flow telemetry disable --json only when explicitly requested. Disabling changes future local capture only and never governs work.
6. Report unavailable when the provider omitted model, tokens, or cost. Never estimate, and never treat native IDE chat as captured by an adjacent CLI launch.
7. Keep provider observations separate from SFlow packet estimates. Preserve every metric's status and assurance, and never call omitted context “tokens saved.”