docs: add contributing-efficiently, ways-to-help, and sponsorship sections

Documents that limited Claude Code quota is best spent on a finished PR
rather than a feature request, adds a ways-to-help list (bug reports,
docs, testing pre-releases), and points to GitHub Sponsors.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Author: malys

.github/FUNDING.yml

@@ -0,0 +1,3 @@
+# Funding platforms for this repository.
+# Renders the "Sponsor" button on GitHub once the account has GitHub Sponsors enabled.
+github: [malys]

CONTRIBUTING.md

@@ -64,6 +64,43 @@ is imposed rather than following the system: the screen faces the driver at nigh
 light background filling the windscreen is glare, not a preference. Keep new surfaces on
 the tokens instead of hard-coded colours or dimensions.
 
+## Ways to help
+
+Not every useful contribution is code:
+
+- **Bug reports** — firmware generation, app version, what you did, what happened.
+- **Feature requests** — describe the problem before the solution.
+- **Documentation** — README, this guide, translations.
+- **Pull requests** — see below.
+- **Testing pre-releases** — install an `unstable` build and report what broke.
+- **Sponsorship** — see below.
+
+## Contributing efficiently
+
+Maintainer time and AI quota are the scarce resources here, ideas are not. If you have
+access to Claude Opus or another capable coding model, a finished pull request is worth
+much more than a feature request: someone still has to design, write, test and verify the
+request, and that someone has a limited quota too.
+
+A pull request that lands quickly usually carries:
+
+- The problem, in one or two sentences.
+- The proposed solution, and what you rejected.
+- The implementation, scoped to one concern.
+- Tests — `mise run check` passes.
+- Documentation updated: README, CHANGELOG, this guide where relevant.
+
+Generate the change locally with whatever model you have, then read every line yourself
+before opening the PR. You are the author, not the model. Unreviewed generated code on a
+path that reaches the vehicle will be sent back.
+
+## Sponsorship
+
+Maintaining EVSuite costs development time, test hardware and AI usage. If it is useful in
+your daily driving, consider sponsoring through
+[GitHub Sponsors](https://github.com/sponsors/malys). Sponsorship covers those costs and
+gets fixes and features out faster.
+
 ## Language and licence
 
 English by default — code, comments, commit messages, docs. Read