Repository navigation
Add AI triage through MCP with durable declared model results - #20
Merged
Merged
Conversation
fruwe
force-pushed
the
fruwe/reference-mcp-workflow-v030
branch
from
October 5, 2026 13:16
e0ff79f to
d1278ee
Compare
fruwe
force-pushed
the
fruwe/ai-mcp-workflow-v030
branch
from
October 5, 2026 13:19
bf38ba5 to
f90686f
Compare
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.
Adds an independent AI support triage workflow using the public-v1 remote execution host. After an analysis intent commits, the customer worker invokes an actual stdio MCP tool backed by native OpenAI SDK objects. Only validated category/summary values cross into portable state. The local result is durable before correlated remote admission/processing, and retained outcomes are reused after unknown responses.
The default provider is explicitly an offline fixture, with documented deployment opt-in for live calls. Container validation forces offline mode even when the parent shell is configured live. No model-quality, verified-helper or exactly-once claim.
Validation at 366ad65: three tests and Ruff pass; ordinary Docker build/workflow/restart passed with inherited live mode and no provider key. All eight GitHub checks pass; independent exact-head review approved the implementation, resolved findings and source closure. Every source/config/lock is folder-owned. No tag or publication.
Closes #19.