chore(2meet-data-optimizer-hivepress-addon): 0.5.0 release notes and version

- CHANGELOG: PR-119 (sort indexes ending with post_id), PR-120 (a day's TTL)
- Version 0.4.0 -> 0.5.0 (header, TMDO_HIVEPRESS_VERSION)
- PR: PR-125

CHANGELOG.md

@@ -11,6 +11,26 @@ Versioning follows [Semantic Versioning](https://semver.org/).
 
 ---
 
+## [0.5.0] — 2026-09-28
+
+Released with 2meet-data-optimizer 1.4.0 (hardening 2.4).
+
+### Changed
+
+- `hp_listing_core` declares `(hp_price, post_id)`, `(hp_rating, post_id)` and
+  `(hp_hourly_rate, post_id)` indexes for the listing sorts HivePress offers:
+  with core 1.4.0 reading the ID tie-break from the flat `post_id`, a sort walks
+  the index and stops at the page instead of sorting every match (dev36, 1.3M
+  listings: price sort 14 s native → 0.37 s routed, hourly rate 11.5 s → 0.35 s,
+  rating 43 s → 0.51 s). Core 1.3.0 ignores indexes ending with `post_id`, so
+  nothing changes there. The pinned schema hash is unchanged. (PR-119)
+- Transient entries in a persistent object cache live a day (`MAX_CACHE_TTL`,
+  HivePress's own default) instead of a week; a timeout still outlives its value
+  by a minute. At a week dev36 kept 4.7M entries (1 GB) in the shared Redis and
+  pushed other sites' keys out. Entries already cached keep their week. (PR-120)
+
+---
+
 ## [0.4.0] — 2026-09-27
 
 Released with 2meet-data-optimizer 1.3.0 (hardening 2.3).