Documentation Quality Checks

Documentation changes must describe retained, runnable contracts and update their cross-references in the same change.

Run the documentation checks before review:

Static Transcript — not runnable

Audit pending; do not treat this block as a runnable example.

PYTHONPATH=src python ci/docs/check_code_examples.py
PYTHONPATH=src python ci/docs/check_api_coverage.py
sphinx-build -E -W -b html docs docs/_build/html
PYTHONPATH='' python ci/docs/run_documentation_examples.py --case installed-wheel-docs

The root-level ci/ directory owns executable continuous-integration checks: ci/docs/ contains documentation gates and the fresh installed-wheel reader journey, while tests/integration/local/ is the implementation-CI installed-wheel E2E gate for the local Golden Paths and feature matrix. Sphinx extensions live in docs/_ext/; one-off documentation maintenance tools live in docs/tools/. The live Gemini qualification remains an explicit local credential-and-billing gate and is not part of normal CI.

External link checking is intentionally not required PR CI because it depends on external services. Manually dispatch Documentation External Link Check on superpose-arc; it runs sphinx-build -E -W -b linkcheck strictly.

Reviewers verify that examples use supported commands, internal links resolve, and qualified Golden Path claims retain their stated limits. Linkcheck must have zero unexpected failures; its exact documented exceptions are limited to authoritative reader-facing sources that reject automated requests. Do not retain historical design-spec warnings, speculative command examples, or obsolete configuration mechanisms as user guidance.