MTG farm volunteer client v22

Superseded by client-v23, which carries the new harness pin (the farm's harness no longer cuts off slow AI decisions, so a game stops depending on machine speed) and fetches that harness on Start. A v22 client keeps playing the harness it has, and its Install Forge now refuses the farm's new harness.

One-zip Windows volunteer client for the MTG sim farm. Unzip, double-click run-client.bat, enter the farm URL and your runner credential on the first-run page, click Add, pick your work, and go.

New in v22: the client can install Forge engine 2.0.14+6747f05e908 -- the dead-card batch: 161 cards the AI never cast now get cast, plus Commandeer and seven others from the batch before it. When the farm switches to that engine, Start (which syncs first) or Install Forge fetches the pinned, digest-checked engine release. Nothing about how the client plays changed.

From v21: the bundle is GPLv3 (LICENSE and NOTICE.txt travel in the zip). From v20: a stopped worker starts from its own row. From v19: a candidate's own named derived card order. From v17: the 2.0.14+139b268b780 engine row. From v16: workers persist -- add, start, stop and delete are separate, and rows and their game counts survive a restart. From v12: the client updates itself.

Headless: farmrunner.py --mode backfill --decks REF[,REF...] [--scope within].

Ships Windows embeddable Python 3.12.10; the Forge engine (~205 MB) is downloaded on demand. Needs a farm that advertises active_engine on /hello (any farm since de63260).

sha256(mtg-farm-client-v22.zip) = 167c79593e7e452eae0a1f06fae0d77214a0f7344e06b24e80562de0877582d6