A conflict-free textual merge is not evidence of a compatible integration: when a PR removes

A conflict-free textual merge is not evidence of a compatible integration: when a PR removes or reshapes an API and the new base adds a consumer or dependency edge in another file, Git can auto-merge cleanly while build and policy-contract checks fail. After a base change, run the repository’s semantic preflight and at least a compile/build boundary even when every reported conflict is documentation or generated output. This is most important for long-lived branches and does not imply every base update needs the entire test suite; select the smallest checks that cover module exports and declarative routing/dependency ownership.