test(storage): derive byte assertions from observation state - #183
Merged
Conversation
try-works
force-pushed
the
fix/run94-storage-boundary-timeout
branch
from
August 28, 2026 23:42
162745a to
5e0bcbe
Compare
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Correct the packaged storage UI contract: byte expectations follow observationState, so observed local, cloud, and deduplicated physical-resource records remain measurable while unobserved/unconfigured records remain null.\n\nThe prior test failed in the authoritative paired packaged-runtime browser gate.