Examples you can inspect#
Use an example to understand a behavior, then follow its guide or source. Each example identifies whether it is a real host interaction, an experimental interface, or illustrative report data.
| Example | Try or inspect | What it establishes |
|---|---|---|
| Interactive bug reporter | Right-edge button, capture setup, recording, review and settings | Maintained reporting UI with simulated capture/submission |
| Small on-demand API examples | Read focused code, run, inspect and reset | Supported report revisions and configuration cleanup |
| Full demonstrations | Separate host, capture, diagnostic and reporting pages | Real host behavior and clearly labelled experiments |
| Maintained sample site | Buggy/fixed saves, reset, plain HTML and the bug reporter | Deterministic host behavior and interactive reporting |
| Markdown test catalog | Definitions, sections, inherited hooks and evidence policy | How to author the sample's acceptance checks |
| Portable and test-run results | Local report generation, report data and reviewed run output | How results, incidental problems and sanitized exports relate |
Start with the profile scenario#
Save Morgan Lee in buggy mode, navigate away, and return. The displayed confirmation and retained value disagree. Repeat in fixed mode and compare. The first test run explains how to execute the relevant authored test with an actual runtime.
Read code alongside the example#
The maintained examples use supported entries and one shared scenario implementation. Example contributor guidance describes startup and build layout. The public API reference identifies consumer imports; private implementation paths are source inspection links only.
Illustrative screenshots, recordings, and fixture reports are not proof of an actual run. Only observed actions and collected evidence from the executing runtime establish a result.