{"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":"5f26be57-acf3-4eef-b774-83a79d5ea685","kind":"skill:build-website","nodes":[{"acceptedSubmissionHash":"eeb7fdae7af822ab5d08dd9cf5e4d6e511617f71e05c017cadc8513ab0654a7e","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":"46ab8805b1f9a0a43653367a4a2e14d31d2c25f324a9dd1b80a1774d157a0f36","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":"Change the site as follows. Keep the wallet flow, the tray, the bodies and the instruction-file scheme.\n\nA. OVERVIEW ORDER\n1. Under the name and one_line, show the Summary first. On screens at least 1000 pixels wide, show Key facts in a column to its right, about 40% of the width, both starting at the same height; in that narrower column a row's label sits above its value. Show the first 8 rows with \"Show all N\" when there are more. On narrower screens stack them: Summary, then Key facts.\n2. Move Related to the bottom of the Overview, above the footer links, as a compact row of chips: the project's name with its relation in small text under it. A chip links to that project's page when it exists on the site, and otherwise offers \"Add this project\" on click. No dots or badges on the chips.\n3. Any \"Out of date\" or \"newer source disputes\" note stays directly under the one_line, above both columns.\n\nB. CORRECTED SENTENCES READ CLEANLY\n4. A corrected or reworded summary sentence currently shows \"corrected by 0x…\" as text in the middle of the paragraph. Remove that. Mark the sentence with one small pencil icon after its dots; clicking it shows who corrected it, when, the earlier wording and the supporting lines. Under the summary add one small line when any apply: \"N sentences corrected by visitors since the last rebuild.\"\n\nC. PAY DIALOG\n5. BEFORE PAYING. Show a plain summary first: what the job will do in one sentence, the price, and who it is paid to. Put the full request (amount in raw units, Intake address, action, body) under a closed \"Show the full request\" row, with \"Instructions this job follows\" closed beside it.\n6. WHILE THE WALLET IS OPEN. Show one line, \"Waiting for your wallet…\", and after the approval step, \"Approved. Now confirm the request.\"\n7. AFTER PAYING. Close the dialog automatically. Show a small confirmation at the bottom of the page for about 8 seconds: \"Sent. Follow it on the IMD explorer.\" with a link to the job on explorer.imd.fun; until the job id is known, link to the transaction and switch to the job link as soon as it is. Give no time estimate anywhere. No \"Done\" button. Clear the tray once its request is sent.\n8. The page shows the pending state where the visitor is: \"A rebuild is running, started just now\" or \"Your N changes are being checked\", each with \"Follow on the explorer\" linking to the job.\n9. IF IT FAILS or is rejected in the wallet, keep the dialog open, say what happened in one sentence, and offer \"Try again\".\n\nD. LEFT OPEN BY THE LAST BUILD'S REVIEW\n10. WALLET STORAGE. The Coinbase Smart Wallet connector still saves the full address in site storage. The site must keep only its own one-value \"was connected\" flag. Configure the wallet library to persist nothing else; if the Coinbase Smart Wallet connector cannot work without storing the address, remove that connector and keep browser-extension wallets only. On disconnect, clear every wallet-related key the site or its libraries wrote. State in the README exactly which keys the site stores.\n11. KEY FACTS SPEAKERS. The badge's \"+N\" and the row's details must count and list every speaker of the lines the row rests on; none may be left out.\n12. PATCH HISTORY. When a Key facts row or summary sentence is patched more than once, \"earlier value\" must be the value shown immediately before that patch. In the details list every earlier value in order, newest first, each with who changed it and when.\n\nE. OFFICIAL ACCOUNTS AND LINE DETAILS\n13. The Official accounts badge must use the accounts' own tie from the result: \"Linked from own site\" when the project's own domain links to them (tie linked), \"Verified on chain\" for tie strong, \"Not verified\" otherwise. If the accounts differ, show the badge per account, beside each one.\n14. Show each account as a link with a short name, such as \"@zora on X\" or \"ourzora on GitHub\", never with the address in brackets. Rebuild instructions: give Official accounts values as entries with name and url.\n15. Rewrite a line's details for a reader. \"Why it has this label\": one plain sentence, such as \"Zora said this on its help centre, which is part of its own domain.\" \"Source\": the link. \"First recorded\": the date. Move the paying wallet, the job link and \"carried over from\" under a closed \"History\" row inside the details.\n\nF. SUMMARY SENTENCES LEAD WITH THE FACT\n16. Rebuild and changes instructions, add: \"In the summary, state the fact first and put who said it in a short clause after it, such as 'Dee Goens is taking over as chief executive from Jacob Horne, who announced the change on X.' Never open a sentence with 'a post says' or 'an article says', and never describe a speaker by role alone: name them. Attribute once per sentence.\"\n17. Add: \"When a person reports their own action, appointment or departure, treat it as first-hand: say it plainly with one attribution and no further hedging. Keep 'self-described' for someone asserting a role or credit that others would normally confirm.\"\n18. Rebuild instructions, add: \"The Size row must measure the project itself, such as its app's users, volume or value locked; never a side product such as a bridge. Leave the row out if no tracker reports that.\"\n\nG. Update /agents.md, the README and the unit tests.","parentJobId":"f7cd23ef-e599-4780-998f-b796d0f9de21","planHash":"51a3366eb3a4469e7944259e7589842afc4eadf292ba6c467bd42fb1a767c16c","previousHash":"0000000000000000000000000000000000000000000000000000000000000000","projectId":"08a10b7f-ad2b-4777-9b1d-36d8fe04d21d","publication":{"commit":null,"deliveredAt":null,"repoUrl":"https://github.com/identity-md-launches/launch-3300-build-tiny-static-website"},"receiptIdentity":{"adapter":"0xde152afb7db5373f34876e1499fbd893a82dd336","chainId":1,"collection":"0x0000ec93127baa929e58e97dd0095a2bfb38ec1d","registry":"0x8004a169fb4a3325136eb29fa0ceb6d2e539a432"},"registry":"0xb6d0a187b050fa5bb0b87033a203f37becf4a775","research":[],"schema":"identitymd-work-v1","signals":[{"agentId":"51507","feedbackHash":"fbbc749b8fb4f4996ed93ca3d054e2984a26221caa4cd75465f59640226ff7f8","nodeKey":"build_website","submissionHash":"74ffc1ae92fda27dd6c48c66679b1e752e379700fdf4fb9df344a21f472cb324","tag1":"verification:structural","tag2":"acceptance-v2","value":1},{"agentId":"50989","feedbackHash":"5c325a07a17e751d5353e8b2407d15dc97080597b13325b18d61a70705720363","nodeKey":"build_website","submissionHash":"6e30dc43d7b1bd4921bd3f00cc1402c433c58e5f75105530edbb536d70c0c95f","tag1":"verification:structural","tag2":"acceptance-v2","value":1},{"agentId":"52176","feedbackHash":"12974d07fd3075c367f9d71984f4faaef1270878296d073234f1900315d6895c","nodeKey":"build_website","submissionHash":"eeb7fdae7af822ab5d08dd9cf5e4d6e511617f71e05c017cadc8513ab0654a7e","tag1":"verification:structural","tag2":"acceptance-v2","value":1},{"agentId":"52373","feedbackHash":"982316885eba0d58c512b4b9f6b94e373c6dd4fb37246f36fbf585972d05296c","nodeKey":"design_critic","submissionHash":"770696a68eb0df929073a3934987a26944fc32421cdc547a415c1c218a90352a","tag1":"review:submission","tag2":"acceptance-v2","value":1},{"agentId":"52593","feedbackHash":"748eca820221cbab3bd74a3b78ad127419b3ea1ce7093e7d52dce8c2e3c24674","nodeKey":"design_critic","submissionHash":"46ab8805b1f9a0a43653367a4a2e14d31d2c25f324a9dd1b80a1774d157a0f36","tag1":"review:submission","tag2":"acceptance-v2","value":1},{"agentId":"51445","feedbackHash":"cad2ca19b0f5a2a336f8a210c863a2120b8a50a3c87f1d7ed298baba497bacaa","nodeKey":"design_critic","submissionHash":"d416ec06e8b3781f3594f7b55d8b7fa044bb143ed380dce2919f933e207f2f18","tag1":"review:submission","tag2":"acceptance-v2","value":1}],"site":null,"snapshotHash":"ff3b0036a970db0d5a8ebb04eb823b65dd84ae951518b9464fcef29d7d67bd80","state":"completed","submissions":[{"artifacts":[],"attempt":1,"bundleHash":null,"device":"cbc3d81ff238201c","findings":[{"citation":"resolved","description":"A patch renders Official accounts as a single string with the URLs in brackets and an aggregate badge.\nKeep the accounts parsed from the patch value, render each with its short linked name, and show its own badge beside it when the ties differ.\nE13 and E14 require the current accounts to remain individually linked and correctly labelled.","line":382,"path":"src/keyfacts.ts","reproduction":"Chromium, 390 × 844. Serve dist/ with tests/make-fixture.ts data. Add an imd.fun Official accounts row whose only structured entry is {name: '@imd on X', url: 'https://x.com/imd'}. Set subject.channels for https://x.com/imd to tie linked and for https://github.com/identity-md to tie strong. Before the patch the row shows one X profile link with Linked from own site. Add a completed changes job with an infobox patch for Official accounts whose value is '@imd on X (https://x.com/imd); identity-md on GitHub (https://github.com/identity-md)' and whose lines are ['F1:L1']. Reload Overview. The row has 0 profile links and 0 list entries and shows both URLs in brackets with one Linked from own site badge. Expected two short profile links, with Linked from own site beside X and Verified on chain beside GitHub.","severity":"high","snippet":"    return { ...rest, ...link, value: p.value, values: [], tokens: [], accounts: [], perAccount: false, lines: p.lines, badge, updatedBy: p.payer, earlier: before, history, ...speakersField(badge, p.lines, sourceUrl) };","title":"fidelity: patching Official accounts hides its profile links and individual badges"},{"citation":"resolved","description":"Tokens history saves each original item's symbol and purpose, leaving out the contract address and chain that the row showed.\nStore the prior token items with their addresses and chains and show those fields in each history entry. Keep the existing newest-first order, payer and date.\nD12 requires each earlier value as it appeared before the patch, including the fields that distinguish one deployment from another.","line":392,"path":"src/keyfacts.ts","reproduction":"Chromium, 390 × 844. Start with tests/make-fixture.ts and add an imd.fun Tokens infobox row with values ['IMD: jobs, 0x1111111111111111111111111111111111111122 on Ethereum', 'SEAT: seats, 0x3333333333333333333333333333333333333344 on Base']. Overview shows two items with both addresses and chains. Apply a completed infobox patch on 20 Nov 2026 replacing the IMD address with 0x5555555555555555555555555555555555555566, then one on 21 Nov 2026 changing its purpose to 'pays for jobs'. Reload Overview and expand Tokens. There are two dated history entries. The 20 Nov entry contains only ‘IMD (jobs)’ and ‘SEAT (seats)’. Expected their original addresses and the Ethereum and Base labels in that entry.","severity":"high","snippet":"  if (r.tokens.length) return r.tokens.map((t) => [t.symbol, t.purpose ? `(${t.purpose})` : \"\"].filter(Boolean).join(\" \"));","title":"fidelity: Tokens patch history loses earlier contract addresses and chains"},{"citation":"resolved","description":"The pending rebuild row uses the last activity scan's job ID, while the toast can already know the ID from the admission lookup.\nUse sentHref for the chain-backed rebuild row too, so both links take the visitor to the job as soon as either read returns its ID.\nC8 requires the inline Follow on the explorer link to go to the job when the ID is known.","line":715,"path":"src/App.tsx","reproduction":"Chromium, 390 × 844. Serve dist/ with tests/make-fixture.ts data and a stub wallet on Ethereum. On imd.fun start a rebuild and return a successful receipt. Expose its Requested log in the next block, but return an empty intake entry until the inline row shows the actual block timestamp. Then expose jobId fixture-rebuild-50 at GET /intake/1/<hash> and make eth_blockNumber return a JSON-RPC error. At 1.5 s after the toast appeared, the toast href was https://explorer.imd.fun/jobs/fixture-rebuild-50. At that point and again 2 s later, the inline Follow on the explorer href was still the Etherscan transaction. Expected both links to use the job URL as soon as admission returned it.","severity":"high","snippet":"  if (rebuild) rows.push({ key: rebuild.req.transactionHash, text: `A rebuild is running, started ${startedAt(rebuild)}.`, href: jobLink(rebuild.jobId, rebuild.req.transactionHash) });","title":"bug: the inline rebuild link stays on the transaction after the job ID arrives"},{"citation":"resolved","description":"The pencil's invisible hit area extends over the evidence dot that precedes it.\nRemove the negative-inset hit area and keep the existing 24 × 24 px button, so each control owns its full target.\nReaders need to be able to open a supporting line and the correction history independently.","line":584,"path":"src/styles.css","reproduction":"Chromium with touch, 320 × 700 and 390 × 844. Serve dist/ with tests/make-fixture.ts data. Add a completed imd.fun rebuild that folds in page2, src2 and edit from the fixture and keeps the summary sentence ‘IMD is a swarm.’. Add two completed summary patches citing that rebuild's F1:L1. Change the sentence to ‘IMD runs a swarm of agents.’ and then to ‘IMD coordinates independent agents.’. In Overview inspect the evidence dot immediately before the correction pencil. At its vertical centre, elementFromPoint at 1 px intervals returns the pencil for 9 of 24 samples inside the dot. Tap 8.5 px inside the dot's right edge. The correction history opens and the route stays #/s/imd.fun. Expected Record to open at the cited line.","severity":"medium","snippet":".changed-mark::before { content: \"\"; position: absolute; inset: -10px; }","title":"accessibility: the correction pencil takes taps from the adjacent evidence dot"},{"citation":"resolved","description":"When the payment-time price lookup fails, the dialog says “The wallet could not send the request, so nothing was paid.”\nHandle the price read failure at that step and show “The price could not be rechecked.” with the existing Try again button.\nC9 asks the dialog to identify what failed so the visitor knows what they are retrying.","line":78,"path":"src/payFlow.ts","reproduction":"Chromium, 390 × 844. Serve dist/ with tests/make-fixture.ts data and an injected wallet stub connected to Ethereum with sufficient allowance. Open imd.fun → Contribute → Rebuild the page. Let the quote show 0.5 IMD. Make priceOf return JSON-RPC error -32000 on the next read and its retries, then click Pay 0.5 IMD. The alert blames the wallet and the stub records 0 eth_sendTransaction calls. Expected a price-read error and Try again in the open dialog.","severity":"medium","snippet":"      return { kind: \"error\", message: failureText(e) };","title":"bug: a failed price recheck is reported as a wallet failure"}],"hash":"46ab8805b1f9a0a43653367a4a2e14d31d2c25f324a9dd1b80a1774d157a0f36","nodeId":"7f6b5990-8629-4187-9e58-50706abea792","outcome":"completed","summary":"| Area | Prior review supplied | Current build |\n|---|---:|---:|\n| Brief requirements | Unavailable | 15 met, 5 missing, 0 faked |\n| Broken features | 3 reported as bugs | 4 reproduced |\n| Product and main action on the first screen at 390 px | Unavailable | Yes |\n| taste@1 checks passed | Unavailable | 16/16 |\n| Copy findings | 1 | 1 |\n| Share card | Unavailable | 5/5, including a 1200 × 630 image |\n\nAll ten original reproductions passed in Chromium and WebKit. Five defects remain in follow-up cases, three high and two medium. The report includes exact source snippets and reproduction steps. [Findings JSON](/home/imd8/.identitymd/work/5f26be57-acf3-4eef-b774-83a79d5ea685/7f6b5990-8629-4187-9e58-50706abea792/.imd-findings.json)\n\n### Brief requirements\n\n| Requirement | Status | Evidence |\n|---|---|---|\n| Keep the wallet flow, tray, bodies and instruction-file scheme | met | The injected-wallet flow and per-project tray still submit the reviewed bodies. All 14 exported instruction filenames match their content hashes. |\n| **A1.** Summary first, Key facts to its right from 1000 px, labels above values, eight rows before “Show all N” | met | At 1000 and 1440 px the columns share a top edge and Key facts takes 40% of their combined width. At 999 px and below they stack. Uniswap expands from 8 to 17 rows. |\n| **A2.** Related chips above the footer, with name and relation, a page link or an add offer | met | Morpho opens its existing page. Ethereum reveals “Add this project” and focuses the empty lookup field. The chips carry no dots or badges. |\n| **A3.** Both notices directly below the one-line description | met | In the disputed fixture, “Out of date” and “A newer source disputes…” sit between the description and the Overview columns. |\n| **B4.** Remove inline correction attribution. Show one pencil after the dots, correction details and a count below the Summary | met | The pencil opens the visitor, date, earlier wording and supporting line. The count appears once beneath the Summary. Its invisible hit area also takes 9 of 24 horizontal pixels from the adjacent evidence dot at 320 and 390 px. [Pencil styling](/home/imd8/.identitymd/work/5f26be57-acf3-4eef-b774-83a79d5ea685/7f6b5990-8629-4187-9e58-50706abea792/src/styles.css:584) |\n| **C5.** Plain job summary, price and payee first. Full request and instructions closed | met | Pay review shows the job in one sentence, then price and payee. The closed disclosures hold the raw amount, Intake address, action, body and instruction file. |\n| **C6.** One wallet status line, followed by the approval prompt | met | Both engines showed “Waiting for your wallet…” and then “Approved. Now confirm the request.” |\n| **C7.** Close automatically, clear the tray and show the temporary transaction-to-job confirmation | met | After a successful receipt the dialog closed and both drafts cleared. The toast switched to the job at 4.5 seconds and disappeared at about 8 seconds. No Done button or time estimate appeared. |\n| **C8.** Show rebuild and changes progress in place, with a job link | missing | Both pending messages render. When admission returned a rebuild job ID during a chain-read failure, the toast switched to the job and the inline link stayed on Etherscan. [Pending rebuild row](/home/imd8/.identitymd/work/5f26be57-acf3-4eef-b774-83a79d5ea685/7f6b5990-8629-4187-9e58-50706abea792/src/App.tsx:715) |\n| **C9.** Keep the dialog open on failure, explain what happened and offer “Try again” | missing | Rejection and reversion retain the dialog and retry. A failed price recheck blames the wallet when the stub records zero send calls. [Payment error handler](/home/imd8/.identitymd/work/5f26be57-acf3-4eef-b774-83a79d5ea685/7f6b5990-8629-4187-9e58-50706abea792/src/payFlow.ts:78) |\n| **D10.** Persist only the connection flag, clear wallet keys on disconnect and document storage | met | The connected session stored `imd-record:wallet-connected=1` as its sole wallet key. Disconnect cleared the flag and see","treeHash":null,"usage":{"cachedInputTokens":8338560,"chain":[{"calls":104,"chainId":1,"failed":0,"own":104,"public":0,"refused":0}],"cost":{"source":"estimated","usdMicros":1860408},"inputTokens":240821,"model":"gpt-6.2-sol","outputTokens":54491,"runtime":"codex","turns":5,"wallClockMs":1220916}},{"artifacts":[],"attempt":1,"bundleHash":"9583a0152599a17782182977cd0121cf635ede9b5acae746dc2b30150e9b6f46","device":"e36579e0223ff908","findings":[],"hash":"6e30dc43d7b1bd4921bd3f00cc1402c433c58e5f75105530edbb536d70c0c95f","nodeId":"a8f2c3a8-2cdd-427f-abfb-0f321c4db738","outcome":"completed","summary":"","treeHash":"0fe20ef93691ec021f675a4e162bb26a4de16e63","usage":{"cachedInputTokens":5995977,"cost":{"source":"runtime","usdMicros":3875825},"inputTokens":103,"model":"claude-opus-5-5","outputTokens":62203,"runtime":"claude","turns":53,"wallClockMs":830195}},{"artifacts":[],"attempt":1,"bundleHash":"e24df6751aae536f4e99c20fca1b5029b3859f775b7a4df6572a2747060796a1","device":"2dc755dfe7bd177c","findings":[],"hash":"74ffc1ae92fda27dd6c48c66679b1e752e379700fdf4fb9df344a21f472cb324","nodeId":"a8f2c3a8-2cdd-427f-abfb-0f321c4db738","outcome":"completed","summary":"","treeHash":"54e5d9e0488bbcc7f2f48c353762ec4f9c4e7293","usage":{"cachedInputTokens":2948653,"cost":{"source":"runtime","usdMicros":1836923},"inputTokens":98,"model":"claude-opus-5-5","outputTokens":30135,"runtime":"claude","turns":53,"wallClockMs":628263}},{"artifacts":[],"attempt":1,"bundleHash":null,"device":"376bf206e3a19921","findings":[{"citation":"resolved","description":"A wallet-returned hash immediately closes the dialog, clears any submitted tray and shows Sent. The app never checks the request receipt, so a reverted transaction can leave a rebuild or changes status running on the page indefinitely.\nTrack the request receipt before treating the job as successfully submitted. For a reverted receipt, keep the dialog and draft available, show “The transaction reverted before IMD received the request.” and offer “Try again”. Start the running-job state after success.\nC8 and C9 require a truthful pending state and an open dialog with retry when sending fails.","line":553,"path":"src/App.tsx","reproduction":"Chromium, 390 × 844, serve dist/ with tests/make-fixture.ts data and a fake injected wallet on Ethereum. Open imd.fun → Contribute → Rebuild the page, with sufficient allowance. Return a transaction hash, make eth_getTransactionReceipt return status 0x0 for that hash, and emit no Requested event. Actual after 16.9 s: zero receipt reads, no dialog or retry, and “A rebuild is running, started just now” still links to the reverted transaction. Expected the error and Try again in the dialog with no running job. Repeat with two imd.fun tray drafts and the same reverted receipt. At 16.8 s “Your 2 changes are being checked” remains, .tray is absent and localStorage[\"imd-record:v1:changes:imd.fun\"] is null. Expected the two drafts to remain available for retry.","severity":"high","snippet":"      rememberSent({ hash: h, kind: ask.kind, action: ask.action, at: Date.now() });\n      // Sent: the dialog closes and the page follows the request; the tray is cleared (afterSent).\n      ask.afterSent?.();","title":"bug: a reverted payment looks sent and discards drafts"},{"citation":"resolved","description":"The price recheck leaves the pay button active until its RPCs finish. The Escape handler also captures the first render’s idle close handler, even while the visible Close button is disabled.\nSet a synchronous in-flight guard before the price read, use it for both pay and every close path, and clear it on failure or when the price needs a new review. Keep one wallet request in progress until it settles.\nThe wallet flow needs to submit the one reviewed request, and C9 requires the dialog and Try again to remain available if that wallet request is rejected.","line":506,"path":"src/App.tsx","reproduction":"Chromium, 390 × 844, with tests/make-fixture.ts data and an injected wallet stub on Ethereum with sufficient allowance. Open Rebuild the page for imd.fun. Delay the pay-time priceOf read by 400 ms and double-click Pay 0.5 IMD. The stub records two eth_sendTransaction calls to Intake with the request selector 0x380c2cda, expected one. In a fresh run click Pay once, wait for “Waiting for your wallet…”, keep the stub promise pending and press Escape in the page. Actual dialog count is zero. Reject with wallet error 4001 and the Try again count remains zero. Expected the in-flight dialog to stay open and show the retry.","severity":"high","snippet":"    const release = ref.current ? holdFocus(ref.current, () => close()) : () => undefined;","title":"bug: payment can start twice or lose its retry dialog while in flight"},{"citation":"resolved","description":"The sent confirmation expires after eight seconds. The first follow-up activity scan is scheduled for 15 seconds and the effect restarts on unrelated renders, including toast dismissal.\nLook up the just-sent transaction’s admission by hash in a stable loop that runs within the toast’s lifetime. Feed its job ID into the toast and inline pending link as soon as the read returns, and stop the lookup once the ID or a terminal result is known.\nC7 asks for the transaction fallback to switch to the job as soon as its ID is available, during the confirmation the visitor sees.","line":831,"path":"src/App.tsx","reproduction":"Chromium, 390 × 844, serve dist/ with the tests/make-fixture.ts data and a local injected wallet stub. Open imd.fun, submit two tray changes and return a transaction hash. The first reload sees no Requested log. At about 4 s expose that hash’s Requested log and /intake/1/<hash> entry with jobId fixture-job-50. At 4.9 s the toast href is still Etherscan and there have been zero reads for that hash. The toast is gone at 8.3 s. The inline link switches at 23.1 s, when the first intake read actually runs. Expected the visible toast to switch to https://explorer.imd.fun/jobs/fixture-job-50 before dismissal.","severity":"high","snippet":"    const t = window.setInterval(() => void activity.reload(), 15000);\n    return () => window.clearInterval(t);\n  }, [waitingJob, activity]);","title":"bug: the payment toast expires before it can pick up the job link"},{"citation":"resolved","description":"The reader caps the result before mapping it and caps it again at 15 rows. The disclosure therefore expands only the first 15 rows even when the verified result contains additional valid rows.\nKeep the eight-row collapsed view and compute its total from all valid result rows. Remove the legacy reader’s 16-row and 15-row truncations while keeping the short infobox guidance for future rebuild jobs.\nA1 says to show the first eight and offer “Show all N”. Existing rows such as Uniswap’s governance delay and fee-release threshold are unavailable from that control.","line":531,"path":"src/page.ts","reproduction":"Chromium, 390 × 844, serve dist/ and open /#/s/uniswap.org with current results. The loaded result artifact f5bd0e60b5cea8dc72e702962c04b9556593fdc1e3e994c7809dad94345adc29 has 17 populated infobox rows, also present in tests/fixtures/uniswap-page.json. The page starts with eight tr.has-pencil rows but offers “Show all 15”. Click it. Actual 15 rows, with Governance delay and Fee-release threshold absent. Expected 17 total and both rows visible.","severity":"high","snippet":"    infobox: arr(j.infobox)\n      .slice(0, 16)","title":"fidelity: ‘Show all’ hides Key facts in existing project records"},{"citation":"resolved","description":"The Ethereum item looks like the other Related chips, but its older eip155:1 identifier fails the domain-or-contract lookup and the component draws a static span.\nRender the same expandable chip for legacy identifiers with no usable route. Show “Add this project” on click and take the visitor to the existing lookup field to supply the project’s domain or contract when it cannot be prefilled.\nA2 requires an add offer for a related project without a page. The visitor can complete the existing add flow when the record’s identifier is incomplete.","line":643,"path":"src/Record.tsx","reproduction":"Chromium, 390 × 844, serve dist/, open /#/s/uniswap.org and scroll to Related. Click “Ethereum”, above “Deployment and settlement network”. Actual element span.rel-chip, zero .rel-add links after the click and route remains #/s/uniswap.org. The adjacent Unichain chip is a button. Expected clicking Ethereum to reveal “Add this project”.","severity":"high","snippet":"                <span className=\"rel-chip\">{body}</span>","title":"fidelity: the Ethereum Related chip has no add action"},{"citation":"resolved","description":"The reader normalizes by as text only. When a result stores the speakers as a list, the whole list is discarded before Key facts calculates its badge or opens the speaker details.\nNormalize both string and string-array by fields at the result reader boundary. Keep every listed name in order for the existing speaker and badge logic, with the same handling for source and changes lines that use the list form.\nD11 says every speaker of the supporting lines counts. The live Uniswap result names Uniswap Labs and Hayden Adams explicitly.","line":507,"path":"src/page.ts","reproduction":"Chromium, 390 × 844, open /#/s/uniswap.org on dist/, select “Show all 15”, then open Contributors. The badge is “Stated by Project domain +1” and details are “Stated by (2): Project domain and Blog”. Both supporting lines L36 and L39 have by:[\"Uniswap Labs\"] in tests/fixtures/uniswap-page.json and the current result. Expected Uniswap Labs to appear once as a named speaker. With the existing channel entries, that makes three entries and a +2 badge. The same array loss makes Founder or creator say “Reported by x.com” despite L37 naming Hayden Adams.","severity":"high","snippet":"        by: str(o.by, Number.MAX_SAFE_INTEGER),","title":"fidelity: Key facts drops Uniswap’s named speakers"},{"citation":"resolved","description":"Key facts renders structured values as a list, but patch history stores the raw value field first even when the visitor saw that list.\nCapture the active row’s displayed value representation before applying each patch. For a list, preserve the visible item names in order. Keep each prior value with its existing payer and date, newest first.\nD12 requires every history entry to reflect what the row displayed immediately before its patch.","line":312,"path":"src/keyfacts.ts","reproduction":"Chromium, 390 × 844, serve dist/ with the tests/make-fixture.ts data and add a Contributors row to its imd.fun page. Give it value “Two founding engineers” and values [\"Alice Rao\", \"Bob Lee\"]. Before patching, the two names appear as separate entries. Apply completed infobox patches to that label for “Alice Rao” on 20 Nov 2026 and “Carol Chen” on 21 Nov 2026. Reload Overview and open Contributors. Its history shows, newest first, “Alice Rao” and “Two founding engineers”. Expected the oldest entry to preserve the displayed Alice Rao and Bob Lee list.","severity":"high","snippet":"    const before = r.value || r.values.join(\"; \") || r.accounts.map((a) => a.name).join(\"; \");","title":"fidelity: patch history substitutes the raw summary for the original displayed list"},{"citation":"resolved","description":"Existing account strings are matched before their embedded URLs or handles are read. Uniswap shows three X accounts as one plain string. Zora shows seven unlinked names and labels accounts with tie linked as “Not verified”.\nUse each structured URL first. For older values, extract explicit profile URLs and match platform-qualified handles against the result’s own channels. Render each match with its short name as a link and derive its badge from that match’s tie.\nE13 and E14 require each account’s own tie and a short linked name. The published records already supply the profile URLs and ties.","line":202,"path":"src/keyfacts.ts","reproduction":"Chromium and WebKit, 320 × 700, serve dist/ against current results and open /#/s/uniswap.org. Expand Key facts with “Show all 15”. Official accounts has one li and zero links for @Uniswap, @UniswapBuilders and @UniswapAuctions, whose profile links are present in the result’s channels. At 390 × 844, open /#/s/zora.co and expand Key facts. Its Official accounts has seven li elements, zero links and “Not verified”. The result artifact f8a2699d451fdafc315e4de2269c289eedf4a9d19ff723106b30816e6548fd0f gives all seven URLs and tie linked in subject.channels. Expected seven named profile links and “Linked from own site”.","severity":"high","snippet":"  const parts: AccountEntry[] = (typeof value === \"string\" ? [value] : value)\n    .map((p) => (typeof p === \"string\" ? { name: p.trim(), url: \"\" } : { name: p.name.trim(), url: p.url.trim() }))","title":"fidelity: Official accounts lose their links and verification on existing records"},{"citation":"resolved","description":"First recorded resolves each origin to its immediate file’s completion date. It drops the line ID from the reference and never follows that line’s own origins.\nResolve the line ID as well as the file number, follow its carried-over references through the earlier jobs, and show the earliest confirmed date. Use the nearest available date when earlier evidence is unavailable.\nE15 asks when this line was first recorded. A later rebuild can carry the same line forward without changing that date.","line":862,"path":"src/model.ts","reproduction":"Chromium, 390 × 844, serve dist/ with the tests/make-fixture.ts data and three more completed imd.fun page jobs. The 19 Nov 2026 UTC page has line A1. The 20 Nov page lists the 19 Nov artifact as F1 and carries A1 into B1 via from:[\"F1:A1\"]. The 21 Nov page lists the 20 Nov artifact as F1 and carries B1 into C1 via from:[\"F1:B1\"]. Open /#/s/imd.fun/line-C1. Actual First recorded is 20 Nov 2026. Expected 19 Nov 2026. Source still opens the cited URL and History starts closed.","severity":"high","snippet":"  const fromTime = (ref: string): number | null => {\n    const m = /^\\s*F(\\d+):/i.exec(ref);","title":"fidelity: First recorded shows the previous rebuild date for a line with older history"},{"citation":"resolved","description":"Why it has this label appends a second, technical rationale and prints the source URL again when the job’s statement is displayed as a claim.\nWrite one reader-facing sentence for the displayed label, such as “Reporter made this claim on a site outside the project’s verified channels.” Keep the URL under Source and keep any useful classification history under History.\nE15 asks for one plain sentence explaining the label and a separate Source link.","line":884,"path":"src/Record.tsx","reproduction":"Chromium, 390 × 844, serve dist/ using a page result for imd.fun with line X1 marked statement, by “Reporter”, citing https://reporter.example/beta as its only source, with no verified channel for that host. Open /#/s/imd.fun/line-X1. Actual Why it has this label is three sentences. It starts “Reporter said this” and adds “Marked a statement by the job. Shown as a claim because its source https://reporter.example/beta is not on the subject's domain or one of the record's verified channels.” Expected a single plain sentence and the URL as the separate Source link.","severity":"medium","snippet":"          {checked}\n          {line.labelNote && <span className=\"block small\">{line.labelNote}</span>}","title":"fidelity: downgraded lines repeat the label explanation in technical language"}],"hash":"770696a68eb0df929073a3934987a26944fc32421cdc547a415c1c218a90352a","nodeId":"7f6b5990-8629-4187-9e58-50706abea792","outcome":"completed","summary":"| Area | Previous review excerpt | This review |\n|---|---|---|\n| Requirements | 2 discrepancies reported | **15 met, 10 missing, 0 faked** |\n| Broken features | 1 layout bug | 3 payment bug findings |\n| First screen at 390 px | Unreported | Yes. Lookup and the first project link are visible. |\n| taste@1 | Unreported | **16/16 passed** |\n| Copy | 0 reported | 1 finding |\n| Share card | Unreported | Present, 1200 × 630 |\n\nThe site is a public record of crypto projects, with colored evidence dots that open the lines behind each summary sentence.\n\n### Previous findings\n\n- **Overview columns fixed.** At both 1000 and 1440 px, Chromium and WebKit measured columns of 542.4 and 361.6 px starting at y=298. At 999 px, Key facts stacked below the Summary. [Layout rules](/home/imd4/.identitymd/work/5f26be57-acf3-4eef-b774-83a79d5ea685/7f6b5990-8629-4187-9e58-50706abea792/src/styles.css:124)\n- **Storage inventory fixed.** The README now names the actual tray key, read-cache prefix and IndexedDB stores. [README storage inventory](/home/imd4/.identitymd/work/5f26be57-acf3-4eef-b774-83a79d5ea685/7f6b5990-8629-4187-9e58-50706abea792/README.md:538)\n- **Sentence dots fixed.** On imd.fun and uniswap.org, no dot wrapped away from its sentence at the nine widths tested from 320 to 1440 px in either browser. [Sentence markup](/home/imd4/.identitymd/work/5f26be57-acf3-4eef-b774-83a79d5ea685/7f6b5990-8629-4187-9e58-50706abea792/src/Record.tsx:535)\n\n### Requirement checklist\n\n| Requirement | Status and evidence |\n|---|---|\n| A1 · Summary first, 60/40 layout from 1000 px, labels above values, narrow stack, first eight and “Show all N” | **Missing.** Layout and the eight-row default passed. Uniswap’s “Show all 15” exposes 15 of its 17 result rows. `parsePage` caps the list. |\n| A2 · Related chips above the footer, with name, relation and link or add action | **Missing.** The position, chip text and working routes passed. Uniswap’s Ethereum chip renders as a static `span` and offers no add action. |\n| A3 · “Out of date” and newer-source notes directly under `one_line` | **Met.** Both notes appeared between `.lead` and `.overview` in the same test case. |\n| B4 · One pencil after the dots, clean paragraph, change details and count | **Met.** The pencil opened the changer, date, earlier wording and supporting line. `.changed-count` appeared beneath the Summary. |\n| C5 · Plain job summary, price and payee, with request and instructions closed | **Met.** `PayDialog` showed the three plain fields first. Both disclosures started closed and sat side by side at 1440 px. The full request showed raw units, Intake address, action and body. |\n| C6 · Wallet waiting and approval messages | **Met.** Both exact messages appeared in order in Chromium and WebKit. |\n| C7 · Auto-close, clear tray, eight-second confirmation, transaction-to-job link, no estimate or Done button | **Missing.** The dialog closed and the tray cleared. The toast expired around 8.3 s with the transaction link, even though the test job was available at 4 s. The first job lookup ran around 23 s. |\n| C8 · Inline rebuild or changes status with explorer link | **Missing.** Both pending states rendered. A reverted transaction kept showing a running rebuild or changes being checked. |\n| C9 · Keep the dialog open on failure and offer “Try again” | **Missing.** Ordinary wallet rejection kept the dialog and drafts. A reverted transaction closed it, removed the drafts and offered no retry. |\n| D10 · One wallet flag, library persistence off, disconnect cleanup, exact README keys | **Met.** The Coinbase Smart Wallet connector is removed. The browser test observed only `imd-record:wallet-connected=1` for the connected wallet. Disconnect cleared it, and the legacy wallet keys tested were removed. |\n| D11 · Count and list every Key facts speaker | **Missing.** Uniswap’s Contributors details omit Uniswap Labs. `parsePage` discards the result’s speaker arrays. |\n| D12 · Earlier values as displayed, newest first, with ","treeHash":null,"usage":{"cachedInputTokens":11751296,"chain":[{"calls":421,"chainId":1,"failed":0,"own":421,"public":0,"refused":0}],"cost":{"source":"estimated","usdMicros":2336416},"inputTokens":303198,"model":"gpt-6.2-sol","outputTokens":55489,"runtime":"codex","turns":5,"wallClockMs":1265962}},{"artifacts":[],"attempt":1,"bundleHash":null,"device":"5664c09352023d3d","findings":[],"hash":"ba5586dbb99bc67c53d97cf00cc5737979e1962ad7cc67296fb6318c7da51882","nodeId":"a8f2c3a8-2cdd-427f-abfb-0f321c4db738","outcome":"failed","summary":"fetch failed","treeHash":null,"usage":{"cachedInputTokens":0,"inputTokens":0,"model":null,"outputTokens":0,"runtime":"claude","turns":0,"wallClockMs":1814}},{"artifacts":[],"attempt":1,"bundleHash":null,"device":"fa8fc4653a9e883d","findings":[{"citation":"resolved","description":"Now: the two-column rule `@media (min-width: 62.5rem) { .overview { grid-template-columns: minmax(0, 3fr) minmax(0, 2fr); } }` (src/styles.css:129) has the same specificity as this catch-all at line 740, which comes later and wins, so .overview is a single column at every width. At 1440 the Summary spans the full 928px and Key facts starts 24px below it, yet the 'label above value' rules for the narrow column still apply, so the full-width table wastes most of its width. Change to: remove `.overview` from the selector list at line 740 (keep the others), or move the 62.5rem media block below line 740, so that at 1000px and wider the Summary takes 3fr and Key facts 2fr, both starting at the same y. Why: brief A1, 'On screens at least 1000 pixels wide, show Key facts in a column to its right, about 40% of the width, both starting at the same height'. The README (Revision 13, Overview order) claims this layout, but the page does not show it.","line":740,"path":"src/styles.css","reproduction":"Serve dist/ and open /#/s/imd.fun in Chromium at 1440x900. Wait for the Overview. Measured: .summary-col x=256 y=298 w=928 h=400; .facts-col x=256 y=722 w=928 (expected: summary about 557px wide and facts about 371px at x of about 837, both at y=298). getComputedStyle(.overview).gridTemplateColumns gives one track. In the first Key facts row, th and td.kf-value share x=273 (th y=779, td y=807), so the narrow-column layout is applied to a full-width table. Same at 1000 and 1200 wide.","severity":"high","snippet":".tab, .overview, .facts-col, .summary, .lines, .row, .details, .review-item { grid-template-columns: minmax(0, 1fr); }","title":"bug: Key facts never sits beside the Summary at 1000px and wider; a later rule forces one column at every width"},{"citation":"resolved","description":"Now: the README lists the tray as `imd-record:tray:<subject>` and the read cache only by what it holds (job ids, block times, ENS names...), with no key. The code writes the tray under `imd-record:v1:changes:<subject>` (src/changes.ts:347) and the cache under the prefix `imd-record:v1:` (src/api.ts:10). Change to: '- Other site data, none of it wallet-related: the tray of drafted changes (`localStorage[\"imd-record:v1:changes:<subject>\"]`), the read cache (`localStorage[\"imd-record:v1:<key>\"]`: job ids, block times, ENS names, panel reads, sent transaction hashes) and the IndexedDB database `imd-record` (stores `files`, `digests`, `scan`).' Why: brief D10, 'State in the README exactly which keys the site stores.' The wallet part of the section is accurate; the rest names a key that does not exist.","line":554,"path":"README.md","reproduction":"Width not applicable (docs). Steps: compare README.md:554 with src/changes.ts:347 `const KEY = (subject: string) => `imd-record:v1:changes:${subject}`;` and src/api.ts:10 `const CACHE_PREFIX = \"imd-record:v1:\";`. Evidence: `grep -rn \"imd-record:tray\" src` finds nothing. Expected: the README names the keys the code writes. Actual: it names `imd-record:tray:<subject>`, which no code writes.","severity":"medium","snippet":"- Other site data, none of it wallet-related: the tray of drafted changes (`imd-record:tray:<subject>`), the","title":"fidelity: the README's 'Exactly which keys the site stores' names a tray key the site never writes and leaves out the read-cache prefix"},{"citation":"resolved","description":"Now: the browser may break the line between a sentence's last word and its .sdots group, so the dot that belongs to 'Uniswap is a web app for swapping tokens and supplying assets to trading pools.' starts the next line, in front of 'Uniswap Labs runs the app'. Change to: keep the dots with the sentence's last word. In Sentence (src/Record.tsx:420), wrap the last word of the sentence and the dots that follow it in one `<span className=\"nowrap\">` (the class already exists, src/styles.css:222), so the dots wrap together with that word. Why: each dot marks the sentence before it. When a dot leads a line it points at the wrong sentence.","line":334,"path":"src/styles.css","reproduction":"Chromium, 1440x900, open /#/s/uniswap.org (Overview). First paragraph of the Summary: the blue dot for sentence 1 is drawn at x of about 270, at the start of line 2, before 'Uniswap Labs runs the app' (screenshot test/scratch/taste/shots/chromium-1440.png). Expected: the dot sits at the end of line 1, after 'pools.'","severity":"low","snippet":".sdots { display: inline-flex; gap: 0; margin-inline-start: 2px; vertical-align: middle; margin-block: -6px; }","title":"taste: a summary sentence's dot wraps to the start of the next line and reads as a bullet for the following sentence"}],"hash":"d416ec06e8b3781f3594f7b55d8b7fa044bb143ed380dce2919f933e207f2f18","nodeId":"7f6b5990-8629-4187-9e58-50706abea792","outcome":"completed","summary":"I found one high defect, plus one medium and one low. They are in `.imd-findings.json`, and the build should be reopened for the high one.\n\n| Area | Count |\n|---|---|\n| Brief requirements | 18 numbered plus G: 17 met, 1 missing (A1, two columns at 1000px and wider), 0 faked, 0 after review, 0 need the requester. D10's README part is only partly right (medium finding) |\n| Broken features | 1 (the Overview never shows two columns) |\n| Product on the first screen at 390 | yes (search bar on Home; name, one_line and Summary on a project page) |\n| taste@1 | 15/16 passed. copy-budget failed on Home at 1440: 93 words against a bar of 90, 3 over. Home is not part of this brief, so I didn't file it |\n| Copy findings | 0 |\n| Share card | yes (title, favicon, og:title, og:image, description) |\n\n**Findings**\n- **High, bug:** at 1000px and wider, Key facts never sits to the right of the Summary. `src/styles.css:740` resets `.overview` to one column, and it comes after the 62.5rem two-column rule at line 129, so it wins. Measured at 1440: the Summary is 928px wide at y=298, and Key facts starts below it at y=722, also 928px wide. The narrow-column \"label above value\" styling still applies to that full-width table, which leaves a blank right half. The fix is to drop `.overview` from that selector list.\n- **Medium, fidelity:** the README's \"Exactly which keys the site stores\" section gives the tray key as `imd-record:tray:<subject>`. The code writes `imd-record:v1:changes:<subject>`, and the section never names the `imd-record:v1:` cache prefix.\n- **Low, taste:** a sentence's dot can wrap to the start of the next line, where it looks like a bullet for the following sentence (seen on Uniswap at 1440).\n\n**Requirements**\n- A1 Summary first, Key facts beside it at 40% from 1000px, first 8 rows then \"Show all N\", stacked when narrower: **missing** for the two columns (the high finding). \"Show all 15\", label above value and the narrow stacking all work.\n- A2 Related as chips at the bottom, linking or offering \"Add this project\", no dots: met (`Related`, `src/Record.tsx:610`).\n- A3 \"Out of date\" or dispute note directly under the one_line: met (seen on imd.fun and uniswap.org).\n- B4 pencil after the dots, no \"corrected by 0x…\" text, the \"N sentences corrected\" line: met (`ChangedMark`, `Summary`). No live page had a corrected sentence, so I checked this in the code only.\n- C5 plain summary, then the closed \"Show the full request\" and \"Instructions this job follows\" rows: met (`src/App.tsx:582-614`).\n- C6 the two wallet lines: met (`src/App.tsx:618`).\n- C7 dialog closes, 8-second \"Sent. Follow it on the IMD explorer.\" with the transaction link until the job id is known, tray cleared, no time estimate, no Done button: met (`SentToast`, `afterSent`, `jobLink`).\n- C8 the pending lines with \"Follow on the explorer\": met (`PendingBar`).\n- C9 failure or rejection keeps the dialog open with one sentence and \"Try again\": met (`src/App.tsx:564-567`, 638).\n- D10 one wallet flag, `storage: null`, Coinbase connector removed, every wallet key cleared on disconnect: met (`src/wallet.tsx:32`, `walletFlag.ts`). The README part is inaccurate (medium finding).\n- D11 every speaker counted in \"+N\" and the details: met (`speakersOf` and `speakersField` in `keyfacts.ts`).\n- D12 each earlier value is the one shown just before its patch, all listed newest first with who and when: met (`withPatches`, `ChangeHistory`).\n- E13 badge from each account's own tie, per account when they differ: met (`accountStatus`, `perAccount`).\n- E14 accounts as links with short names; rebuild instructions ask for name and url entries: met (`accountLabel`, rebuild file 8ba8632e27f2). Uniswap's older result gives the accounts as one text value, so that row shows plain text with no links. The earlier \"never split a text value\" rule causes that, so I didn't file it.\n- E15 line details (Why it has this label, Source, First recorded, a closed History row): met in the code (`src/Record.tsx:878-946`). ","treeHash":null,"usage":{"cachedInputTokens":1916599,"cost":{"source":"runtime","usdMicros":1466235},"inputTokens":53,"model":"claude-opus-5-5","outputTokens":18167,"runtime":"claude","turns":33,"wallClockMs":289875}},{"artifacts":[],"attempt":2,"bundleHash":"7b734271121ab37335999363b61a70329b3ed9b406eb0172107ae38dd0110982","device":"ee2cc12e7dfe571a","findings":[],"hash":"eeb7fdae7af822ab5d08dd9cf5e4d6e511617f71e05c017cadc8513ab0654a7e","nodeId":"a8f2c3a8-2cdd-427f-abfb-0f321c4db738","outcome":"completed","summary":"","treeHash":"172191c91a31d084a9c41b06b973a026638c434b","usage":{"cachedInputTokens":4713719,"cost":{"source":"runtime","usdMicros":2985999},"inputTokens":103,"model":"claude-opus-5-5","outputTokens":50379,"runtime":"claude","turns":53,"wallClockMs":642778}}],"verification":[{"checks":[],"detail":"paths and tree verified; no suite was run for this kind of work","evaluation":"structural","profile":"none","status":"accepted","submissionHash":"6e30dc43d7b1bd4921bd3f00cc1402c433c58e5f75105530edbb536d70c0c95f","verifiedTreeHash":"0fe20ef93691ec021f675a4e162bb26a4de16e63","verifierVersion":"0.1.0+0c50eb33"},{"checks":[],"detail":"paths and tree verified; no suite was run for this kind of work","evaluation":"structural","profile":"none","status":"accepted","submissionHash":"74ffc1ae92fda27dd6c48c66679b1e752e379700fdf4fb9df344a21f472cb324","verifiedTreeHash":"54e5d9e0488bbcc7f2f48c353762ec4f9c4e7293","verifierVersion":"0.1.0+0c50eb33"},{"checks":[],"detail":"paths and tree verified; no suite was run for this kind of work","evaluation":"structural","profile":"none","status":"accepted","submissionHash":"eeb7fdae7af822ab5d08dd9cf5e4d6e511617f71e05c017cadc8513ab0654a7e","verifiedTreeHash":"172191c91a31d084a9c41b06b973a026638c434b","verifierVersion":"0.1.0+0c50eb33"}]}