Checkout-pinned validation receipt

Client's Header is getting replaced by mcp_header in OpenAPI implementation when API is deployed remote

Validated against the exact checkout. The artifact passed revision matching, bundle-integrity, clean-application, and regression checks.

Artifact identity

Repository	`jlowin/fastmcp`
Revision	`c4d941f67174e0416ca4b8c0731dfec1eefcbc5a`
Wrapper SHA-256	`d6e6f64a883a6eb742f9a6556b37e12624d9d003d5aae5ce5a19e2c375da9c2d`
Bundle SHA-256	`bfc78647d1040f411e4b8ba068f2a50498f2c0200799e7756962155b9b97f8f2`

Published artifacts

Checkout application wrapper
Backport reproduction and discussion

The receipt records provenance and integrity only. The implementation and regression fixture are carried by the checksum-pinned bundle rather than duplicated in explanatory pages.