Development
The generated notice above identifies the exact code revision used for this manual and API build. Documentation changes in this preview are explicitly identified when they are still uncommitted.
{{REVISION_NOTICE}}
The checked documentation code basis is 9552d2bde73b11551027fb829b17d7b4813253d9. At the time of this validation, upstream main included merge commit 0bbf4720af92a392bfeedf801096b3fd4917e42c, whose source tree was identical to that documented basis. The revision notice is generated at build time from the checked-out Git revision. It distinguishes the code revision from local manual changes; a commit is required before a published revision can reproduce those authored pages.
For the downloadable manual and API, checkout instructions use the exact generated source revision: git checkout {{BASE_REVISION}}. The version field shown in generated API pages comes from project(VERSION ...) in CMake and currently reads 0.1.0; it is a project version, not the source commit.
The current JSON interface is strict and is distinct from the original Fortran YSpec's line-counted parameter files. Other documented differences include controlled integration steps; boundary-side behavior; responses in fluid and core receiver regions; corrections using receiver gravity and the potential-flux term; and allowed degrees above 1827. Read the source revision's Differences from the Fortran YSpec section before comparing old workflows.
Historical DSpecM1D comparison material attributes YSpecpp to 84be5a6cbe442324c164e5193a66b0911fca5860. That historical comparison does not describe this later code basis and is not replaced by current test coverage. Preserve its attribution when updating comparison material.
Before documenting a changed API or parser behavior, compare the proposed source revision with the documented code tree, inspect the public headers/parser/examples/build settings, and rerun affected examples and tests. Update the smallest relevant page and fixture, rebuild the strict API from that same source, review compatibility notes, then approve and record a new source revision. See the maintainer procedure. The manual does not automatically follow a moving branch.