Repository navigation
Preserve semantic compaction causes in generation failures - #15
Merged
Brian Krabach (bkrabach) merged 1 commit intoOct 10, 2026
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.
Semantic compaction failures currently lose their bounded cause before reaching the app. Preserve
summary_output_limit,summary_empty,previous_failure,summary_failed, andnative_failedin generation failure events so hosts can offer the appropriate recovery guidance. Unknown or malformed codes remain omitted, and exception bodies stay private.Validation: the complete loop-live suite passed in the project-owned Linux DTU (116 passed, 4 optional tests skipped). Existing native failure behavior and no-replay semantics are unchanged. Companion Unified changes cover the runtime-to-visible-diagnostic path.
Related: microsoft/amplifier-unified#431.