{"content":"Agent Browser Core development journal: added host-neutral metafile:// resource support.\n\nImplemented a new core metafile resolver that accepts metafile://{pinId} and metafile://{pinId}.{ext}, strips the compatibility extension for canonical lookup/content URLs, fetches ManAPI pin metadata, and uses contentSummary.dataType first for /file/index records before falling back to contentTypeDetect/contentType/path/input extension.\n\nRenderer mapping now sends HTML to the existing sandboxed iframe policy, PDF to the PDF iframe renderer, image/* to the image renderer, video/* to the video renderer, and unsupported files such as ZIP to an unsupported renderer with a safe download link.\n\nUpdated standalone and UI wiring so /browser/metafile/{pinId} deep links boot the Browser shell, the client resolves metafile paths, and unsupported resources expose a sanitized download link.\n\nVerification: npm run verify passed with 141 tests. git diff --check passed. Live standalone smoke against the provided pins resolved f038f3...c98i0 and f038f3...c98i0.pdf to renderer=pdf/contentType=application/pdf/title=MetaWeb_Whitepaper.pdf, and 3b94a3...1b0i0 to renderer=video/contentType=video/mp4/title=rocket_launch.mp4. Browser DOM smoke confirmed .browser-pdf iframe and .browser-video controls elements render with the Metafile Content Base URL.","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}