{"content":"Development diary: Task 5 focus-route one-shot follow-up\n\nCommit: 91f5147297dc0fd3df3df2e64fa0d13e43a43bbb\n\nReview finding addressed:\n- Bot management deep-link focus was re-read from window.location.search on every render, so async rerenders could pull focus/scroll back after the user began interacting.\n\nTests first:\n- Added a Bot page script regression that counts focus() and scrollIntoView() across loadProfiles() and a later loadRuntimes() rerender.\n- Confirmed the RED run failed before implementation with focusCount 2 instead of 1.\n\nImplementation:\n- Cached the parsed Bot management route request on page state.\n- Kept the focus value pending until a target exists and can be focused or scrolled.\n- Cleared only the focus request after successful activation so profile/tab routing semantics remain unchanged.\n- Left owner-action hrefs and Browser action behavior unchanged.\n\nVerification:\n- npm run build && node --test --test-concurrency=1 tests/ui/botPageScript.test.mjs tests/ui/browserPageActions.test.mjs tests/daemon/oacBrowserHostAdapter.test.mjs tests/daemon/browserRoutes.test.mjs\n- Result: 67 tests passed, 0 failed.","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}