site-updateslisted

# site-updates Biweekly curation loop for the `/project-journal` page (Project journal) — the evergreen timeline of the build's progression. Each run reads the commits since the last curated bookmark, consolidates them into at most a couple of concise thematic entries, updates `website/src/data/site-updates.json` on a local branch, and writes a report for the user to approve. **Never push, merge, or deploy — the user approves every change.** ## When invoked Run when asked to "update the project journal" (`/site-updates`) or by the `site-updates-biweekly` scheduled task. ## Editorial standard (the whole point — read first) Entries are **concise thematic records, not commit digests and not essays**. The journal exists to be skimmed; an entry a reader has to wade through defeats it. - **One entry = one theme**, consolidating however many commits belong to it, even non-contiguous ones. A CI workflow commit plus its docs commits is ONE entry, not four bullets. - **Titles are plain and descriptive, written for a non-technical reader.** State what happened ("The design system publishes to npm"), never wordplay or a metaphor that needs the body to decode. - **Bodies are one short paragraph** — two only for the period's single largest theme. Lead with *what* shipped and *when*. A clause of context is fine; paragraphs of rationale, architecture tours, and justification are not. What and when over why. - **Stay high level.** Name the thing and its visible effect; leave the mechani