integration-gatelisted

# Integration Gate ## Purpose Enforce that `A = STABLE` and `B = STABLE` does not imply `A+B = STABLE`. ## Trigger Run when two or more Components are ready to combine, when Contracts change, or when an integrated unit needs fresh evidence. ## Inputs - Exact Component revisions and their Component Quality Gate evidence. - Versioned consumer/provider Contracts, integration design, and integration points. - Integration workspace/base, test strategy, environment/data, risks, and rollback plan. ## Prerequisites - Every participating Component is `STABLE` for the supplied revision. - Contracts are sufficiently valid and compatible for attempted integration. - Integration workspace and ownership are explicit; unverified changes are excluded. ## Procedure 1. Perform the Stable Component Check and reject stale/mismatched evidence. 2. Validate consumer/provider Contract versions, schemas, protocols, errors, and compatibility. 3. Confirm workspace base, constituent revisions, rollback point, and absence of overlapping untracked integration work. 4. Mark the combined unit `UNVERIFIED`. 5. Integrate the smallest dependency-ready set in controlled order. 6. Build/initialize the integrated unit. 7. Run Contract tests, integration tests, and relevant regression tests. 8. Validate cross-boundary data, error, security, performance, and lifecycle behavior as risk requires. 9. Diagnose failures at interface, Contract, data, integration implementation, environment, design, architecture