Promote dev → staging (remove Android Auto from the shipping app)

[patrickrb]

Promotes PR #809 to staging so the internal-track build carries a manifest with
no Android Auto marker.

What's in this promotion

Three commits, all one work item — clearing the Play Auto rejection.

The rejection. Play rejected the update under "Auto App Quality Guidelines:
Visual info on phone — Your app does not disable features requiring phone
interaction while in driving mode." Both evidence screenshots were the same car
screen: the Auto idle state reading "Open FT8AF on your phone to start the FT8
engine" — the fallback QsoStatusScreen/RecentDecodesScreen render whenever
MainViewModel.peekInstance() is null, i.e. any Auto connect before the phone
app has been opened. The car told the driver to pick up their phone, with
nothing gating it on the car being stopped.

This is the second Auto rejection in two months (versionCode 1327 was rejected
in July under the NAVIGATION category), so #809 takes Play's other path rather
than answering findings again.

c95b4a05 — made the car UI compliant. Idle message is status only
(car_engine_idle, en + pt-BR); the one phone-reaching action is wrapped in
ParkedOnlyOnClickListener so the host only runs it when parked.

5177c3de — unwired Auto from the shipping app. Dropped the
com.google.android.gms.car.application descriptor, the
androidx.car.app.minCarApiLevel meta-data and the FT8AFCarAppService
service; deleted res/xml/automotive_app_desc.xml; flipped
CarAppManifestWiringTest into a guard asserting Auto is unwired, recording
both rejections so a third revival is deliberate.

The car/ package, its tests and the androidx.car.app:app dependency stay
in-tree — dead but compiling — as they did after the July removal, and now carry
the compliance fix so a revival starts clean.

Verification

• Full testDebugUnitTest on the branch: 3724 tests, 0 failures.
• processReleaseMainManifest: merged release manifest keeps only the car-app
  library's own entries (connection provider, permission activity, notification
  receiver) — no Auto descriptor, no CarAppService. Same state that shipped and
  passed review between PR Remove Android Auto support to clear Play production rejection #600 and the restore.
• Remove Android Auto from the shipping app (clears the driving-mode rejection) #809 CI: all gates green (android-gate, lint/detekt/ktlint, unit + instrumented
  tests, Build APK, codecov).

Follow-up outside the repo

Play Console → Advanced settings → Form factors still declares Android Auto.
Google requires Auto support removed from all active artifacts across tracks
before the Remove button works, so the order is: land this build on the
tracks that hold Auto artifacts (production via the manual workflow_dispatch
on the android-v* tag; replace/halt any open or closed testing builds), then
click Remove. Internal-track builds never trigger Auto review, but they do keep
the Remove button disabled.

🤖 Generated with Claude Code

https://claude.ai/code/session_01B4bi57TiMribneqcSBddRB

[codecov]

Codecov Report

❌ Patch coverage is 43.75000% with 9 lines in your changes missing coverage. Please review.
✅ Project coverage is 42.40%. Comparing base (fe346e4) to head (caadc95).
⚠️ Report is 16 commits behind head on staging.

Files with missing lines	Patch %	Lines
...n/kotlin/radio/ks3ckc/ft8af/car/QsoStatusScreen.kt	46.66%	8 Missing ⚠️
...tlin/radio/ks3ckc/ft8af/car/RecentDecodesScreen.kt	0.00%	1 Missing ⚠️

Additional details and impacted files

@@              Coverage Diff              @@
##             staging     #810      +/-   ##
=============================================
- Coverage      42.64%   42.40%   -0.24%     
- Complexity       226      228       +2     
=============================================
  Files            267      270       +3     
  Lines          32068    32450     +382     
  Branches        3664     3735      +71     
=============================================
+ Hits           13675    13761      +86     
- Misses         18132    18413     +281     
- Partials         261      276      +15     

Flag	Coverage Δ
android	17.21% <43.75%> (+0.13%)	⬆️
desktop	63.89% <ø> (-0.07%)	⬇️
ios	97.71% <ø> (ø)
native	9.93% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
...tlin/radio/ks3ckc/ft8af/car/RecentDecodesScreen.kt	0.00% <0.00%> (ø)
...n/kotlin/radio/ks3ckc/ft8af/car/QsoStatusScreen.kt	5.92% <46.66%> (+5.92%)	⬆️

... and 13 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.