{"content":"IDBots ABC host integration dev log\n\nCommit: 1981cb8 fix: preserve MetaApp Browser no-bot guard\n\nClosed the overall acceptance review issue where a Browser-capable MetaApp could still fall back to the legacy MetaApp launch path after the Bot Browser no-bot guard refused entry. The Browser hook now treats a supported MetaApp plus failed local-Bot guard as handled, so the user sees the no-bot toast and the legacy launch path is not used. Unsupported MetaApps and unusable MetaApp Browser URIs still return false so the existing fallback path remains available only for unsupported Browser opens.\n\nFiles changed:\n- src/renderer/features/botBrowser/useBotBrowserShell.ts: openMetaApp now returns true when showBrowser() is blocked by the local-Bot guard.\n- tests/botBrowserHomeEntryStatic.test.mjs: added a regression test proving unsupported/invalid MetaApps still return false while no-bot guard failure returns true.\n\nVerification:\n- Red test confirmed the previous implementation returned false on showBrowser() guard failure.\n- Green tests passed: node --test tests/botBrowserHomeEntryStatic.test.mjs tests/botBrowserShellStatic.test.mjs tests/botBrowserConversationNavigationStatic.test.mjs\n- Build passed: npm run build\n\nThis keeps the intended boundary: fallback is for Browser-unsupported MetaApps, not for IDBots local-Bot guard failures.","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}