Land ad hoc work safely

<!-- 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: explicit-selection -->

Output contract: Collect every required choice explicitly; never infer or preselect; preserve errors, artifacts, and next actions. 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. Run singularity-flow adhoc status --json. session: null means none is active: relay its next; to inspect existing work, run singularity-flow land --json.
2. Show every observed resource and the exact change-set digest. The candidate objective is advisory and must never be described as pre-existing intent.
3. Ask the contributor for the objective and at least one observable success criterion. Only after they answer, run singularity-flow adhoc intent confirm <SESSION-ID> --objective "..." --success "..." --confirm <CHANGE-SET-SHA256> --json.
4. Show unresolved resources. Apply only the exact claimed/deviation/split/revert choices the contributor gives; never claim a resource automatically.
5. Run singularity-flow adhoc landing preview <SESSION-ID> --json. If multiple allowlisted tests exist, show the IDs and ask which one to use.
6. If the result is promotion-required, preserve the reasons and offer singularity-flow adhoc promote <SESSION-ID>. Do not weaken protected-path, branch, resource, or verification checks.
7. Show the complete packet digest. Publish only after the contributor explicitly confirms that exact digest, using singularity-flow adhoc publish <SESSION-ID> --confirm <PACKET-SHA256> --json.
8. Report that direct landing is reverse-converged ad hoc work (workflowExecuted: false), together with the exact commit, push status, authority receipt, and any pending recovery.