release-notes(next): fit browser 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 browser highlights (28 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.
Evidence
Running digest.parse and digest.entry_problems on every file in the directory:
- on this branch, 0 of these 28 files fail;
- once this PR and its sibling (the app highlights, #21717) are both in, 0 of 83 fail.
No app build: only Markdown changes.
Changelog
none
🤖 Generated with Claude Code