/changelog: the last 30 releases, newest first, each with its date and the pulls it carries, readable by anyone #6096

releases.json links each release to releases.json#<version> because there is no page per release (src/web/standards.ts says so), and /releases is admin-only. A changelog worth reading is P8's first line.

Done when:

• [ ] GET /changelog (a new src/web/pages/changelog.ts) lists the last 30 Release <version>: … commits on the default branch, newest first. Each shows its version as a heading with an anchor #<version>, its date via time(), and each pull title as a link to the pull, parsed with the release-subject parser that #5807 lands. Every title is escaped.
• [ ] It is public, server-rendered, under 50 ms with 200 releases (one bounded git log read, cached per head oid), and names its Server-Timing phases.
• [ ] A test seeds three release commits and finds them in order with their pull links, and bun scripts/design-lint.ts passes.
• [ ] The release workflow and the chart are untouched.

Parked by the crew: the check failed ("GET /settings/tokens names its phases and answers within its budget") and the decider saw no point in another try (pull #6163 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

Parked by the crew: the check failed ("GET /settings/tokens names its phases and answers within its budget") and the decider saw no point in another try (pull #6915 closed).

Parked twice since a person last spoke here, so it is the planner's now. Every reason:

1. the check failed ("GET /settings/tokens names its phases and answers within its budget") and the decider saw no point in another try (pull #6163 closed)
2. the check failed ("GET /settings/tokens names its phases and answers within its budget") and the decider saw no point in another try (pull #6915 closed)

The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.

Replaced by #6917. Both pulls were refused only by test/settings-timing.test.ts. On #6915's head that test passes 3 of 3 runs when run alone, so the cause is a timing check that flakes on a loaded check machine, not the changelog. #6916 fixes that test, and #6917 waits for it and starts from 13b4e3cc.