wpdev 1b21ee9add fix(2meet-data-optimizer): drift checks only where native meta is authoritative ...

- In aeav_only flat is the source of truth and native meta is stale by design, so drift there means nothing: drift-check --fix refuses (it would overwrite current flat values with stale native ones), the daily sample skips such entities, and the router keeps routing a drifting group instead of falling back to stale native meta.
- Found before PR-074 on hardening/2.2 (PR-071–073 not released; dev21 still runs aeav_only).
- Verify: DriftCheckTest / PostQueryRouterDriftTest aeav_only cases (RED before); dev36 fix() in a simulated aeav_only refused.
- PR: PR-073b

2026-09-27 00:34:03 +08:00

..

class-tmdo-cli-member.php

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

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

class-tmdo-cli-post.php

refactor(2meet-data-optimizer): list post groups for backfill from the registry

2026-09-26 22:54:27 +08:00

class-tmdo-cli-term-comment.php

refactor(2meet-data-optimizer): resolve post_type/group/table mappings through the registry

2026-09-26 00:22:20 +08:00

class-tmdo-cli-v2.php

fix(2meet-data-optimizer): drift checks only where native meta is authoritative

2026-09-27 00:34:03 +08:00

class-tmdo-cli.php

refactor(2meet-data-optimizer): remove HPCT legacy from core

2026-09-26 00:14:18 +08:00