`/release-notes` should indicate which version is current stable (per `/doctor`)

/doctor distinguishes a "stable" version from the newest version on npm. /release-notes does not — it lists every version sequentially with no marker for which one /doctor would currently recommend.

Result: users reading /release-notes have no signal about update safety and tend to upgrade on every release, even when stable is significantly behind.

Concrete example from today (2026-05-07): /doctor reports stable = 2.1.119, latest = 2.1.132 — a 12-version gap. Nothing in /release-notes between 119 and 132 indicates this. Several intermediate releases contain regressions that were only fixed in 132 (e.g., the --resume emoji-surrogate corruption fix in 132 implies a real bug in 120–131).

Suggested fix: mark the current stable version in /release-notes output, or visually separate "stable and below" from "newer than stable." Aligning the two surfaces would let users make informed cadence decisions.