Skip to content

C-203: Pace demo videos: dwell after each step, hold the result at the end, type slower - #399

Open
AndreyBegma wants to merge 8 commits into
developfrom
card/c203-pace-demo-videos-dwell-after-each-step-h
Open

AndreyBegma wants to merge 8 commits into
developfrom
card/c203-pace-demo-videos-dwell-after-each-step-h

Conversation

@AndreyBegma

@AndreyBegma AndreyBegma commented Oct 26, 2026 •

Copy link
Copy Markdown
Owner

What changed and why

  • core: new pacing scenario object (stepDwellMs 1000, typingDelayMs 80) with resolvePacing; a fill takes typingDelayMs. The per-step dwell override reuses C-191's hold, which now accepts 0 (turns the dwell off). The end hold reuses render.endHoldMs, whose default is now 3500. Schemas regenerated.
  • engine: after each visible step the run holds step.hold ?? pacing.stepDwellMs through C-191's hold path (recorded as holdMs, never trimmed). The last step gets no default dwell; the C-191 end hold follows it. Setup and off-camera steps are not slowed; check runs add no default dwell. Typing defaults to 80 ms.
  • renderer: unchanged. It already keeps holdMs and the end hold at real speed.
  • docs: "Pacing" section in scenarios docs; hold and render.endHoldMs docs updated.

Acceptance criteria

  • Default ~1000 ms dwell after visible steps — pacing.spec.ts (stepPace, paced run).
  • ~3500 ms end hold — render.endHoldMs default 3500 (core + CLI render test); paced run test holds the end.
  • Typing ~80 ms — stepPace defaults.
  • Overrides: pacing.*, step hold, fill typingDelayMs, 0 off — core and engine tests.
  • Schema and docs describe them.
  • wait adds to the dwell; setup not slowed — paced run tests.
  • Unit tests for defaults, overrides, end hold.
  • Engine release for the Nautelle runner — done by the repo's bump PR after merge.

Nautelle-Card: C-203

Scenarios may set pacing.stepDwellMs, pacing.endHoldMs and pacing.typingDelayMs (defaults 1000/3500/80 ms); any step may override its dwell with dwellMs and a fill its typing speed with typingDelayMs. The timeline records each event's dwell and the run's end hold.
Recorded on-camera steps now wait stepDwellMs after a visible action, the run holds endHoldMs before the video stops, and typing defaults to 80 ms per character. Setup steps, check runs and failed runs are not slowed down.
The idle trim no longer compresses a dwell or the end hold the engine recorded, and a timeline's endHoldMs replaces the fixed 1 s tail. Document pacing in the scenario reference.
Recorded fixture scenarios now get the default pacing; the renderer's real-run tests pin no dwell, a 1 s end hold and 35 ms typing unless a scenario sets its own pacing.
With the default pacing the 26-step repeat takes about 30 s more; the CLI test checks iteration tagging, not pacing. The scenario now sets its own pacing, which also exercises the field through the CLI.
@AndreyBegma
AndreyBegma marked this pull request as ready for review October 26, 2026 17:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant