Bake corpus: genuine frozen locks and retained full-suite evidence

Parent #66. Implementation and retained evidence: see the completion checkpoint below.

Completed the native Bake corpus checkpoint in ccecdcf9b, with 1,185 Git-verified evidence artifacts.

• All 24 unchanged pinned Bake files: 177 passing cases, zero failures, zero skips, two original upstream TODOs. Native Home and the independent validator exit zero; source membership, exact identities, terminal counters and complete streams validate.
• Genuine base/React native locks replace the empty cache placeholder. Home's frozen installs preserve both lockfiles byte-for-byte; a manifest mismatch is rejected without changing its lock.
• The suite's outer capture budget derives from its 24 distinct sources. Original assertions, fixtures, workloads and per-test deadlines remain unchanged.
• Native test dispatch retains a spawned fixture's requested working directory; the unchanged deinitialization child passes nine tests.
• Production source providers retrieve actual stored map JSON, restoring original React source lines in errors. The expanded production control verifies the original line and file location; this follows the behavior tracked in #563.
• --changed dependency graphs compare canonical file identities, handling Git/caller path aliases without changing execution/report paths. The full coordinator controls, including an explicit symlink case, pass with 29 complete journals. Development/HMR and production controls pass.
• Fresh 157-file regression: 396 passing cases, 142 passing process checks, zero failures. Its 37 case skips and three file skips retain zero pass credit. Validator, ABI, lint, formatting and the 12,996-entry corpus integrity checks pass.

The initial full run's 175 pass / 2 fail / 2 TODO and intermediate control failures remain in the evidence history. Committed raw Git blobs were independently decompressed and hash-checked against the manifest, including exact committed implementation hashes.

This completes #902's native runner/execution tranche. #901 retains optimized native execution and platform gates; #564 retains the Linux Bake TODO coverage. The two upstream TODOs, all-platform verification and the full #66 Bun feature/test-suite objective remain open.

The first retained complete 24-file run finished with 175 pass, 2 fail, 2 TODO. Its journal, JUnit, exact case metadata and source inventory validate without evidence-format errors; the two failures are actual runtime failures, so this is not a passing suite checkpoint.

The failures expose two implementation gaps being repaired together:

• deinitialization.test.ts: native test dispatch changes a spawned fixture's working directory from its requested fixture directory to the corpus project root. The unchanged child asserts its actual working directory before exercising server deinitialization.
• dev/production.test.ts: the ported production source provider obtains Bake's per-thread state but never retrieves its stored source map. The unchanged React error assertion receives generated minified source instead of its original throw new Error line. This concerns the source-map behavior previously tracked in #563.

Both repairs have targeted regression controls. The rebuild and a fresh complete suite run remain pending. The original failed run is retained, and the two upstream TODOs remain separate from executed-case pass credit.