CMS publishing
Connect a publishing surface, preserve a snapshot, verify the public result, and roll back through Orbitr.
Connect the real publishing surface
Use the integration flow for the site platform. For repository-backed sites, connect the repository that actually serves the selected domain. For a CMS, select the site or store returned by the provider.
Capability discovery
Orbitr determines whether it can read content, create a snapshot, publish the requested change, and verify the public URL. A connected integration does not mean every task shape is supported.
Publishing path
Approved writes pass through Orbitr's publishing service or snapshot-instrumented adapter. The worker records the provider operation, changed resource, and verification result.
Partial and failed publishes
If a provider accepts only part of a change, times out, or returns an ambiguous result, Orbitr should not present the task as publicly verified. Review the task transcript and provider operation before retrying.
Retry and idempotency
Retry from the task when the app offers it. Do not create a duplicate task to retry the same provider mutation. The existing task and operation identity are used to prevent duplicate writes.
Rollback
Open the completed task or rollback history, select the original operation, and request rollback. Then inspect the customer-visible URL to confirm the restoration.