docs(i18n): #642 analyse structurelle GDrive Rules — paste-ready impossible + worklist garbage - #646
Merged
Merged
Conversation
…impossible + worklist garbage Deep-queue PRIMAIRE (dispatch ai-01 msg-c60w1b). L'artefact paste-ready row-level demandé est structurellement impossible: les rangées GDrive (24, granularité fine) traversent les frontières de records repo (15 main + 6 PP, coarser). Preuve: GDrive row 4 chevauche Rules_04 (fin "Le baratineur expose...") ET Rules_05 (debut "### 4. Le jury"); row 5 "En cas d'egalite" est un paragraphe interne a Rules_05, pas RulesPP_06. 17/24 rangées n'ont pas de correspondance rangée-à-rangée propre. Livraison re-cadrée en analyse décisionnelle: - Carte structurelle 24 rangées -> records repo (avec marquage chevauchements) - Inventaire 27 cellules garbage MT residuel avec clean equivalent + record source - Re-cadrage decisions A (A1 collapser / A2 fixing in-place / A3 re-split fragile), B (OAuth vs paste), C (colonnes AR/ES/ZH/FA), D (feuille PP) - Reco po-2024: A2 + B2 (fixing paragraphe-level 27 cellules, preserve structure) Aucun upload GDrive (conforme mandate jsboige + B non tranché). Relates #193, #211, #633, #640. Base master 99145fa. Co-Authored-By: Claude-Code <noreply@anthropic.com>
2 tasks
jsboige
added a commit
that referenced
this pull request
Jul 3, 2026
) Companion artefact to the #642 structural analysis (#646). Records, for each of the 24 legacy GDrive "Cards" rows, the best repo record match + migration verdict: 1 IDENTICAL, 0 PRESERVED, 1 FRAGMENT, 10 GARBAGE-MT, 12 NO-MATCH (variant games not in repo Rules CSV, preserved verbatim in archived tab). Documents the audit trail proving no authentic partner content (juliadespb) was silently lost when Option 3 was applied (2 clean sheets byte-perfect from repo master + legacy tab archived under neutral name). Generated by code from live GDrive snapshot + repo master (code=truth, not hand-authored). Base master cb98905. Co-authored-by: Your <your.email@example.com> 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.
docs(i18n): #642 analyse structurelle GDrive Rules — paste-ready impossible, worklist garbage + décisions
Deep-queue PRIMAIRE (dispatch ai-01 msg-…c60w1b). Cible initiale : produire un
CSV paste-ready (24×5) aligné sur la structure GDrive + diff cell-by-cell sur #642.
Trouvaille bloquante — l'artefact row-level paste-ready est structurellement impossible
Les rangées GDrive (24, granularité fine) traversent les frontières de records repo
(15 main + 6 PP, coarser). Preuve airtight (V1 « École des menteurs ») :
Rules_04finit par…Le baratineur peut écourter la saynète quand il le souhaite.Rules_05commence par### 4. Le juryrow 4commence parLe baratineur expose ses arguments…(= dernier paragraphe de Rules_04) puis### 4. Le jury(= Rules_05) → chevauche 2 recordsrow 5« En cas d'égalité (🥈👇👇) » = paragraphe interne àRules_05, pasRulesPP_0617/24 rangées GDrive n'ont pas de correspondance rangée-à-rangée propre (chevauchent
ou sont des fragments internes). Un artefact construit en remplaçant chaque cellule
GDrive par un record repo serait incorrect (duplication, paragraphes coupés, langues
misalignées). Le contenu propre vit dans le repo mais dans un découpage différent.
Livraison re-cadrée (analyse décisionnelle au lieu de CSV paste-ready)
docs/investigations/2026-07-02-gdrive-rules-642-structural-analysis.md(+178 lignes) :↔chevauchements,∅fragments internes).Roll of the English Channel,Facility,peacher/pêssego,picareta,manga,baratiner) avec cleanéquivalent + record repo source + glossaire verrouillé fix(i18n): refonte traduction Rules — 23 HIGH résolus (PT/RU + purge embromador + glossaire) #633 #640.
paragraphe-level / A3 re-split fragile), B (OAuth vs paste manuel), C (colonnes
AR/ES/ZH/FA), D (feuille PP). Reco po-2024 : A2 + B2.
Impact
(qui aurait écrasé 24→15 rangées en perdant la granularité + misaligné les langues).
gate asset. Le garbage GDrive n'affecte pas les PDFs générés (repo = source CardPen).
Décision attendue (jsboige, via ai-01)
Trancher A2 + B2 (reco) → je livre le fixing paragraphe-level des 27 cellules
garbage (CSV 24×5 préservant la structure, diff cell-by-cell, 0 cellule non-ciblée).
C et D peuvent rester différés (non-bloquants pour nettoyer FR/EN/RU/PT = cœur du
clobber #211).
Relates #193, #211, #633, #640. Base master
99145fab.🤖 Generated with Claude Code