What problem does it solve? When a consumer and supplier live in different deploy 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 consumer-driven contract tests so both sides can develop in parallel against a verified interface. ## Core Features & Use Cases - OpenAPI Projection: Converts the consumer-owned Port signature into an OpenAPI contract with stable operationIds and schema names from the ubiquitous language. - Per-Side Generated Types: Generates types from the contract on each side, enabling parallel frontend/backend 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, enforcing additive-vs-breaking discipline at merge. - Event-Schema Variant: For event-replication or local-first sync wires, projects the contract as a versioned event schema with descriptor-reflection contract tests and pinned delivery guarantees. - Use Case: A frontend and backend team in separate deploy units need to evolve an API without breaking each other — the consumer publishes a Pact contract, and the producer must turn it green before the consumer depends on the new shape. ## 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 tests.
