fix(send): show failure reason and IDs after response streaming - #192
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
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.
Outcome
Human CLI output shows the actual failed target reason plus send and assignment IDs, rather than pointing to an invisible receipt. Fixes #191.
Work authority
Plan
Render failed targets even when responses were streamed, retain response deduplication, bound text and remove control characters, test the user's failure shape.
Changes and commits
5f3c6f6 adds compact failure rendering and a streamed receipt regression.
Verification
Three focused outcome tests pass; source architecture checks pass. Managed CLI rebuild running; Actions pending.
Risk and rollback
Display-only change; no credential or schema migration. Render bounded failure fields, not protected execution context. Revert through managed development if necessary.
Completion summary
The previously invisible human failure is implemented; underlying intermittent Kata startup is still tracked separately, not declared fixed.
Submission checklist