Conversation
The previous release branch left a missing parseDoctorArgs helper while the active doctor command path still referenced it, causing runtime failure for users immediately after update checks. This patch restores doctor argument parsing, adds a metadata regression assertion for parser presence, and bumps release metadata to 5.0.16 with synced release notes. Constraint: Keep doctor command behavior backward compatible for --target and --strict Rejected: Remove legacy doctor code path in this patch | broader refactor risk in hotfix window Confidence: high Scope-risk: narrow Reversibility: clean Directive: Do not remove doctor parser helpers without updating both doctor entrypoints and tests Tested: node --check bin/multiagent-safety.js; npm test; manual smoke: setup temp repo then gx doctor --target <repo> Not-tested: Global npm publish/install path on external host
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.
Automated by scripts/agent-branch-finish.sh (PR flow).