← Commit history

0.49.0 build notes: correct the v49 assertion count and record the battery result

Drew Owens ·d480d53307 · ·parent 4cc89d4
1 file changed +10−1
docs/BUILD-NOTES.md+10−1
@@ -181,9 +181,15 @@ actually working on.  ### The suites, and every assertion that was rewritten -New: `g49/v49.mjs`, 114 assertions on a new bench (port 9011, with a dependency-free twin+New: `g49/v49.mjs`, 118 assertions on a new bench (port 9011, with a dependency-free twin on 9015), plus `g49/oldnew.mjs`, which is the old-versus-new recording quoted above. +The whole standing battery is green on both the source tree and the installed 0.49.0+runtime: 1930 assertions across 21 suites, 0 failures, zero JS errors, plus the three+crosscheck identities. `mssel.js` and `msphase.js` are byte-identical A/B against 0.48.0+(md5 `6ab865f017697c83f4f3ed00ac60e28d` on both sides). `server.js` is byte-identical to+0.48.0 and the glow rules are byte-identical to 0.42.0.+ The fixture is built to make the two definitions disagree rather than accidentally agree: a two-row 15-day chain that ends last, a six-row 66-day build that finishes two months earlier and runs on through a third lane to 85 days, a branch that must never light, a@@ -222,6 +228,9 @@ suite that explains itself in terms of a rule the app no longer follows. `mssel.js` and `msphase.js` are fixture-coupled and still report NEEDS REVIEW with an empty `jsErrors`, byte-identical to 0.48.0. +**No live plan was opened and no live server was restarted.** `dc-demo-gantt/` was never+read, written or served at any point in the round.+ ## Build notes, 2026-08-20 (0.48.0, Auto-schedule says it is running)  One change from Drew, client-side. `gantt.html` only. `server.js` did not move: nothing