storyink 0.3.0 → 0.3.1

package/CHANGELOG.md

@@ -1,5 +1,28 @@
 # Changelog
 
+## 0.3.1
+
+- **Fix: Play did nothing under reduced motion.** With Reduce Motion on (OS or `#motion=reduced`),
+  Play now walks the story step by step ("Play steps"): each step's settled state at once (reveals,
+  landed pulses, counters, the whole caption), held for its reading time (caption read time or
+  1.5 s), then the next, ending on the final frame. No pulses, trails, glows or tweens. Pause, ←/→,
+  Shift+←/→, R (restart from step 1, no rewind) and the scrubber work on settled steps. The page
+  loads on the final frame with a static play button; `autoplay` is ignored.
+- **`story.motion`: `"full"` (default) | `"reduced"` | `"system"`.** Full motion is the default and
+  **ignores the reader's OS reduced-motion setting**; `"system"` restores the 0.3.0 behaviour
+  (follow `prefers-reduced-motion`), `"reduced"` always steps. Auto stories:
+  `{ "steps": "auto", "motion": … }`, `render --motion …`, tool `storyink_render` `motion`.
+  Precedence: `#motion=` > the reader's toolbar choice > `story.motion` > OS (only for `"system"`).
+- Viewer toolbar: **Motion: full / reduced** toggle (`aria-pressed`, shortcut `M`), saved in
+  `localStorage`; `#motion=` still wins. Switching mid-playback continues from the current step.
+- Core: `steppedSchedule`, `steppedTime`, `steppedIndex`, `steppedStop`, `STEP_BEAT` and
+  `storyState(…, { stepped: true })`.
+- Snapshot: `--motion reduced` (tool `motion`) captures stepped `at` frames; new gate `reduced=stepped`.
+- Fix: live counter reels were placed at the node-local position (top-left of the diagram) and
+  shown before their node was revealed; they now sit on their node and follow its reveal.
+  `bun run verify:viewer` checks this in headless Chrome (full play, reduced → full, reload,
+  resize, theme toggle) along with stepped playback.
+
 ## 0.3.0
 
 - **Animated SVG (SMIL):** the story plays inside a plain `<img>`, so in GitHub READMEs and PR

package/README.md

@@ -52,7 +52,7 @@ storyink render <in.json|in.mmd|-> [-o out.html] [--svg out.svg] [--theme light|
 storyink mermaid <in.mmd> [-o out.json]
 storyink validate <in> [--json]
 storyink snapshot <out.html> [--theme light,dark] [--width N] [--sheet [themes|beats]|--no-sheet] [--at 0.5,1.2,end] [--scale 2] [-o dir] [--json]
-                  [--preview out.jpg [--preview-size 1024]]
+                  [--preview out.jpg [--preview-size 1024]] [--motion reduced]
 storyink skill
 ```
 
@@ -122,7 +122,15 @@ Add a `story` to play a diagram as a sequence of beats in the HTML viewer:
 
 `"story": "auto"` (or `--story auto`) derives the beats from the graph or message order. Playback
 has a click-to-play gate, play/pause, a tape-rewind replay and a scrubber with step and chapter
-ticks. Space, ←/→ and R control it. When reduced motion is on, the viewer jumps to the final frame.
+ticks. Space, ←/→ and R control it.
+
+Motion is **full by default, even when the reader's system asks for reduced motion**. Authors can
+set `"story": { "motion": "reduced" }` (always step by step) or `"motion": "system"` (follow
+`prefers-reduced-motion`); `--motion full|reduced|system` on `render` does the same, including
+for auto stories. Readers switch with the toolbar's **Motion** toggle (`M`, remembered), and
+`#motion=full|reduced` overrides everything. In reduced mode Play walks the story step by step:
+each step's settled state shown at once and held for its reading time, with no travelling pulses
+or tweens, and the page opens on the final frame.
 
 The final frame is always the static diagram. Every frame is a pure function of time
 (`storyState(scene, timeline, t)`), so `#t=2.5` seeks exactly and