Make PIA's fullest gloss language the one the WebView shows

Importing PIA looked like it produced no glosses. It had produced them - six
records carried an es gloss - but the platform scans interlinear files in
ordinal path order, that order becomes the project's analysisLanguages, and
the WebView renders only analysisLanguages[0]. Interlinear_en sorted ahead of
Interlinear_es, so the language on screen was the deliberately thin one: two
glossed records, both in verse 1, and nothing at all in verses 2 and 3.

PIA's second gloss language is now fr, so Interlinear_es sorts first and the
es glosses are what the view shows. The thin file keeps its job - it still
overlaps es on two tokens so their records merge, and still reads "daxes" as
a single stem where es reads stem plus suffix, so the parses still conflict.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: imnasnainaec

test-data/pt9-projects/PIA/InterlinearSetup.xml

@@ -6,7 +6,7 @@
     <RelatedLanguages>false</RelatedLanguages>
     <ExportOnApprove>false</ExportOnApprove>
   </InterlinearSetup>
-  <InterlinearSetup type="Glossing" language="en">
+  <InterlinearSetup type="Glossing" language="fr">
     <FontSize>12</FontSize>
     <RightToLeft>false</RightToLeft>
     <RelatedLanguages>false</RelatedLanguages>

…IA/Interlinear_en/Interlinear_en_PHP.xml …IA/Interlinear_fr/Interlinear_fr_PHP.xmltest-data/pt9-projects/PIA/Interlinear_en/Interlinear_en_PHP.xml renamed to test-data/pt9-projects/PIA/Interlinear_fr/Interlinear_fr_PHP.xml test-data/pt9-projects/PIA/Interlinear_en/Interlinear_en_PHP.xml renamed to test-data/pt9-projects/PIA/Interlinear_fr/Interlinear_fr_PHP.xml

@@ -1,11 +1,11 @@
 <?xml version="1.0" encoding="utf-8"?>
-<InterlinearData GlossLanguage="en" BookId="PHP">
+<InterlinearData GlossLanguage="fr" BookId="PHP">
   <Verses>
     <item>
       <string>PHP 1:1</string>
       <VerseData>
         <Cluster><Range Index="0" Length="3" /><Lexeme Id="Word:wug" GlossId="s-wug1" /></Cluster>
-        <Cluster><Range Index="4" Length="7" /><Lexeme Id="Word:blicket" GlossId="s-blicket-en" /></Cluster>
+        <Cluster><Range Index="4" Length="7" /><Lexeme Id="Word:blicket" GlossId="s-blicket-fr" /></Cluster>
       </VerseData>
     </item>
     <item>

test-data/pt9-projects/PIA/Lexicon.xml

@@ -18,7 +18,7 @@
       <Entry>
         <Sense Id="s-wug1">
           <Gloss Language="es">uno</Gloss>
-          <Gloss Language="en">one</Gloss>
+          <Gloss Language="fr">un</Gloss>
         </Sense>
         <Sense Id="s-wug2">
           <Gloss Language="es">primero</Gloss>
@@ -31,8 +31,8 @@
         <Sense Id="s-blicket">
           <Gloss Language="es">dos</Gloss>
         </Sense>
-        <Sense Id="s-blicket-en">
-          <Gloss Language="en">two</Gloss>
+        <Sense Id="s-blicket-fr">
+          <Gloss Language="fr">deux</Gloss>
         </Sense>
       </Entry>
     </item>

test-data/pt9-projects/README.md

@@ -43,7 +43,7 @@ it.
 
 | Project | Purpose       | Key features                                                                                                                                                                                                                                                                                                                                                                                |
 | ------- | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `PIA`   | Happy path    | Two gloss languages (`es`, `en`) over one book, so records merge across languages and one token's parses conflict; a phrase cluster; word parses; a word and a parse cluster sharing one range; an approved verse hash; an excluded cluster; a punctuation entry; a repeated surface form, for an ambiguous anchor; every sense-resolution outcome; every bare-word-analysis outcome        |
+| `PIA`   | Happy path    | Two gloss languages (`es`, `fr`) over one book, so records merge across languages and one token's parses conflict; a phrase cluster; word parses; a word and a parse cluster sharing one range; an approved verse hash; an excluded cluster; a punctuation entry; a repeated surface form, for an ambiguous anchor; every sense-resolution outcome; every bare-word-analysis outcome        |
 | `PIB`   | Cluster drops | All five `clusterDrops` reasons (`formMismatch`, `duplicateCluster`, `lemmaOrOther`, `unparseableLexemeId`, `verseNotFound`), plus an `Interlinear_es_JAS.xml` for a book the project has no text for, which reports `bookFound: false`                                                                                                                                                     |
 | `PIC`   | File identity | A canonical book file beside a non-canonical twin of it (`booksDroppedAsDuplicates`, and the canonical file's data is the data that must survive); one file with no `GlossLanguage` and one with no `BookId` (`booksMissingIdentity`); `GlossLanguage="English"` (`tagIsFallback`); `es-MX` and `es-mx`, which stay separate language groups but resolve onto one tag (`sameTagCollisions`) |
 | `PID`   | Lexicon only  | A `Lexicon.xml` and `WordAnalyses.xml` with no interlinear book file at all: the manifest is non-empty, so the import is offered and succeeds, but the conversion has no book to report on and `report.languages` comes back empty                                                                                                                                                          |