/changelog lists the last 30 releases, finished from pull #7013's branch with a private forge repository kept off the page #7101

Replaces #6917. Pull #7013 (branch scout/6917-changelog-lists-the-last-30-releases-new) went three review rounds. Each round answered the last: §5 rows, the reader moved out of the page, parseReleaseSubject reused, and a terminal door. What is left is the third round's findings.

Start from that branch, rebased on main.

Done:

• [ ] High: a test makes FORGE_REPO private and asserts /changelog and the terminal's changelog screen both show the empty state, with no version id and no pull link. Removing the visibility check fails it.
• [ ] Medium: the git log grep is ^Release [0-9]+\.[0-9]+\.[0-9]+: , so every counted commit parses. A test with 31 releases shows exactly 30.
• [ ] Low: drop the dead empty-title branch (title: p.title) and the read! assertions (bind const repo = read?.repo once).
• [ ] Low: the terminal test asserts that Enter opened pull #2's screen, naming #2, not just that the screen changed.
• [ ] Everything else the branch does stays as reviewed.

Files: src/release/changelog.ts, test/changelog.test.ts

If the test finds the behaviour wrong, fix the action in the same pull and say so. If the check fails in a test this pull does not touch, name it in the pull rather than widening the change.

Before pushing: bun x tsc --noEmit and the new test.