Add Muse Code harness support - #105
Merged
Merged
Conversation
This was referenced Sep 13, 2026
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.
Adds Muse Code as a standard Harness so
va muselaunches with the selected Manifest andva muse --yoloforwards Muse's native flag unchanged. The default is baremusein the caller's directory, preserving Muse's permission settings and native resume arguments.Includes the shipped profile, installer discovery and existing-profile preservation, Doctor working-directory checks, operator documentation, and CLI acceptance tests. Uses the existing secret-resolution and Manager-token removal path.
Closes #103.
Validation:
cargo testcargo check --all-targetscargo fmt --checkcargo clippy --all-targets -- -D warningsbash -n install.shexec --yoloreceived an injected non-secret sentinel; the tool result reported the expected output and exit code 0. No real third-party credential or authenticated external action was tested.Standards and Spec reviews completed: no correctness or spec findings; one optional note about the installer's existing repeated discovery pattern was left for a broader refactor.