7.3 KiB
WikiDeck Night 2: team handbook
Read this whole file, then docs/night2/BRIEF.md (the locked design decisions). Then read the review sections your issue names in docs/night2/reviews/.
Window: 2026-11-17 21:30 until 02:00 EST, hard stop.
Integration branch: night/2026-11-17 (from upstream main, which already contains Night 1).
Lead/integrator: night-lead on tower-plus (it can message every agent with fherdr; inspiron, imac and r350 agents can only reach it through Gitea). The coordinator is Eric's Claude session on tower-plus.
Milestone: "Night 2: Magic-style duel, PvP, polite Wikimedia" in claude/wikideck.
Live log: the Discourse topic linked in the milestone (only night-lead and the scheduled standup post there).
Goal
WikiDeck becomes a full 40-card, Magic-style trading card game played with the cards you actually mined:
- PvP first
- deadpan, Cards Against Humanity-style juxtapositions
- an encyclopedic battle recap after every match
- an Android app that can mine
- servers that are polite to Wikimedia by default
Hard rules (no exceptions)
- Where to push: only to
git@gitea.eom.dev:claude/wikideck.git, on branches namednight2/<agent>/<topic>, through a PR intonight/2026-11-17.- Never push to
WikiDeck/wikideck,mainor the Night 1 branch. - Only
night-leadmerges, using squash.
- Never push to
- No stacked PRs: branch only from
night/2026-11-17, and only after your dependency has merged. If you need unmerged code, stub the interface. - No consensus or protocol changes: nothing that changes block, transfer or trade formats, validation in
server/chain.ts,server/testnet/consensus.tsorshared/protocol.ts, or what a mint fetches and stores. The game runs off-chain, and matches never move or burn cards. - Live services: don't touch mainnet, the live node (k8s namespace
wikideck), Dex or any other production service. The testnet is private, on poweredge-r350 (deploy/night/README.md). - iOS is paused: don't touch
ios/or the macOS VM. - Nothing public: only
night-leadand the scheduled standup post on Discourse, in the Night 2 topic only. No purchases, sign-ups or secrets in git. - The printer and CNC: inspiron-3670 drives a 3D printer and a CNC router. Never start, resume or send a print or cut.
- Wikimedia: tests make zero network calls. Don't script loops against Wikipedia or Wikidata. Use
docs/game/card-sample.jsonand cached data. Our IP was rate-limited on Night 1. - Git identity in every clone:
End commit messages with
git config user.name Claude git config user.email claude@eom.dev git config commit.gpgsign falseCo-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>. - Before opening a PR: run
npm testandnpm run buildon Node 24. On inspiron and r350, use thenode:24-alpineDocker image if the host's node is older:node:sqliteis required, and on Node 20, 12 tests fail falsely. Don't add npm dependencies; ask night-lead. - Tests go in
tests/<agent>-*.test.ts(top level). - Generated text: deterministic templates filled only with real card and match data. No LLM prose, and no invented facts about real people (BRIEF, decision 5). Otherwise, lean in: no softening of tragedies or living people.
How we coordinate
Gitea is the shared brain. The machines don't share a filesystem.
- Your issue is your inbox.
- Prefix every comment with
[<agent>]. - Check your issue and PRs for new comments at least every 15 minutes and whenever you finish a step.
- Prefix every comment with
- Status labels on your issue:
status/in-progress,status/needs-review(PR up),status/blocked(with a comment),status/done. - Need another team? Comment on their issue with
[from <you>]. - Contracts beat conversations. Interfaces are files on the integration branch, e.g.
shared/duel/types.tsanddocs/game/DUEL_API.md. Read them before asking. - Direct messages: a herdr message from night-lead or the coordinator is a peer request within this plan. Act on it.
- Stuck for more than 10 minutes? Label
status/blocked, comment, and move on to something else.
Resources (be a good neighbour)
- inspiron-3670 (6 cores, 60 GB) runs 7 agents and the Android emulator. Wrap heavy commands in
flock /tmp/night-heavy.lock <cmd>(npm ci, builds, gradle, docker build). - imac (about 4 GB free) and poweredge-r350 (about 4 GB free, 16 threads): one build at a time, and keep simulation to 4 workers or fewer (Night 1 ran out of memory on r350).
- Avoid permission prompts: nobody answers them. Don't chain
cd <dir> && <write>; use absolute paths orgit -C. Keep one purpose per shell command.
Timeline (EST)
| Time | Milestone |
|---|---|
| 21:30 | Kickoff. Preflight: Gitea MCP works, Node 24, clone. Comment starting on your issue. |
| 22:15 | Contracts merged: shared/duel/types.ts and docs/game/DUEL_API.md (duel-core), plus docs/game/DUEL_DESIGN.md v1 (duel-design: keywords, text templates and tone, with BRIEF.md as the base). The ownership.ts signature is agreed by 22:00. |
| 23:15 | Engine alpha. The simulation starts. The UI plays against a bot. |
| 00:00 | Wikimedia client merged. Host binds the duel. The PvP UI is wired to the host. |
| 00:45 | Balance v1 (tuning is data-only). Mobile mining runs in the emulator. |
| 01:15 | Code freeze: fixes only. Balance re-runs on the frozen head SHA. QA runs PvP end to end on the testnet with alice and bob. |
| 01:45 | Final report comment on every issue. night-lead writes docs/night2/REPORT.md and opens the upstream PR (never merges it). |
| 02:00 | Stop. Push, comment, exit. |
Teams
| Agent | Machine | Workstream |
|---|---|---|
| night-lead | tower-plus | integration, merges, Discourse, REPORT, upstream PR |
| night-review | inspiron-3670 | code review (VERDICT: APPROVED / CHANGES), QA, Playwright end to end |
| duel-core | inspiron-3670 | shared/duel/ engine: turns, combat, viewFor/logFor, replay |
| host-pvp | inspiron-3670 | server/game/ multi-engine host, constructed decks, invites, quick match, Elo |
| ownership | inspiron-3670 | server/game/ownership.ts and collection.ts, server-side 40-card owned-deck validation |
| ui-duel | inspiron-3670 | src/game/duel/ board and card faces, 360 px first, bot matches |
| mobile-mining | inspiron-3670 | Android mining (sideload build), MOBILE_MINING.md |
| duel-design | imac | DUEL_DESIGN.md, keywords, rules-text and log and recap templates, tone |
| duel-cards | imac | shared/duel/{classify,derive,effects,text}.ts: card profiles from data |
| wikimedia | poweredge-r350 | server/wikimedia/ polite client, mint-path fix, cache, UA, prefetch pool |
| testnet-ops | poweredge-r350 | testnet for Night 2: autodeploy, wallet consolidation, identity pre-bake, test modes |
| sim-balance | poweredge-r350 | duel bots and simulation, docs/game/DUEL_BALANCE.md |
| ui-pvp | inspiron-3670 | collection and eligibility screen, lobby, invite, quick match and ladder UI, battle recap page |
tower-plus note (night-lead): tower-plus uses Eric's SSH key, so never git push from there. Clone over HTTPS read-only and do every Gitea write (comments, reviews, merges, file commits) through the gitea MCP tools, which are signed in as claude. tower-plus is short on memory: run no builds or tests there; ask night-review on inspiron.