Community route
Ask in Discussions Usage question
Configuration, workflows, and integration help from other users.
Choose the right public or private path
Community
Get help, report a problem, shape a focused proposal, or contribute without exposing secrets, source, logs, or personal data.
Keep private material private.
Never post credentials, private source, raw environment values, browser bootstrap URLs, database contents, or an unreviewed support bundle. Security reports belong in the private advisory flow.
Community route
Open a bug report Reproducible bug
One behavior with a minimal safe reproduction and no private repository material.
Community route
Propose a feature Focused proposal
A concrete user problem, boundary, and outcome—not a speculative platform expansion.
Community route
Report a docs problem Documentation correction
A wrong command, stale claim, missing example, or accessibility issue.
Private route
Report privately Security concern
Potential vulnerabilities must stay private until coordinated disclosure.
Community route
Start contributing Code contribution
Pick a bounded issue, follow domain rules, add tests, and submit a focused change.
Support boundaries
Useful context, clear limits.
Community support has no response-time SLA and covers listed platforms and supported releases. Maintainers may request a minimal public fixture when private repository content prevents reproduction.
Contributor showcase foundation
Credit follows reviewed work.
Release stories and repository history remain the source of contributor attribution. A dedicated showcase will appear after community contributions exist; it will never be filled with placeholder people or invented endorsements.