feat(types): Plugin Batch 1 / ADR-043 explainability fields on MCP responses (v6.1.0)#141
Merged
Merged
Conversation
…sponses (v6.1.0) Surfaces fields the AxonFlow agent has emitted since v7.1.0 that the MCP response types didn't declare. Pure Cat B field-additions on existing methods — all optional, no breaking changes. Pre-existing constructors preserved as source-compat overloads. Documented in OpenAPI via platform v7.4.3 (axonflow-enterprise#1714); SDK catches up here. Coordinated cycle: TypeScript v6.1.0 / Python v6.8.0 / Go v5.8.0 ship same day with the same field set. MCPCheckInputResponse gains 5 fields (decisionId, riskLevel, policyMatches List<ExplainPolicy>, overrideAvailable Boolean, overrideExistingId). overrideAvailable is boxed so callers can distinguish "unset" from "false" on older platforms. MCPCheckOutputResponse gains 3 fields (decisionId, policyMatches, redactedMessage — text-redaction counterpart to redactedData). ExplainPolicy already shipped — same Jackson record reused on MCP responses. Java's @JsonProperty + camelCase getter convention handles the wire mapping naturally. Source compatibility preserved on both types: 4-arg constructor (Input) and 6-arg constructor (Output) kept as overloads that delegate to the new @JsonCreator constructors with null for the new fields. equals/hashCode/toString updated to include new fields. ExplainDecision tool surface (client.explainDecision + ExplainRule + DecisionExplanation full type surface) is feature work tracked separately in axonflow-enterprise#1716 — not this release's scope. 1200 tests pass; validate-version-alignment green.
saurabhjain1592
added
the
spec-pin-bump
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.
Summary
Minor release — pure Cat B field-additions. Surfaces the 8 Plugin Batch 1 / ADR-042 / ADR-043 fields the agent has emitted since v7.1.0. Pre-existing constructors preserved as source-compat overloads.
Coordinated cycle
Same field set across all 4 SDKs, same release day: TypeScript v6.1.0 / Python v6.8.0 / Go v5.8.0 / Java v6.1.0 (this).
Added
MCPCheckInputResponsegains 5 fields (decisionId,riskLevel,policyMatches: List<ExplainPolicy>,overrideAvailable: Boolean,overrideExistingId).overrideAvailableis boxed so callers can distinguish "unset" fromfalseon older platforms.MCPCheckOutputResponsegains 3 fields (decisionId,policyMatches,redactedMessage).ExplainPolicyalready shipped — same Jackson record reused on MCP responses.Source compatibility
Both response types retain their v6.0.0 constructor signatures as overloads that delegate to the new
@JsonCreatorconstructors withnullfor the new fields. Existing callers compile unchanged.equals()/hashCode()/toString()updated.Held back
client.explainDecision(decisionId)is feature work — see axonflow-enterprise#1716.Test plan
validate-version-alignmentgreen at 6.1.0