Qodana baseline staleness after linter image or profile change

Qodana baseline allows teams to snapshot existing issues so subsequent runs report only newly introduced problems against a quality gate.

The baseline file is compared to current analysis results, and behavior depends on the linter image version, inspection profile, and how analysis caching is managed in CI.

It is unclear under which configuration or code changes a committed baseline should be considered stale, and how stale baselines interact with quality gate thresholds for new issues.

Which conditions formally invalidate a baseline? Does Qodana surface a mismatch when the linter image or profile used for a run differs from that used to create the baseline? When is regeneration of the baseline recommended versus updating the quality gate?