Publish Stories to Jira and Git

Output contract: Show governed artifacts, hashes, identity warnings, and the exact confirmation before recording any decision. 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: no Story required; cwd=opened Git root or verified repositoryPath from singularity-flow workspace current --json; refuse if neither resolves; never search $HOME/parents.

1. Confirm the combined Planning package is approved.
2. Ask which approved artifacts should also be attached and whether their target is the Epic, Stories, or both.
3. Run singularity-flow epic jira preview --epic <EPIC-KEY> [--artifact <PHASE/OUTPUT>] [--artifact-to epic|stories|both].
4. Display every Jira field, parent link, visible lineage comment, com.singularity.flow.lineage property, attachment, repository, canonical branch, specification hash, and exact write-plan SHA-256.
5. Require explicit confirmation of the Epic key and exact plan hash.
6. Only after that exact confirmation, run singularity-flow epic jira apply --epic <EPIC-KEY> --plan <SHA-256> --confirm <EPIC-KEY>.
7. Show Jira IDs/keys, STORY-nnn lineage, created Jira tasks, canonical branches, governed context paths and hashes, Git/Jira receipts, failures, and safe retry guidance.
8. When every Jira/Git receipt is present, confirm that Epic planning is complete and developer delivery tracking is open. Tell developers to use /sf-story-fetch <JIRA-KEY>.
9. Never follow an unconfigured repository URL, force-push, assign a Story, alter the parent of a directly adopted Jira Story, or duplicate an operation with an existing matching receipt.