ReviewOS

home-lang/home

Bake graph invariant and native JUnit identity verification

#901
Open chris opened this 8 days ago ·
8 days ago

Parent #66; follows completed native Bake ports #553/#555.

Native source d8c890b03 is on main through 1daa83a11. 945 verified raw artifacts retain source/executable identities, successes, failures and resource limits.

Completed host work:

  • The relaxed <=64-byte graph invariant is removed. The actual production type is compiler-enforced at 32 bytes without runtime safety; ReleaseFast frontend checking succeeds, and a 33-byte negative control produces the required compile error before restoring source exactly.
  • Debug measures 56 bytes with safety tags, and layout/alignment, 240 content/metadata combinations, source-map transfer/clone/deallocation tests pass. Debug safety checks remain active.
  • Filtered native roots link the actual entry-point promise callbacks. A dedicated graph target preserves the existing full-runtime and Bake integration targets.
  • Native JUnit emits legal XML display text plus reversible original identity attributes, retains raw journal identities, and escapes describe names once. Validation checks exact identity, canonical encoding, display transformation, case order/status/counters and source integrity. Thirty-four validator controls and the real 3-pass/1-skip/1-TODO XML/journal control pass.
  • Eight unchanged Bake files pass with 73 passing cases, zero failures and two upstream TODOs. Production/development/HMR controls pass. The fresh 157-file filesystem/FileHandle batch has 396 passing cases, 142 process checks, zero failures, 37 case skips and three skipped files; all validators pass. ABI 10 tests/58 assertions, Pickier and the 12,996-entry audit pass.

Remaining acceptance:

  • Actual optimized graph-test execution: LLVM exceeded the unchanged 8,192 MB ceiling. Frontend checking is recorded separately and is not execution.
  • Whole ReleaseFast language CLI completion: its attempt stopped at the critical disk floor. The failed attempt is retained without passing credit.
  • Expand from these eight files to the full pinned Bake corpus and every required platform/linked SDK. Preserve original assertions, workloads, fixtures and deadlines.
  • Upstream TODOs, skips and environment gates remain separate from implemented passing features.
  • The entire #66 feature/suite/all-platform objective remains open.

Initial reserved-word compilation, missing export linkage, an incorrect all-mode Debug size assertion, invalid original JUnit reports and journal-enabling control invocation failures remain retained. Cache cleanup preserved source/evidence/SDK inputs and invalidated complete inactive derived caches after checking references.

8 days ago

Native Bake graph/JUnit checkpoint: source d8c890b03 and 945 Git-verified evidence artifacts are on main through 1daa83a11. Bake's exact 32-byte release invariant is restored and compiler-enforced; actual ReleaseFast frontend checking passes, and a 33-byte negative control fails as required. Debug remains 56 bytes with safety checks; layout/240 metadata combinations/source-map ownership controls pass. Native promise callbacks link in filtered roots. JUnit now emits valid XML while preserving exact original identities, fixing describe double escaping; 34 validator controls and the actual XML/journal control pass. Eight unchanged Bake files pass with 73 cases/zero failures/two upstream TODOs. Production/development/HMR controls pass. The fresh 157-file regression has 396 passing cases, 142 process checks, zero failures, 37 case skips and three skipped files; validators, ABI, lint and the 12,996-entry integrity audit pass. Optimized graph execution exceeded the unchanged 8 GB ceiling, and the whole ReleaseFast CLI attempt hit the critical disk floor; neither receives passing credit. #901 retains these runtime/platform gates. The full #66 feature/suite/all-platform objective remains open.

Sign in to comment on this issue.