release: 3.3.0 → 3.3.1 — drop "WP" prefix, plugin is now just "Logbook"

David's call after a short discussion about WordPress.org marketplace
considerations. WP.org's trademark policy historically discourages
plugins implying official endorsement via a "WP" prefix and has been
known to request rename during submission review. Dropping it now
makes the name cleaner AND sidesteps that future hurdle if/when the
plugin lands on the marketplace.

CHANGES
All user-facing brand mentions: WP Logbook → Logbook across:
- Plugin header (Plugin Name + docblock)
- Admin menu top-level
- Admin sidebar submenu label still "My Log" (already prefix-free)
- Admin bar count menu
- Dashboard widget title
- Settings page H1
- Main page H1
- About page intro card + "What Logbook does" card heading
- Email feedback subject + body intro
- Legacy feedback.php subject lines
- error_log() prefix [WP Logbook] → [Logbook]
- Updater panel description text
- styles.php docblock

VERSION
- wp-notes.php header Version: 3.3.0 → 3.3.1
- WP_NOTES_VERSION constant: 3.3.0 → 3.3.1
- About page version-history card gets new top entry for v3.3.1
  with green "latest" pill; v3.3.0 demoted to previous entry
- CHANGELOG header line tracks the full naming lineage now:
  A-WP-Notes (≤v3.1.0) → WP Logbook (v3.2.0-v3.3.0) → Logbook
  (v3.3.1+)

NOTABLY NOT CHANGED
- Historical CHANGELOG entries for v3.2.0 still say "WP Logbook" —
  that was the correct name at the time, rewriting would be
  revisionist.
- Same zero-migration commitment: internal function names,
  constants, DB option keys, user_meta keys, file paths, plugin
  slug 'wp-notes', and text domain 'a-wp-notes' all unchanged.
- Pure user-facing string change. No data migration, no behaviour
  change. Existing installs see "Logbook" appear on next page
  refresh.

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

CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-All notable changes to **WP Logbook** (formerly **A-WP-Notes** through v3.1.0) are documented here.
+All notable changes to **Logbook** (formerly **A-WP-Notes** through v3.1.0, then **WP Logbook** in v3.2.0–v3.3.0) are documented here.
 Format: [Keep a Changelog 1.1.0](https://keepachangelog.com/en/1.1.0/) — versioning: [SemVer](https://semver.org/).
 
 ---
@@ -9,6 +9,40 @@ Format: [Keep a Changelog 1.1.0](https://keepachangelog.com/en/1.1.0/) — versi
 
 ---
 
+## [3.3.1] — 2026-05-25
+
+**Naming: dropped the `WP` prefix. The plugin is now just `Logbook`.**
+
+David's call after a short discussion about WordPress.org marketplace
+considerations — WP.org's trademark policy historically discourages
+plugins implying official endorsement via a `WP` prefix and has been
+known to request a rename during submission review. Dropping it now
+makes the name cleaner *and* sidesteps that future hurdle if/when
+the plugin lands on the marketplace.
+
+### Changed
+- All user-facing brand mentions: `WP Logbook` → `Logbook` across
+  plugin header, admin menu, admin bar, dashboard widget, settings
+  H1, main page H1, About page intro, About page card heading,
+  feedback email subjects/body, error_log prefix, updater panel
+  copy, and styles docblock.
+- About page version-history card gets a new top entry for v3.3.1
+  with the green "latest" pill; v3.3.0 demoted to the previous slot.
+- CHANGELOG header line updated to track the full naming lineage:
+  *A-WP-Notes (≤v3.1.0) → WP Logbook (v3.2.0–v3.3.0) → Logbook
+  (v3.3.1+)*.
+
+### Notably NOT changed
+- Historical CHANGELOG entries for v3.2.0 (the original "WP
+  Logbook" rebrand) still say "WP Logbook" — that was the correct
+  name at the time and rewriting it would be revisionist.
+- Same zero-migration commitment as the v3.2.0 rebrand: internal
+  function names, constants, DB option keys, user_meta keys, file
+  paths, plugin slug, and text domain all unchanged. Pure
+  user-facing string change.
+
+---
+
 ## [3.3.0] — 2026-05-25
 
 **New feature: self-hosted update checker.** WP Logbook is hosted on