Validate documentation changes

Start with the affected workflow, then check links and examples in the locked environment. Record what was executed and distinguish syntax checks, execution smokes and statistical qualification.

uv run --no-sync python scripts/check_docs.py

The checker covers ordinary inline local links, Markdown fragments and obsolete generated-documentation directives. It does not check external websites, interpret prose or prove that API examples run. Review incoming links from the README and repository modelling skill when deleting a page.

Execute self-contained examples and applicable continuation blocks against the same objects. Test YAML by constructing the graph with --dry-run, then use a small explicit non-provider smoke when the output contract changed. A short fit can verify persistence and stage execution while failing convergence diagnostics.

For source changes, follow CONTRIBUTING.md and run the relevant package checks. A documentation-only rewrite does not require a package release. Keep logs and temporary models in sandbox/, not in the user guide.