docs(audits): explain why audit checks duplicate real-time validation

[kaligrafy]

Summary

• Clarifies in the audit READMEs that audit checks must validate interview data on its own merits, never assuming it was already validated in real time on the frontend.
• Explains the two concrete reasons this matters: a respondent can leave a field invalid after passing through it (without correcting the red error shown in the frontend) and abandon the interview, or edit the stored interview data directly (e.g. via browser dev tools), bypassing real-time validation entirely.
• Short version added to packages/evolution-backend/src/services/audits/README.md; more complete version with the two scenarios added to packages/evolution-backend/src/services/audits/auditChecks/README.md, linked from the short one.

No code changes — documentation only.

Test plan

• Review rendered markdown for the two README files
• Confirm the cross-link anchor (auditChecks/README.md#1-what-is-an-audit-check) resolves correctly on GitHub

Summary by CodeRabbit

• Documentation
  • Clarified that audit checks independently re-validate stored interview data.
  • Documented scenarios where data may change or bypass real-time validation.
  • Added guidance to create corresponding audit checks for new real-time validations.

[coderabbitai]

Caution

Review failed

An error occurred during the review process. Please try again later.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[greenscientist]

Frankly I feel you are going into too much details here. I don't feel this is useful to add

[kaligrafy]

#1726

[kaligrafy]

Frankly I feel you are going into too much details here. I don't feel this is useful to add

En fait, je pense que c'est utile, car n'importe qui pourrait se poser la même question que toi: pourquoi les audits + validations temps réel, et donc ça explique pourquoi et ça relance le TODO de convertir tout en objets dans le frontend aussi. Si tu pense que c'est vraiment pas nécessaire, on peut rejeter cette PR.