Release Gate
Forge uses executable checks to keep public docs, SDK behavior, and deployment claims aligned.
Local tools
| Tool | Purpose |
|---|---|
tools/release_gate.py |
Aggregated release checks for production readiness. |
tools/production_audit.py |
Scans for non-production markers and unsafe release posture. |
tools/test_release_gate.py |
Unit coverage for release-gate behavior. |
tools/test_openagent_docs_portal.py |
Navigation and page-existence checks for OpenAgent docs. |
tools/test_forge_site_and_docs.py |
Forge website and docs regression checks. |
What the gate should protect
The gate should catch:
- navigation entries pointing at missing pages
- docs that outrun shipped behavior
- release-blocking TODO or placeholder markers
- missing conformance vectors
- provider capability drift
- unsafe security posture
- generated site regressions
- website links that route users to the wrong domain
Before deployment
Run the narrow checks for your change, then run the package builds that prove the deployable artifacts can be produced.
For the public Forge site and docs:
python3 -m unittest tools.test_forge_site_and_docs
python3 docs-site/build.py --docs docs-site --brand forge --out /tmp/forge-docs-dist
npm --prefix website run build
Cluster rollout should happen only after these checks pass.