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.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
chore(prompts): retire order 510 now that the per-coin earnings migration is applied in production
nirholas39caaddba3d3
diff --git a/prompts/README.md b/prompts/README.mdindex e942e72f6..b7571adee 100644--- a/prompts/README.md+++ b/prompts/README.md@@ -78,7 +78,7 @@ order to run them in, see [RUN-ORDER.md](RUN-ORDER.md).| `backlog-` | The open backlog, two items: [x402 settle runway](finish/902-backlog-01-x402-settle-runway.md) (code half done; needs the sponsor-wallet funding in `production-100-OWNER-ACTIONS.md` row 2) and [the OKX chat-bot always-on fix](finish/907-backlog-08-okx-chat-bot-always-on.md). || `beat-` | Closing the gaps found in the 2026-10-09 survey of open-source crypto and agent repositories. 12 open, runnable, on-chain steps devnet/simulation only: `605`, `606`, `610`, `614`, `615`, `616`, `619`, `621`, `622`, `623`, `626`, `627` (on-chain allowance budgets, a burner wallet with owner confirmation, the hire-escrow evaluator and disputes, the orders engine with ratcheting exits, perps venues, Solana prediction markets in shadow mode, token due diligence and a funding graph, agent CLI automation and HTML reports, Solana agent registry registration, a skill supply-chain scanner, a metered OpenAI-compatible router, and launch-fee/holder-reward features). Context: [finish/_context/beat-00-CONTEXT.md](finish/_context/beat-00-CONTEXT.md). || `best3d-` | Closing the gaps found by the 2026-10-09 sweep of open-source and commercial 3D ([docs/research/3d-landscape-2026-10.md](../docs/research/3d-landscape-2026-10.md)). 10 open: `067`, `068`, `069`, `070`, `074`, `081` runnable (TRELLIS.2 default lane, Pixal3D multi-view, non-humanoid rigging, editable parts, the WebGPU TSL path, splat parity) plus `932` to `935` owner-gated (pricing preview and pay-to-keep, SAM 3D Objects, the orphaned-avatar campaign, engine store publishing). Shared facts: [finish/_context/best3d-00-CONTEXT.md](finish/_context/best3d-00-CONTEXT.md). |-| `integrate-` | Bringing the owner's other repositories into three.ws. 13 open, runnable: `506`, `510`, `512`, `525`, `530`, `534`, `536`, `539`, `540`, `544`, `545`, `548`, `549` (the pump.fun claims listener, the per-coin earnings source, the native-lane anti-snipe fee, skill import from Anchor IDL, MCP registry cleanup, news reader lanes, the $THREE-post impact tracker, coin intel signals, a memo/inscription reader, chains turnover, a 3D funder graph, Robinhood Chain launch venues, and the hookforge catalog). Context: [finish/_context/integrate-00-CONTEXT.md](finish/_context/integrate-00-CONTEXT.md). |+| `integrate-` | Bringing the owner's other repositories into three.ws. 12 open, runnable: `506`, `512`, `525`, `530`, `534`, `536`, `539`, `540`, `544`, `545`, `548`, `549` (the pump.fun claims listener, the native-lane anti-snipe fee, skill import from Anchor IDL, MCP registry cleanup, news reader lanes, the $THREE-post impact tracker, coin intel signals, a memo/inscription reader, chains turnover, a 3D funder graph, Robinhood Chain launch venues, and the hookforge catalog). Context: [finish/_context/integrate-00-CONTEXT.md](finish/_context/integrate-00-CONTEXT.md). || `okx-ai-` | Taking the three.ws 3D Studio listing (agent #2632) to approved status on OKX.AI. Three open orders, owner-gated: [the real-payment gauntlet](finish/913-okx-ai-04-e2e-real-payment-test.md), [forge relisting](finish/911-okx-ai-08-forge-relisting.md), and [the final audit and watch](finish/914-okx-ai-07-final-audit-and-watch.md), plus a runbook. || `parity-` | Closing the gaps a teardown of a leading agent launchpad found ("Competitor X", [docs/research/competitor-teardown-2026-09.md](../docs/research/competitor-teardown-2026-09.md)). Seven open, owner-gated: `919` to `925` (shipping and publishing, a community skill registry, directory listings, a "why three.ws" page, a builder competition, pricing levers, and a mention-to-launch flow). Shared facts: [finish/_context/parity-00-CONTEXT.md](finish/_context/parity-00-CONTEXT.md). || `partners-` | Working the 2026-10-09 partner prospects list ([docs/partners/prospects.md](../docs/partners/prospects.md)). 13 open: `085`, `087`, `088`, `091` to `095` runnable (the Mixamo-clip animation library license, LiveKit and Pipecat avatar plugins, a Discord Activity, a Shopify product-media app, VRoid Hub import, agent-framework tool packages, site-builder embeds, the HACS package) plus `936` to `940` owner-gated (the Tripo reply and house key, sponsorships, third-party submissions, program applications, a Sketchfab re-tag). Shared facts: [finish/_context/partners-00-CONTEXT.md](finish/_context/partners-00-CONTEXT.md). |diff --git a/prompts/finish/510-integrate-11-per-coin-earnings-source.md b/prompts/finish/510-integrate-11-per-coin-earnings-source.mddeleted file mode 100644index f7375fbc7..000000000--- a/prompts/finish/510-integrate-11-per-coin-earnings-source.md+++ /dev/null@@ -1,56 +0,0 @@-# integrate 11: reconciled per-coin creator earnings from the coin timeline--**Evolve status (2026-10-14, re-verified 2026-10-15):** Everything except the production migration apply is done. `fetchCoinEarnings` and `fetchAllShares` are ported into `api/_lib/pump-creator-fees.js` behind the existing circuit breaker (no second client); `api/_lib/creator-earnings-snapshot.js` now reconciles each coin's timeline sum against the wallet-level claimed figure and stores the delta, percentage and source; `api/pump/launch-detail.js` and `api/_lib/agent-earnings.js` serve `distributed` and `reconciliation` alongside the existing wallet-level figures, falling back to a live timeline read when no snapshot row exists; `src/launch-detail.js` and `src/shared/agent-earnings-card.js` render "this coin paid X SOL" with a plain-English reconciliation sentence; `earningsMethod()` names both sources. `tests/pump-creator-fees.test.js` gained 8 new cases (timeline paging/summing, share paging/truncation, reconciliation arithmetic), all passing; a pre-existing, unrelated DDL gap in `tests/agent-earnings-board.test.js` (missing `agent_commerce_invoices` table, from an earlier unrelated commit) was fixed alongside the new columns so that suite's 10 tests pass too. The new migration (`api/_lib/migrations/20261015090000_agent_coin_earnings_timeline.sql`) is written and verified idempotent and syntactically valid via a throwaway PGlite run, and the full `launch-detail.js` handler was proven correct end to end against a PGlite database with both migrations applied and a seeded row, matching the exact JSON shape documented above. It cannot be applied to the real production database from this session (hard-denied), so a live curl against production still returns `creator_fees.distributed: null` until it lands; the query and render logic are verified correct via the PGlite and Playwright route-interception runs described above instead. UI verified at 375/768/1440 with zero console errors via Playwright. 2026-10-15 re-verification: `npm run db:status` confirms `20261015090000_agent_coin_earnings_timeline.sql` is still `[pending]` against the real production database (10 pending migrations total, none specific to this order applied); `information_schema.columns` on the live `agent_coin_earnings` table confirms the five new columns genuinely do not exist yet; a live local server (`node --env-file=.env.local server/index.mjs`) against the real production DB answered `/api/pump/launch-detail` for a real earning mint with `economics.creator_fees: null` and no 500, confirming the degrade-to-null wrapper behaves exactly as designed while unmigrated; `tests/pump-creator-fees.test.js` and `tests/agent-earnings-board.test.js` re-run clean (24/24); no code or test changes were needed this pass. See [OWNER-ACTIONS row 63](_context/production-100-OWNER-ACTIONS.md) for the exact migration-apply command and a critical ordering note: the migration must land before this code deploys, or the combined old+new column SQL select throws and the pre-existing enrichment-degrades-to-null wrapper silently drops `economics.creator_fees` to `null` for every coin until it does. Leaving this file in place until that migration lands.--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 diff names pump.fun endpoints (commit 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--Order 015 (parity 01) builds per-agent creator earnings from pump.fun fee totals. The owner's `pumpfun-creator-rewards` repo has a stronger source for the per-coin number: it sums the `distribution` events in `swap-api.pump.fun/v1/coins/<mint>/timeline`, pages `fee-sharing/account/<wallet>/shares`, and reconciles the two so the displayed figure carries its own audit. `api/_lib/pump-creator-fees.js` only has per-wallet totals and nothing here calls either endpoint. This order makes the per-coin figure reconciled and gives the snapshot from 015 a second, independent source.--## Step 0: re-derive the current state-- ls prompts/finish/015-parity-01-creator-earnings.md 2>/dev/null && echo "015 still open"- ls api/_lib/creator-earnings-snapshot.js api/_lib/agent-earnings.js- grep -n "timeline\|fee-sharing" api/_lib/pump-creator-fees.js api/pump/launch-detail.js | head- curl -s "https://swap-api.pump.fun/v1/coins/FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump/timeline" | head -c 500--If 015 is still open, run it first; this order extends its snapshot rather than building a parallel one.--## Tasks--1. Port `fetchCoinEarnings`, `fetchAllShares` and the reconciliation from upstream `lib/pump.js` into `api/_lib/pump-creator-fees.js`, behind the existing circuit breaker used by `launch-detail.js` (do not add a second client).-2. Feed the per-coin snapshot (from 015, in `api/_lib/creator-earnings-snapshot.js`) from the timeline sum, and store the reconciliation delta and its source.-3. Show "this coin paid X SOL" with the reconciliation note on `/launches/<mint>` (`src/launch-detail.js`) and in the agent earnings card.-4. Docs: the `method` string in the earnings API names both sources.--## Definition of done--- [ ] `tests/pump-creator-fees.test.js` gains cases for timeline summing, share paging and reconciliation against recorded $THREE responses.-- [ ] `curl -s 'localhost:3000/api/pump/launch-detail?mint=FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump'` shows the per-coin figure with its reconciliation.-- [ ] UI verified at three widths, zero console errors; docs and changelog updated.--## Never blocked--| Blocker | Resolution (act, do not ask) |-|---|---|-| The timeline endpoint is down | The breaker serves the last snapshot with `refreshed_at`; never invent a number. |-| The two sources disagree by more than 1% | Show both and the delta; that disagreement is the feature, not a bug. |--## 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/510-integrate-11-per-coin-earnings-source.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.mdindex 75456b2ac..d46a779c4 100644--- a/prompts/finish/_context/integrate-PROGRESS.md+++ b/prompts/finish/_context/integrate-PROGRESS.md@@ -1428,3 +1428,7 @@ Remaining (orders kept): 539 page cells need a post-deploy browser check against## 2026-10-23: order 547 (integrate 48, Robinhood Crypto MCP tools), doneFour read-only tools (`robinhood_chain_stats`, `robinhood_token_prices`, `robinhood_recent_launches`, `robinhood_wallet_holdings`) in `api/_mcp/tools/robinhood.js`, registered in the catalog. Evidence: a live `robinhood_chain_stats` call returned block 96324688 on chain 4663, `tests/mcp-catalog.test.js` plus `tests/api/v1-robinhood.test.js` 28 passed (the launches test was updated for the NOXA removal), `audit:mcp-safety` passes. Docs section added to `docs/mcp.md`.++## 2026-10-25: order 510 (integrate 11, per-coin earnings source), done++Code shipped in 98744d430. Close-out found `20261015090000_agent_coin_earnings_timeline.sql` already `[applied]` in production (`npm run db:status`), the five new columns present on `agent_coin_earnings`, `tests/pump-creator-fees.test.js` plus `tests/agent-earnings-board.test.js` 24/24, and `launch-detail` answering 200 with `creator_fees.distributed` and `reconciliation` keys for a real earning mint (values fill when the snapshot cron next runs). OWNER-ACTIONS row 63 removed. Production still needs the normal deploy to serve the new code.diff --git a/prompts/finish/_context/production-100-OWNER-ACTIONS.md b/prompts/finish/_context/production-100-OWNER-ACTIONS.mdindex 69ab7b3c9..ccfe9225b 100644--- a/prompts/finish/_context/production-100-OWNER-ACTIONS.md+++ b/prompts/finish/_context/production-100-OWNER-ACTIONS.md@@ -77,7 +77,6 @@ on it; some resolve themselves as other work lands.| 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) || 67 | **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; renumbered from a collided row 63 by the 2026-10-15 triage-lane sweep, two concurrent agents having picked the same number in this shared worktree; row 63 stays with the per-coin earnings migration below). 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`) || 64 | **Create the mainnet native-launchpad curve config and pin it, activating the lane** (added 2026-10-14 by the evolve loop closing out order 512-integrate-13). `api/_lib/native-launch/config.js`'s curve now opens every pool at a 50% anti-snipe trading fee that decays exponentially to the steady-state 1% over the first 100 slots (Meteora DBC's own fee scheduler, verified by `tests/native-launch-curve.test.js`, a devnet e2e run against a local validator cloning the real DBC/Token-2022/ATA/Metaplex programs, and a zero-cost `--simulate` run against the live mainnet DBC program). Production currently has zero `NATIVE_LAUNCH_*` env vars set (`gcloud run services describe three-ws-api --region us-central1` env list checked), so this is first-time lane activation, not a change to a live config; no existing launch is affected. Exact command: `node scripts/native-launchpad-create-config.mjs --network mainnet`, needing `NATIVE_LAUNCH_PARTNER_SECRET_BASE58` (or `X402_TREASURY_SECRET_BASE58` as a fallback signer) funded with at least 0.05 SOL in that wallet (the script's own balance floor for rent + fees headroom); the on-chain spend itself is about 0.006 SOL (this order's own estimate for the `createConfig` transaction's rent and fee). Optionally set `NATIVE_LAUNCH_FEE_WALLET` first if the platform's fee claimer should be a wallet other than the signer. The script prints the created config pubkey and the exact env line to pin; run `gcloud run services update three-ws-api --region us-central1 --update-env-vars NATIVE_LAUNCH_CONFIG_KEY=<printed pubkey>` (config-only, pre-approved) to put the lane live. | one `node scripts/native-launchpad-create-config.mjs --network mainnet` run (~0.006 SOL) + one `gcloud run services update --update-env-vars` pin | Activates the native $THREE launchpad lane on mainnet with the decaying anti-snipe fee baked into the curve from the very first launch | [512-integrate-13-anti-snipe-native-lane.md](../512-integrate-13-anti-snipe-native-lane.md) |