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 508, five-tab Transaction V1 lab shipped on /atomic

nirholasa88b78d74ae3
diff --git a/prompts/finish/508-integrate-09-atomic-v1-lab.md b/prompts/finish/508-integrate-09-atomic-v1-lab.md
deleted file mode 100644
index b44ac757e..000000000
--- a/prompts/finish/508-integrate-09-atomic-v1-lab.md
+++ /dev/null
@@ -1,59 +0,0 @@
-# integrate 09: fold the seventy transaction-v1 tools into one real lab at /atomic
-
-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, no gate.
-
-## 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 is not expected to hit one. 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
-
-The owner published about 70 single-page repos about Solana transaction v1 (`txv1-inspector`, `txv1-size-lab`, `transaction-diff`, `config-mask-decoder`, `loaded-data-calculator`, `priority-fee-modeler`, `account-map-v1`, `v1-wallet-check`, `rpc-v1-canary`, `indexer-v1-canary`, `sponsor-cap-auditor`, `bundle-to-v1`, `atomic-batch-builder` and many more). The survey found they are one template: after removing each repo's product line and example text, every `app.js` has the same md5, and none of them decodes anything (the "inspector" hashes its input and estimates a size). Integrating 70 of them would import nothing. The concepts are good, though, and `/atomic` already has real v1 decoding (`api/_lib/solana/transaction-v1.js`, `inspectWireTransaction`). This order builds the real versions of the tooling concepts in one place.
-
-## Step 0: re-derive the current state
-
- sed -n 1,60p api/_lib/solana/transaction-v1.js
- grep -n "findV1WalletStandardSigner" src/onchain/adapters/solana.js
- grep -n '"/atomic"' -A4 data/pages.json
- ls node_modules/@solana/kit >/dev/null && echo kit-ok
-
-## Tasks
-
-Build these as tabs on `/atomic`, all real computation over `@solana/kit` and the existing v1 code, nothing estimated where it can be computed:
-
-1. **Size and budget planner**: paste instructions or a serialized transaction; get exact bytes against the 1,232-byte legacy and 4,096-byte v1 ceilings, the loaded-accounts-data-size limit with headroom, a priority fee total for a chosen micro-lamports-per-CU, and a duplicate-account check (the v1 sanitization rule).
-2. **Config mask decoder**: decode the v1 `u32` config mask and its fixed-width resource values from a real transaction.
-3. **Legacy vs v0 vs v1 diff**: the same instruction set compiled three ways, byte by byte.
-4. **Wallet v1 capability check**: uses `findV1WalletStandardSigner` to report whether the connected wallet honestly advertises v1 signing.
-5. **Sponsor cap view**: for a v1 transaction, the fee and resource caps a paymaster or co-signer is agreeing to.
-6. Deep links (`/atomic?tab=planner`), keyboard navigation between tabs, every state designed.
-7. **Docs**: `docs/atomic.md` sections per tab; update the `/atomic` description in `data/pages.json`.
-
-Do not copy any code from the 70 repos; there is none worth copying. Credit the concept repos in the docs page footer only if the commit-gate approval covers it (they do not name other crypto projects, so it does).
-
-## Definition of done
-
-- [ ] Vitest cases for the planner, mask decoder and diff against recorded real transactions.
-- [ ] Each tab browser-verified at 375, 768 and 1440 px, both themes, zero console errors.
-- [ ] `npm run check:pages` passes; docs and changelog updated.
-
-## Never blocked
-
-| Blocker | Resolution (act, do not ask) |
-|---|---|
-| v1 is not yet live on the cluster you test against | Build and decode locally with `@solana/kit`; the size math does not need a live cluster. Say which parts need mainnet v1 in the report. |
-| A browser wallet is unavailable in headless testing | Verify the capability check's logic with a Wallet Standard test double in vitest and the real UI path manually with whatever wallet is installed; report which. |
-
-## 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/508-integrate-09-atomic-v1-lab.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 04506961b..ee4bd75e4 100644
--- a/prompts/finish/_context/integrate-PROGRESS.md
+++ b/prompts/finish/_context/integrate-PROGRESS.md
@@ -360,3 +360,62 @@ fixture account is the $THREE mint or a synthetic placeholder.
Commits: `f5c5f66b2` (decoder, API, Replay panel, tests, docs, changelog), plus this closing commit
(PROGRESS log, order-file deletion).
+
+## 2026-10-14: order 508-integrate-09 closed (evolve)
+
+Built five real tabs on `/atomic` beyond the Inspector, replacing the "concept value" of the ~70
+templated Solana transaction-v1 repos the owner found (every one of them hashes its input and
+estimates a size instead of decoding anything; none of their code was copied). All five compute
+over `@solana/kit` and the existing `api/_lib/solana/transaction-v1.js` v1 code, nothing estimated:
+
+- **Size and budget planner**: compiles a pasted fee payer + instruction set with `@solana/kit` to
+ an exact wire byte count against the legacy/v0 1,232-byte ceiling or the v1 4,096-byte ceiling,
+ with headroom, the resolved resource budget (compute unit limit, loaded-accounts-data-size limit,
+ heap size), an exact priority-fee lamport total for a chosen micro-lamports-per-CU, and the v1
+ duplicate-static-account sanitization check.
+- **Config mask decoder**: reads a real v1 transaction's exact `TransactionConfigMask` u32 and its
+ fixed-width `ConfigValues` byte by byte (mask hex, binary string, popcount, per-field raw bytes
+ and decoded value), flags a half-set priority-fee bit pair as invalid, and flags any bit above 4
+ as reserved for a future SIMD.
+- **Legacy vs v0 vs v1 diff**: the identical instruction set compiled three ways, byte-exact, with
+ the real delta either direction (v1 is not assumed to always win: its inline config can make a
+ tiny transaction larger than legacy or v0, and the diff reports that honestly).
+- **Sponsor cap view**: for a v1 transaction, the exact fee and resource caps a paymaster or
+ co-signer is agreeing to, read from the inline `transactionConfig`, not a Compute Budget
+ instruction scan that sees nothing on a v1 transaction.
+- **Wallet v1 capability check**: calls the existing `findV1WalletStandardSigner` (same helper the
+ rest of three.ws calls before ever requesting a real v1 signature) against the browser's injected
+ wallet and reports its real Wallet Standard verdict and advertised versions.
+
+All six tabs (Inspector plus the five above) are reachable by click, by `ArrowLeft`/`ArrowRight`/
+`Home`/`End` keyboard navigation computed from the currently-selected tab, and by deep link
+(`/atomic?tab=mask`, `?tab=sponsor`, `?tab=planner`, `?tab=diff`, `?tab=wallet`). `docs/atomic.md`
+gained a "The lab: five more tools" section plus an API section per tab; `data/pages.json`'s
+`/atomic` description now names the lab instead of just the Inspector.
+
+Verified live: `npx vitest run tests/transaction-v1-lab.test.js tests/transaction-v1.test.js
+tests/atomic-page.test.js` passes, 21/21, against real compiled/decoded transactions (no mocks):
+`decodeV1ConfigMask` against a real partially-signed v1 wire transaction built with
+`buildPartiallySignedV1Transaction`, `planTransactionSize` against a real `SystemProgram.transfer`
+instruction compiled through `@solana/kit`, `diffTransactionVersions` against the same instruction
+compiled legacy/v0/v1. A Playwright script drove the real page at 375, 768, and 1440px in both
+light and dark themes: all six tabs render with zero console errors, arrow-key/Home/End navigation
+correctly wraps from the currently-selected tab, and each deep link opens its tab directly. A second
+Playwright pass exercised real form submissions (planner and diff against a local API server
+running the real handler, since Vite's dev proxy forwards undeployed endpoints to production) and
+the mask/sponsor tabs against a real mainnet signature, confirming real decoded values (not
+placeholder text) render in the report panel. `npm run check:rules -- --paths <touched files>`
+exits 0. `npm run build:chat && npm run build && npm run check:pages` passes clean: all 962
+declared pages resolve (952 static, 10 api, 0 redirect, 0 external); `/chat` needs its own
+`build:chat` sub-build step (a pre-existing repo quirk unrelated to this diff, confirmed via
+`git log` showing `vite.config.js` untouched since well before this order started).
+
+One judgment call: full 84-locale translation of the new `atomic.*` i18n keys is blocked by the
+project-wide GCP billing dunning hold (`Lightning dunning decision is deny`, both Vertex ADC and
+the Generative Language API key path return 403), already tracked as row 20 in
+`prompts/finish/_context/production-100-OWNER-ACTIONS.md` (which names this exact i18n translation
+gap). The English source strings are complete and correct; this is a pre-existing, owner-only
+billing blocker, not something left unwired by this order.
+
+Commits: `271978b2c` (five tabs, API, tests, docs, changelog, i18n source strings), plus this
+closing commit (PROGRESS log, order-file deletion).