ecosystem-grounding

You can check API contract mismatches across multiple repositories by parsing an ecosystem digest to identify exact, compatible, and breaking contract statuses across backend, iOS, and shared-types. It explicitly lists mismatch locations and enforces acknowledgment of breaking issues before code generation proceeds.

An ecosystem digest provides an overview of a multi-repo project state by detailing scanned repositories, branches, uncommitted changes, and contract health. It helps you quickly orient yourself by summarizing per-repo naming conventions, file organization, and error handling patterns before starting work.

To get an overview of repository layouts and coding conventions before starting a feature, run an ecosystem grounding process that scans your project. This provides a consolidated view of branches, uncommitted changes, and per-repo naming, file organization, and error handling patterns.

Yes, you can enforce acknowledgment of breaking contract mismatches before code generation. The ecosystem grounding process explicitly identifies breaking, warning, and informational mismatches across your backend, iOS, and shared-types, requiring acknowledgment of breaking issues before proceeding with code generation.

Yes, ecosystem grounding works with iOS, backend, and shared-types repositories by parsing their digest to identify repository layouts, contract statuses, and active mismatches. It provides a consolidated view of these scanned repositories, their branches, and any uncommitted changes.