docs(i18n): #642 correct migration-table note — variants ARE in repo (NO-MATCH = layout artefact) - #658
Merged
Conversation
…t artefact, variants ARE in repo Correction to PR #656's audit-trail note. The original note (and the PR #656 description) stated the 12 NO-MATCH rows were "variant game rules not present in the repo". That conclusion was WRONG. Verified against repo (code=truth): the 4 variants ARE present — Rules_07 (Le Bingo mixologie), Rules_09 (Le dernier beau parleur), Rules_11 (Le moulin à baratin), Rules_13 (La parlote coinchée). The repo holds the full 15-card set. The 12 NO-MATCH are a layout-alignment artefact: the legacy GSheet used a 24-fine-row layout; the repo uses a condensed 15-card structure (#438/#250 restructure). The row-by-row sentence-overlap matcher could not align GSheet title-rows against merged repo cards, so it reported NO-MATCH. The 24->15 restructure lost 0 character (16446 FR chars identical, verified by ai-01). The migration lost no data. The note now documents this correctly. Root-cause of the error: interpreting a matcher's NO-MATCH signal as "content absent from repo" without empirically verifying the repo records exist (pattern [[test-counter-empirical-dotnet-test]]). Co-Authored-By: Claude-Code <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Correction to PR #656's audit-trail note. The original note claimed the 12 NO-MATCH rows were "variant game rules not present in the repo". That was WRONG.
Verified against repo (code=truth)
The 4 variants ARE present in
Cards/Rules/Argumentum Rules - Cards.csv:Rules_07= "Le Bingo mixologie argumentative"Rules_09= "Le dernier beau parleur"Rules_11= "Le moulin à baratin"Rules_13= "La parlote coinchée"Repo holds the full 15-card set (Rules_01..15), not "base game only".
What the 12 NO-MATCH actually mean
A layout-alignment artefact, not missing content. The legacy GSheet used a 24-fine-row layout; the repo uses a condensed 15-card structure (#438/#250 restructure merged each rule into one cell with
\n). The row-by-row sentence-overlap matcher couldn't align GSheet title-rows against merged repo cards → reported NO-MATCH. The 24→15 restructure lost 0 character (16 446 FR chars identical, verified by ai-01).Net
The migration lost no data. The note now documents this correctly so the doc doesn't read as a data-loss record.
Root-cause of the error: interpreting a matcher's NO-MATCH signal as "content absent from repo" without empirically verifying the repo records exist (pattern: [[test-counter-empirical-dotnet-test]]).
Docs-only, base
ca5db818. No risk to content.🤖 Generated with Claude Code