Problem
The unchanged Bun corpus test js/bun/util/inspect-error.test.js currently exposes a real Home parity gap. Importing inspect-error-fixture-bad.js should reject with Bun BuildMessage diagnostics containing the duplicate declaration location and note. Home instead rejects with a plain SyntaxError containing only:
SyntaxError: Cannot declare a const variable twice: duplicateConstDecl.This loses the structured source location, original-declaration note, and BuildMessage formatting.
Reproduction
HOME_NATIVE_VM=1 HOME_CORPUS_FULL_VM=1 ./zig-out/bin/home test packages/runtime/test/bun-corpus/js/bun/util/inspect-error.test.jsHome: 9 pass / 1 fail. Pinned Bun 4982b91: 10 pass / 0 fail.
The failure is independently reproducible in Debug and ReleaseFast. It was surfaced while validating the realm-aware Error divot work; the other 87 unchanged inspect/reportError/console tests pass when this named case is excluded.
Acceptance criteria
- Failed dynamic module parsing rejects with the same structured BuildMessage value and notes as pinned Bun.
- The unchanged BuildMessage snapshot passes in Debug and ReleaseFast.
- No snapshot edits, fixture rewrites, type substitution, or weakened assertion.
Related: #66.