EVULGARE

RELEASE DRIFT · BOUNDED PUBLIC OBSERVATION

DEPLOYMENT RECONCILIATION

The live deployment presents evidence from more than one release state. This page keeps observations, possible causes, recovery steps, and promotion boundaries separate.

ClassificationDEPLOYMENT_DRIFT_WITH_PUBLIC_INDEX_RECOVERY
Candidate2.0.0-rc.9-WIP
Automatic repairNO
Promotion effectNONE

Observed public state

Bounded public route observations
RouteHTTPStateQualification
/200OLDER_RELEASE_RETRIEVABLEThe public homepage responded but identified the older deployed release.
/healthz200DEPLOYMENT_DRIFTThe public health contract identifies an older deployed package than the RC9 candidate.
/simulations/200PUBLIC_INDEX_RECOVEREDThe public Simulation Explorer responded and rendered ten records during the current bounded observation.

Established facts

  • The live homepage, health endpoint, and Simulation Explorer are publicly retrievable.
  • The live health version does not match the RC9 package version.
  • The live database health probe reports reachable.
  • The live Simulation Explorer currently renders ten records.

Possible causes—not established

  • The RC9 package has not been deployed to the public host.
  • A stale cPanel APP_VERSION value may remain configured.
  • Passenger may still be serving the older application root or process.

Reconciliation sequence

  1. Back up .env, MySQL, and the current application root.
  2. Stop the cPanel Python application before replacing the root source tree.
  3. Extract one complete root-content candidate archive into /home/tomlzkelce/evulgare.com/.
  4. Keep startup file cpanel_app.py and entry point application; do not select passenger_wsgi.py.
  5. Install production and test requirements in the Python 3.13.14 virtual environment.
  6. Run Alembic upgrade, idempotent seed, full-stack diagnostics, and deterministic proofs.
  7. Restart Passenger and verify /healthz identifies the candidate release and reports configuration drift explicitly.
  8. Verify all canonical routes, assets, APIs, sitemap, robots, headers, cache, compression, and error handling.
  9. Roll back to the backed-up root and database if the candidate cannot pass the declared acceptance plan.
Open JSON recordOpen proofRelease Acceptance Center →

This bounded public observation establishes route availability and package-version drift only. It is not actual-host shell evidence, does not identify a single root cause, and cannot promote the release.

RECORD ff3344243499c9ac7e85de4f44c273323935257ee9c5c83e194a9d2553231c43 · PROOF 170fb71fdba42ae6bdcc8062385cb27e876fb1ae9a660190cbe2006f93d0b272