Publish this week's issue of CHANGELOG.md, an unofficial weekly newspaper about the IMD swarm (imd.fun) written for ordinary, non-technical readers. The repository already holds the paper's website and its earlier issues in issues/. Cover the most recent full week, Monday 00:00 to Sunday 24:00 UTC, before the moment this job runs.

PART 1, THE NEWS. Gather the week's facts from IMD's public API at https://api.imdnotdead.fun (send your own User-Agent header; the default ones are refused) and write them as issues/NNN.json, where NNN is the number of earlier issue files + 1, three digits. Write for readers who know nothing about code or crypto: plain English, short sentences, no jargon, no addresses, hashes or code words in the text. Say what each thing does and why a normal person might find it interesting. Never discuss token prices, market caps, trading or returns, and never suggest buying anything. Refer to workers only as 'Seat #N'. Leave out spam, offensive or copycat projects. An empty list is fine when nothing qualifies.

The issue file has exactly this shape: {"no": N, "date": "YYYY-MM-DD, the UTC date this job runs (the publication date)", "week": "the covered week, e.g. 5–11 October",

"lead": {"kicker", "headline", "standfirst", "body": [three short paragraphs], "visit": url or null, "source": url},

"new": [{"headline", "summary", "more", "visit", "source"}] up to 4, from GET /publications?sort=newest, /launches and /workflows,

"bugs": [{"severity": "Serious" or "Moderate", "headline", "summary", "source"}] up to 3, from GET /publications?type=audits and /jobs/:id/report.md, explained as what could have gone wrong for users,

"answers": [{"question", "summary", "source"}] up to 3, from GET /oracle/requests (status attested), each question rewritten in plain words; prefer questions about real projects, the IMD network or on-chain activity, and use general-knowledge trivia only when there is nothing else,

"numbers": {"accepted", "launches", "answers", "online"} as integers, from /steps/hourly, /jobs?since=, /launches, /oracle/requests and /health; 'online' is the number of connected workers,

"meter": {"level": 0-100, "verdict": one short line}, how busy the week was against the week before (50 = the same),

"leaders": [{"seat", "jobs"}] the 3 seats with the most accepted work during the covered week, counted from that week's jobs (GET /jobs?since= and GET /jobs/:id, accepted nodes and their seat),

"leadersScope": "this week", or "all time" only if a weekly count was impossible and /seats/records totals were used instead,

"watch": {"headline", "text", "visit"},

"glossary": the terms the issue uses, from: swarm, worker, schedule, audit, oracle, seat, launch}

'visit' links go to a project's own site (https://LABEL.sites.imd.fun) or explorer.imdnotdead.fun; 'source' links go to the api.imdnotdead.fun record that proves the entry. The lead is the most interesting story of the week. Every story must come from the covered week.

PART 2, THE PAPER. Then update the website so it includes every file in issues/, as described in the step.