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
prompts(triage): track Birdeye compute-unit exhaustion as owner row 53, confirm deploy gap and CoinGecko no-op unchanged
nirholas4d7dd5991bfc
diff --git a/prompts/finish/_context/production-100-OWNER-ACTIONS.md b/prompts/finish/_context/production-100-OWNER-ACTIONS.mdindex 78c19d280..448fc9ff2 100644--- a/prompts/finish/_context/production-100-OWNER-ACTIONS.md+++ b/prompts/finish/_context/production-100-OWNER-ACTIONS.md@@ -9,11 +9,11 @@ it and, if that unblocks a work order, say which one in the owning pack's `produRows carry the date they were added so staleness is visible. Re-verify a row before actingon it; some resolve themselves as other work lands.-## Open rows (2026-10-13 (triage-lane sweep, fourth pass): row 1 re-measured, deploy gap still 0 against the pushed `threews/main` ref; the `ccv-ai-providers-unavailable-503` finding's Groq/OpenRouter/Vertex angles confirmed already covered by rows 6 and 20, no new row added; 2026-10-13 (order 087 close-out): row 51 added for the LiveKit and Pipecat avatar integrations, both built and verified end to end this session, with the PyPI publishes and the two upstream pull requests left as owner actions; 2026-10-13 (order 085 close-out): row 50 added for publishing the CC0 bulk animation library to production, and the Adobe Mixamo permission letter draft is ready to send as owner order 938; 2026-10-12 (order 084 close-out): row 49 added for the Tripo signed webhook's three linked steps (apply the `forge_webhook_deliveries` migration, set `TRIPO_WEBHOOK_SECRET`, register the dashboard webhook), not an active bug since the secret is unset and polling answers every Tripo job today; 2026-10-12 18:10 UTC (triage-lane sweep, third pass): row 48 added for the dist-lib CDN embed size fix (previously-unclassified `/dist-lib/agent-3d.js` 500s, root-caused and fixed on `evolve`, pure code change awaiting the next deploy); 2026-10-12 17:54 UTC (triage-lane sweep, second pass): row 1's same-day "11 behind" figure corrected to the real deploy gap of 0 (querying `/api/version` live, not `/api/healthz`, which has no commit field), row 47 added for CoinGecko's keyless tier being rate-limited (`COINGECKO_API_KEY` already absent from the service, so the finding's own pre-approved env fix is a no-op); 2026-10-12 (triage-lane sweep): row 1 re-measured against the canonical `threews` remote, 11 commits behind `main` (down from 28, local stale ref corrected), row 45 added for the HF image-provider (fal-ai/nscale) credit exhaustion, a separate pool from row 6; 2026-10-11 (best3d order 070 close-out): rows 43 and 44 added for the `model-partcrafter` and `model-holopart` first deploys; 2026-10-11 (triage-lane sweep): row 42 added for the MCP client-sessions nullable-column migration, an active production bug; row 1 re-measured, 28 commits behind `main` (up from 5); 2026-10-11 (best3d order 069 close-out): rows 40 and 41 added for the `model-rig-nonhuman` and `model-anigen` first deploys; 2026-10-11 (best3d order 068 close-out): row 39 added for the `model-pixal3d` first deploy; 2026-10-11 (best3d order 067 retry): row 38 added for the `model-trellis2` first deploy; 2026-10-11 (order 404 close-out): row 34 deleted, its premise cleared by merge commit `d77b89178` (the `evolve`/`main` reconciliation) which also carried the `x-mention-reply.js` `chainFor()` fix row 34 called out, verified live with `RUN_LLM_TESTS=1 npx vitest run tests/x-mention-reply.llm.test.js` (16/16 `source: 'model'`, no `buildBody` TypeError); 2026-10-11 (scout lane): row 36 added for the Cloudflare R2 flapping degraded/down pattern; 2026-10-11 (even later): row 24 re-measured again after order 400's ring-leak-scan tiering/lock fix shipped on `evolve`; 2026-10-11 (later): row 35 added for the agent mention-policy migration; 2026-10-11 04:16 UTC: rows 1 and 24 re-measured by the deep triage sweep; row 34 added for the evolve/main branch divergence; 2026-10-10: row 33 added for the xAI MCP e2e key; rows 1, 19 and 24 re-measured by the triage sweep; 2026-10-09: rows 1, 2 and 24 re-measured by the triage sweep, row 31 added for the GPU worker redeploy and row 32 for database table retention; row 30 added for the Grok Bot CLI setup rerun; 2026-10-08: row 26 added for the coin-gated MCP catalog regeneration; rows 1 and 2 re-measured by the triage sweep, row 24 added for the paid Solana RPC credits, row 25 added for the MCP connector OAuth deploy; 2026-09-30: row 23 added for the $THREE receiver wallets; 2026-09-29: row 19 re-measured after the agent-sniper deploy; 2026-09-09: row 19 added, and row 1 corrected because its outage premise no longer holds; rows 1, 2, 3, 9, 13, 15 and 16 re-measured 2026-09-04; the former row 18 was cleared that day and its number is not reused; the 2026-09-02 and 2026-08-09 passes are folded in below)+## Open rows (2026-10-13 (triage-lane sweep, fifth pass): row 53 added for the Birdeye compute-units cap behind `pump-price-history-upstreams-502` (confirmed live, a billing/plan decision only); row 1 re-measured, deploy gap still 0 against the pushed `threews/main` ref and the 8 page-404/wrong-canonical findings this pass confirmed as deploy lag; row 47 re-measured, still a no-op (`COINGECKO_API_KEY` still absent); the previously-unclassified `/dist-lib/agent-3d.js` and `/agent-3d/latest/agent-3d.js` 500s ("Response size was too large") are the same bug row 48 already tracks, fixed on `evolve` in `f939d5ef1`, confirmed still green (`npx vitest run tests/lib-bundle-size.test.js tests/whisper-stt.test.js`, 16/16) and awaiting the pending deploy, no new row; 2026-10-13 (triage-lane sweep, fourth pass): row 1 re-measured, deploy gap still 0 against the pushed `threews/main` ref; the `ccv-ai-providers-unavailable-503` finding's Groq/OpenRouter/Vertex angles confirmed already covered by rows 6 and 20, no new row added; 2026-10-13 (order 087 close-out): row 51 added for the LiveKit and Pipecat avatar integrations, both built and verified end to end this session, with the PyPI publishes and the two upstream pull requests left as owner actions; 2026-10-13 (order 085 close-out): row 50 added for publishing the CC0 bulk animation library to production, and the Adobe Mixamo permission letter draft is ready to send as owner order 938; 2026-10-12 (order 084 close-out): row 49 added for the Tripo signed webhook's three linked steps (apply the `forge_webhook_deliveries` migration, set `TRIPO_WEBHOOK_SECRET`, register the dashboard webhook), not an active bug since the secret is unset and polling answers every Tripo job today; 2026-10-12 18:10 UTC (triage-lane sweep, third pass): row 48 added for the dist-lib CDN embed size fix (previously-unclassified `/dist-lib/agent-3d.js` 500s, root-caused and fixed on `evolve`, pure code change awaiting the next deploy); 2026-10-12 17:54 UTC (triage-lane sweep, second pass): row 1's same-day "11 behind" figure corrected to the real deploy gap of 0 (querying `/api/version` live, not `/api/healthz`, which has no commit field), row 47 added for CoinGecko's keyless tier being rate-limited (`COINGECKO_API_KEY` already absent from the service, so the finding's own pre-approved env fix is a no-op); 2026-10-12 (triage-lane sweep): row 1 re-measured against the canonical `threews` remote, 11 commits behind `main` (down from 28, local stale ref corrected), row 45 added for the HF image-provider (fal-ai/nscale) credit exhaustion, a separate pool from row 6; 2026-10-11 (best3d order 070 close-out): rows 43 and 44 added for the `model-partcrafter` and `model-holopart` first deploys; 2026-10-11 (triage-lane sweep): row 42 added for the MCP client-sessions nullable-column migration, an active production bug; row 1 re-measured, 28 commits behind `main` (up from 5); 2026-10-11 (best3d order 069 close-out): rows 40 and 41 added for the `model-rig-nonhuman` and `model-anigen` first deploys; 2026-10-11 (best3d order 068 close-out): row 39 added for the `model-pixal3d` first deploy; 2026-10-11 (best3d order 067 retry): row 38 added for the `model-trellis2` first deploy; 2026-10-11 (order 404 close-out): row 34 deleted, its premise cleared by merge commit `d77b89178` (the `evolve`/`main` reconciliation) which also carried the `x-mention-reply.js` `chainFor()` fix row 34 called out, verified live with `RUN_LLM_TESTS=1 npx vitest run tests/x-mention-reply.llm.test.js` (16/16 `source: 'model'`, no `buildBody` TypeError); 2026-10-11 (scout lane): row 36 added for the Cloudflare R2 flapping degraded/down pattern; 2026-10-11 (even later): row 24 re-measured again after order 400's ring-leak-scan tiering/lock fix shipped on `evolve`; 2026-10-11 (later): row 35 added for the agent mention-policy migration; 2026-10-11 04:16 UTC: rows 1 and 24 re-measured by the deep triage sweep; row 34 added for the evolve/main branch divergence; 2026-10-10: row 33 added for the xAI MCP e2e key; rows 1, 19 and 24 re-measured by the triage sweep; 2026-10-09: rows 1, 2 and 24 re-measured by the triage sweep, row 31 added for the GPU worker redeploy and row 32 for database table retention; row 30 added for the Grok Bot CLI setup rerun; 2026-10-08: row 26 added for the coin-gated MCP catalog regeneration; rows 1 and 2 re-measured by the triage sweep, row 24 added for the paid Solana RPC credits, row 25 added for the MCP connector OAuth deploy; 2026-09-30: row 23 added for the $THREE receiver wallets; 2026-09-29: row 19 re-measured after the agent-sniper deploy; 2026-09-09: row 19 added, and row 1 corrected because its outage premise no longer holds; rows 1, 2, 3, 9, 13, 15 and 16 re-measured 2026-09-04; the former row 18 was cleared that day and its number is not reused; the 2026-09-02 and 2026-08-09 passes are folded in below)| # | Action | Size | Unblocks | Detail lives in ||---|---|---|---|---|-| 1 | Approve the production deploy (or say "get production working", which is itself the approval). **The outage this row was written for is CLEARED.** Re-measured 2026-09-09 from the live origin: production serves `880bdcef8` on revision `three-ws-api-00420-ljh`, built 2026-09-08 19:05 UTC, and the `ERR_MODULE_NOT_FOUND` on `/app/services/home-relay/src/token.js` is gone: `/api/healthz` answers **HTTP 200** and `/api/home/status` and `/api/home/connections` answer 401 (auth required) rather than 500. What remains is ordinary staleness, 182 commits behind `main`, which is a routine cadence question and no longer a platform-health emergency. The 2026-09-04 text of this row, which described 96 commits and a 500ing healthz, is superseded. **Re-measured 2026-10-08 17:05 UTC:** production serves `fe2a8b24f` on `three-ws-api-00479-d7z`, **146 commits behind `main`, 90 of them fixes** (security, payouts, SSRF and XSS among them). Shipping them clears four live findings at once: the ring sweep's fee falls back to the treasury instead of the dry sponsor (`a9c996e72`, about 30 failed sweeps an hour since 2026-10-03), an EVM testnet identity-index cursor frozen since 2026-09-11 (`21fa42bb5`), two pages and their two docs pages advertised in the sitemap but answering 404 (added in `16f9d07f4`), and `/tty` holding its animation until the end for any client that accepts compression (`03b4f1189`). One migration must go with it: `20261008150000_revenue_direct_settle_backfill.sql` (pending; it matches 0 rows today, so applying it is safe, and the code half is what keeps the payout cron from paying a direct-to-seller sale twice). Commands, in order: `npm run db:status`, `npm run db:migrate`, `npm run deploy:gcp:full`. **Re-measured 2026-10-09 03:05 UTC by the triage sweep:** production still serves image `fe2a8b24f` (now on revision `three-ws-api-00480-mws`, an env-only roll that raised `DB_RETENTION_HIGH_WATER_MB` to 16384), **172 commits behind `main`**, and the `evolve` branch holds 85 more awaiting the runner's merge, six of them this sweep's production fixes: the leak scanner's lease and budget (`0abce6d69`, which ends about eight overlapping 600 to 900 s scans that were burning the Solana RPC quota), `-32020` RPC failover (`4b51a179c`), static 412/416 instead of 500 (`e01e43b3b`), the news knowledge write fix (`833407d4f`, 120 lost stories a day), and the reconstruct sweep's plan-limit close (`85d3b2034`). `20261008150000_revenue_direct_settle_backfill.sql` has since been applied; `npm run db:status` now lists two pending, `20261008190000_oauth_refresh_user_client_index.sql` and `20261008200000_mcp_client_analytics.sql` (rows 27 and 28). The 8 sitemap pages still answering 404 (`/grok`, `/grok-skill.md`, `/docs/grok`, `/docs/grok-bot`, `/dextools`, `/docs/dextools`, `/chart-companion`, `/docs/chart-companion`) are all deploy lag. **Re-measured 2026-10-10 20:06 UTC by the triage sweep:** production serves `5af439bc0` on `three-ws-api-00487-7mt`, built 2026-10-10 05:01 UTC, **45 commits behind `main`** (down from 172 on 2026-10-09; most of the gap already shipped), and the `evolve` branch holds 89 more. All 869 advertised pages, every cron (125) and the fleet (48 services) check out clean; the only pending migrations are rows 27 and 28's two files. **Re-measured 2026-10-11 04:16 UTC by the deep triage sweep:** production serves `3503381b1` on `three-ws-api-00491-fbl`, **112 commits behind `main`** (up from 45 on 2026-10-10). One new page-lag symptom from the gap: `/docs/tutorials/grok-bot-recipes` (added in `71c673f99`, after the running revision) answers 200 with `/docs`'s content instead of its own; this is deploy lag, not a routing bug (verified: `71c673f99` is not an ancestor of `3503381b1`). The fleet (48 services), 125 crons and DB are otherwise clean; the only pending migrations remain rows 27 and 28's two files. **Re-measured 2026-10-11 12:32 UTC by the triage-lane sweep:** production serves `66a5e93bd` on `three-ws-api-00494-wh5`, built 2026-10-11 07:22 UTC, **only 5 commits behind `main`** (down sharply from 112 on 2026-10-11 04:16; the earlier large gap has shipped). The 5 outstanding commits are the desktop OS/shell/widgets feature set and the campus world update (`e33f529d8`, `33b5490c5`, `a48caf816`, `9c47f3ceb`, `86366a55e`). Rows 27 and 28's migrations are now applied; `npm run db:status` shows 2 new pending files, `20261011220000_agent_mention_policy.sql` (tracked by row 35) and `20261011230000_x402_ring_scan_checked_at.sql` (tracked by row 24's narrative), both additive. This sweep also committed two root-cause fixes to `main`-bound code that are NOT yet in this 5-commit gap: `65d6c4be8` (clink-fun MCP stream timeout misclassified as investigate) and `2f2fedf99` (a Pollinations 402 was putting the paid Replicate/TRELLIS lane into cooldown, contributing to `forge_generation: down`); the second one fixes a live production defect, so it is worth prioritizing in the next deploy. **Re-measured 2026-10-11 21:12 UTC by the triage-lane sweep:** production still serves `66a5e93bd` on `three-ws-api-00494-wh5`, **28 commits behind `main`** (`main` now at `9eda7992d`), up from 5 at 12:32 UTC because the desktop OS/shell/widgets/campus set from that measurement has been joined by new work: the x-content partner-spotlight feature (registry, daily scheduler, published IBM and AWS partner articles, the `/partners/benefits` page) and five dependabot bumps (`js-yaml`/`markdownlint-cli2`, `nanoid`, `maplibre-gl`, `torch` in `workers/texture`, `brace-expansion`, `source-map-js`, `moment`, `fast-uri`). `2f2fedf99` (the forge-cooldown fix) is still only on `evolve`, not yet on `main`; it remains worth prioritizing. The deep sweep found exactly one new pending migration, now tracked as row 42; rows 24 and 35's migrations are applied. The `/docs/desktop-widgets` 404 and `/docs/tutorials/grok-bot-recipes` wrong-canonical findings are confirmed deploy lag again (their catalog commits are not ancestors of `66a5e93bd`), not new routing bugs. **Re-measured 2026-10-12 by the triage-lane sweep, against the canonical `threews` remote (the local `main` ref in the `evolve` worktree was stale):** production (`/api/healthz`'s own `commitShort`) serves `c266e2591`, **11 commits behind `threews/main`** at `80e5e35f7`, down sharply from 28. The outstanding set is the Dissolve feature (a GPU particle-storm viewer for any 3D model) with its docs and page-catalog regeneration, a security-hardening batch (`8a56a44ab`: auth, wallet policy, SDP, vault, skill sandbox, MCP bridge URL guard, all with regression tests), a worker fix (`315e96f96`: block internal-host navigation in the screen pool, load text2motion weights with `weights_only`), an accessibility fix (`f772c8708`: icon-only button tooltips, gallery/create/header name-to-text matching), the Grid desktop world (`762269248`, `f35d07d93`, `a60d72dad`) and a new UI-lint tool (`568162d8d`). None of this sweep's own fixes (the Vertex/HF image-lane circuit breaker, the `forge-image-ladder-exhausted-502` and widened `r2-downstream-5xx` triage signatures) are in this 11-commit gap either; they are further back on `evolve`, behind the runner's usual fast-forward-to-`main` cadence. **Corrected 2026-10-12 17:54 UTC by the triage-lane sweep: the same-day "11 commits behind" figure above was a misread.** Querying the live `/api/version` endpoint directly (not `/api/healthz`, which carries no commit field) shows production still serves `771cfef01` on `three-ws-api-00496-78g`, built 2026-10-12 07:08 UTC. A fresh `git fetch threews` puts `threews/main` at `80e5e35f7`, and `git merge-base --is-ancestor threews/main 771cfef01` succeeds with exactly 1 commit between them, so the deployed revision is 1 commit AHEAD of the canonical remote `main`, not behind it. **The real deploy gap (commits on `main` not yet in production) is 0.** The 242 commits the deep sweep reports as "ahead" are `evolve`-branch commits (this worktree's local `main`, one commit ahead of pushed `threews/main`) not yet pushed, including this sweep's own `5afb045cf` (widened the `r2-downstream-5xx` triage signature to cover `/api/render/animate`, `/api/render/glb`, `/api/render/avatar-clip` and `/api/animations/clips/<id>`, all previously-unmatched symptoms of the same R2 flap row 36 already tracks); they are not a production staleness problem. **Re-measured 2026-10-13 by the triage-lane sweep:** production still serves `771cfef01` on `three-ws-api-00496-78g`. A fresh `git fetch threews` puts `threews/main` at `80e5e35f74302c85138bf6cabdad4f2db65b9ecf`, and `git merge-base --is-ancestor threews/main 771cfef01` succeeds, so the deployed revision is still exactly 1 commit AHEAD of the canonical remote `main`. **The real deploy gap remains 0.** The deep sweep's "283 commits ahead" figure is `evolve`-branch backlog (unpushed local commits, including `f939d5ef1`, the dist-lib CDN embed size fix documented in row 48) awaiting the runner's fast-forward, not a production staleness problem. This sweep found no new code-level defect to fix: the dist-lib bug is already root-caused, fixed and tested on `evolve`; the Solana-adjacent degraded subsystems (`agent_index`, `rpc_lanes`, `helius`, `sniper`, `three_token_rail`) and the `ccv-ai-providers-unavailable-503` finding (Groq's 200k tokens/day cap, the GCP billing hold, and the revoked OpenRouter key) are all pre-existing owner items already tracked in rows 23, 24, 19, 2, 20 and 6; none needed a new row. | one yes | Shipping whatever has landed on `main` since 2026-09-08, now including the security-hardening batch and the forge image-lane breaker fix | [01-ship-readiness.md](../901-production-100-01-ship-readiness.md) |+| 1 | Approve the production deploy (or say "get production working", which is itself the approval). **The outage this row was written for is CLEARED.** Re-measured 2026-09-09 from the live origin: production serves `880bdcef8` on revision `three-ws-api-00420-ljh`, built 2026-09-08 19:05 UTC, and the `ERR_MODULE_NOT_FOUND` on `/app/services/home-relay/src/token.js` is gone: `/api/healthz` answers **HTTP 200** and `/api/home/status` and `/api/home/connections` answer 401 (auth required) rather than 500. What remains is ordinary staleness, 182 commits behind `main`, which is a routine cadence question and no longer a platform-health emergency. The 2026-09-04 text of this row, which described 96 commits and a 500ing healthz, is superseded. **Re-measured 2026-10-08 17:05 UTC:** production serves `fe2a8b24f` on `three-ws-api-00479-d7z`, **146 commits behind `main`, 90 of them fixes** (security, payouts, SSRF and XSS among them). Shipping them clears four live findings at once: the ring sweep's fee falls back to the treasury instead of the dry sponsor (`a9c996e72`, about 30 failed sweeps an hour since 2026-10-03), an EVM testnet identity-index cursor frozen since 2026-09-11 (`21fa42bb5`), two pages and their two docs pages advertised in the sitemap but answering 404 (added in `16f9d07f4`), and `/tty` holding its animation until the end for any client that accepts compression (`03b4f1189`). One migration must go with it: `20261008150000_revenue_direct_settle_backfill.sql` (pending; it matches 0 rows today, so applying it is safe, and the code half is what keeps the payout cron from paying a direct-to-seller sale twice). Commands, in order: `npm run db:status`, `npm run db:migrate`, `npm run deploy:gcp:full`. **Re-measured 2026-10-09 03:05 UTC by the triage sweep:** production still serves image `fe2a8b24f` (now on revision `three-ws-api-00480-mws`, an env-only roll that raised `DB_RETENTION_HIGH_WATER_MB` to 16384), **172 commits behind `main`**, and the `evolve` branch holds 85 more awaiting the runner's merge, six of them this sweep's production fixes: the leak scanner's lease and budget (`0abce6d69`, which ends about eight overlapping 600 to 900 s scans that were burning the Solana RPC quota), `-32020` RPC failover (`4b51a179c`), static 412/416 instead of 500 (`e01e43b3b`), the news knowledge write fix (`833407d4f`, 120 lost stories a day), and the reconstruct sweep's plan-limit close (`85d3b2034`). `20261008150000_revenue_direct_settle_backfill.sql` has since been applied; `npm run db:status` now lists two pending, `20261008190000_oauth_refresh_user_client_index.sql` and `20261008200000_mcp_client_analytics.sql` (rows 27 and 28). The 8 sitemap pages still answering 404 (`/grok`, `/grok-skill.md`, `/docs/grok`, `/docs/grok-bot`, `/dextools`, `/docs/dextools`, `/chart-companion`, `/docs/chart-companion`) are all deploy lag. **Re-measured 2026-10-10 20:06 UTC by the triage sweep:** production serves `5af439bc0` on `three-ws-api-00487-7mt`, built 2026-10-10 05:01 UTC, **45 commits behind `main`** (down from 172 on 2026-10-09; most of the gap already shipped), and the `evolve` branch holds 89 more. All 869 advertised pages, every cron (125) and the fleet (48 services) check out clean; the only pending migrations are rows 27 and 28's two files. **Re-measured 2026-10-11 04:16 UTC by the deep triage sweep:** production serves `3503381b1` on `three-ws-api-00491-fbl`, **112 commits behind `main`** (up from 45 on 2026-10-10). One new page-lag symptom from the gap: `/docs/tutorials/grok-bot-recipes` (added in `71c673f99`, after the running revision) answers 200 with `/docs`'s content instead of its own; this is deploy lag, not a routing bug (verified: `71c673f99` is not an ancestor of `3503381b1`). The fleet (48 services), 125 crons and DB are otherwise clean; the only pending migrations remain rows 27 and 28's two files. **Re-measured 2026-10-11 12:32 UTC by the triage-lane sweep:** production serves `66a5e93bd` on `three-ws-api-00494-wh5`, built 2026-10-11 07:22 UTC, **only 5 commits behind `main`** (down sharply from 112 on 2026-10-11 04:16; the earlier large gap has shipped). The 5 outstanding commits are the desktop OS/shell/widgets feature set and the campus world update (`e33f529d8`, `33b5490c5`, `a48caf816`, `9c47f3ceb`, `86366a55e`). Rows 27 and 28's migrations are now applied; `npm run db:status` shows 2 new pending files, `20261011220000_agent_mention_policy.sql` (tracked by row 35) and `20261011230000_x402_ring_scan_checked_at.sql` (tracked by row 24's narrative), both additive. This sweep also committed two root-cause fixes to `main`-bound code that are NOT yet in this 5-commit gap: `65d6c4be8` (clink-fun MCP stream timeout misclassified as investigate) and `2f2fedf99` (a Pollinations 402 was putting the paid Replicate/TRELLIS lane into cooldown, contributing to `forge_generation: down`); the second one fixes a live production defect, so it is worth prioritizing in the next deploy. **Re-measured 2026-10-11 21:12 UTC by the triage-lane sweep:** production still serves `66a5e93bd` on `three-ws-api-00494-wh5`, **28 commits behind `main`** (`main` now at `9eda7992d`), up from 5 at 12:32 UTC because the desktop OS/shell/widgets/campus set from that measurement has been joined by new work: the x-content partner-spotlight feature (registry, daily scheduler, published IBM and AWS partner articles, the `/partners/benefits` page) and five dependabot bumps (`js-yaml`/`markdownlint-cli2`, `nanoid`, `maplibre-gl`, `torch` in `workers/texture`, `brace-expansion`, `source-map-js`, `moment`, `fast-uri`). `2f2fedf99` (the forge-cooldown fix) is still only on `evolve`, not yet on `main`; it remains worth prioritizing. The deep sweep found exactly one new pending migration, now tracked as row 42; rows 24 and 35's migrations are applied. The `/docs/desktop-widgets` 404 and `/docs/tutorials/grok-bot-recipes` wrong-canonical findings are confirmed deploy lag again (their catalog commits are not ancestors of `66a5e93bd`), not new routing bugs. **Re-measured 2026-10-12 by the triage-lane sweep, against the canonical `threews` remote (the local `main` ref in the `evolve` worktree was stale):** production (`/api/healthz`'s own `commitShort`) serves `c266e2591`, **11 commits behind `threews/main`** at `80e5e35f7`, down sharply from 28. The outstanding set is the Dissolve feature (a GPU particle-storm viewer for any 3D model) with its docs and page-catalog regeneration, a security-hardening batch (`8a56a44ab`: auth, wallet policy, SDP, vault, skill sandbox, MCP bridge URL guard, all with regression tests), a worker fix (`315e96f96`: block internal-host navigation in the screen pool, load text2motion weights with `weights_only`), an accessibility fix (`f772c8708`: icon-only button tooltips, gallery/create/header name-to-text matching), the Grid desktop world (`762269248`, `f35d07d93`, `a60d72dad`) and a new UI-lint tool (`568162d8d`). None of this sweep's own fixes (the Vertex/HF image-lane circuit breaker, the `forge-image-ladder-exhausted-502` and widened `r2-downstream-5xx` triage signatures) are in this 11-commit gap either; they are further back on `evolve`, behind the runner's usual fast-forward-to-`main` cadence. **Corrected 2026-10-12 17:54 UTC by the triage-lane sweep: the same-day "11 commits behind" figure above was a misread.** Querying the live `/api/version` endpoint directly (not `/api/healthz`, which carries no commit field) shows production still serves `771cfef01` on `three-ws-api-00496-78g`, built 2026-10-12 07:08 UTC. A fresh `git fetch threews` puts `threews/main` at `80e5e35f7`, and `git merge-base --is-ancestor threews/main 771cfef01` succeeds with exactly 1 commit between them, so the deployed revision is 1 commit AHEAD of the canonical remote `main`, not behind it. **The real deploy gap (commits on `main` not yet in production) is 0.** The 242 commits the deep sweep reports as "ahead" are `evolve`-branch commits (this worktree's local `main`, one commit ahead of pushed `threews/main`) not yet pushed, including this sweep's own `5afb045cf` (widened the `r2-downstream-5xx` triage signature to cover `/api/render/animate`, `/api/render/glb`, `/api/render/avatar-clip` and `/api/animations/clips/<id>`, all previously-unmatched symptoms of the same R2 flap row 36 already tracks); they are not a production staleness problem. **Re-measured 2026-10-13 by the triage-lane sweep:** production still serves `771cfef01` on `three-ws-api-00496-78g`. A fresh `git fetch threews` puts `threews/main` at `80e5e35f74302c85138bf6cabdad4f2db65b9ecf`, and `git merge-base --is-ancestor threews/main 771cfef01` succeeds, so the deployed revision is still exactly 1 commit AHEAD of the canonical remote `main`. **The real deploy gap remains 0.** The deep sweep's "283 commits ahead" figure is `evolve`-branch backlog (unpushed local commits, including `f939d5ef1`, the dist-lib CDN embed size fix documented in row 48) awaiting the runner's fast-forward, not a production staleness problem. This sweep found no new code-level defect to fix: the dist-lib bug is already root-caused, fixed and tested on `evolve`; the Solana-adjacent degraded subsystems (`agent_index`, `rpc_lanes`, `helius`, `sniper`, `three_token_rail`) and the `ccv-ai-providers-unavailable-503` finding (Groq's 200k tokens/day cap, the GCP billing hold, and the revoked OpenRouter key) are all pre-existing owner items already tracked in rows 23, 24, 19, 2, 20 and 6; none needed a new row. **Re-measured 2026-10-13 (triage-lane sweep, fifth pass):** production still serves `771cfef01` on `three-ws-api-00497-2ss`. `git fetch threews` puts `threews/main` at `80e5e35f74302c85138bf6cabdad4f2db65b9ecf`, and `git merge-base --is-ancestor threews/main 771cfef01` still succeeds, so the deployed revision remains exactly 1 commit AHEAD of `main`. **The real deploy gap stays 0.** The deep sweep's "291 commits ahead" figure is `evolve`-branch backlog (unpushed, includes `f939d5ef1` / row 48 and this pass's new row 53) awaiting the runner's fast-forward, not production staleness. The 8 sitemap-advertised pages answering 404 or wrong-canonical this pass (`/discord-activity`, `/docs/discord-activity`, `/docs/engine-bridges`, `/docs/engine-qa`, `/docs/open-source-credits`, `/docs/voice-framework-integrations`, `/open-source`, `/docs/tutorials/grok-bot-recipes`) are all confirmed deploy lag (`git merge-base --is-ancestor <add-commit> 771cfef01` fails for each); no routing bug. | one yes | Shipping whatever has landed on `main` since 2026-09-08, now including the security-hardening batch and the forge image-lane breaker fix | [01-ship-readiness.md](../901-production-100-01-ship-readiness.md) || 2 | Fund the settle sponsor wallet `WwwuGbqHrwF5RG89KhUbmRWEvjnRH9k5kVM5p7T3WwW`. Healthz reports `x402_settle` down with `cause: sponsor_floor` (settle 5.9%, 3 of 51 paid attempts over 3 hours, 329 `no_solana_accept`) and the sniper worker out of capital (0.2307 SOL to refill its wallets, funding master holds 0.0250 SOL); no config change moves either. Re-read 2026-09-04 08:21 UTC against mainnet: the sponsor holds **0.001507661 SOL** (1,507,661 lamports), still below the settle floor, so the Solana accept stays withdrawn from every 402 challenge. Two months of re-measurement have only ever moved this number down; nothing on this machine can move it up. **Re-measured 2026-10-08 17:05 UTC:** the sponsor holds **651,828 lamports (0.000652 SOL)**, below rent-exempt (890,880), and healthz reads `x402_settle` down at 0.0% (0 of 32 paid attempts in 3 hours, 58 settles refused at the fee-wallet floor). Because the sponsor cannot co-sign, every 402 challenge advertises the Solana accept without `feePayer`, and the ring skips it: 151 `missing_fee_payer` skips in 24 hours on the MCP streaming health probe alone. Last successful settle: 2026-10-03 19:24 UTC. **Row 1's deploy alone restores the ring, no funding needed** (diagnosed 2026-10-08 by read-only simulation): the treasury pays its own sweep fee (5,001 lamports; it holds 0.060 SOL, about 11,800 sweeps) and moves its stranded 2.587 USDC back to the ring payer, which holds 341 atomics today, and ring settles are self-pay. What still needs this wallet: the sponsor-mode callers (the loop's inline entries and the MCP streaming health probe) and the facilitator's `sponsor_fee_unfunded` verify rejects. Clearing the 2,000,000-lamport floor takes at least **1,348,172 lamports**. **Re-measured 2026-10-09 03:05 UTC:** still **651,828 lamports**, unchanged; healthz reads `x402_settle` down at 0.0% (0 of 39 paid attempts in 3 hours, 37 `sweep_broadcast_failed`, 53 settles refused at the fee-wallet floor). The sweep failures are the ones row 1's deploy clears (`a9c996e72`). | ~1 SOL | x402 settle recovery, backlog 01 retirement, sniper | [../backlog/PROGRESS.md](backlog-PROGRESS.md), 2026-08-02 and 2026-09-01 entries || 3 | Decide the stranded customer funds: customers hold about 0.35 SOL behind the retired encryption key and cannot withdraw. Credit (recommended), contact first, or write off. The brief now exists with the measurement, the impossibility argument, the cost of each option and the exact commands: **[docs/ops/stranded-wallets.md](../../docs/ops/stranded-wallets.md)**. Measured 2026-09-02 from production's own records: the platform side is exactly two bot wallets holding 0.142875505 SOL (the reclaim cron has failed on them ~35,700 times each, most recently today), and one customer agent is confirmed by a `wallet_key_retired` withdraw failure (`GemVS5fT958FKRe5fpgizohUYUKE8cUDueEdmB1bmXnm`, 0.250001 SOL). **Both customer wallets are now named** (2026-09-04): the keyed audit was run against production, so this row no longer waits on anything. `GemVS5fT958FKRe5fpgizohUYUKE8cUDueEdmB1bmXnm` holds 0.250001 SOL and `HPL1LfuTdYDwtzJDzsnrmR2ngrrQwLTQyxJszCC4DHsN` holds 0.100001 SOL, 0.350002 SOL across exactly two wallet-auth accounts. Nine of 735 custodial wallets are sealed; the other five customer ones hold nothing. The brief carries the full table. Every input the decision needs is measured. | decision | Closing the support obligation | [docs/ops/stranded-wallets.md](../../docs/ops/stranded-wallets.md), [../backlog/PROGRESS.md](backlog-PROGRESS.md) || 4 | Rotate or explicitly accept three credentials, now that the storage half is done. **The config work shipped 2026-09-02**: the economy master key and 58 other plaintext credentials are Secret Manager references on `three-ws-api-00407-m7c`, zero plaintext credentials remain, healthz verified no worse and the master's signing path verified live. What is left is a judgment only the owner can make. (a) The master key was readable in the service config for some window, so decide whether to rotate it or accept that exposure, knowing who held project viewer access in that period; the exact owner-gated commands are in the runbook. (b) `WALLET_ENCRYPTION_KEY` and `JWT_SECRET` hold the SAME value on production, which passes the dedicated-key guard in `secret-box.js` while defeating what it guards; changing it is a re-key with real stranding risk, so it is not an agent's call. (c) `X402_SEED_SOLANA_SECRET_BASE58` holds the same value as `LAUNCHER_MASTER_SECRET_KEY_B64` though `scripts/wire-master-wallet.mjs` assigns those slots to different wallets; decide which is correct. | decision (+ one fund move if rotating) | 03 is otherwise closed | [docs/ops/wallet-key-migration.md](../../docs/ops/wallet-key-migration.md), 2026-09-02 section |@@ -59,13 +59,14 @@ on it; some resolve themselves as other work lands.| 45 | **Top up the HF Inference Providers credit balance for fal-ai and nscale (image generation), a separate pool from row 6's LLM-lane `HF_TOKEN` usage** (added 2026-10-12 by the evolve triage-lane sweep). Root-caused the `/api/3d/generate` 502 storm: both HF-routed image providers answer `402 "You have no remaining credits"` on every call (`api/_mcp3d/text-to-image.js`), alongside the already-tracked Vertex billing hold (row 20) on the image lane. The amplification bug (every request re-paying the full timeout of both known-dead lanes before ever reaching keyless Pollinations, often blowing the shared ladder budget) is fixed in code this sweep: a 401/402/403 now parks the lane for 5 minutes (`AUTH_COOLDOWN_SECONDS`), same breaker already used for Vertex elsewhere. That stops the 502 storm either way, but the ladder is still down two rungs (Vertex, HF) until the owner funds one or both; Pollinations alone is a lower-quality free-tier fallback with no paid Replicate backstop configured. Fix: top up the HF Inference Providers billing for the account behind `HF_TOKEN`, or fund the Vertex billing hold (row 20); either clears most image generations, both together clear all of it. | billing | `/api/3d/generate` image quality and the 502 rate | `scripts/gcp-triage.mjs` `forge-image-ladder-exhausted-502`, [docs/ops/production-log-triage.md](../../docs/ops/production-log-triage.md) §forge-image-ladder-exhausted || 46 | **Build and deploy `model-text2motion` with its new MoMask backend, then benchmark it against MDM** (added 2026-10-12 by the evolve loop, best3d order 077 task 1). `workers/model-text2motion/` now carries a second generation backend, MoMask (EricGuo5513/momask-codes, MIT, published FID 0.045 on HumanML3D vs. MDM-era T2M-GPT's 0.141), selectable per request via `model: "mdm" | "momask"` on `/infer`, alongside the existing default MDM backend. `main.py`'s model selector, the new `momask_sampler.py` and shared `motion_decode.py`, the updated `Dockerfile` (clones momask-codes, installs its one missing pip dependency `einops`), and the updated `cloudbuild.yaml` (adds `MOMASK_MODEL_DIR=/weights/momask` to both the primary and standby deploy steps) are all written and locally tested (49/49 passing in `workers/model-text2motion`'s own suite, including a new 12-case `test_model_selector.py`). The real checkpoints are already staged to `gs://three-ws-model-weights/momask/t2m/` (four checkpoint dirs: `length_estimator`, `rvq_nq6_dc512_nc512_noshare_qdp0.2`, `t2m_nlayer8_nhead6_ld384_ff1024_cdp0.1_rvq6ns`, `tres_nlayer8_ld384_ff1024_rvq6ns_cdp0.2_sw`), matching momask-codes' own HumanML3D checkpoint layout, so a deploy has real weights to mount the moment it lands. This is a production deploy (rebuilds and redeploys an existing Cloud Run GPU service, gate 2), so no agent runs it. Command, from the repo root: `gcloud builds submit --config workers/model-text2motion/cloudbuild.yaml --substitutions=SHORT_SHA=manual$(date +%s) .`. After it lands, run the same prompt through both backends and time the second call to each (post cold-load) for a real warm-vs-warm comparison: `curl -s -X POST "$MOTION_URL/infer" -H "authorization: Bearer $GCP_RECONSTRUCTION_KEY" -H 'content-type: application/json' -d '{"prompt":"a slow tai-chi sweep","duration_seconds":3,"fps":20,"model":"mdm"}'` and the same body with `"model":"momask"`, each followed by polling `GET $MOTION_URL/tasks/<task_id>` until `status:"done"`. That reproduced, in-house FID/latency comparison is task 1's own "benchmarked" requirement, not one of order 077's three Definition of done lines (all three passed and were reconfirmed live on 2026-10-12 against the already-deployed MDM backend, so the order retired without waiting on this deploy); the published 0.045 FID in the README is momask-codes' own number, not yet confirmed against this worker's own output. | one build + one deploy + two benchmark calls | Gives the Animation Studio and `/api/forge-motion` a second, stronger text-to-motion backend selectable per request (best3d order 077 is retired; see its 2026-10-12 entries in [best3d-PROGRESS.md](best3d-PROGRESS.md)) | [workers/model-text2motion/README.md](../../workers/model-text2motion/README.md) |-| 47 | **Buy a paid CoinGecko plan (or confirm a free monthly reset) for `/api/coin/*`.** Added 2026-10-12 by the triage-lane sweep: the deep sweep's `coingecko-quota-exhausted-502` finding (`/api/coin/detail`, `/api/coin/exchange`, 3 occurrences in the last 24h) names its own fix as `gcloud run services update three-ws-api --region us-central1 --remove-env-vars COINGECKO_API_KEY`, config-only and pre-approved. Checked live before running it: `gcloud run services describe three-ws-api --region us-central1` shows no `COINGECKO_API_KEY` env var on the service at all, so that fix is already in effect and there is nothing to remove. Every `/api/coin/*` call is already keyless; the 502s are the keyless CoinGecko tier itself being rate-limited (the Cloud Run egress IP is shared across every request this service makes), which only a paid CoinGecko API plan or a wait for next month's free-tier reset resolves. No in-repo code or config change can fix this. | one purchase decision | Stops the intermittent 502s on coin detail/exchange pages | [docs/ops/production-log-triage.md](../../docs/ops/production-log-triage.md) |+| 47 | **Buy a paid CoinGecko plan (or confirm a free monthly reset) for `/api/coin/*`.** Added 2026-10-12 by the triage-lane sweep: the deep sweep's `coingecko-quota-exhausted-502` finding (`/api/coin/detail`, `/api/coin/exchange`, 3 occurrences in the last 24h) names its own fix as `gcloud run services update three-ws-api --region us-central1 --remove-env-vars COINGECKO_API_KEY`, config-only and pre-approved. Checked live before running it: `gcloud run services describe three-ws-api --region us-central1` shows no `COINGECKO_API_KEY` env var on the service at all, so that fix is already in effect and there is nothing to remove. Every `/api/coin/*` call is already keyless; the 502s are the keyless CoinGecko tier itself being rate-limited (the Cloud Run egress IP is shared across every request this service makes), which only a paid CoinGecko API plan or a wait for next month's free-tier reset resolves. No in-repo code or config change can fix this. **Re-measured 2026-10-13 (triage-lane sweep, fifth pass):** still no `COINGECKO_API_KEY` on `three-ws-api` (`gcloud run services describe`); 20 occurrences in the last 24h across `/api/coin/exchange`, `/api/coin/detail`, `/api/coin/tickers`, `/api/coin/ohlc`. No change. | one purchase decision | Stops the intermittent 502s on coin detail/exchange pages | [docs/ops/production-log-triage.md](../../docs/ops/production-log-triage.md) || 48 | **Ship the dist-lib CDN embed size fix with the next deploy** (added 2026-10-12 by the triage-lane sweep, pure code fix, no migration, no env var). Root-caused the previously-unclassified `/dist-lib/agent-3d.js` and `/agent-3d/latest/agent-3d.js` 500s: `src/runtime/whisper-stt.js`'s on-device speech recognizer did a bare `import('@huggingface/transformers')`, which `vite.config.js`'s `inlineDynamicImports` lib-build setting inlines (it has to, so the CDN embed stays one file), dragging in onnxruntime-web's WebGPU runtime and bloating `agent-3d.js`/`agent-3d.umd.cjs` from the documented ~600-900KB gzipped to 76MB raw each, past Cloud Run/GFE's response-size handling for HTTP/1.1 or identity-encoding clients (confirmed live via curl with varying `Accept-Encoding`; gzip+HTTP/2 at 21MB succeeds, identity/HTTP/1.1 at 76MB 500s with an empty body). Fixed on `evolve` (commit `f939d5ef1`): the import now goes through the existing `loadModule()` CDN mirror loader instead of a bundler-visible specifier, the same pattern already used for WalletConnect and Leaflet. Local rebuild (`npm run build:lib:full`) drops both files to 4.1MB; `tests/lib-bundle-size.test.js` (new) proved red against the unfixed build and green after; `whisper-stt.test.js`'s 14 tests still pass. Sitting on `evolve` waiting for the usual fast-forward-to-`main` and row 1's deploy cadence; no separate action beyond that deploy. Post-deploy verification: `curl -sI -H "Accept-Encoding: identity" --http1.1 https://three.ws/dist-lib/agent-3d.js` should answer 200, not 500. | one deploy (already covered by row 1's cadence) | Fixes the `<agent-3d>` CDN embed for every third-party site that drops it in over plain HTTP/1.1 or without gzip | `tests/lib-bundle-size.test.js`, [docs/ops/production-log-triage.md](../../docs/ops/production-log-triage.md) || 49 | **Finish wiring the Tripo signed webhook (work order 084-partners-01), three linked steps.** (added 2026-10-12 by the evolve loop closing out order 084). Not an active bug today: `TRIPO_WEBHOOK_SECRET` is unset in production, so `verifySignature` in `api/forge/webhook/tripo.js` rejects before it ever touches the database, and polling (`pollJob` in `api/forge.js`) answers every Tripo job either way. But all three steps are needed together before the webhook path can turn on for real: (a) apply the pending idempotency-ledger migration, `node scripts/apply-migrations.mjs --apply --file 20261015040000_forge_webhook_deliveries.sql` (or `npm run db:migrate`, which applies every pending migration immediately with no dry run; `npm run db:status` shows it as the only one left from this order), since `claimForgeWebhookDelivery`/`markForgeWebhookApplied` in `api/_lib/forge-store.js` would otherwise hit `relation forge_webhook_deliveries does not exist` the first time a verified delivery arrives; (b) set `TRIPO_WEBHOOK_SECRET` (`gcloud run services update three-ws-api --region us-central1 --update-env-vars TRIPO_WEBHOOK_SECRET=...`, never `--set-env-vars`) to whatever Tripo's dashboard issues; (c) register the production webhook URL (`https://three.ws/api/forge/webhook/tripo`) in Tripo's own dashboard, which only exists once a Tripo account is set up, the same account gate order 936 tracks for `TRIPO_API_KEY`. Putting a platform-paid `TRIPO_API_KEY` on the service is tracked separately in **order 936** (`936-partners-13-tripo-reply-and-house-key.md`), not duplicated here, since that order is itself gated on the owner's reply and call with Tripo. | one migration apply + one env var + one dashboard step | Lets a Tripo generation complete by webhook instead of only by poll, once a Tripo account exists | [084-partners-01-tripo-v3-house-lane.md](../084-partners-01-tripo-v3-house-lane.md), [936-partners-13-tripo-reply-and-house-key.md](../936-partners-13-tripo-reply-and-house-key.md) || 50 | **Publish the CC0 bulk animation library to production** (added 2026-10-13 by the evolve loop closing out order 085-partners-02). `GET /api/animations/library` currently answers `total: 0` in production: the bulk motion library (previously baked from Mixamo, which Adobe's own Mixamo FAQ says may not be redistributed as raw files) has been rebuilt from two CC0 1.0 Universal sources, Quaternius's Universal Animation Library 2 and Mesh2Motion's human animation packs, 219 clips retargeted and verified locally (0 failures, every entry carries `source`/`license`). The only remaining step is to run `node scripts/cc0-animation-library.mjs --upload` with the production R2 credentials (`node scripts/read-service-env.mjs` to read them from the `three-ws-api` Cloud Run service if not already in `.env.local`), which publishes the staged manifest to the live bucket the endpoint reads at request time, no code deploy required. This was deliberately not run this session: it is a production-publish action (CLAUDE.md gate 2) that makes 219 clips reachable to real users and third-party mirrors immediately. Separately, and not blocking this row: the Adobe Mixamo redistribution-permission letter is drafted and ready at [`marketing/growth/submissions/adobe-mixamo-permission.md`](../../marketing/growth/submissions/adobe-mixamo-permission.md); sending it is owner order 938. | one upload command | Makes the openly-licensed bulk animation library live on `/animations` and `GET /api/animations/library` | [085-partners-02-animation-library-license.md](../085-partners-02-animation-library-license.md) || 51 | **Publish and submit the LiveKit and Pipecat avatar integrations** (added 2026-10-13 by the evolve loop closing out order 087-partners-04). Both packages (`integrations/livekit/livekit-plugins-threews/`, `integrations/pipecat/pipecat-threews/`) are built, tested (unit tests, ruff lint/format), and verified end to end against a real local `livekit-server` with real browser automation driving the actual avatar lipsync and gesture off a live agent/bot in both frameworks (Playwright specs, both passing; the Pipecat run also captured the 30-60s demo video `COMMUNITY_INTEGRATIONS.md` asks for, saved locally and gitignored). Three remaining steps are all owner actions (CLAUDE.md gate 2, external posting/publishing): (a) `python -m build && twine upload` (or equivalent) to publish each package to PyPI as `livekit-plugins-threews` and `pipecat-threews`; (b) open the LiveKit plugin pull request against `livekit/agents` using the title, description and verification packet in [`marketing/growth/submissions/livekit-avatar-plugin.md`](../../marketing/growth/submissions/livekit-avatar-plugin.md), then apply to the LiveKit Startups program; (c) open the Pipecat documentation pull request against `pipecat-ai/pipecat` using the three files in `integrations/pipecat/pipecat-threews/docs-submission/` and the text in [`marketing/growth/submissions/pipecat-integration.md`](../../marketing/growth/submissions/pipecat-integration.md), attaching the local demo video. | two PyPI publishes + two pull requests + one program application | LiveKit plugin PR 938/Startups 939, Pipecat community-integration listing | [087-partners-04-livekit-pipecat-avatar.md](../087-partners-04-livekit-pipecat-avatar.md) || 52 | **Register the Discord application and verify the Activity in a real Discord client** (added 2026-10-13 by the evolve loop closing out order 088-partners-05). The shared Forge room Activity ([`src/discord-activity/app.js`](../../src/discord-activity/app.js), [`api/gateway/discord-activity-*`](../../api/gateway/), migration [`20261015050000_discord_activity_rooms.sql`](../../api/_lib/migrations/20261015050000_discord_activity_rooms.sql)) is built and unit-tested (`tests/discord-activity-store.test.js`, `tests/discord-activity-auth.test.js`, 13/13 passing), and the OAuth2 token-exchange path was proven live against Discord's real endpoint (`curl` to `https://discord.com/api/oauth2/token` with a placeholder client returned Discord's real, documented `invalid_client` 400, matching the error path the code already surfaces). No Discord application has ever been registered in this production project (`node scripts/read-service-env.mjs '^DISCORD' --names` returns zero matches), so nothing past that point is testable from this workspace. Full step-by-step with exact Developer Portal settings and the Discovery listing copy: [`marketing/growth/submissions/discord-activity.md`](../../marketing/growth/submissions/discord-activity.md). Summary: (a) create the Discord application and enable Activities, pointing the root URL Mapping at `/discord-activity` and adding a `cdn` URL Mapping for the R2 host; (b) set the OAuth2 redirect and `identify` scope; (c) `gcloud run services update three-ws-api --region us-central1 --update-env-vars DISCORD_CLIENT_ID=...,DISCORD_CLIENT_SECRET=...,DISCORD_PUBLIC_KEY=...` (never `--set-env-vars`); (d) `npm run db:status` then `npm run db:migrate` to create the `discord_activity_rooms`/`discord_activity_events` tables (applies immediately, no dry run); (e) create a test Discord server, invite two accounts, open the Activity in a voice channel on both, and confirm both see the same prompt/generation/vote state (screenshots); (f) submit the Discovery listing using the exact copy in the submission file. | one Developer Portal app + one env update + one migration apply + one live two-account verification + one Discovery submission | Turns on the Discord Activity for real users; completes order 088's two-accounts-in-Discord Definition of Done line | [088-partners-05-discord-activity.md](../088-partners-05-discord-activity.md), [marketing/growth/submissions/discord-activity.md](../../marketing/growth/submissions/discord-activity.md) |+| 53 | **Reset or upgrade the Birdeye API plan (`birdeye-api-key` Secret Manager secret, used by `three-ws-api`).** Added 2026-10-13 by the triage-lane sweep (fifth pass): the deep sweep's `pump-price-history-upstreams-502` finding on `/api/pump/price-history` traced to Birdeye's OHLCV rung. Confirmed live: `curl -H "X-API-KEY: $BIRDEYE_API_KEY" -H "x-chain: solana" "https://public-api.birdeye.so/defi/ohlcv?..."` answers `{"success":false,"message":"Compute units usage limit exceeded"}` (HTTP 400). 5 occurrences of this exact message in the service logs over the last 24h, spaced roughly every 6 hours, meaning the plan's compute-unit allowance is exhausted well before each period rolls over. While Birdeye is out, affected mints fall back to GeckoTerminal alone (`api/_lib/birdeye.js`, `api/pump/price-history.js`); a mint with no cache yet on both rungs 502s cleanly rather than guessing. No in-repo code or config change raises a third-party compute-unit cap. | one plan upgrade decision | Keeps the pump.fun price-history chart populated from Birdeye instead of occasionally falling through to a 502 | [docs/ops/production-log-triage.md](../../docs/ops/production-log-triage.md) |Deleted 2026-09-01: the former row 5 (`WALLET_ENCRYPTION_KEY_PREVIOUS` policy), whichdeclared itself "delete on reading" and had outlived that by three weeks.