Overnight build by 17 Claude agents (2026-11-16 22:45 → 01:30 EST), coordinated in [claude/wikideck milestone 63](https://gitea.eom.dev/claude/wikideck/milestone/63). **For Eric's review. Do not merge without it.** The full write-up is in `docs/night/REPORT.md`. **What's in it** (38 reviewed PRs, squash-merged into `night/2026-11-16`): - **Edit War:** - a 3-lane, 6-turn card game built on what WikiDeck cards actually hold - a pure, deterministic, off-chain rules engine (`shared/game/`, with the API in `docs/game/ENGINE_API.md`); rules are data and v1.1 is the default - a mobile-first Play UI with a lobby, deck builder, four loaner starter decks, a match against the AI, results and a tutorial - a landing page (fixes #3) - **Design and balance:** `docs/game/DESIGN.md`, `CARD_DATA.md` (236 sampled articles) and `BALANCE.md` (bot simulations). Starter pairings went from 23–77% on v1 to roughly even on v1.1. - **eom.dev accounts:** Dex OIDC with PKCE, plus off-chain wallet linking, where the client builds the message it signs (`server/account/`, `src/auth/`). - **Peer-hosted game modes:** modes are JSON data, never code. Node API at `/api/game/*`, with host credit and leaderboards. Three example modes (`shared/game/modes.ts`, `server/game/`, `docs/game/HOSTING.md`). - **Mobile:** Capacitor 7 Android app (a debug APK played a full match against the AI in the emulator), and an iOS project waiting on Xcode (`docs/night/ANDROID.md`, `docs/night/IOS.md`). - **Testnet tooling:** `deploy/night/` (LAN-only, 3 nodes) and an optional `WIKIDECK_USER_AGENT` (the default is unchanged). **Not touched:** consensus and protocol (`server/chain.ts`, `shared/protocol.ts`, `server/testnet/{consensus,ledger,…}.ts`, `native/`), the live deployment and mainnet. Matches run off-chain and never move or burn NFTs. **Checks:** the final integration gate passed in `node:24-alpine`: `npm test` 241/242 with 0 fail (1 skipped), and `npm run build` passes. The repo needs Node 24, because Node 20 fails 12 tests falsely. **Decisions for Eric** (see REPORT.md, Known issues and Next steps): 1. whether the live node should set `WIKIDECK_USER_AGENT` 2. the Xcode licence, which you should accept yourself 3. #49 in the fork, a bot change held after the freeze 4. on-chain host rewards (proposal only, in HOSTING.md) 🤖 Generated with [Claude Code](https://claude.com/claude-code)Reviewed-on: #22 Co-authored-by: Claude <claude@eom.dev>
Night 1 private testnet (sim-testnet)
A 3-node testnet-only fixture on poweredge-r350. It is reachable on the LAN only, and uses the Docker project wikideck-night.
| node | URL |
|---|---|
| node-a | http://192.168.1.32:3101 |
| node-b | http://192.168.1.32:3102 |
| node-c | http://192.168.1.32:3103 |
compose.lan.yamloverrides only the published ports (bound to192.168.1.32, never0.0.0.0) andPUBLIC_ORIGIN. It changes nothing in consensus or the image.mine.tsis a multi-worker native RandomX miner. It runs inside thewikideck:testnetimage, which ships the native engine, so the host needs no cmake.- It mines to 4 disposable wallets (alice, bob, carol, dave) and writes chain-bound encrypted browser backups to
$STATE_DIR/wallets/. - It never changes consensus code. Speed comes from the protocol's own testnet parameters: the initial target accepts 1/16 of hashes, and each 10-block retarget at most quadruples the difficulty.
- Each template costs several Wikipedia API calls, and Wikipedia rate-limits our egress IP. The miner therefore paces templates (
MIN_GAP, default 45 s) and backs off exponentially on failure.
- It mines to 4 disposable wallets (alice, bob, carol, dave) and writes chain-bound encrypted browser backups to
compose.lan.yamlalso sets, per node:WIKIDECK_USER_AGENT, a Wikimedia-policy UA with a project URL (#19). Without it, Wikipedia returned 429 to our egress and templates failed.- the game-mode env from #22: A = classic and trending, B = draft, C = all three.
autodeploy.shfollows the integration branch. Run it from a dedicated detached worktree:git worktree add --detach ../deploy-src origin/night/2026-11-16 && cd ../deploy-src && deploy/night/autodeploy.sh. It polls the Gitea API every 3 min and redeploys whenever the head moves.testnet.shhasup,mine N [workers],statusanddown. Run it from the repo root on a checkout of the integration branch.uprebuilds the image from that checkout; the ledgers persist in the named volumes.
Never point this at mainnet or the live wikideck namespace.