SUPPORT / PUBLIC AND PRIVATE ROUTES

Support and reporting

Use the route that matches the information you need to share. GitHub issues are public.

Get help with a test#

Start with Troubleshooting and Compatibility and evidence . They explain common failure categories, current release targets, and terminal limits.

For a reproducible defect containing information safe to publish, open the structured bug-report form . Include the runner version/archive/checksum, host, target version, minimal spec, exact status/category, and reviewed evidence.

Remove credentials, private source, personal paths, command arguments, typed values, and sensitive terminal output before posting. No response-time or long-term support SLA is promised.

Report a security problem privately#

Use GitHub private vulnerability reporting . Do not put vulnerabilities, exploits, credentials, or unsanitized evidence in a public issue.

Compatibility policy#

Stable v0.1.0 accepts spec v1 and emits report v1. Published tags and assets are not overwritten. Read the complete support policy source for compatibility rules and release-blocker definitions.