TWA shows "Running in Chrome" despite matching assetlinks.json and asset_statements in APK

**Describe the bug**
My TWA app never opens in standalone/full-screen mode — Chrome always shows "Running in Chrome" with visible browser UI, even though I've verified every piece of the Digital Asset Links chain matches.

**What I've verified:**
1. SHA256 fingerprint matches exactly between keystore, twa-manifest.json, and live assetlinks.json
2. Google's official Digital Asset Links validator confirms SUCCESS
3. Decompiled the built APK's AndroidManifest.xml — the embedded asset_statements string exactly matches the live assetlinks.json, including both handle_all_urls and use_as_origin relations
4. assetlinks.json is served correctly at https://food-at-door.vercel.app/.well-known/assetlinks.json
5. Tried: uninstall + clear Chrome cache/data + reinstall, full phone restart, completely fresh Bubblewrap build from scratch

**Result:** Still shows "Running in Chrome" banner every time, app never enters standalone mode.

**Environment:**
- Android device: realme P1 Pro 5G, realme UI 7.0
- Site: https://food-at-door.vercel.app
- Package: app.vercel.food_at_door.twa

**To Reproduce**
1. Install signed TWA APK on device
2. Open the app
3. See "Running in Chrome" banner, full browser UI visible

**Expected behavior**
App should launch in standalone full-screen mode with no browser UI, matching the verified Digital Asset Links configuration.
You

Start by reproducing the behavior with the signed APK on the realme P1 Pro 5G, then inspect the referenced twa-manifest.json, embedded AndroidManifest.xml asset_statements, and live .well-known/assetlinks.json. Compare the installed app and Chrome behavior with the verified Digital Asset Links values; done means the TWA opens without the “Running in Chrome” banner or browser UI.

Written by the indexing model from the issue text.