Repository navigation
Preserve model 11 applicability reviews after model 12 migration - #54
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Model 11 applicability reviews became stale after a workspace-only migration to model 12 because the review hash includes the model version. Evaluate model 12's current facts through the published model 11 applicability calculation and its existing legacy/Git recovery paths. The bridge is explicit to this version pair; changed statements, criteria, scope links, and requirement decisions still invalidate reviews. Stored revisions and review dates stay unchanged, and model 12 still requires its new schedule-set review.
Regression coverage includes all four applicability record types, historical recovery, substantive changes, migration preservation, collection bindings, and CLI/browser-state parity. Coordinated patch release: 0.17.1.
Validation: Node 24.11.1,
npm ci,CI=true npm run validate, both package dry runs,npm audit, private-source/secret scan, and a fresh consumer repository with the local engine (224 records, no diagnostics). Playwright verified current → stale → current behavior against an isolated generic workspace, CLI/HTTP parity, and clean browser console/network and application logs. Combined correctness/security review completed clean after fixing timestamp-only parity-test metadata.Landed at
7161b933dc6f777b21cfb6be2ba70882ad6cbc5f. PR validation and release publication passed. Release 0.17.1 publishes both packages as npmlatest, with provenance bound torefs/tags/v0.17.1. Main and the tag resolve to the same commit.