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(x-grok): log order 023, the connector probe passes locally and waits on a deploy for production OAuth
nirholascf3286879da4
diff --git a/prompts/finish/023-x-grok-01-connector-compat-probe.md b/prompts/finish/023-x-grok-01-connector-compat-probe.mdindex 533f1c3b2..0f15f3533 100644--- a/prompts/finish/023-x-grok-01-connector-compat-probe.md+++ b/prompts/finish/023-x-grok-01-connector-compat-probe.md@@ -1,5 +1,7 @@# x-grok 01: prove every hosted MCP server works as a Grok Bot connector+**Evolve status (2026-10-08).** Tasks 1 to 5 are shipped and verified: the probe, the npm script, the matrix in `docs/mcp.md`, both evidence captures, and the fixes with tests that fail without them (`7985f1cce`, `59bdf5707`, `be536043e`, `c3b56080f`, `e3009e6d3`, `c27821cb2`). Against local code the probe passes 7 of 7. Two Definition of done lines remain. (1) Production: `mcp-studio` and `pump-fun-mcp` exit 0 and every OAuth server answers 401 with `resource_metadata`, but the full `npm run probe:mcp-clients` still fails 4 of 7, because production (`fe2a8b24f`) predates the per-server OAuth resource fix. A deploy is owner-gated: row 25 of [production-100-OWNER-ACTIONS.md](_context/production-100-OWNER-ACTIONS.md). (2) `npm test` is red with 72 failures in 34 files that this order does not touch. Order [401](401-auto-restore-green-vitest.md) owns them. Once both are done, rerun the probe against production, commit the capture, and retire this order.+How to run: paste this file's repo path into a fresh Claude Code chat in this repository and say "run this work order". Runnable now, no gate. Run this first in lane A: every later lane A order assumes its matrix.## Operating clause (binding)diff --git a/prompts/finish/_context/production-100-OWNER-ACTIONS.md b/prompts/finish/_context/production-100-OWNER-ACTIONS.mdindex 52eed4b9b..0f2ba948f 100644--- a/prompts/finish/_context/production-100-OWNER-ACTIONS.md+++ b/prompts/finish/_context/production-100-OWNER-ACTIONS.md@@ -9,7 +9,7 @@ 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-08: rows 1 and 2 re-measured by the triage sweep, row 24 added for the paid Solana RPC credits; 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-08: 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 ||---|---|---|---|---|@@ -36,6 +36,7 @@ on it; some resolve themselves as other work lands.| 22 | **Decide whether to arm the three trading growth programs** (added 2026-09-29). Built, tested and disarmed: the big-win X poster (`BIG_WIN_X_ENABLED`, posts to @trythreews), the first-rug softener (`RUG_SOFTENER_ENABLED`, pays $THREE, default cap $25 per claim and $100 per day) and the early-leader bonus (`EARLY_LEADER_ENABLED`, pays $THREE, default 20 slots at $50 and $250 per week). Each is armed on its own. Steps: (1) `npm run db:status`, then `npm run db:migrate` for `20260929120000_growth_program_payouts.sql` (payout programs only); (2) set `THREE_PRIZE_PAYOUT_KEY` (unset on production as of 2026-09-29; the programs deliberately refuse the club treasury fallback, which is the economy master wallet) to a dedicated wallet holding the $THREE to cover the caps (payout programs only); (3) deploy; (4) read the dry run at `/api/ops/growth-programs`; (5) `gcloud run services update three-ws-api --region us-central1 --update-env-vars <FLAG>=1`. Measured 2026-09-29 against production data: nothing would be posted or paid today (no live win cleared the 0.1 SOL size gate, no first trade met the softener bar, no leader has a profitable 30-day record with followers). | one yes per program | Roadmap 917 items 3.8, 12.15, 13.4 | [docs/growth-programs.md](../../docs/growth-programs.md) || 23 | **Name the two $THREE receiver wallets** (added 2026-09-30). `/api/healthz` reports `three_token_rail` down and signed-in `POST /api/token/quote` answers `503 treasury_unavailable`, so no $THREE-priced purchase can be priced (Forge paid tiers, spins, scarcity mints, token marketplace sales, copy-trading fees). The quote signing key is done (`three-quote-secret`, wired on `three-ws-api-00466-85g`); only `THREE_TREASURY_WALLET` and `THREE_REWARDS_WALLET` remain. No revision ever held them, so there is nothing to restore. Candidates: treasury `wwwwwDxFWRn7grgr3Esrsg5C6NvDoDHSA4gaCffccrU` (x402 receiver, already holds a $THREE account), rewards `WwwuGbqHrwF5RG89KhUbmRWEvjnRH9k5kVM5p7T3WwW` (the economy master, which `REWARDS_DISTRIBUTOR_SECRET` signs as). The rewards candidate is also the buyback signer, so arming `THREE_BUYBACK_ENABLED` or `THREE_MICROBUY_ENABLED` would sweep the whole rewards pool into the treasury; decide that before arming either lane. Setting the two vars moves no funds by itself: `gcloud run services update three-ws-api --region us-central1 --update-env-vars THREE_TREASURY_WALLET=<treasury>,THREE_REWARDS_WALLET=<rewards>`. | two addresses | The whole $THREE purchase rail | [docs/money-map.md](../../docs/money-map.md#three-split-receivers-inbound-three) || 24 | **Top up the paid Solana RPC plans** (added 2026-10-08). Helius answers `429: max usage reached` on every call: 45,461 such lines on `three-ws-api` in the 24 hours to 2026-10-08 17:10 UTC, the oldest retained one from 2026-09-08. healthz reads `helius` degraded and `rpc_lanes` "all 2 paid lanes exhausted", so Solana traffic runs on throttled free nodes. That is the whole cause of `agent_index` reading down: 172 of the 176 erroring Solana cursors carry `solana rpc 429 @ public.rpc.solanavibestation.com`, the last free lane, and the rest are a free provider's own errors. No config change adds credits, and promoting the reserve lane is the documented wrong fix. Upgrade or top up the Helius plan (and the second paid lane), then confirm `helius` and `rpc_lanes` read ok on `curl -s https://three.ws/api/healthz`. | billing | Solana agent index freshness, balance reads, every on-chain route's latency | [docs/ops/production-log-triage.md](../../docs/ops/production-log-triage.md), "Every paid Solana RPC lane exhausted at once" |+| 25 | **Deploy so cloud MCP connectors can sign in to four hosted servers** (added 2026-10-08 by the evolve loop, x-grok order 023). Production (`fe2a8b24f`, revision `three-ws-api-00479-d7z`) still points every OAuth 401 at the root protected-resource document naming `/api/mcp`, so a stock MCP SDK client (Grok Bot, claude.ai connectors) refuses to start sign-in on `/api/mcp-3d`, `/api/mcp-agent`, `/api/mcp-bazaar` and `/api/ibm-mcp`. The fix is on `main` (`7985f1cce`, `59bdf5707`) and the probe passes all seven servers against local code. The submit gate also needs the pending `20261008150000_revenue_direct_settle_backfill.sql` applied first (`npm run db:status`, then `npm run db:migrate`), which is another session's payout backfill, so read it before applying. Then `npm run deploy:gcp:full`, then `npm run probe:mcp-clients -- --json prompts/x-grok/_generated/connector-probe.json`, which must print `all 7 servers passed`. | one deploy | Grok Bot and every OAuth connector on four servers; closes x-grok order 023 | [docs/mcp.md](../../../docs/mcp.md#client-compatibility), [prompts/x-grok/_generated/connector-probe.json](../../x-grok/_generated/connector-probe.json) |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.diff --git a/prompts/finish/_context/x-grok-PROGRESS.md b/prompts/finish/_context/x-grok-PROGRESS.mdindex 71150c223..c8a4f3661 100644--- a/prompts/finish/_context/x-grok-PROGRESS.md+++ b/prompts/finish/_context/x-grok-PROGRESS.md@@ -50,3 +50,12 @@ Cross-session handoff for the `x-grok-` orders ([x-grok-00-CONTEXT.md](x-grok-00- Shipped `3b60a4836`: `GROK_MODELS` in `api/_lib/chat-models.js` is the only place a Grok id is written (context, tools, vision, reasoning efforts, price, OpenRouter mirror, menu flag), with `GROK_RETIRED_ALIASES`, `GROK_DEFAULT_MODEL` (`grok-4.7`, BYOK default) and `GROK_BUDGET_MODEL` (`grok-4.3` with `reasoning_effort: none`, server backstop, previews, intent compilers). Consumers: `llm.js`, `brain/chat.js` (and through it `/api/v1/models` and the shared picker), `api/chat.js`, the embed proxy, `/api/v1` providers, the marketplace preview, both intent compilers, `llm-pricing.js`, and the three static pickers in `src/`. Guard: `tests/grok-model-literals.test.js`. Drift check: `npm run check:xai-models` (`scripts/check-xai-models.mjs`), documented in `docs/ops/llm-lanes.md`. Order file deleted in that commit.- Measured: no xAI key anywhere (`.env`, `.env.local`, `three-ws-api` env, Secret Manager), and `api.x.ai/v1/models` answers 401 without one, so the catalog and the drift check ran against xAI's public docs (`docs.x.ai/developers/models.md` plus per-model pages, fetched fine). xAI retired `grok-4-1-fast-*` and seven other slugs on 2026-05-15 and redirects them to `grok-4.3`; our `grok-4.1-fast` default had been a retired slug since then. Current text models: 4.7, 4.6, 4.5, 4.3, 4.20 reasoning, 4.20 non-reasoning, 4.20 multi-agent (Responses API only, catalogued but never routed), Build 0.1. `check:xai-models` reports in sync against the docs.- For order 927: once `GROK_API_KEY` exists, run `npm run check:xai-models -- --source=api` to diff against the account's live list (adds price and reasoning-effort checks from the API).++## 2026-10-08: order 023 (connector compatibility probe) built, production line waits on a deploy (order file kept)++- An earlier session had already shipped the probe, the npm script and the matrix (`62903ced4`, `f2e42a064`). It also shipped the OAuth fix for the one failure class the probe found (`7985f1cce`, `59bdf5707`). That failure: every protected server pointed its 401 at the root metadata naming `/api/mcp`, so the MCP SDK's `checkResourceAllowed` refused sign-in on `mcp-3d`, `mcp-agent`, `mcp-bazaar` and `ibm-mcp`.+- This session: `be536043e` makes the binding test resolve metadata URLs through the real `vercel.json` route table. Before, the test emulated the route with a regex, so deleting the RFC 9728 rewrite left it green. It now fails 14 cases without the rewrite. `c3b56080f` removes the dashes from the 3D and IBM 402 descriptions and names all 33 agent-wallet tools in its challenge metadata, which fixes `mcp-agent-challenge.test.js`. `e3009e6d3` makes the probe store a compact error summary instead of whole 402 envelopes. `c27821cb2` documents local probing and refreshes both captures.+- Measured: production 3 of 7 pass; only the four OAuth resource mismatches fail. On production, API-key mode works on all seven servers, `mcp-studio` and `pump-fun-mcp` work anonymously, and every protected server answers 401 with `resource_metadata`. Local code passes 7 of 7.+- Local probing needs the API server beside Vite. Plain `npm run dev` proxies `/api` and `/.well-known` to production, so `--base http://localhost:3000` silently measures production. The commands are now in `docs/mcp.md`.+- Remaining: (1) a deploy, gated behind the pending `20261008150000_revenue_direct_settle_backfill.sql` (owner row 25), then a production rerun that must print `all 7 servers passed`; (2) a green `npm test`, owned by order 401 (72 failures in 34 files, none new from this order, one fewer after `c3b56080f`).+