Repository navigation
Increment 9: durable shipment exceptions and acknowledgement - #27
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Increment 9: shipment exceptions
Validation
Release constraints
Production INDEXER_ENABLED remains false; production inference/backfill is not enabled. No external notifications, paid resource upgrade, database reset or destructive downgrade. Old API artifacts cannot restart against the new strict schema head; use a compatible corrective release. See SHIPMENT_EXCEPTIONS.md and RELEASE_RUNBOOK.md.
Production rollout observation
Production schema migrated transactionally with unchanged business/journal fingerprints. PR merged normally as 7adb990 after all eight trusted checks passed. The exact-main CI/deployment gate remains in force.
A cold start of the previous API image at 08:18 UTC rejected the new schema head while the new image was waiting for main CI. The migration was applied too early for a sleeping free service. The compatible replacement restored liveness/readiness HTTP 200 at 08:27:55 UTC; no data loss or schema downgrade occurred. For future additive releases, stage the admitted replacement and coordinate migration immediately with rollout, accounting for cold starts and strict schema-head admission. Recovery and acceptance evidence follows below.
Final production acceptance