docs: trim changelog to user-facing items and clarify release notes guidelines

CHANGELOG.md

@@ -2,14 +2,11 @@
 
 ## 0.1.15 - 2026-02-19
 ### Improved
-- Improved website release visibility with a public changelog page plus cleaner GitHub navigation and changelog heading presentation.
-- Improved website onboarding by redesigning the homepage get-started flow into a clearer two-step experience.
 - Improved app draft/new-agent UX by simplifying working directory placeholder and empty-state messaging and enabling drag interactions in previously unhandled draft areas on Tauri.
-- Improved sidebar structure by renaming `Sidebar` to `LeftSidebar` and hiding empty filter groups.
 
 ### Fixed
 - Fixed archived-agent navigation by redirecting archived agent routes to draft.
-- Fixed duplicate `/rewind` user-message behavior and added an end-to-end regression test.
+- Fixed duplicate `/rewind` user-message behavior.
 
 ### CI / Docs
 - Updated release automation to sync GitHub release notes from `CHANGELOG.md`.

CLAUDE.md

@@ -195,7 +195,10 @@ Notes:
 - The website Mac download CTA URL is derived from `packages/website/package.json` version at build time, so no manual update is required after release.
 
 Release completion checklist:
-- Manually update CHANGELOG.md with release notes, between current release vs previous one, use Git commands to figure out what changed
+- Manually update CHANGELOG.md with release notes, between current release vs previous one, use Git commands to figure out what changed. The notes are user-facing:
+    - Ask yourself, what do Paseo users want to know about?
+    - Include: New features, bug fixes
+    - Don't include: Refactors or code changes that are not noticeable by users
 - `npm run release:patch` completes successfully.
 - GitHub `Desktop Release` workflow for the new `v*` tag is green.
 - GitHub `Android APK Release` workflow for the same tag is green.