feat: GitHub Sponsors link (Settings + repo Sponsor button)

[sarim2000]

Lowest-friction monetization for the current scale (1k+ installs / 80 reviews / 4.6★). No Play Billing yet, no review-bomb risk, no AGPL server-side complications, doesn't contradict the README "no hidden costs" promise. Pure goodwill support.

Changes

• .github/FUNDING.yml — adds the "Sponsor ❤" button to the GitHub repo header. Pointed at sarim2000. Activates as soon as GitHub Sponsors enrollment is approved (file is harmless until then).
• Settings → Support & Community → "Support development" — opens github.com/sponsors/sarim2000 in the browser. Lives below "Report an Issue", uses the existing SettingsNavItem pattern, red heart icon to stand out from the blue/pink neighbours.

Why this and not Play Billing

At 1k installs the math doesn't work for subscription (~₹50/month realistic), and adding a Play Billing tip jar would burn a week on Merchant account + tax forms + sandbox testing. GitHub Sponsors costs zero infrastructure, taps the same goodwill pool, and skips Google's 15-30% cut.

When the install base or AI/infra spend warrants it, the next monetization step is a one-time Pro unlock (₹199 one-time, client-side features only — AGPL-safe). Subscription stays parked until 10k+ installs + a cloud-cost-bearing feature like sync.

Out of scope

• No Play Billing.
• No UPI/QR (could add later if Sponsors signup is delayed; either path works).
• F-Droid build is unaffected — same Settings entry shows there, linking to GitHub Sponsors is policy-compliant for F-Droid (non-promotional support link).

[greptile-apps]

Greptile Summary

This PR adds a GitHub Sponsors funding path at two levels: a .github/FUNDING.yml file that activates the "Sponsor ❤" button on the repo header, and a new "Support development" settings entry in the app's Support & Community section that opens the GitHub Sponsors page in the browser.

• .github/FUNDING.yml uses the correct single-key YAML format (github: [sarim2000]) and is harmless until enrollment is approved.
• SettingsScreen.kt correctly re-labels "Report an Issue" from ItemPosition.BOTTOM to ItemPosition.MIDDLE and adds the new item as ItemPosition.BOTTOM, preserving proper rounded-corner semantics for the three-item group. The new click handler follows the same Intent(ACTION_VIEW, Uri.parse(…)) pattern already used by the neighbouring "Report an Issue" item.

Confidence Score: 5/5

Safe to merge — both changes are additive, self-contained, and follow established patterns in the codebase.

The FUNDING.yml is a standard inert config file; the Settings change is a single new nav item using the same Intent/Uri pattern already in use immediately above it. The ItemPosition update for 'Report an Issue' is correct for a three-item group. No logic is modified, no existing behavior is altered.

No files require special attention.

Important Files Changed

Filename	Overview
.github/FUNDING.yml	New file adding GitHub Sponsors button to the repo header; uses the correct YAML format for the github key.
app/src/main/java/com/pennywiseai/tracker/ui/screens/settings/SettingsScreen.kt	Adds 'Support development' nav item at the bottom of the Support & Community settings group and correctly updates 'Report an Issue' from BOTTOM to MIDDLE position to maintain proper corner-rounding semantics for three items.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    S["Settings Screen"] --> SC["Support & Community Section"]
    SC --> HF["Help & FAQ\n(ItemPosition.TOP)"]
    SC --> RI["Report an Issue\n(ItemPosition.MIDDLE)\nOpens GitHub Issues"]
    SC --> SD["Support development NEW\n(ItemPosition.BOTTOM)\nOpens GitHub Sponsors"]
    RI --> GH["github.com/.../issues/new"]
    SD --> GS["github.com/sponsors/sarim2000"]

Loading

_{Reviews (1): Last reviewed commit: "feat: GitHub Sponsors link (Settings + r..." | Re-trigger Greptile}