runtime verify fails in sandbox due to Chromium mach_port Permission denied, but passes with require_escalated

[axisrow]

Description

When running npm run verify, Chromium crashes in a macOS sandboxed environment. In sandbox, the browser fails with a Permission denied error in mach_port_rendezvous_mac.cc, and runtime verification is terminated before reaching the actual game checks.

Reproduction environment

Issue was reproduced in Codex App with in-app browser open at http://127.0.0.1:3000/.

Steps to reproduce

1. Run npm run verify in the pipeline.
2. Logs include Chromium/sandbox errors such as:
   • CRITICAL:gpu/ipc/service: Failed to reserve sync point: mach_port_insert_right ... Permission denied 1100
   • then: Target page, context or browser has been closed
3. Rerun with require_escalated — verification proceeds into a real game session and passes.

Expected behavior

npm run verify should run reproducibly under a normal invocation without requiring manual require_escalated.

Actual behavior

• In sandbox, runtime verification fails at the browser layer.
• With elevated runtime, verification reaches gameplay and passes.

Additional context

This appears to be an environment/sandbox-related Chromium permission issue on macOS rather than a gameplay code regression.