test: add arch stories verification tests

[bbopen]

Summary

Adds comprehensive tests verifying that BoundedContext addresses the acceptance criteria from architecture issues:

• arch: Unified numeric validation layer for NaN/Infinity handling #141: Unified numeric validation layer
• arch: Shared BridgeLifecycle mixin for init/dispose state management #142: Shared BridgeLifecycle mixin
• arch: Standardized error classification across all bridges #143: Standardized error classification

All 35 verification tests pass.

Issues Verified as Addressed

Via #141 (Numeric Validation)

• OptimizedNodeBridge should guard against negative/NaN timeoutMs #114 - Guard against negative/NaN timeoutMs
• Python bridge should disallow NaN/Infinity in JSON responses #95 - Disallow NaN/Infinity in responses
• Reject NaN/Infinity in JS arguments to avoid silent conversion #93 - Reject NaN/Infinity in JS arguments
• Bridge timeoutMs should be validated to avoid NaN/negative timeouts #87 - Validate timeoutMs

Via #142 (Lifecycle Management)

• fix: Track initialization state more robustly in NodeBridge.init() #137 - Robust initialization state tracking
• PyodideBridge should clear initPromise on init failure to allow retry #116 - Clear initPromise on init failure to allow retry
• OptimizedNodeBridge should block late worker spawns after dispose #102 - Block late spawns after dispose
• PyodideBridge dispose should reset initPromise to allow re-init #69 - Dispose resets state properly
• NodeBridge dispose should cancel in-flight init to avoid orphaned processes #63 - Dispose cancels in-flight init
• Pyodide bridge should allow retry after init or package load failures #57 - Allow retry after init failures

Via #143 (Error Classification)

• HttpBridge should classify timeouts and protocol errors with Bridge* errors #118 - Classify timeouts as BridgeTimeoutError
• HttpBridge should handle JSON.stringify failures with BridgeProtocolError #120 - Protocol errors classified correctly
• Map Python ProtocolError responses to BridgeProtocolError #94 - Python ProtocolError maps to BridgeProtocolError
• HTTP runtime should handle error payloads, timeouts, and invalid JSON explicitly #56 - HTTP handles errors explicitly

Test plan

• All 35 new tests pass
• Full test suite passes

🤖 Generated with Claude Code

[coderabbitai]

Warning

Rate limit exceeded

@bbopen has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 1 minutes and 17 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between a4f6c0a and 78d0174.

📒 Files selected for processing (1)

• test/arch-stories.test.ts

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 78d0174a1d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".