Repository navigation
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
Open
AndreyBegma wants to merge 8 commits into
AndreyBegma wants to merge 8 commits into
Conversation
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
marked this pull request as ready for review
October 26, 2026 17:38
…o-videos-dwell-after-each-step-h
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed and why
pacingscenario object (stepDwellMs1000,typingDelayMs80) withresolvePacing; afilltakestypingDelayMs. The per-step dwell override reuses C-191'shold, which now accepts 0 (turns the dwell off). The end hold reusesrender.endHoldMs, whose default is now 3500. Schemas regenerated.step.hold ?? pacing.stepDwellMsthrough C-191's hold path (recorded asholdMs, 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.holdMsand the end hold at real speed.holdandrender.endHoldMsdocs updated.Acceptance criteria
pacing.spec.ts(stepPace, paced run).render.endHoldMsdefault 3500 (core + CLI render test); paced run test holds the end.stepPacedefaults.pacing.*, stephold, filltypingDelayMs, 0 off — core and engine tests.waitadds to the dwell; setup not slowed — paced run tests.Nautelle-Card: C-203