# Community game-night board · recorded Ergod run

This is a synthetic planning brief processed in the signed-in Ergod web Work surface on 23 September 2026, using **Hunyuan 3** (`openrouter/tencent/hy3`). The people, place and event are fictional. The saved HTML versions are unmodified downloads from the run. Do not describe this as a live Discord channel room.

## Initial request, 00:05

> Build a self-contained interactive HTML decision board for a fictional five-person community game night. This is a real usable page, not a mockup screenshot. Use only these synthetic notes: Friday October 9, 2026, 7–9 pm works for Ash, Bee, Dev and Eli (4 people). Saturday October 10, 2026, 6–8 pm works for Ash, Cal and Dev (3 people). Game votes are cooperative heist 4, trivia 3, drawing relay 2; individual votes are unknown, so do not invent them. The room is Oak Room, 14 Sample Lane, Example City; use the courtyard ramp. One player needs instructions in text, not audio alone. Please make the page mobile-friendly and keyboard usable. Show the recommended slot and game with the numbers and reasoning visible; let someone toggle each person’s availability for either slot and recompute the recommendation live, including an honest tie state. Include a copyable channel announcement based on the current selection and a short print-friendly run sheet. No external assets or made-up policies/contacts. Attach the finished HTML file, then tell me how to test the interactive parts.

The first large `Write` tool call hit its 8,192-token argument cap. Ergod split the file into a small write and an edit. During its own review it caught a game-vote tie bug caused by comparing the first game with itself, corrected it, then attached `game-night-v1.html`. This is evidence of correction, not a flawless first pass.

## Independent first-pass check

`node proof/verify-game.cjs` at 1280 px and 390 px found no page errors or horizontal overflow. The initial recommendation was Friday with four confirmed players against Saturday's three, and cooperative heist led with four votes. Toggling Eli's Friday availability off produced a 3–3 tie in the recommendation, announcement and run sheet. A4 print used **two pages**, and the design was visually repetitive and included self-referential process text. `game-night-v1.html` is retained intact.

## Quality revision requested, 00:15

> I tested the attached board at 1280px and 390px: the default Friday 4 vs Saturday 3, cooperative-heist 4-vote lead, and a 3–3 tie after one toggle all work. Please now make a focused quality revision to this same HTML. The current screen reads like a debug report with many repeated cards and process notes. Give it a clearer visual hierarchy: a striking but restrained decision summary, visible 4-versus-3 comparison, compact vote bars, and a crisp announcement area; keep it self-contained, calm, and readable on a phone. Replace “No” for people with no stated slot availability with “Unconfirmed” (count only confirmed people). Remove self-referential page copy about synthetic notes, code buttons, and no external assets; a small “fictional example” note is enough. Make the A4 print view contain only the title plus a complete run sheet on one page. Keep the working live recommendation/tie logic, keyboard controls and copy action; show success only if copying actually succeeds. Reattach the revised file and briefly say what changed.

The first response to this revision read the existing file but stopped before any edit. A follow-up at 00:20 explicitly told Ergod to continue. The revision needed another continuation after an interrupted intermediate edit; that attached version is preserved as `game-night-v2.html`.

## Final correction and check, about 00:32

Independent visual review found that the comparison and vote bars in v2 were blank: their width was being applied to inline spans. We asked Ergod for the narrow display fix and a reattached file. The unmodified download is `game-night-final.html`. This correction is part of the recorded journey, rather than a local edit to the output.

`node proof/verify-game.cjs` then checked the final file at 1280 × 800 and 390 × 844. Both widths had no script errors or horizontal overflow; the Friday 4 versus Saturday 3 comparison and 4/3/2 vote bars were visibly filled. Toggling Eli off Friday changed the recommendation, channel announcement and run sheet to an honest 3–3 tie. The generated print PDF is one A4 page with the essential venue, access, attendance and schedule details. The screenshots and PDF beside this note come from that check. The copy action reports success only after its browser clipboard call or fallback succeeds; the system clipboard was not checked independently.

This is a **web Work run with fictional inputs**, not a Discord run. The final board is useful and inspectable, although it required several follow-ups and still has a restrained utility style. Its actual result can support a showcase; the revised versions and original request should remain linked.