[baba-dev]

Scope

Follow-up to merged #350; implement only the three requested audit corrections.

A — Native printer launch (P1)

• Replace navigation to an Android intent:// URL after an awaited fetch with a two-step flow: prepare the existing short-lived signed receipt grant, then show an actual user-tapped Open printer anchor link.
• The launch link is built with the existing package-restricted intent helper and per-sale URL, and expiry is rechecked synchronously on click. If expired, prevent navigation and ask the user to prepare again.
• Keep BLE and Print/PDF fallbacks; no changes to receipt authorization, signing, token format, or printer transports.
• Extend native-print client tests for successful and malformed/expired grants.

B — Android manifest metadata (P2)

• Correct an audit false-positive: GoogleChrome/android-browser-helper LauncherActivityMetadata actually looks for androix.browser.trusted.NAVIGATION_BAR_DIVIDER_COLOR*. Renaming to androidx would break styling.
• Preserve the upstream-compatible value, explain it in the manifest and lock the exact strings with a regression test.
• Upstream reference: https://github.com/GoogleChrome/android-browser-helper/blob/main/androidbrowserhelper/src/main/java/com/google/androidbrowserhelper/trusted/LauncherActivityMetadata.java

C — QR Studio test flake (P2)

• Root cause: Playwright getByLabel matched two QR inventory at a glance sections while App Router retained an inactive route tree.
• Scope to #workspace-main [data-testid="tabletop-press"]:visible; require exactly one visible studio, then query the accessible region by name. Real duplicate visible UI still fails.
• Preserve all existing QR Studio visual, functional, responsive and print-format assertions.

Verification

• CI required: lint/typecheck, unit/integration/browser suites, Android build and source contract tests.
• Manual Play-installed Android print handoff is still needed to confirm Chrome/device behaviour; these changes avoid assuming a browser grants activation after a network await.
• No DB migrations, entitlement/billing changes, additional permissions, or Play production publication.

Do not merge before all mandatory checks pass.