release-notes(next): fit app highlights to the What's New limits
The nightly What's New digest is built from release-notes/next/highlights/*.md, and scripts/whats-new/digest.py drops every file that fails validate.py. On feat-cmux-next, 70 of the 83 files failed: bodies over 240 characters or two sentences, titles over 60, no try-it action or docs link, or internal names such as cmux-tui. So most highlights never reached What's New. Each failure only shows as a stderr line in the nightly job.
This PR rewrites the app highlights (43 files) so each one passes, and keeps them user-facing. Every file now sets category: explicitly. Each action: id was checked against the CmuxNextActions catalogs; the rest link a cmux.com/docs page. Bogus values such as action: docs | plans/... were replaced. File names (the entry ids) are unchanged. claude-through-coderouter already passed, but its action pointed at a repo path, so it now links the CodeRouter docs.
Evidence
Running digest.parse and digest.entry_problems on every file in the directory:
- on this branch, 0 of these 43 files fail;
- once this PR and its sibling (the browser highlights, #21716) are both in, 0 of 83 fail.
No app build: only Markdown changes.
Changelog
none
🤖 Generated with Claude Code
Summary by cubic
Rewrites the app highlights under release-notes/next/highlights/ so the nightly What's New digest stops dropping them. On feat-cmux-next, 70 of 83 files failed validation — bodies over the limits, internal names like cmux-tui, bogus actions — so most notes never reached What's New.
- Every file now has an explicit
category:, and eachaction:id was checked against the action catalogs or links a cmux.com/docs page. Two dead links were swapped for live actions or docs pages, and the profile-menu note now lists what the button opens. - Content stays user-facing and file names are unchanged; once the sibling browser-highlights PR lands, all 83 files validate.