Records the engine run before 0.6.0

[johnnyt]

What

The engine proof, re-run on the source that carries every change made for 0.6.0 except the release prep, and its dated result written into both READMEs.

scripts/hermes-conformance.mjs ran on 2026-10-04 at 9a2fb80 (main at dispatch), on the standalone VM at Hermes release 0.12.0, HBC bytecode version 89, with the server runtime at Node v24.21.0. The corpus was tier 9, 262 cases. It printed:

Report	Server runtime	The VM	Differences
evaluator	257 rows	257 rows	0
compiler	215 rows	215 rows	0
location	112 rows	112 rows	0
statement	64 rows	64 rows	0

and "every report agrees, row for row", exit 0. No difference was found, so none is recorded.

Changes

• README.md: a new dated paragraph after the c901cc0 run, naming the commit, the two source changes since that run (the fraction expander's bound computed from the unit table, the exported name for evaluateTagged's result type), the engine release and bytecode version, the four reports' row counts, and what the run covers. The earlier runs stay as they are.
• conformance/README.md: a dated subsection under the second evidence path with the same result as a table, pointing at the README's history of earlier runs.

No changelog fragment: documentation only, which changelog.d/README.md excludes.

Gate

mise exec -- pnpm run gate green on the staged tree, read whole: typecheck, lint, neutrality, 43 test files with 4113 tests passed, coverage, corpus check, record cites, build, identity, resolution. README.md and conformance/ are gated paths, so the gate ran.

Verification against the acceptance

• Run at a head carrying every campaign change except the release prep: 9a2fb80, main at dispatch; the only other open bead for this release is the prep.
• Zero differences on every suite: the four lines above, exit 0.
• Both READMEs carry the dated result with the engine release and bytecode version: the two sections above.
• Every commit the new text cites (9a2fb80, c901cc0) is an ancestor of main.