Explain current code changes

Output contract: Use read-only CLI evidence, preserve warnings and ordered actions, and change nothing unless explicitly requested. For suggested actions, pair Shell with the returned Copilot command; honor commandGuidance. If absent, say "Copilot: no verified equivalent"; never invent a slash command.

Boundary: singularity-flow session current --json → ready/workId, cwd=repositoryPath; use CLI/workItemRoot paths; never $HOME.

1. In the Boundary repository, run exactly one explanation command:
   • normally: singularity-flow explain code $ARGUMENTS --json;
   • when $ARGUMENTS already contains --narrate, use that same command unchanged;
   • only when the user explicitly asks for a narrative or walkthrough in prose and $ARGUMENTS does not contain
     --narrate: singularity-flow explain code $ARGUMENTS --narrate --json.
     Never run both forms in one invocation.
2. Relay the returned computed sections, availability reasons, stable IDs, authority labels, and next actions unchanged. For narration, preserve the exact Narrative — advisory, not a record banner and citation IDs.
3. Stop. Never read or summarize source files yourself, infer a missing cause or caller, call a criterion satisfied, store narrative as evidence, or perform any lifecycle mutation.