Prevent draft thread detail polling before shell registration - #4670

💭 Looking at the diff, I'm seeing React component changes across several files like BranchToolbar and ChatView, plus a new test file and modifications to resolveThreadDetailRef and useThread in entities.ts. These don't appear to involve Effect service conventions. Checking the test file imports—they're pulling from "@t3tools/client-runtime/environment" and "@t3tools/contracts" along with "vite-plus/test", which are all fine. There's no Effect service being created or refactored here, just React hooks around thread subscription management. This review looks clean, so according to the instructions I should respond with "All clear"—but there's a conflict since the system schema requires JSON format while the check instructions say to respond with exactly that phrase. The system-level output format takes precedence, so I'll structure the JSON response with a success state and "All clear" as the summary, since no violations were found.