docs(2meet-data-optimizer-hivepress-addon): 0.3.0 release notes

- Bump to 0.3.0; CHANGELOG entry for PR-081–084, with the post-upgrade cleanup-hp-transients step
- Verify: composer test, integration
- PR: PR-087

2meet-data-optimizer-hivepress-addon.php

@@ -3,7 +3,7 @@
  * Plugin Name:       2meet Data Optimizer — Hivepress AddOn
  * Plugin URI:        https://2meet.io/2meet-data-optimizer/hivepress
  * Description:       HivePress + 12 擴充整合：13 adapter (core/reviews/bookings/messages/memberships/requests/favorites/statistics/tags/seo/social-links/blocks/marketplace) + 7 HPCT interceptor + 5 query interceptor + admin tab + CLI namespace
- * Version:           0.2.0
+ * Version:           0.3.0
  * Requires at least: 6.0
  * Tested up to:      6.9.4
  * Requires PHP:      8.1
@@ -24,7 +24,7 @@ if ( ! defined( 'ABSPATH' ) ) {
 	exit;
 }
 
-define( 'TMDO_HIVEPRESS_VERSION', '0.2.0' );
+define( 'TMDO_HIVEPRESS_VERSION', '0.3.0' );
 define( 'TMDO_HIVEPRESS_PATH', plugin_dir_path( __FILE__ ) );
 define( 'TMDO_HIVEPRESS_URL', plugin_dir_url( __FILE__ ) );
 define( 'TMDO_HIVEPRESS_FILE', __FILE__ );

CHANGELOG.md

@@ -11,6 +11,39 @@ Versioning follows [Semantic Versioning](https://semver.org/).
 
 ---
 
+## [0.3.0] — 2026-09-27
+
+Released with 2meet-data-optimizer 1.2.0 (hardening 2.2).
+
+### Changed
+
+- With a persistent object cache (`wp_using_ext_object_cache()`), the
+  transient filter keeps HivePress's per-post transient pairs in the
+  `tmdo_hp_transient` cache group instead of `wp_options`, where they piled
+  up (1.15 M pairs on dev36). Reads fall back to `wp_options` for values
+  written before; deletes clear both. Without an object cache nothing changes.
+  After upgrading, remove the rows left behind with core's
+  `wp tmdo cleanup-hp-transients --options --confirm`.
+
+### Fixed
+
+- The detected / bound status cells of the HivePress admin table go through
+  `esc_html()` (2.1 audit); output unchanged.
+
+### Docs
+
+- `docs/REGISTERED-KEYS.md`: the six registered keys HivePress never writes
+  as meta, because its models alias them to core columns (listing
+  `hp_vendor` → `post_parent`, `hp_status` → `post_status`; request
+  `hp_status`, `hp_user`; vendor `hp_user`; review `hp_rating` →
+  `comment_karma`). The schema stays; their flat columns are always NULL.
+- `docs/HIVEPRESS-COVERAGE.md`: dev36 inventory of the meta each HivePress
+  post type holds, where the extensions keep their data and the query shapes
+  the front end produces. Attribute auto-registration is not needed now:
+  every meta key HivePress queries is registered.
+
+---
+
 ## [0.2.0] — 2026-09-26
 
 Released with 2meet-data-optimizer 1.1.0 (hardening 2.1, search-index mode).