# Issue Labels

Use labels to keep early public feedback tied to operator evidence and release gates.

## Core Labels

- `install` - install, upgrade, first-run, rollback, or readiness review.
- `hardware` - device compatibility, appliance candidates, embedded routers, relays, VPS nodes, or portable nodes.
- `dns` - resolver, upstream, rewrite, filtering, or DNS ownership behavior.
- `routing` - route ownership, policy, tunnel, bridge, relay, or fallback behavior.
- `privacy-posture` - leak checks, identity separation, telemetry blocking, and bounded privacy claims.
- `recovery` - rollback, backup, restore, outage, or emergency access procedures.
- `documentation` - unclear, stale, missing, or misleading docs.
- `security-boundary` - support access, redaction, credential custody, or vulnerability-reporting process.
- `needs evidence` - issue needs redacted logs, screenshots, command output, or reproduction notes.
- `good first issue` - scoped public contribution with low operational risk.

## Triage Rules

- Ask for redacted evidence before diagnosing network behavior.
- Redirect vulnerability details to `SECURITY.md` and contact links.
- Close issues that require private keys, tokens, full traffic captures, unredacted topology, or credential custody.
- Keep anonymity claims bounded: The Gateway helps verify privacy posture but does not guarantee anonymity by itself.