{"content":"dev-journal: commit e7c64014a — fix: restore mobile Browser compatibility in native WebView\n\nBranch: fix/mobile-native-browser-compatibility\n\nRoot cause: Android Chromium 114 parses pin:// and metaapp:// with an empty hostname and a leading // pathname, while newer Chromium handles their authority correctly. ABC therefore rejected valid pin URIs with 'pin URI does not support a path component.'\n\nChanges:\n- Added a self-detecting legacy WebView URL compatibility layer for pin, metaapp, metafile, metaid, map, preview-file, and preview-metaapp URIs in the parent PWA, ABC iframe, and MetaApp documents. Modern browsers remain untouched.\n- Rebuilt mobile MetaApp resource handling around final module URLs and import maps, eliminating stale raw-JS references and supporting dependency order and cycles without guessing opaque signed-token URLs.\n- Added dynamic fetch/import/require and import.meta.url resource resolution, correct document-relative Markdown assets, inline data-URL code/text resources, bounded concurrent binary publishing, and longer resolve timeouts for large MetaApps.\n- Preserved the existing iframe sandbox, mixed-content setting, certificate checks, CSP, CORS, origin restrictions, and gateway allowlists.\n\nVerification:\n- Full mobile suite: 500/500 passed.\n- Shared Bot Browser suite: 244/244 passed.\n- Native shell suite: 21/21 passed; Android unit tests and production-debug APK build passed.\n- Production mobile PWA build, repository ESLint, Electron compile, and skills build passed.\n- Real-gateway MetaApp E2E passed on iPhone and Pixel fixtures.\n- Native Android WebView opened the reported pin with payload and transaction details.\n- The exact 20 MB Yellow Paper MetaApp rendered its first screen, chapter navigation, full dynamic Markdown chapter, and a 1536x1024 image; downloaded image bytes matched the original 1,093,948-byte PNG.\n\nNo production deployment or merge to main was performed.","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}