fix(taxonomy): #497 rename crossLink header typo Levarages->Leverages + validation

[jsboige]

What & why

Dispatch secondaire #497 (ai-01 deep-queue, base master 50247b77). The crossLink_Levarages column header is a typo of Leverages. This PR fixes the typo and ships a validation pass of the existing cross-link data so the cluster isn't chasing non-existent defects.

Change

Single header-cell rename, byte-exact:

• crossLink_Levarages → crossLink_Leverages
• Same-length (9-char) substitution on raw bytes — file size (4,071,127 B), byte offsets, UTF-8-no-BOM encoding, and the mixed CRLF+LF newlines are all preserved verbatim. No csv round-trip (which would have normalized newlines and corrupted the file).
• git diff --stat: 1 file changed, 1 insertion(+), 1 deletion(-) — exactly the header line.
• All 1408 data rows byte-identical (row count verified against master).

Zero blast radius (verified before edit)

A repo-wide search confirms no code/config reads the crossLink_* columns by literal name:

• The Fallacy entity + its CsvHelper ClassMap do not map crossLink_* at all — they are passive columns the C# pipeline never parses.
• VirtueMindMapDocumentConfig.cs matched only the crossLink variable/type name, not the header string.
• Git_Archeology_Report.md matched a historical git-diff excerpt, not the column.
• GSheetSync is Enabled = false; no config references the literal typo header.
• The literal token crossLink_Levarages appeared exactly once (this header).

Validation report — the 22 existing cross-link cells

The #497 garde-fou is "aucun lien fabriqué, fail-loud, decimal_path valides, symétrie cohérente". I validated the existing data against the canonical path column (1408 distinct paths). Result: every target resolves (0/22 invalid); no curation needed.

PK	source path	predicate	target path	target PK	valid
3	1.1.1	IsRelatedTo	7.1.2.3	1294	✅
38	1.1.2.1.3.1	Opposes	6.2.1.1.4	982	✅
151	1.3.1.3.3.1	Denounces	5.1.2.3.2	821	✅
152	1.3.1.4	Leverages	5.3.3.1	877	✅
154	1.3.2.1	Leverages	4.1.3.1.1.1	722	✅
332	2.2.2.3	Allows	1.3.2.3.3.1	163	✅
355	2.2.3.4	PredatesOn	1.1.1.1.1	5	✅
358	2.3.1.1	PredatesOn	6.3.1.1.1.2.1	1039	✅
369	2.3.1.1.2	PredatesOn	6.3.1.2.3.1.3.3	1161	✅
377	2.3.1.1.4.1	PredatesOn	6.3.1.1.1.2.1.3	1046	✅
383	2.3.1.1.5	PredatesOn	6.3.1.2.1.1	1092	✅
390	2.3.1.2.3.1	PredatesOn	6.3.1.1.1.2.1.1	1040	✅
439	2.3.2.2.1.1.4	PredatesOn	6.3.1.1.1.2.1.4	1047	✅
440	2.3.2.2.1.1.4.1	PredatesOn	6.3.1.2.3.1.1.3	1151	✅
673	3.3.1.2.2	Mirrors	5.1.2.2.4	814	✅ (reciprocated)
814	5.1.2.2.4	Inverts	5.1.2.2.2	810	✅
814	5.1.2.2.4	Mirrors	3.3.1.2.2	673	✅ (reciprocated ↔ 673)
982	6.2.1.1.4	IsRelatedTo	1.1.2.1.3.1	38	✅ (reciprocated ↔ 38)
1021	6.2.3.4.1	Opposes	6.2.1.1.1	976	✅
1282	7.1.1	Leverages	5.3.2.3.2.1	869	✅
1372	7.3.2.1	Leverages	5.2.3	844	✅
1395	7.3.2.4.3	PredatesOn	6.3.2.3.1.6	1234	✅

Predicate distribution: PredatesOn 9, Levarages→Leverages 4, Opposes 2, Mirrors 2, IsRelatedTo 2, Denounces 1, Allows 1, Inverts 1.

What this PR does NOT do (deliberately)

• No new cross-links added. The garde-fou forbids fabrication, and adding fallacy-relationship semantics requires domain expertise / gpt-5.5 (po-2023 lane) — out of scope for this worker slice. ai-01: if you want relationship additions, please route with a DoD / source.
• No data-cell edits. Validation found nothing broken to curate.
• No code changes. This is a pure CSV header rename.

Scope & review

• 🟡 HELD for ai-01 review (per dispatch: feat(taxonomy): peupler la couche relationnelle transverse (8 liens typés, 23/1408) #497 cross-link slice PRs are held for coordinator review).
• Not gated (jsboige-sanctioned enhancement, hors v0.9.0 gate). No pipeline behavior change (columns are passive).
• The CSV content rule ("never modify before CardPen injection") concerns content escaping, not header schema — a header rename is legitimate and does not touch any data cell.

🤖 Worker po-2024

[clusterManager-Myia]

[NanoClaw]

fix(taxonomy): typo in CSV header Levarages->Leverages.

One character fix in the header row. Trivially correct.

LGTM.