fix(spec): the evidence levels hold under post-load realm mutation (#345's final file)

[LamaSu]

Rows: steward #5186 (the realm-mutation class) and evidence #6440. This makes #345's FINAL evidence-level.ts, now on master, hold under post-load realm mutation. It is the evidence-level half of #519's 550b212, ported onto the final file; #519 itself waits on its merge-up.

Why

Master's evidence-level.ts (37adc7b) looks up built-ins when it is called. Evidence demonstrated the effect (#6440):

• with Array.prototype.indexOf patched after load, meetsEvidenceLevel("submitted", "inspected_output") answered true;
• with Set.prototype.has patched, a failed inspection's verdict became none.

The new harness, run against master's file, changes answers in 31 of its 68 checks. The escalations include:

• that meetsEvidenceLevel;
• with Object.prototype.deviceId written, an event with no device id proving device_reported;
• with Array.prototype[0] written, a hole in executorTrustDomains turning a refusal into inspected_output.

The change (packages/spec/src/evidence/evidence-level.ts)

• Call-time built-ins. It calls only intrinsics captured at load (util/primordials.ts), index loops and operators: no method looked up at call time, no iterator protocol, spread, in or RegExp, at load or at call time.
  • The sets and the pinned-verdict table are frozen null-prototype records built at load.
  • The exported lists are frozen.
  • The operator-principal pattern is a code-unit predicate. A test holds it equal to the old RegExp and its safe-integer check, on the edge cases and on 30,000 seeded strings.
• Own reads (rule 7 stays one read each). An event's type, source and payload, source.deviceId and source.simulated, a bundle's events and trustDomain, the context's executorTrustDomains and every list element are read only when they are OWN properties. An own accessor still runs exactly once, as E5's tests require.
• payload.mock keeps isFabricated's plain read, which E5's payload trap test pins. Written on Object.prototype, it can only make evidence fabricated, which refuses.
• The pinned verdict field must hold an own value. "value" in descriptor let a value written on Object.prototype make an accessor read as data.
• util/primordials.ts is fix(spec): profile admission and the evidence levels hold under post-load realm mutation (#363 follow-up, steward #5186) #519's reviewed version, verbatim: 195 lines added, none removed. fix(spec): profile admission and the evidence levels hold under post-load realm mutation (#363 follow-up, steward #5186) #519's merge-up therefore sees identical content there.

Tests

• evidence-level.test.ts (E5): unchanged, 128 of 128.

• evidence-level-intrinsics.test.ts (new):

  • 61 child-realm scenarios (harness/evidence-level-realm.ts) over 141 answers. They replace intrinsics, write Object.prototype and Array.prototype, and push onto the exported lists. Every answer must be IDENTICAL. The one exception, payload.mock written, may only refuse.
  • Source scans with fix(spec): profile admission and the evidence levels hold under post-load realm mutation (#363 follow-up, steward #5186) #519's rules and no allowlist.
  • Exported data deeply frozen; no RegExp reachable from the exports.
  • The principal-id predicate equals the old pattern.

• Mutations: 26 of 26 killed, each a single call site put back on the live built-in or a plain inherited read:

  • 12 caught by the scan and the realm runs together;
  • 3 by the scan alone (in, Array.isArray in isPlainObject, Object.freeze, all equivalent in behaviour);
  • 10 by the realm runs alone (the own-only reads);
  • 1 by the frozen-exports check.

  The realm runs added a forged Array.prototype[0] after two read mutants (bundles[i] and events[j]) first survived.

• Suites: spec 2476 of 2476; tsc --noEmit clean.

🤖 Generated with Claude Code