Preserve legacy thank-you markup, Vue bindings, scripts and add-on callbacks by default. Sites may explicitly opt into the additive provisioning enhancement; existing checkouts do not require add-on upgrades or new nonce arguments. In opt-in mode, keep one stable, owner-scoped screen while background provisioning continues. Update site readiness and links in place without document reloads or fabricated progress percentages. The enhanced screen stays on thank-you by default; integrations may supply a validated ready-site handoff. A polite live status, bounded waiting, keyboard-accessible recovery and sign-in guidance must remain usable on narrow viewports. Recovery checks the saved order, never repurchases it. Do not globally dequeue other widgets' assets: completion uses thank-you scripts instead of dispatching checkout-form dependencies.
The default checkout pricing-table list presents each selectable plan with a visible native radio control. The focused control keeps the existing card focus ring, while the selected control retains the blue card border. Contact-us cards use a non-submitting button so they remain keyboard operable without becoming a checkout selection. After a plan refresh, focus returns to the selected radio only when the visitor has not moved it elsewhere during the request.
Page choices use asynchronous search, never a dropdown preloaded with every page. The block inspector uses WordPress's keyboard-accessible combobox; shortcode and customization forms reuse the existing Selectize model selector. Keep results bounded to at most 20 published pages on the current site, debounce typing, and hydrate only the saved selection. Preserve the zero-valued Current Page/Default choice and existing saved IDs, including when a lookup fails. Show search errors without silently changing the selection. Controls follow their container width in both the narrow editor sidebar and mobile forms; do not add fixed widths. Editor-only settings are resolved on the editor-assets hook, not on unrelated admin requests. See the block-editor widget manager and Base_Element page-search field helper for the shared implementation.
DNS lookup without a configured integration is a normal read-only state, not a warning. Use a neutral gray information strip with a secondary configuration link; reserve warning/error styling for actual failures.
Show returned NS records in a separate nameserver summary, using escaped text and hiding the entire summary when none are returned. Nameservers may help identify the DNS host, but do not infer a provider name or imply an integration is enabled.
Keep the existing stacked widget layout on desktop and mobile. List nameservers on separate lines and allow long hostnames to wrap without truncation. Hide the summary during loading or lookup errors; preserve the existing record table and provider-managed editing controls.
Show the API v2 access-token checklist on the credentials step using the same configuration-instructions component as BigScoots, not a separate instructions screen. Explain token permissions, legacy-key migration, SSL contact email, resource IDs, extra domains and wildcard limitations beside the relevant form. Reuse the existing stacked, wrapping layout on desktop and mobile; no new styles or wizard steps are needed. Keep the access token in a password field.