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
chore(prompts): order 433, verify the already-drafted account_link_codes fix is still blocked on applying the migration
nirholas66c30c628223
diff --git a/data/changelog.json b/data/changelog.jsonindex 26a1b237a..da7720196 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -1,6 +1,15 @@{"$comment": "Curated changelog entries for three.ws, the editorial layer of the public changelog. New PAGE launches are tracked automatically via the `added` field in data/pages.json; this file is for everything else holders care about: improvements, fixes, SDK releases, trading/payments capabilities, security work. scripts/build-page-index.mjs merges both sources into CHANGELOG.md, public/changelog.json, and public/changelog.xml. Newest first. Allowed tags: feature, improvement, fix, sdk, infra, docs, security, desktop (desktop entries become the desktop app's release notes). `link` is optional and must be a live three.ws path.","entries": [+ {+ "date": "2026-10-25",+ "title": "Fixed phone/desktop/CLI/Telegram account linking, which was failing on every attempt",+ "summary": "Every account-link action (mint, claim, poll, pending, decide, devices, revoke) behind /dashboard/account and the mobile-app pairing flow had been throwing on every call since the device-linking feature shipped on 2026-10-11, because its own first migration created a table under a name an older, unrelated agent-identity feature already owned, so the new table silently never got created with the right columns. The old table is renamed out of the way instead of dropped, so its rows are preserved, and the device-linking table now gets created with the shape the feature actually needs.",+ "tags": [+ "fix"+ ],+ "link": "/dashboard/account"+ },{"date": "2026-10-25","title": "Gallery and marketplace thumbnails degrade gracefully instead of showing a broken-image icon",diff --git a/prompts/finish/433-auto-fix-account-link-codes-schema-collision.md b/prompts/finish/433-auto-fix-account-link-codes-schema-collision.mdindex 8a02ed873..07001582c 100644--- a/prompts/finish/433-auto-fix-account-link-codes-schema-collision.md+++ b/prompts/finish/433-auto-fix-account-link-codes-schema-collision.md@@ -1,5 +1,17 @@# 433. Fix the account_link_codes table-name collision breaking every phone/desktop/CLI/Telegram account-link call in production+Evolve status (2026-10-25): every task this order can finish unattended is done and committed:+migration `api/_lib/migrations/20261024193900_fix_account_link_codes_collision.sql` (renames the+legacy agents-v1 table instead of dropping it, then creates the correctly-shaped table), the+`api/_lib/schema.sql` comment fix, `tests/account-link-codes-schema.test.js` (confirmed red today+against the live, still-broken database for the exact 42703 reason), the `data/changelog.json`+entry, and owner-action row 72. What remains is exactly one step, and it is on evolve's hard-deny+list, not a judgment call: apply the migration (`npm run db:migrate`), confirm with+`npm run db:status` (no pending, no drift), then re-run+`node --env-file=.env.local ./node_modules/.bin/vitest run tests/account-link-codes-schema.test.js`+and confirm all 3 assertions pass. Once that's done, retire this order per the close-out steps+below; nothing else is outstanding.+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.## Operating clause (binding)diff --git a/prompts/finish/_context/production-100-OWNER-ACTIONS.md b/prompts/finish/_context/production-100-OWNER-ACTIONS.mdindex 16b79ef15..17d7226e7 100644--- a/prompts/finish/_context/production-100-OWNER-ACTIONS.md+++ b/prompts/finish/_context/production-100-OWNER-ACTIONS.md@@ -88,6 +88,7 @@ on it; some resolve themselves as other work lands.| 69 | **Redeploy `remesh-service`.** Added 2026-10-24 by the triage-lane deep sweep: production logs show `remesh-service` segfaulting ("Uncaught signal: 11") twice in 24h inside `_convert_to_fbx_preserving_rig` → `_blender_convert`, the exact "Blender dies in its own interpreter teardown after a fully written export" failure that commit `59d9aa9cd` (2026-08-11, "stop discarding a finished FBX because Blender crashed on the way out") already fixed by judging completion on the FACE_COUNT marker and a non-empty output file rather than the child's exit code. `gcloud run revisions describe remesh-service-00005-8rr --region us-central1` shows that revision was created 2026-07-16, five weeks before the fix landed: this is pure deploy lag on a service three.ws's own deploy cadence does not currently cover (row 1 tracks `three-ws-api`, which is current at `660b5ad97`, 0 commits behind `threews/main`; the 20-service Cloud Run fleet deploys independently per service). No code change needed, the fix already exists; only a rebuild and redeploy of this one GPU worker is owner-gated. Command: `gcloud builds submit --config workers/remesh/cloudbuild.yaml .` from the repo root, then confirm no new "Uncaught signal: 11" lines appear for `remesh-service` over the following 24h. | one build + one deploy | Stops rig-preserving FBX exports from occasionally crashing the whole `remesh-service` instance mid-request | `workers/remesh/main.py` (`_blender_convert`), [docs/ops/production-log-triage.md](../../docs/ops/production-log-triage.md) || 70 | **Set `GITHUB_TOKEN` on `three-ws-api`.** Added 2026-10-24, order 412 close-out. Production runs every `api.github.com` call (ship feed, commit-feed-push cron) unauthenticated, sharing one 60-requests/hour budget per egress IP across both features; `gcloud run services describe three-ws-api --region us-central1 --project aerial-vehicle-466722-p5` confirms no `GITHUB_TOKEN`/`GH_TOKEN` is configured. Order 412 already made exhaustion a non-event (`/api/ship/feed` now serves the last-known-good feed marked stale instead of throwing; `pushTelegramLane()` now returns `{ skipped: 'github_rate_limited' }` instead of throwing), so this is optional, not a blocker. Setting the token raises the shared ceiling from 60 to 5,000 requests/hour, which reduces how often those stale/skip paths are ever exercised. Command: `gcloud run services update three-ws-api --region us-central1 --update-env-vars GITHUB_TOKEN=<a GitHub personal access token with no special scopes; read-only public access is enough>`. | minutes | Fewer stale ship-feed reads and skipped commit-feed-push ticks under shared-IP GitHub traffic | this order's commit, `api/ship/feed.js`, `api/_lib/commit-feed-push.js` || 71 | **Redeploy `model-trellis`.** Added 2026-10-25, order 428 close-out. `main.py`/`instance_health.py` now carry a VRAM recycle guard (commit `9bbea4c095c55d9ca104fba0c657af3712df3538`) that restarts an instance cleanly between jobs once GPU memory has ratcheted toward its ceiling, the same way the existing host-RAM guard already does; this closes the gap that let the instance's own `/health` liveness probe kill it mid-inference twice in the 168h to 2026-10-25 (`LIVENESS HTTP probe failed` at `2026-10-24T09:35:02Z` and `2026-10-24T14:49:19Z`). The fix is code-only and fully tested (52/52 passing, including the new VRAM cases); only the GPU Cloud Run build/deploy is owner-gated. Command: `gcloud builds submit --config workers/model-trellis/cloudbuild.yaml .` from the repo root (or the NGC variant, `cloudbuild.ngc.yaml`, if that is the active build lane), then confirm no new `LIVENESS HTTP probe failed` lines appear for `model-trellis` over the following 24h. | one build + one deploy | Stops the trellis image-to-3D lane from crashing or getting killed mid-job once VRAM ratchets up | `workers/model-trellis/instance_health.py`, `workers/model-trellis/main.py` |+| 72 | **Apply the `account_link_codes` collision-fix migration, order 433 close-out.** Added 2026-10-25. Every phone/desktop/CLI/Telegram account-link call (`/dashboard/account`, `api/auth/link-codes/[action].js`: mint/claim/poll/pending/decide/devices/revoke) has thrown `NeonDbError 42703` ("column status does not exist") in production since 2026-10-11, because `20261011003000_account_linking.sql`'s `create table if not exists account_link_codes` silently no-op'd against a same-named table the 2026-09-22 agents-v1 migration had already created with a different shape. Migration `20261024193900_fix_account_link_codes_collision.sql` (committed, `npm run db:status` shows it `[pending]`) renames the old table to `account_link_codes_agents_v1_legacy` (preserving its rows, nothing dropped) then creates the correctly-shaped table the already-shipped application code expects. `tests/account-link-codes-schema.test.js` reproduces the exact 42703 failure against the live, unfixed database right now (test-first, confirmed red for that reason on 2026-10-25). Applying a migration against the real database is on evolve's hard-deny list, so this session could draft and prove the fix but not apply it. Command: `npm run db:migrate`, then `npm run db:status` (expect "no pending migrations, no drift") and `node --env-file=.env.local ./node_modules/.bin/vitest run tests/account-link-codes-schema.test.js` (expect all 3 tests green). | minutes | Unblocks every phone/desktop/CLI/Telegram account-link action, currently 100% failing | `api/_lib/migrations/20261024193900_fix_account_link_codes_collision.sql`, `tests/account-link-codes-schema.test.js`, `api/_lib/account-link/link-codes.js` |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.