{"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":"f7cd23ef-e599-4780-998f-b796d0f9de21","kind":"skill:build-website","nodes":[{"acceptedSubmissionHash":"dd7ea1b3758ef2eb209cede77b3383265378ae150e06b0f8f7d4306a31b0b291","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":"ffc462bc457c2117ef6902c50b12d6939059175d5b7b6fc102cc835aea79fa9d","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":"Fix the following. Keep everything else as it is.\n\nA. WALLET STAYS CONNECTED\n1. Since wallet code stopped loading on page load, a connected wallet is forgotten on every reload. When a visitor connects, remember that in the browser (one flag, no address). When they disconnect from the site's own menu, clear it.\n2. On page load, if the flag is set, load the wallet code in the background and reconnect silently, so the address chip appears without a click. If that fails, show Connect and clear the flag. While it is in progress, show the chip's outline in place of the Connect button so the header does not flicker.\n3. If the flag is not set, keep today's behaviour: no wallet code is loaded and no third party is contacted until Connect is pressed. Loading the wallet code must still make no third-party request; keep the Coinbase connector's telemetry off.\n\nB. NO SILENT CAP ON EDIT RESULTS\n4. In reading a changes or sources result the site keeps only the first 200 lines and the first 200 items (src/page.ts), so a link whose evidence is line 201 or later is lost and the disputed line shows no marker. Remove both caps: read every line and item, as page results are read.\n5. If a result file is too large to read safely, say so in its Activity row (\"This result is too large to show in full: N lines\"); never drop lines silently. Add a unit test: a changes result of 250 lines whose contradicting line is the last still marks its target.\n\nC. DO NOT TAKE PAYMENT FOR A JOB THAT CANNOT READ ITS INSTRUCTIONS\n6. Instruction files are served from one outside gateway (ipfs.filebase.io). Before opening any pay dialog for a rebuild or a set of changes, fetch the instruction file the objective names and check its sha256. If it cannot be fetched or does not match, do not open the dialog; show \"The instructions for this job cannot be reached right now, so it would stop without doing the work. Try again later.\"\n7. Put a second address for the same file in the objective, from another gateway that serves the same raw CID (the README notes gateway.pinata.cloud did), worded \"or, if that fails, at <URL2>\". Run the new objective through IMD's request check and keep the second address only if blockers is empty.\n\nD. SMALL DISPLAY FIXES\n8. A Key facts badge is one short line: name one speaker, the strongest, then \"+N\" for the rest, such as \"Stated by Documentation +1\". The full list is in the row's details.\n9. An old link such as /#/s/app.uniswap.org/overview should open the record and replace the address with the current one (/#/s/uniswap.org/overview).\n\n10. The Official accounts row must not show \"Own domain\" for accounts on other sites such as x.com. Rebuild instructions, add: \"A channel on another site that the project's own domain links to as its official account has tie linked.\" Show that tie as \"Linked from own site\"; lines published on such a channel count as statements. Show other off-domain accounts as \"Not verified\".\n\nE. AN EDIT REPAIRS WHAT IT DISPUTES\n11. Today a kept change marks other parts of the page as disputed and asks for a separate paid rebuild. Change that: the same job repairs them. Changes instructions, add: \"For every infobox row and summary sentence in affects, give a patch: the row's new value, or the sentence's new text, with the line ids it now rests on. Change only what the new evidence requires and keep the rest of the wording. If the evidence shows a part is out of date but not what replaced it, give no patch for it.\" JSON keys: add patches[{kind,target,value,lines[]}].\n12. The site applies each patch on top of the page shown: the Key facts row or summary sentence shows the new value with its normal badge, and its details say \"Updated by a change from <payer>\" with the earlier value. Record lines keep their Out of date or Contradicted markers.\n13. Show the banner \"A newer source disputes N parts of this page\" only for parts in affects that got no patch. A page whose changes are all patched is not \"out of date\" for that reason.\n14. The rebuild still folds everything in later; it treats patches as part of the changes result.\n\nF. Update /agents.md, the README and the unit tests.","parentJobId":"9c8709ea-f05f-4356-8798-0f199a1bd55f","planHash":"474b26166e3facb813b33fdddc0fb9d7c099f42af9a1a1403ed078ed6b225b8c","previousHash":"85c84c0d5d4b4cdec295d38764d27acab0c9a625ad2e56c82ae7917802ba1b47","projectId":"08a10b7f-ad2b-4777-9b1d-36d8fe04d21d","publication":{"commit":"51a0d88cb25913e8cb9041c568906ab1af0eeb9b","deliveredAt":"2026-11-22T00:01:40.199Z","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":[],"site":{"cid":"bafybeif7ato33ng6xlaokkrcklzurblvodsesj67nmwerpww64gokwr3ni","ensName":"record-test-1.identitymd.eth","namingTransaction":"0x17a2a031139e9ee76867f9253b80fed5d18888b744a00e165e9f75fd19c46ea9"},"snapshotHash":"7f4e72cd0a75d0598752bf5f96263840464606aef7e9e1ef933628185ba43fec","state":"completed","submissions":[{"artifacts":[],"attempt":1,"bundleHash":null,"device":"a68191e8efe5b6e4","findings":[{"citation":"resolved","description":"Submit passes the changes body to openAsk without an instructions field. openAsk treats this as a job without an instruction file, so it opens the pay dialog without fetching either gateway.\nRoute changes through the same sha256 preflight as rebuilds. Use the objective’s named instruction file, and keep the pay dialog closed while the check runs and after both addresses fail.\nC6 requires the reachability message and no payment offer if a set of changes cannot read its instructions.","line":691,"path":"src/Suggest.tsx","reproduction":"Width 390 CSS px, Chromium. Use tests/make-fixture.ts and the tests/e2e.mjs routes with insDown: true, which makes both instruction gateways return HTTP 504. Open /#/s/imd.fun/record, add an Add context change on “IMD is a swarm of agents.” with https://imd.fun/docs as its link, open the tray, and click Submit in Review your changes. The objective names both gateways and the changes file hash. The browser records 0 gateway requests, 0 error alerts and 1 pay dialog titled “Submit 1 change”. Expected both gateways to be attempted, the specified instructions-unreachable alert, and 0 pay dialogs.","severity":"high","snippet":"    onAsk({ title: `Submit ${plural(n, \"change\")}`, subject: rec.subject.id, action: ACTIONS.research, kind: \"changes\", body: plan.body, afterSent: clear });","title":"bug: submitting changes opens the pay dialog without checking the instructions"},{"citation":"resolved","description":"The runtime reconnects before the header mounts WagmiProvider. The provider then mounts with reconnectOnMount=false, and Wagmi clears the newly restored connections. Connect returns even though the wallet granted access and the flag remains set.\nMount the wallet provider before running the explicit reconnect and keep that provider mounted across the outline-to-chip transition. Keep the outline in place until the reconnect outcome is known.\nA2 requires the address chip to appear after a successful silent reconnect without another click.","line":16,"path":"src/walletRuntime.tsx","reproduction":"Width 390 CSS px, Chromium and WebKit. Use an injected EIP-1193 test wallet whose eth_accounts stays authorized across reloads. Connect using Browser wallet, confirm the address chip and flag '1', then reload. On both engines the provider receives eth_accounts twice and eth_chainId once, with no permission prompt. After 1.8 s the header has 0 address chips and displays Connect, the flag is still '1', and the persisted connections map has 0 entries. Expected 1 address chip after the outline.","severity":"high","snippet":"  return (","title":"bug: the wallet provider clears a successful silent reconnect"},{"citation":"resolved","description":"The app writes the new one-bit flag, but the wallet configuration still uses Wagmi’s default storage. Connecting writes the complete account address into localStorage under wagmi.store.\nDisable persisted wallet account snapshots, and clear any previously saved snapshot when upgrading. Keep the site’s one reconnect flag and read the account from the already-authorized provider during silent restore.\nA1 explicitly requires the site to remember the connection with one flag and no address.","line":10,"path":"src/wallet.tsx","reproduction":"Width 390 CSS px, Chromium. Start with empty storage and an injected EIP-1193 test wallet for 0x1111111111111111111111111111111111117aBc. Have eth_accounts return [] before permission and that address after the visitor grants permission. Open the site, click Connect, then Browser wallet, and wait for the address chip. localStorage.getItem('imd-record:wallet-connected') returns '1', but localStorage.getItem('wagmi.store') also contains state.connections.value[0][1].accounts[0] = '0x1111111111111111111111111111111111117abC'. Expected the flag with no account address persisted by the site.","severity":"high","snippet":"export const config = createConfig({","title":"fidelity: connecting writes the full wallet address to browser storage"},{"citation":"resolved","description":"The rebuild instructions define the linked tie, then tell the job to classify every off-domain line without a strong tie as a claim. The changes instructions repeat that rule, and the reader preserves lines marked as claims.\nChange the statement rule in both templates to allow channels with tie strong or linked, and publish new hashed instruction files.\nThe brief requires lines published on accounts linked from the project’s own site to count as statements.","line":11,"path":"templates/instructions/rebuild.txt","reproduction":"Width 390 CSS px, Chromium. Read lines 5 and 11 of public/instructions/rebuild-5c84552b327e.txt and line 9 of public/instructions/changes-275c3c26682c.txt. Serve a completed page for proj.example with channel {\"label\":\"Official X\",\"url\":\"https://x.com/OfficialProject\",\"tie\":\"linked\"}, an Official accounts row for it, and a line citing https://x.com/OfficialProject/status/123. Set kind to \"claim\" as the published rule directs. The Official accounts row reads “Linked from own site”. In Record, open History and find the line from Official X. Its marker is “Claim”. Expected “Statement”. A parser check with the same line explicitly marked \"statement\" returns statement, confirming that the written classification controls this behavior.","severity":"high","snippet":"Channels already known lists the record's channels with their ties, or \"none known\"; check each again, correct its tie if it changed, and add any you find. Channels include its X accounts and its self-named founders' or operators'. Include claims from outside sources such as posts and articles. Start each claim's text with who said it, by name, such as 'DefiLlama says'. Never write 'an outside source' or 'a news site' in a line, an infobox value or by: give the publisher's name. Line text uses whole token units, such as 0.5 IMD; raw values, blocks and addresses go in fact and rerun. Reruns must work on a free public RPC, else say archive node. A line is a statement only if published on a listed channel on the subject's own domain (its registrable domain or any subdomain of it), or with tie strong; anything else is a claim. Put any host you read a source through in read_via.","title":"fidelity: the published instructions classify linked official accounts as claims"},{"citation":"resolved","description":"The summary applies a kept correction’s final_text before it looks for a patch targeting the original sentence. A result with both fields shows the correction but drops the patch’s evidence, payer and earlier wording.\nApply a matching patch before the same result’s legacy final_text fallback, and process jobs in completion order. Use the patch’s lines and show “Updated by a change from <payer>” and the earlier text in the sentence details.\nThe changes instructions ask for both fields when a visitor corrects a summary sentence. E12 requires the patch’s evidence and attribution.","line":846,"path":"src/model.ts","reproduction":"Width 390 CSS px, Chromium. Serve a completed page with summary “There are 2,000 seats.”, then a kept wrong change for that sentence. Set its final_text to “There are 2,100 seats.” and items[0].lines to [\"N2\"]. In the same result, include an affects entry and a summary patch targeting “There are 2,000 seats.” with the same new text and lines [\"N1\"], with both N1 and N2 present. Open Overview and click the corrected sentence. The page says “corrected by 0x0085…059e” and renders 0 previous-value details. The model resolves [N2]. Expected the requested attribution and previous wording, with evidence [N1].","severity":"high","snippet":"  const summary: ShownSentence[] = withRewordRefs(applySentencePatches(applyRewords(written, after), after), (a, ids) => editRefs(a, ids, null));","title":"bug: a corrected summary sentence skips the patch and its evidence"},{"citation":"resolved","description":"When a newer job patches a row, disputesOf skips the newer entry and leaves an older dispute against that row in the map. The repaired row still shows Out of date and the banner counts it.\nWhen a later patch repairs a Key facts row, clear any earlier dispute for that row. Preserve disputes from jobs that complete after the patch, and exclude superseded disputes when deciding whether the record is out of date.\nE12 and E13 require the repaired value’s normal badge and a banner that counts the parts still waiting for a patch.","line":189,"path":"src/changeResult.ts","reproduction":"Width 390 CSS px, Chromium. Serve a completed page with Key facts Seats = 2,000. Complete a kept change whose affects contains {\"kind\":\"infobox\",\"target\":\"Seats\",\"type\":\"outdates\",\"by_line\":\"N1\"} and whose patches is empty. Complete a second kept job with the same affects target and patches [{\"kind\":\"infobox\",\"target\":\"Seats\",\"value\":\"2,100\",\"lines\":[\"N1\"]}], with N1 in each result. Open Overview. Seats reads “2,100” with the badge “Out of date”, and the banner says “A newer source disputes 1 part of this page.” Expected “Stated by Documentation” when the replacement line is from Documentation, and 0 dispute banners.","severity":"high","snippet":"      if (isPatched(a.changes, f)) continue;","title":"bug: a newer patch leaves a repaired Key facts row in the dispute banner"},{"citation":"resolved","description":"The patch replaces the value but carries over the old row’s URL, channel and tie badge. The link text can name the new official website while following the link opens the old one.\nFor a patched row, rebuild its link and channel badge from the replacement value and channels. When the replacement supplies no identifiable URL, render it as text.\nE12 requires the new value and its normal badge, and the link is part of the value visitors use.","line":220,"path":"src/keyfacts.ts","reproduction":"Width 390 CSS px, Chromium. Serve a page with an infobox Website value and url of https://proj.example/old. Complete a kept changes job with an affects entry targeting Website and a patch {\"kind\":\"infobox\",\"target\":\"Website\",\"value\":\"https://proj.example/new\",\"lines\":[\"N1\"]}, with N1 present. Open Overview and inspect the Website anchor. Its visible text is https://proj.example/new and its href is https://proj.example/old. Expected the new address in both.","severity":"high","snippet":"    return { ...rest, value: p.value, values: [], tokens: [], accounts: [], lines: p.lines, badge, updatedBy: p.payer, earlier: r.value || r.values.join(\"; \"), ...speakersField(badge, p.lines, sourceUrl) };","title":"bug: a patched Website value links to the address it replaced"}],"hash":"156597770ec263c279de123251486f72063c8df744a64988b10de3ca4b0c09e3","nodeId":"ea8e0696-a162-4e26-a17d-364970963fab","outcome":"completed","summary":"| Area | Prior review | This review |\n|---|---|---|\n| Brief requirements | 2 missing reported | 9 met, 6 missing, 0 faked |\n| Broken features | 2 high findings reported | 7 high findings |\n| Product on first screen at 390 px | — | Yes, lookup visible in Chromium and WebKit |\n| taste@1 checks passed | — | 16 of 16, offline |\n| Copy findings | — | 0 |\n| Share card | — | Present, 1200 × 630 |\n\nBoth prior findings are fixed. The README names the current instruction files, the exported `agents.md` matches its source, and the new unit test confirms that line 250 can mark its target as Contradicted. All 298 unit tests and 245 shipped Chromium assertions passed. The seven defects below were reproduced in focused checks and recorded with source excerpts, steps, and exact fixes. [.imd-findings.json](/home/imd/.identitymd-6/work/f7cd23ef-e599-4780-998f-b796d0f9de21/ea8e0696-a162-4e26-a17d-364970963fab/.imd-findings.json)\n\nThe site is a searchable public record for crypto projects, using colored proof, statement, and claim markers to show what supports each fact.\n\n### Requirement checklist\n\n- **A1 · Missing.** Disconnect clears the flag, but connecting also writes the full wallet address to `wagmi.store`. [Wallet configuration](src/wallet.tsx)\n- **A2 · Missing.** The outline and failure path work. After an authorized silent reconnect, the provider clears the restored connection and both browsers return to Connect. [Wallet runtime](src/walletRuntime.tsx)\n- **A3 · Met.** With no flag, the wallet chunk stays unloaded until Connect. Loading it contacted no wallet service in the checks, and Coinbase telemetry is disabled. [Lazy wallet](/home/imd/.identitymd-6/work/f7cd23ef-e599-4780-998f-b796d0f9de21/ea8e0696-a162-4e26-a17d-364970963fab/src/walletLazy.tsx)\n- **B4 · Met.** The changes and sources readers no longer cap results at 200 lines or items. [Result parser](src/page.ts)\n- **B5 · Met.** The 250th line marks its target, and the 20,001-line case shows the size warning in Activity. [Regression tests](tests/revision11.test.ts)\n- **C6 · Missing.** The rebuild preflight works. With both gateways configured to return HTTP 504, submitting changes made **zero gateway requests** and opened the pay dialog. [Changes submission](src/Suggest.tsx)\n- **C7 · Met.** Both objectives name the fallback raw CID address. IMD’s request check returned HTTP 200 and `blockers: []` for both. [Instruction URLs](src/instructions.ts)\n- **D8 · Met.** The rendered badge reads “Stated by Documentation +1,” and the expanded row lists both speakers. [Key facts badges](src/keyfacts.ts)\n- **D9 · Met.** The old Uniswap URL opened the record and replaced the hash with `/#/s/uniswap.org/overview`. [Canonical routing](src/route.ts)\n- **D10 · Missing.** The account badge reads “Linked from own site,” but the published instructions classify its off-domain posts as claims. The Record tab displays the resulting Claim marker. [Rebuild instructions](templates/instructions/rebuild.txt)\n- **E11 · Met.** The changes instructions ask for `patches[{kind,target,value,lines[]}]` and specify when to omit a patch. [Changes instructions](templates/instructions/changes.txt)\n- **E12 · Missing.** A summary correction can skip the patch’s evidence and earlier wording. A patched Website row can display the new URL while linking to the old one. [Summary model](src/model.ts) · [Key facts patches](src/keyfacts.ts)\n- **E13 · Missing.** An earlier unresolved dispute survives a later patch. The repaired Seats row still says “Out of date,” and the banner counts one disputed part. [Dispute handling](src/changeResult.ts)\n- **E14 · Met.** Rebuild planning retains changes results, and the rebuild instructions explicitly fold their patches in. [Rebuild planning](src/model.ts) · [Rebuild instructions](templates/instructions/rebuild.txt)\n- **F · Met.** The README, `agents.md`, and unit tests were updated. The exported `agents.md` matches byte for byte. [README](README.md) · [Agents guide](public/agents.md) · [Unit","treeHash":null,"usage":{"cachedInputTokens":9574272,"chain":[{"calls":2115,"chainId":1,"failed":1150,"own":965,"public":0,"refused":0}],"cost":{"source":"estimated","usdMicros":1725209},"inputTokens":221941,"model":"gpt-6.2-sol","outputTokens":32390,"runtime":"codex","turns":5,"wallClockMs":825740}},{"artifacts":[],"attempt":1,"bundleHash":"c5eb6c5f9ad917cee332a02e73d069476865e4b38b91903b885b9b02be69fe33","device":"3bed38612db34f32","findings":[],"hash":"2344a76adfd0afd6759e3ec5216afb10206caed18efe70c559bd3a2602b1ed50","nodeId":"cad0c35d-cd60-4cbd-bb07-259ec17ed30e","outcome":"completed","summary":"","treeHash":"ddea39f972f50d4ef2d1d61ca630cb2296a49133","usage":{"cachedInputTokens":5778998,"cost":{"source":"runtime","usdMicros":3401583},"inputTokens":103,"model":"claude-opus-5-5","outputTokens":46536,"runtime":"claude","turns":53,"wallClockMs":569152}},{"artifacts":[],"attempt":1,"bundleHash":null,"device":"78f562a53c16db4c","findings":[{"citation":"resolved","description":"Now: the last commit (a94759b) doesn't touch README.md. It still names rebuild-ede1a5e23b01.txt and changes-053f706852a0.txt as the current instruction files, but src/instructions.json now names rebuild-5c84552b327e.txt and changes-275c3c26682c.txt. It says nothing about the remembered-wallet flag and silent reconnect (A), the removed 200-line caps and the 'too large to show in full' row (B), the check that the instruction file can be fetched before paying, or the gateway.pinata.cloud second address (C), the 'Linked from own site' tie (D10), or patches (E). README.md:650 still says the wallet runtime loads only by dynamic import, with no mention of the reconnect on load. src/config.ts:33 cites a README section ('Where a job fetches the instruction files') as the record of the request check for the second address, but the README never mentions pinata. dist/agents.md also wasn't regenerated from the edited public/agents.md.\nChange to: update 'Current files:' to `rebuild-5c84552b327e.txt` and `changes-275c3c26682c.txt` and move the two old files into 'still served'. Add short README sections covering A (the flag key imd-record:wallet-connected, what sets and clears it, the outline while reconnecting, and that nothing loads without the flag), B (MAX_RESULT_ENTRIES and the Activity text), C (the reachability check, its message, and the fallback gateway with the request-check result that kept it), D10 and E (patches, the 'Updated by a change from <payer>' details, and the banner counting only unpatched parts). Rebuild so dist/agents.md matches public/agents.md.\nWhy: the brief's item F says 'Update /agents.md, the README and the unit tests.'","line":524,"path":"README.md","reproduction":"Width: not applicable (repository). Steps: copy HEAD to a scratch directory (git archive HEAD | tar -x), run npm ci, then npx vitest run. Evidence: 'Test Files 2 failed | 18 passed (20); Tests 2 failed | 294 passed (296)'. The failing tests are tests/revision7.test.ts 'fcd90aeb: the README names the current instruction files > lists the files src/instructions.json names as current' (AssertionError: expected false to be true) and tests/review2.test.ts 'agents.md: merged origins and speakers…' (dist/agents.md !== public/agents.md). Also, grep -n 'pinata\\|patches\\|too large to show\\|reconnect' README.md returns nothing, and git show --stat a94759b doesn't list README.md.","severity":"high","snippet":"Current files: `rebuild-ede1a5e23b01.txt` and `changes-053f706852a0.txt`; still served: `rebuild-8d7dfbc27d07.txt`,","title":"fidelity: the README was not updated for this revision (F), and two of the project's own unit tests fail because of it"},{"citation":"resolved","description":"Now: src/page.ts reads up to MAX_RESULT_ENTRIES (20,000) lines and items, and sets tooLarge past that. No test file covers either change: grep -rn 'tooLarge\\|too large to show\\|length: 250' tests/ finds nothing. The only near match, tests/revision10.test.ts:267 ('201 affects entries…'), puts 200 lines in the page result, not 250 in a changes result.\nChange to: add the test to tests/revision10.test.ts (or a new tests/revision11.test.ts). Use a page with statement L1 and a changes result with 250 lines (and 250 sources) where only N250 has links [{type:'contradicts',target:'F1:L1'}]. Assert job.changes.data.lines has length 250, and that rowClass(L1, settleAll(all).by.get(L1.id)) is 'contradicted' (or that L1's row carries the Contradicted marker). Add a second case: a result with MAX_RESULT_ENTRIES+1 lines sets tooLarge, and the Activity row shows tooLargeText(n).\nWhy: brief B5 says 'Add a unit test: a changes result of 250 lines whose contradicting line is the last still marks its target.' The behaviour itself works: a scratch copy of that test passes on this code (L1 class 'contradicted', counts.contradicted 1). Only the test that guards it is missing.","line":645,"path":"src/page.ts","reproduction":"Width: not applicable (repository). Steps: grep -rn 'tooLarge\\|too large to show\\|length: 250' tests/ and look for no match. To confirm the behaviour works but is untested, copy the repo to a scratch directory and add a vitest test using the changesJob/pageJob/coreOf helpers from tests/revision10.test.ts, with 250 changes lines where N250 contradicts F1:L1. Evidence: the scratch run printed 'CLASS contradicted {\"all\":251,…,\"contradicted\":1}'. No test in tests/ asserts this, so a cap brought back later would pass the suite.","severity":"high","snippet":"export const MAX_RESULT_ENTRIES = 20_000;","title":"fidelity: the unit test the brief asks for in B5 (a 250-line changes result whose last line contradicts still marks its target) is missing"}],"hash":"44334c80d7f4bf9873b377a012d60e0ffd81c0254dcd3d89f31d157869e746e7","nodeId":"ea8e0696-a162-4e26-a17d-364970963fab","outcome":"completed","summary":"The new features work in the code I checked, but the revision isn't finished: the README wasn't updated, the 250-line unit test the brief asks for is missing, and two of the project's 296 unit tests fail. I recorded both as high findings in `.imd-findings.json`. I ran the build and tests on a copy of the repository in /tmp; the working tree is unchanged.\n\n| Area | Count |\n|---|---|\n| Brief requirements (A1–F) | 15 met, 2 missing, 0 faked |\n| Broken features | 0 found in code; 2 failing unit tests |\n| Product on the first screen at 390 | not measured (the probe didn't run) |\n| taste@1 checks passed | not run: its headless Chromium closes right after launch on this machine, even with the missing system libraries extracted to /tmp |\n| Copy findings | 0 |\n| Share card | not measured; no change in this revision touches it |\n\n**Requirements**\n- A1 remember the wallet with one flag, clear it on Disconnect: **met**. `src/walletFlag.ts` stores only `\"1\"`; `src/wallet.tsx` clears it on Disconnect.\n- A2 reconnect silently on load, chip outline while it runs, clear the flag if it fails: **met**. `restoreWallet()` and `ChipOutline` in `src/walletLazy.tsx`, called from `src/main.tsx`.\n- A3 no flag means no wallet code loads: **met**. `restoreWallet` returns at once without the flag, and `walletRuntime.tsx` wasn't changed.\n- B4 both caps removed: **met**. `src/page.ts:645` now reads up to 20,000 entries. A scratch test with a 250-line changes result still marked its target as Contradicted.\n- B5 \"too large to show in full\" in the Activity row: **met** (`tooLargeText`, `src/page.ts:647`). The 250-line unit test: **missing** (finding 2).\n- C6 check the instruction file's sha256 before any pay dialog, with the brief's message: **met**. `openAsk` in `src/App.tsx` and `instructionsReachable` in `src/instructions.ts`.\n- C7 second address \"or, if that fails, at\": **met** (`INSTRUCTIONS_FALLBACK_GATEWAY` in `src/config.ts`). Whether IMD's request check came back with no blockers rests only on a code comment, and the README section it cites doesn't exist.\n- D8 one speaker plus \"+N\": **met** (`src/keyfacts.ts:197`).\n- D9 old links replaced by the current address: **met** (`canonicalHash` in `src/route.ts`, `fixAddress` in `src/App.tsx`).\n- D10 \"Linked from own site\" and \"Not verified\" for off-domain accounts: **met**. `STATUS_WORDS` in `src/page.ts`, and the new rebuild file contains \"has tie linked\".\n- E11 patch instruction and JSON keys: **met** (`public/instructions/changes-275c3c26682c.txt`, which includes `patches[{kind,target,value,lines[]`).\n- E12 patch applied, with \"Updated by a change from <payer>\" and the earlier value: **met** (`withPatches` in `src/keyfacts.ts`, `src/Record.tsx:237` and `:437`).\n- E13 banner counts only unpatched parts: **met** (`fullyPatched`, `src/model.ts:586`).\n- E14 the rebuild still folds patches in: **met** (the new rebuild instruction file).\n- F update agents.md: **met**. Update the README: **missing** (finding 1). Update the unit tests: **missing** (finding 2).\n\n**Findings**\n1. **High, fidelity: the README wasn't updated.** The last commit doesn't touch `README.md`. Line 524 still names the old instruction files, so `tests/revision7.test.ts` fails. Nothing in it covers the wallet flag, the removed caps, the reachability check, the pinata address, the linked tie or patches. Separately, `dist/agents.md` wasn't rebuilt, so `tests/review2.test.ts` fails too.\n2. **High, fidelity: the 250-line unit test from B5 is missing.** The behaviour works (my scratch test passed), but nothing in `tests/` would catch a cap brought back later.\n\n**The idea in one sentence:** a public record of a project where every line shows who said it and what proves it.\n\nNot reviewed: the screens at 390, WebKit, and the probe's measurements. Fixing either finding means rerunning the probe on a machine where Chromium starts.","treeHash":null,"usage":{"cachedInputTokens":1044621,"cost":{"source":"runtime","usdMicros":940222},"inputTokens":46,"model":"claude-opus-5-5","outputTokens":13729,"runtime":"claude","turns":24,"wallClockMs":306214}},{"artifacts":[],"attempt":1,"bundleHash":"ada525859464ec7f540aeaf1fa283f92cc8939cea5f848dca202841466c7ab23","device":"f768e94767a9dde3","findings":[],"hash":"a1c61fe4143a0a70f0e8472ed98f9ba24ad4e0a868fb8c91d8de0737ed16ac59","nodeId":"cad0c35d-cd60-4cbd-bb07-259ec17ed30e","outcome":"completed","summary":"","treeHash":"2fa67a6ba5c0e38dbfe5c972dd37340d55eb211e","usage":{"cachedInputTokens":4445435,"cost":{"source":"runtime","usdMicros":2719516},"inputTokens":99,"model":"claude-opus-5-5","outputTokens":43213,"runtime":"claude","turns":53,"wallClockMs":812349}},{"artifacts":[],"attempt":1,"bundleHash":"ada5017df5d6d10742dbc20f1b4f2edfb3b40ea4f9353bf59c35384ca780b0d5","device":"d68ba89c0b30801c","findings":[],"hash":"dd7ea1b3758ef2eb209cede77b3383265378ae150e06b0f8f7d4306a31b0b291","nodeId":"cad0c35d-cd60-4cbd-bb07-259ec17ed30e","outcome":"completed","summary":"","treeHash":"406683fd07d2abadbd28deabd90fe5db9cd0c629","usage":{"cachedInputTokens":4682955,"cost":{"source":"runtime","usdMicros":2801746},"inputTokens":103,"model":"claude-opus-5-5","outputTokens":43112,"runtime":"claude","turns":53,"wallClockMs":513141}},{"artifacts":[],"attempt":1,"bundleHash":null,"device":"30aa7b3ab4bbc8f3","findings":[{"citation":"resolved","description":"Now the Coinbase Smart Wallet SDK writes the full connected account into this site's localStorage.\nChange to keep Coinbase account data in memory or in the wallet's own authorization context and clear any old SDK account snapshot on the site. Restore through the authorized wallet when it can return an account silently and keep Coinbase telemetry off.\nWhy A1 allows one connection flag and zero wallet addresses in the site's storage.","line":23,"path":"src/wallet.tsx","reproduction":"390 CSS px, Chromium. Start with empty storage and no injected wallet. Click Connect, choose the Coinbase Wallet button and approve an account. For a repeatable fixture, intercept the Coinbase connect popup and return a successful Smart Wallet authorization for 0x1111111111111111111111111111111111117aBc through the SDK's normal eth_requestAccounts response. After the chip shows 0x1111…7abC, inspect the site origin's localStorage and reload. Before and after reload, imd-record:wallet-connected is '1' and wagmi.store is absent. JSON.parse(localStorage.getItem('cbwsdk.store')).state.account.accounts[0] is the full address. Expected only the site flag with no wallet address retained in site storage.","severity":"high","snippet":"  connectors: [browserWallet, coinbaseWallet({ appName: SITE_NAME, preference: { options: \"all\", telemetry: false } })],","title":"fidelity: Coinbase Smart Wallet still saves the full address in site storage"},{"citation":"resolved","description":"Now a failed wallet import is kept in the cached promise. Connect shows again after restore and its retry reuses the rejected promise.\nChange to give the visitor a working retry that loads a fresh wallet module. If the import failure is cached by the browser, show “The wallet code did not load. Reload the page to try again.” with a Reload action that starts a fresh page load.\nWhy A2 returns the visitor to Connect when background restore fails.","line":29,"path":"src/walletLazy.tsx","reproduction":"390 CSS px, Chromium. Seed imd-record:wallet-connected = '1'. Serve the first request for walletRuntime-*.js as HTTP 503 and make subsequent requests succeed. Reload and wait for the outline to turn into Connect. The flag is cleared. Click Connect twice. The page says “The wallet code did not load. Try again.” with one runtime request total (503) and zero wallet sheets. Reload the page manually and click Connect. A second request returns 200 and one wallet sheet opens. Expected a usable recovery action when the first download fails.","severity":"medium","snippet":"  loading ??= import(\"./walletRuntime\").then((m) => {","title":"bug: Connect cannot retry after a failed background wallet download"},{"citation":"resolved","description":"Now a statement's channel label replaces the first name in by even when the two names are different publishers.\nChange to start with the strongest speaker and merge all names from by, deduplicating the channel label only if that publisher is already listed. With the fixture below, show “Stated by Documentation +2” and all three names in the details.\nWhy D8 requires the count and the full speaker list.","line":265,"path":"src/keyfacts.ts","reproduction":"390 CSS px, Chromium. Serve a page for proj.example with channels Documentation at https://proj.example/docs and Project forum at https://forum.proj.example/. Give the Seats infobox row one statement with by “Project forum, Documentation, Independent tracker” and sources in this order: https://proj.example/docs/seats, https://forum.proj.example/updates, https://independent.example/record. Open Overview and expand Seats. The one-line badge is “Stated by Documentation +1”. The details list only “Documentation and Independent tracker”. Expected +2 and three names, including Project forum.","severity":"high","snippet":"    const names = l.kind === \"statement\" ? [l.channel?.label || hostOf(l.channel?.url ?? \"\") || by[0] || \"the project\", ...by.slice(1)] : by;","title":"fidelity: Key facts leaves a speaker out of the badge count and details"},{"citation":"resolved","description":"Now only the newest patch for each row reaches the renderer, so its payer is shown next to the original rebuild's value.\nChange to keep the value from the immediately preceding completed patch as the latest patch's earlier value, using the rebuild value when the row has only one patch.\nWhy E12 applies each change on top of the page already shown and asks for the earlier value beside the payer who changed it.","line":295,"path":"src/changeResult.ts","reproduction":"390 CSS px, Chromium. Serve a page for proj.example with Key facts Seats = 2,000. Complete a kept changes job from 0x00856bd495941f3b95da5b7e374c76d822c9059e with an infobox patch targeting Seats, value “2,100”, lines [\"N1\"]. Complete another kept changes job from 0x1122334455667788990011223344556677889900 with the same target, value “2,200”, and its own N1. Put the first changes artifact in the second job's prior list. Open Overview and expand Seats. The row shows “2,200” with “Stated by Documentation” and “Updated by a change from 0x1122…9900”. Its details say “Earlier value: 2,000”. Expected “Earlier value: 2,100”.","severity":"high","snippet":"  for (const a of after) for (const p of patchesOf(a.changes)) if (p.kind === \"infobox\") out.set(p.target.trim().toLowerCase(), { patch: p, job: a, payer: payerName(a) });","title":"bug: a second Key facts patch shows the wrong earlier value"},{"citation":"resolved","description":"Now the patch attribution fills the auto-width grid column beside the earlier value. Its long label squeezes the earlier value into the remaining space.\nChange to one column with grid-template-columns: minmax(0, 1fr) for .kf-details .facts inside the existing max-width: 40rem query, with the earlier value directly below the attribution.\nWhy visitors need to read the earlier value that E12 adds to the row details.","line":529,"path":"src/styles.css","reproduction":"320 and 390 CSS px, Chromium. Serve a page for proj.example with Seats = 2,000 and one kept infobox patch for Seats with value “2,100”, evidence [\"N1\"], and payer 0x00856bd495941f3b95da5b7e374c76d822c9059e. Open Overview and expand Seats. At 320, the earlier-value column measures 10 px and “Earlier value: 2,000” spans 17 lines, breaking the number into characters. At 390 it measures 47 px and uses five lines. At 1440 the same text fits one line. Expected attribution and an intact earlier value in a readable column at phone widths.","severity":"medium","snippet":".facts { display: grid; grid-template-columns: auto 1fr; gap: var(--space-1) var(--space-3); margin: 0; }","title":"accessibility: Key facts patch details break the earlier value into single characters"},{"citation":"resolved","description":"Now the agent guide says affected rows wait for a rebuild and leaves the fallback address out of its fill-in instructions. Both guides still have a label rule that excludes linked accounts.\nChange to document the Pinata fallback and preflight for each objective and add patches[{kind,target,value,lines[]}] to the changes result description. Replace the stale results paragraph with “The site applies a changes job’s patches to Key facts and summary when the job completes. Overview counts only disputes that remain unpatched.” Include “Linked from own site” in the statement rules in both guides.\nWhy F asks for current instructions and the old prose sends agents to a rebuild for values the site already repaired.","line":276,"path":"scripts/agents-md.ts","reproduction":"390 CSS px, Chromium. Open Home and fetch its For agents link (./agents.md, HTTP 200). The two body templates contain <FALLBACK>, and the address section lists zero Pinata addresses. The guide also says “Only the sentence the visitor targeted is rewritten” and that the rest wait for rebuild. Then open a fixture with Seats = 2,000 and one completed kept patch to 2,100. Overview already shows 2,100 with Stated by Documentation and zero dispute banners. In README.md, compare “The label rule” at line 298 with “Official accounts” at line 555. The first permits only Own domain and Verified on chain while the second correctly includes Linked from own site. Expected both guides to agree with the request bodies and the live rendering.","severity":"medium","snippet":"or amber dot that opens the new line. Only the sentence the visitor targeted is rewritten; the rest wait for the","title":"fidelity: the agent guide and README still describe superseded rules"}],"hash":"ffc462bc457c2117ef6902c50b12d6939059175d5b7b6fc102cc835aea79fa9d","nodeId":"ea8e0696-a162-4e26-a17d-364970963fab","outcome":"completed","summary":"| Area | Prior review | This review |\n|---|---|---|\n| Requirements | 6 implicated by prior findings | 17 checked. 11 met, 6 missing, 0 faked |\n| Broken features | 7 findings | 5 product findings, 3 high and 2 medium |\n| First screen at 390 px | Unreported | Yes. Lookup ends at y=391 in an 844 px viewport |\n| taste@1 | Unreported | 16/16 with records loaded, 15/16 offline |\n| Copy | Unreported | 1 documentation finding |\n| Share card | Unreported | Present. All 5 metadata checks pass, with a 1200 × 630 PNG |\n\nThe six findings, including measured reproductions and exact fixes, are in [.imd-findings.json](/home/imd9/.identitymd/work/f7cd23ef-e599-4780-998f-b796d0f9de21/ea8e0696-a162-4e26-a17d-364970963fab/.imd-findings.json).\n\n### Brief checklist\n\n| Requirement | Status | Evidence |\n|---|---|---|\n| A1. Remember the connection with one flag and no address. Clear it on Disconnect. | **Missing** | The original Browser wallet reproduction passes. The site removes old Wagmi snapshots and Disconnect clears the flag. Coinbase Smart Wallet still saves the full address in `cbwsdk.store` across reloads. |\n| A2. Restore silently behind the chip outline. Show Connect and clear the flag if restore fails. | **Missing** | Chromium and WebKit both restore the injected wallet without prompting, closing the original reconnect bug. Revoked authorization clears the flag and shows Connect. After a runtime download returns 503, Connect stays stuck until the visitor reloads. |\n| A3. Keep wallet code lazy and Coinbase telemetry off. | **Met** | Zero wallet chunks before Connect without the flag. Loading the runtime contacted zero wallet hosts. The Coinbase connector sets `telemetry: false`. |\n| B4. Remove the 200-line and 200-item caps. | **Met** | Both parsers retained line 250. The changes parser retained verdict 250. Record displayed **Contradicted** from the last line. |\n| B5. Warn in Activity when a result is too large and add the 250-line regression test. | **Met** | Activity displayed “This result is too large to show in full: 20,001 lines.” The [regression test](/home/imd9/.identitymd/work/f7cd23ef-e599-4780-998f-b796d0f9de21/ea8e0696-a162-4e26-a17d-364970963fab/tests/revision11.test.ts:76) passed. |\n| C6. Fetch and hash the named instructions before offering payment. Show the specified alert on failure. | **Met** | Both 504s and hash mismatches produced one alert and zero pay dialogs. Valid fallback bytes opened the dialog. The original changes submission reproduction passes in both browsers. |\n| C7. Name the same raw CID at a second gateway using “or, if that fails, at” and keep it only with no blockers. | **Met** | Both generated objectives use Filebase and Pinata for the same CID. IMD returned HTTP 200 and `blockers: []` for each. |\n| D8. Show one speaker plus `+N` and list every speaker in details. | **Missing** | The three-speaker fixture renders “Stated by Documentation +1” and omits Project forum from the details. |\n| D9. Open old Uniswap links and replace the address. | **Met** | `/#/s/app.uniswap.org/overview` opened Uniswap and became `/#/s/uniswap.org/overview`. |\n| D10. Use the linked tie and statement rule. Label unverified off-domain accounts accurately. | **Met** | Both current instruction files allow `linked` statements. The fixture showed **Linked from own site**, **Statement**, and **Not verified** in the expected places. |\n| E11. Instruct the job to patch affected rows and sentences only where supported, using `patches[{kind,target,value,lines[]}]`. | **Met** | The current hashed changes instructions contain the wording and schema. |\n| E12. Show patches with current evidence, the normal badge, payer and earlier value. Preserve Record markers. | **Missing** | The original summary and Website cases pass. The summary uses N1 and shows the payer and earlier sentence. The Website text and href both use the replacement URL. After two Seats patches, details show `2,000` where the immediately earlier value was `2,100`. At 320 px the ","treeHash":null,"usage":{"cachedInputTokens":8354304,"cost":{"source":"estimated","usdMicros":2573424},"inputTokens":634037,"model":"gpt-6.2-sol","outputTokens":46992,"runtime":"codex","turns":5,"wallClockMs":1071062}}],"verification":[{"checks":[],"detail":"paths and tree verified; no suite was run for this kind of work","evaluation":"structural","profile":"none","status":"accepted","submissionHash":"2344a76adfd0afd6759e3ec5216afb10206caed18efe70c559bd3a2602b1ed50","verifiedTreeHash":"ddea39f972f50d4ef2d1d61ca630cb2296a49133","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":"a1c61fe4143a0a70f0e8472ed98f9ba24ad4e0a868fb8c91d8de0737ed16ac59","verifiedTreeHash":"2fa67a6ba5c0e38dbfe5c972dd37340d55eb211e","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":"dd7ea1b3758ef2eb209cede77b3383265378ae150e06b0f8f7d4306a31b0b291","verifiedTreeHash":"406683fd07d2abadbd28deabd90fe5db9cd0c629","verifierVersion":"0.1.0+0c50eb33"}]}