fix: equal_mode normalized implique case_insensitive + trim sauf override

[VincentGuyader]

Closes #27

Probleme

equal_mode n'etait lu qu'a un seul endroit, ou normalized activait normalize_text(case_insensitive = FALSE, trim = FALSE) - l'identite. Un utilisateur ecrivant equal_mode: normalized seul n'obtenait rien, silencieusement, et test-utils verrouillait meme l'inertie. La vignette documentait pourtant depuis toujours « Apply both transformations ».

Decision (option A de l'issue) : le code s'aligne sur sa propre doc

• normalized implique case_insensitive = TRUE et trim = TRUE pour les colonnes character, un flag explicite (meme FALSE) gagne sur le mode (tri-etat : absent -> suit le mode)
• write_rules_template() cesse de co-ecrire les flags FALSE par defaut a cote d'un mode normalized (ils neutralisaient l'implication - releve par la review interne, le parametre etait un piege inerte) ; un flag explicitement fourni est conserve
• date/datetime/logical : *_equal_mode documentes acceptes-mais-inertes (la normalisation ne touche que character)
• NEWS avertit que les verdicts de YAML manuscrits avec normalized seul peuvent basculer FAIL -> PASS (la normalisation ne fait que fusionner des valeurs)

Tests (TDD red-first)

Test d'inertie retourne + overrides par flag + reprex de l'issue bout-en-bout + template normalized non auto-neutralise (rouges constates).

Suite complete : 1023 PASS / 0 FAIL sur la pile. Check --as-cran : 0 erreur / 0 warning.

Review interne

pr-reviewer : APPROVE, finding important applique (le template auto-neutralisant).

[Copilot]

Pull request overview

This PR fixes the long-standing inconsistency where equal_mode: normalized did not actually apply any normalization, aligning runtime behavior with the documented intent and preventing the YAML template generator from accidentally neutralizing the mode.

Changes:

• Make equal_mode: normalized imply case_insensitive = TRUE and trim = TRUE for character columns unless explicitly overridden per rule.
• Update write_rules_template() to avoid co-writing default FALSE flags alongside equal_mode: normalized (while preserving explicitly supplied flags).
• Add/adjust tests plus update documentation (roxygen/Rd) and NEWS to reflect the corrected semantics and behavioral impact.

Reviewed changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
tests/testthat/test-utils.R	Updates/extends tests to lock in the new implied-default behavior, overrides, issue reprex, and template non-neutralization.
R/preprocessing.R	Implements tri-state behavior: normalized implies defaults unless flags are explicitly set, with normalization driven by resolved flags.
R/compare_datasets_from_yaml.R	Updates parameter docs and adjusts write_rules_template() to omit default FALSE flags when equal_mode = "normalized" unless explicitly supplied.
NEWS.md	Documents the behavior change, rationale, and potential FAIL→PASS flips for hand-written YAML using normalized alone.
man/write_rules_template.Rd	Keeps generated user-facing documentation consistent with the updated equal_mode semantics and caveats for non-character types.

Files not reviewed (1)

• man/write_rules_template.Rd: Generated file

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.