The existing import_graph and reexport_graph benchmark rows do not currently establish equivalent semantic work. Found while auditing cross-file declaration ownership for #480; tracker #416.
In temporary copies of the unchanged generated corpora, append these statements to src/index.ts:
// import_graph: result is Model127<string>
export const bad: number = result.current;
result.missing;
// reexport_graph: value0 is Item0<number>
export const bad: string = value0.value;
value0.missing;TS 6.0.3 and native TS 7.0.2 each report exactly TS2322 and TS2339 in each project. Home accepts both without diagnostics. The positive projects passing is insufficient admission evidence.
Required work:
- Preserve real generic exported interfaces and function return types across module imports and barrel re-exports, including missing-member rejection and assignment checks. Do not hardcode benchmark names/shapes.
- Add untimed negative controls to both existing workloads. Keep the corpora unchanged and make the full run stop before any measurement/results creation if any selected workload fails admission.
- Mark the historical graph rows ineligible as fair speed claims, retaining the raw measurements; qualify the previous all-18 leadership statement.
- Re-admit and retime only after both baselines and Home accept the original projects and reject the same invalid controls. Audit the other workloads' semantic coverage as well.
Evidence: bench/vs_tsgo/results/global-audit.TExK7j/graphs.log, tested with the frozen home-config binary (global declaration precedence and config-directory fixes, before type/value-namespace follow-up). This is distinct from global script declaration linkage in #480 but shares the missing cross-file typed environment.