v3.0.0 — [DATE NEEDED: the original notes didn't include a release date] BREAKING: - Custom field behavior changed. [SPECIFICS NEEDED: the original only said "some changes to how custom fields work" — state exactly what changed (schema, key format, API contract) and link a migration guide. The change was buried in a soft sentence; surface it here so integrators catch it in a scan.] Added: - New dashboard. [SPECIFICS NEEDED: which widgets, charts, or layout changed? "Completely reimagined" gives users nothing to look for.] Fixed: - [SPECIFICS NEEDED: "Squashed some pesky bugs" must be replaced with the specific bugs fixed, ideally with issue or ticket numbers. Pull the closed-issue list since v2.x from the tracker.] Performance: - [SPECIFICS NEEDED: "Lightning-fast performance improvements" must name which subsystems and by what factor — e.g. "Dashboard load reduced from 2.3s to 0.8s p50" or "/v1/customers response time reduced 40% under load."] Other: - [SPECIFICS NEEDED: "Various quality of life improvements" must be enumerated — keyboard shortcuts added, default filters changed, error messages clarified.] --- **Changes:** - Replaced the emoji launch announcement with a version-number + date header - Surfaced the buried breaking change ("some changes to how custom fields work") under a BREAKING heading - Flagged the missing release date and the missing migration guide - Flagged "Squashed pesky bugs," "Lightning-fast performance improvements," and "Various quality of life improvements" for specifics - Flagged the "reimagined dashboard" for what actually changed - Deleted the closing CTA cluster ("We hope you love this release...", "Don't forget to update your apps!") **Vague entries flagged:** - "Squashed some pesky bugs that were affecting some users" - "Lightning-fast performance improvements across the board" - "Various quality of life improvements throughout the app" - "All-new dashboard — completely reimagined" - Missing release date - Missing migration guide for the breaking change **Specificity verdict:** - Does each entry tell the user what specifically changed? No (most of the original was non-specific; flagged for engineering follow-up) - Are breaking changes clearly marked? Now yes (surfaced from a buried sentence) **Word count before → after:** 135 → 105 (flags inflate the count; the substantive content is ~25 words until engineering fills the gaps) **AI/template signal estimate before → after:** high → low