cabloy-contract-loop

To prevent Cabloy contract drift, you must coordinate Vona and Zova synchronization workflows. This involves identifying the contract source, regenerating the OpenAPI SDK, and validating end-to-end across backend and frontend outputs.

The correct OpenAPI SDK regeneration workflow is backend-first: verify the backend API contract, regenerate the OpenAPI SDK, update REST types, and perform end-to-end verification across frontend integration paths instead of manual patching.

You diagnose stale generated consumers and dependency drift by identifying the contract boundary scenario. Determine whether the change is a forward chain, reverse chain, consumer drift, or local dependency drift before selecting a regeneration path.

Manual patching does not work reliably for Cabloy frontend metadata handoffs. You should direct synchronization toward backend-first verification, OpenAPI checks, and REST/type regeneration to ensure accurate dependency synchronization.

To verify end-to-end Cabloy contract synchronization, validate both Basic and Start workflows across backend contracts, generated consumers, and frontend integration paths to ensure complete Vona and Zova alignment without drift.