Contributing

This project benefits most from focused pull requests with clear user impact.

Before You Open a Pull Request

Confirm the problem is reproducible or the feature request is concrete.
Keep the change scope narrow.
Verify the affected workflow locally.
Update docs when user behavior or setup steps change.

Pull Request Expectations

Explain what changed and why.
Explain user-visible impact.
Mention how you verified the change.
Call out known limits instead of hiding them.

Issue Reports

Useful reports usually include:

App version
Device and Android version
Exact steps to reproduce
Relevant logs or screenshots
Whether the problem affects built-in or external sources

Documentation Policy

README.md is the short project landing page.
docs/ holds setup guides, troubleshooting, and reference material.
New features should usually add or update a task-oriented document.