refactor: remove dead install progress streaming - #158
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.
What does this PR do?
Removes the obsolete install-progress event bridge and makes the existing linear console progress path unconditional.
Why?
The v5 wizard install screen was intentionally removed in #150, leaving
internal/progress, the brew/npmSetProgressSinkhooks, and everyprogressSink.Emitbranch without a production caller. The informational deadcode job reports the drift but does not block merges.Testing
go vet ./...passesCross-repo checklist
openboot.devNotes for reviewer
The
no-direct-execbaseline only changes because deleting branches moved two existing, intentional call sites to new line numbers.