docs(2meet-data-optimizer): add PR-111, PR-113 and PR-114 to the 1.3.0 release notes

- deferred-upgrade hardening from the acceptance reviews, notice() audit trail, known cold-cache version window - PR: PR-101 (follow-up)
2026-09-27 17:34:19 +08:00
parent 1d70d13f45
commit 1835c8776a
2 changed files with 12 additions and 2 deletions
@@ -117,6 +117,7 @@ The Classifier tab analyzes your existing `wp_postmeta` data (access frequency,
 * Existing flat tables are upgraded from WP-CLI or WP-Cron only; a group waiting for its upgrade uses native meta, then a drift fix rebuilds it
 * The index lock goes to the primary under read/write splitting; clearing the cold cache bumps a version instead of scanning the object cache group
 * Groups whose flat table was dropped no longer cause database errors on post status changes
+* Schema upgrades share one MySQL lock with index DDL; new or upgraded groups stay native until a drift fix has filled them; mode changes and snapshot deletions are always logged

 = 1.2.0 =
 * `wp tmdo drift-check <entity> [--group] [--sample] [--fix]`: reports flat-vs-native drift per key (miss / diff / extra) and rebuilds drifted flat rows from native; native meta is never written, and aeav_only sites are refused