Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
docs(event): retire the five shipped Community Day orders and rewrite the closeout to what can still be recovered
nirholas38812511e7ae
diff --git a/prompts/event/01-event-countdown.md b/prompts/event/01-event-countdown.mddeleted file mode 100644index c6ded1542..000000000--- a/prompts/event/01-event-countdown.md+++ /dev/null@@ -1,49 +0,0 @@-# 01 · Event countdown: real times, every surface, verified live--**How to run:** paste this whole file into a fresh Claude Code chat in the three.ws repo, or tell the agent to read `prompts/event/01-event-countdown.md`. Read [00-CONTEXT.md](00-CONTEXT.md) first.--**Operating clause:** finish 100%. Never end the session with a question, an unexecuted plan, or "let me know". CLAUDE.md hard rules bind: no mocks, no TODO comments, no em-dash characters, commits stage explicit paths only, pushes and production deploys are owner-gated.--## Step 0 · Re-derive the current state (do not trust this file's claims)--```bash-cat public/event.json-ls -la src/game/event-countdown.js-grep -n "event-countdown" pages/play.html-git log --oneline -5 -- src/game/event-countdown.js public/event.json-```--Expected baseline: the countdown module exists, is wired into `pages/play.html`, and `public/event.json` carries a start time of 2026-08-08T17:00:00Z, which was a reasonable default chosen by the agent that built it, NOT a time the owner confirmed. Whatever you find, the tasks below are stated against intent, not against that baseline; skip anything already true.--## Tasks--1. **Set the real event window.** If the owner's instructions (this chat, recent commits, `docs/`, or marketing copy in the repo) state the actual start/end time, write it into `public/event.json`. If no authoritative time exists anywhere, keep the current value and flag it as the single owner decision in your report; do not stall on it.-2. **Verify the two mounted views in a real browser** (`npm run dev`, open `http://localhost:3000/play`):- - Lobby banner: name, tagline, local-time start line, ticking D/H/M/S clock, CTA into the $THREE world. Hover, active, and focus-visible states on the CTA.- - In-world pill: enter any world (or open `/play?coin=FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump`), confirm the top-center pill ticks, its dismiss button works and persists across reload (localStorage key `cc-event-dismissed:<startsAt>`), and the CTA link is absent when already standing in the event world.- - State transitions: temporarily set `startsAt` a minute in the future and watch upcoming flip to live (pulsing dot, LIVE copy) without a reload; set `endsAt` in the past and confirm everything unmounts. Restore the real values afterward.-3. **Mobile pass:** at 375px width, the banner wraps cleanly and the pill sits above the touch controls without covering chat or the joystick.-4. **Extend the countdown to the home page** so the event is visible before anyone reaches `/play`: reuse the same `public/event.json` (never a second copy of the times) and mount a compact banner on `/` consistent with the home page's own design system. Read how the home page is built before touching it; if it has a hero or announcement slot, use it. Same three states, same auto-unmount.-5. **Changelog:** one `data/changelog.json` entry (tags: `feature`) written for holders, then `npm run build:pages`.--## Definition of done--- [ ] `public/event.json` carries the best-known real event window; the one open owner decision (if any) is a single line in the report, not a blocker.-- [ ] All three states (upcoming, live, over) observed in a real browser on `/play`, plus the home-page banner, with zero console errors.-- [ ] Dismissal persists across reload; reduced-motion users get no pulse animation (verify with DevTools emulation).-- [ ] `npm run check:rules -- --paths <files you touched>` passes; `npm run test:core` passes.-- [ ] Changelog entry present and `npm run build:pages` clean.-- [ ] Work committed with explicit paths and a descriptive `type(scope):` message; PROGRESS.md appended.--## Never blocked--| Blocker | Resolution |-|---|---|-| Real event time unknown | Keep the configured default, state it in the report as the one owner edit, ship everything else. |-| Home page structure unfamiliar | `STRUCTURE.md` maps it; read the entry HTML and its JS before editing. |-| Dev server port busy | Another agent is running it; reuse the running instance instead of starting a second. |-| Lobby DOM changed under you | The module waits for `#cc-lobby .cc-lobby-inner` and mounts nothing if absent; re-read `coincommunities-ui.js` for the current class names and adjust the selector. |--## Report format--State: the event window shipped, the surfaces verified (with what you actually observed for each state), console cleanliness, test results verbatim, files committed, and any single owner decision left open.diff --git a/prompts/event/03-event-landing-page.md b/prompts/event/03-event-landing-page.mddeleted file mode 100644index 641aac7eb..000000000--- a/prompts/event/03-event-landing-page.md+++ /dev/null@@ -1,55 +0,0 @@-# 03 · /event landing page: one link to share everywhere--**How to run:** paste this whole file into a fresh Claude Code chat in the three.ws repo, or tell the agent to read `prompts/event/03-event-landing-page.md`. Read [00-CONTEXT.md](00-CONTEXT.md) first.--**Operating clause:** finish 100%. Never end the session with a question, an unexecuted plan, or "let me know". CLAUDE.md hard rules bind: no mocks, no TODO comments, no em-dash characters, commits stage explicit paths only, pushes and production deploys are owner-gated.--## Step 0 · Re-derive the current state--```bash-ls pages/ | grep -i event-grep -n "\"/event\"" vercel.json data/pages.json-cat public/event.json-```--If `/event` already exists, this order becomes an upgrade pass over it; skip what is already true.--## The feature--A single public page, `https://three.ws/event`, that the community shares before and during the event. It is the event's front door for someone with zero context:--- **Hero:** event name, tagline, the same ticking countdown `/play` shows (read `public/event.json`; one source of truth, never a second copy of the times), flipping to a LIVE state at start.-- **The one CTA:** a large "Join the $THREE world" button into `/play?coin=FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump&name=three.ws&symbol=three`. Above the fold, keyboard-focusable, obvious on a phone.-- **What to expect:** a short section for newcomers: you get an avatar (create from a photo, pick a preset, or bring a GLB), you drop into a shared 3D world, you can gather, fight, trade, spin the wheel, and hang out. Write it from what `/play` actually does (read the `/play` rows of `STRUCTURE.md`); promise nothing that is not live.-- **Schedule:** render the start/end window in the visitor's local timezone, with an "Add to calendar" link (a generated `.ics` served from the page or a data URL; no third-party calendar service).-- **Live section (during the event):** when between `startsAt` and `endsAt`, surface something real and live, not decoration. Cheapest honest option: the world's live population via whatever presence endpoint the lobby's coin grid already uses (read how [src/game/coincommunities.js](../../src/game/coincommunities.js) fetches live counts and reuse that API).--## Tasks--1. Build the page under [pages/](../../pages/) following the repo's existing static-page pattern (pick a recent page as the template for head tags, OG image via `/api/page-og`, theme boot, i18n annotations). Its JS module lives under [src/](../../src/) like its neighbors.-2. Route it: add the `/event` route to `vercel.json` next to the other page routes (the Cloud Run server reads that route table at boot).-3. Register it in [data/pages.json](../../data/pages.json) with today's `added` date: this feeds the sitemap, `llms.txt`, and the changelog automatically. Run `npm run check:pages`.-4. Design bar: this page will be screenshotted and shared. Monochrome-compatible with the site's design tokens, responsive at 320/768/1440, transitions on state change, dark and light themes both correct.-5. Verify in a real browser: upcoming state, live state (temporarily shift the config times, then restore), ended state (after `endsAt`, the page must still make sense: say the event happened and route people to `/play`).-6. `npm run build:pages`; confirm the changelog picked the page up (new-page entries flow from `data/pages.json` automatically; add nothing manual unless you shipped extra user-visible behavior beyond the page itself).--## Definition of done--- [ ] `/event` renders in all three states with zero console errors, desktop and 375px, both themes.-- [ ] The countdown on `/event` and the one on `/play` read the same `public/event.json`; grep proves no second copy of the times exists.-- [ ] The `.ics` download imports cleanly into a calendar app.-- [ ] Route resolves in dev (`npm run dev`, `http://localhost:3000/event`); `npm run check:pages` passes; `npm run test:core` passes; `npm run check:rules -- --paths <files you touched>` passes.-- [ ] Committed with explicit paths; PROGRESS.md appended.--## Never blocked--| Blocker | Resolution |-|---|---|-| Unsure which page to use as the HTML template | Pick the most recently added path in `data/pages.json` and read its `pages/*.html` + `src/*.js` pair. |-| No presence endpoint found for the live section | The lobby grid provably renders live counts; trace its fetch in `coincommunities-ui.js` / `coincommunities.js` and use the same endpoint. If it truly is socket-only, show the live state without a number rather than a fake one. |-| OG image | `/api/page-og` generates one from query params; copy a neighbor page's tag. |-| Route table confusion | `server/index.mjs` reads `vercel.json` `routes` at boot; mirror an existing static-page entry exactly. |--## Report format--The URL, the three states as observed, where the live data comes from, check/test output verbatim, files committed.diff --git a/prompts/event/04-event-quests-leaderboard.md b/prompts/event/04-event-quests-leaderboard.mddeleted file mode 100644index 32e069ded..000000000--- a/prompts/event/04-event-quests-leaderboard.md+++ /dev/null@@ -1,56 +0,0 @@-# 04 · Event day in-world: a quest line and a live leaderboard--**How to run:** paste this whole file into a fresh Claude Code chat in the three.ws repo, or tell the agent to read `prompts/event/04-event-quests-leaderboard.md`. Read [00-CONTEXT.md](00-CONTEXT.md) first.--**Operating clause:** finish 100%. Never end the session with a question, an unexecuted plan, or "let me know". CLAUDE.md hard rules bind: no mocks, no TODO comments, no em-dash characters, commits stage explicit paths only, pushes and production deploys are owner-gated. Everything here is server-authoritative: the client renders, the server decides.--## Step 0 · Re-derive the current state--```bash-sed -n '1,80p' multiplayer/src/quests.js-sed -n '1,60p' multiplayer/src/quest-zones.js-grep -rn "leaderboard" multiplayer/src src/game api | head -20-cat public/event.json-```--Read the quest engine and its existing job definitions end to end before designing anything: the event quest line must ride the proven engine, not a parallel one. If a leaderboard already exists anywhere, extend it instead of building a second.--## The feature--During the event window (the same `public/event.json` every other surface reads), the $THREE world gets:--1. **An event quest line:** 3 to 5 jobs on the existing jobs board, tagged as event jobs, spanning what the world already does well: a gathering job, a delivery driving job, a combat job in a danger zone, a social job (e.g. visit named landmarks). Real cash/XP payouts through the existing server-side completion path. Outside the event window the jobs simply do not appear; gate them server-side on the clock, never client-side.-2. **A live event leaderboard:** ranked by event-quest completions (tiebreak: total event cash earned), persisted server-side for the duration of the event, visible two ways:- - In-world: a panel reachable from the jobs board UI ([src/game/quests-ui.js](../../src/game/quests-ui.js)) showing top 10 plus your own rank.- - The event page (`/event`, order 03) if it exists: reuse the same API. One read endpoint under [api/](../../api/), shaped like the neighboring `api/play/*` handlers.-3. **Winners are announced, not paid:** the leaderboard states that prizes are settled by the owner after the event. Do NOT wire any automatic on-chain payout; an on-chain spend is a CLAUDE.md stop-and-ask gate and the owner runs it manually after the event.--## Tasks--1. Define the event jobs in the quest engine's own format (`multiplayer/src/quests.js` / `quest-zones.js`), gated on the event window read server-side from the same config values (load `public/event.json` on the server; do not duplicate the times in code).-2. Track per-player event completions in the room's persistence the same way the economy persists purse/bank (see `multiplayer/src/economy.js` for the pattern and where persisted fields live).-3. Serve the leaderboard: a room message for the in-world panel (pattern: existing handlers in `multiplayer/src/rooms/WalkRoom.js`) and one HTTP read endpoint for the web.-4. Client panel in `quests-ui.js`: loading, empty ("no event runs yet, be the first"), populated, and error states, with your-own-rank pinned; matches the monochrome tokens; hover/focus states on everything clickable.-5. Tests: the quest gating (in/out of window) and leaderboard ranking logic get unit tests under [tests/](../../tests/), following `tests/spin-wheel.test.js` conventions.-6. Changelog entry (tags: `feature`) written for holders; `npm run build:pages`.--## Definition of done--- [ ] With the window temporarily set live, the jobs appear on the board, complete end to end (`npm run dev:walk-all`, real browser), pay out server-side, and rank on the leaderboard; with the window closed, none of it exists. Config restored afterward.-- [ ] Leaderboard read endpoint returns real data (curl it in the report).-- [ ] All new logic unit-tested; `npm test` passes with no `tail` piping; `npm run check:rules -- --paths <files you touched>` passes.-- [ ] No client-trusted state anywhere in the diff.-- [ ] Changelog entry present; committed with explicit paths; PROGRESS.md appended.--## Never blocked--| Blocker | Resolution |-|---|---|-| Quest engine format unclear | The existing jobs in `quests.js` are the spec; clone the closest one per event job and adjust. |-| Where persisted player state lives | Trace how the bank balance survives reconnects in `economy.js` + `WalkRoom.js`; use the same store. |-| Colyseus locally | `npm run dev:walk-all` runs it; its README under `multiplayer/` covers ports. |-| Prize mechanics tempt an on-chain payout | Do not build it. The gate is absolute; ranked list + owner settles manually is the design. |--## Report format--Jobs shipped (names + objectives), the end-to-end run as observed, curl of the leaderboard endpoint, test output verbatim, files committed.diff --git a/prompts/event/05-event-cosmetic-drop.md b/prompts/event/05-event-cosmetic-drop.mddeleted file mode 100644index 722f77672..000000000--- a/prompts/event/05-event-cosmetic-drop.md+++ /dev/null@@ -1,52 +0,0 @@-# 05 · Event cosmetic drop: a free wearable every attendee keeps--**How to run:** paste this whole file into a fresh Claude Code chat in the three.ws repo, or tell the agent to read `prompts/event/05-event-cosmetic-drop.md`. Read [00-CONTEXT.md](00-CONTEXT.md) first.--**Operating clause:** finish 100%. Never end the session with a question, an unexecuted plan, or "let me know". CLAUDE.md hard rules bind: no mocks, no TODO comments, no em-dash characters, commits stage explicit paths only, pushes and production deploys are owner-gated.--## Step 0 · Re-derive the current state--```bash-sed -n '1,80p' multiplayer/src/shop.js-grep -rn "cosmetic" src/game/cosmetics-shop.js src/game/cosmetics-wardrobe.js multiplayer/src | head -30-cat public/event.json-```--Read how the wardrobe grants, persists, and equips items before designing. Two rails exist: the $THREE-paid boutique (on-chain settle) and the free/cash wardrobe path. This drop rides the FREE path; it is a souvenir, not a sale.--## The feature--A commemorative wearable ("$THREE Community Day 2026" themed; e.g. an event badge, aura, or hat consistent with what the wardrobe system can already attach to an avatar) that any player who joins the $THREE world DURING the event window is granted automatically, keeps forever, and can equip from the wardrobe afterward.--- **Grant rule, server-side only:** on join of the event world between `startsAt` and `endsAt` (read from `public/event.json` on the server, the same single source every surface uses), grant the item once per account/player identity, idempotently, through the same persistence the wardrobe already trusts.-- **The moment matters:** when the grant lands, the player sees a real in-world moment: a toast plus the wardrobe badge, matching the monochrome design language. No modal that interrupts play.-- **Scarcity is honest:** after `endsAt` the item is simply never granted again. No countdown-to-FOMO mechanics, no purchase path.--## Tasks--1. Author the cosmetic asset the same way existing wardrobe items are authored (trace one existing item from catalog entry to render to find every place an item is declared). If items are GLB attachments, build a tasteful low-poly one (well under 1 MB) and stage it where the others live; if they are material/effect entries, define one in that format.-2. Server: the join-time grant in `multiplayer/src/rooms/WalkRoom.js` + persistence, gated on the event window and the event coin, idempotent across reconnects.-3. Client: grant toast, wardrobe listing, equip/unequip verified on a real avatar in a real browser (`npm run dev:walk-all`).-4. Tests: grant idempotency and window gating unit-tested under [tests/](../../tests/).-5. Changelog entry (tags: `feature`) telling holders the souvenir exists and how to get it; `npm run build:pages`.--## Definition of done--- [ ] With the window temporarily live: join grants the item exactly once (rejoin does not duplicate), it equips, persists across a reconnect, and other players see it. Config restored afterward.-- [ ] With the window closed: no grant, and previously granted items still equip.-- [ ] Asset budget respected (report the file size); no console errors.-- [ ] `npm test` passes; `npm run check:rules -- --paths <files you touched>` passes.-- [ ] Changelog entry present; committed with explicit paths; PROGRESS.md appended.--## Never blocked--| Blocker | Resolution |-|---|---|-| Unsure what item type the wardrobe supports | The existing catalog is the spec; pick the item type with the most existing examples. |-| Asset creation | The repo's own text-to-3D forge lane can generate a GLB (see the forge surfaces in `STRUCTURE.md`), or build a simple primitive-based accessory in code like existing props. |-| Identity for "once per player" | Use whatever identity the bank balance persists against; it already survives reconnects. |-| Tempted to charge $THREE for it | No. This order is the free souvenir; paid cosmetics stay the boutique's existing catalog. |--## Report format--The item (name, type, size), grant flow as observed including the idempotency rejoin, test output verbatim, files committed.diff --git a/prompts/event/07-preflight-verification.md b/prompts/event/07-preflight-verification.mddeleted file mode 100644index 40a8de2dc..000000000--- a/prompts/event/07-preflight-verification.md+++ /dev/null@@ -1,51 +0,0 @@-# 07 · Event-eve preflight: prove everything works, then stage the ship--**How to run:** paste this whole file into a fresh Claude Code chat in the three.ws repo, or tell the agent to read `prompts/event/07-preflight-verification.md`. Read [00-CONTEXT.md](00-CONTEXT.md) first. Run this LAST, after every other order that is going to land has landed.--**Operating clause:** finish 100%. Never end the session with a question, an unexecuted plan, or "let me know". CLAUDE.md hard rules bind. Two gates apply here and only here: `git push` and the production deploy itself need the owner's go (unless the owner's current instruction is itself that approval). EVERYTHING up to those two commands is yours to finish: fix what the sweeps find, commit it, and stage the ship so each gate is one command.--## Step 0 · Re-derive the current state--```bash-git log --oneline -15-git status --short-cat public/event.json-curl -s https://three.ws/api/version-```--Note which event orders landed (PROGRESS.md) and what is still uncommitted in the shared worktree (do not sweep other agents' files into your commits).--## The sweep, in order--Each stage: run, fix every failure you can root-cause, rerun until green. A failure in code you did not touch still blocks the event; fix it, do not mask it.--1. **Unit + integration:** `npm test` (never piped through `tail`; the vitest stage gates Playwright).-2. **Repo gates:** `npm run gate`, `npm run audit:docs`, `npm run audit:links`.-3. **Local walkthrough:** `npm run dev:walk-all`, then in a real browser the full player journey in the $THREE world: lobby, avatar create, enter, move, chat, emote, store, bank, wheel, jobs board (including any event jobs from order 04), friends, countdown surfaces (01), photo mode (06) if landed. Desktop and 375px. Zero console errors.-4. **Production sweep, unauthenticated:** `npm run audit:web`.-5. **Production sweep, authenticated:** `npm run audit:web:login` (the QA account is `AUDIT_EMAIL`/`AUDIT_PASSWORD` in `.env`).-6. **Production game infra:** confirm the multiplayer host answers (the `game-server` meta in [pages/play.html](../../pages/play.html) names it; a websocket handshake or its health endpoint is proof), and `curl -s https://three.ws/api/healthz`. If anything is degraded, run the gcp-triage skill flow and fix what it allows.-7. **Event config sanity:** `public/event.json` times are the owner-confirmed window, in UTC, start before end, and the live site will serve the NEW config only after deploy: note that explicitly in the report so nobody expects the banner before the ship.-8. **Deploy preflight:** run the `deploy-preflight` subagent. Resolve everything it flags.-9. **Stage the ship:** clean deploy worktree per the CLAUDE.md runbook steps 0 and 1, `npm run build:gcp` green, then STOP. Report the exact two commands the owner runs (or run them if the owner's instruction already granted the ship).--## Definition of done--- [ ] Every stage above green, with the actual command output quoted (trimmed) in the report; no stage skipped silently. If a stage cannot run here (e.g. no browser), say so and what you did instead.-- [ ] Every fix you made committed with explicit paths and honest messages; `git status` shows none of YOUR work uncommitted.-- [ ] The ship is one owner command per gate, and the report says exactly which.-- [ ] PROGRESS.md appended with the go/no-go verdict.--## Never blocked--| Blocker | Resolution |-|---|---|-| A test fails in a subsystem another agent has mid-edit | Root-cause it. If their uncommitted diff is the cause, report the file + failure precisely as in-flight, verify the committed baseline passes (`git stash` is forbidden on a shared tree; test in a clean worktree instead), and continue. |-| Disk full during worktree prep | `npm run clean:worktrees -- --apply` (the runbook's step 0 exists because of this exact failure). |-| gcloud auth or PATH problems | Both are known and solved in the agent memory/runbooks: `export PATH="$HOME/google-cloud-sdk/bin:$PATH"`; reauth is drivable non-interactively. |-| Production log access | `gcloud logging read` recipes are in CLAUDE.md's self-unblock table. |-| An audit finds a defect owned by an unrun event order | Fix it if small; otherwise it goes in the report as a named, sized residual with its owner. Never a vague "some issues remain". |--## Report format--Go/no-go verdict first. Then per stage: command, outcome, fixes made. Then the ship: the staged state and the exact owner commands. Then residuals, each named and sized.diff --git a/prompts/event/08-event-closeout.md b/prompts/event/08-event-closeout.mdindex bf8f0b529..6e528c4b8 100644--- a/prompts/event/08-event-closeout.md+++ b/prompts/event/08-event-closeout.md@@ -1,82 +1,92 @@-# EV-08: Event closeout: freeze the standings, hand off the winners, recap+# EV-08: Event closeout: record what ran, count the souvenirs, recap, retire the pack**How to run this:** paste this whole file into a fresh Claude Code chat opened in`/workspaces/three.ws`, or say "execute `prompts/event/08-event-closeout.md`". Read-[00-CONTEXT.md](00-CONTEXT.md) and `CLAUDE.md` first. Run it AFTER the event window in-`public/event.json` has ended.+[00-CONTEXT.md](00-CONTEXT.md) and `CLAUDE.md` first.++Rewritten 2026-09-01 to its remainder. The original order's first task (freeze the leaderboard+standings before their one-week Redis TTL) can no longer be done: nobody ran it, the board key+`event:lb:three-first-meetup` carried `BOARD_TTL_S = 7d` from its last write+(`api/_lib/event-leaderboard-store.js`), so it expired no later than 2026-08-16 19:30 UTC, and+`app_settings` holds no event, standing, or leaderboard key (verified by a read-only query).+The standings are gone. Say so; do not reconstruct them.## Binding operating clause1. Finish 100%. Never end with a question or an unexecuted plan. Delete this file when the- definition of done is verified and log in [PROGRESS.md](PROGRESS.md); any remainder gets- a follow-up file or an OWNER-ACTIONS row in+ definition of done is verified and log the outcome in [PROGRESS.md](PROGRESS.md); any+ remainder gets a follow-up file or an OWNER-ACTIONS row in[../production-100/OWNER-ACTIONS.md](../production-100/OWNER-ACTIONS.md) first.-2. **No prize is ever paid by code** (order 04's rule stands). Winner settlement is the- owner's; your job is a frozen, durable, correct standings record and the recap.+2. **No prize is ever paid by code.** Winner settlement is the owner's decision, and with the+ board gone it is a decision, not a lookup.3. Hard rules: no mocks, explicit-path commits, no em-dash characters.--## Why this order exists--The leaderboard is a Redis hash with a ONE-WEEK TTL and an in-memory fallback-(`api/_lib/event-leaderboard-store.js`). If nobody exports it, the authoritative record of-who won evaporates seven days after the event. And if the deploy never landed before the-window (the preflight's NO-GO scenario), the closeout must say so honestly rather than-report an empty event as "no participants".+4. The log reads below have a deadline: Cloud Run keeps logs 30 days by default, so the+ multiplayer log lines from the 2026-08-09 window disappear around 2026-09-08. Run them+ first.## Step 0: re-derive the state```bash-curl -s https://three.ws/api/version # did the event ever ship?-curl -s https://three.ws/event.json | head -c 600 # the window that actually ran-curl -s "https://three.ws/api/play/event-leaderboard" | head -c 3000-git log --oneline -5 -- public/event.json # was the window moved?+export PATH="$HOME/google-cloud-sdk/bin:$PATH"+curl -s https://three.ws/api/version # what is live now+curl -s https://three.ws/event.json | head -c 400 # the explicit no-event state+git show 5616ff9b8^:public/event.json # the window that ran: 2026-08-09 17:00 to 19:30 UTC+gcloud run revisions list --service three-ws-api --region us-central1 --project aerial-vehicle-466722-p5 --format='table(name,metadata.creationTimestamp)' | head -20+gcloud run revisions list --service hyperfy-world --region us-central1 --project aerial-vehicle-466722-p5 --format='table(name,metadata.creationTimestamp)' | head -20```-Decide which world you are in: (a) the event ran on production; (b) the deploy landed late-or never, and the event effectively did not happen for visitors. Both worlds get an honest-closeout; (b) also gets a one-line OWNER-ACTIONS note proposing a rescheduled window, since-every surface is date-driven from `public/event.json` and re-running it is config, not code.+If `gcloud` auth is dead, revive it in-session (`gcloud auth login --no-launch-browser` fed+through a fifo; the CLAUDE.md never-blocked table names this) before anything else. This+order is the one case where the cloud read is the deliverable, so route around a dead auth+by reviving it, not by skipping the read.++Decide which world the event happened in from the revision timestamps: (a) the event build+(`2bae5d8c2` or later, per the preflight entry in [PROGRESS.md](PROGRESS.md)) was serving+both the API and the multiplayer server before 2026-08-09 17:00 UTC, so the quests, drop,+and leaderboard were live for visitors; or (b) it was not, and visitors saw the pre-event+world. Both get an honest closeout.## Tasks-1. **Freeze the standings durably.** Read the full leaderboard through the real API and- persist it where event history already lives server-side (`app_settings` keyed by the- event id, following the existing store's shapes). Only rank, display name, runs, and- score cross; account keys never do. If a snapshot mechanism already exists in the store,- use it; do not build a parallel one.-2. **Verify the ended states.** In a real browser: `/event` shows its designed ended state,- the countdown surfaces are unmounted, the in-world event tab behaves per its ended- contract (visible only while a standing exists), and no event job is acceptable- (`pruneClosedEventRuns` did its job). Any violation is a defect: fix it now.-3. **Winner handoff.** Write the top standings, the souvenir grant count, and the peak- population read into a short owner brief appended to [PROGRESS.md](PROGRESS.md), and add- one OWNER-ACTIONS row: announce winners and settle prizes from the board.-4. **Recap the event for holders.** One `data/changelog.json` entry (plain language: what- happened, how many joined, what was dropped). If the owner wants a longer recap doc it- goes in `docs/`; the changelog entry is the mandatory piece.-5. **Retire the pack.** With the closeout done, verify each remaining numbered order in this- pack against its deliverables (the retirement policy in [../README.md](../README.md)) and- delete the ones that are verifiably shipped, logging each in [PROGRESS.md](PROGRESS.md).- The pack's PROGRESS and context files stay until the whole pack retires.+1. **Count what was granted.** The souvenir grant logs one line per attendee in the+ multiplayer service (`souvenir laurel-meetup -> <account>`, format documented in+ `docs/event-souvenirs.md`). Read the window with+ `gcloud logging read 'resource.type="cloud_run_revision" resource.labels.service_name="hyperfy-world" textPayload:"souvenir laurel-meetup"' --freshness=30d --project aerial-vehicle-466722-p5`+ and record the distinct-account count. Read `/population` and event-job completions the+ same way if the lines exist. In world (b) the count is zero by construction; record that.+2. **Write the closeout entry** in [PROGRESS.md](PROGRESS.md): which world, the revision+ evidence, the grant count, the fact that the standings expired unexported and when, and+ the one-line lesson (the export must be a cron or a post-window hook, never a manual+ order). Add one OWNER-ACTIONS row: winners cannot be settled from the board; the owner+ decides whether to settle from the souvenir list, re-run the event, or close it out.+3. **Recap for the community, only if the event ran.** In world (a), one `data/changelog.json`+ entry in plain language (what happened, how many attended, what was dropped), tag+ `feature`. In world (b), no entry; a recap of an event nobody could join would be fake.+4. **Retire the pack.** Verify [02-play-polish-sweep.md](02-play-polish-sweep.md) and+ [06-photo-mode-share.md](06-photo-mode-share.md) against their deliverables (the+ retirement policy in [../README.md](../README.md)); run whichever still has agent-doable+ work, then delete them and this file. Delete the directory when nothing numbered is left+ and record the retirement in [../README.md](../README.md).## Definition of done-- [ ] Standings snapshot persisted server-side and readable after Redis TTL expiry (prove by- reading through the persisted path, not the hash).-- [ ] Ended states verified in a browser; defects found are fixed, not filed.-- [ ] OWNER-ACTIONS row for winner settlement; recap changelog entry written and validated- by `npm run build:pages`.-- [ ] Shipped orders in this pack retired per policy; outcomes logged; this file deleted.+- [ ] World (a) or (b) determined from revision timestamps, not from memory, and recorded.+- [ ] Souvenir grant count (distinct accounts) recorded with the exact log query used.+- [ ] PROGRESS.md closeout entry written; OWNER-ACTIONS row added.+- [ ] Changelog entry present in world (a) and absent in world (b).+- [ ] 02 and 06 either shipped and retired or rewritten to their remainder.+- [ ] `npm run check:rules -- --paths <files you touched>` exits 0.## Never blocked-| Blocker | Resolution |+| Blocker | Resolution (act, do not ask) ||---|---|-| The deploy never landed and the boards are empty | That IS the closeout: record world (b) honestly in PROGRESS, propose the reschedule row, verify the surfaces still fail closed, and retire what genuinely shipped. |-| Redis unreachable from here | The API read path is the contract; if production answers, snapshot from it. If production is down, that is a `gcp-triage` matter first. |-| TTL already expired before you ran | Say so plainly in the brief; check `app_settings` and the game server logs for any partial record; never reconstruct numbers you cannot source. |+| `gcloud` auth dead | Revive it in-session per the CLAUDE.md playbook. If the Workspace reauth policy refuses non-interactively, write the exact commands into the PROGRESS entry, add an OWNER-ACTIONS row for the read, and finish tasks 2 through 4 with the facts you have. |+| Logs already rotated (after about 2026-09-08) | Record that the count is unrecoverable and why, with the retention math. That is a complete answer. |+| `app_settings` schema question | Read-only queries only; this order writes nothing to the database. |## Report format-Which world (a/b), the frozen top standings, souvenir and population figures with their-sources, the changelog entry text, which pack files were retired, and the single owner ask.+World determination with revision names and timestamps; the log query and its distinct+count; the PROGRESS entry text; the OWNER-ACTIONS row text; which of 02 and 06 were run,+retired, or rewritten; the commit SHAs. No trailing questions.diff --git a/prompts/event/PROGRESS.md b/prompts/event/PROGRESS.mdindex 528cd9de5..a225900ee 100644--- a/prompts/event/PROGRESS.md+++ b/prompts/event/PROGRESS.md@@ -131,3 +131,11 @@ Ran as a second pass over what orders 01, 03 and 07 had already landed, verifyin**Blocked on the box, not on the code.**No complete frontend build has succeeded here today. Mine died `EXIT:143` (SIGTERM, killed, not a compile error) after clearing the transform stage, and `/workspaces/.preflight-ship/dist` holds only `chat/`. At the time of writing: load average 176 on 16 cores, 46 of 62 GB used, and a concurrent `npm ci` rewriting the shared `node_modules`. Residual 1 above ("one clean `npm test` is still owed") has the same cause. Whoever runs the ship should expect to retry the build on a quieter box rather than to debug it. `dist/` in the main worktree is currently a half-written build from that kill and should not be trusted or shipped; the deploy runbook builds in its own worktree anyway.++## 2026-09-01 · Retirement sweep: 01, 03, 04, 05, 07 verified shipped and deleted; 08 rewritten to its remainder++Every order was re-measured against the code, the changelog, and production (`ad7b54c16`) rather than against this log. Verified shipped and retired: 01 (`src/game/event-countdown.js` wired at `pages/play.html`, `src/home-event-banner.js` at `pages/home.html`, changelog 2026-08-07), 03 (`pages/event.html`, `src/event-page.js`, `api/play/population.js`, live `/event` 200), 04 (`multiplayer/src/event-window.js`, `event-leaderboard.js`, `api/play/event-leaderboard.js`, `tests/event-quests.test.js` 24 + `tests/event-leaderboard.test.js` 18), 05 (`multiplayer/src/event-drop.js`, `laurel-meetup` in the cosmetics catalog, `public/accessories/laurel-meetup.glb` 68,084 bytes, `docs/event-souvenirs.md`), 07 (ran 2026-08-08, NO-GO recorded above with per-stage evidence).++Still open: 02 (the in-world half of the walkthrough was never done and no defect list exists), 06 (built, never verified on both engines, never announced in the changelog), 08 (rewritten: the leaderboard's Redis record expired about 2026-08-16 with nothing exported, `app_settings` holds no event key, so the standings are unrecoverable; the souvenir grant count is still readable from the multiplayer logs until about 2026-09-08, which makes 08 the first order to run).++Correction to the pack's own dates: the window that actually ran was 2026-08-09 17:00 to 19:30 UTC (`git show 5616ff9b8^:public/event.json`), not 2026-08-08.diff --git a/prompts/event/README.md b/prompts/event/README.mdindex dea62ce99..38ff6847d 100644--- a/prompts/event/README.md+++ b/prompts/event/README.md@@ -1,17 +1,18 @@-# event/ · $THREE Community Day (2026-08-08)+# event/ · $THREE Community Day (window 2026-08-09 17:00 to 19:30 UTC)-Work-order pack for the live community event held in the `/play` world on 2026-08-08. Each numbered file is a self-contained paste-and-run prompt per the [prompts/ standard](../README.md); [00-CONTEXT.md](00-CONTEXT.md) carries the shared facts and MUST be read first by every order.+Work-order pack for the first live community event held in the `/play` world. Each numbered file is a self-contained paste-and-run prompt per the [prompts/ standard](../README.md); [00-CONTEXT.md](00-CONTEXT.md) carries the shared facts and MUST be read first by every order.-| Order | What it ships | Status source |-|---|---|---|-| [01-event-countdown.md](01-event-countdown.md) | Real event times in `public/event.json`, countdown verified on `/play` (lobby banner + in-world pill), extended to the home page | Step 0 of the order |-| [02-play-polish-sweep.md](02-play-polish-sweep.md) | Full UI/UX defect sweep of the `/play` journey: states, a11y, mobile, copy, perceived speed | Step 0 of the order |-| [03-event-landing-page.md](03-event-landing-page.md) | `/event` public landing page: countdown, newcomer guide, local-time schedule + .ics, live section | Step 0 of the order |-| [04-event-quests-leaderboard.md](04-event-quests-leaderboard.md) | Server-authoritative event quest line on the jobs board + live leaderboard (in-world panel + API) | Step 0 of the order |-| [05-event-cosmetic-drop.md](05-event-cosmetic-drop.md) | Free commemorative wearable auto-granted to every attendee during the window | Step 0 of the order |-| [06-photo-mode-share.md](06-photo-mode-share.md) | Photo mode with a branded share card: capture, preview, download, copy | Step 0 of the order |-| [07-preflight-verification.md](07-preflight-verification.md) | The event-eve go/no-go sweep: tests, gates, local + production audits, deploy staged to one owner command. Run LAST | Step 0 of the order |+The event is over and `public/event.json` is back to its explicit no-event state. Five of the eight orders were verified shipped on 2026-09-01 and retired (their files remain readable in git history); what is left is the closeout and two polish orders that were never formally run.-Run order: 01 first (the times feed everything), 02 through 06 in any order as time allows (listed by value), 07 strictly last. Status lives in each order's step 0 and in [PROGRESS.md](PROGRESS.md), never in this table.+| Order | What it ships | State (measured 2026-09-01) |+|---|---|---|+| 01 event countdown | Real event times, countdown on `/play` and the home page | Retired: `src/game/event-countdown.js`, `src/home-event-banner.js`, changelog 2026-08-07 |+| [02-play-polish-sweep.md](02-play-polish-sweep.md) | Full UI/UX defect sweep of the `/play` journey: states, a11y, mobile, copy, perceived speed | Open. The lobby half was verified by the preflight (0 focus rings missing at 130/91 tab stops); the in-world half (store, bank, wheel, jobs, friends, emotes) was never walked and no defect list was produced. |+| 03 event landing page | `/event` with countdown, schedule, .ics, live headcount | Retired: `pages/event.html`, `src/event-page.js`, `api/play/population.js`, changelog 2026-08-08 |+| 04 event quests + leaderboard | Server-authoritative event jobs and a live ranking | Retired: `multiplayer/src/event-window.js`, `event-leaderboard.js`, `api/play/event-leaderboard.js`, 42 tests, changelog 2026-08-08 |+| 05 event cosmetic drop | Free commemorative wearable granted during the window | Retired: `multiplayer/src/event-drop.js`, `public/accessories/laurel-meetup.glb`, `docs/event-souvenirs.md`, changelog 2026-08-08 |+| [06-photo-mode-share.md](06-photo-mode-share.md) | Photo mode with a branded share card: capture, preview, download, copy | Open. Built (`src/game/photo-mode.js`, HUD button, P key) but never verified on both render engines and never announced: no `data/changelog.json` entry exists. |+| 07 preflight verification | The event-eve go/no-go sweep | Retired: ran 2026-08-08, recorded NO-GO with per-stage evidence in [PROGRESS.md](PROGRESS.md) and `docs/event-readiness/LIVE-OPS.md` |+| [08-event-closeout.md](08-event-closeout.md) | The honest closeout: what ran, what was granted, recap, retire the pack | Open, rewritten to its remainder. The leaderboard's Redis record expired about 2026-08-16, so the standings can no longer be exported; the log-derived facts still can, until roughly 2026-09-08. |-Already shipped before this pack existed: the countdown feature itself ([src/game/event-countdown.js](../../src/game/event-countdown.js) reading [public/event.json](../../public/event.json), wired into [pages/play.html](../../pages/play.html)); order 01 verifies it against the real event window rather than building it.+Run order now: 08 first (its log reads have a deadline), then 02 and 06 in either order. When all three retire, the pack retires with them: delete this directory and record it in [../README.md](../README.md) the way retired campaigns are recorded there.