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(prompts): retire the remaining work orders and record why they stay retired
nirholas1ab0f9754011
diff --git a/prompts/finish/309-home-14-reliability-scale.md b/prompts/finish/309-home-14-reliability-scale.mddeleted file mode 100644index 13ae0d30c..000000000--- a/prompts/finish/309-home-14-reliability-scale.md+++ /dev/null@@ -1,148 +0,0 @@-# 14. Reliability and the scale envelope--**How to run this:** paste this whole file into a fresh Claude Code chat opened in-`/workspaces/three.ws`. Read [00-CONTEXT.md](_context/home-00-CONTEXT.md) first. Orders-[02](home-02-bridge-runtime.md), [03](home-03-api-surface.md) and-[13](home-13-observability.md) must have landed.--## Binding operating clause--Finish 100%. Never end with a question or an unexecuted plan. All CLAUDE.md hard rules apply: no-mocks, no fake data, no TODOs, no stubs, no em-dash or en-dash, explicit-path commits, pushes and-production deploys owner-gated.--**Measure, then state. Never assume a number.**-------## Step 0: re-derive the current state--```bash-node -e "import('./api/_lib/home/runtime.js').then(m=>console.log(Object.keys(m)))"-gcloud run services describe three-ws-api --region us-central1 --format=yaml 2>/dev/null | grep -A5 -i "resources\|concurrency\|scal" | head -30-cat docs/ops/gcp-credits-plan.md | head -40-curl -s https://three.ws/api/healthz | head -c 300-```--## The envelope, measured at three volumes--Fill this table with **measured** numbers and publish it in `docs/home-operations.md`. Every cell-that says "assumed" is an unfinished line.--| Volume | Connections per instance | Heap | p95 action | Behaviour |-|---|---|---|---|---|-| 10 homes | | | | everything inline, nothing to tune |-| 1,000 homes | | | | |-| 100,000 homes | | | | |--Measure the first two for real. For the third, measure the per-connection cost precisely and-extrapolate honestly, naming the extrapolation and its assumptions. A measured unit cost plus a-stated model is engineering; a guessed total is not.--The unit costs that matter, each measured:--- Heap per idle connection, and per connection for a large house (500+ entities).-- CPU per state burst of 100 entity updates.-- Socket count and file-descriptor headroom per instance.-- SSE stream cost per subscriber, separate from connection cost.-- Cold-start time to first connected home on a fresh instance.--## Backpressure and degradation, in order--The system must degrade in latency and features, never in correctness and never in safety. Write-the ladder down and implement it:--1. Under the per-instance cap: normal.-2. At the cap: new acquisitions get a short-lived unpooled connection. Slower, correct.-3. Under DB pressure: reads serve from the in-memory graph; writes still go through, because a- write is somebody pressing a button.-4. Under severe load: SSE stream admission is limited before action admission is. **A user who- asks to unlock a door gets served before a user who is watching a dashboard.**-5. Beyond that: `503` with `retry-after` and a designed UI state. Never a silent hang, never a- half-applied action.--**The gate never degrades.** No load condition may cause a guarded action to skip a confirmation.-If shedding load would require weakening the gate, shed the action instead and say so.--## Chaos: the seven failures, each run for real--| # | Failure | Injected how | Must |-|---|---|---|---|-| 1 | House goes offline mid-session | stop the container | stale not empty, recovers on restart with no reload |-| 2 | House flaps (up, down, up) every 5 s for 2 minutes | a loop against the container | the breaker damps it; no alert storm; no socket leak |-| 3 | Token revoked while connected | delete the token in Home Assistant | connection moves to `auth_failed` with the real reason; the user is told to reconnect |-| 4 | Our instance recycled mid-stream | `docker restart` the API, or SIGTERM the process | streams reconnect client-side; sockets closed cleanly on the house's side |-| 5 | Database unavailable | point `DATABASE_URL` at a dead host | reads degrade to the in-memory graph, writes fail with a designed error, no crash loop |-| 6 | Slow house (2 s per response) | a latency shim in front of the container | timeouts bound it; one slow house does not slow others; prove isolation |-| 7 | 500-entity house with a 10-per-second update rate | the demo integration plus a generator | frame budget held in the UI, coalescing works, heap flat |--Failure 6 is the one that finds shared-resource bugs. Run it with a second, fast house connected-and prove the fast one is unaffected.--## Cloud Run configuration--Read `docs/ops/gcp-production.md` and `docs/ops/gcp-credits-plan.md` before changing anything.-CLAUDE.md pre-approves config-only `gcloud run services update` changes; a deploy is still-owner-gated.--Decide and justify, with the measured number behind each:--- Concurrency per instance (the current value, and whether long-lived SSE streams change it).-- Memory limit, from the measured heap plus headroom.-- Whether this lane needs a `minScale` above zero, and the honest cost of saying yes. Default is- no: the pool is a cache, cold starts are sub-second, and paying to keep sockets warm is a- decision that needs a measured latency complaint behind it.-- CPU throttling behaviour with an idle SSE stream open, which is the setting most likely to be- wrong for this workload. Test it, do not reason about it.--## Tasks--| # | Task |-|---|---|-| 1 | A load harness that opens N real connections against N real Home Assistant containers (or one instance with N tokens, stated either way). `scripts/home-load.mjs`. |-| 2 | Measure every unit cost above. Record the raw output in `tasks/home/` as evidence, the way `tasks/sim-readiness/` does. |-| 3 | Implement the backpressure ladder. |-| 4 | Run all seven chaos scenarios and fix what they break. |-| 5 | Decide and apply the Cloud Run configuration, with the justification. |-| 6 | Publish the envelope table in `docs/home-operations.md`. |--## Definition of done--- [ ] The envelope table has measured numbers for 10 and 1,000 homes and a stated extrapolation for 100,000. No cell says "assumed".-- [ ] Every unit cost measured, with the raw evidence file committed under `tasks/home/`.-- [ ] All seven chaos scenarios run, with a transcript each, and every failure they exposed fixed.-- [ ] Scenario 6 proves isolation: the fast house's p95 is unchanged with a slow house connected. Paste both numbers.-- [ ] The backpressure ladder is implemented and each rung is demonstrated, including that action admission survives longer than stream admission.-- [ ] A load test proves the gate never degrades: guarded actions under saturation still require confirmation. Assert it.-- [ ] The Cloud Run configuration decision is written down with its measured justification, including the CPU-throttling test result.-- [ ] `npx vitest run --root .` shows no new failures.-- [ ] `npm run audit:docs` clean, `npm run check:rules -- --paths <your files>` clean.--## Never blocked--| Blocker | Do this |-|---|---|-| Cannot run 1,000 Home Assistant containers | You do not need to. Measure the per-connection cost precisely with 10 to 50 real ones, then drive the pool with a protocol-level load generator for the connection count. State exactly which part was real and which was generated. |-| The 100,000 number needs a distributed design | Then say so, with the measured point where the single-instance model breaks and what the next architecture is. An honest ceiling with a named successor beats a fabricated capacity. |-| Tempted to raise `minScale` to fix a cold start | Measure the cold start first. Sub-second is fine and free. Credits are approved for quality, but paying to hide a problem you have not measured is not quality. |-| A chaos scenario reveals a bug in `packages/home-bridge` | Fix it there, add a test there, and per the CLAUDE.md open-source rule, upstream anything that belongs to `home-assistant-js-websocket`. |-| The load harness would hammer a third party | It must only ever point at your own containers. Never load-test somebody's house. |--## Report format--1. The completed envelope table with its evidence file path.-2. Every unit cost with how it was measured.-3. Seven chaos transcripts and every fix made.-4. The isolation numbers from scenario 6.-5. The backpressure demonstration, rung by rung.-6. The Cloud Run decision and its justification.-7. Anything in this file you found to be wrong, and what you changed it to.--## Retire this prompt when it is done (required)--Verify every line against real output, append to `prompts/finish/_context/home-PROGRESS.md`, commit with-explicit paths, and delete this file in that commit:-- git rm prompts/finish/309-home-14-reliability-scale.md--Never delete it on a partial.diff --git a/prompts/finish/908-backlog-09-telegram-bots-durability.md b/prompts/finish/908-backlog-09-telegram-bots-durability.mddeleted file mode 100644index 545def99e..000000000--- a/prompts/finish/908-backlog-09-telegram-bots-durability.md+++ /dev/null@@ -1,205 +0,0 @@-# 09. Telegram feed bots: durable hosting for both channels--Read [00-INDEX.md](_context/backlog-00-INDEX.md) first.--> **Commit gate.** These bots track a launchpad other than `$THREE`. The code-> lives in a different repo (`nirholas/pump-fun-sdk`), so nothing here should land-> in three.ws without owner approval. Build and deploy freely; ask before-> committing anything that names the launchpad into this repo.--## Status: both feeds live and hardened, re-verified 2026-09-09--The 2026-09-02 pass declared this done. It was half true. Re-measuring on-2026-09-09 found the graduation tracker healthy and **the all-claims firehose-silently dead**: 99 hours of uptime, `mode: websocket`, and zero events.--Root cause: `rpc.magicblock.app` went key-gated. It now answers `401` on the-WebSocket upgrade and `{"error":"invalid api key"}` over HTTP, and it was the-firehose's only WebSocket endpoint *and* its primary RPC. The 2026-08-01 note-below calling it a working free endpoint is what stopped being true.--Why it stayed invisible for four days is the part worth keeping: **subscribing-cannot fail loudly.** web3.js returns a subscription id immediately and retries-the socket internally, so `startWebSocket()` resolved, `transport` was set to-`websocket`, and `/stats` reported a healthy feed. The 90-second silence-heartbeat did fire, but its reconnect rebuilt the same dead endpoint, so the-watchdog looped instead of escaping. Nothing in the metrics distinguished a-connected socket from a refused one.--Both halves are fixed and deployed.--| Feed | Cloud Run service | Revision | Transport | Measured 2026-09-09 |-|---|---|---|---|---|-| Graduation and migration tracker | `pumpfun-channel-bot` | `-00006-wp4` | websocket on `solana-rpc.publicnode.com` | 156 events in 3m17s, `degraded: false`, delivery `ok` |-| All-claims firehose | `pumpfun-allclaims-bot` | `-00010-bdc` | websocket on `solana-rpc.publicnode.com` | 745 claims and 242,207 WS events in 23m, 145 instant posts, 23 digests, **0 post failures** |--Both `Ready=True`, pinned singletons (`minScale=1`, `maxScale=1`) on the-`three-ws@` runtime SA, each with its own bot token in its own Secret Manager-secret and its own numeric channel id (`-1003965305979`, `-1003905427189`).--The firehose recovered the moment its endpoints were repointed: 62 claims in the-first two minutes, against the ~20 claims/min baseline this order set.--### The config fix (immediate)--Both services were repointed off magicblock onto endpoints verified keyless and-streaming the same day: `solana-rpc.publicnode.com`, `api.mainnet-beta.solana.com`-(HTTP and WS), and `solana.leorpc.com/?api_key=FREE` (HTTP only; its WS refuses).-`drpc.org` and `rpc.ankr.com` are no longer keyless either and were rejected.--A trap this exposed: `deploy-cloudrun.sh` ships env from `.env` via-`--env-vars-file`, which **replaces the whole set**. The local `.env` still held-the magicblock config, so the next deploy would have silently re-broken the feed.-`recover-env.sh` now regenerates it from the corrected live revision, and both-`.env` files carry the new endpoint lists.--### The code fix (so this class of outage cannot hide again)--Landed in the sibling repo at `2a12ec3a`, canonical copy first and propagated to-`channel-bot`, per the rule in its own `DECODERS.md`:--- **A WebSocket endpoint list, not one endpoint.** `SOLANA_WS_URLS` is- comma-separated, and whatever the RPC list implies is appended, so there is- always somewhere to fail over to. The firehose now runs with 5 resolved.-- **Liveness is proven by traffic, not by a subscription id.** A new- subscription must deliver a real log event within 20 seconds or the endpoint is- rejected and the next one tried. The monitored programs emit thousands of- events a minute, so silence that long means the endpoint, not the chain.-- **Reconnects rotate** instead of retrying the endpoint that just went quiet.-- **The heartbeat timer is cleared before it is re-armed.** Every reconnect since- this code was written had been stacking another interval.-- **`/stats` exposes `activeWs` and `wsEventsReceived`,** so a WebSocket carrying- no traffic is visible rather than indistinguishable from a healthy one.-- `channel-bot`'s live feed runs on `event-monitor.ts`, not the claim monitor, so- the rotation was applied there too rather than only to the shared decoder path.--Verified by running the monitor against the dead endpoint first: it rejected-magicblock, settled on `solana-rpc.publicnode.com`, and reported 9,773 events.-Covered by `src/__tests__/ws-urls.test.ts` in both bots (7 cases, including the-regression that a single explicit endpoint must never de-duplicate down to a-single point of failure). Suites green: 95 tests allclaims, 205 channel-bot.--Deliberately not done: neither bot has a persistent volume, so tracker state is-ephemeral and a redeploy resets it. That is pre-existing, was true before this-pass, and mounting one is a separate change.--### Standing observation, not a failure--`queueDrops` sits at 53 on the firehose (~0.9% of pipeline claims). That is the-RPC queue's designed backpressure, and the levers are queue capacity and endpoint-count. The 2026-08-02 baseline of zero drops was a 3h43m measurement, not a-contract.--## The work---1. **Deploy both to Cloud Run.** `channel-bot/deploy-cloudrun.sh` exists and is the- template. Write the equivalent for the all-claims package. Pin the- `three-ws-build@` and `three-ws@` service accounts.--2. **Never use `--set-env-vars` for these.** Their config breaks the flag: the RPC- URL list contains commas and the channel id can contain `@`, so neither the- default separator nor the `^@^` alternate delimiter is safe. `deploy-cloudrun.sh`- writes a YAML env file instead. Do the same for the second bot.--3. **Keep the bot identities separate.** Each feed has its own bot and its own- channel. Reusing one token across both is unsupported and crosses the feeds.- Put the **numeric `-100…` chat id** in `CHANNEL_ID`, never the handle: the- shared `t.me` link is not always the username, and `getChat?chat_id=@handle`- returns `chat not found` even with the bot already an admin. Recover the real- id from `getUpdates?allowed_updates=["my_chat_member"]`, whose promotion event- carries the chat id, username, and full admin rights object.--4. **Keep websockets, do not fall back to polling, and configure more than one.**- `getSignaturesForAddress` limit-20 per 30s against the program samples a- handful of valid transactions per minute out of thousands, so events get- missed entirely. WS is enabled when `SOLANA_WS_URL` or `SOLANA_WS_URLS` is- set. **`wss://rpc.magicblock.app/mainnet` is dead as of 2026-09-09**: it went- key-gated and answers 401 on the upgrade. Do not re-add it. Keyless and- verified streaming that day: `wss://solana-rpc.publicnode.com` and- `wss://api.mainnet-beta.solana.com`. The three.ws Helius key is plan-exhausted- and its WS handshakes 429 forever, so do not point these at it.-- Always set `SOLANA_WS_URLS` with at least two. A single endpoint is a single- point of failure, and the failure is silent: see the status section above.--5. **Sync the stale decoders.** `@pumpkit/core` and `@pumpkit/channel` are March- snapshots missing the post-2026-05-21 V2 layouts (quote-mint claims, lifetime- claimed, fake social-claim detection). The current decoder lives in- `channel-bot/src/claim-monitor.ts`. Either sync pumpkit from it or make every- future bot copy from channel-bot, and write down which, because this trap has- already been hit once.--6. **Process hygiene for whoever debugs this next.** The bot's cmdline is- `node dist/index.js` (relative), so `pkill -f "channel-bot/dist/index.js"`- silently matches nothing. Match on cwd via `/proc/<pid>/cwd`, and never kill a- same-named process whose cwd is `/workspaces/three.ws`.--## Verify--Both services are private, so a stats read needs an identity token:--```sh-P=aerial-vehicle-466722-p5-for S in pumpfun-channel-bot pumpfun-allclaims-bot; do- curl -s -H "Authorization: Bearer $(gcloud auth print-identity-token)" \- "$(gcloud run services describe "$S" --region us-central1 --project "$P" \- --format='value(status.url)')/stats"-done-```--`localhost:3900` and `localhost:3901` only answer when a bot is running locally-as a fallback, which is no longer the normal state. If a local run is needed,-restore its config first with `./recover-env.sh` from the bot's directory: the-gitignored `.env` does not survive a codespace rebuild.--Baseline for the firehose once live: roughly 20 claims/min detected, digest every-60s, zero post failures. Flood control matters: Telegram caps around 20 posts/min-per channel, so large claims post individually and the rest batch into a digest,-with a sliding-window budget reserving one slot for the digest.--## Definition of done--- [x] Both bots run on Cloud Run, surviving a codespace rebuild. Proven by the- 2026-09-02 rebuild: both local processes died, both services stayed up.-- [x] Each uses its own token and numeric channel id, verified by live posts to- distinct `-100...` ids (145 instant posts and 23 digests on the firehose in- the 23 minutes after the fix, 0 post failures).-- [x] WS mode confirmed active on both, with event rates recorded above.- Re-measured 2026-09-09 after the firehose was found silent for four days:- both now carry traffic on `solana-rpc.publicnode.com`, and `/stats`- reports `activeWs` so a dead socket is visible rather than reported as- healthy.-- [x] A dead WebSocket endpoint can no longer flatline a feed: endpoint lists,- a traffic-based liveness check, rotating reconnects, and the metrics to- see it, committed in the sibling repo at `2a12ec3a` and deployed- (`pumpfun-allclaims-bot-00010-bdc`, `pumpfun-channel-bot-00006-wp4`).-- [x] The decoder sync decision is made, executed, and written down in- `DECODERS.md` at the sibling repo root: the all-claims copy is canonical,- nothing was refactored into a shared package, and the two stale copies are- marked do-not-copy. Its rule for future bots is to copy that file and its- test together.-- [x] A README in each bot directory documents deploy, env, and revival, now- including `recover-env.sh`.-- [ ] Owner approval to commit this file's update into three.ws. Nothing else- here needs it: the code landed in the sibling repo, which the gate at the- top of this file exempts.--## Retire this prompt when it is done (required)--1. Verify every Definition of done line against actual command output in front- of you. Never claim a line you did not verify.-2. Record the outcome in this campaign's PROGRESS or INDEX file if it has one.-3. Commit with explicit paths and a subject that describes the diff (house- style: type(scope): what changed and why a reader cares), and delete this- prompt file in that same commit:-- git rm prompts/finish/908-backlog-09-telegram-bots-durability.md-- A finished order left on disk reads as open work to the next agent, so the- shrinking directory is the campaign's progress ledger.--If a line genuinely cannot pass inside this session (an external party must-respond, or an owner-gated action is the final step), finish everything else,-leave this file in place, and state exactly which line remains and who owns it.-Never delete this file on a partial.diff --git a/prompts/finish/909-backlog-10-x402scan-listing.md b/prompts/finish/909-backlog-10-x402scan-listing.mddeleted file mode 100644index 34770dbb4..000000000--- a/prompts/finish/909-backlog-10-x402scan-listing.md+++ /dev/null@@ -1,135 +0,0 @@-# 10. Finish the x402scan listing--Read [00-INDEX.md](_context/backlog-00-INDEX.md) first.--> **Commit gate.** This touches a third-party registry. Any commit into three.ws-> whose diff names it needs owner approval first.--## Where this stands (re-measured 2026-09-02)--The indexer lists settlements per facilitator address from a registry in the-upstream repo. Our self-hosted Solana facilitator settles from fee payer-`WwwuGbqHrwF5RG89KhUbmRWEvjnRH9k5kVM5p7T3WwW`.--**The facilitator listing is done and live.** PR #1032 **merged 2026-08-11**-with no review requested, so the reviewer-verification comment that blocked-this for six weeks was never needed and is now moot. Measured the same day, all-without credentials:--| Fact | Value | How it was read |-|---|---|---|-| PR #1032 | `MERGED` 2026-08-11T20:01:45Z, 4 commits, 0 reviews | `gh pr view 1032 --repo Merit-Systems/x402scan` |-| Facilitator page | live, both fee payers rendered | `https://www.x402scan.com/facilitator/three-ws` |-| Attribution | 18,636 transactions, $1,055.01 USDC, latest settle same day | that page's payload |-| Origin listing | 60 resources, none deprecated, re-crawled by them 2026-08-27 | `https://www.x402scan.com/server/17cbd874-52ac-4920-a020-b22ff2489a07` |-| Discovery crawl | 46 pages, 4,519 items, `total` stable, 0 duplicate identities | their `listAllFacilitatorResources` replayed against production |-| Config URLs | `/supported` 200, logo 200, `docsUrl` 200 | `curl` |-| CDP Bazaar | three.ws in 0 of 15,127 catalog resources | full paged sweep of the CDP catalog |--Solana settlement is unchanged and still self-hosted. Nothing in this arc has-re-pointed, demoted, or touched the Solana rail, and nothing here should.--## What the re-verify found, and what it fixed--Their registration flow reads **`/openapi.json`**, not the facilitator catalog-(their facilitator crawl is still paused upstream: `FACILITATOR_SYNC_PAUSED =-true` in `apps/scan/src/app/api/resources/sync/route.ts`, re-checked-2026-09-02). That document hand-enumerated 24 of the 75 live paid services, so-52 endpoints answered a spec-valid 402 in production while being impossible to-register. That is why the origin has sat at 60 resources since 2026-07-11.--Fixed in the tree, not yet deployed: `catalogPaidPaths()` in-[api/openapi-json.js](../../api/openapi-json.js) projects every live paid-service from `api/_lib/service-catalog/` into the document, spread before the-hand-authored paths so the 24 richer entries keep their exact wording.-`/api/x402/*` operations went 24 → 79, with zero change to any existing path.-Five guards in [tests/openapi-aggregator.test.js](../../tests/openapi-aggregator.test.js)-keep it from reopening.--## What remains (re-measured 2026-09-09)--1. ~~**Deploy.**~~ **Done.** The `/openapi.json` fix shipped on 2026-09-08- (production `880bdcef8`, revision `three-ws-api-00418-j26`). The document now- declares **82** paid `/api/x402/*` paths, not 24.-2. **Register the missing resources** (owner: one SIWX wallet signature, no- funds move). This is the ONLY remaining step. Run- `npm run preview:x402scan-registration` first: it reproduces x402scan's- classify/probe/deprecate pipeline against live production and, on 2026-09-09,- reported 123 registrable endpoints declared, 63 already listed, **60 rows- added and 0 deprecated**, with 59 of the 60 answering a spec-valid 402 to a- bare probe. The zero is the safety property, so re-run the preview- immediately before signing and stop if it is no longer zero. Then use "Add- API" for origin `https://three.ws` at- <https://www.x402scan.com/resources/register>. Wallet sign-in is a signature,- not a spend, but it binds an identity: render what is being signed and get an- owner yes.-3. **The "five blocked endpoints" line was wrong and is retired.** Re-probed- 2026-09-09: `dance-tip`, `feed-health` and `spend-session` all answer a- spec-valid 402 advertising USDC and $THREE on Solana mainnet, so they are- probe-registerable today. The sponsor floor bites at settle time, not at- challenge time (`/api/healthz` reports `x402.self_facilitator.settle` at- 84 ok / 366 failed, every failure `fee_wallet_below_floor`), which stays work- order 01's capital problem. `ring-settle` and `three-buy` also answer 402 but- are `discoverable: false` internal ring machinery, deliberately absent from- the service catalog so `catalogPaidPaths()` never projects them. Listing them- would let dogfooded volume masquerade as organic demand. **Leave them out.**- One endpoint genuinely will not probe-register and should not: `GET- /api/x402/vanity-premium` browses the inventory for free and only- `?address=<base58>` triggers the 402, so their required-params-only probe- sees the free mode. Marking `address` required would be a lie about the route.-4. **Optional Base leg.** three.ws is in none of the CDP Bazaar's 15,127- resources, exactly as documented: indexing is triggered by a settle through- the CDP facilitator on Base, and production has no `X402_BUYER_PRIVATE_KEY`- to pay from. It is a nice-to-have. **Never re-point Solana settlement to a- third-party facilitator for visibility.** Listing is additive, Solana stays- self-hosted, and an EVM-only directory is a footnote, not a goal.--## Verify--```sh-gh pr view 1032 --repo Merit-Systems/x402scan --json state,mergedAt-curl -s https://three.ws/api/x402-facilitator/discovery/resources \- | python3 -c "import json,sys; d=json.load(sys.stdin); print(d['pagination']['total'], 'resources')"-curl -s https://three.ws/openapi.json \- | python3 -c "import json,sys; p=json.load(sys.stdin)['paths']; print(len([k for k in p if k.startswith('/api/x402/')]), 'paid paths')"-npm run preview:x402scan-registration-npx vitest run tests/openapi-aggregator.test.js tests/service-catalog.test.js-```--The third command read 24 before the 2026-09-08 deploy and reads 82 now. The-fourth is the one to trust before spending the signature: it must report 0 rows-would be deprecated.--## Definition of done--- [x] PR #1032 state re-read and reported: merged 2026-08-11, attribution live.-- [x] The verification comment is moot; the PR merged without it.-- [x] The discovery endpoint's live output matches what the PR registers,- proven by replaying their own crawler against production.-- [x] Solana settlement unchanged and still self-hosted.-- [x] The deploy landed 2026-09-08; `/openapi.json` declares 82 paid paths.-- [x] Registration preview built and validated against x402scan's own discovery- library (`npm run preview:x402scan-registration`): 60 rows added, 0- deprecated, 59/60 probe-valid.-- [ ] Origin registration: **owner-gated**, one SIWX wallet signature and- nothing else. Re-run the preview immediately before signing.-- [x] [PROGRESS.md](_context/backlog-PROGRESS.md) updated.--## Retire this prompt when it is done (required)--1. Verify every Definition of done line against actual command output in front- of you. Never claim a line you did not verify.-2. Record the outcome in this campaign's PROGRESS or INDEX file if it has one.-3. Commit with explicit paths and a subject that describes the diff (house- style: type(scope): what changed and why a reader cares), and delete this- prompt file in that same commit:-- git rm prompts/finish/909-backlog-10-x402scan-listing.md-- A finished order left on disk reads as open work to the next agent, so the- shrinking directory is the campaign's progress ledger.--If a line genuinely cannot pass inside this session (an external party must-respond, or an owner-gated action is the final step), finish everything else,-leave this file in place, and state exactly which line remains and who owns it.-Never delete this file on a partial.diff --git a/prompts/finish/910-backlog-07-bnb-testnet-deploys.md b/prompts/finish/910-backlog-07-bnb-testnet-deploys.mddeleted file mode 100644index 980c46870..000000000--- a/prompts/finish/910-backlog-07-bnb-testnet-deploys.md+++ /dev/null@@ -1,95 +0,0 @@-# 07. Deploy the two finished testnet contracts--Read [00-INDEX.md](_context/backlog-00-INDEX.md) first.--> **Commit gate.** This work order and its deliverables reference a chain other-> than Solana. Per CLAUDE.md, any commit whose diff references a crypto project-> other than `$THREE` needs explicit owner approval before staging. Build freely;-> ask before committing.--## What is wrong--`GreenfieldVault` and `WorldMoves` are code-complete and dry-run verified, and-neither has ever been deployed publicly. Every proof in the retired campaign ran-against an anvil fork or a local instance because no funded deployer key exists:-`BNB_TESTNET_DEPLOYER_KEY` is absent from the shell env, the root `.env`, and-`contracts/.env`, and the public faucet is reCAPTCHA-gated so an agent cannot-self-serve it.--No code change is needed. The moment the addresses exist,-`/api/bnb/world-config` starts returning `deployed: true` for real visitors and-the sender, reader, and ghost paths light up as already proven.--Full history: [../bnb-chain/PROGRESS.md](../bnb-chain/PROGRESS.md). Deploy-addresses and script names: [../../contracts/DEPLOYMENTS.md](../../contracts/DEPLOYMENTS.md).--## The work--1. **Re-verify the dry runs still pass** against the current tree before asking- for anything. A stale claim of "ready to deploy" is worse than no claim.- ```sh- cd contracts- forge script script/DeployGreenfieldVault.s.sol- forge script script/DeployWorldMoves.s.sol- ```--2. **Owner action, one funded key.** Fund a throwaway EOA at- `https://www.bnbchain.org/en/testnet-faucet` (reCAPTCHA, so a human must do- it), then set `BNB_TESTNET_DEPLOYER_KEY` in `contracts/.env`.- `GREENFIELD_VAULT_OPERATOR_KEY` falls back to the same key.--3. **Deploy, then wire the address.** Deploying to a public testnet spends funds- from a key: render the network, the deployer address, and the estimated cost- and get an explicit owner yes first (stop-and-ask gate 1).- ```sh- forge script script/DeployGreenfieldVault.s.sol --broadcast- forge script script/DeployWorldMoves.s.sol --broadcast- ```- Then set `WORLD_MOVES_ADDRESS_TESTNET` on the service with- `--update-env-vars` and confirm:- ```sh- curl -s https://three.ws/api/bnb/world-config | python3 -m json.tool- ```--4. **Prove the read and write paths against the real deployment**, not the fork.- Every path the campaign proved locally gets one live re-run, and the evidence- goes in [PROGRESS.md](_context/backlog-PROGRESS.md) with transaction hashes.--5. **Update `contracts/DEPLOYMENTS.md`** with the live addresses, the network, the- deploy block, and the verification link.--## Keep Solana first--This is an additive testnet surface. It does not change where the platform lives.-Do not re-point, migrate, or de-prioritize any Solana infrastructure as part of-this work, and lead your report with the Solana position if you touch anything-shared.--## Definition of done--- [ ] Both dry runs re-verified green against the current tree.-- [ ] Both contracts deployed with transaction hashes recorded.-- [ ] `WORLD_MOVES_ADDRESS_TESTNET` set; `/api/bnb/world-config` returns- `deployed: true` to an anonymous caller.-- [ ] Sender, reader, and ghost paths exercised against the live deployment.-- [ ] `contracts/DEPLOYMENTS.md` updated.-- [ ] Owner approval obtained before any commit containing this content.--## Retire this prompt when it is done (required)--1. Verify every Definition of done line against actual command output in front- of you. Never claim a line you did not verify.-2. Record the outcome in this campaign's PROGRESS or INDEX file if it has one.-3. Commit with explicit paths and a subject that describes the diff (house- style: type(scope): what changed and why a reader cares), and delete this- prompt file in that same commit:-- git rm prompts/finish/910-backlog-07-bnb-testnet-deploys.md-- A finished order left on disk reads as open work to the next agent, so the- shrinking directory is the campaign's progress ledger.--If a line genuinely cannot pass inside this session (an external party must-respond, or an owner-gated action is the final step), finish everything else,-leave this file in place, and state exactly which line remains and who owns it.-Never delete this file on a partial.diff --git a/prompts/finish/_context/00-RETIRED-BY-OWNER.md b/prompts/finish/_context/00-RETIRED-BY-OWNER.mdnew file mode 100644index 000000000..b6593205f--- /dev/null+++ b/prompts/finish/_context/00-RETIRED-BY-OWNER.md@@ -0,0 +1,69 @@+# Retired by the owner, 2026-09-09++The owner directed that every remaining work order in `prompts/finish/` be retired, after being+told which ones their lane ledgers still called open or owner-gated. This file is the record, so+nobody restores them a fourth time.++**Do not restore these files.** An earlier restore (`9815c2410`) was correct at the time: it+reversed a by-number sweep the owner had not asked for. This retirement is the owner's own call,+made with the open-state evidence in front of them.++## What is not lost++The work orders were instructions, not state. Every open item they tracked survives in this+directory, which is untouched:++- [backlog-00-INDEX.md](backlog-00-INDEX.md): the owner action blocking each backlog item.+- [production-100-OWNER-ACTIONS.md](production-100-OWNER-ACTIONS.md): the numbered owner rows.+- [home-PROGRESS.md](home-PROGRESS.md): the home campaign state table and every finished entry.+- [okx-ai-README.md](okx-ai-README.md), [roadmap-00-README.md](roadmap-00-README.md),+ [gcp-credits-README.md](gcp-credits-README.md),+ [openai-pr-00-START-HERE.md](openai-pr-00-START-HERE.md) and+ [fix-queue-00-INDEX.md](fix-queue-00-INDEX.md): the same, per lane.++The `../NNN-*.md` links in those files now point at retired orders. That is expected drift, and+`scripts/audit-docs.mjs` skips the `prompts` tree, so it is not a gate failure.++## Recovering one, if a running session still needs its text++The parent commit of the retirement holds every one of them:++ git show 5b7c292ca:prompts/finish/<name>.md++## The 30 orders retired++Home campaign (the state table in `home-PROGRESS.md` remains the record of what is still open):++- `302-home-05-connect-flow.md`+- `303-home-06-3d-home-scene.md`+- `304-home-07-floorplan-editor.md`+- `305-home-08-voice-loop.md`+- `306-home-09-wyoming-satellite.md`+- `307-home-10-addon-relay.md`+- `308-home-11-security.md`+- `309-home-14-reliability-scale.md`+- `310-home-16-test-program.md`+- `311-home-17-a11y-i18n-mobile.md`+- `313-home-19-plans-entitlements.md`+- `314-home-20-launch-readiness.md`++Campaign-level orders:++- `900-swarm-100-sweep-console.md`+- `901-production-100-01-ship-readiness.md`+- `902-backlog-01-x402-settle-runway.md`+- `903-production-100-04b-fact-check-publish-run.md`+- `904-gcp-credits-05-catalog-animation-seeding.md`+- `905-fix-queue-03-cron-drift-garment-sweep.md`+- `906-backlog-05-r2-bucket-cors.md`+- `907-backlog-08-okx-chat-bot-always-on.md`+- `908-backlog-09-telegram-bots-durability.md`+- `909-backlog-10-x402scan-listing.md`+- `910-backlog-07-bnb-testnet-deploys.md`+- `911-okx-ai-08-forge-relisting.md`+- `913-okx-ai-04-e2e-real-payment-test.md`+- `914-okx-ai-07-final-audit-and-watch.md`+- `915-openai-pr-07-final-verification-and-submit.md`+- `916-roadmap-native-widgets.md`+- `917-roadmap-pumpfun-trading.md`+- `918-roadmap-pumpfun-trading-arena.md`diff --git a/prompts/finish/_context/backlog-00-INDEX.md b/prompts/finish/_context/backlog-00-INDEX.mdindex a24ad0eb9..9a8e8977e 100644--- a/prompts/finish/_context/backlog-00-INDEX.md+++ b/prompts/finish/_context/backlog-00-INDEX.md@@ -43,7 +43,7 @@ observable health, so 01 to 03 come first.| 01 | [x402 settle: clear `fee_runway_exhausted`](../902-backlog-01-x402-settle-runway.md) | **the deploy landed 2026-09-08**; one capital decision left (re-measured 2026-09-09: `fee_runway_exhausted` is gone, the hard SOL floor is the constraint) | pick one: release the **0.0558 SOL the platform already owns** but has fenced behind `pump-x402-launcher`'s 0.1 SOL `minSol` (the ring payer is 0.0012 SOL short), or send SOL to the economy master. Either moves funds, so either is gate 1 || 05 | [R2 bucket CORS: verify, then fix at the origin](../906-backlog-05-r2-bucket-cors.md) | one credential (re-measured twice on 2026-09-09, both bucket-origin surfaces still fail) | mint an R2 "Admin Read & Write" token for `chatty-storage`. The storage outage that briefly gated this (`S3_SECRET_ACCESS_KEY`) recovered the same day, so this is the only step left || 07 | [BNB testnet: deploy the two finished contracts](../910-backlog-07-bnb-testnet-deploys.md) | one funded EOA | send tBNB to `0x1C4918894dfA5eE11cfF9629B458b5169Cfa3871` (faucet is reCAPTCHA-gated) |-| 08 | [OKX chat bot: move off the codespace](../907-backlog-08-okx-chat-bot-always-on.md) | **deployed 2026-09-04**; only the reply lane is blocked | clear the GCP billing hold so the bot can author replies |+| 08 | [OKX chat bot: move off the codespace](../907-backlog-08-okx-chat-bot-always-on.md) | **deployed 2026-09-04** and still beating (re-measured 2026-09-09 from `bot_heartbeat`, no `gcloud` needed); only the reply lane is blocked, and the AI-lane chain committed the same day has not shipped | two: clear the GCP billing hold (it also restores the platform Vertex anchor, `LLM providers DOWN` x657), and deploy `workers/okx-chat-bot/cloudbuild.yaml` so a funded lane can actually be elected || 09 | [Telegram bots: durable hosting for both feeds](../908-backlog-09-telegram-bots-durability.md) | **done**; the firehose was found silently dead on 2026-09-09 (dead RPC), fixed and hardened the same day | clear the commit gate on its file update || 10 | [x402scan listing: finish the last three steps](../909-backlog-10-x402scan-listing.md) | **the deploy landed 2026-09-08**; only the origin registration is left (re-measured 2026-09-09) | one SIWX wallet signature at x402scan `/resources/register` for origin `https://three.ws`; no funds move |