fix(eval): swallow microsandbox 'egress frame too large' so the eval doesn't die mid-run

[nickwinder]

Why

microsandbox's egressIntercept() runs its event-pump loop as a fire-and-forget async IIFE with try/finally — no catch. When the native binding throws "egress frame too large" (protocol parser hit a frame above its internal buffer), the rejection escapes as unhandledRejection and crashes the parent node process, taking out the whole eval. We've reproduced this consistently mid-suite — early test cases finish, then a later test's executor sandbox triggers the bug and the eval dies before any judging happens.

Summary

• Install a process-level unhandledRejection handler at the CLI entry point that only catches errors with code === 'GenericFailure' AND message matching /egress frame too large/. Re-throw everything else so genuine unhandled rejections still crash loudly.
• Egress logging for the affected test case stops (it's observability, not correctness — the eval can still execute, snapshot, and judge).
• After this fix the same suite that previously died mid-run completes and all test cases produce judge results.

Single-file change to src/index.ts (+18 lines, no test changes — the bug originates in the native binding, hard to reproduce deterministically in unit tests).

[nickwinder]

not required after fixing up claude oauth sessions