Any change to docs/0*.md must be followed by a rebuild of the docs vault (tools/example-vaults/build.py, publisher key only in the sb_publisher_data Docker volume on the maintainer's machine) before the next tag, or the vault-freshness job fails the release. This is correct but undocumented for contributors, who see a red release gate with no explanation.
Done means: docs/internal/ has a page explaining the gate and the rebuild, CONTRIBUTING.md links it from the docs section, and a CI check on pull requests that touch docs/0*.md posts a comment saying the vault rebuild will be required (no secrets needed).
Any change to
docs/0*.mdmust be followed by a rebuild of the docs vault (tools/example-vaults/build.py, publisher key only in thesb_publisher_dataDocker volume on the maintainer's machine) before the next tag, or thevault-freshnessjob fails the release. This is correct but undocumented for contributors, who see a red release gate with no explanation.Done means:
docs/internal/has a page explaining the gate and the rebuild, CONTRIBUTING.md links it from the docs section, and a CI check on pull requests that touchdocs/0*.mdposts a comment saying the vault rebuild will be required (no secrets needed).