Project · Reconciliation · UI Testproject

Drift vs WordPress

Does the live site still match the plan? The locked creative objects (pages, menus, forms) are compared to the app's last deploy. Accept WordPress makes the current WordPress version the new baseline (non-destructive). Pages are never overwritten from the app — the Greenshift rendering is the value; they're only re-deployed when missing in WordPress. Menus rebuild from the app (re-paste); forms can be overwritten field-wise (JetFormBuilder actions and notifications survive).

↻ Re-check drift

Fleet management (MainWP)

Could not reach the MainWP Dashboard (Cannot reach the MainWP Dashboard (network error, DNS failure, or wrong URL). Check MAINWP_DASHBOARD_URL and that the Dashboard is online.) — re-check later.

MainWP ↗

⚠

Quality blocked — the clean room isn't ready yet.

The Quality tooling runs here on a frozen, verified environment, so all drift must be resolved before starting Quality.
Checks: Creative drift check failed: No WordPress connection (URL + token) on this project.; Plugin drift check failed: No WordPress connection (URL + token) on this project..

Couldn't check drift

No WordPress connection (URL + token) on this project.

Platform layer — plugins

The desired plugin set (stack + baseline) compared to what's installed and active on the site. Presence/active drift blocks the Quality clean-room gate; version is an advisory governance check against the Library's approved version. Resolution actions land in the next step.

Couldn't check plugins

No WordPress connection (URL + token) on this project.