14 Commits

Author	SHA1	Message	Date
wpdev	13c4a1bcb9	chore(2meet-data-optimizer): 1.4.0 release notes and version ... - CHANGELOG / readme: PR-118, 122, 123, 127, 128, 129; upgrade step `wp tmdo post-status-sync` for the three-column copy index - Version 1.3.0 -> 1.4.0 (header, TMDO_VERSION, Stable tag) - PR: PR-124	2026-09-27 23:29:11 +08:00
wpdev	947e130386	docs(2meet-data-optimizer): add PR-116 and PR-117 to the 1.3.0 release notes ... - routed count cache: placeholder escape and count version group - PR: PR-101 (follow-up)	2026-09-27 17:58:07 +08:00
wpdev	1835c8776a	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
wpdev	0aec4b9bb6	docs(2meet-data-optimizer): add PR-106 to PR-110 to the 1.3.0 release notes ... - Changed: deferred table upgrades (PR-107), index lock on the primary (PR-108), cold cache flush by version (PR-110); Fixed: dropped tables in post status sync (PR-106) - Verify: composer test - PR: PR-101 (follow-up)	2026-09-27 17:12:54 +08:00
wpdev	303781e68b	docs(2meet-data-optimizer): 1.3.0 release notes ... - version 1.3.0; CHANGELOG and readme.txt for PR-090a, 091, 093 (verified, no change), 094–098, with the post-upgrade steps (first CLI / cron run adds the HivePress indexes; INFO lines need WP_DEBUG_LOG) - Verify: composer test (701) - PR: PR-101	2026-09-27 16:46:55 +08:00
wpdev	fab07655a2	docs(2meet-data-optimizer): 1.2.0 release notes ... - Bump to 1.2.0; CHANGELOG / readme entries for PR-066–080, with the post-upgrade ops commands - ADR-004 Release 2.2 design (scope, drift check / fix / router / resync) and CONTEXT.md drift paragraph - Verify: composer test, integration, phpcs 0 - PR: PR-086	2026-09-27 09:52:22 +08:00
wpdev	336664473b	fix(2meet-data-optimizer): keep registered fields out of the public listings REST endpoints ... - show_in_rest defaulted to true, so GET /wpdo/v1/listings and /listings/{id} (public by design) returned every registered hot / cold field to anonymous visitors — e.g. infocards tmeetic_ig_access_token_enc / _token_expiry / _user_id and WooCommerce _purchase_note (confirmed on dev36) - Fields are private unless registered with show_in_rest => true; protected (underscore) and credential-like keys (token, secret, password, api key, private key, credential, salt, nonce) are never exposed - Zone A list path no longer returns whole rows when nothing is public, and filters / orderby accept public columns only - Version 1.1.1; CHANGELOG, readme - Verify: unit 690 (+3), integration 525 (+3 private-column tests, RED on 1.1.0), live suite rest 2/2 (RED on 1.1.0), all live 49/49, phpcs 0, stan OK	2026-09-26 22:22:40 +08:00
wpdev	e8731c5119	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
wpdev	4fc59b757e	docs(2meet-data-optimizer): ADR-004 search-index mode and 1.1.0 release notes ... - ADR-004: HivePress / WooCommerce sites keep native meta as the source of truth and use flat tables as its search index; records the 2.1 write order, shadow_read, Promotion Guard, restore policy and router rules, with known limits - CONTEXT.md Entity Bridge, BENCHMARK-SCALE.md front-end and write-chain measurements (dev36), CHANGELOG and readme for 1.1.0; version 1.1.0 - composer phpcs uses phpcs.xml like CI (was --standard=WordPress with 2312 false errors) - Verify: composer phpcs (0); composer test; composer stan - PR: PR-064	2026-09-26 20:24:42 +08:00
wpdev	9fa84845be	fix: NinjaFirewall 相容性 — 保護 WAF 設定選項不被重導向 ... 評估 NinjaFirewall (WP Edition) 4.9 的相容性，結論是兩者可共存且 不需要開發 AddOn（該外掛全 codebase 零個 apply_filters('nfw_*') / do_action('nfw_*')，官方相容手段全在部署層）。但核心有一個隱患必須補。 TMDO_Options_Manager::register_settings_group() 以 pre_update_option_{key} 回傳 $old_value，讓選項不再落地 wp_options、改存專屬設定表。而 NinjaFirewall 的 Full WAF 走 auto_prepend_file，在 WordPress 載入前就以 原生 mysqli 直查 wp_options 取 nfw_options / nfw_rules。一旦這些鍵被 重導向，WAF 會讀不到設定而靜默停止防護 —— 不報錯、不寫 log。 nfw_rules 約 77KB 且 autoload=auto，正是 autoload 瘦身最誘人的目標， 因此這條路徑並非理論風險。 Added - PROTECTED_OPTIONS 常數與註冊守衛（nfw_options / nfw_rules / nfw_checked）， 命中時發出 _doing_it_wrong()。守衛置於方法開頭，全部鍵都被擋時提前返回， 不再建立空的設定表。 - tests/unit/OptionsManagerProtectedTest.php（4 tests / 10 assertions）， 鎖住「受保護鍵絕不會被掛上 pre_option_* / pre_update_option_* 攔截」。 - docs/WAF-COMPATIBILITY.md：模式差異、symlink 多租戶部署、WP SaaS 開站 流程與驗證清單、三條開發約束、實測風險矩陣。 Changed - Migration Wizard 輪詢 500ms → 2s，與四個 stress-test 面板一致。 原本 2 req/s 打同一 REST endpoint，易觸發 WAF rate-limit 與 bot 偵測。 autoload 最佳化不受影響：optimize_autoload() 只改 autoload 欄位、不刪列， 而 Full WAF 的 SELECT * 不看 autoload。 驗證：591 tests / 1166 assertions 通過，PHPCS 零違規，版本一致性 1.0.2。 dev30 於 Full WAF 與 WP WAF 兩種模式下實測，firewall log 中 TMDO 相關 攔截 0 筆。 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SdjXAU473eekjPBB8vPVRS	2026-08-15 20:38:09 +08:00
wpdev	9f587c39dc	fix: Schema Registry cold zone 註冊改為冪等（修復欄位重複累積） ... 三個 zone 索引的寫入方式並不一致： - hot -> hot_columns[post_type][column] 以 column 為 key，天生冪等 - warm -> warm_fields[meta_key] 以 meta_key 為 key，天生冪等 - cold -> cold_fields[post_type][] append，無去重 而 wpdo_register_fields 本來就會被觸發多次：核心自身於 plugins_loaded:4 觸發，主檔另有 late-bind safety net 於 :30 再觸發一次（讓在 :6 之後才 bootstrap 的 AddOn 趕上）；加上主外掛與其 AddOn 可能同時註冊同一批欄位。 實測影響：某站台 cold_fields['hp_vendor'] 累積到 35 筆但只有 9 個相異值， 每個 key 重複 4 次。修正後為 9 筆、零重複。 修法：cold 分支加入 in_array() 去重，使 register() 對同一 (post_type, meta_key) 成為冪等操作，與 hot / warm 既有行為一致。 驗證：核心單元測試 587 tests / 1156 assertions 全綠； wp wpdo doctor 於兩個站台皆 0 FAIL。 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-08 14:27:15 +08:00
wpdev	c5027b0fce	docs: CHANGELOG 補上階段 6/7 的 Admin、邊界與品質數據	2026-07-31 10:44:46 +08:00
wpdev	fbe41e2130	release: v1.0.0 — 取代 wp-data-optimizer v3.4.6 ... 版本 0.1.0 → 1.0.0（含 TMDO_VERSION / TWO_MEET_DATA_OPTIMIZER_VERSION / WP_DATA_OPTIMIZER_VERSION 與 unit bootstrap）。姊妹外掛只在診斷 CLI 顯示 WP_DATA_OPTIMIZER_VERSION、無版本比較，故報 1.0.0 安全。 wp-data-optimizer 退休：兩站台已停用，本機三個目錄改名為 *.retired （wp-data-optimizer / -v3.1.1 / _audit），git 歷史保留在 gitea。 CHANGELOG 記錄本次 backport 全貌與 4 項 ABI/行為變更。 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TbG1keQQ7XBa7qMQY16KCY	2026-07-31 09:45:22 +08:00
wpdev	d36bb954d1	chore: initial snapshot of 2meet-data-optimizer v0.1.0 ... Baseline before backporting wp-data-optimizer v3.0.1-v3.4.6. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TbG1keQQ7XBa7qMQY16KCY	2026-07-31 05:06:36 +08:00