Issue 002 of CHANGELOG.md is published and committed (commit 89035d1), with the rebuilt site export.

The news (issues/002.json). Covered week 5–11 October 2026, publication date 12 October. Every story comes from a record on api.imd.fun inside that week:

• Lead: Pepeolithic, a cave-wall website painted by one-task helpers, published 9 October.
• New: the "IMD, right now" live status page, Swarm Chat, QuantumCanary, and the Worker Frens five-layer portraits.
• Bugs: three serious audit findings (PondPad reward freeze, a seat vault whose registration could never work, Sherwood scoring on the amount asked rather than spent), each explained as what could have gone wrong.
• Answers: the network health index, a PEPE transfer count, and whether it rained at Heathrow, all attested in the week.
• Numbers: 3,693 completed jobs, 203 live launches, 953 answers, 966 workers online. Meter 41 (18% fewer jobs than the prior week, whose figure reproduced issue 001's 4,517 exactly). Leaders counted from the week's 3,693 job details: Seats #1120, #1943, #13, so leadersScope is "this week".

The paper. Issue 001's date was changed to 2026-10-10 (its only change). The index and RSS list both issues newest first. The site design and code are unchanged apart from the requested items: date line with "Covering ", the seats heading switching between "this week" and "of all time", the "Workers online" label, plus Open Graph tags with a locally rendered share image, which the acceptance criteria required and the page lacked.

Validation. Typecheck, build, content and evidence checks pass, and 57 Chromium interaction checks pass (two tabs with Latest on the newest, sources switch, glossary, keyboard tabs, offline, no-JS, axe clean at five widths, no overflow). One limitation: the sandbox proxy refused Google Fonts for the test browser, so rendered checks used fallback fonts. Details are in docs/validation-002.md, README.md and DESIGN.md.

One note on the commit: git add -A fails in this sandbox because of device-file stubs in the workspace root, so I staged the deliverable paths explicitly. The worker's own git add -A may need the same treatment.

Review complete. The findings file holds four entries, none critical or high, so nothing blocks hosting.

What was read

Every hosted file in dist/ and its source: the built HTML, the 240 kB bundle, the stylesheet, the feed, favicon, share image and notices, plus the React source, the build config, the content and test scripts, both issue files and both evidence notes. The bundle is React plus the app only. It makes no network calls of its own, uses no storage, cookies, wallets, eval or iframes, and the only external request is the Google Fonts stylesheet. All 77 lockfile packages resolve to the npm registry. Embedded issue data matches the issue files byte for byte, and prose is rendered as text with links restricted to api.imd.fun, explorer.imd.fun and project sites.

What was verified against the live API

• Completed jobs, launches, signed answers and the meter all recount exactly: 3,693 and 4,517, 203 and 953.
• Weekly seat leaders recount from accepted nodes in 3,684 of the 3,693 jobs: Seat #1120, #1943 and #13 with the same totals.
• All fourteen story sources exist and fall inside 5 to 11 October. All ten Visit links return 200.

Findings written to .imd-findings.json

• Medium, issues/002.json:14. The lead's Visit link opens Pepeolithic, which by its own text is a token-priced sale with wallet connection and a drop opening the afternoon of publication day. The lead describes it only as a charming artwork record, which sits badly with the paper's rule against suggesting purchases.
• Medium, dist/index.html:17. Vite inlined the RSS discovery link as a base64 data: URL instead of ./feed.xml, so feed autodiscovery gets a frozen snapshot. The README claim and the test suite both miss this.
• Low, dist/feed.xml:5. The channel link is imd.fun, so readers present IMD's homepage as the paper's own site despite the unaffiliated disclaimer.
• Low, dist/index.html:12. The share image uses a relative URL, which link-preview scrapers ignore.

No files other than the findings file were created or changed.

Saved five findings in .imd-findings.json. Website files remain unchanged.

• High — fidelity: Weekly rankings exclude accepted work in blocked jobs. Seat #13 has two omitted reviews.
• Medium — bug: RSS issue links open API JSON instead of newspaper editions.
• Medium — fidelity: Two summaries confuse requested panel sizes with actual responses: 100 versus 54, and five versus four.
• Medium — fidelity: The transfer question retains unexplained crypto vocabulary.
• Low — fidelity: Seven share metadata tags and new images exceed the explicitly permitted changes.

Each finding includes exact source lines, replacement instructions and concrete reproductions.

The checklist’s editorial references are to issues/002.json; interface references are to src/App.tsx.

Revision complete. All five findings were reproduced against the live API before anything changed; four are fixed, one is disputed, and the answers are in .imd-responses.json.

Leaderboard (high, fixed). Both cited jobs are blocked and each holds an accepted review by Seat #13 inside the week, so the completed-only rule under-counted. I fetched every job created from 1 October or updated from 3 October (6,233 records) and counted every accepted node with an acceptance time inside the week, whatever the parent job's state. The old rule reproduced the published 32/31/29 exactly, confirming the trail.

Ties list the lower seat first. The evidence checker now enforces the acceptance-time rule and passes against a rebuilt trail that also re-derives the published job, launch and answer totals from fresh reads.

Advisory findings.

• RSS links (fixed). IMD's own publication record for issue 001 names the paper's site, which is live and serves the feed. The feed now links the channel there and each item to its issue tab. The build setting for another address still works, and a new browser check covers the links.
• Helper counts (fixed). The health answer says 54 checked and 53 agreed. The Heathrow answer says four checked and all four agreed.
• Transfer question (fixed). Reworded as a digital currency moving over half an hour, with no token, block or ledger terms. The verified count and agreement are unchanged.
• Share metadata (disputed). The acceptance criteria require og:title and og:image in index.html, so the tags and image stay. No other page code changed.

Checks on the final source ran in an external mirror: typecheck clean, production build, content and evidence checks passing, and 58 browser checks passed with zero accessibility violations at five widths, no overflow, and no console or request failures. Fonts loaded in this run. The export, feed and index were copied back. Issue 001 is byte-for-byte unchanged, and no dependency or cache directories entered the tree.

Four findings are fixed. One low-severity advisory remains. No high-severity findings remain. Saved to .imd-findings.json. Website files are unchanged.

The site is a weekly community newspaper carried by warm newsprint, ruled columns and a gothic masthead.

The requirement checklist below includes retained requirements; this round focused on the reported regressions.

Wrote .imd-findings.json.

• Fixed: RSS channel address.
• Medium, unresolved: lead’s token-sale link; embedded RSS discovery URL.
• Low, unresolved: relative share-image URL.

No critical or high findings. TypeScript, build and all 58 browser checks passed. Rebuilt export matches the committed files exactly. Site files remain unchanged.