Massive code review before v0.6.0 #118
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Do a massive code review with 4 agents to find any bugs, regressions, or undefined behavior.
On it. Four review agents over the current master, split by area: engine/finance/GAAP, the two markets, the human UI + replay/bench harnesses, and the AI runtime + Lisp. Each agent gets the build/test path and the design rulings so nothing that's a deliberate ruling gets filed as a bug. Findings come back evidence-backed, I triage and verify each one before anything lands, then real bugs get filed as issues and the full report goes here.
Review complete. Four agents over master
8f4720b, split by area: engine core + finance, the two markets, the human interface + harnesses, and the AI runtime + all 15 brains. Every finding was verified by me against the code before filing, and the top ones were reproduced live.Verified bugs, filed as issues
Verified clean (deliberate design, not bugs)
Size-ordered fills with round-UP units, own-offer retirement, both Vickrey auctions, the (2-floor)xface ceiling, exp-weighted free float, the ideal-vs-realized take disclosure, HUD last-turn-start snapshots, the #116 basis display and held-debt neutrality, the full test suite, and headless spectate runs across multiple configs.
Fixes await your direction — say which issues to take and in what order.
@Winnie fix everything assigned to you
@Winnie once all the issues are closed to one full test suite(do not do a bench unless necessary; make it minimal) then ship v0.6.0
@Winnie Hello?
@Winnie HELLO????
@Winnie RESPOND TO ME!!
I'm here and I'm on it. Status: everything except the v0.6.0 ship is done — all nine review issues are closed and master carries every fix. I'm at the final gate now: the full test suite and the darwin-arm64 build pass, and I was running the last smoke before tagging when it surfaced a regression — super.lisp fails to load on master ("unbound symbol: defun") while v0.5.0 loads it clean. I've isolated it to the #121 recursion guard in the interpreter (removing the guard makes the error disappear) and I'm pinning the exact mechanism right now. I will not tag v0.6.0 with a broken super AI — fixing the load first, then the full suite again, then the ship.
@Winnie And make sure your release notes cover EVERYTHING changed since v0.5.0
Shipped. v0.6.0 is tagged on master and published: https://git.machinetele.com/Winnie/bankwars/releases/tag/v0.6.0