hermes - 💡(How to fix) Fix One-shot smoke: add Flue-backed orchestration fixture

What to build

Create the smallest safe test target for validating the Flue-backed one-shot pipeline from Slack/Hermes through GitHub Issues, Kanban, Absurd, Flue, Shannon/Claude Opus 4.8, verification gates, and green-gated push to main.

This issue is intentionally low-risk and should be used as the first simple issue to run through the new pipeline once the Flue harness/skill behavior is ready.

Acceptance criteria

• Add a tiny, non-production fixture or documentation artifact that proves the Flue-backed one-shot pipeline can process a GitHub Issue end-to-end.
• The run records/prints the expected durable IDs where available: GitHub Issue, Kanban card/task, Absurd task/run, Flue workflow/session, and final commit.
• The one-shot uses an isolated worktree/sandbox and Shannon/Claude Opus 4.8 for any implementation/conflict-resolution step.
• Required gates are explicit and green before pushing to main.
• If any gate fails, the run fails closed and reports what was tried.

Blocked by

• Flue one-shot orchestration design/spec and skill updates from the Slack planning session.

Dependency metadata

blocked_by:
  - "Flue one-shot orchestration design/spec and skill updates"
blocks: []
afk: true
confidence: high
kanban_sync: pending

Notes

This issue should remain small. Prefer a docs/fixture change over product behavior so the first pipeline run validates orchestration mechanics without risking user-facing functionality.