Newest first: the last two weeks here, and every day in its month's page. Each entry describes a change by its effect. How sure the project is of a fix is noted where it matters.
By month: October 2026 · September 2026
2026-10-31#
Engineering#
- The plan's remaining fixed-duration waits now wait on the events they assert.
- The three dependency cycles between units are removed, with a check that fails any new one; it merges after a one-line change to the agents' entry page.
Testing#
- The weekly full pass's chance failure is fixed: the stun check moved to the scripted pair, where a stun is expected.
- Two planted-fault checks were made exact, so each catches only the fault it plants.
- The movement check fails on Dalaran Sewers when the teams start about 62 yards apart, with no approach to judge; a fix is under way.
2026-10-30#
Engineering#
- Every unit-test suite runs through one runner that reports a skip as a skip, and a check refuses any suite that bypasses it.
Testing#
- The weekly full test pass on the main branch failed 2 of 63 tests. One is a check that fails by chance: it waited for a stun in a match where nothing makes a stun land. A fix moving it to the scripted pair is in review.
2026-10-29#
Engineering#
- The agent interface's build check plants its fault in one step instead of a second full build, which halves its run time.
- Unit test programs are limited by processor time rather than wall-clock time, so load on the machine no longer fails them.
2026-10-28#
Engineering#
- A log tool's test-only switch removed; its test plants the fault in a copy of the tool instead.
- Two time-dependent tests fixed: a helper that lived a fixed 30 seconds now lives until stopped, and a commit test runs in under 100 seconds cold.
2026-10-27#
Engineering#
- Every default check now declares the faults it must catch and is shown catching them on every run.
- Three test defects fixed: a fixed sleep replaced by waiting on the event, and two partial-message assertions made whole.
2026-10-26#
Engineering#
- Every live test's planted fault is now shown caught on every run, and the in-game monitors judge every event they see.
- The last cluster of the engineering rebuild, a planted fault for every check, is under way: most of the checks already carry one.
2026-10-25#
Engineering#
- Every dependency is fetched by an exact pin, recorded once; references between files are checked to resolve against the game client's data and the code; the spell data's field positions are declared once and checked against the server's source.
- The last three clusters of the engineering rebuild are under way: a planted fault for every check, live tests shown to catch theirs on every run, and in-game monitors that judge every event they see.
2026-10-24#
Engineering#
- Three more engineering clusters closed: the loadout plan's field order and the server module's environment-name rule are checked against their one definition, the playbook's data has a machine-readable schema checked against its files, and the older formula tests each have a planted fault they are shown to catch.
- The live-test ledger carries a format version.
2026-10-23#
Testing#
- The weekly full live test run passed: 63 tests, none failed or skipped.
Engineering#
- Three more engineering clusters closed: the C++ unit's remaining build configurations are declared to its build, the server's build lives under its own folder and fails loudly when its script is missing, and the unit test programs' remaining gaps are closed.
- The check runner reuses a sealed check's pass when none of its declared inputs changed.
2026-10-22#
Engineering#
- Two more engineering clusters closed: the session loop's own test runs without test-only settings and its lock names have one definition; a check now holds which folders may depend on which, across shell scripts, C++ includes and Python imports, and data folders are read only through their format's reader.
2026-10-21#
Engineering#
- Four more engineering clusters closed: the full test run reads a skipped check as a skip and runs every check on only its declared files; the rules model's live tests wait on the events they check; the rules model's packet reading has one definition; the loadout and data-comparison tools test against committed sample data instead of a live database.
2026-10-20#
Engineering#
- Four more engineering clusters closed: scripts hold no logic, the small test programs are built and checked like the product, the agent's seat is held by the build, and a check whose data is missing fails instead of skipping.
- An inventory of the gaps no cluster named added nineteen more clusters to the engineering rebuild.
- The rules model's live tests are being moved to wait on the events they check instead of fixed delays. This work is not merged yet.
2026-10-19#
Engineering#
- The live-test engineering cluster closed and went live: every live test is shown to catch its planted fault, an aborted test is a failure, and a skipped test is counted as a skip, not a pass.
- The gear-test fix merged, and the gear-loading crash fix is live on the game server.
- The check runner's selection, caching, locks and run log, and the memory-budget arithmetic, are moving out of shell scripts into typed programs. This work is not merged yet.
2026-10-18#
Engineering#
- A crash in the game server's gear-loading code was fixed, along with a race in how its test reads the gear back. Neither fix is live yet.
- A rare failure in the gear test turned out to be in the test itself: it closed a fresh login too early. A fix is in review.
- The comment checker no longer mistakes a
#inside a quoted shell string for a comment. - The governance and comments checks now also cover the agents' own configuration, which closes another engineering-gaps cluster.