voice (m4): FCM client entry for the dev application id — unblocks all phone validation (FR-M4) (#188)

[thedancingdeveloper]

Part of #188 — the remaining external gate for mobile voice delivery.

Current state

The repository-side identity and configuration work is complete:

• Production builds use com.sprooty.vogt; the CI dev lane uses com.sprooty.vogt.dev.
• Firebase project metadata contains Android clients for both renamed package IDs.
• Real google-services.json is operator/CI supplied and git-ignored; the repository carries only a sanitized example.
• CI validates the expected package before Gradle consumes the out-of-tree Firebase config.
• Fresh live-configured prod and dev APKs build and install side by side with distinct package IDs.

What remains is the acceptance test, not another repository implementation: register both installations with FCM and verify that a push sent through each environment reaches only its matching app.

Remaining work

1. Use the operator-supplied Firebase configs and reachable production/dev front doors.
2. Install com.sprooty.vogt and com.sprooty.vogt.dev together on a stable Android device or emulator.
3. Confirm both FCM tokens register with their matching Vogt instance.
4. Trigger one push per environment and record that routing is isolated to the intended installation.

Acceptance

• Dev and prod shells coexist on one device.
• Both register for FCM.
• Dev and prod pushes route to the correct installation.

The disposable Android 15 software AVD used for local validation repeatedly hit System UI ANRs before reliable token capture, so this issue remains open until stable device/emulator evidence is recorded.

[thedancingdeveloper]

Verified from the Firebase console (this session): the com.sprooty.mydevenv2.dev client is a real, registered app in project mydevenv2 (app id 1:1022775516765:android:5ef85b3f8375753fbe77b4), matching the repo google-services.json. So the config half is done and confirmed. The dev app already targets https://vogt-dev.sprooty.com. Remaining (you): install the dev APK alongside prod on one device and confirm both register for push + routing (add the dev SHA-1 to this app only if push registration errors). That closes this and unblocks #192.

[thedancingdeveloper]

Status reconciliation (2026-08-26): the dev Firebase client/config is implemented and deployed. Remaining scope is the explicit hardware coexistence test of the dev APK alongside the production APK and push-routing confirmation, so this remains open because it includes production coexistence.

[thedancingdeveloper]

Production verification (2026-08-26): prod is live from prod@028b3e3 and the v0.2.2 front door is healthy. The dev Firebase client/config implementation is present. This remains open only for the device test that installs dev alongside prod and verifies FCM registration/routing; no production code gap was found.

[thedancingdeveloper]

Status update after PR #432 (merged to dev as 20b7f53): the app-id/config handling and dev/prod delivery evidence are documented and covered by repository checks. The remaining gate is an actual dev and prod install side by side with FCM routing verified on hardware; this issue remains open until that evidence exists.

[thedancingdeveloper]

Read-only Firebase verification (2026-08-26): project mydevenv2 now has Android clients for com.sprooty.vogt and com.sprooty.vogt.dev, and each generated config contains both package entries. The remaining acceptance is still the real side-by-side APK install and correctly-routed FCM delivery on hardware.