docs(2meet-data-optimizer): add PR-057b and PR-062c to the 1.1.0 notes

- CHANGELOG / readme 1.1.0: flat-first routing for flat-sorted searches (tmdo_router_flat_first) and the all-NULL flat row left after deleting an entity - ADR-004: NULL sync never inserts a row; flat-first rule; front-end p50 from the R-2.1 acceptance run - BENCHMARK-SCALE: front-end table from the acceptance run (flat tables backfilled) and the join-order finding behind PR-062c - Verify: composer phpcs (0) - PR: PR-064b
2026-09-26 21:07:51 +08:00
parent dc9a8e9886
commit e8731c5119
4 changed files with 18 additions and 9 deletions
@@ -114,7 +114,8 @@ The Classifier tab analyzes your existing `wp_postmeta` data (access frequency,
 * dual_write / shadow_read: flat values follow native after every write (added_/updated_/deleted_ meta actions, delete_all, key change by meta_id)
 * Arrays in text fields are stored serialized, never "Array"; `wp tmdo repair-array-literals`
 * `wp tmdo bridge-restore-native`: overwrite in aeav_only, only-missing otherwise; no invented default rows
-* Post query router: routes only when the result equals native (OR, several post types, untyped numeric compares stay native), LIKE wildcards, one join per group, no GROUP BY, HivePress `_sort` / named / meta_value_num ordering, WordPress split query kept
+* Post query router: routes only when the result equals native (OR, several post types, untyped numeric compares stay native), LIKE wildcards, one join per group, no GROUP BY, HivePress `_sort` / named / meta_value_num ordering, WordPress split query kept, flat-sorted searches driven from the flat table (filter `tmdo_router_flat_first`)
+* Deleting an entity no longer leaves an all-NULL flat row behind
 * Zone tables that were never created are never queried

 = 1.0.0 =