Skip to content

REL-07 rollout preflight

Server branch codex/release-rollout, base 7cc678ddf6726664ad410d60309871ce8d69db48.

The authorized release is gated on exact-commit CI, merge, the immutable production wrapper with ops/openbao-production-compose.yaml, matched Bridge installation and production acceptance. The previous production revision is 2fa913a521c01625406d2c80ff8249b2ff362d1c.

Preflight evidence on 2026-09-22:

  • Dedicated HeyAira SSH identity and runtime user verified over the private network. No Voyana credentials or services used.
  • Production backup health returned healthy=true, no reasons or alerts.
  • Installed deployment guard matches the tracked deployed script: SHA-256 34af658850864d9448502790f1acc44c5eccd54feb3dd973d8265c3232e8ba2c.
  • Full server PostgreSQL suite: 251 passed in 10.41s, zero skips. The additional test executes the production canary's actual remote bootstrap/cleanup code against a disposable database and proves a different project name is not deleted.
  • Generated MCP contract, documentation coverage, runtime validation and strict documentation build passed.
  • The final real-provider cancellation test exposed stale local active state; the Bridge cleanup guard was corrected before rollout. The repeat passed in 21.04s with server cancellation, nonzero CLI exit and inactive persisted session metadata. Rust tests, fmt/clippy and release build also passed.

The production canary creates one uniquely named synthetic project, checks public HTTPS and exact MCP identity/revision, runs the installed Rust Bridge's fixed synthetic provider, verifies one receipt without automatic task completion, and deletes only its exact synthetic project. No actual provider credentials or real project data are involved in that canary.

This report records preparation, not a deployment claim. The exact merged SHAs and actual rollout/canary output must be recorded in HeyAira task c0d93a1e-099f-48e5-b30e-d71b2bdba89c and its RESULT memory after execution.

Concurrent migration gate

A targeted preflight reproduced a rollout race: server and backup runtime both call apply_migrations during startup, and two concurrent calls applying the pending release migration produced one UniqueViolationError. Migration-table creation and the check/apply boundary now share a PostgreSQL transaction advisory lock. A four-caller real PostgreSQL regression proves one application and one version record. Failure or connection loss releases the lock through the transaction. No external deployment lock or configuration was changed.

Final local PostgreSQL run after the migration correction: 252 passed in 10.23s, zero skipped tests. Generated MCP contract and runtime validation remain green. Exact-head GitHub CI must be refreshed for this final commit.