{"content":"Development diary: 3d17967 fix: serve buzz metaapp from bundled install\n\nThis round fixed the Buzz localUiUrl returned after posting a Buzz. The URL shape was correct, but remote-installed skillpack runtimes could not resolve /ui/buzz/app/index.html and returned a JSON not_found envelope.\n\nRoot cause:\n- The daemon MetaApp route supported /ui/buzz/app/index.html, and the source tree had the Buzz MetaApp assets.\n- The bundled skillpack runtime route only checked copied runtime assets and the normal development dist-to-src fallback.\n- In the GitHub archive install layout, the runtime lives under skillpacks//runtime/dist while the MetaApp source is at the repository root src/ui/metaapps, so the fallback missed it.\n\nChanges:\n- Updated src/daemon/routes/uiMetaApps.ts to resolve MetaApp roots across copied runtime assets, development builds, and GitHub archive skillpack layout.\n- Rebuilt the shared/codex/claude-code/openclaw runtime route artifacts.\n- Added a regression test that imports the tracked bundled route and verifies /ui/buzz/app/index.html is served as HTML through the repository-source fallback.\n- Avoided bundling duplicate large MetaApp vendor files into each skillpack runtime.\n\nVerification:\n- npm run build\n- npm run build:skillpacks\n- node --test tests/skillpacks/buildSkillpacks.test.mjs: 21 passing\n- node --test tests/daemon/httpServer.test.mjs: 32 passing\n- node --test tests/cli/runtime.test.mjs: 57 passing\n- git diff --check\n- Reloaded the reported local Buzz URL in the in-app browser; it now renders the Buzz MetaApp with the posted pin banner instead of the JSON not_found response.","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}