chore(gates): follow replay health baseline renames - #3046
Merged
Merged
Conversation
Size Report
Startup median (7 runs, lower is better):
|
Member
Author
|
Reviewed at a7c4e8a. This looks correct: the two baseline keys in |
|
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.
Summary
Move the two remaining path-keyed fallow health baseline entries from removed
src/daemon/replay/internal/paths to their renamed@agent-device/replay-portsource files. This completes the baseline follow-up requested in #3041 review. No runtime behavior or test logic changes.Validation
pnpm check:fallow --base origin/mainpassed; nosrc/daemon/replay/keys remain underfallow-baselines/.a7c4e8a6eon main3fe2e6929: frozen install, build, repository-widepnpm format, andpnpm check:affected --runpassed.