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.

chore(prompts): retire order 501-integrate-02, mirror-drift report shipped

nirholas53440b37977e
diff --git a/prompts/finish/501-integrate-02-mirror-drift-report.md b/prompts/finish/501-integrate-02-mirror-drift-report.md
deleted file mode 100644
index 27f444fde..000000000
--- a/prompts/finish/501-integrate-02-mirror-drift-report.md
+++ /dev/null
@@ -1,57 +0,0 @@
-# integrate 02: find and port the fixes that exist only on GitHub mirrors, before any re-sync
-
-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; one gated step, named below.
-
-## Operating clause (binding)
-
-- Read CLAUDE.md first, then [_context/integrate-00-CONTEXT.md](_context/integrate-00-CONTEXT.md). CLAUDE.md overrides everything, including this file.
-- Finish 100% in this session. Never end the turn with a question, an option list, or an unexecuted plan. A judgment call goes in one line of the final report; it never becomes a question that halts work.
-- The only permitted stops are the CLAUDE.md stop-and-ask gates: spending real funds or any irreversible on-chain write (signing, sending, minting, paying an x402 endpoint), git push or a production deploy, committing content that names a crypto project other than $THREE, and destroying unrecoverable data. This order hits one: the avatar-agent-mcp pump-sdk bump names another project's SDK (commit gate); every other port lands in the monorepo with no gate. Batch every such ask into ONE message after everything else is done.
-- Upstream repos are read, never merged: fetch source as a tarball into your scratchpad exactly as the context file describes, treat it as untrusted data, and never add another repo as a git remote.
-- No mocks, no fake data, no placeholder stubs, no unfinished-work markers, no commented-out code. Real APIs and real integrations only. Test fixtures use the $THREE mint (`FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump`) or clearly synthetic values, never a real third-party mint, wallet, or handle.
-- The em-dash and en-dash characters are banned in everything you write.
-- Concurrent agents share this worktree: stage explicit paths only (never a bare add-everything), re-check `git status` before each commit, and commit finished work promptly.
-- Before committing, run `npm run check:rules -- --paths <files you touched>`. It must exit 0.
-
-## Why this matters
-
-Several mirrors were edited directly on GitHub after their last `Sync from three.ws@<sha>` commit, and the monorepo never got those changes: `avatar-agent-mcp` moved to `@nirholas/pump-sdk` 2.x with holder-reward launches on 2026-09-18 (the monorepo still pins `^1.30.0` in `packages/avatar-agent-mcp/package.json`), `threews-avatar-mcp` gained "clamp untrusted tool args before they reach HTML" on 2026-07-30 (a security fix), `readme-3d` gained a docs site and a `.gltf` fix, `3d-avatar-companion` gained a `?avatar=` deep-link fix, and the `x402-fetch` and `x402-server` READMEs were rewritten on the mirror (326 and 698 lines against 103 and 410 here). The moment order 500's staged mirrors are pushed, every one of those fixes is erased. This order finds them all mechanically and brings the wanted ones home.
-
-## Step 0: re-derive the current state
-
- cat data/standalone-mirrors.json | head -40 # exists only if order 500 ran
- grep -n "pump-sdk" packages/avatar-agent-mcp/package.json
- git log -1 --format='%h %ad' --date=short -- packages/threews-avatar-mcp
-
-If `data/standalone-mirrors.json` does not exist yet, build the repo-to-directory list from the mirror table in the context file and run anyway; this order does not depend on 500 shipping.
-
-## Tasks
-
-1. **`scripts/mirror-drift-report.mjs` (read-only).** For each mirror: download its HEAD tarball from codeload into the scratchpad; find the last commit whose subject starts `Sync from three.ws@` via `https://api.github.com/repos/nirholas/<repo>/commits?per_page=100` (fall back to the README timestamp heuristic if rate limited, and say so); check out nothing locally, instead read the monorepo directory at that sha with `git archive <sha> <path>` into the scratchpad; produce three-way output: changed only on GitHub, changed only here, changed in both. Write a JSON report to `tasks/mirror-drift-<date>.json` and a readable summary to stdout. `npm run mirrors:drift` runs it.
-2. **Triage every GitHub-only change** in the report into port, drop, or already-superseded, and write that decision table into the report summary.
-3. **Port the wanted fixes by hand**, one topical commit each, with a test where the fix is behavioural: at minimum the `threews-avatar-mcp` argument clamp (with a test that an over-long or HTML-bearing argument is clamped), the `readme-3d` `.gltf` fix, the `3d-avatar-companion` `?avatar=` deep link (in `walk-sdk`), and the `avatar-agent-mcp` pump-sdk 2.x move (only if `npm test` in that package stays green and the holder-reward path builds instructions without sending; the dependency bump falls under the commit gate because it names another project's SDK, so stage it and ask).
-4. **Backport the better README content** from the `x402-fetch`, `x402-server`, `x402-modal`, `x402-payment-modal` mirrors into the monorepo READMEs where it is accurate against the current code (verify every code sample runs).
-5. **Rerun the report** and confirm only metadata differences remain for the ported repos.
-
-## Definition of done
-
-- [ ] `npm run mirrors:drift` runs read-only and writes `tasks/mirror-drift-<date>.json`.
-- [ ] The report flags the `avatar-agent-mcp` pump-sdk version difference and the 93 license footers (or the current counts).
-- [ ] Each ported fix is its own commit; the argument-clamp port has a test that fails on the old code (show the red run) and passes now.
-- [ ] After porting, a rerun lists only metadata differences (package `repository`, license footer) for every ported repo.
-- [ ] `npm test` passes for every touched package.
-
-## Never blocked
-
-| Blocker | Resolution (act, do not ask) |
-|---|---|
-| A mirror has no `Sync from three.ws@` commit at all | Diff its HEAD against the monorepo directory at HEAD, label the result "no sync base", and triage by reading. |
-| A GitHub-only change conflicts with newer monorepo work | The monorepo wins unless the GitHub change is a security or correctness fix; then re-apply it on top and test. |
-| The pump-sdk 2.x bump breaks other consumers in the root | Keep the root on 1.x and scope 2.x to the package if its `package.json` is independent; otherwise drop the bump and record why. |
-
-## Close out (required)
-
-1. Verify every Definition of done line with the actual command output in front of you. Never claim a line you did not verify.
-2. Commit with explicit paths and a subject that describes the diff (house style: `type(scope): what changed and why a reader cares`). User-visible work also gets a `data/changelog.json` entry and `npm run build:pages`; a new surface gets its `STRUCTURE.md` row and its `data/pages.json` entry.
-3. If every Definition of done line passes, delete this file in that same commit (`git rm prompts/finish/501-integrate-02-mirror-drift-report.md`) and append a dated entry to [_context/integrate-PROGRESS.md](_context/integrate-PROGRESS.md) with the commit SHAs. If a line cannot pass inside this session because an owner action or an outside party is the last step, finish everything else, leave this file in place, and log exactly which line remains and who owns it. Never delete this file on a partial.
-4. Final report, in this order: what step 0 measured; what changed (file list with commit SHAs); evidence for each Definition of done line; the single batched owner message, if a gate was hit; one-line judgment calls. No trailing questions.
diff --git a/prompts/finish/_context/integrate-PROGRESS.md b/prompts/finish/_context/integrate-PROGRESS.md
index f3c1a6a9b..f71e9f37f 100644
--- a/prompts/finish/_context/integrate-PROGRESS.md
+++ b/prompts/finish/_context/integrate-PROGRESS.md
@@ -54,3 +54,81 @@ Pushing every staged mirror is the owner's call (gate 2); logged as row 59 in
Commits: `a9c8abfae` (manifest, script rewrite, docs, changelog), plus this closing commit
(PROGRESS log, order-file deletion, owner-action row).
+
+## 2026-10-14: order 501-integrate-02 closed (evolve)
+
+`scripts/mirror-drift-report.mjs` (`npm run mirrors:drift`) does the three-way comparison the
+order asked for: for each of the 105 mirrors in `data/standalone-mirrors.json` it finds the last
+`Sync from three.ws@<sha>` commit via the GitHub commits API, archives the monorepo directory at
+that sha into the scratchpad, and diffs it against the mirror's current HEAD tarball and the
+monorepo's current tree, writing `tasks/mirror-drift-<date>.json`. It fell back to the README
+timestamp heuristic and said so once the GitHub token's rate limit reset mid-run (61 calls, 98/105
+resolved this run; a repo with no sync-marker commit at all gets `status: "no-sync-base"` per the
+order's own never-blocked table). The first run (before anything below was ported) flagged exactly
+what the order named: `avatar-agent-mcp`'s package.json diff showed `@nirholas/pump-sdk` at
+`^1.36.0` on GitHub against `^1.30.0` here, and the aggregate reported 6 mirrors still carrying the
+legacy "all rights reserved" footer (the order's own "93" figure was stale; 6 is the current,
+re-measured count).
+
+Two of the order's five named GitHub-only changes were real and got ported, each its own commit,
+each with a test that failed on the pre-fix code for the right reason before it passed:
+- `fix(threews-avatar-mcp): clamp name/camera-orbit args before they reach modelViewerHtml`
+ (`2a5caaec9`). `isSafeModelUrl` already bounded the model URL; `name` and `cameraOrbit` had no
+ such bound before reaching the generated `<model-viewer>` HTML. New `clampArg` closes that gap;
+ `test/threews.test.mjs` proves an over-long argument is clamped (13/13 green).
+- `fix(walk-sdk): give ?avatar= precedence over the stored choice on deep links` (`6be91ed66`).
+ `?walk=play&avatar=<id>` and the drop-in resume path read the saved avatar preference straight
+ out of storage and never looked at the query string. New `deepLinkAvatarId` in
+ `walk-sdk/src/companion.js` gives the query param precedence and persists it;
+ `test/companion.test.mjs` covers precedence, persistence, and both fallback paths (48/48 green).
+ `walk-sdk/src/picker.js` was also checked and is byte-identical to its mirror; nothing else in
+ that package needed a port.
+
+Three of the order's named changes turned out to be stale or inaccurate on closer reading (the
+order itself is nine days old against mirrors that keep moving):
+- `readme-3d`'s claimed "docs site and `.gltf` fix" is just the auto-generated GitHub Pages build
+ output and scaffold (`AGENTS.md`, `CITATION.cff`, `llms.txt`, etc.) that every synced mirror
+ carries; after stripping the generated marker blocks, `src/` and the README are identical to the
+ monorepo. No port made; the rerun shows `github-only` is metadata only (`README.md`,
+ `package.json`).
+- `x402-fetch` and `x402-server`'s claimed README rewrites ("326 and 698 lines against 103 and
+ 410") are also stale: after stripping generated blocks, both READMEs differ from GitHub only in
+ whitespace. No port made; both rerun to metadata-only `github-only`.
+- `x402-modal` and `x402-payment-modal`'s GitHub READMEs are real rewrites (676 and more lines),
+ but per task 4's own condition ("where it is accurate against the current code") they fail
+ verification: both claim "vendor-neutral defaults" (`brand: null`, `builderCode: null`), but
+ both packages' actual `DEFAULTS` ship three.ws branding (`brand: { label: 'Powered by three.ws'
+ ... }`, `builderCode: { wallet: '3d_agent', ... }`). The GitHub README also drops the `discover()`
+ API and the Development section that the current local README documents correctly. Per the
+ order's own never-blocked row ("the monorepo wins unless the GitHub change is a security or
+ correctness fix"), neither was backported. Both mirrors have no sync-marker commit (`heuristic`
+ method, `legacyLicenseFooter: true`), so their `github-only` list stays large after the rerun;
+ that is the expected no-sync-base/heuristic shape for an independently-edited mirror, not an
+ unported fix.
+
+One gated port, staged but not committed: `packages/avatar-agent-mcp/package.json`'s
+`@nirholas/pump-sdk` bump from `^1.30.0` to `^1.36.0` (and the matching root `package-lock.json`
+update from `npm install`) names another project's SDK, so it falls under the commit gate. The
+order's own claim of a "2.x move with holder-reward launches" did not hold up: the real current
+GitHub range is `^1.36.0` (still 1.x), and no holder-reward code exists in the mirror (checked,
+no match for `holder.reward`/`holder_reward`/`holderReward`). The edit is verified (`npm install`,
+`npm ls @nirholas/pump-sdk` → `1.36.0`, `npm test` → 26/26 green) and left staged, uncommitted,
+in this worktree. Logged as row 60 in
+[production-100-OWNER-ACTIONS.md](production-100-OWNER-ACTIONS.md).
+
+Verified live: the rerun after porting shows `github-only` reduced to metadata (`README.md`,
+`package.json`, and `glama.json` where present) for `readme-3d`, `x402-fetch`, `x402-server`, and
+`threews-avatar-mcp` (whose `here-only` now lists the 5 files of this session's own fix, expected
+since GitHub hasn't been re-synced); `avatar-agent-mcp`'s `package.json` diff narrows to the
+unrelated, out-of-scope `@grpc/grpc-js`/`@modelcontextprotocol/sdk` drift once `@nirholas/pump-sdk`
+itself is applied locally. `npm test` is green for every touched package: `walk-sdk` 48/48,
+`threews-avatar-mcp` 13/13, `avatar-agent-mcp` 26/26. `npm run check:rules` (no `--paths`, full
+repo) reports zero hard-rule violations across every changed file. `npm run build:pages` and
+`npm run audit:docs` ran clean against the new `data/changelog.json` entries (the 24 audit
+findings reported are pre-existing and unrelated to this diff).
+
+Commits: `82fb502a2` (mirror-drift-report script + npm script + first report),
+`2a5caaec9` (threews-avatar-mcp arg-clamp fix + test),
+`6be91ed66` (walk-sdk `?avatar=` deep-link fix + test),
+`fa3b6a34a` (changelog entries + generated build files),
+plus this closing commit (PROGRESS log, order-file deletion, owner-action row).
diff --git a/prompts/finish/_context/production-100-OWNER-ACTIONS.md b/prompts/finish/_context/production-100-OWNER-ACTIONS.md
index 8f078a8fd..9a09cedaf 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-14 (order 500-integrate-01 close-out): row 59 added for pushing every staged standalone mirror now that sync-standalone-repos.mjs stages instead of force-pushing; 2026-10-14 (order 404 second pass): correcting the 2026-10-11 entry below, the `x-mention-reply.js` `chainFor()` fix was not actually carried by merge commit `d77b89178`; checking out that commit's own `evolve` parent showed `chainFor()` still importing `resolveAgentBrain`/`modelChain` (the tool-calling chain shape, no `buildBody`), the exact bug row 34 flagged, still live. The real fix is this session's `evolve` commit `7ba9f9749` ("fix(x-mentions): give public replies a buildBody-shaped provider chain"), switching `chainFor()` to `llm.js`'s own `providerChain()` plus `loadOwnerGrokKey`/`agentDefaultModel`/`MODEL_CATALOG`; re-verified now genuinely passing with the same command the earlier entry cited (`RUN_LLM_TESTS=1 npx vitest run tests/x-mention-reply.llm.test.js`, 16/16 `source: 'model'`, no `buildBody` TypeError). Row 34's premise (the `evolve`/`main` divergence) is still correctly closed, just not for the reason originally stated; no row reopened. Order 060's matching status paragraph corrected the same way. 2026-10-13 (order 095 close-out): row 58 added for the Home Assistant integration's standalone repository, release, and the hacs/default and home-assistant/brands pull requests; 2026-10-13 (order 094 close-out): row 57 added for the WordPress.org/Framer/Webflow account signups and submissions for the three <agent-3d> site-builder embeds; 2026-10-13 (order 092 close-out): row 55 added for the VRoid Hub avatar-import OAuth app registration and migration; 2026-10-13 (triage-lane sweep, fifth pass): row 53 added for the Birdeye compute-units cap behind `pump-price-history-upstreams-502` (confirmed live, a billing/plan decision only); row 1 re-measured, deploy gap still 0 against the pushed `threews/main` ref and the 8 page-404/wrong-canonical findings this pass confirmed as deploy lag; row 47 re-measured, still a no-op (`COINGECKO_API_KEY` still absent); the previously-unclassified `/dist-lib/agent-3d.js` and `/agent-3d/latest/agent-3d.js` 500s ("Response size was too large") are the same bug row 48 already tracks, fixed on `evolve` in `f939d5ef1`, confirmed still green (`npx vitest run tests/lib-bundle-size.test.js tests/whisper-stt.test.js`, 16/16) and awaiting the pending deploy, no new row; 2026-10-13 (triage-lane sweep, fourth pass): row 1 re-measured, deploy gap still 0 against the pushed `threews/main` ref; the `ccv-ai-providers-unavailable-503` finding's Groq/OpenRouter/Vertex angles confirmed already covered by rows 6 and 20, no new row added; 2026-10-13 (order 087 close-out): row 51 added for the LiveKit and Pipecat avatar integrations, both built and verified end to end this session, with the PyPI publishes and the two upstream pull requests left as owner actions; 2026-10-13 (order 085 close-out): row 50 added for publishing the CC0 bulk animation library to production, and the Adobe Mixamo permission letter draft is ready to send as owner order 938; 2026-10-12 (order 084 close-out): row 49 added for the Tripo signed webhook's three linked steps (apply the `forge_webhook_deliveries` migration, set `TRIPO_WEBHOOK_SECRET`, register the dashboard webhook), not an active bug since the secret is unset and polling answers every Tripo job today; 2026-10-12 18:10 UTC (triage-lane sweep, third pass): row 48 added for the dist-lib CDN embed size fix (previously-unclassified `/dist-lib/agent-3d.js` 500s, root-caused and fixed on `evolve`, pure code change awaiting the next deploy); 2026-10-12 17:54 UTC (triage-lane sweep, second pass): row 1's same-day "11 behind" figure corrected to the real deploy gap of 0 (querying `/api/version` live, not `/api/healthz`, which has no commit field), row 47 added for CoinGecko's keyless tier being rate-limited (`COINGECKO_API_KEY` already absent from the service, so the finding's own pre-approved env fix is a no-op); 2026-10-12 (triage-lane sweep): row 1 re-measured against the canonical `threews` remote, 11 commits behind `main` (down from 28, local stale ref corrected), row 45 added for the HF image-provider (fal-ai/nscale) credit exhaustion, a separate pool from row 6; 2026-10-11 (best3d order 070 close-out): rows 43 and 44 added for the `model-partcrafter` and `model-holopart` first deploys; 2026-10-11 (triage-lane sweep): row 42 added for the MCP client-sessions nullable-column migration, an active production bug; row 1 re-measured, 28 commits behind `main` (up from 5); 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)
+## Open rows (2026-10-14 (order 501-integrate-02 close-out): row 60 added for approving the `@nirholas/pump-sdk` bump to `^1.36.0` in `packages/avatar-agent-mcp/package.json`; 2026-10-14 (order 500-integrate-01 close-out): row 59 added for pushing every staged standalone mirror now that sync-standalone-repos.mjs stages instead of force-pushing; 2026-10-14 (order 404 second pass): correcting the 2026-10-11 entry below, the `x-mention-reply.js` `chainFor()` fix was not actually carried by merge commit `d77b89178`; checking out that commit's own `evolve` parent showed `chainFor()` still importing `resolveAgentBrain`/`modelChain` (the tool-calling chain shape, no `buildBody`), the exact bug row 34 flagged, still live. The real fix is this session's `evolve` commit `7ba9f9749` ("fix(x-mentions): give public replies a buildBody-shaped provider chain"), switching `chainFor()` to `llm.js`'s own `providerChain()` plus `loadOwnerGrokKey`/`agentDefaultModel`/`MODEL_CATALOG`; re-verified now genuinely passing with the same command the earlier entry cited (`RUN_LLM_TESTS=1 npx vitest run tests/x-mention-reply.llm.test.js`, 16/16 `source: 'model'`, no `buildBody` TypeError). Row 34's premise (the `evolve`/`main` divergence) is still correctly closed, just not for the reason originally stated; no row reopened. Order 060's matching status paragraph corrected the same way. 2026-10-13 (order 095 close-out): row 58 added for the Home Assistant integration's standalone repository, release, and the hacs/default and home-assistant/brands pull requests; 2026-10-13 (order 094 close-out): row 57 added for the WordPress.org/Framer/Webflow account signups and submissions for the three <agent-3d> site-builder embeds; 2026-10-13 (order 092 close-out): row 55 added for the VRoid Hub avatar-import OAuth app registration and migration; 2026-10-13 (triage-lane sweep, fifth pass): row 53 added for the Birdeye compute-units cap behind `pump-price-history-upstreams-502` (confirmed live, a billing/plan decision only); row 1 re-measured, deploy gap still 0 against the pushed `threews/main` ref and the 8 page-404/wrong-canonical findings this pass confirmed as deploy lag; row 47 re-measured, still a no-op (`COINGECKO_API_KEY` still absent); the previously-unclassified `/dist-lib/agent-3d.js` and `/agent-3d/latest/agent-3d.js` 500s ("Response size was too large") are the same bug row 48 already tracks, fixed on `evolve` in `f939d5ef1`, confirmed still green (`npx vitest run tests/lib-bundle-size.test.js tests/whisper-stt.test.js`, 16/16) and awaiting the pending deploy, no new row; 2026-10-13 (triage-lane sweep, fourth pass): row 1 re-measured, deploy gap still 0 against the pushed `threews/main` ref; the `ccv-ai-providers-unavailable-503` finding's Groq/OpenRouter/Vertex angles confirmed already covered by rows 6 and 20, no new row added; 2026-10-13 (order 087 close-out): row 51 added for the LiveKit and Pipecat avatar integrations, both built and verified end to end this session, with the PyPI publishes and the two upstream pull requests left as owner actions; 2026-10-13 (order 085 close-out): row 50 added for publishing the CC0 bulk animation library to production, and the Adobe Mixamo permission letter draft is ready to send as owner order 938; 2026-10-12 (order 084 close-out): row 49 added for the Tripo signed webhook's three linked steps (apply the `forge_webhook_deliveries` migration, set `TRIPO_WEBHOOK_SECRET`, register the dashboard webhook), not an active bug since the secret is unset and polling answers every Tripo job today; 2026-10-12 18:10 UTC (triage-lane sweep, third pass): row 48 added for the dist-lib CDN embed size fix (previously-unclassified `/dist-lib/agent-3d.js` 500s, root-caused and fixed on `evolve`, pure code change awaiting the next deploy); 2026-10-12 17:54 UTC (triage-lane sweep, second pass): row 1's same-day "11 behind" figure corrected to the real deploy gap of 0 (querying `/api/version` live, not `/api/healthz`, which has no commit field), row 47 added for CoinGecko's keyless tier being rate-limited (`COINGECKO_API_KEY` already absent from the service, so the finding's own pre-approved env fix is a no-op); 2026-10-12 (triage-lane sweep): row 1 re-measured against the canonical `threews` remote, 11 commits behind `main` (down from 28, local stale ref corrected), row 45 added for the HF image-provider (fal-ai/nscale) credit exhaustion, a separate pool from row 6; 2026-10-11 (best3d order 070 close-out): rows 43 and 44 added for the `model-partcrafter` and `model-holopart` first deploys; 2026-10-11 (triage-lane sweep): row 42 added for the MCP client-sessions nullable-column migration, an active production bug; row 1 re-measured, 28 commits behind `main` (up from 5); 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 |
|---|---|---|---|---|
@@ -74,6 +74,7 @@ on it; some resolve themselves as other work lands.
| 57 | **Create a WordPress.org account and submit the plugin; create a Framer account and submit the Marketplace listing; create a Webflow account, run `webflow devlink import`, and submit the Apps marketplace listing** (added 2026-10-13 by the evolve loop closing out order 094-partners-11). All three embeds for `<agent-3d>` are built and verified: the WordPress plugin ([`integrations/wordpress/three-ws-agent/`](../../integrations/wordpress/three-ws-agent)) passes the official Plugin Check tool against a real local WordPress 7.1.3 in Docker ("Checks complete. No errors found.", reproduced in [`docs/wordpress-embed.md`](../../docs/wordpress-embed.md)); the Framer code component ([`integrations/framer/`](../../integrations/framer)) and the Webflow Code Component ([`integrations/webflow/`](../../integrations/webflow)) each boot a live WebGL canvas against the real pinned production CDN release in a real-React Playwright harness (`tests/e2e/agent-3d-framer-component.spec.js`, `tests/e2e/agent-3d-webflow-component.spec.js`, both passing), and the Webflow component additionally compiles through the real, unmodified `@webflow/webflow-cli`'s `devlink bundle` ("Code Library bundled successfully!"). No WordPress.org, Framer, or Webflow account exists in this workspace, so nothing past this point is testable here. Full step-by-step with exact settings and listing copy for all three: [`marketing/growth/submissions/site-builders.md`](../../marketing/growth/submissions/site-builders.md). Summary: (a) create a WordPress.org account, submit the plugin zip for review, and commit to the assigned SVN repo once approved; (b) create a Framer account, paste the three component files into a project, confirm it renders in Framer's own canvas, and submit to the Marketplace; (c) create a Webflow account, run `webflow auth login` then `webflow devlink import` from `integrations/webflow/`, confirm the component drags into the Designer, and submit to the Apps marketplace. | three account signups + two submissions + one SVN commit + one devlink import | Lists three.ws's `<agent-3d>` embed in the WordPress.org plugin directory, the Framer Marketplace, and the Webflow Apps marketplace | [094-partners-11-site-builder-embeds.md](../094-partners-11-site-builder-embeds.md), [marketing/growth/submissions/site-builders.md](../../marketing/growth/submissions/site-builders.md) |
| 58 | **Create `github.com/nirholas/three-ws-home-assistant` from the exported tree, confirm its two CI workflows pass, cut a `v1.0.1` release, then open the `hacs/default` and `home-assistant/brands` pull requests** (added 2026-10-13 by the evolve loop closing out order 095-partners-12). `home-assistant-integration/` now validates clean: `manifest.json`'s broken `documentation` link fixed to the live `/docs/home-relay`, `version` bumped to `1.0.1`, `hacs.json`'s minimum Home Assistant version corrected to `2024.12.0` (the first release bundling the `aiohttp.ClientWSTimeout` the integration's relay client uses, confirmed against HA's own `package_constraints.txt` history), and real local brand icons added at `custom_components/three_ws/brand/{icon,icon@2x,dark_icon,dark_icon@2x}.png`. `node scripts/export-hacs-repo.mjs` builds the exact standalone-repository tree (the integration, README, LICENSE, `hacs.json`, and the two validation workflows, which live only in that exported tree since this monorepo runs no GitHub Actions of its own) under `dist/hacs-export/`. Verified this session with the real tools HACS's own CI runs: the real `ghcr.io/home-assistant/hassfest` Docker image against the exported tree ("Invalid integrations: 0"), the real upstream HACS schema/brand/readme validators from `hacs/integration`'s own source (all pass; the GitHub-settings-dependent checks are architecturally impossible to run before the repository exists), and a full real end-to-end install: a real `ghcr.io/home-assistant/home-assistant:stable` container onboarded via its own REST API, paired through the real config flow against a real `services/home-relay` server, 18 real entities read back, and a confirmed auto-reconnect after a relay restart. Full step-by-step with exact settings and PR text for both targets: [`marketing/growth/submissions/home-assistant.md`](../../marketing/growth/submissions/home-assistant.md). Summary: (a) push `dist/hacs-export/` (rebuild with `node scripts/export-hacs-repo.mjs` first) to a new public personal repository at `github.com/nirholas/three-ws-home-assistant`, set its description/topics/issues, confirm `hassfest.yml` and `hacs.yml` both pass on `main`, and cut a `v1.0.1` release; (b) add it to HACS as a custom repository in a real Home Assistant instance and confirm it installs; (c) fork `hacs/default`, add `"nirholas/three-ws-home-assistant"` to the `integration` file between `nimroddolev/chime_tts` and `nishithdev/wled-taskmap`, and open the PR with the title/description already written in the submission file; (d) fork `home-assistant/brands`, copy the four PNGs already sitting in this repository into `custom_integrations/three_ws/`, and open that PR with its own title/description. | one repository creation + one release cut + two pull requests | Lists three.ws's Home Assistant integration in the HACS default store and gives it an official brand icon | [095-partners-12-home-assistant-hacs.md](../095-partners-12-home-assistant-hacs.md), [marketing/growth/submissions/home-assistant.md](../../marketing/growth/submissions/home-assistant.md) |
| 59 | **Push every staged standalone mirror** (added 2026-10-14 by the evolve loop closing out order 500-integrate-01). `npm run sync:repos` now stages a one-commit snapshot per mirror under `dist/standalone-mirrors/<repo>/` instead of force-pushing, reading `data/standalone-mirrors.json` as the single source of truth for which monorepo directory maps to which public repo (this also fixes the eleven mirrors already renamed on GitHub, so no duplicate repo gets created for them). It never calls `gh`, never pushes, and makes no network writes; the script's own output after staging is the exact push line for each mirror, in the form `git -C dist/standalone-mirrors/<repo> push --force https://github.com/nirholas/<repo>.git HEAD:main`. Run `npm run sync:repos` (optionally `-- --only <repo>` for a single mirror), review a staged tree if you want to, then run the printed push command for each mirror you want to publish. `npm run sync:repos:check` reports drift against each mirror's live tree without writing anything, useful to see which mirrors are stale before deciding which pushes to run. | one `npm run sync:repos` run plus N `git push --force` commands (one per mirror, printed by the tool) | Publishes the Apache-2.0 license-footer fix and the renamed-mirror corrections to every public GitHub mirror | [500-integrate-01-mirror-manifest.md](../500-integrate-01-mirror-manifest.md) (retired this session; see `_context/integrate-PROGRESS.md`), [data/standalone-mirrors.json](../../data/standalone-mirrors.json) |
+| 60 | **Approve bumping `@nirholas/pump-sdk` from `^1.30.0` to `^1.36.0`** in `packages/avatar-agent-mcp/package.json` (added 2026-10-14 by the evolve loop closing out order 501-integrate-02). The `avatar-agent-mcp` GitHub mirror moved to this range on its own; `npm run mirrors:drift` flagged the drift. This names another project's SDK, so the commit gate applies: the edit is made and verified (`npm install`, `npm ls @nirholas/pump-sdk` → `1.36.0`, `npm test` → 26/26 green) but held staged, uncommitted, in the worktree rather than committed. The order's own text also named a "2.x move with holder-reward launches"; that claim is stale, the real current GitHub range is `^1.36.0` (still 1.x) and no holder-reward code exists in the mirror (checked, no match for `holder.reward`/`holder_reward`/`holderReward`). To approve: review the staged diff (`git diff packages/avatar-agent-mcp/package.json package-lock.json`), then `git add packages/avatar-agent-mcp/package.json package-lock.json && git commit`. | one `git add` + `git commit` | Keeps `packages/avatar-agent-mcp` on the pump-sdk range its own GitHub mirror and `npm test` already validate | [501-integrate-02-mirror-drift-report.md](../501-integrate-02-mirror-drift-report.md) (retired this session; see `_context/integrate-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.