refactor(mqlaunch): extract prompt concern#53
Merged
Conversation
MCamner
marked this pull request as ready for review
July 17, 2026 13:06
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.
Why
Step 11a reduces the live
mqlaunchmonolith one concern at a time. Promptdirectory handling, AI-backend guardrails, prompt browsing, and prompt backups
were still defined directly in the launcher, which made their ownership harder
to test and allowed duplicate definitions to return unnoticed.
What Changed
mqlaunch/lib/prompts.sh.routes.
and AI-mode argument forwarding.
Verification
The focused contract test confirms that the repo-local prompt directory still
wins over the configured fallback, all three backend states are preserved, and
safe_run_aiforwards the selected mode unchanged. The monolith gate confirmsthat all seven functions have one live definition.