TEST-001A3 — Stabilize the untrusted Error recapture assertion across Node 20 platforms #187

Outcome

Repair one test-only portability defect that blocks a clean macOS Node 20 verification while the same exact main commit passes hosted Linux Node 20.

Exact claim

CLAIMED by /root at 2026-07-13T22:19:02Z on codex/issue-187-request-validation-stack-test, based on exact main 5c7d2d160237465b367c4dcc799cefcfab1e4e9b.

Owned path only:

• functions/requestValidation.test.js

Excluded: functions/requestValidation.js, all runtime, package/lockfiles, CI/deploy workflows, Rules, frontend, docs, providers, and production.

Reproduction and corrected invariant

On exact main with Node 20.20.2 on macOS, the test expects Reflect.set(fabricated, 'stack', canary) to return false. Inside Jest's VM, V8 returns true and the special lazy Error stack accepts the value even though Object.isFrozen(fabricated) is true. The exact same commit passed hosted Linux run 29288647739 with 990 Functions tests.

The caller-constructed error is deliberately untrusted. Production parseBoundedArray does not recognize it in the private safe-error WeakSet, does not reuse it, and emits a fresh fixed validation error. That recapture, fixed reason/message, empty serialization, distinct identity, and canary-free stack are the portable security properties. This test-only correction must not pretend the untrusted input itself is immutable on every V8 host.

Acceptance

• Do not change production source.
• Preserve the class freeze assertion and fixed message mutation assertion.
• Attempt the hostile stack mutation without relying on an engine-specific return value or untrusted-input state.
• Prove the parser returns a distinct, fresh fixed error with the expected safe reason/message, empty serialization, and no hostile canary in its stack.
• Run the focused test and complete Functions suite on macOS Node 20.20.2.
• Pass exact hosted Linux Functions CI.
• Record that no website, Firebase, Stripe, provider, or production behavior changed.

Officer impact: None — test portability only.

Officer documentation: None — no officer task or public behavior changes.

Deployment evidence: Test/merge evidence only; no deployment or provider action.