Repository navigation
Conversation
Confirm provider capability before bounded read-only chat resolution, derive UTC windows, and page grounding content safely. Preserve production defaults and document isolated TDF testing and rollback. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 0815a301-264d-439b-9f67-d8fc0897377c
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.
Summary
asksynthesis or Graph chat-message listing. Preserve the existing routes for chat inventory, exact messages, channels, mutations, and cross-workload requests.Configuration
The committed plugin retains its production MCP endpoint and OAuth settings. TDF routing remains an explicit local test configuration, not a published default. No backend deployment or provider enablement is included.
Validation
The full local offline guidance suite passed: 342 tests, zero failures or skips. These checks validate documentation and routing contracts; they do not establish live tenant permissions, provider availability, or observed model-routing behavior.