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(ops): add owner-action rows for the two best3d 069 GPU deploys

nirholasf10073da878f
diff --git a/prompts/finish/_context/production-100-OWNER-ACTIONS.md b/prompts/finish/_context/production-100-OWNER-ACTIONS.md
index 192dd58c5..8c1fc5223 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 `produ
Rows carry the date they were added so staleness is visible. Re-verify a row before acting
on it; some resolve themselves as other work lands.
-## Open rows (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-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 |
|---|---|---|---|---|
@@ -50,6 +50,8 @@ on it; some resolve themselves as other work lands.
| 37 | **Ship the cron time-budget fix with the next deploy** (added 2026-10-11 by the evolve loop, order 403, otherwise complete and retired). `wrapCron()` in `api/_lib/http.js` now races every cron handler against a real time budget (`maxDurationMs`, wired from each handler's own `export const maxDuration * 1000`, defaulting to 120000ms) and answers a clean `503 { reason: 'cron_timeout' }` instead of hanging until Cloud Run's blind 900s ingress kill, which is what `/api/cron/x402-ring-leak-scan` was hitting repeatedly before order 400 landed its own fix. Verified locally: a real `http.createServer` hosting `wrapCron` with an 800ms budget and a never-resolving handler answered `503 cron_timeout` at 0.809s (not 900s, not instantly); the new `tests/http-cron-timeout.test.js` (4 tests) and the added `wrapCron` case in `tests/http-db-unavailable-boundary.test.js` pass 10/10, and the timeout test was proven red (indefinite hang) against the pre-fix code via a path-scoped `git stash` before the fix landed. No migration, no env var, nothing else needed; this is a pure code fix sitting on `evolve` waiting for row 1's routine deploy cadence to carry it to `main` and production. Ship with `npm run deploy:gcp:full` (row 1 already tracks the general "approve the next deploy" gate; this row exists only so the new behavior is named for verification). Post-deploy verification: re-run the step 0 query from `prompts/finish/403-auto-cron-timeout-enforcement.md` (`gcloud logging read 'resource.type="cloud_run_revision" resource.labels.service_name="three-ws-api" textPayload:"maximum request timeout"' --freshness=24h --project aerial-vehicle-466722-p5`) after the deploy window; a healthy rollout shows that query going quiet (or near-quiet) while `textPayload:"exceeded its"` picks up any genuine stuck cron with its name attached, cross-referenced against order 400's `x402-ring-leak-scan` fix so a recurrence is distinguished from a different handler entirely. | one deploy (already covered by row 1's cadence) | Clean, diagnosable cron timeouts platform-wide instead of a blank "maximum request timeout" | `docs/ops/production-log-triage.md`, "HTTP timeout with no cron context" section |
| 38 | **Deploy `model-trellis2` (the TRELLIS.2 GPU worker), then point `MODEL_TRELLIS2_URL` at it** (re-measured 2026-10-11 by the evolve loop, best3d order 067, built and tested on 2026-10-09, not yet deployed). `workers/model-trellis2/` is complete (Dockerfile, `cloudbuild.yaml` pinned to `three-ws-build@`, 64 of 65 local tests passing, 1 skipped), the Forge lane registry already makes `trellis2` the default image-to-3D backend with the old chain (`trellis_selfhost`, `hunyuan3d`, `trellis`, `modly`, `triposg`) as failover, and the territory router already keeps the EU, the UK and South Korea off every Tencent lane regardless. Confirmed live today: `gcloud run services describe model-trellis2 --region us-central1` answers "Cannot find service", and `three-ws-api`'s env has no `MODEL_TRELLIS2_URL`, so the registry's default lane is currently unreachable and every image-to-3D request falls through to the next lane in the chain, same as the 2026-10-09 measurement. This is a production deploy (new Cloud Run GPU service, gate 2), so no agent runs it. Commands, in order: `gcloud builds submit --config workers/model-trellis2/cloudbuild.yaml --region us-central1 --project aerial-vehicle-466722-p5 .` from the repo root, then `gcloud run services update three-ws-api --region us-central1 --update-env-vars=MODEL_TRELLIS2_URL=<service-url>` (never `--set-env-vars`, which replaces the whole set). After that, run one real image-to-3D generation and confirm the `forge_creations` row for it shows `backend: 'trellis2'`, and validate the returned GLB with `packages/glb-tools`; both are the two remaining Definition of done lines in the order file. | one build + one env update + one test generation | Closes best3d order 067; makes TRELLIS.2 (MIT, EU/UK/KR-safe) the live default instead of the untested fallback chain | [067-best3d-01-trellis2-default-lane.md](../067-best3d-01-trellis2-default-lane.md), [best3d-PROGRESS.md](best3d-PROGRESS.md) |
| 39 | **Deploy `model-pixal3d` (the Pixal3D fidelity-lane GPU worker), then point `MODEL_PIXAL3D_URL` at it** (added 2026-10-11 by the evolve loop, best3d order 068, built and tested same day). `workers/model-pixal3d/` is complete (Dockerfile, `cloudbuild.yaml` pinned to `three-ws-build@`, 81 of 82 local tests passing, 1 skipped), `api/forge.js`/`api/_lib/forge-tiers.js`/`api/_providers/gcp.js` already register and wire the `pixal3d` backend (1-4 photos, `view_labels`, `fill_other_sides`, opt-in only: never a named default or a failover target), and `src/forge.js`/`pages/forge.html` already ship the "Match my photo" engine button and panel. Confirmed live today: `gcloud run services describe model-pixal3d --region us-central1` answers "Cannot find service", and `three-ws-api`'s env has no `MODEL_PIXAL3D_URL`, so the lane reports `backend_unconfigured` today and the engine button does not render in the catalog (verified against a synthetic catalog entry in a local browser session, since the real worker isn't deployed yet). This is a production deploy (new Cloud Run GPU service, gate 2), so no agent runs it. Commands, in order (from `workers/model-pixal3d/README.md`): `workers/model-pixal3d/stage_weights.sh` (one time, idempotent weight mirror), then `gcloud builds submit --config workers/model-pixal3d/cloudbuild.yaml --region us-central1 --project aerial-vehicle-466722-p5 --substitutions=SHORT_SHA=manual$(date +%s) .` from the repo root, then `gcloud run services update three-ws-api --region us-central1 --update-env-vars MODEL_PIXAL3D_URL=$(gcloud run services describe model-pixal3d --region us-central1 --format='value(status.url)')` (never `--set-env-vars`, which replaces the whole set). After that, run one real 3-image generation with `backend: "pixal3d"` and confirm the `forge_creations` row records all three input URLs and the returned GLB is valid; that is the order's last unverified Definition of done line. | one weight stage + one build + one env update + one test generation | Closes best3d order 068; makes "Match my photo" (pixel-aligned fidelity to the caller's own photos, MIT + Apache-2.0) live in the Forge engine grid | [068-best3d-02-pixal3d-multiview.md](../068-best3d-02-pixal3d-multiview.md), [best3d-PROGRESS.md](best3d-PROGRESS.md) |
+| 40 | **Deploy `model-rig-nonhuman` (the UniRig+SkinTokens non-humanoid rigging worker), then point `RIG_NONHUMAN_URL` at it from `model-rig`** (added 2026-10-11 by the evolve loop, best3d order 069, built and tested same day). `workers/rig-nonhuman/` is complete (Dockerfile, `cloudbuild.yaml` pinned to `three-ws-build@`, its own test suite passing locally with no GPU). This is an additional GPU service alongside the existing `model-rig`, not a replacement, so budget it against the per-region L4 quota in `docs/ops/gcp-credits-plan.md` before deploying. This is a production deploy (new Cloud Run GPU service, gate 2), so no agent runs it. Commands, in order (from `workers/rig-nonhuman/README.md`): `bash workers/rig-nonhuman/stage-assets.sh` (one time, stages UniRig's skeleton checkpoint, SkinTokens' two checkpoints, and the Qwen3-0.6B config/tokenizer SkinTokens was fine-tuned from), then `gcloud builds submit --config workers/rig-nonhuman/cloudbuild.yaml --substitutions=SHORT_SHA=manual$(date +%s) .` from the repo root, then `gcloud run services update model-rig --region us-central1 --update-env-vars RIG_NONHUMAN_URL=$(gcloud run services describe model-rig-nonhuman --region us-central1 --format='value(status.url)')` (never `--set-env-vars`, which replaces the whole set). `RIG_NONHUMAN_URL` is unset by default, so until that last command runs, 100% of `model-rig` traffic stays on the pre-existing humanoid-only path; deploying the new service alone changes nothing. After wiring, run one real non-humanoid mesh (a creature or prop) through `POST /api/forge?action=rig` and confirm the response GLB is skinned with a valid skeleton. | one weight stage + one build + one env update + one test generation | Closes best3d order 069 task 1; lets `model-rig` rig creatures, props and vehicles instead of leaving them unrigged | [069-best3d-03-rig-anything.md](../069-best3d-03-rig-anything.md), [best3d-PROGRESS.md](best3d-PROGRESS.md) |
+| 41 | **Deploy `model-anigen` (the AniGen rig-on-generation GPU worker), then point `MODEL_ANIGEN_URL` at it** (added 2026-10-11 by the evolve loop, best3d order 069, built and tested same day). `workers/model-anigen/` is complete (Dockerfile, `cloudbuild.yaml` pinned to `three-ws-build@`, its own test suite passing locally with no GPU), and `api/forge.js`/`api/gpt-forge.js`/`api/_lib/forge-tiers.js`/`api/_providers/gcp.js`/`src/forge.js` already register and wire the `anigen` backend end to end (single reference image, opt-in only: never a named default or a failover target, catalog `rigged: true` flag, poll response `rigged`/`joint_count` fields, "Rig on generate" engine-grid label). Confirmed live today: `gcloud run services describe model-anigen --region us-central1` answers "Cannot find service", and `three-ws-api`'s env has no `MODEL_ANIGEN_URL`, so the lane reports `backend_unconfigured` today. This is a production deploy (new Cloud Run GPU service, gate 2), so no agent runs it. Commands, in order (from `workers/model-anigen/README.md`): `bash workers/model-anigen/stage-assets.sh` (one time, stages the AniGen checkpoints under `gs://three-ws-model-weights/anigen/`), then `gcloud builds submit --config workers/model-anigen/cloudbuild.yaml --substitutions=SHORT_SHA=manual$(date +%s) .` from the repo root, then `gcloud run services update three-ws-api --region us-central1 --update-env-vars MODEL_ANIGEN_URL=$(gcloud run services describe model-anigen --region us-central1 --format='value(status.url)')` (never `--set-env-vars`). After that, run one real single-image generation with `backend: "anigen"` and confirm the `forge_creations` row's result reports `rigged: true` and a `joint_count`, and that the returned GLB is a valid, already-skinned asset. | one weight stage + one build + one env update + one test generation | Closes best3d order 069 task 2; makes the "Rig on generate" lane (mesh, skeleton and skin weights in one pass, no vendor cost) live in the Forge engine grid | [069-best3d-03-rig-anything.md](../069-best3d-03-rig-anything.md), [best3d-PROGRESS.md](best3d-PROGRESS.md) |
Deleted 2026-09-01: the former row 5 (`WALLET_ENCRYPTION_KEY_PREVIOUS` policy), which
declared itself "delete on reading" and had outlived that by three weeks.