fix: doctor recognizes the strategy-advice prompt hook variant - #312
Merged
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
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.
Doctor compared the registered UserPromptSubmit command against the plain form only, so
jevcompass install --strategy-advice— the installer's own supported opt-in — made doctor report the hook as unregistered and overall FAIL. The check now also accepts the product prompt hook carrying the installer's strategy-advice flag (reusing_has_strategy_advice_flag); SubagentStart and spawn validation are unchanged. Found while enabling the opt-in hooks on the maintainer profile. One focused regression test; full suite 859 OK locally; diagnostics-only change (VCR411 in TASKS/PILOT). Hosted CI required before merge.