2meet-data-optimizer

Files

T

wpdev 9d1a7c5591 feat(2meet-data-optimizer): throttle shadow_read diffs per key and promote on clean drift checks

- The shadow diff logger records at most 20 rows per entity type + key per hour across all objects, on top of the existing per-object 5-minute window: a key stale on every object (WooCommerce total_sales, written by direct SQL) no longer logs a row per product read.
- The auto-promoter's third condition is now TMDO_Drift_Check::clean_since(): every backfillable group of the entity checked within 2 days (sampled or full) with no drift; no record, no promotion. The shadow diff count no longer gates it (the filter's 4th argument is passed as 0). The Promotion Guard still refuses HivePress / WooCommerce sites.
- Reason classification was dropped (decision 2026-09-27): it needs a schema change and drift-check already reports miss / diff / extra per key.
- Verify: ShadowDiffThrottleTest, AutoPromoterDriftTest (RED before); dev36 simulated user shadow_read: clean_since yes, promotion still refused by the guard, mode unchanged.
- PR: PR-075

2026-09-27 00:48:18 +08:00

class-tmdo-audit-logger.php

refactor: 全部 128 個生產檔加入 declare(strict_types=1)（PR-H）

2026-07-31 06:13:33 +08:00

class-tmdo-auto-promoter.php

feat(2meet-data-optimizer): throttle shadow_read diffs per key and promote on clean drift checks

2026-09-27 00:48:18 +08:00

class-tmdo-cache-orchestrator.php

refactor: 全部 128 個生產檔加入 declare(strict_types=1)（PR-H）

2026-07-31 06:13:33 +08:00

class-tmdo-conflict-detector.php

refactor: 全部 128 個生產檔加入 declare(strict_types=1)（PR-H）