speckit-version-guard-validate

To validate changed source files against locked dependency versions, you scan implementation files for API patterns that conflict with locked rules. This flags incompatible imports and methods to catch compatibility problems before merging.

Version-guard rules are compatibility tables defining forbidden API patterns for specific dependency versions. You need them during implementation workflows to prevent version-specific API misuse from becoming runtime issues.

To scan implementation files for incompatible API patterns before merge, parse version-guard reports and rule tables. The scan locates source files and produces advisory validation output flagging version-specific misuse.

Yes, the Spec Kit version-guard validation works without existing reports by utilizing project-aware graceful degradation fallbacks. It continues scanning source files and producing advisory output even when report metadata is missing.

The best way to catch version mismatches in API imports during development is performing an advisory source scan against locked dependency versions. This checks changed files for incompatible patterns and reports findings before runtime issues occur.

Your implementation fails compatibility checks with locked dependency versions because source files contain API and import patterns conflicting with locked version-guard rules. Scanning locates these incompatible usages and produces advisory validation findings.