{"assessments":[],"deployments":[],"fuzz":[],"identity":{"adapter":"0xde152afb7db5373f34876e1499fbd893a82dd336","chainId":1,"collection":"0x0000ec93127baa929e58e97dd0095a2bfb38ec1d","registry":"0x8004a169fb4a3325136eb29fa0ceb6d2e539a432"},"interpretation":"Records acceptance and evidence. Neither completion nor an AI assessment establishes correctness, safety, or independent review.","jobId":"29b1df0b-843b-4e71-a669-543cd48a4133","kind":"skill:build-website","nodes":[{"acceptedSubmissionHash":"37909e26e4561f20e6e47d807c485ae9d35251e78ae6cbd6fc8f8073ddb32192","dependsOn":[],"execution":{"mustProduce":["dist/index.html"],"network":true,"optionalTools":["browser"],"profile":"none","requires":["network"],"skillHash":"a60bc8b42446c13d993341179fe13c712a5addb118fc532fb2d15e71f912efc8","skillId":"build-website","tools":[]},"key":"build_website","kind":"code","role":"implement","skillHash":"a60bc8b42446c13d993341179fe13c712a5addb118fc532fb2d15e71f912efc8","skillId":"build-website","state":"accepted"},{"acceptedSubmissionHash":"e40cb2390dc18e400354568ebcf32e30195f13b4196ccd79f9fb7907da8ae638","dependsOn":["build_website"],"execution":{"network":true,"optionalTools":["browser"],"profile":"none","requires":["network"],"skillHash":"fd33b6741366d364a55a4c0ba2bc4f5d329cec0b62f27a83289dc5b30ab03575","skillId":"design-critic","tools":[]},"key":"design_critic","kind":"code","role":"review","skillHash":"fd33b6741366d364a55a4c0ba2bc4f5d329cec0b62f27a83289dc5b30ab03575","skillId":"design-critic","state":"accepted"}],"objective":"# IMD LAUNCHPAD — MULTI-CHAIN SWAP + FULL SWARM INTEGRATION\n\n**EXISTING WEBSITE:**\nhttps://imd-launchpad-idea-in-ecosy-df03.imd.site/\n\nUpgrade this exact website. Preserve its design, branding, and existing features. Do not create a duplicate.\n\n## 1. MULTI-CHAIN SWAP\n\nAdd a complete SWAP page supporting:\n\n- IMD (Ethereum)\n- ETH (Ethereum)\n- SOL (Solana)\n- USDC (Ethereum and Solana)\n- USDT (Ethereum and Solana)\n- PIMD (Solana, once deployed)\n\nUsers must be able to swap between these assets, including supported cross-chain swaps between Ethereum and Solana.\n\nIntegrate established DEX aggregators such as Jupiter for Solana, 0x or equivalent for Ethereum, and a reputable cross-chain swap provider.\n\nSupport MetaMask, Rabby, Phantom, and Solflare.\n\nShow token balances, prices, exchange rates, fees, slippage, estimated output, routes, network, transaction status, and explorer links.\n\nUse verified token addresses, liquidity, and real quotes. If a route is unavailable, clearly explain why.\n\nAll swaps must be non-custodial, with explicit user authorization. Never invent liquidity, prices, or swap routes.\n\n## 2. AUTOMATIC SOLANA TOKEN LAUNCH\n\nUsers must be able to create Solana tokens as easily as on Pump.fun.\n\nConnect a Solana wallet, enter name, ticker, image, optional description/socials and initial SOL buy, then click CREATE & LAUNCH.\n\nAutomatically generate technical metadata and integrate Raydium LaunchLab for bonding curves, token deployment, trading, liquidity, and graduation.\n\nNo administrator approval or manual developer intervention for ordinary launches. Users approve their own wallet transactions.\n\n## 3. LAUNCH TOKEN + BUILD WITH SWARM TOGETHER\n\nThis is the main feature.\n\nCreate a unified **LAUNCH + BUILD WITH SWARM** workflow.\n\nUsers can launch a Solana token while IMD Swarm builds the rest of their project.\n\nAllow users to select:\n\n- Website or landing page\n- Smart contracts\n- NFT collections\n- Security audits and code reviews\n- Oracle integrations\n- Games and mini-apps\n- Images and logos\n- Audio and music\n- Videos and animations\n- Branding and marketing\n- X and Telegram content\n- Documentation and tokenomics\n- Full applications and dApps\n- Other supported IMD Swarm services\n\nUsers choose one service, multiple services, or a complete project package.\n\nThe token launch and Swarm jobs must run as independent workflows. A successful token launch should not depend on completion of AI jobs.\n\nShow real-time progress, worker assignments, deliverables, and completion status.\n\nUse actual IMD Swarm capabilities and APIs. Do not simulate unsupported services.\n\n## 4. IMD SWARM PAYMENT\n\nAdd a visible **BUILD WITH IMD SWARM** button.\n\nDisplay the verified official job fee, currently expected to be 0.5 IMD per eligible job.\n\nUsers connect MetaMask or Rabby, review costs, approve payment, and submit real Swarm jobs.\n\nFor multiple services, calculate the actual total fee before payment.\n\nShow job IDs, worker progress, deliverables, and continuation options.\n\nNever invent payment wallets or double-charge users.\n\n## 5. WALLET INTEGRATION\n\nProvide one wallet interface supporting:\n\n- MetaMask — Ethereum\n- Rabby — Ethereum\n- Phantom — Solana\n- Solflare — Solana\n\nAllow independent Ethereum and Solana connections, with network switching, balances, and transaction history.\n\n## 6. PUMP IMD (PIMD)\n\nIntegrate the planned Pump IMD ecosystem token:\n\nName: Pump IMD\nTicker: PIMD\nSupply: 1,000,000,000\nBlockchain: Solana\n\nSupport its approved deployment, PIMD/SOL trading, airdrops, ecosystem reserves, and utility.\n\nProposed distribution: 30% public/liquidity, 30% airdrops, 20% development, 10% marketing, 10% developer treasury.\n\nUse transparent allocation wallets, vesting, and appropriate security controls.\n\n## 7. IMD REVENUE AND BURNS\n\nAllocate eligible net platform revenue:\n\n- 25% IMD ecosystem treasury\n- 20% Operations and development\n- 20% IMD NFT worker rewards\n- 20% IMD buyback and permanent burn\n- 15% Developer IMD accumulation\n\nUse verified Ethereum IMD transactions, protected treasury controls, and public reporting. Never use customer deposits as revenue.\n\n## 8. PROJECT STUDIO AND TRADING\n\nMaintain Pump.fun-style token discovery, charts, buy/sell, trending tokens, portfolios, comments, creator profiles, watchlists, and live activity.\n\nEvery project receives a Studio for its token, website, files, Swarm jobs, branding, marketing, NFT collections, and ongoing development.\n\nUsers can return anytime to hire Swarm for additional work.\n\n## 9. SECURITY AND DEPLOYMENT\n\nBuilders choose compatible SDKs, RPC providers, swap integrations, and APIs.\n\nVerify all IMD contract addresses and payment destinations.\n\nUse secure wallet connections, explicit signatures, transaction simulation where available, slippage protection, and audit logs.\n\nTest Solana and Ethereum integrations before production.\n\nDo not request private keys or seed phrases.\n\nDeliver functional integrations, not simulated interfaces. Clearly report unavailable APIs or unsupported features.\n\n**FINAL GOAL:** One website where users can swap IMD, ETH, SOL, USDC, USDT, and PIMD; create Solana tokens instantly; and simultaneously hire IMD Swarm to build websites, contracts, NFTs, audits, oracles, games, images, audio, video, and complete ecosystems.\n\n**IDEA IN. ECOSYSTEM OUT.**","parentJobId":null,"planHash":"7baa9a715a51aa8ce1b6bcfcb181c8b38dfc932a08ed8239805404245ac83e6a","previousHash":"b77223722e74d5666e225a80e14383d7481dfa3e2e68c3e9b923fcd4a546b9c7","projectId":"29b1df0b-843b-4e71-a669-543cd48a4133","publication":{"commit":"051efd9009ee9e0f595557744881144a643cff23","deliveredAt":"2026-11-15T03:29:23.383Z","repoUrl":"https://github.com/identity-md-launches/launch-3273-imd-launchpad"},"receiptIdentity":{"adapter":"0xde152afb7db5373f34876e1499fbd893a82dd336","chainId":1,"collection":"0x0000ec93127baa929e58e97dd0095a2bfb38ec1d","registry":"0x8004a169fb4a3325136eb29fa0ceb6d2e539a432"},"registry":"0xb6d0a187b050fa5bb0b87033a203f37becf4a775","research":[],"schema":"identitymd-work-v1","signals":[],"site":{"cid":"bafybeihtv6fy43befzzeszr2orbl2cwuldtu2dcvstoryythjypmcs47m4","ensName":"imd-launchpad-idea-in-ecosy-29b1.identitymd.eth","namingTransaction":"0x75ca9b52efc486ad932c80fcfd2db84319a721d30d1672fffbd4d2ce5d001826"},"snapshotHash":"bfb131eac429d3bb745441b8fccf4d1943b5fab90f1978d7fed73306359992dc","state":"completed","submissions":[{"artifacts":[],"attempt":1,"bundleHash":"5eccb59f5740f42c8bedff84d08245b4ea049221a9499de2c50fd951753365c1","device":"be85220723d9ce9d","findings":[],"hash":"37909e26e4561f20e6e47d807c485ae9d35251e78ae6cbd6fc8f8073ddb32192","nodeId":"427f0492-c845-43b1-a8b8-61de598fa6f7","outcome":"completed","summary":"I reproduced all 10 review findings and fixed each one. The rebuilt `dist/` (2.4 MB) is in the working tree, uncommitted, alongside the source changes and the updated README and DESIGN.md. Each finding's answer is in `.imd-responses.json`, all marked \"fixed\".\n\n**High findings**\n- **Worker assignments:** the live job response for `1496b318…` lists its workers under `nodes` with a `seat`, so the old code showed none. The job card now reads `nodes`, so both workers appear (seat #392 and seat #874, both accepted). That job also has no files, only a delivered repository and source bundles, so those now count as deliverables too.\n- **Live activity:** the token page now re-reads market and bonding-curve data every 30 seconds while the tab is visible, and stops when you leave the page. It shows when it last updated; if a refresh fails it keeps the last data and says it's stale.\n- **Jobs started before a launch:** the Launch + build page now creates a local project ID before either track starts, and both the launch record and the job records store it. After a launch, earlier jobs are given the new mint, so they show in that token's Studio. Jobs saved before this change are matched by the token name in their brief. Neither track waits for the other.\n- **Cross-chain slippage:** the minimum you reviewed is now a hard floor. If the final quote returns less, the swap stops before anything is simulated or signed, shows the new quote, and asks you to confirm again.\n\n**Medium findings**\n- The hero **Build with IMD Swarm** button now scrolls to the builder instead of jumping back to the top.\n- The **wallet dialog** keeps Tab inside itself, blocks the page behind it, and returns focus to the Connect button when it closes.\n- Choosing a slippage preset clears the custom field, and a line always shows the limit actually in use.\n- Clearing the amount now discards any quote that arrives late.\n- If a result fetch fails, the job card shows \"Deliverables could not load. Retrying…\" and tries again until it works.\n- When a quote service refuses the request (like the KyberSwap 403), the message now says the service is unavailable rather than claiming there's no liquidity. Real \"no route\" answers from the providers keep their own messages.\n\n**Checks run**\n- Typecheck and production build: both pass.\n- Browser tests in headless Chromium against the built site, with saved real API responses and injected failures and delays: 22 of 22 pass. To get Chromium running I extracted its missing system libraries into a temp folder outside the repo.\n- Tests of the real swap code with wallets stubbed out: 9 of 9 pass. This includes your exact case (0.5% limit, reviewed minimum 0.995 SOL, new quote 0.9751 SOL), which now stops before any signing.\n- Design probe: all 16 checks pass at 320, 390 and 1440 wide. At 390 the headline, the Build with IMD Swarm button and the Create & launch form still show on the first screen.\n\n**Not tested:** no real transactions were signed, since there was no funded wallet. The screen that asks you to re-confirm a lower cross-chain quote needs connected wallets, so I checked it by reading the code and through the swap-code tests rather than in a browser.","treeHash":"5420f5aa7d9cca9af0462b12e75a5dcf626c05f0","usage":{"cachedInputTokens":4228314,"cost":{"source":"runtime","usdMicros":2993995},"inputTokens":71,"model":"claude-opus-5-5","outputTokens":46594,"runtime":"claude","turns":47,"wallClockMs":686959}},{"artifacts":[],"attempt":1,"bundleHash":"3179785e2d90b69163471ea3feb7cb1f8723dbc613ec1d5bfb60879e19162a32","device":"b4f6137e7c93a2b3","findings":[],"hash":"9e82fdf3929a9d7b25921fb82aae388b8e4dc7905db562d8d2cf1df31ff31c19","nodeId":"427f0492-c845-43b1-a8b8-61de598fa6f7","outcome":"completed","summary":"I've upgraded the IMD Launchpad and committed it as `c21557b` on `main`: source, lockfile, the `dist/` export, `DESIGN.md` and `README.md`, about 3.1 MB in total. The typecheck and production build pass, and a test run against the live services passed every check. No real wallet transactions were signed, and I couldn't look at the site in a browser on this machine.\n\n**How it was built.** The live site only published a compiled bundle, so I rebuilt it as Vite + React + TypeScript. Its stylesheet is kept unchanged, so the design and branding carry over. Its existing pages (Discover, token pages, Portfolio, creator profiles, PIMD, Revenue) are all still there. I took its contract addresses, contract interfaces, IMD API calls and Raydium LaunchLab calls from that bundle.\n\n**What's new:**\n- **Swap**:\n  - Ethereum-to-Ethereum swaps go through KyberSwap, standing in for 0x because 0x now needs an API key.\n  - Solana swaps go through Jupiter.\n  - Ethereum↔Solana swaps go through LI.FI.\n  - The page shows balances, prices, rate, minimum received, price impact, fees, route, network, step-by-step status and explorer links.\n  - Each swap is simulated before you sign, and token approvals are for the exact amount only.\n  - PIMD is listed, and a swap involving it is refused with the reason: it isn't deployed yet.\n- **Launch + build** (home page): the token form creates the token on Raydium LaunchLab, on devnet or mainnet. Swarm jobs run on a separate track, so neither waits for the other.\n- **Swarm payment**:\n  - You can pick one of 14 services, several, or a 5-job package; each maps to a skill on the live IMD Swarm list.\n  - The fee comes from the official payment contract, and the total is fee × number of jobs.\n  - One approval covers the exact total; then each job is paid with its own signature.\n  - Paying twice for the same brief needs an explicit tick.\n  - Each job then shows its ID, workers, deliverables, and options to continue it.\n- **Wallets**: one control with Ethereum (MetaMask, Rabby, other extensions, Coinbase) and Solana (Phantom, Solflare) connected separately. It shows balances, Ethereum network switching, the devnet/mainnet choice for launches, and transaction history.\n- **Studio** for each project: its token, jobs, deliverables, and a way to hire Swarm again.\n\n**Checks that ran:**\n- Typecheck and production build both pass.\n- The payment contract returned 0.5 IMD as the job fee.\n- Real quotes came back for six swaps:\n  - ETH→IMD\n  - IMD→USDC\n  - SOL→USDC\n  - USDT→SOL\n  - SOL→IMD across chains\n  - USDC from Ethereum to Solana\n- `dist/index.html` has the title, favicon, description, og:title and og:image, and uses only relative URLs.\n\n**Not verified:**\n- **Real transactions:** wallet connect, Swarm payment, swap sending and a devnet token launch need a browser wallet with funds, which this machine doesn't have.\n- **Anything visual:** the design probe couldn't start Chromium (a system library is missing and can't be installed without root). So there are no screenshots, the first screen at 390px wasn't seen, and console and overflow weren't checked.\n- **Design review:** it was done from the source. It found three problems, now fixed:\n  - the Build with IMD Swarm button was hidden on phones;\n  - the Discover tabs had no arrow-key support;\n  - a fee step showed up as a route hop in swap routes.\n\n  One remains open: the wallet panel doesn't keep keyboard focus inside it. All of this is written up in the README.\n\n**Values only the IMD team can supply.** These are blank in `src/config.ts`, and the pages that need them say \"not published\" or \"not deployed\":\n- PIMD's token address and its allocation wallets\n- the revenue-split wallets\n- a metadata upload endpoint\n- a dedicated Solana RPC\n\n**Other limits:**\n- **Token metadata isn't fully automatic yet.** The site writes the metadata file, but with no server the creator has to host it and paste the link. Setting the upload endpoint removes that step.\n- **Some data stays on one device.**","treeHash":"1846f3e3b5a5584ceb3580410fb345ef3036b1b1","usage":{"cachedInputTokens":5277898,"cost":{"source":"runtime","usdMicros":4872738},"inputTokens":89,"model":"claude-opus-5-5","outputTokens":113110,"runtime":"claude","turns":48,"wallClockMs":1096702}},{"artifacts":[],"attempt":1,"bundleHash":null,"device":"6d18805b99aeb48a","findings":[],"hash":"e40cb2390dc18e400354568ebcf32e30195f13b4196ccd79f9fb7907da8ae638","nodeId":"cc7a18e0-2421-4bb1-81f9-2a66eaccb14a","outcome":"completed","summary":"| Area | Previous | This review |\n|---|---:|---:|\n| Requirements | Not tallied | 39 met; 0 missing; 0 faked; 8 need requester; 1 after review |\n| Broken features | 10 | 0 reproduced |\n| Product and action on first screen, 390px | — | Yes |\n| taste@1 | — | 16/16 passed |\n| Copy findings | — | 0 |\n| Share card | — | Present and valid |\n\nAll ten previous findings are fixed. [.imd-findings.json](.imd-findings.json) contains `{\"findings\":[]}`. Application files are unchanged.\n\n| Previous finding | Verification |\n|---|---|\n| Worker assignments | Both real seats, agents and accepted states render. |\n| Frozen market and curve data | Both refresh every 30 seconds; failures show stale-data feedback; navigation stops polling. |\n| Pre-launch jobs missing from Studio | Shared-project and legacy records both appear. |\n| Cross-chain slippage | A lower minimum triggers re-review before simulation or signing. |\n| Home builder button | Scrolls to the service picker while preserving the route. |\n| Wallet focus escape | Focus stays inside, background becomes inert, and closing restores focus. |\n| Conflicting slippage controls | Presets clear the custom field and display the effective limit. |\n| Obsolete quote restoration | Clearing the amount keeps output and route details empty. |\n| Delivery polling failure | A first-result 503 retries successfully, then polling stops. |\n| Incorrect liquidity diagnosis | Provider access failures display service-unavailable messages. |\n\nThe browser checks passed in Chromium and WebKit: 22/22. The source-level swap checks passed 9/9. Signed transactions remain unverified.\n\nThe counts above cover these 48 grouped requirement checks. “Met” records inspected implementation and tested reachable behavior.\n\n| # | Requirement | Status and evidence |\n|---:|---|---|\n| 1 | Upgrade the existing website; preserve design, branding and features | **Met** — original stylesheet preserved byte for byte; [App] and [Home]. |\n| 2 | IMD, ETH, SOL, Ethereum/Solana USDC and USDT | **Met** — token definitions in [swap API]. |\n| 3 | PIMD swaps once deployed | **Needs requester** — approved mint in [config]. |\n| 4 | Same-chain and Ethereum↔Solana swaps | **Met** — quote and execution paths in [swap API]. |\n| 5 | Jupiter, Ethereum aggregator equivalent, reputable cross-chain provider | **Met** — Jupiter, KyberSwap and LI.FI in [swap API]. |\n| 6 | MetaMask, Rabby, Phantom and Solflare | **Met** — [wallet sheet], [Ethereum wallet] and [Solana wallet]. |\n| 7 | Balances, prices, rates, fees, slippage, estimated output, routes, network, status and explorer links | **Met** — [Swap] and [Flow]. |\n| 8 | Verified assets, real quotes/liquidity and clear unavailable-route explanations | **Met** — [swap API]; real quote reads and provider-error reproductions checked. |\n| 9 | Non-custodial swaps with explicit authorization | **Met** — wallet signing paths in [swap API]. |\n| 10 | Solana connection; name, ticker, image, optional description/socials/initial SOL; Create & Launch | **Met** — [Launch]; validation, review and wallet prompt checked in both browsers. |\n| 11 | Automatically generate technical metadata | **Met** — `buildMetadata` in [LaunchLab]. |\n| 12 | Automatic metadata hosting and an ordinary launch without manual hosting | **Needs requester** — `metadataUploadUrl` is empty; [Launch] explains the hosting step. |\n| 13 | LaunchLab curves, deployment, trading, liquidity and graduation | **Met** — SDK integration in [LaunchLab]; signed execution remains unverified. |\n| 14 | No administrator approval; users approve transactions | **Met** — [Launch] and [LaunchLab]. |\n| 15 | Unified Launch + Build with Swarm workflow | **Met** — [Home]. |\n| 16 | Websites, contracts, NFTs, audits/reviews, oracles, games, images/logos, audio/music, video/animation, branding/marketing, X/Telegram, documentation/tokenomics, applications/dApps and other supported services | **Met** — all 14 choices in [Swarm API] map to published skills. |\n| 17 | One service, multiple se","treeHash":null,"usage":{"cachedInputTokens":2993920,"cost":{"source":"estimated","usdMicros":1099444},"inputTokens":108340,"model":"gpt-6.1-sol","outputTokens":28398,"runtime":"codex","turns":8,"wallClockMs":787962}},{"artifacts":[],"attempt":1,"bundleHash":null,"device":"b3450b02f80aa5c2","findings":[{"citation":"resolved","description":"Now: OrderRow reads job.tasks or job.workflow.items, but the actual IMD job endpoint returns assignments in nodes with a nested seat object; those jobs render no workers.\nChange to: Normalize nodes into the existing Worker assignments list, using node.key, node.state, node.role, seat.tokenId and seat.agentId, and update the Job response type.\nWhy: The brief explicitly requires real-time progress and worker assignments from the actual Swarm API. This is a repository integration defect, not a missing requester credential.","line":179,"path":"src/components/Swarm.tsx","reproduction":"Width 390 or 1440. GET https://api.imd.fun/jobs/1496b318-5803-462e-8195-4411eea4e085: state is completed, tasks is absent, workflow is null, and nodes contains two accepted assignments with seat.tokenId 392 and 874. With that jobId in a locally stored imd:swarm-orders record, open #/swarm and let the existing getJob poll complete. The line cited evaluates to [], so no Worker assignments list appears; expected both real assignments and their states. No wallet or signature is needed to reproduce the read/render mismatch.","severity":"high","snippet":"  const tasks = job?.tasks ?? job?.workflow?.items ?? [];","title":"bug: Swarm worker assignments ignore the real job response"},{"citation":"resolved","description":"Now: The token page labels transaction counts Live activity, but market data and the LaunchLab pool are fetched only on mount or a mint/network change. Counts, price, liquidity and curve progress stay frozen while other users trade; pool data refreshes only after this visitor trades.\nChange to: Refresh the existing market and pool reads on a bounded interval while the token page is visible, clean up the interval on navigation, and show the last successful update or an unavailable state if refresh fails.\nWhy: The brief explicitly requires live activity, charts and trading. Static snapshots presented as live are a feature fidelity failure the repository can fix.","line":62,"path":"src/pages/Other.tsx","reproduction":"At 390×844, open #/token/So11111111111111111111111111111111111111112. Observe the Live activity card. Route /tokens/v1/solana/<mint> to its captured real DexScreener response and count requests, then advance the browser clock 65 seconds. Observed marketRequests=1, Live activity headings=1, update/staleness messages=0. The effect has only [mint, cluster] dependencies and no timer, so it never reads a new market snapshot until navigation. Expected periodic reads and honest freshness feedback; no wallet or transaction is required.","severity":"high","snippet":"  useEffect(() => {\n    if (cluster === \"mainnet\") tokenPairs([mint]).then((p) => setPair(p[0] ?? null)).catch(() => setPair(null)); else setPair(null);\n    readPool(cluster, mint).then(setPool).catch(() => setPool(null));\n  }, [mint, cluster]);","title":"fidelity: Live activity and bonding-curve data never refresh"},{"citation":"resolved","description":"Now: A Swarm job started before launch is stored with mint undefined (SwarmCheckout copies token?.mint). When launch succeeds, onLaunched only sets Home state; it never associates existing orders with the minted token. Studio then filters those jobs out by mint.\nChange to: Give the shared project a stable local identifier before either track starts, persist it on launch and job records, and use that identifier to collect the existing Studio jobs while attaching the mint after launch. Keep both workflows independent.\nWhy: The brief requires launching while Swarm builds independently and a Studio containing every project’s Swarm jobs and deliverables. Starting the jobs first must not lose the project relationship.","line":29,"path":"src/pages/Home.tsx","reproduction":"Width 390×844. Start a website job from Launch + build while the token has a name/ticker but no mint, then complete the token launch and open its Studio. The production writers produce an imd:swarm-orders record without mint and an imd:launched record with mint; there is no reconciliation step. Read-only reproduction: seed those two exact record shapes, with one pre-launch order and a launched Review Project (REVIEW) record, then open #/studio/So11111111111111111111111111111111111111112. Observed title=\"Studio: Review Project (REVIEW)\", storedOrders=1, and \"No jobs for this token yet.\" Expected the already-started website job in that Studio. The fixture represents the source-defined post-success state; no transaction was sent.","severity":"high","snippet":"          <LaunchForm f={f} setF={setF} onLaunched={setLaunched} />","title":"bug: jobs started before a token launch are lost from its Studio"},{"citation":"resolved","description":"Now: Cross-chain execution silently replaces the reviewed quote and accepts a new minimum up to 3% below the minimum the visitor reviewed, regardless of the selected slippage limit. The fresh transaction is used without a new review.\nChange to: Preserve the reviewed minimum as a hard lower bound. If a replacement quote would return less, show that fresh quote in the existing review state and require the visitor to confirm it before entering the signing pipeline.\nWhy: The brief requires explicit authorization and slippage protection; a 0.5% selection must not authorize an additional hidden 3% deterioration.","line":205,"path":"src/lib/swap.ts","reproduction":"At 390×844 on #/swap, the relevant state is ETH→SOL, selected slippage 0.5% (50 bps), reviewed output 1 SOL and minimum 0.995 SOL. Make the executable LI.FI re-quote return output 0.98 SOL and minimum 0.9751 SOL. The cited check accepts it because 0.9751 > 0.995×0.97 = 0.96515, then uses its transactionRequest. Executed the repository’s actual executeSwap through a Node import hook with controlled quote and wallet/RPC fixtures: simulationReached=true, sent=false; an assertion that a below-reviewed-minimum quote must stop before the transaction pipeline failed. The test deliberately stops in simulation, so no signature or send occurs. Expected a new review instead of executing a quote 0.0199 SOL below the reviewed minimum.","severity":"high","snippet":"  if (fresh.minOut < (q.minOut * 97n) / 100n) throw new Error(\"The cross-chain price moved more than 3% since you reviewed it. Review the new quote.\");","title":"bug: cross-chain re-quotes can exceed the reviewed slippage limit"},{"citation":"resolved","description":"Now: The hero button links to #build, but the global hash router handles it as a route change and immediately scrolls back to the top. The visitor remains above the service picker.\nChange to: Handle this existing button as an in-page action with preventDefault and scrollIntoView on #build, without changing the route hash.\nWhy: The main Launch + Build workflow must let visitors reach the Swarm service selection; a button that appears to do nothing breaks that flow.","line":23,"path":"src/pages/Home.tsx","reproduction":"At 390×844, load #/ at scrollY=0 and click the hero Build with IMD Swarm button. After hashchange, location.hash is #build, scrollY is 0, and #build starts at y=887.67, below the viewport. Expected the Build with IMD Swarm section to scroll into view. src/lib/route.ts:13 unconditionally calls window.scrollTo(0,0) on that hash change. Reproduced in Chromium with the committed export.","severity":"medium","snippet":"            <a className=\"button button-small\" href=\"#build\">Build with IMD Swarm</a>","title":"bug: the home Build with IMD Swarm button never reaches the builder"},{"citation":"resolved","description":"Now: The wallet sheet declares aria-modal=true and focuses Close, but it only handles Escape. Tab and Shift+Tab can move focus to links and transaction controls behind the overlay.\nChange to: Keep Tab navigation within the existing dialog, make the background inert while it is open, and restore focus to the opener when it closes.\nWhy: A modal wallet chooser must keep keyboard and screen-reader navigation in the active dialog (WCAG 2.4.3); the visual overlay must not conceal the focused control.","line":42,"path":"src/wallet/WalletSheet.tsx","reproduction":"At 390×844, load #/ and click the header Connect button. Close receives focus. Press Shift+Tab once: document.activeElement becomes the footer IMD link (href=https://imd.fun), and activeElement.closest(\"[role=dialog]\") is null while the dialog remains open. Expected focus to wrap to the final wallet-dialog control. Confirmed in Chromium without any wallet.","severity":"medium","snippet":"  useEffect(() => {\n    const k = (e: KeyboardEvent) => e.key === \"Escape\" && onClose();\n    addEventListener(\"keydown\", k);\n    return () => removeEventListener(\"keydown\", k);\n  }, [onClose]);","title":"accessibility: the wallet dialog lets keyboard focus escape behind it"},{"citation":"resolved","description":"Now: The custom slippage input is uncontrolled. Choosing a preset changes slip but leaves the previous custom percentage visibly entered, so two conflicting limits are shown.\nChange to: Bind the custom input to a dedicated display state and clear it when a preset is selected, or display the effective slip / 100 value consistently in the existing input.\nWhy: Visitors must be able to review the actual slippage protection before authorizing a swap.","line":113,"path":"src/pages/Swap.tsx","reproduction":"At 390×844, open #/swap, enter 25 in Custom slippage percent, then click the 0.1% preset. The custom field still reads 25, while button[aria-pressed=true] reads 0.1% and slip passed to getQuote is 10 bps. Expected a single unambiguous effective percentage. Reproduced in Chromium before connecting a wallet.","severity":"medium","snippet":"              <label className=\"visually-hidden\" htmlFor=\"s-slip\">Custom slippage percent</label><input id=\"s-slip\" className=\"select-small slip-input\" inputMode=\"decimal\" placeholder=\"Custom %\" onChange={(e) => { const v = Math.round(Number(e.target.value) * 100); if (v > 0 && v <= 5000) setSlip(v); }} /></div>","title":"bug: custom slippage shows a different limit from the selected preset"},{"citation":"resolved","description":"Now: Clearing or invalidating the amount returns before incrementing seq.current. An already-running request still matches the old sequence number and restores its output and route against the now-empty amount.\nChange to: Increment the request sequence before the invalid-amount early return, and invalidate the sequence in effect cleanup so obsolete responses cannot update the quote.\nWhy: Estimated output, rate and minimum received must describe the amount currently entered, including during loading and empty states.","line":54,"path":"src/pages/Swap.tsx","reproduction":"At 390×844, open #/swap?from=SOL&to=USDC-SOL, enter 0.1 SOL, and delay its Jupiter response after the 500ms debounce. Clear You pay, then release the original real quote response. Observed input=\"\", output=\"7.097129\", with Route, Rate and Minimum received still rendered. Expected empty output and no quote details. Reproduced using a captured real Jupiter response, delayed only for deterministic network ordering; no wallet or signature.","severity":"medium","snippet":"    if (!amt || amt <= 0n) { setQState(\"idle\"); return; }\n    const n = ++seq.current;","title":"bug: clearing the swap amount can resurrect an obsolete quote"},{"citation":"resolved","description":"Now: As soon as a job is completed, the polling interval is cleared before getResult succeeds. A failed result request is swallowed, leaving a completed card with no deliverables, no error and no retry.\nChange to: Stop polling only after the result loads successfully; on a result failure keep retrying and show \"Deliverables could not load. Retrying…\" in the existing card.\nWhy: Real Swarm deliverables and honest failure/retry states are explicit requirements. A temporary API failure must not strand a paid job.","line":173,"path":"src/components/Swarm.tsx","reproduction":"At 390×844, render a stored order for public completed job 1496b318-5803-462e-8195-4411eea4e085. Serve its actual completed job response, return HTTP 503 for the first /jobs/<id>/result request, then a valid result on later requests. Advance the browser clock 31 seconds. Observed resultRequests=1, Deliverables headings=0 and visible error alerts=0; the interval had already been cleared. Expected another result fetch and recovery, or an error with a retry action. This tests the read-only result state and sends no transaction.","severity":"medium","snippet":"        if (terminal(j.state)) { clearInterval(t); const r = await getResult(jobId); if (live) setRes(r); }","title":"bug: a transient result error permanently stops delivery polling"},{"citation":"resolved","description":"Now: getJson returns HTTP status/ok, but quote readers ignore them. A KyberSwap HTTP 403 HTML response becomes \"no liquidity for this pair and size,\" falsely diagnosing API access failure as a market condition.\nChange to: Handle non-success HTTP responses before interpreting quote bodies. Show \"KyberSwap quote service unavailable (HTTP 403). Try again later.\" for this case, and reserve no-route/liquidity messages for valid provider responses. Apply the same status handling to the existing quote readers.\nWhy: The brief requires unavailable APIs and unsupported routes to be reported clearly. The external 403 itself is not the finding; the incorrect local explanation is.","line":56,"path":"src/lib/swap.ts","reproduction":"Width 390×844, #/swap, ETH→IMD, amount 0.01 ETH. The public configured KyberSwap route endpoint returned HTTP 403 with an HTML body during review. Feed that captured body/status into the repository’s actual getQuote through a read-only Node import-hook fixture: it throws \"KyberSwap found no Ethereum route: no liquidity for this pair and size.\" An assertion requiring the message to identify API rejection/unavailability fails. Expected the HTTP/API-access explanation rather than an unverified claim about liquidity; no wallet or transaction is involved.","severity":"medium","snippet":"  if (!s) throw new NoRoute(`KyberSwap found no Ethereum route: ${j?.message ?? \"no liquidity for this pair and size\"}.`);","title":"bug: quote API rejection is presented as a liquidity failure"}],"hash":"f714c611a94d4aae6f62d7841ec88eff5492e9bbe391e6cf1804256af62ce7b6","nodeId":"cc7a18e0-2421-4bb1-81f9-2a66eaccb14a","outcome":"completed","summary":"| Area | Count / result |\n|---|---|\n| Requirements | 102 checked: 84 met, 4 missing, 1 faked, 12 need requester, 1 after review |\n| Broken features | 9, plus 1 accessibility defect |\n| First screen at 390px | Product and Create & launch action visible |\n| taste@1 | 16/16 passed |\n| Copy | 0 editorial findings |\n| Share card | Present; image and metadata verified |\n\nRecorded **10 findings: 4 high, 6 medium** in [.imd-findings.json](/home/imd/.identitymd/work/29b1df0b-843b-4e71-a669-543cd48a4133/cc7a18e0-2421-4bb1-81f9-2a66eaccb14a/.imd-findings.json). Website source is unchanged. Every finding includes an exact source citation, proposed correction, reproduction and measured evidence.\n\nThe four high findings are:\n\n- **bug:** Cross-chain execution accepts a replacement quote below the minimum the visitor reviewed.\n- **bug:** Worker assignments ignore the actual Swarm API’s `nodes` response.\n- **bug:** Jobs started before token creation disappear from that token’s Studio.\n- **fidelity:** “Live activity” and bonding-curve figures never refresh.\n\nThe six medium findings cover the broken hero Build button, escaping modal focus, conflicting slippage values, obsolete quotes reappearing, abandoned deliverable retries, and API rejection incorrectly described as insufficient liquidity.\n\n“Met” below means implementation and relevant UI/source checks passed, subject to the recorded defects. No launch, payment or swap was signed. Jupiter and LI.FI returned real quotes; KyberSwap returned HTTP 403. Chromium and WebKit visitor flows were exercised; live API access in WebKit remains unverified after a sandbox block.\n\nIMD Launchpad combines a Solana token launcher and Swarm checkout, carried visually by lime actions on quiet dark surfaces.\n\nEvidence paths below are relative to `src/` unless specified.\n\n| # | Requirement | Status | Evidence |\n|---|---|---|---|\n| 1 | “Upgrade this exact website”; no duplicate | after review | Publish the single App/export to the supplied URL. |\n| 2 | “Preserve its design, branding” | met | `base.css` exactly matches existing live CSS; branding retained. |\n| 3 | Preserve existing features | met | `App.tsx` retains original page routes. |\n| 4 | Complete SWAP page | met | `pages/Swap.tsx`, `#/swap`. |\n| 5 | IMD on Ethereum | met | `lib/swap.ts` token registry. |\n| 6 | ETH on Ethereum | met | Token registry and selectors. |\n| 7 | SOL on Solana | met | Token registry and selectors. |\n| 8 | USDC on Ethereum and Solana | met | Both assets in token registry. |\n| 9 | USDT on Ethereum and Solana | met | Both assets in token registry. |\n| 10 | PIMD once deployed | needs requester | Approved mint/liquidity; `config.ts` leaves mint empty. |\n| 11 | Swap between supported assets | met | `getQuote` / `executeSwap`; signing untested. |\n| 12 | Ethereum–Solana cross-chain swaps | met | Real SOL→IMD and USDC cross-chain quotes. |\n| 13 | Jupiter integration | met | `jupQuote`; real SOL→USDC quote. |\n| 14 | 0x or equivalent on Ethereum | met | [KyberSwap API](https://api-docs.kyberswap.com/aggregator-api.html) integration; live request returned 403. |\n| 15 | Reputable cross-chain provider | met | LI.FI integration and real preview routes. |\n| 16 | MetaMask, Rabby, Phantom, Solflare | met | `wallet/WalletSheet.tsx`, `eth.ts`, `solana.tsx`; signing untested. |\n| 17 | Token balances | met | `fetchBalances`; balance fields. |\n| 18 | Prices | met | LI.FI token API; Assets panel. |\n| 19 | Exchange rates | met | Swap Rate field. |\n| 20 | Fees | met | Provider fee estimates displayed. |\n| 21 | Slippage controls | met | Presets/custom input; display defect recorded. |\n| 22 | Estimated output | met | You receive field; stale-response defect recorded. |\n| 23 | Routes and network | met | Swap Route/Network fields. |\n| 24 | Transaction status and explorer links | met | `components/Flow.tsx`, transaction records. |\n| 25 | Verified token addresses | met | Registry; IMD addresses match supplied existing site. |\n| 26 | Real liquidity and quotes | met |","treeHash":null,"usage":{"cachedInputTokens":10196864,"cost":{"source":"estimated","usdMicros":3023269},"inputTokens":155203,"model":"gpt-6.1-sol","outputTokens":67349,"runtime":"codex","turns":11,"wallClockMs":2096922}}],"verification":[{"checks":[],"detail":"paths and tree verified; no suite was run for this kind of work","evaluation":"structural","profile":"none","status":"accepted","submissionHash":"37909e26e4561f20e6e47d807c485ae9d35251e78ae6cbd6fc8f8073ddb32192","verifiedTreeHash":"5420f5aa7d9cca9af0462b12e75a5dcf626c05f0","verifierVersion":"0.1.0+a490e3c0"},{"checks":[],"detail":"paths and tree verified; no suite was run for this kind of work","evaluation":"structural","profile":"none","status":"accepted","submissionHash":"9e82fdf3929a9d7b25921fb82aae388b8e4dc7905db562d8d2cf1df31ff31c19","verifiedTreeHash":"1846f3e3b5a5584ceb3580410fb345ef3036b1b1","verifierVersion":"0.1.0+a490e3c0"}]}