New app: Rouse Context (com.rousecontext)

Required

• The app complies with the inclusion criteria
• The original app author has been notified — I am the app author (Jason Monk / Monkopedia).
• All related fdroiddata and RFP issues have been referenced — there is no RFP or fdroiddata issue for this app.
• Builds with fdroid build — verified locally end to end: source scanner, from-source build, reproducible-binary comparison against the published release asset, and signer check all pass.
• There is an issue tracker and author contact info (IssueTracker in the metadata; author reachable via the GitHub repo).

Strongly Recommended

• The upstream repo contains the app metadata (summary/description/images/changelog) in a Fastlane folder structure.
• Releases are tagged and auto-update is enabled (AutoUpdateMode: Version, UpdateCheckMode: Tags).

Suggested

• External repos added as git submodules — N/A (no srclibs/submodules).
• Reproducible Builds enabled (Binaries: + AllowedAPKSigningKeys; verified with apksigcopier and fdroid build).
• Multiple APKs for native code — N/A (no native code).

---

About the app: Rouse Context turns an Android phone into an on-demand MCP (Model Context Protocol) server, woken via UnifiedPush — no Firebase or Google Play Services.

• gradle: [yes] — the FOSS build is the bare assembleRelease; the -Pgoogle project property (a Firebase variant) is not built for F-Droid.
• scanignore on the two build.gradle.kts files covers Firebase dependency/plugin references that are guarded by -Pgoogle and are absent from the FOSS APK (confirmed byte-for-byte by the reproducibility check).

fdroid build com.rousecontext:7 passes locally with reproducibility + signer verification; happy to help re-run CI whenever a maintainer can trigger it.