refactor(2meet-data-optimizer-hivepress-addon): leave HivePress queries to the post router

- Do not bind optimize_query / optimize_search on hivepress/v1/models/{listing,vendor}/{query,search} while core's TMDO_Post_Query_Router is active: core now routes HivePress searches (filters and _sort) to the entity flat tables, and two routers would claim the same clauses
- Version 0.2.0 (released with core 1.1.0); CHANGELOG
- Verify: composer test (144, +2 binding tests); integration 49; dev36 fe.sh 9 URLs ids == native (except known flat drift)
- PR: PR-063

CHANGELOG.md

@@ -9,6 +9,20 @@ Versioning follows [Semantic Versioning](https://semver.org/).
 
 ## [Unreleased]
 
+---
+
+## [0.2.0] — 2026-09-26
+
+Released with 2meet-data-optimizer 1.1.0 (hardening 2.1, search-index mode).
+
+### Changed
+
+- HivePress model query / search hooks (`optimize_query`, `optimize_search`)
+  are no longer bound while core's post router is active
+  (`TMDO_Post_Query_Router::is_router_active()`): core routes HivePress
+  searches, including `_sort`, to the entity flat tables, and two routers
+  would claim the same clauses.
+
 ### Added
 
 - `tests/integration/`：bootstrap（複用核心的 integration bootstrap，連真實