Documentation#

Choose a journey, then use guides for tasks and reference for exact contracts. These pages cover the current repository checkout; project status distinguishes shipped workflows from experimental demonstrations and future work.

Use SnagBadger#

1. Choose a supported path and establish prerequisites. Use guided setup for discovery and an approved reporting/testing integration plan.
2. Create a first portable bug report, or run a first Markdown test with your own runtime.
3. Review results and promote problems.
4. Review and sanitize evidence before export.

Start with the sample site when you need a disposable behavior to explore.

Understand the model#

• Reports and evidence: authored steps, actual interactions, revisions and reproduction readiness.
• Plans and sections: reusable definitions, inheritance and execution revisions.
• Runs, results and attempts: retained history, independent comments and aggregation.

Find an exact contract#

Use public APIs, configuration, catalog format, runner commands, skills/runtime requirements, and serialized formats.

Contribute or work as a coding agent#

Setup and first change introduces the pinned toolchain and complete gate. Continue with architecture, quality checks, and worktrees/browser evidence.

Repository-agent verification is different from running the product's agent-testing workflow. Read the correct prerequisites for each. Documentation maintenance explains how to keep this site aligned with code.