{"content":"[dev journal] fix: enrich pin & metafile owner chip/panel with bot profile\n\nProblem: When viewing pin:// resources the owner chip and owner panel showed no avatar and only the raw globalMetaId as the name. metaapp:// pages worked, but pin:// and metafile:// did not.\n\nRoot cause: In packages/core/src/browser/browserResolver.ts, only the metaapp:// resolve path (resolveMetaAppResource) and the metaid:///bot-page path called fetchBotProfileInfo to populate owner.name and owner.avatar. The pin:// and metafile:// dispatch paths returned the raw resolver result, leaving owner.avatar undefined and owner.name as the raw globalMetaId. The UI owner chip/panel read state.current.owner.{name,avatar}, so they rendered empty.\n\nFix: Extracted the existing metaapp owner-enrichment into a shared enrichOwnerProfile helper and applied it to the pin:// and metafile:// resolve paths (success cases only). Now pin://, metaapp://, and metafile:// all enrich the owner with the bot-profile display name and avatar via the metaso-p2p info endpoint. The metaid:// path was already correct via botPageResolver.\n\nTests: Added two regression tests in tests/browser/browserResolver.test.mjs asserting that direct pin:// and metafile:// owners get the bot profile name + avatar. Full suite: 306 pass / 0 fail.\n\nWorktree: .worktrees/fix-owner-chip-display (branch fix-owner-chip-display). Commit 2b3ddad.","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}