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(store-submissions): record the 2026-09-09 re-verification in the tracker

nirholas2265e118de34
diff --git a/prompts/store-submissions/_generated/TRACKER.md b/prompts/store-submissions/_generated/TRACKER.md
index 646c45678..f59dd6df3 100644
--- a/prompts/store-submissions/_generated/TRACKER.md
+++ b/prompts/store-submissions/_generated/TRACKER.md
@@ -38,6 +38,19 @@ Three consequences, all reproduced live today rather than inferred:
fails open: rung 1 (Vertex Gemini) is 403 on the billing hold and rung 2 (the free NVIDIA NIM
VLM) returned 504, so `runQualityGate` answers `qa_available:false` and the router correctly
ships what it has. The degenerate slab reaches the caller with `score 0.976 / flag ok`.
+
+ **Re-measured 2026-09-09 (task 07), and rung 2 is not dead.** The scorer half re-verified on 40
+ consecutive production generations: 4 planar flags, 4 of 4 escalating, 0 false escalations on the
+ flatness rule. On the QA half, one live generation at 15:04Z scored **through** the NVIDIA rung
+ and returned a full verdict (`provider: nvidia`,
+ `model: meta/llama-3.2-11b-vision-instruct`, `score 85`, and a real observation: *"the glass shade
+ is slightly too green"*). A second generation two minutes earlier failed open on the Vertex 403.
+ So rung 2 is intermittent, not down, and the 504 reading above is no longer true in general. Two
+ consequences: the billing hold is still the fix that makes escalation deterministic, and until it
+ clears the exposure is a **fraction** of generations rather than all of them. Note also that the
+ chain used to report only the FIRST rung's error, so every outage read as "Vertex 403" and rung
+ 2's own failure was never recorded anywhere; that is fixed (`60111ab16`) and the next reading of
+ this section will be able to say why the fallback lost.
2. **The free lane is slow, not broken.** `forge_free` completed in **147s** with a real
3,674,712-byte GLB. That is the NIM 504 plus fallback latency, not the 2026-07-08 hang.
3. **The OpenRouter rungs are separately misconfigured**, independent of billing: five model IDs
@@ -74,7 +87,7 @@ There are **six** MCP gates, not four: `audit:mcp`, `audit:mcp-golden`, `audit:m
| **Claude Connectors Directory** | ready-to-submit (pending the human items) | `POST /api/mcp tools/list` unauthenticated returned **200 with 53 tools in 0.10s**; `initialize` likewise. `GET /.well-known/oauth-protected-resource` 200 with 13 scopes. `/legal/privacy`, `/legal/tos`, `/support`, `/docs/mcp` all 200, and privacy still carries the "MCP Connectors, AI Processing & Payments" section. | The 2026-06-28 blocker that discovery was auth-gated is **resolved and no longer true**: the portal can sync tools with no credential. Remaining: `[HUMAN: Team/Enterprise org + Owner role, or use the public form]` and `[HUMAN: generate a real MCP_REVIEW_SECRET and decide which vendor credentials a reviewer gets]`. Note the 147s free-lane latency above before demoing live. |
| **Claude plugin marketplace** | ready-to-submit | `.claude-plugin/marketplace.json` carries 4 plugins (`three-ws-core`, `three-ws-developer`, `three-ws-pump-fun`, `three-ws-3d`). The end-to-end CLI install evidence from 2026-07-08 stands in `_generated/claude-plugin-marketplace-e2e.md` and was not re-driven today. | `[HUMAN: submit via https://platform.claude.com/plugins/submit per marketplace/plugins/three-ws-3d/SUBMISSION.md]` |
| **Claude Agent Skills pack** | ready-to-submit | `node scripts/build-skills-pack.mjs --check` → `skills-pack manifest up to date (42 skills)`; `.agents/skills/` holds 44 entries. | None in code. The live free-lane E2E it wanted is now green but slow (147s, see above). |
-| **OpenAI App Directory** | blocked (B3, infrastructure) | Free studio surface re-verified live: `initialize` 200, `tools/list` **11 tools**, `resources/list` **2 widget resources** (`ui://widget/three-studio-model.html`, `ui://widget/three-studio-persona.html`), `/.well-known/3d-studio-openapi.yaml` and `/.well-known/ai-plugin.json` both 200, and a real keyless `forge_free` returned a 3.67 MB GLB whose `/viewer?src=` link returned 200. | **B3 is now understood and is NOT a code gap.** The scorer flags the slab correctly; vision QA cannot run because Vertex is 403 on the billing hold and the NIM fallback 504s. Clearing the hold, then one clean re-verification generation, unblocks the submission. `[HUMAN: clear the GCP billing hold]` then `[HUMAN: final submit in the partner portal]`. |
+| **OpenAI App Directory** | blocked (B3, infrastructure) plus an unshipped deploy | Whole surface re-verified live 2026-09-09: `initialize` 200 keyless, `tools/list` **11 tools** each with its four `openai/*` annotations and correct `outputTemplate`, `resources/list` **2 widget resources** with `widgetCSP`/`widgetDescription`/`widgetDomain`, `/.well-known/3d-studio-openapi.yaml` (Redocly-clean, free-only, all inner URLs 200) and `/.well-known/ai-plugin.json` both 200, `/legal/privacy` + `/legal/tos` 200, a real keyless `forge_free` returned a 5.40 MB GLB in 137s whose `/viewer?src=` returned 200, `POST/GET /api/3d/studio` polled to a real GLB, `/api/ar` correct per device class, and the widget drove through empty/loading/ready/error in a `window.openai`-less browser. Every one of those payloads scanned clean of crypto, payment and internal ids. | **B3 is narrower than it looked.** The scorer fix IS deployed (revision `three-ws-api-00420-ljh`) and re-measuring it on 40 consecutive production generations gave 4 planar flags, 4/4 escalating. The fallback rung is also **not** dead: a 15:04Z generation scored through the free NVIDIA vision lane with a full verdict, so "the NIM fallback 504s" no longer holds in general. Vertex is still 403 on the billing hold, and the gate fails open, so escalation stays non-deterministic until the hold clears. Four fixes from this pass are in the tree and unshipped (widget CORS routing, honest pending ETA, failover-error reporting, 14 reviewer-visible em-dashes). `[HUMAN: clear the GCP billing hold]`, `[HUMAN: deploy the tree]`, then `[HUMAN: final submit in the partner portal]`. |
| **OpenAI GPT Store** | live, with a duplicate to remove | `https://chatgpt.com/g/g-6a563a3b49a88191abf346245491a444-three-ws-3d-studio` returns 200 logged-out. The old draft `g-6a5672fbf3f48191b559e482c7fcbf51` **301s to a 200 page titled "ChatGPT - three.ws 3D Studio"**, so the 2026-09-02 escalation stands: two public GPTs share one name. | `[HUMAN: delete the draft duplicate in My GPTs]` (no API for it) |
| **Official MCP Registry** | ready-to-submit | `node prompts/store-submissions/_generated/build-registry-republish.mjs` against the live registry, after the pagination fix below: **3 servers need a publish (0 stale, 3 new: `herald-mcp`, `knock-mcp`, `home-mcp`), 47 are already current**, including all 7 hosted remotes. Cross-checked with `node scripts/publish-mcp-servers.mjs --dry-run`, which agrees. The batch is staged in `_generated/mcp-registry-republish.sh` and was NOT run. | `[HUMAN: mcp-publisher login github, then review and run the staged batch]` |
| **Smithery** | ready-to-submit | `_generated/mcp-directories/smithery.md` regenerated today from the corrected canonical source; it now covers **50 servers (7 remote + 43 stdio)**. | `[HUMAN: create/claim the Smithery account]` |