release: 3.1.0 → 3.2.0 — rebrand A-WP-Notes → WP Logbook

The plugin's identity has shifted over the day's work — from a notes
pad to a work-logbook with time tracking, earnings, and a Wallet
tile on the v4 roadmap. "WP Notes" undersold what it had become and
collided semantically with WordPress's notes-as-memos connotation;
"WP Logbook" matches both the freelancer use case ("logbook for
clients") and the student use case ("logbook for teachers"), and
matches the exact word the plugin's own About-page intro had been
using all day.

USER-FACING CHANGES
- Plugin Name header: A-WP-Notes → WP Logbook
- Description header rewritten to reflect the work-logbook framing
- Admin menu top-level: WP Notes → WP Logbook
- Admin sidebar submenu: My Notes → My Log (matches new parent —
  reads cleanly as "WP Logbook → My Log")
- Admin bar count menu: WP Notes (N) → WP Logbook (N)
- Dashboard widget title: WP Notes → WP Logbook
- Settings page H1: WP Notes Settings → WP Logbook Settings
- Main page H1: WP Notes → WP Logbook
- About page: every brand mention updated; "Go to WP Notes →" CTA
  now reads "Go to My Log →" to match the new submenu
- About page version history now leads with v3.2.0 (this release)
  as latest, demotes v3.1.0 to the previous entry
- CPT menu_name label: WP Notes → WP Logbook (cosmetic only — CPT
  hidden from admin UI since the duplicate-form fix in v3.1.0)
- Migration notice text updated
- Email-feedback subject + body intro updated
- Legacy feedback.php subjects (WP Notes Feedback / Help Request)
  → WP Logbook variants
- error_log() prefix [WP Notes] → [WP Logbook]

ZERO-MIGRATION COMMITMENT — these stay unchanged
- All wp_notes_* function names
- All WP_NOTES_* constants
- All DB option keys (wp_notes, wp_done_notes, wp_notes_settings,
  wp_notes_migration_completed, wp_notes_version,
  wp_notes_dismissed_empty_active|completed)
- All user_meta keys
- Admin page slug 'wp-notes' (preserves bookmarks, admin-bar
  #new-note anchor, and the legacy ?page=wp-notes-create redirect)
- Plugin text domain 'a-wp-notes'
- File and directory names (wp-notes.php, inc/wp-notes-*.php,
  assets/wp-notes-banner.jpg)
- Gitea repo name (ranger/a-wp-notes-v3) — David can rename on the
  Gitea side separately if he wants

The rename is purely user-facing strings. Existing installs see the
new name appear after a plugin file refresh, with zero behaviour
change. No re-activation needed.

VERSION BUMP
- wp-notes.php header Version: 3.1.0 → 3.2.0
- WP_NOTES_VERSION constant: 3.1.0 → 3.2.0
- CHANGELOG: new [3.2.0] section that bundles the rename with the
  post-3.1.0 unreleased work (About-page rewrite, feedback form)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

CHANGELOG.md

@@ -1,12 +1,87 @@
 # Changelog
 
-All notable changes to **A-WP-Notes** are documented here.
+All notable changes to **WP Logbook** (formerly **A-WP-Notes** through v3.1.0) are documented here.
 Format: [Keep a Changelog 1.1.0](https://keepachangelog.com/en/1.1.0/) — versioning: [SemVer](https://semver.org/).
 
 ---
 
 ## [Unreleased]
 
+---
+
+## [3.2.0] — 2026-05-25
+
+**Plugin rebrand: `A-WP-Notes` → `WP Logbook`.** Bundles the rename
+with the About-page rewrite and the working Leave-Feedback form that
+were sitting in the post-3.1.0 unreleased block.
+
+The plugin's identity has shifted over the day's work — from a notes
+pad to a work-logbook with time tracking, earnings, and a Wallet
+tile on the v4 roadmap. "WP Notes" undersold what it had become and
+collided semantically with WordPress's *notes-as-memos* connotation;
+"WP Logbook" matches both the freelancer-proof-of-work use case
+("logbook for clients") and the student-evidence-of-work use case
+("logbook for teachers"), and matches the exact word the plugin's
+own About-page intro had been using all day.
+
+### Changed
+- **Plugin Name** header: `A-WP-Notes` → `WP Logbook`.
+- **Description** header rewritten from "A plugin to add your notes
+  to the WordPress dashboard with import/export functionality" to
+  *"A lightweight task & logbook plugin for WordPress. Log your
+  daily work, mark tasks done, and keep a tidy record inside the
+  dashboard. Perfect for freelancers showing clients what's been
+  delivered and students proving work to teachers."*
+- **Version bumped** v3.1.0 → v3.2.0 (header + `WP_NOTES_VERSION`
+  constant).
+- **Admin menu top-level** `WP Notes` → `WP Logbook`.
+- **Admin sidebar submenu** `My Notes` → `My Log` (matches the
+  new parent name; reads cleanly as "WP Logbook → My Log").
+- **Admin bar count menu** `WP Notes (N)` → `WP Logbook (N)`.
+- **Dashboard widget** title `WP Notes` → `WP Logbook`.
+- **Settings page H1** `WP Notes Settings` → `WP Logbook Settings`.
+- **Main page H1** `WP Notes` → `WP Logbook`.
+- **About page** every brand mention updated (intro card, "What WP
+  Logbook does" heading, "Go to My Log →" CTA on the side-by-side
+  intro that used to say "Go to WP Notes →").
+- **About page version history** now leads with v3.2.0 (this
+  release) as `latest` and demotes v3.1.0 to the previous entry.
+- **CPT `menu_name` label** `WP Notes` → `WP Logbook` (cosmetic
+  only; CPT is hidden from admin UI since the duplicate-form fix in
+  v3.1.0).
+- **Migration notice text** "WP Notes needs to migrate…" → "WP
+  Logbook needs to migrate…".
+- **Email-feedback subject** `[Site] WP Notes feedback from X` →
+  `[Site] WP Logbook feedback from X`. Body intro line same change.
+- **Legacy feedback.php subjects** (`WP Notes Feedback` /
+  `WP Notes Help Request`) → `WP Logbook Feedback` /
+  `WP Logbook Help Request`. These render only if the unused legacy
+  feedback file is ever required-in; brought along for hygiene.
+- **`error_log()` prefix** `[WP Notes]` → `[WP Logbook]`.
+
+### Notably NOT changed (zero-migration commitment)
+- **All internal function names** keep `wp_notes_*` prefix.
+- **All constants** keep `WP_NOTES_*` names.
+- **All DB option keys** (`wp_notes`, `wp_done_notes`,
+  `wp_notes_settings`, `wp_notes_migration_completed`,
+  `wp_notes_version`, `wp_notes_dismissed_empty_active|completed`)
+  stay as-is. **No data migration runs on upgrade.**
+- **All `user_meta` keys** stay as-is.
+- **Admin page slug** `wp-notes` stays — preserves bookmarks, the
+  admin-bar `#new-note` anchor, and the legacy
+  `?page=wp-notes-create` → `?page=wp-notes` redirect added in
+  v3.1.0.
+- **Plugin text domain** `a-wp-notes` stays — would otherwise
+  invalidate any future translation files.
+- **File and directory names** unchanged (`wp-notes.php`,
+  `inc/wp-notes-*.php`, `assets/wp-notes-banner.jpg`). The Gitea
+  repo `ranger/a-wp-notes-v3` is unchanged too — David can rename
+  it on the Gitea side separately if he wants.
+
+The rename is **purely user-facing strings**. Existing installs see
+the new name appear after a plugin file refresh, with zero behaviour
+change. No re-activation needed.
+
 ### Changed — Leave Feedback form (more options, multi-select, wired to email)
 The right-column "Leave Feedback" form on the About page has been
 expanded from two radio buttons to **seven checkboxes** (users can