{"content":"Development journal for agent-browser-core: committed 1a0dd8a on branch codex/owner-chip-metafile-homepage with message `fix: preserve custom Bot homepage owner`.\n\nChange: custom Bot homepage aliases now keep the source Bot homepage owner identity when a metaid:// URI renders a custom metaapp:// or metafile:// target. The resolver still renders the target resource and preserves the visible metaid:// URI, but the top-level owner used by the Browser owner chip and owner panel now comes from the Bot homepage profile, including Global MetaID, display name, avatar, online state, and verification state.\n\nWhy: for bots whose homepage points at metafile content, the owner chip could lose the Bot profile and show an unknown or target-resource owner instead. That made the chip and click-opened owner panel miss the expected avatar and name.\n\nTests: added regression coverage in tests/browser/browserResolver.test.mjs for custom metaapp and custom metafile homepage aliases. Verified red first: the new assertions failed with metaapp-publisher/unknown owners. Then updated packages/core/src/browser/browserResolver.ts and verified green with `npm run build && node --test tests/browser/browserResolver.test.mjs` and full `npm test` passing 324/324. Also checked the live repro URI metaid://idq1q00mqzr58z99a43u008ntscdyfcl53mxhhpefc against the fresh build; it resolves to owner kind bot, name `Bot 1`, with an avatar URL while still rendering the custom metafile homepage.","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}