TanStack's global catch boundary turned a crash into an error UI, so negative assertions could pass against a broken tree. Disable it and cover it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Julius Marminge committed on 10/20/2026, 7:28:16 AMparent273bef5
Checks
- SuccessfulCodeRabbitGitHub
Review completed
- FailedCheckGitHub
- Skipped
- SuccessfulTestGitHub
- SuccessfulBuild and TypecheckGitHub
- SuccessfulRelease SmokeGitHub
- SuccessfulTest WebGitHub
- SuccessfulRustGitHub
- Skipped
- SuccessfulLabel PR sizeGitHub
- SuccessfulLabel PR 22187GitHub
- Successful
- Skipped
- SuccessfulPOST to CursorGitHub
- SkippedEAS PreviewGitHub
- SuccessfulPrepare PR size configGitHub
- SuccessfulCollect PR targetsGitHub
- SuccessfulTest Server 3GitHub
- SuccessfulTest Server 2GitHub
- SuccessfulTest Server 1GitHub
- SuccessfulTest Server 8GitHub
- SuccessfulTest Server 7GitHub
- SuccessfulTest Server 5GitHub
- SuccessfulTest Server 6GitHub
- SuccessfulChangesGitHub
- SuccessfulTest Server 4GitHub
- FailedLintGitHub
- SuccessfulNative fingerprint diffGitHub
2 files changedLine totals unavailable