ci-deploy-preflight

A pre-flight CI check validates runtime contracts by curling the actual endpoint with identical headers and credentials before deployment, emitting a precise error message naming the credential, HTTP status, and remediation required when violations occur.

Preventing silent runtime degradation from reaching production requires a CI gate that tests the endpoint, authentication shape, expected HTTP status, and minimum scope before deploy, surfacing actionable remediation messages when violations occur.

Yes, you can use GitHub Actions to check API endpoint authentication and status before deploy by inserting a pre-flight step that hits the runtime resource with the same credentials, failing with an error message when the HTTP status or scope is violated.

A pre-flight check for runtime contracts in CI is a validation step that pins down the endpoint, authentication shape, expected HTTP status, and minimum scope, curling the runtime resource to prevent silent degradation from reaching production.

Deployments silently degrade when runtime contracts are not enforced in CI because the endpoint, authentication, status, and scope are never validated against the actual resource before the production release occurs.

No specific dependencies are required to run a pre-flight curl validation in your workflow, as the skill operates without external dependencies to insert the CI gate that tests your runtime endpoint and credentials.