Managed documents and routes

Each supported surface uses a canonical WordPress document and exact route policy. SnapWeb Builder owns fetching, history, metadata, route commits, and the persistent shell. The adapter owns managed publication and mount or teardown coordination.

If no compatible page exists, the integration may create one. It never overwrites an existing compatible page and does not delete it during plugin removal.

Disabling a destination retires its native route and optional navigation entry without deleting content or settings. Re-enabling adopts the same document instead of creating duplicates.

Do not add manual route parsers or duplicate HTML fetching inside an add-on adapter.