13  Regenerating this guide

This guide is generated content, held to the same discipline as every other manifest-derived surface:

• Each reference page states the exact tool version it was written against — a version-lock note naming the pin — so every page is bound to a tool version.
• When a package bump or a release moves a tool’s version, that tool’s page is regenerated in the same change; the repository’s coverage and provenance checks enforce this (a page whose recorded pin no longer matches the lock blocks merge). Upstream interface drift is answered by regeneration — never by hand-editing a generated page.
• Coverage invariant: every enabled tool has a complete page or an explicit pending stub with a stated reason — the check that proves it is the same CI gate, and tools never vanish silently from the reference.

The generation pipeline and enforcement gate are the tool-section lanes of this window (the coverage page tracks their status); per-release and per-bump regen obligations are ledgered on the standing upkeep issue.