Repository navigation
Record measured peer-flow playback and retained duration limit - #83
Merged
Merged
Conversation
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.
Publish the measured result from the deployed verified-piece-flow runtime: both fresh headless Chrome viewers recorded zero post-frame stalls, player errors and dropped frames, with a natural wrap followed by 71.665 seconds. The overall strict result remains RED because its 329,993 ms wall span missed the frozen 330,000 ms requirement; the separate monotonic span is retained without replacing that gate.
Add a compact sanitised evidence record, linked showcase documentation and llms.txt discovery. The record includes actual peer payload and inclusive HTTP bodies, partial/cancelled downloads and evicted report rows. It makes no traffic-saving, causal performance, competitor or physical-device claim, and preserves earlier failed results.
Validation: JSON parsing, diff whitespace checks and independent review against the sealed original evidence. This changes three documentation files; runtime, player, source pins and TURN configuration are unchanged.