feat: @adcp/client 5.1.0 + retire platform_type for capability-driven compliance#2277
Merged
Conversation
… compliance 5.1.0 replaces AAO curated platform-type bundles with capability-driven storyboard resolution: agents declare supported_protocols and specialisms in get_adcp_capabilities, and the runner picks bundles accordingly. Rip out the AAO's own platform_type concept end-to-end: MCP tool inputs, REST routes, DB schema, heartbeat, rendering. Migration 409 drops the column; 410 adds the version column the 5.1.0 state store needs for CAS. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced Apr 17, 2026
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
@adcp/clientto^5.1.0platform_typeconcept end-to-end: MCP tool inputs, REST routes, DB schema, heartbeat, result rendering. Storyboard selection is now capability-driven (supported_protocols+specialismsfromget_adcp_capabilities) — the protocol's own mechanism replaces our curated platform bundlesagent_registry_metadata.platform_type; 410 addsversion INTEGER NOT NULL DEFAULT 1toadcp_stateso the 5.1.0putIfMatch/patchWithRetryprimitives work against PostgresloadBundledStoryboards→listAllComplianceStoryboards,getStoryboardById→getComplianceStoryboardById. Test kits now live atcompliance/cache/{version}/test-kits/evaluate_agent_qualityoutput no longer includes the "Platform Coherence" section; coherence signals come from per-track results and advisory observationsWhy this is breaking — and OK pre-3.0
5.1.0 is labeled minor but the 5.x surface is still pre-3.0. The
platform_typeinput existed only because 5.0'sComplyOptions.platform_typedrove curated bundle selection; 5.1.0 removed it in favor of the spec's specialisms. Keeping ourplatform_typeas a shim would just shift the inconsistency elsewhere, so we retire it in one go.Migrations run together: 409 drops the column after code stops reading it in the same release; 410 adds the state-store version column additively.
Test plan
npx tsc --noEmit— clean on changes (two pre-existingParsedRepoerrors in member-tools unrelated to 5.1.0)npm run test:unit— 587 / 587 passed in precommitnpx vitest run server/tests/unit/storyboards.test.ts server/tests/unit/mcp-eval-tools.test.ts— 36 / 36 passed. Pre-existing failures incomply-test-controller.test.tsandmcp-response-unwrap.test.tsare unrelated (verified by stashing)npx tsx scripts/generate-openapi.ts— regenerated, 11 lines removed for droppedplatform_typefieldsPUT /api/registry/agents/{url}/connectno longer acceptsplatform_type(caller audit — anyone who still sends it gets it ignored; they don't break)🤖 Generated with Claude Code