# Support

Use the channel that best matches the request:

- **Bug reports:** open a GitHub issue with the bug/regression form. Include a minimal reproduction, environment details, and redacted logs.
- **Feature requests:** open a GitHub issue with the feature request form when the request has clear acceptance criteria.
- **Documentation fixes:** use the documentation issue form or open a focused pull request.
- **Usage questions and ideas:** start a GitHub Discussion.
- **Security reports:** use GitHub Security Advisories, not public issues.
- **Conduct concerns:** follow [`CODE_OF_CONDUCT.md`](CODE_OF_CONDUCT.md).

## Triage SLA

| Severity | First response target | Resolution target |
|---|---:|---:|
| `priority:p0` data loss, security, production block | 24 hours | 7 days |
| `priority:p1` major bug | 3 business days | 30 days |
| `priority:p2` minor bug or feature | 7 days | Next minor when accepted |
| `priority:p3` nice-to-have | 14 days | Best effort |

These targets depend on maintainer availability. If a target is at risk, maintainers should add `help wanted` and describe the specific help needed.

## Before Opening a Bug

- Check the latest release and current open issues.
- Include KiCad, Python, MCP client, transport, and install method.
- Remove tokens, private board data, and customer-specific paths from logs.
- For regressions, include the last working version and first broken version.


## Repository maturity and governance

Repository maturity, OpenSSF evidence, and remaining manual hardening tasks are tracked in [`docs/repo-maturity-report.md`](docs/repo-maturity-report.md), [`docs/openssf-evidence.md`](docs/openssf-evidence.md), and [`docs/openssf-gap-analysis.md`](docs/openssf-gap-analysis.md).
