Messages ingress alternate-main success-control times out in changed-mode suite #7418

Client or integration

Claude Code

Area

Proxy and routing

Summary

The success-control case for pool-to-native-main cancellation through messages ingress timed out at the default 5-second limit in the final-head changed-mode run for #7414. This is an existing unchanged regression file. A focused follow-up is being recorded separately; no timeout has been raised and no assertion has been removed in #7414.

Reproduction

Run OCX_TEST_RUNNER_BUN=<Bun 1.4.3> bun run test:changed at e2ab0d7. It selected 1,565 files / 35,300 cases and completed in 415.6 seconds with 35,252 pass / 43 skip / 5 fail. Four failures are tracked in #7417; the fifth is this case.

Version

e2ab0d7

Operating system

macOS arm64

Logs or error output

tests/responses/responses-alternate-main-cancellation.test.ts: pool to native main cancellation through messages ingress > success-control timed out after 5017ms (limit 5000ms).

Screenshots and supporting files

#7414
All 565 focused account-collision/auth/routing tests passed separately. The timeout is not described as a proven baseline bug; load sensitivity remains under investigation.

Checks

• I searched existing issues and documentation.
• I removed secrets, tokens, account details, request credentials, and personal data.

Focused follow-up at the same final head: bun test tests/responses/responses-alternate-main-cancellation.test.ts with Bun 1.4.3 passed 6/6 in 1.50s; the timed-out success-control took 311ms. No code, timeout or test assertion was changed. This supports a suite/load-sensitive failure, not a proven deterministic product regression.