verify-rsn-fix

To fix RSN failures, run npm run rsn to identify mismatched codefix files, update the corresponding data/static/codefixes challenge variants to match your snippet edits, and re-run the check until it passes.

RSN check failures occur when source code edits inside vuln-code-snippet blocks cause the locked snippet state to diverge from the associated codefix variant files stored under the data/static/codefixes directory.

When updating codefix files, carefully preserve the intended incorrect variants while ensuring the _correct variant exactly matches your fixed snippet source code to maintain challenge integrity and pass RSN verification.

Running npm run rsn before editing vuln-code-snippet blocks is not required, but doing so establishes a baseline RSN state, making it easier to identify which codefix files become out of sync after your snippet edits.

The npm run rsn check fails after snippet source code edits because the Refactoring Safety Net detects that the challenge codefix variant files no longer match the newly modified locked snippet state, requiring targeted reconciliation.

The best way to locate out-of-sync codefix files is to run the RSN verification, map each reported challengeName to the corresponding snippet block, and locate the related files under data/static/codefixes/ for consistent updates.