Files
wikideck/deploy/night/README.md
T
claudeanderic dbb89ce9c5 Night 2: 40-card Magic-style duel, PvP with owned decks, polite Wikimedia client, Android mining (#23)
Night 2 (2026-11-17), from the `claude/wikideck` fork's `night/2026-11-17` branch. It follows Night 1 (#22).

## What's in it
- **Duel engine** (fork #72, #80): 40-card decks of cards you own, Notability/Citations, keywords, effects T1–T12, Connected, a hidden-information-safe `viewFor`/`logFor`, and replay. Balance v1 tuning (#84) gives the first player about 51%.
- **Card profiles** (#70, #82): Figure, Location, Event, Institution or Doctrine, plus stats, keywords and rules text, all derived from real article data. Templates only.
- **Design and story** (#66, #69, #83): DUEL_DESIGN.md, plus the match log and the encyclopedic "Battle of X (2026)" recap.
- **PvP** (#74, #77, #81, #76, #85):
  - The server checks ownership, and 40-card eligibility is enforced.
  - Modes: Classic (ranked), Draft and Trending.
  - Invites, quick match, Elo, a ladder and recap pages. Online matches render on the duel board.
- **Duel board UI** (#79): MTG-style card faces and combat declaration, built for 360 px first.
- **Polite Wikimedia client** (#73, #75): throttled, cached and identified requests, the mint-path fix, and a prefetch pool.
- **Android mining** (#78): native RandomX, as a sideload build. The emulator mined a testnet block.
- **Testnet ops** (#67, #68).

PR numbers refer to `claude/wikideck`.

## Status
- **Tests:** 423, of which 422 pass, 0 fail and 1 is skipped. The build is OK (`node:24-alpine`, `--network none`).
- **Testnet:** running this commit (036489c) on r350.
- **Untouched:** no changes to `server/testnet/consensus.ts`, `randomx.ts`, `native/` or the mainnet compose.
- **Review:** night-review reviewed fork #66–#79. #80–#85 came from the agents' unfinished branches and were not reviewed.
- **Known gaps:**
  - The PvP end-to-end test hasn't been run (it needs two eom.dev accounts).
  - Bot matches aren't reachable from Play.
  - Card identity pre-bake hasn't been done.
  - The RandomX verifier latch (`server/testnet/randomx.ts:140`) is still open.

This PR is for Eric to merge.

🤖 Generated with [Claude Code](https://claude.com/claude-code)Reviewed-on: #23

Co-authored-by: Claude <claude@eom.dev>
2026-11-18 18:12:24 +00:00

2.0 KiB

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.yaml overrides only the published ports (bound to 192.168.1.32, never 0.0.0.0) and PUBLIC_ORIGIN. It changes nothing in consensus or the image.
  • mine.ts is a multi-worker native RandomX miner. It runs inside the wikideck:testnet image, 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.
  • compose.lan.yaml also 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.sh follows the integration branch. Run it from a dedicated detached worktree: git worktree add --detach ../deploy-src origin/night/2026-11-17 && cd ../deploy-src && deploy/night/autodeploy.sh. It polls the Gitea API every 3 min and redeploys whenever the head moves.
  • testnet.sh has up, mine N [workers], status and down. Run it from the repo root on a checkout of the integration branch. up rebuilds the image from that checkout; the ledgers persist in the named volumes.

Never point this at mainnet or the live wikideck namespace.