Skip to content

fix: harden automatic matching decisions - #3

Merged
QvarcY merged 1 commit into
mainfrom
fix/automatic-matching-hardening
Sep 26, 2026
Merged

QvarcY merged 1 commit into
mainfrom
fix/automatic-matching-hardening

Conversation

@QvarcY

@QvarcY QvarcY commented Sep 26, 2026

Copy link
Copy Markdown
Owner

Summary

Hardens the automatic comparison path without adding new workflow steps.

Changes

  • gives mapping suggestions explicit key / comparison roles;
  • refuses automatic key selection when multiple identifier candidates are too close;
  • prevents automatic pairing of known semantic groups with conflicting meanings;
  • expands parser regression coverage for TSV, escaped quotes, malformed quotes, corrupt UTF-8 markers, duplicate headers and empty files;
  • adds normalization/percentage-tolerance tests;
  • adds CSV formula-injection regression coverage;
  • updates roadmap state.

Scope

The default product flow remains unchanged:

2 files → automatic local comparison → Visual Diff

If automatic key selection is genuinely ambiguous, the app falls back to manual/expert mapping instead of guessing.

@QvarcY
QvarcY merged commit 30811a7 into main Sep 26, 2026
1 check passed
@QvarcY
QvarcY deleted the fix/automatic-matching-hardening branch September 26, 2026 19:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant