¶ Demo Run (Aborted) — Dental Appointment Booking (2026-08-13T174115Z)
- Scene: agents/hermes/demo_scenes/dental_appointment_booking
- Started: 2026-08-13T17:41:15Z
- Stopped: operator stop 17:49:12Z; finalized 17:54:08Z (demo-server restart)
- Result: ABORTED — two-presenter collision (see below)
¶ What happened
The run was triggered from the control panel with the default spawned
presenter while the Hermes session was ALSO presenting the scene manually.
Two presenters drove the same browser concurrently:
- the spawned agent flew through the whole scene — screenshots of the
booking form, booking created and triage queue exist (17:42Z), and the
closing narration was posted at 17:42:44Z; - the manual session logged steps 3–17 (login → appointments list →
booking form: practice + Filling selected) and stopped logging there.
The result was exactly the symptom set documented in demo-agent skill §9c:
narration racing ahead of the visible browser state, the run appearing to
repeat itself, and a viewer left watching a screen that did not match the
narration. The operator stopped the run at 17:49:12Z; the demo-server restart
at 17:54:08Z (code edits) finalized the stop.
Mechanically the booking flow itself was fine (consistent with the morning
PASS runs) — the failure was process, not app.
¶ Fixes already applied (skill §9c)
- NEVER trigger a run with the default spawn while presenting manually.
- Always trigger with
"spawn": falsewhen Hermes presents the scene itself.
¶ Follow-ups
- Re-run the scene cleanly (reseeded, spawn:false) to re-establish the smooth
baseline — the queued next step on the demo backlog.