Always severity: "info", and never escalated to blocking by any flag,
including --strict -- an identical shape is genuinely common and
frequently correct (two unrelated features can both take a number timeout
with a validator, and that is not a defect). This is an observation offered
to a reader, not a rule; making it blockable would make it noise a team has
to suppress rather than a signal they can scan.
Scope, deliberately narrow on every axis:
detectCompatibilityIssues()'s own, entirely separate concern above;
reporting them here too would double-report one problem under two codes.
Flags differently-named variables in different contracts that share an identical type shape -- a soft signal that two features may be independently modelling the same underlying configuration value under two names, worth a human glance before they drift apart.