Report problems without exposing secrets.

The full reporting, tracking and notification backend is a separate security-sensitive subsystem. This page currently provides safe support boundaries.

Planned

Report problem

A structured report flow will collect only safe diagnostics and issue context.

Planned

Track report

Report IDs and status tracking will be enabled when the backend lands.

In Development

Known issues

Until the support system exists, use repository issues for non-sensitive reproducible defects.

Available

Security

Sensitive vulnerabilities should follow the repository SECURITY.md process, not public issue content.

Security guidance ↗

Never send secrets.

No support workflow should request seed phrases, private keys, AWS credentials, privileged RPC credentials or authentication tokens.