Repository navigation
Preserve contiguous startup extension during admission - #47
Merged
Merged
Conversation
This was referenced Oct 27, 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.
A moving startup target can reach two verified future fragments while the reservoir still lacks recovery headroom. Admission then applies the previous fragment's service-time lead to their next contiguous successor and skips it, leaving a gap despite an available fourth slot.
Preserve that successor when both verified futures cover the fresh target. Initial forward-window selection and the one-future service-lead path keep their existing behaviour. Reservation, verification, authority, four-object/24 MiB limits, recovery headroom, ACK ownership and original deadline remain unchanged.
Validation: the new encoded-loader regression fails before the fix and passes after it; warm-buffer suite 129/129, syntax 202 modules, documentation 30 authored files/450 links. Independent review found no blockers. The controlled successor completion is correctness evidence, not a field latency measurement; real-source startup, sustained playback and physical-device acceptance remain separate.
Full existing swarm suite: 666/666 passed, zero skips/failures. The source-only 4K smoke still failed the late-join deadline; first viewer decoded at 4.685 seconds, second decoded no frame. This is a bounded correctness fix, with real-source startup still unqualified.