Problem
Current main fails zig build benchmark-comparison-test:
V26 exact-parent integration changed without a matrix version bump:
tools/exact-parent-regression.tsV26 froze tools/exact-parent-regression.ts at SHA-256 bb464660074fac79c82360306318efd9cd88c9828bf1face21847becdeec8ead. Commit 053ac8ad (#461) later added schema-v2 direct-binary validation, producing current SHA-256 27c35a0a23a74cc33efbe5284396af349e4bdb6419f9aaaf65d380952c1890bb, but did not publish a successor representative matrix.
The fail-closed gate is correct. The matrix inventory is stale.
Scope
Publish V27 as an evidence-integration-only child of V26. It must repin the exact-parent tool and document the schema-v2 direct-binary versus schema-v3 shared-overlay provenance distinction while inheriting all workloads, jobs, checksums, modes, scored operations, thresholds, and publication rulings unchanged.
This must not be fixed by:
- editing the frozen V26 file;
- accepting the current digest without a new matrix version;
- weakening or bypassing
validatePinnedFile; - changing benchmark workloads, checksums, jobs, lanes, or scoring;
- silently changing historical artifacts or reports.
Acceptance criteria
representative-benchmark-matrix-v27.jsonhash-inherits V26 and repins only evidence-integration metadata required by #461.- The matrix loader defaults to V27, supports schema 27 explicitly, and preserves fail-closed parent/integration validation.
- Matrix self-tests reject source drift and unsupported future versions while accepting the exact V27 tree.
docs/benchmarks.mddescribes V27 accurately and the owned bunpress output manifest is regenerated.zig build benchmark-comparison-testpasses in full on current main.- The change flips 0 Test262 cases.
Relationship
Found while validating the benchmark-first #772 row. This repair is intentionally separate so #772 can land only after the repository benchmark gate is healthy again.