Contributing

Pick the right path

• Use Discussions for setup, compatibility, and workflow questions.
• Use a bug report for a reproducible defect.
• Use a feature request for a bounded workflow proposal.
• Use private vulnerability reporting for security issues.

The repository's CONTRIBUTING.md is the canonical setup, style, validation, privacy, and pull-request guide. The Code of Conduct applies to all project spaces.

Evidence expected in a pull request

Describe the problem, affected layer, behavior change, tests run, device coverage, privacy impact, and known limitations. Use synthetic or sanitized screenshots and logs. Changes to process handling should exercise real short-lived child processes where practical; packaging changes should validate the frozen application and both release architectures.

The product audit records current architecture risks, ecosystem boundaries, and prioritized work.