Every phase, verified in live games

Each client owns a lock-free lane, executed in batches inside the game thread's event dispatch; public facade Game + Bot; new directory layout.

Acceptance Results match the old channel item by item; latency and throughput under concurrency; example bots run end to end.

Move, attack, gather, build, train, cast, learn skills, revive, use items, buy… each with a receipt and a reason code; the SDK facade uses only these.

Acceptance All live verification scripts pass: every kind of command has been issued in a real game and its effect read back.

Push-based world state + trees + event stream: mana, cooldowns, inventory, buffs and current target are all in the snapshot, and items no longer go through the log.

Acceptance Zero game-thread calls to read this information; reconciled unit by unit against the old snapshot; no events lost over a full game.

The reference brain, reflex layer, console, bubbles and director all moved to W3P; map block, engine-level damage / kill events, camera and HUD semantic commands.

Acceptance All live checks pass; the reference brain has 0 task errors over a full game, and the 4 reflex-layer modules have 0 errors.

Lane roles player / observer; per-unit visibility mask; SDK fair mode and enemy memory.

Acceptance Observer commands are rejected, and a player can't command other players' units; fair mode sees only its own vision.

Production table and progress, day/night, combat stats and counters, ground pathfinding, Shift-queue / paths / chained builds / cancel / attack ground, batched commands, per-command execution time; bot manual, pro strategy cookbook, four examples.

Acceptance Every item has offline tests + live checks.

Canvas (runtime-drawn text boxes, panels, progress bars, images, terrain-hugging circles and routes; safe in multiplayer); JASS channel (1291 functions called by name from the Farsight console, command line, HTTP and Python); RPG companion framework (four modes; follow / assist / heal; chat commands, portrait dialogue, lines from a local LLM); reading unit names from custom maps; AI schemes (switch, export, import, trust, results).

Acceptance Run end to end in live games on RPG maps on a test instance: canvas per-frame cost and unit following; JASS functions checked one by one for their effects; the companion follows, assists and retreats for a whole game and keeps following after being revived; switching schemes mid-game to take over the current game.

UI & input (drawn buttons and choice cards are clickable; hotkeys, ground clicks, the ground point under the cursor, local selection; drawn under the mouse cursor); event coverage filled in (spell casts, players leaving, selection changes, screen messages and full chat text, leaving the game); gameplay mods (scheme type mod, with two examples: Hero Roguelike and Endless Defense); gateway (WebSocket / JSON, three roles dev / player / observer, a JS client and browser demo page); MCP server (10 tools).

Acceptance Checked item by item in real games: clicking drawn buttons, pressing hotkeys, clicking the ground, casting spells, chat, defeating the computer player, leaving the game; the gateway and MCP called one by one against a live game; the key flows of both mods run in live games; MCP actually hooked up in Claude Code.