wpdev a26500206a feat(2meet-data-optimizer): backfill writes made while the Hook Bus was off ...

- When an entity goes from disabled to dual_write / shadow_read, or the Hook Bus flag is switched on, a single WP-Cron event (tmdo_drift_resync, one per entity, 60 s later) runs drift-check --fix for the entities that keep native meta, so values written while flat was bypassed land in flat. aeav_only is never touched.
- A full fix instead of the planned post_modified_gmt increment (decision 2026-09-27): meta-only writes such as WooCommerce's direct stock SQL do not bump post_modified. No wpdo_bridge_off_since.
- The resync hook is cleared on deactivate / uninstall (literal name: uninstall.php does not load TMDO_Drift_Check).
- Verify: DriftCheckTest resync cases (RED before); dev36 end to end with real WP-Cron: write while user disabled → miss 1 → bridge-mode user dual_write schedules tmdo_drift_resync [user] → run → drift 0.
- PR: PR-074

2026-09-27 00:41:43 +08:00

..

bench

perf(2meet-data-optimizer): route status and date ordering to entity tables

2026-09-26 01:41:07 +08:00

integration

feat(2meet-data-optimizer): backfill writes made while the Hook Bus was off

2026-09-27 00:41:43 +08:00

live

feat(2meet-data-optimizer): report flat-vs-native drift with wp tmdo drift-check

2026-09-26 23:56:23 +08:00

unit

feat(2meet-data-optimizer): set an entity bridge mode from the CLI under the Promotion Guard

2026-09-26 23:36:55 +08:00

bootstrap.php

fix(2meet-data-optimizer): keep searches native while a group is known to drift

2026-09-27 00:22:47 +08:00