Skip to main content

Deployment Health Gate

Purpose

This page defines the permanent production-release gate for consequential Skyhawk.org changes.

Binding Release Sequence

  1. Define prerequisites and postconditions before modification.
  2. Back up the affected custom implementation.
  3. Apply one bounded change set.
  4. Lint and parse modified files.
  5. Rebuild Drupal caches where required.
  6. Prove required files, routes, libraries, services, database objects, and storage.
  7. Run an end-to-end production smoke test.
  8. Verify the actual affected user workflow.
  9. Promote the deciding evidence automatically to chatgpt-debug-latest.txt.
  10. Only then declare the change released.

Standard Health Surface

The permanent administrative health surface is /admin/skyhawk/system-status. It must report objective PASS/FAIL state for critical custom subsystems.

Current Upload Regression Gate

Before another Pixel upload test, all of the following must pass: observer JavaScript exists; controller exists; library is defined; upload form attaches the library; observer route resolves; observer endpoint persists a smoke event; observer JavaScript is proven delivered on the live Chatgpt 4 page.

Missing telemetry is evidence about telemetry first, never evidence about the uploader.