release: CX-Codex 2.7.5 Android stability

[Qjzn]

Summary

• fix duplicate Android user bubbles after foreground/history reconciliation
• recover stalled, reclaimed, or crashed Android WebView renderers with evidence-driven retries
• keep the default renderer priority and distinguish low-memory recovery from crash-loop recovery
• include community fixes for hidden Windows App Server consoles and fork-aware bootstrap CI
• publish version 2.7.5 release notes and validation contract

Community feedback

Includes the reviewed changes from #46 and #47 with the original contributor authorship preserved.

Dependency PRs #49, #50, and #51 are intentionally excluded from this stability release because they affect Android PDF rendering, Markdown rendering, or the native SQLite runtime and need dedicated regression evidence.

Issue #28 remains open: foreground/WebView recovery does not substitute for physical-device FCM deep Doze acceptance.

Verification

• npm.cmd run verify:release -- -AllowDirty -SchemaAudit warn (155.2s)
• npm.cmd run test:7420:frontend -- -BaseUrl http://127.0.0.1:17420 against an exact source-matched isolated server (36 surfaces, 476.9s)
• Android focused unit tests, lintDebug, and assembleRelease (127.7s)
• local ZIP/APK packaging plus checksum verification (84.9s)
• clean-worktree npm.cmd run verify:release -- -RequireCleanGit -SchemaAudit skip (84.8s)
• npm 10.9.3 production audit: 131 dependencies, 0 vulnerabilities
• APK package com.cxcodex.bridge, version 2.7.5 / code 20705
• APK SHA-256 9a3f9729bdd2012f98aac938cb02b2ab6b95399010d0794da20efa064e5ef5a7
• APK signing certificate matches public v2.7.4

Remaining release gates

After merge and tag: wait for main/tag Actions, verify every public asset/checksum/signature, and run the public latest Windows -NoStart install smoke. Physical Android process-death and deep Doze evidence remains outstanding.

[Qjzn]

Release decision note: the windows-bootstrap-smoke job passed all steps, including locked in-place upgrade and official uninstall cleanup. The GitHub-hosted Ubuntu build job was retried once; both attempts were cancelled after 15 minutes with runner_id=0, steps=[], and no runner assigned, so this is recorded as an infrastructure cancellation, not a passing check or a code failure.

Equivalent local release gates passed on the exact head commit, including clean-worktree governance/build/normalizer/server/package checks; the full 36-surface frontend regression, Android focused tests/lint/release build, signed APK verification, and production dependency audit also passed. Proceeding with the release while preserving this exception in the PR history.