Confirm the WordPress batch before it writes
Dry Run turns the approved page plan into a reviewable manifest. It shows the exact Pages and actions without sending a content mutation to WordPress.
Last updated
Create, Update and Skip
Each page receives one action from its current Gate decision and saved WordPress identity.
- Create — no WordPress ID is bound yet.
- Update — the same page already has a WordPress ID and is eligible for a Draft update.
- Skip — the page cannot or should not move in this batch, including a published page that has not been rolled back.
What the manifest records
The manifest keeps the target path, mapped fields, expected content hash, parent dependency, Destination identity and current Gate contract together.
- Changing source data, template version, page decisions or Destination identity invalidates the old confirmation.
- The manifest is limited to 8 MiB and stored in chunks.
- Parent Pages are ordered before their children.
Dry Run does not verify remote content
Dry Run uses saved WordPress identity and the current plan; it does not fetch every remote Page. Use Verify to discover content or status drift on WordPress.
- A planned URL is not the remote identity.
- A remote edit can exist even when Dry Run still shows Skip.
- No WordPress content is created or updated until Create / Update Drafts is confirmed.
Next action
Use the rule reference when a page needs a decision, or continue through the Docs in order.