Implemented all four indexer changes and rebuilt dist/, preserving the existing design and dependencies.

Build, typecheck, 284 tests, responsive checks, and live counts 5/47/0 passed. WebKit could not run because required system libraries are missing.

Results and limitations are recorded in artifacts/validation.md; build instructions and design documentation are updated.

Review complete. The findings file is written and the working tree is otherwise untouched; the build and browser checks ran in a scratch copy under /tmp.

Result: nothing critical or high. The site can be hosted.

What I verified:

• Build reproducibility. Running the README recipe (npm ci, agents script, typecheck, build) on a copy of the source produced a dist byte-identical to the committed one. The export has 90 files in the same layout as the previous version, with only the four hashed asset names changed.
• Scripts and outbound traffic. The bundle loads no script from another origin and has no iframes. In a headless Chromium run of the home, catalog, mint, explorer and fact-check pages at 1280 and 390 px, outbound requests went only to ethereum-rpc.publicnode.com, api.imd.fun and sworn.vibingco.de/api. No console or page errors, no horizontal overflow.
• The four changes. The catalog shows rule 10001 as "at least 5 Transfer events of 0xd34a… sent by the wallet to 0x4e0f… between blocks 26,038,414 and 26,279,931" with the registrant and the one-ring CommunityCard. The indexer module validates every field, recomputes met from count, op and threshold, and falls back to the chain path on any null, unsupported or partially indexed answer. Fact-check and history read the wallet endpoint first. The live indexer returns count 5, 47 and 0 for the three named wallets and card 2 with four verified requests for the first one. The unit suite (284 tests) and the project's indexer browser suite both pass.
• No drainer, seed-phrase prompt, impersonation, obfuscation or hidden redirect anywhere in the source or export.

Findings recorded in .imd-findings.json:

• Low. The 1.5 second indexer deadline in web/src/indexer.mjs discards a late answer and silently falls into the browser log scan that public RPCs cannot finish. Live latency here is 0.6 to 0.75 s, so it works today, but slow links will see the fallback text.
• Info. The community card's SVG description ends with a dangling " · " because the window string is now always empty.
• Info. The site reads the launch 2404 registry, which matches the indexer, not the registry in this project's deployment.json. That is the state the requester commissioned since version 2, so it is noted for the verifier, not flagged as a defect.

I found three problems in the four indexer changes: two medium and one low. Nothing is high, so none of them reopens the build. The findings are in .imd-findings.json, and the working tree is otherwise unchanged.

Area	Count
Brief requirements	14: 13 met, 0 missing, 0 faked, 1 after review
Broken features	1 (rules disappear when the indexer is behind the chain; medium)
Product on the first screen at 390	yes ("Explore wallet" input and button are above the fold)
taste@1	15 of 17 pass; the 2 failures are the design the owner approved, so they are not findings
Copy findings	1 (medium)
Share card	present: title, favicon, og:title and og:image (./share.png); the share check passes

Requirements

1. "first asks GET /api/rules/:id/eligibility… uses that answer": met, in web/src/eligibility.mjs scan() and web/src/indexer.mjs indexedEligibility. Against the live API it returns 5/met, 47/met and 0/not met for the three wallets in the brief.
2. "The browser scan stays as the fallback": met. Any answer that is not supported, not fully indexed or not valid returns null, and the old readSpec scan runs.
3. "The eligibility text names its source": met, but the wording is wrong (finding 2).
4. "catalog facts 601 to 1301… nothing reads the indexer for them": met. The snapshot check comes first, plus a guard for ids below 10001 in indexer.mjs.
5. "every community rule shows… what it counts… plus the registrant", in the catalog and in Mint Facts: met, in web/src/community-rule.mjs, pages.tsx and claim.tsx. At 320 and 390 the text reads "at least 5 Transfer events of 0xd34a…e263b7 sent by the wallet to 0x4e0f…adbc between blocks 26,038,414 and 26,279,931", with the registrant on the next line. The page prints both addresses in full (shortened here); nothing overflows.
6. "GET /api/rules gives the fields…; specOf… the fallback": met, with a bug (finding 1).
7. "CommunityCard for ids of 10001 and above": met, at claim.tsx:1499 and in the catalog row in pages.tsx. The card renders at 56px.
8. "first read GET /api/wallets/:address… fall back to the scan": met, in history-controller.ts, live-controller.ts, swarm.tsx and claim.tsx. The live page shows card 2 and the verified requests 601, 701, 1105 and 1301.
9. "no new npm dependency": met; package.json is not in the diff.
10. "no design change; hash routes, data files, ABIs, static export layout": met. The only dist/ metadata changes are new asset hashes.
11. "one constant… default https://sworn.vibingco.de/api": met, INDEXER_BASE_URL at web/src/indexer.mjs:2.
12. "build the dist… as web/README.md says": met, partly checked. The bundle dist/assets/index-omQwcS2n.js contains the indexer URL, "Registrant:" and "Source: indexer, block". I did not rebuild it myself: web/node_modules is not installed and time was short.
13. "put the source tree… into this project's repository": met; web/ is committed.
14. "host the dist under this project's name": after review.

The idea: a monospace instrument panel for one registry, carried by dense rows of facts with the hive card as the only image.

Findings

1. Medium, bug: a lagging indexer hides registered rules (web/src/chain.ts:354). The rule list from /api/rules now replaces the registry's own count. When the API answered {"rules":[]} (tested with an intercepted response), the catalog said "No community specs registered yet" and Mint Facts showed no row for 10001, which is registered on chain. With the live API as it is today the row shows correctly. Fix: keep reading nextSpecId and only use the indexer for the fields of rules it actually lists.
2. Medium, copy: the eligibility text names two sources (web/src/eligibility.mjs:28). An indexer answer reads "Our check of the public chain data finds this rule met (…). The panel decides. Source: indexer, block 26,281,272." Replacement: "Th