Merge branch 'main' into ge-hch.3.4.7/add-validate-story-ci

Author: Sorra

.beads/issues.jsonl

@@ -48,6 +48,10 @@ Repo rules:
 - Use `bd` for issue tracking; don’t introduce markdown TODO checklists.
 - Record a `bd` comment/notes update for major items of work or significant changes in design/content (brief rationale + links to relevant files/PRs).
 - Issue notes must list documents created, deleted, or edited while working the issue (paths) and call out any temporary planning stored in `history/`.
+- `main` is always releasable; avoid direct-to-main changes.
+- Use a git branch + PR workflow; do not push directly to `main`.
+- Ensure the working branch is pushed to `origin` before you finish.
+- Do NOT close the Beads issue until the PR is merged.
 
 Boundaries:
 - Ask first:

.opencode/agent/ship.md

@@ -28,6 +28,7 @@ This document explains how to run the InkJS-based smoke demo and where to find i
 ## Telemetry configuration
 - Telemetry facade: `window.Telemetry` (ConsoleTelemetry by default) with methods `emit(eventName, payload?)`, `enable()`, `disable()`, and property `enabled` (boolean).
 - Events emitted by the runner: `story_start` (on story init), `choice_selected` (on every choice), `smoke_triggered` (when the #smoke tag is seen), `story_complete` (when story ends).
+- Note: telemetry emission is performed by the runtime/player (web/demo/js/inkrunner.js) — it does not require content-level choice tags like `#choice_selected`. The runtime emits `choice_selected` when a player choice is selected.
 - Toggle telemetry off: in devtools console run `window.Telemetry.disable()` or set `window.Telemetry.enabled = false`. Re-enable with `window.Telemetry.enable()`.
 
 ## Testing