Support without putting private order data in public.
Community support is public. Security reports and Team order support use separate private paths.
Community questions and reproducible bugs
Search or open a GitHub issue. Include the Community version, host, operating system, expected behavior, observed behavior, and a minimal redacted reproduction. Never include credentials, private keys, access tokens, or unrelated customer data.
Security reports
Use a private GitHub Security Advisory for a suspected vulnerability. Do not disclose an exploitable report in a public issue.
Team Local order, recovery, or refund support
For an existing Team order, open the private Team support route and authenticate with the receipt-bound recovery material. Authorized agents may POST https://living-stack-agent-checkout-live.neoaethel.workers.dev/api/v1/team-local/support. The route records a support or refund request; it never auto-refunds or exposes order details in a public issue.
When sales are live, use the private support link bound into the Stripe checkout or fulfillment receipt. The authenticated agent route records a support or refund request; it never auto-refunds. Do not put an order identifier, payment reference, wallet address, recovery kit, installation private key, or package link in GitHub.
Community issues
Good for install help, documentation gaps, and redacted reproducible bugs.
Security and paid orders
Security Advisories protect vulnerability details. The receipt-bound Team route protects purchase and recovery data.