Production, staging, and development environments
Select WordPress environments carefully and understand the limits of the clone and sync planner.
Identify the destination
The Toolkit’s environment view is intended to organize a site’s environments and their roles. Confirm the source and destination labels before planning a change. Production is the customer-facing environment; staging and development are for controlled validation. Names and availability are account-specific.
Clone and sync status
The interface and request routes include clone/sync planning and durable job/reservation concepts. This does not mean an operational executor is available: the clone/sync planner is not an operational executor. Do not promise that a submitted plan has copied files or data, and do not assume a queued or unresolved operation will self-heal. Conflicting work can require operator reconciliation.
Before a promotion
Confirm the target, take or verify a recovery point, review content/data implications, and check any domain or integration dependencies. Ask support to confirm execution and completion when the interface does not provide verified completion evidence. Never use production as a test destination.