Repository navigation
Retain bounded peer-flow diagnostics in saved reports - #84
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.
The saved playback report can show unused verified pieces and unsuccessful races, but cannot distinguish an untrained rate from an admission cooldown. Pin RelaySwarm c8120c5 (relayswarm#50), rebuild the exact-source bundle, and project its bounded peer-flow diagnostics into normal locally saved reports.
The new field allows only fixed numeric/nullable fields and decision enums. Missing older SDK data remains unknown; raw SDK objects, identifiers, keys and URLs are excluded. It records evaluations and verified estimator inputs, not additional playback credit. Player controls, peer-selection policy, timers, network requests and public TURN configuration are unchanged. Documentation and llms.txt explain the new receipts without a performance claim.
Validation: site build and all 373 tests passed, including new privacy/type/clone regressions through the ordinary report API. Source provenance, notices, module query versions and unchanged committed WASM were checked; no Rust build or dependency installation occurred. A separately prepared 180-second public diagnostic will inspect actual model decisions after deployment, without replacing or rescoring the earlier sustained-playback results.