- "Step N passed" log entry carries the step's return value as data
- context.assert accepts an optional details argument; on failure the
assertion:fail entry stores { details, error } as data
- assertion failures throw AssertionFailedError so "Step N failed" and
"Snippet X failed" entries name only the assertion, without repeating
the details; the step run description keeps the full message
- exported e2e runtime accepts and prints assert details
- log output shows elapsed time in whole seconds, matching the stored
timestamp resolution
- run artifact and scenario file names link to the inline file content
in a new tab
- a (?) button next to the Code label on the step and snippet
create/edit pages opens a reference of the script runtime: globals,
every context member with examples, and pitfalls such as awaiting
getStepOutput and assert
- the reference lives in components/modals/code-help.md and is
rendered as markdown
- Modal takes size="lg" for document-like content; the dialog is
capped to the viewport and its body scrolls, focusable when lg so
the keyboard can scroll it
- docs/scenario.md notes that getStepOutput is async and points to
the in-app reference to keep in sync