Discover, map, validate, and publish an integration.

An integration should not be treated as published until it has moved through a governed lifecycle: capability discovery, contract and schema mapping, fixture development, sandbox validation, and round-trip proof. This template frames integration work as a progression from initial validation to supported publication, with explicit checkpoints for fixture validation, partner confirmation, and ongoing versioning and maintenance. It also defines the exceptions that keep the process honest: capability gaps may require a partial projection only, vendor contract changes may invalidate prior assumptions, and some implementations must remain documented projections until the partner confirms the contract. The result is a repeatable path from discovery to a maintained, supported published status.