Binary Compatibility Validator was removed in #150. v1.0.0 ships a SemVer-stable Android API but relies on manual public-API review in PRs only (CLAUDE.md and CONTRIBUTING were corrected during the release to stop falsely claiming automated enforcement).
For a stable public surface, re-add an automated gate: apply BCV (or the Kotlin binary-compatibility-validator), generate .api baselines (apiDump) across the public modules, and wire apiCheck into CI so accidental public-API changes fail the build.
Decision needed: scope (all modules vs. core + public-facing modules only). Note Featured uses Explicit API mode and has a no-migration-window policy, so the baseline is the enforcement mechanism, not deprecation cycles.
Binary Compatibility Validator was removed in #150. v1.0.0 ships a SemVer-stable Android API but relies on manual public-API review in PRs only (CLAUDE.md and CONTRIBUTING were corrected during the release to stop falsely claiming automated enforcement).
For a stable public surface, re-add an automated gate: apply BCV (or the Kotlin
binary-compatibility-validator), generate.apibaselines (apiDump) across the public modules, and wireapiCheckinto CI so accidental public-API changes fail the build.Decision needed: scope (all modules vs. core + public-facing modules only). Note Featured uses Explicit API mode and has a no-migration-window policy, so the baseline is the enforcement mechanism, not deprecation cycles.