verify-rsn-fix

To fix broken RSN mappings, run npm run rsn to identify affected challengeName_*_correct files, update the corresponding codefix files in data/static/codefixes to match the locked snippet state, and re-run the check until all files pass.

A Refactoring Safety Net failure occurs when edits to vuln-code-snippet blocks cause the application's codefix files in data/static/codefixes to drift out of sync with the locked snippet state, breaking the Fix It challenge functionality.

You keep codefix files synchronized by updating the affected files in data/static/codefixes to mirror your modified vuln-code-snippet source, then running npm run rsn repeatedly to verify that all codefix files match the locked state.

Yes, the RSN verification loop applies to security challenge snippet edits across server, routes, and frontend code, ensuring all locked snippet variations remain consistent throughout the OWASP Juice Shop application.

The npm run rsn command reports affected challengeName_*_correct files because it detects that the codefix files in data/static/codefixes no longer match the locked snippet state after you changed code inside a vuln-code-snippet block.

The RSN check is limited to verifying that codefix files match the locked snippet state, requiring manual updates to the data/static/codefixes files and repeated npm run rsn executions until all discrepancies are fully resolved.