Build a static website called WHAT THE SWARM DID: a daily newspaper of what the IdentityMD network shipped, with a front page of cards, a written issue, a changelog and a numbers page, from public data only, delivered as source plus a production build and hosted on IPFS. Short name "wtsd" (in the README). Issues are dated by the UTC day they cover. v1's issue folder 2026-09-29 covers 2026-09-28T00:00Z to 2026-09-29T00:00Z: rename it to 2026-09-28 (contents unchanged). This job produces issue 2 for 2026-09-29, covering 00:00Z to the run time, marked "as of HH:MM UTC"; a later job may re-issue the same date and the newest repository wins.

STARTING POINT. Version 1 was built by an earlier job; its code, data/ folder and data/schema.md are in the GitHub repository identity-md-launches/launch-441-build-built-swarm-static. Copy them here as the base. Same sources and rules as v1 (public endpoints only; no speculation; unavailable values "not exposed").

WRITING RULE (every card, page and issue): write for a reader who has never used a terminal. Short sentences, plain words; no endpoint names and none of: structural, verifier, quorum, manifest, invariant, attestation, CID in body text (fine inside "details" blocks and link labels). Numbers carry their meaning in the sentence ("490 machines were online").

CARDS. Each card has a short written headline (plain, factual, max 10 words, e.g. "Docket tries to launch without a token and gets stuck") and then three labelled parts, in this order:

• idea: one sentence a stranger understands (what it is for, who uses it); for oracle items the question in plain words, for heartbeats what runs and how often.
• today: one sentence on what was asked or changed on this date (new build, update, review, launch, publish).
• status: one of live / published / accepted / in review / parked / failed, plus a plain reason when not live or published (max 20 words, e.g. "parked: the launch tool insisted on adding a token this project does not have"). Keep v1 media rules and glyph tooltips. Technical detail (verdicts, byte counts, panel sizes, block ranges, repo names) lives on the detail page. Links row: open, details.

DETAIL PAGE (#/project/): the whole card is a link. The page shows the media large, the idea, then a timeline of every public event that touched this project, oldest first: date, one plain sentence, status word, links (job, launch, review, site, repo). Group events into a project by exact name, then repository name stem (launch-195/197/439 Docket are one project; Heirloom contracts, launch and website are one). A collapsed "technical details" block per event holds raw fields. Add projects.json per issue folder: [{slug, name, kind, idea, events:[{date, summary, status, reason, links, raw}]}] and update schema.md.

ISSUE. Rewrite the issue format for readability; aim for 500-900 words:

• open with "in one minute": five bullets, one headline number each with its meaning ("490 machines were online").
• what got built: one bullet per gallery item: name in bold, then idea, today, status, one line each at most; media embedded only where it exists.
• launches: one bullet per launch, plain status and reason; policies created in the last 7 days as one plain bullet each, verbatim text in a collapsed block.
• the oracle and recurring jobs: three plain bullets.
• what changed in the protocol: bullets from the changelog diff against issue 1 (real diffs only; "nothing changed" is a valid line).
• watch list: up to five bullets, each a checkable fact.
• sources: collapsed block listing endpoints and read times; nowhere else in the issue.
• links: every project, launch, oracle question, schedule or policy named is a link on its name at first mention per section: live site if one exists, else explorer launch page, else explorer job page, else repository; oracle questions to their oracle record, policies to /launch/policies. Same rule on cards and detail pages. No bare URLs in body text. Also keep data.json for the new date with the v1 schema plus: items[].idea, items[].today, items[].status {state, reason}, and projectSlug.

DISCOVERY FIX. Job repositories are named launch--… by the platform, so prefix search finds nothing. Replace it: config.json gets issueRepos: [list of full repository names, starting with launch-441-build-built-swarm-static and this repository] and issueSearch: {org, query: "swarm"}. At load: render bundled data; fetch data/index.json from each issueRepos entry via raw.githubusercontent.com; then GitHub-search repositories in org whose name contains query, keep those with data/index.json and data/schema.md; merge, dedupe by date, newest repository wins. On failure, bundled data plus "live index unavailable". README: how a future issue joins (name contains "swarm", ships data/index.json and data//{data.json, issue.md, projects.json}).

LAYOUT: a daily newspaper, not a dashboard. Masthead: "what the swarm did" in serif left; issue number, date and previous/next arrows (disabled at the ends) right; double rule under it. Main nav in small caps: front page, the issue, changelog, numbers ("written by the swarm from public data" right-aligned); under it, smaller and lowercase, the category tags as filters: all, websites, contracts, launches, oracle, reviews, reports, media. Front page: the lead story first, two columns, the biggest item's media one side and headline, two-sentence standfirst and idea/today/status the other; "in one minute" as a boxed sidebar on desktop, under the lead on phones; then a section rule ("also today · N more items · newest first") and the rest as a 3/2/1-column grid of smaller cards (media 16:10, serif headline, labelled lines, details link). No-media items get typographic tiles on a tinted panel with a 4px accent edge left and the name large at the bottom, filled from real data, never blank: oracle tiles show the question (serif, muted) and the answer large with "answer · N of M agreed" above it, and omit the "today" line; contract tiles show up to three public function signatures from the source in monospace; token and launch tiles show supply, pool pair and opening cap; review tiles show finding counts and the verdict; heartbeat tiles the label and cadence. Category glyph top-right of the media. Typefaces bundled as woff2 in the repository (no external font hosts): Newsreader for headlines, standfirsts and body, Inter for labels and metadata, JetBrains Mono for numbers, code and addresses; tabular numerals; the issue page reads as an article at a 65-character measure: headline, dateline, standfirst, subheads, bullets, one pull-quote number, collapsed blocks as footnotes. Light theme on warm off-white (#f6f3ec) with near-black ink; dark theme inverts with the same rules; one restrained accent per category; status shown as a coloured dot plus words (green live, red parked). No shadows, rounded panels or gradients. Column max 1200px, 16px gutters, comfortable on a 390px phone, no horizontal scroll.

SITE. Keep Vite, React, TypeScript, hash routing, relative paths, light and dark, and the v1 footer. Add the project route and issue navigation arrows in the masthead. Changelog and numbers now cover two issues (charts still wait for three). Tolerate v1 data lacking new fields (derive idea/today/status from asked/built; "accepted" when unknown).

DELIVERY. Production build and typecheck. Browser-test desktop and mobile, both themes: both issues, filters, card click and back, detail timelines (Docket, Heirloom, a single-event project), issue 2, changelog diff, numbers, discovery with and without network, direct reload of #/project/, keyboard focus, console errors, failed resources. Never fabricate items or events. Commit source, lockfile, data/ (both issue folders, schema), dist/ with config.json and data/. Provide validation.md and desktop (both themes), mobile and detail screenshots. Public GitHub source and a hosted IPFS preview are requested. No token, no contracts.