Repository navigation
test(v0.49): retain two-case backlog progress and drain latency evidence - #19
Merged
grove merged 3 commits intoOct 21, 2026
Conversation
grove
marked this pull request as ready for review
October 21, 2026 21:48
This was referenced Oct 21, 2026
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.
CI repair — 2026-10-21
The initial exact-head pinned producer run #39673424319 completed the original full joint-stack audit, one-case outage test and new two-case managed-outage test successfully. The two-case test printed its final PASS after asserting immutable vectors, monotone case-key progress and no replay. The step then failed in the shell wrapper only:
unexpected EOF while looking for matching \', caused by an unmatched single quote at the end of the appended inlinepython3 -cassertion. No runtime or numerical gate failed.Commit
feb85b2closes that quote. The existing complete runtime and final evidence assertions remain unchanged. Fresh exact-head CI is pending; do not merge until the current-head pinned test and all other required checks are green.Focused backlog observation and drain-budget evidence
Based on the exact green React feature PR #14 head
1d44dfda473591bea19c88a0a3f4078560c553c1. Extends the already-qualified real two-case MDM outage inaudit.py --multi-outagewith explicit monotone backlog progress observations, without changing production runtime, worker scheduling, SQL, authorization, or pinned MDM/pg-trickle images.Limitations: The 150-second wait here is a small focused two-case runtime test, not the signed T49.12 300-case p95/maximum target or an approved operational bound. Sampling cannot by itself prove actual per-cycle admission count or mixed-backlog fairness. Those need a dedicated instrumentation/acceptance profile; likewise clone/restore, 60/min throughput and signed owner envelope remain open.
Draft, pending current-head CI. Merge only into
issue/11-explicit-escalation-timeafter clean exact-head checks, nevermain. Keep PR #14 and issues #11/#12/#8 open.