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(finish): add owner row 63 for the production PAY_VERDICT_HMAC_KEY env var

nirholasc653fed89784
diff --git a/prompts/finish/_context/production-100-OWNER-ACTIONS.md b/prompts/finish/_context/production-100-OWNER-ACTIONS.md
index 7c11dadee..0d3dbf257 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 506-integrate-07 close-out): row 62 added for deploying the new `services/pump-claims` Cloud Run service and applying its `pump_fee_claims` migration to production; 2026-10-14 (order 503-integrate-04 close-out): row 61 added for pushing and archiving 7 retired repos (`three-ui`, `crypto-market-data`, `crypto-market-data-ts`, `crypto-data-aggregator`, `memescope-monday-directory`, `robinhood-chain-alert-bot`, `robinhood-chain-trading-bot`); 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)
+## Open rows (2026-10-15 (order 518-integrate-19 close-out): row 63 added for setting a dedicated `PAY_VERDICT_HMAC_KEY` on the production Cloud Run service; not an active bug, the signed-verdict feature it covers already works today on a fallback secret, this just gives it its own rotatable key; 2026-10-14 (order 506-integrate-07 close-out): row 62 added for deploying the new `services/pump-claims` Cloud Run service and applying its `pump_fee_claims` migration to production; 2026-10-14 (order 503-integrate-04 close-out): row 61 added for pushing and archiving 7 retired repos (`three-ui`, `crypto-market-data`, `crypto-market-data-ts`, `crypto-data-aggregator`, `memescope-monday-directory`, `robinhood-chain-alert-bot`, `robinhood-chain-trading-bot`); 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 |
|---|---|---|---|---|
@@ -76,6 +76,7 @@ on it; some resolve themselves as other work lands.
| 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`) |
| 62 | **Deploy `services/pump-claims` (new Cloud Run service) and apply its migration** (added 2026-10-14 by the evolve loop closing out order 506-integrate-07). The service is a standalone real-time listener: it subscribes to PumpFees program logs, decodes and attributes every GitHub social-fee-PDA claim (`claim_social_fee_pda`), and writes it to a new `pump_fee_claims` table, so `api/_lib/pump-claims.js`'s claims feed can read a persisted real-time source instead of re-scanning RPC history on every request (it still falls back to the RPC scan whenever the table has nothing for the requested window). Built and verified this session: 21/21 `node --test` passing (decode, attribution, idempotent insert, reconnect/gap-fill, a 429-backoff helper for the free RPC lane), a Docker image built AND run (not just built) confirming every transitively-imported module resolves, a new transitive-import-aware vitest guard (`tests/pump-claims-worker-image.test.js`) so a future drift fails the build instead of crashing the container on boot, and the actual migration file applied and verified with the real `npm run db:migrate -- --apply --file 20261015080000_pump_fee_claims.sql` / `npm run db:check` tooling against a local throwaway Postgres (`scripts/use-local-neon.mjs`), never against production. Two things only the owner can do: (a) apply the migration to the real production database, exactly `npm run db:migrate -- --apply --file 20261015080000_pump_fee_claims.sql` (read `npm run db:status` first; this applies immediately, no dry run, and the shared worktree may have other agents' unrelated pending migrations queued, so review the full pending list before running); (b) deploy the service, exactly `gcloud builds submit --config services/pump-claims/cloudbuild.yaml .` from the repo root (pinned to the `three-ws-build@`/`three-ws@` service accounts, `--no-cpu-throttling --min-instances=1`, defaults `SOLANA_RPC_URL` to the free `api.mainnet-beta.solana.com` lane, one of only two lanes measured to serve `logsSubscribe`; see `docs/ops/solana-rpc-lanes.md`). After both land, run `node services/pump-claims/backfill.js --days=7` once (or let the live listener's cold-start gap-fill do it) so the table isn't empty on day one, then confirm with `select count(*) from pump_fee_claims;`. One real finding from this session worth knowing before that backfill runs: the PumpFees program is extremely busy overall (measured ~500 signatures/second across ALL its traffic, not just GitHub claims), so `backfill.js`'s `MAX_SIGNATURES_SCANNED` safety cap (20,000) will be reached within roughly the most recent minute of chain activity regardless of the `--days` flag; a true 7-day backfill of this specific claim type is not reachable by walking raw signature history on any RPC lane and would need a dedicated indexer if ever required, the live listener (real-time, no scan) is the real source of ongoing coverage. | one migration apply + one `gcloud builds submit` + one backfill run | Makes the claims feed's GitHub-attribution path real-time and self-hosted, ending its implicit dependence on RPC-scan freshness per request | [506-integrate-07-pump-claims-listener.md](../506-integrate-07-pump-claims-listener.md), [services/pump-claims/README.md](../../services/pump-claims/README.md) |
+| 63 | **Set a dedicated `PAY_VERDICT_HMAC_KEY` on the production Cloud Run service** (added 2026-10-15 by the evolve loop closing out order 518-integrate-19). Not an active bug: `api/_lib/env.js` falls back from `PAY_VERDICT_HMAC_KEY` through `PAYMENT_SESSION_SECRET`, `WALLET_CAPABILITY_SECRET`, `WALLET_ENCRYPTION_KEY`, to `JWT_SECRET`, so every payment-session verdict (allow, reject, or `requires_approval`) is already signed and tamper-evident in production today on whichever of those is set. Setting a dedicated key only gives verdict signatures their own rotatable secret, so rotating `PAYMENT_SESSION_SECRET` (which also mints the `pss_` bearer tokens) stops also invalidating every historical verdict signature. Generate a fresh random value and set it with `gcloud run services update three-ws-api --region us-central1 --update-env-vars PAY_VERDICT_HMAC_KEY=<fresh random value>` (this is a config-only env-var change, pre-approved by CLAUDE.md; no code change or deploy is needed for it to take effect). A dev value already exists in this worktree's gitignored `.env.local`, generated and verified locally this session; it was deliberately not reused for production so the owner can mint production's own secret rather than inherit one that ever existed in a session transcript. | minutes | Gives payment-session verdict signatures their own rotatable secret, independent of `PAYMENT_SESSION_SECRET` | [docs/payment-sessions.md](../../docs/payment-sessions.md), [integrate-PROGRESS.md](integrate-PROGRESS.md), 2026-10-15 entry |
| 63 | **Apply the per-coin earnings timeline migration, and only then deploy** (added 2026-10-14 by the evolve loop closing out order 510-integrate-11). `api/_lib/pump-creator-fees.js` now sums each coin's own pump.fun distribution timeline (`fetchCoinEarnings`) alongside the existing wallet-level fee index, and `api/_lib/creator-earnings-snapshot.js` reconciles the two into five new `agent_coin_earnings` columns (`coin_earned_lamports`, `coin_distributions`, `coin_earnings_source`, `reconciliation_delta_lamports`, `reconciliation_pct`). The migration (`api/_lib/migrations/20261015090000_agent_coin_earnings_timeline.sql`) is written and verified idempotent and syntactically correct via a throwaway PGlite run, never against production. Exact apply command: `npm run db:migrate -- --apply --file 20261015090000_agent_coin_earnings_timeline.sql` (read `npm run db:status` first; this applies immediately with no dry run, and the shared worktree may have other agents' unrelated pending migrations queued, so review the full pending list before running). Critical ordering note: `api/pump/launch-detail.js`'s `creatorFeesFor()` and `api/_lib/agent-earnings.js`'s `getAgentEarnings()` both now select the new columns in the SAME query as the pre-existing ones, so if this commit's code reaches production before the migration lands, that combined select throws `column "coin_earned_lamports" does not exist` on every call; the pre-existing `.catch(() => null)` wrapper around `creatorFeesFor()` silently swallows it, degrading `economics.creator_fees` to `null` for every coin (not just the new fields) until the migration is applied. Apply the migration before (or as part of) the next deploy that includes this diff, not after. | one `npm run db:migrate -- --apply` run, timed before the next deploy | Restores and extends per-coin creator-earnings data (`economics.creator_fees`) with a second, independent, reconciled source instead of risking it going silently null | [510-integrate-11-per-coin-earnings-source.md](../510-integrate-11-per-coin-earnings-source.md) |
| 61 | **Push and archive 7 retired repos** (added 2026-10-14 by the evolve loop closing out order 503-integrate-04). `data/retired-repos.json` lists `three-ui`, `crypto-market-data`, `crypto-market-data-ts`, and `crypto-data-aggregator` (all superseded by the `/markets` page or `src/` in this monorepo), `memescope-monday-directory` (duplicate of `memescope-monday`), and one repo from each of the two Robinhood Chain duplicate pairs (`robinhood-chain-alert-bot`, duplicate of `robinhood-chain-alerts`; `robinhood-chain-trading-bot`, duplicate of `robinhood-chain-traders`). `npm run retire:repos` staged a one-commit pointer README under `dist/retired-repos/<repo>/` for each, explaining the retirement and linking to the replacement; it never calls `gh` and never pushes. To approve, run these 14 commands (7 pushes, 7 archives): `git -C dist/retired-repos/three-ui push --force https://github.com/nirholas/three-ui.git HEAD:main && gh repo archive nirholas/three-ui --yes`, `git -C dist/retired-repos/crypto-market-data push --force https://github.com/nirholas/crypto-market-data.git HEAD:main && gh repo archive nirholas/crypto-market-data --yes`, `git -C dist/retired-repos/crypto-market-data-ts push --force https://github.com/nirholas/crypto-market-data-ts.git HEAD:main && gh repo archive nirholas/crypto-market-data-ts --yes`, `git -C dist/retired-repos/crypto-data-aggregator push --force https://github.com/nirholas/crypto-data-aggregator.git HEAD:main && gh repo archive nirholas/crypto-data-aggregator --yes`, `git -C dist/retired-repos/memescope-monday-directory push --force https://github.com/nirholas/memescope-monday-directory.git HEAD:main && gh repo archive nirholas/memescope-monday-directory --yes`, `git -C dist/retired-repos/robinhood-chain-alert-bot push --force https://github.com/nirholas/robinhood-chain-alert-bot.git HEAD:main && gh repo archive nirholas/robinhood-chain-alert-bot --yes`, `git -C dist/retired-repos/robinhood-chain-trading-bot push --force https://github.com/nirholas/robinhood-chain-trading-bot.git HEAD:main && gh repo archive nirholas/robinhood-chain-trading-bot --yes`. `dist/` is gitignored, so re-run `npm run retire:repos` first if the staged trees were cleaned since this session. | 7 pushes + 7 archives | Removes 7 stale/duplicate public repos from the owner's GitHub without losing their history (each gets a pointer commit first) | [503-integrate-04-robinhood-copies-and-retired-repos.md](../503-integrate-04-robinhood-copies-and-retired-repos.md) (retired this session; see `_context/integrate-PROGRESS.md`) |