HS scoreboard: dict-eq fix entry + post-JIT-Phase-2 regression note
Some checks failed
Test, Build, and Deploy / test-build-deploy (push) Failing after 39s

Records that the 1514/1514 claim was relative to the kernel as of
92619301; the value-handle ABI + numeric tower + JIT Phase 2 commits
introduced three regressions (1 dict-eq, now fixed in 4db1f85f, and 2
event-or-timeout wait tests still pending).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-05-12 21:22:00 +00:00
parent 4db1f85fe8
commit 4d92eafb36

View File

@@ -22,10 +22,29 @@ Cleared this session (18 → 0 skips):
## Status: 1514/1514 ✓ — no remaining work in upstream conformance.
### 2026-05-12 — kernel-eq regression after JIT Phase 2 + numeric tower
The 100% claim held against the kernel as it was at 92619301. Subsequent
commits (Phase 1+2+3 JIT, value-handle ABI, numeric tower) regressed three
tests; one is now fixed:
- arrayLiteral / arrays containing objects work — **fixed** in 4db1f85f
(deep_equal in sx_browser.ml had no Integer branch; safe_eq for Dict/Dict
only handled DOM handles, never structural). Suite back to 8/8.
- hs-upstream-wait / can wait on event or timeout 1 — still failing
(assertion-fail). `wait for foo or 0ms` likely a parser/runtime path.
- hs-upstream-wait / can wait on event or timeout 2 — same shape.
Batched run (75-test batches, parallel=2) currently: 1436+1 confirmed pass,
2 fails, 75 unverified (batch 150-225 hits >15min on slow reactivity tests).
Worst-case score: 1437/1514 (94.9%); best-case (75 unverified pass):
1512/1514 (99.87%).
Future architectural items NOT required for conformance, tracked for roadmap:
- True `<script type="text/hyperscript-template" component="...">` custom-element registrar
- True async kernel suspension for `repeat until event` (yielding to JS event loop)
- Parser fix for `from #<id-ref>` after `event NAME` in until-expressions
- `wait for foo or 0ms` (event-or-timeout) — parser support needed
## Cluster ledger