Repository navigation
Show draft failures with a consumer sentence and quotable refId - #609
Merged
TheGreatAxios merged 2 commits intoSep 4, 2026
Merged
TheGreatAxios merged 2 commits into
TheGreatAxios merged 2 commits into
Conversation
A failed Myra draft must answer the canonical envelope, keep that userMessage and refId on the client, and show both in the panel — never a generic 422 with no quotable id.
…749)
The hub was answering drafting_failed as {code, message}, so the
client could not parse the envelope and the panel showed a generic
422 with no refId. Mount the package draft routes, report the
failure through reportError, and thread that same refId through
ApiQueryError into the panel.
Contributor
Author
Self-reviewVerdict: the change is correct and well-tested — hub now serves the package's
Targeted tests run (all pass):
|
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.
Fixes CL-6749
A failed agent-create draft was answering
{ code, message }from a hand-wired hub route. The client only accepts{ userMessage, refId }, so the panel showed a generic 422 with nothing to quote.createAgentDefinitionDraftRoutesso 422 usesmakeErrorEnvelopereportErrorso the log and envelope share a refIdApiQueryErrorcarriesrefId;postJSONusesparseErrorEnvelopeReference: <refId>