fix: stabilize Matter convergence and Gate 1 packaging - #5
Merged
Conversation
shawliu998
marked this pull request as ready for review
July 16, 2026 05:41
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.
What changed
Why
The merged Matter convergence work left several release-blocking gaps: policy enforcement could be bypassed at provider boundaries, Matter settings were not fully durable across packaged restarts, CI/package checks relied on stale or unreachable build/provenance assumptions, and the UI gate no longer exercised the complete E2E suite.
Impact
Matter workspaces now use one explicit inference policy across global, project, and matter scope. Provider calls are checked at both preparation and final execution boundaries. Profile, policy, default-model, chat, sources, and capabilities survive an offline packaged restart. The complete legacy UI suite remains enforced.
Root causes
Validation
Release note
The locally generated macOS artifacts are intentionally unsigned and unnotarized. They are acceptance-test artifacts, not distributable release binaries.