Builds and atomically publishes a complete static documentation site.

Renderers only return bytes and logical assets. The exporter owns output paths, content hashing, local-link admission, finite budgets, staging, replacement and rollback. It never invokes a network client or external build process. Search adapters follow the same rule: they return local assets and an inert query contract rather than writing into the destination.

The completed tree includes rendered routes, redirects, a not-found page, content-hashed renderer assets, search data, a deterministic manifest, sitemap and robots files, and compact/full machine-readable documentation. Publication happens only after the in-memory output and staged filesystem tree pass validation. A failed replacement preserves the prior destination or reports the retained recovery path.