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 500-integrate-01, mirror manifest shipped

nirholas4888783a949c
diff --git a/prompts/finish/500-integrate-01-mirror-manifest.md b/prompts/finish/500-integrate-01-mirror-manifest.md
deleted file mode 100644
index 5fa1c3b60..000000000
--- a/prompts/finish/500-integrate-01-mirror-manifest.md
+++ /dev/null
@@ -1,70 +0,0 @@
-# integrate 01: one mirror manifest and a sync tool that stages instead of force-pushing
-
-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 final push of every staged mirror is the owner's (gate 2); this order only stages and prints the commands. 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
-
-About 86 public repos are copies of directories in this monorepo, and they are how most people meet three.ws on GitHub and npm. Nothing keeps them honest. Seven separate mechanisms produce them (listed in the context file), none runs on a schedule, and the one that covers `packages/*` is dangerous: `npm run sync:repos` hardcodes `--execute` (package.json, the `sync:repos` script) and `scripts/sync-standalone-repos.mjs` runs `git push --force origin main` (around line 185). That breaks owner gate 2. It also does not know about the eleven mirrors renamed on GitHub (`scene-mcp` is `3d-scene-mcp`, `vision-mcp` is `image-analysis-mcp`, `agent-sniper` is `solana-sniper-mcp`, `tutor-mcp` is `ai-tutor-mcp`, `portfolio-mcp` is `crypto-portfolio-mcp`, `signals-mcp` is `crypto-signals-mcp`, `marketplace-mcp` is `nft-marketplace-mcp`, `notifications-mcp` is `push-notifications-mcp`, `vanity-mcp` is `solana-vanity-mcp`, `naming-mcp` is `token-naming-mcp`, `x402-mcp` is `x402-payments-mcp`), so a run today creates eleven duplicate repos. It never discovers `walk-sdk` (published as `3d-avatar-companion`), `x402-modal-sdk`, `x402-payment-modal`, or `agent-payments-sdk`.
-
-The fix is one source of truth for "which directory is which public repo, in which direction", and one tool that stages every mirror and prints the push for the owner.
-
-## Step 0: re-derive the current state
-
- grep -n '"sync:repos' package.json
- grep -n "push" scripts/sync-standalone-repos.mjs
- sed -n 55,80p scripts/sync-standalone-repos.mjs
- npm run sync:repos:dry 2>&1 | tail -40
- ls satellites/ && grep -n "push" scripts/export-growth-satellites.mjs | head
- sed -n 200,230p docs/contributing.md
-
-Then list the owner's live repos so the manifest is built from reality, not from this file:
-
- curl -s "https://api.github.com/users/nirholas/repos?per_page=100&page=1" | node -e 'let s="";process.stdin.on("data",d=>s+=d).on("end",()=>JSON.parse(s).forEach(r=>console.log(r.name,r.fork)))'
-
-(pages 1 to 4). For each monorepo directory with a `package.json` `repository.url` pointing at `github.com/nirholas/<x>`, check whether `<x>` exists or 301s to a new name (`curl -sI https://github.com/nirholas/<x>`).
-
-## Tasks
-
-1. **`data/standalone-mirrors.json`.** One entry per public mirror: `{ "repo": "<github name>", "path": "<monorepo dir>", "direction": "out" | "in", "exporter": "sync" | "growth-satellites" | "examples" | "awesome" | "skill-repos", "npm": "<package name or null>" }`. Include the eleven renamed MCP mirrors under their GitHub names, `walk-sdk`, `x402-modal-sdk`, `x402-payment-modal`, `agent-payments-sdk`, the three satellites, `awesome-3d-agents`, and the `robinhood/*` copies with `direction: "in"` (order 503 decides their fate; record them truthfully here). Add a JSON schema next to it and a vitest that every `path` exists and every `repo` is unique.
-2. **Rewrite `scripts/sync-standalone-repos.mjs` to stage, never push.** Read the manifest instead of discovering by glob plus an override list. For each `exporter: "sync"` entry, build the snapshot under `dist/standalone-mirrors/<repo>/` as a fresh one-commit git repo whose message is `Sync from three.ws@<12-char sha>`, rewrite `package.json` `repository` to the mirror, and print the exact `git -C dist/standalone-mirrors/<repo> push --force https://github.com/nirholas/<repo>.git HEAD:main` line. No `gh repo create`, no push, no network writes. Add `--check`: compare each staged tree with the mirror's current HEAD tarball (codeload) and exit non-zero listing drifted repos, without writing.
-3. **Make the npm scripts safe.** `sync:repos` stages; `sync:repos:check` runs `--check`. Remove `--execute` everywhere. Make `export-growth-satellites`, `build-awesome --standalone` and `build-standalone-skill-repos` read their repo names from the manifest so there is one list.
-4. **License footer.** The staging step must replace any "All rights reserved" footer in a staged README with the Apache-2.0 line the monorepo uses today (verify against the root `LICENSE`), so the next owner push fixes all 93 stale footers at once.
-5. **Docs.** Rewrite the mirror section of `docs/contributing.md` (around lines 200 to 230), `packages/README.md`, and the promotion section of `STRUCTURE.md` to describe the manifest and the staged flow. Remove any description of `git subtree split` that no longer matches what the scripts do.
-
-Do not run a sync against GitHub until order 501 has ported the GitHub-only fixes; this order builds the tool and stages, nothing more.
-
-## Definition of done
-
-- [ ] `data/standalone-mirrors.json` exists, validates, and its vitest passes; it lists every renamed mirror under its GitHub name.
-- [ ] `grep -n "'push'" scripts/sync-standalone-repos.mjs` matches only printed strings; `grep -n -- "--execute" package.json` prints nothing.
-- [ ] `npm run sync:repos` stages every `sync` entry under `dist/standalone-mirrors/` and reports 0 repos to create for the eleven renamed packages.
-- [ ] `git -C dist/standalone-mirrors/tty-avatar log -1 --format=%s` equals `Sync from three.ws@$(git rev-parse --short=12 HEAD)`, and `diff -r packages/tty-avatar dist/standalone-mirrors/tty-avatar` differs only in `package.json` `repository` and `.git`.
-- [ ] No staged README contains "All rights reserved".
-- [ ] `npm run sync:repos:check` exits non-zero and lists drifted repos (drift is expected until the owner pushes).
-- [ ] `docs/contributing.md`, `packages/README.md`, `STRUCTURE.md` describe the new flow; `npm run audit:docs` passes.
-
-## Never blocked
-
-| Blocker | Resolution (act, do not ask) |
-|---|---|
-| A package's `repository.url` names a repo that does not exist | Record it in the manifest with `"repo": null` and list it in the report as "no mirror yet"; do not create one. |
-| GitHub API rate limit during `--check` | Use codeload tarballs, which are not rate limited; cache them per run in the scratchpad. |
-| A mirror's GitHub history has commits the monorepo lacks | That is order 501's job. Note the repo name and continue. |
-
-## 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/500-integrate-01-mirror-manifest.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 89c6428c6..f3c1a6a9b 100644
--- a/prompts/finish/_context/integrate-PROGRESS.md
+++ b/prompts/finish/_context/integrate-PROGRESS.md
@@ -11,3 +11,46 @@ Surveyed all 389 repositories under `github.com/nirholas` (354 owned, 35 forks)
monorepo in six clusters and wrote 50 work orders. No order has run yet. Order 500 and 501 should
run before anyone pushes a mirror; 505 before 506 and 507 (shared decoder); 524 before 525; 529
before 530 and 531; 015 (parity) before 510.
+
+## 2026-10-14: order 500-integrate-01 closed (evolve)
+
+`data/standalone-mirrors.json` is now the single source of truth for which monorepo directory
+maps to which public GitHub repo, direction, and exporter; it lists all eleven renamed MCP
+mirrors under their real GitHub names, `walk-sdk` (published as `3d-avatar-companion`),
+`x402-modal-sdk`/`x402-payment-modal` (no mirror yet, `repo: null`), `agent-payments-sdk`, the
+three growth satellites, `awesome-3d-agents`, the three skill-repo targets sharing the
+`.agents/skills` source path, and the 17 `robinhood/*` reference copies under `direction: "in"`.
+`scripts/sync-standalone-repos.mjs` was rewritten to read that manifest and stage a one-commit
+snapshot per mirror under `dist/standalone-mirrors/<repo>/`, fix any stale pre-Apache-2.0
+license footer, and print the push command, with zero `gh` calls and zero `git push` calls
+anywhere in the file. `export-growth-satellites.mjs`, `build-awesome.mjs` and
+`build-standalone-skill-repos.mjs` now read repo names from the same manifest instead of each
+keeping its own list. `npm run sync:repos` no longer carries `--execute`; `sync:repos:check`
+replaces the old `sync:repos:dry` and compares staged trees against each mirror's live codeload
+tarball, reporting drift without writing. `docs/contributing.md`, `packages/README.md` and
+`STRUCTURE.md` describe the new flow.
+
+Verified live: staged 96 mirrors with zero errors and zero duplicates for the eleven renamed
+repos; `tty-avatar`'s staged commit message matched `Sync from three.ws@<sha>` exactly, and its
+staged tree differed from `packages/tty-avatar` only in `.git` and `package.json`'s `repository`
+field; zero staged README carried an "all rights reserved" footer; `sync:repos:check` exited
+non-zero and listed every repo as drifted (expected, since nothing has been pushed yet);
+`audit:docs` reported the same 24 pre-existing findings before and after this diff (verified by
+stashing this change and re-running); the full `npx vitest run` showed 44 pre-existing failing
+files unrelated to this diff, confirmed by stashing this change and re-running three of the
+failing files, which failed identically without it.
+
+One judgment call: the previous script also ran the rich enrichment pipeline
+(`enrichMirror`/`boostMirror` from `scripts/lib/standalone-kit.mjs`, adding AGENTS.md, llms.txt,
+an OG card and a docs site to every staged mirror). The order's task list only asked for a
+snapshot, a `package.json` repository rewrite, and a license-footer fix, and its own
+definition-of-done line requires the staged `tty-avatar` tree to differ from the source
+*only* in `.git` and `package.json`'s `repository` field, which the richer pipeline would
+violate. The new script does not call it; `enrichMirror`/`enrichPackageJson`/`boostMirror`
+are unused by any entry point now but left in place as tested library code.
+
+Pushing every staged mirror is the owner's call (gate 2); logged as row 59 in
+[production-100-OWNER-ACTIONS.md](production-100-OWNER-ACTIONS.md).
+
+Commits: `a9c8abfae` (manifest, script rewrite, docs, changelog), 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 da5ba1e55..8f078a8fd 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 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 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 |
|---|---|---|---|---|
@@ -73,6 +73,7 @@ on it; some resolve themselves as other work lands.
| 56 | **Publish the AI SDK/LangChain packages and submit the six agent-registry entries plus the LangChain integration issue** (added 2026-10-13 by the evolve loop closing out order 093-partners-10). `packages/ai-sdk/` (`@three-ws/ai-sdk`) and `packages/langchain/` (`@three-ws/langchain`) are both built, real-API-tested (`npm test` in each: 5/5 passing, live calls against production forge/rig/render/agent-chat/animate), and `npm pack --dry-run` clean. Neither has ever been published (new package names, no npm publish has run from this workspace). The six registry entries for Hermes, Kilo, OpenHands, OpenCode, Dify and cursor.directory are written in `marketing/growth/submissions/agent-registries/` in each registry's confirmed real format, and the LangChain integration-package issue text is at [`packages/langchain/INTEGRATION_ISSUE.md`](../../packages/langchain/INTEGRATION_ISSUE.md). Summary: (a) `cd packages/ai-sdk && npm publish --access public`, then the same in `packages/langchain/`; (b) open the LangChain integration issue against `langchain-ai/langchainjs` using `packages/langchain/INTEGRATION_ISSUE.md`'s text; (c) submit each of the six registry entries per its own file's "Owner steps" section in `marketing/growth/submissions/agent-registries/`. | two npm publishes + one GitHub issue + six registry submissions | Lists three.ws in the Vercel AI SDK and LangChain JS tool ecosystems and in six agent-framework registries | [093-partners-10-agent-tool-packages.md](../093-partners-10-agent-tool-packages.md), [packages/langchain/INTEGRATION_ISSUE.md](../../packages/langchain/INTEGRATION_ISSUE.md), [marketing/growth/submissions/agent-registries/](../../marketing/growth/submissions/agent-registries/) |
| 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) |
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.