official-source-check

Check the official documentation, release notes, or migration guide for the exact version installed in your project. Find the local version first from manifests or lockfiles, then confirm the API pattern against the narrow official source for that version.

Inspect package manifests, lockfiles, import statements, generated clients, schemas, config files, and CI images. These project artifacts pin the actual version, which determines which official documentation applies to your implementation.

Model memory is a hint, not evidence, for version-sensitive behavior. Training data may reflect outdated APIs, so always verify against official docs, standards specs, or provider SDK references before implementing.

Skip verification for project-local logic covered by tests, stable language syntax enforced by compilers or type checkers, and emergency mitigations where the user explicitly accepts unverified risk.

Surface the conflict explicitly rather than silently copying the existing pattern. Check whether the old pattern is still supported, then apply the smallest source-compatible implementation unless repo policy deliberately pins an older supported approach.