What problem does it solve? When a consumer and a supplier live in independently deployed units, the boundary between them crosses the network and needs an executable contract. This Skill projects that boundary into OpenAPI schemas, per-side generated types, and Pact-based consumer-driven contract (CDC) publish/verify, so both sides can develop in parallel against a stable interface. ## Core Features & Use Cases - OpenAPI projection: Converts the consumer-owned Port signature into an OpenAPI contract with stable operationIds and schema names drawn from the ubiquitous language. - Per-side generated types: Consumer and producer each generate types from the contract, enabling parallel development against the interface. - CDC publish/verify with Pact: The consumer publishes the pact; the producer verifies it real-on-real as the D2 welding step, with additive-vs-breaking checks at merge/deploy. - Event-schema variant: For event-replication, local-first sync, or warm-standby wires, the contract becomes a versioned event schema with descriptor-reflection CDC tests (red-on-removal/red-on-rename) and a pinned delivery guarantee. - Use Case: A frontend team and a backend team deploy independently. Use this Skill to project their shared boundary into an OpenAPI contract, generate types on both sides, and gate merges on the producer verifying the consumer's published pact. ## Quick Start Ask the agent to realize the cross-deploy boundary for a feature whose manifest pins boundary.projection = cross-deploy, generating the OpenAPI contract and Pact verification. ## Quick Start Use the seam-cross-deploy skill to project the cross-deploy boundary in the building-block manifest into an OpenAPI contract with Pact consumer-driven verification.
