g06.036 — Goose ACP consumer HTTP MCP wiring

[betterthanclay]

Summary

• Wire Contract 063's consumer-supplied streamable-HTTP MCP placement into goose.acp production session/new as ACP McpServer::Http with headers passed verbatim under the route-owned name swallowtail-goose-acp.
• SSE is not offered: encoding refuses it as swallowtail.goose.acp.mcp_sse_unsupported because the provider rejects SSE. Omission still sends mcpServers: []. URL and header values stay out of Debug, failures, activity, receipts, and fingerprints.
• client_mcp_servers stays No / producer gap naming the live gate. Emission is proven; live honouring is not.

Test plan

• cargo fmt -p swallowtail-adapter-goose -- --check
• effigy validate:focused swallowtail-adapter-goose
• effigy package:verify-affected swallowtail-adapter-goose
• effigy qa:routes
• effigy qa:docs
• git diff --check

Made with Cursor

[betterthanclay]

Changes required

1. docs/guides/provider-solution-feature-matrix.csv:23 — The updated goose.acp row still opens its notes with “Exact GitHub v1.46.0 ACP,” while the same row's guaranteed version posture is “Exact 1.50.1” and Research 351 plus the integration guide identify the reviewed route point as 1.50.1. This leaves the consumer feature matrix with conflicting exact-version claims for the route whose HTTP MCP wiring this PR documents. Update the stale version statement to 1.50.1 (or remove it) so the row consistently describes the current qualified point.

No other blocking findings. Reviewed exact head f4f0f15b74725f9044b88254b6ec1e04c5e1ef0f. Validation passed: cargo fmt -p swallowtail-adapter-goose -- --check; git diff --check; effigy validate:focused swallowtail-adapter-goose (51 tests); effigy package:verify-affected swallowtail-adapter-goose; effigy qa:routes; effigy qa:docs. GitHub checks were green at review time.

[betterthanclay]

Ready to merge

The prior finding in docs/guides/provider-solution-feature-matrix.csv:23 is resolved: the Goose ACP notes now identify exact GitHub v1.50.1, consistent with the row's guaranteed version posture, Research 351, and the integration guide. The only change since the prior review is this matrix correction. No blocking findings remain.

Reviewed exact head d0ce05d5eea8476f4729e287ab0c4dcc1c7fa20d. Validation passed: effigy qa:routes, effigy qa:docs, and git diff --check. All active GitHub checks passed; pinned MSRV floor tests were skipped by the workflow. The exact-head checkout is clean.

[betterthanclay]

Ready to merge

Re-reviewed PR #374 at exact head 42f1033c58e838a2c574667826cacdc9518e3cab, against base 9e058538ca80cf8071e1f51b3d0322dc4c0ebf64. The prior finding in docs/guides/provider-solution-feature-matrix.csv:23 remains resolved: the row identifies exact GitHub v1.50.1, consistent with its guaranteed version posture, Research 351, and the Goose integration guide. The merge from main adds no files to the PR comparison outside the task; the diff remains limited to the Goose route and owned docs/API baseline. No blocking findings.

Validation passed: cargo fmt -p swallowtail-adapter-goose -- --check; effigy validate:focused swallowtail-adapter-goose (51 tests); effigy package:verify-affected swallowtail-adapter-goose; effigy qa:routes; effigy qa:docs; and git diff --check. All active GitHub checks passed; pinned MSRV floor tests were skipped by the workflow. The exact-head checkout is clean.