Skip to content

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.

docs(claude): correct the cron count to 145 and log the integrate 33 X guest reader status and what remains

nirholasef3393a78495
diff --git a/CLAUDE.md b/CLAUDE.md
index b5a33200b..cfc7302ab 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -205,7 +205,7 @@ Production deploys need owner approval (gate 2) unless the current instruction i
- Frontend: vanilla JS modules + Vite (`npm run dev`, port 3000).
- 3D: Three.js with glTF/GLB.
- Backend touchpoints: serverless-style handlers in `api/`, workers in `workers/`.
-- **Production runs on Google Cloud Run, NOT Vercel** (migrated 2026-07-07 after Vercel disabled the deployment). One container ([server/index.mjs](server/index.mjs)) serves the static frontend, the vercel.json route table, and all `api/**` handlers; the crons (140 as of 2026-10-23, see vercel.json) run on Cloud Scheduler. `vercel.json` is a LIVE config file: `server/index.mjs` reads its `routes` array on boot (split at the `{handle:"filesystem"}` marker into pre- and post-filesystem phases), and `scripts/create-gcp-scheduler.mjs` reads its `crons` array to sync Cloud Scheduler jobs. The server itself never reads `crons`. Never delete `vercel.json` as a leftover. GCP builds/deploys must pin the `three-ws-build@` (build) and `three-ws@` (runtime) service accounts; the project's default compute SA was deleted. Deploys: see the "Deploy runbook" section above.
+- **Production runs on Google Cloud Run, NOT Vercel** (migrated 2026-07-07 after Vercel disabled the deployment). One container ([server/index.mjs](server/index.mjs)) serves the static frontend, the vercel.json route table, and all `api/**` handlers; the crons (145 as of 2026-10-23, see vercel.json) run on Cloud Scheduler. `vercel.json` is a LIVE config file: `server/index.mjs` reads its `routes` array on boot (split at the `{handle:"filesystem"}` marker into pre- and post-filesystem phases), and `scripts/create-gcp-scheduler.mjs` reads its `crons` array to sync Cloud Scheduler jobs. The server itself never reads `crons`. Never delete `vercel.json` as a leftover. GCP builds/deploys must pin the `three-ws-build@` (build) and `three-ws@` (runtime) service accounts; the project's default compute SA was deleted. Deploys: see the "Deploy runbook" section above.
- **Env-var trap:** `vercel env pull` returns EMPTY for secret-type vars. Never trust a Vercel env export as complete. Production env lives on the Cloud Run service (`gcloud run services describe/update three-ws-api --region us-central1`).
- Solana/agent SDKs in `sdk/`, `solana-agent-sdk/`, `agent-payments-sdk/`.
- Real APIs in use: Pump.fun feed, Solana RPC, OpenAI/Anthropic via worker proxies. Never mock these.
diff --git a/_context/integrate-PROGRESS.md b/_context/integrate-PROGRESS.md
index ce634e8ec..12ccecb08 100644
--- a/_context/integrate-PROGRESS.md
+++ b/_context/integrate-PROGRESS.md
@@ -6,3 +6,11 @@
- Rescue: `scripts/rescue-wallet.mjs` and `packages/avatar-agent-mcp/src/lib/atomic-rescue.js` (dry run default, `--execute` gated). Landed in 22a5a1f49.
- Runbook `docs/ops/wallet-rescue.md`, alarm link in `api/cron/wallets-leak-scan.js`, docs index, STRUCTURE row, changelog entry: see the commit that deletes `prompts/finish/546-integrate-47-wallet-rescue-dry-run.md`.
- Dry run was executed against a local solana-test-validator wallet set (devnet faucet was rate limited), not devnet.
+
+## 2026-10-23: integrate 33, keyless X guest read rung (not closed)
+
+- Built: `api/_lib/x-guest/` (guest-token reader, NOTICE, README), rung 2 in `src/kol/x-profile.js`, `api/_lib/oracle/x-account.js` (coin X account age and followers into `social.xAccount`), `api/_lib/oracle/social-feed.js`, `api/cron/oracle-social-ingest.js` plus its `vercel.json` cron (every 10 min), docs, STRUCTURE row, changelog. The code landed inside other agents' sweep commits (22a5a1f49, 2b7bb3921); the cron-count fix in CLAUDE.md is the commit that touches this entry.
+- Verified: vitest on x-guest, kol-leaderboard, oracle sources and sources-assemble, 41 passing (run from an isolated install, see below). Live with the bearer unset: `fetchXProfile` returned followers with source `x-guest`; the cron read a real timeline and exited 200.
+- Not verified, so prompts/finish/532 stays: (1) `curl /api/kol/tracker` and (2) the cron writing `oracle_narrative` rows both need the server and a database; this checkout has no `DATABASE_URL` and `node_modules` could not boot `server/index.mjs`. Owner of the remainder: whoever has the DB env, run `node server/index.mjs` with `--env-file`, hit `/api/kol/tracker`, then the cron.
+- `npm run build:pages` currently fails on another agent's changelog entry ("See whether our X posts move $THREE") which uses `tag` instead of `tags`.
+- Incident: my `npm ci` raced about 35 concurrent npm processes and left the shared `node_modules` incomplete (vitest, lru-cache missing). Run `npm ci` once when no other agent is installing.