docs: pin the Zensical toolchain exactly

Zensical is pre-1.0 and the build guards key on its rendering behavior
(autorefs classes, compact-index handling), so toolchain bumps should be
deliberate lockstep changes rather than incidental resolver upgrades. The
pinned versions are what the lockfile already resolved.

Author: maxisbey

pyproject.toml

@@ -82,20 +82,22 @@ docs = [
     # literate-nav) and llms.txt (formerly a hook) are generated by the
     # standalone scripts under scripts/docs/. See scripts/docs/build.sh.
     # 0.0.48 fixes relative/scoped cross-references for mkdocstrings-python,
-    # which the mkdocstrings config in mkdocs.yml relies on.
-    "zensical>=0.0.48",
+    # which the mkdocstrings config in mkdocs.yml relies on. The toolchain is
+    # pinned exactly: Zensical is pre-1.0 and the build guards key on its
+    # rendering behavior, so bumps should be deliberate.
+    "zensical==0.0.48",
     # Zensical's mkdocstrings compatibility layer targets the mkdocstrings 1.x /
     # mkdocstrings-python 2.0.5+ API (griffe 2 / griffelib); the older
     # mkdocstrings 0.30 / python 2.0.1 line renders API pages with an
     # unregistered-autorefs KeyError under Zensical.
-    "mkdocstrings>=1.0.4",
-    "mkdocstrings-python>=2.0.5",
+    "mkdocstrings==1.0.4",
+    "mkdocstrings-python==2.0.5",
     # scripts/docs/build_config.py and llms_txt.py read mkdocs.yml directly.
     "pyyaml>=6.0.2",
     # gen_ref_pages.py imports griffe directly. griffelib is not a typo: it is
     # griffe's successor distribution (same author) and still imports as
     # `griffe`; the old `griffe` distribution is the incompatible 1.x line.
-    "griffelib>=2.1.0",
+    "griffelib==2.1.0",
 ]
 codegen = ["datamodel-code-generator==0.57.0"]