The swiss army knife of lossless video/audio editing
Store release notes: write for customers, leave out internals
Claude51d98d9223de
diff --git a/AGENTS.md b/AGENTS.mdindex 34d5d748..e012b52f 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -22,6 +22,7 @@ Only the bundled FFmpeg version (`script/downloadFfmpeg.ts`) is supported. Don'tThe stores lag behind GitHub releases, so their "What's new" text must cover every version since the one currently live in that store. Ask which version that is (Mac App Store: App Store Connect; Microsoft Store: Partner Center → the product's current submission → Packages), then combine `versions/*.md` after it up to the version being released.+- Write for customers: lead with the most impactful new features and visible fixes. Leave out internals (dependency/FFmpeg upgrades, security fixes, refactors) and niche power-user details; they're covered by a final "Many other improvements and fixes". The longer since the last store release, the more of the interesting changes can be included.- Plain text, no Markdown, code formatting, issue references or links. Use plain-language feature names instead of internal action/variable names.- Leave out what doesn't apply to that store's build: items for other platforms (App Review rejects mentions of other platforms), GitHub-only builds, custom FFmpeg path (not in the Mac App Store build), update checks.- Microsoft Store: max 1500 characters. Mac App Store: max 4000 characters.