check-web

Validate the current state of the website sources. Argument: $ARGUMENTS (empty for the fast check, full to add the strict build).

Fast check (always)

Run from the repo root:

ovweb lint

(If ovweb is not installed: pip install -e "./publish-tool[validate]" first.)

It reports [check] file:line: message — hint lines at three severities. Act on them:

• error — CI fails on these. Fix every error in files this session touched; for errors in files you did not touch, fix them if the fix is unambiguous, otherwise list them for the user.
• warn — convention violations that do not block CI. Fix the ones caused by this session's edits; report pre-existing ones without fixing (they may be deliberate).
• info — janitorial; mention only if the user asked for a cleanup.

Never silence a finding by weakening the checker (publish-tool/src/ovweb/lint/) — the checker changes only when a convention itself changes, with the user's agreement. What each check enforces is documented in contributing/checks.md.

Full check (full argument)

After the fast check passes, also run what CI runs:

CI=false GOOGLE_ANALYTICS_KEY=G-XXXXXXXX mkdocs build --strict --site-dir /tmp/mkdocs-strict-validation
ovweb lint --site /tmp/mkdocs-strict-validation

• The build must end with zero WARNINGs — any WARNING is a failure to fix.
• Anchor INFO lines in the build log are expected noise (~110 pymdownx.tabbed false positives) — ovweb lint --site is the authoritative anchor check, since it resolves every fragment against the ids actually present in the built HTML.
• If mkdocs is not installed locally, use the Docker image instead: docker run --rm -v ${PWD}:/docs -e GOOGLE_ANALYTICS_KEY=G-XXXXXXXX squidfunk/mkdocs-material build --strict -d /tmp/site.

If redirect rules or publish-tool/ovweb.yaml were touched this session, also run ovweb redirects check. If any page was deleted or renamed this session, also run ovweb lint --against origin/main — every removed page must be claimed by a redirect rule.