Repository navigation
Explain mapper failures before a guarded dispatch receipt - #321
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.
Adds a distinct preflight callout to the agent builder and guide. The host
resourceFormapper receives a canonical argument snapshot; a throw, non-string return, or mutation rejects before planning, receipt creation, or tool callback entry. This error belongs in the host integration path and must not be invented as a blocked receipt.Focused builder tests and asset check pass locally; the existing guarded-tool input test covers mapper rejection. The page remains a project-authored local fixture, with no human approval, provider call, delivery evidence, or production safety claim.