Local preview

From a clean checkout with Python 3 and Doxygen 1.9.8 installed, run the standalone manual build and strict link checker. They do not configure CMake or fetch solver dependencies:

python3 docs/tools/build_docs.py --output build/guide-docs
python3 docs/tools/check_docs.py build/guide-docs/site
python3 -m http.server 8000 --directory build/guide-docs/site

Open http://localhost:8000/. The builder only replaces an output directory carrying its exact ownership marker; choose a dedicated ignored path under build/. The notice identifies the current source SHA and says when the manual working tree includes uncommitted changes.

Coverage inventory

WorkflowSource and APIEvidence and limit
First seismogramapp/yspec.cpp, YSpec/Input.hpp, YSpec/Run.hppSmall first-run JSON + checked finite text trace and Matplotlib plot; workflow illustration, not convergence evidence
Snapshot gridapp/yspec-snapshot.cpp, YSpec/Snapshots.hpp, YSpec/Run.hppSmall tutorial fixture with reduced dimensions; canonical examples/snapshot.json remains unchanged
High-level library tracesexamples/library.cpp, YSpec/Synthetics.hpp, YSpec/Seismograms.hppExisting compiled example and CTest case; its scalar result is revision/compiler dependent
Input validationsrc/InputSections.cpp, tests/TestInput.cpp, YSpec/Input.hppDefaults, groups, profiles, instruments, forces and invalid fields; schemas are not duplicated here
Strain tracesYSpec/Synthetics.hpp, YSpec/Seismograms.hppExisting CTest checks strain/displacement differences and reciprocity; no CLI or JSON interface
Radial kernelsYSpec/Kernels.hpp, src/Kernels.cpp, tests/TestKernels.cppExisting finite-difference checks by gravity treatment; radial, isotropy-constrained perturbations only
Fortran referencestests/regression/, tests/fortran/Saved comparisons for listed cases; regeneration uses an external Fortran checkout and is not docs CI

For the wider coverage list, start from the existing README test summary and inspect the named test files at the same source revision.

Adding or revising content

  1. Choose and record the source commit; inspect the parser, public headers, examples, CMake and existing checks that affect the claim.
  2. Edit the smallest relevant guide and its fixture/check. Keep generated API pages out of source control and preserve scientific provenance.
  3. Run the documented fixture and library example under the bounded thread count, run affected tests and the existing Release/serial routes, then build and strictly check the manual/API.
  4. Review desktop and mobile pages, download links, symbol anchors and the generated source notice. Update release notes when behavior or compatibility changes.
  5. Record each logical change and verification in implementation_status.md; approval and a source commit precede any website pin update.