[A-EDev]

Summary

The CI size budget measured the wrong APK. IzzyOnDroid ships the FOSS arm64-v8a APK and applies its 30 MB cap to that one, not to the universal APK. For reference, stable v3.0.0's arm64-v8a APK was 19.8 MB. After the linked-devices stack, the universal FOSS APK is over the old check, and #1559's "Build APK" failed on that step.

• The budget check now measures app-foss-arm64-v8a-release*.apk, with the same 29,500,000 byte budget. Its comment and error message name that APK.
• The comment on the upload steps now says the universal APKs are the README's download for any device, and IzzyOnDroid ships the FOSS arm64-v8a APK.
• The step summary still lists every APK, including the universal one.

Current sizes on origin/main (5253022), from ./gradlew :app:assembleFossRelease run locally offline. These are unsigned; CI's signed APKs are slightly larger.

APK	Bytes
FOSS arm64-v8a (now checked)	21,586,832
FOSS armeabi-v7a	20,569,598
FOSS x86	21,618,486
FOSS x86_64	21,832,593
FOSS universal	29,747,335

That leaves arm64-v8a about 7.9 MB under the budget.

Related issue

None.

Change type

• Bug fix
• Feature
• Refactor or maintenance
• Build, packaging, or CI
• Documentation

Validation

• ./gradlew :app:assembleFossRelease: ok, sizes above
• ./gradlew :app:assembleGithubDebug: ok
• ./gradlew :app:testGithubDebugUnitTest: 4651 passed, 46 skipped, 0 failed (no code changed)
• ./gradlew ktlintCheck: ok
• ruby -ryaml -e 'YAML.load_file(".github/workflows/build.yml")': parses
• The workflow step itself runs only in CI; this PR's own "Build APK" run exercises it.

Test device and Android version: none

Risk and compatibility

• The universal FOSS APK is no longer held to a budget. It is still listed in the step summary.

• The change does not introduce secrets, private data, or unexpected telemetry.

• New user-facing text uses Android string resources. (None.)

• Dependency and lockfile changes are intentional and limited to this PR. (None.)

• Room schema changes include the required version bump and migration, or this PR does not change the Room schema. (No schema change.)

• Breaking changes and upgrade steps are clearly documented. (None.)