fix: harden openwebui passthrough state injection#153
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.
What changed\n- Fixed OpenWebUI base pipe and preprocessor pipe passthrough behavior to carry authoritative state context into downstream calls when active state is non-empty.\n- Updated trace behavior and coverage so passthrough/update/clarify reporting is consistent with live integration expectations.\n- Added explicit regression tests for empty-state passthrough, clarify no-model-call paths, and repeated passthrough no-dup compiler-state message behavior.\n- Updated OpenWebUI integration metadata/title expectations and bumped package version to 0.7.2.\n\nWhy this was needed\n- Manual integration audit found passthrough turns were not reliably honoring active authoritative state in downstream model context, causing policy/premise drift in normal chat turns.\n- The hardening pass closes the integration gap while keeping core engine semantics unchanged and scoped to host integrations.