chore(contract): bump OpenAPI spec pin to community v9.6.1#195
Open
saurabhjain1592 wants to merge 1 commit into
Open
chore(contract): bump OpenAPI spec pin to community v9.6.1#195saurabhjain1592 wants to merge 1 commit into
saurabhjain1592 wants to merge 1 commit into
Conversation
Refresh tests/fixtures/wire-shape-baseline.json from the community spec revision f910aa3d (v7.4.x era) to ac1b7cd8 (v9.6.1, current origin/main of getaxonflow/axonflow). Regenerated via scripts/wire_shape/refresh.py against a detached checkout of docs/api at the target SHA. Validator green (83 class/schema pairs), mvn test fully green (1312 tests, 0 failures). Highlights: - MCPCheckInputResponse drift entry drops entirely: the v9.6.1 spec now declares redacted, redacted_statement and redaction_evaluated (Decision Mode PEP contract). - MCPCheckOutputResponse keeps an acknowledged sdk_only redaction_evaluated with a note: the platform emits it since enterprise #2865/#2866; the spec declaration rides the v9.7.0 community sync. - intra_file_duplicates now empty (orchestrator-api.yaml PolicyMatch duplicate fixed upstream). - Decision Mode types now registered: DecideRequest, DecideResponse, DecisionCallerIdentity, DecisionTarget, ObligationFulfillment (registered_types 79 -> 83). - Many stale drift entries drop as satisfied by the newer spec; new spec-side additions recorded mechanically. No SDK source changes. Baseline + pin only. Refs: getaxonflow/axonflow-enterprise#2861 Signed-off-by: Saurabh Jain <saurabh.jain@getaxonflow.com>
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
Dedicated spec-pin bump: refresh
tests/fixtures/wire-shape-baseline.jsonfrom community spec revisionf910aa3d(v7.4.x era) toac1b7cd8(v9.6.1, currentorigin/mainof getaxonflow/axonflowdocs/api).Regenerated via
scripts/wire_shape/refresh.pyagainst a detached checkout of the community repo at the target SHA. Baseline + pin only — no changes tosrc/,pom.xml, orCHANGELOG.md.Refs getaxonflow/axonflow-enterprise#2861.
What dropped (now satisfied by the v9.6.1 spec)
MCPCheckInputResponse— entire drift entry gone. The spec now declares the Decision Mode PEP fieldsredacted,redacted_statement,redaction_evaluatedthe SDK shipped in v8.5.x.intra_file_duplicatesnow empty — theorchestrator-api.yamlPolicyMatchdouble-declaration was fixed upstream.AuditSearchRequest(spec now declaresdecision_id/offset/override_id/policy_name— the v9.6.1 session/audit-search work),DynamicPolicy,ExecutionSummary,MarkStepCompletedRequest,UsageBreakdown,UsageSummary,WorkflowStepInfo(whole entries), plus sdk_only shrinkage inAuditLogEntry(metadata/model/policy_violations),Budget,CancelPlanResponse,ClientRequest(media),ClientResponse(budget_info/media_analysis),CreateStaticPolicyRequest,CreateWorkflowResponse,ExecutionSnapshot,PlanResponse,ResumePlanResponse,UpdateStaticPolicyRequest,UsageRecord.What was added (new in the v9.6.1 spec, recorded mechanically)
DecideRequest,DecideResponse,DecisionCallerIdentity,DecisionTarget,ObligationFulfillment—registered_types79 → 83.ConformityAssessment(agent-api vs orchestrator-api declare different shapes — a spec-side issue, not SDK drift).HealthResponsecross-spec fingerprint updated: agent-api now also declaresplugin_compatibility.DecideResponse.sdk_only = ["error"]andResumePlanResponse.spec_only += ["step_result"]— see drift notes below.What was kept (acknowledged, with note)
MCPCheckOutputResponse.sdk_only = ["redaction_evaluated"]— kept with an in-baseline_note: the platform emitsredaction_evaluatedon check-output since enterprise #2865/#2866 (2026-07-09); the spec declaration rides the v9.7.0 community sync. Flip this entry out on the next pin bump.Real drift observed (reported, not "fixed" here per pin-bump scope)
DecideResponsedeclares anerrorwire field (@JsonProperty("error")insrc/main/java/com/getaxonflow/sdk/types/DecideResponse.java) that agent-api.yaml v9.6.1 does not declare. The engine returns it on failure paths; spec under-declares. Candidate for the v9.7.0 spec sync alongside check-outputredaction_evaluated.per_type_driftentries (37 types) are the long-standing QF-14 burn-down set, now smaller and re-verified against v9.6.1.Validation
AXONFLOW_OPENAPI_SPECS_DIR=<v9.6.1 docs/api> python3 scripts/wire_shape/validate.py→ ✅ 83 class/schema pairs validated, 0 issues.mvn test(JDK 17) → 1312 tests, 0 failures, 0 errors, 0 skipped.spec-pin-bumplabel applied per the wire-shape-contract SHA-bump guard.