Use the repository's public issue template for reproducible defects in published release assets. Identify the product or component, exact release tag or package version, asset filename or package name, operating system and CPU architecture when applicable, safe error kind, and minimal reproduction steps. For Labor0 CLI bundles, include the l0 version and labor0-runner version output.
Never attach diagnostic ZIPs or raw logs to a public issue, even when they were created by the CLI's redacted diagnostics command. Do not paste credentials, device codes, runner tokens, environment values, private repository names or paths, user names, workspace identifiers, prompts, provider output, or other customer data. Reduce evidence to the smallest secret-free description needed to reproduce the behavior.
For account, security, or data-exposure concerns, use the private Labor0 support channel instead of a public issue.