storylisted

<!-- @harness-posture: cc-native-with-fallback — !shell injection (SKILL.md:20) + Stop-hook auto-emission (SKILL.md:23) are CC-native; degradation: run helpers/emit-story-prompt.sh manually / tell the story on request --> > **Authoritative for:** /story skill — session recap narrated as a story by acts; localized to the operator's language via AIF_HOOK_LANG; single SSOT for the story spec shared with the Stop-hook branch. > **NOT authoritative for:** project goal — see [README.md#why-this-exists](../../../README.md#why-this-exists). Per-turn self-diagnostic recap (`## 🟢`) — that is a separate output. # /story — session recap as a story Narrate the whole session as an engaging, plain-language story for the human — the reader-facing companion to the dry per-turn self-diagnostic recap (`## 🟢`). Different jobs: a story for the reader vs. a checklist for your own sake. ## Steps 1. Get the localized story instruction. Run: `!bash ${CLAUDE_SKILL_DIR}/helpers/emit-story-prompt.sh` It prints the full story-spec in the operator's language (English by default; Russian when `AIF_HOOK_LANG=ru`) — the single source of truth, shared with the Stop-hook `aif_msg_eot_branch_story` branch. 2. Tell the story, following that instruction exactly: open in one sentence, then by acts (named files / PRs / decisions), explain jargon on the spot, be honest about what's thin / uncertain / left, end on the one thing left for the human. Begin with the marker line the instructio