workspace-quality-gate

Release readiness validation runs non-destructive checks across Codex Workspace and Workspace Hub to verify tests, lint, and build statuses. It executes deterministic scripts to surface failures without mutating existing code.

A non-destructive quality gate identifies release-readiness issues by applying validation checks to release candidate changes. It runs scripts like release-readiness.sh and doctor-agent-tooling.sh to report failures without modifying existing code.

Pre-release checks execute deterministic scripts under tools/scripts, including sync-codex-skills.sh, to validate compatibility across repos/workspace-hub. This process reports any test, lint, or build failures without altering existing code.

Yes, you can verify non-breaking changes by running the quality gate to validate agent tooling and documentation updates. It performs non-destructive checks to ensure tests, lint, and build statuses remain healthy across Codex Workspace.

No, the workspace quality gate performs non-destructive checks exclusively. It executes deterministic scripts to identify release-readiness issues and regressions, reporting failures without mutating existing code.

You need a quality gate because Codex Workspace and Workspace Hub release processes risk regressions. Running non-destructive checks validates release readiness by ensuring tests, lint, and build statuses are healthy before an official release.