@elite-dangerous-almanac/core 0.2.5 → 0.2.7

package/PROVENANCE/i18n/SOURCES.md

@@ -23,24 +23,61 @@ tag follows the rule above, so `pt-PT` resolves to Brazilian Portuguese.
 
 ## `module-names.jsonc`
 
-- **Acquired:** 2026-08-14 UTC.
-- **EDDI revision:** commit `fdc1f47933bd930464610111fa11fc9dae264414`.
-- **EDSY revision:** commit `e446fbe6e4597dea7ab0bd3105b9a36642388040`;
-  database version `424009901`, last-modified marker `20260810`.
-- **Derivation:** all 1,199 current module symbols and English names come from the four
-  `data/ships/modules-*.jsonc` catalogues. EDDI's `ModuleDefinitions.cs` joins a symbol
-  to a resource key; `Properties/Modules.resx` and its localized siblings supply names.
-  An EDDI value is accepted only when its base English resource exactly equals the
-  Almanac's canonical English name. This prevents broad EDDI families such as
-  `CargoRack`, `MissileRack` and `PlanetaryApproachSuite` from erasing the distinct Mk II,
-  seeker and advanced names the Almanac carries. EDSY's module `fdname` and effective
-  `namekey` fill a missing `de`, `es`, `fr` or `ru` value only when EDSY's English
-  module name also exactly equals the canonical name. Values shared by modules with one
-  canonical name are retained only when they agree, then stored once under that name.
-- **Coverage:** English covers all 1,199 symbols. The explicit translations cover 1,120
-  in German, 1,090 in Spanish, 1,088 in French, 1,155 in Brazilian Portuguese and 1,153
-  in Russian. Portuguese comes from the same two joins, reading EDDI's
-  `Modules.pt-BR.resx` and EDSY's `lang-pt.json`.
+- **Acquired:** 2026-08-30 UTC.
+- **In-game localisation revision:** none published; the game ships no immutable
+  identifier for its localisation tables. The acquired table is the evidence.
+- **Derivation:** all 1,194 current module symbols and English names come from the four
+  `data/ships/modules-*.jsonc` catalogues, which stay authoritative for canonical
+  English. Each symbol joins case-insensitively to the in-game module localisation
+  identity, which carries a `name`, a `longname` and an `info` string per locale. The
+  join is exact and total: every one of the 1,194 resolves.
+  - **`longname` is the name taken.** It is the outfitting list's full name and equals
+    the canonical English on 1,041 of the symbols, where `name` — the abbreviated panel
+    form — equals it on 726. **Both totals were counted over the 1,199-symbol set that
+    preceded the removal of the five plain size-8 drives (§`data/ships/SOURCES.md`), and
+    are not re-derived here:** the in-game localisation table is not vendored, so whether
+    those five sat inside either total cannot be checked from this repository. Read them
+    as upper bounds over 1,194 symbols until the table is re-acquired. `name` is taken
+    only where a longname is a template rather than a name, which is the cargo racks,
+    fuel tanks and corrosion-resistant racks whose longname carries a capacity.
+  - **Aliasing is followed.** A localisation value may be a `$Other_Key;` pointer rather
+    than text; roughly three thousand of the keys are. Each is followed to the entry
+    holding real text before anything is stored, and a value still carrying a `$` token
+    after that is not a name and is rejected.
+  - **The `(Free)` vessel-hangar grants have no name of their own** — theirs is a
+    template wrapping the base hangar's. Their canonical English is already the base
+    module's, so they share its record, exactly as they did before.
+- **This table replaces the EDDI and EDSY joins the catalogue previously used**, and wins
+  where they disagree, as in-game values do everywhere in this repository. It fills the
+  349 values those joins left empty and restyles 3,135 they carried, across 324 distinct
+  record-and-locale pairs: 73 differ only in letter case, 10 only in punctuation or
+  accents, and 241 in wording. Many of the last are the game being specific where the
+  registries were general — Russian `Двигатели` becomes `Маневровые двигатели`, Brazilian
+  Portuguese `Propulsores` becomes `Propulsores de desempenho melhorado`.
+- **The least abbreviated spelling is the one stored**, as it is in
+  `material-names.jsonc`. The outfitting panel shortens a label that will not fit, and
+  that is a rendering rather than a different translation, so where the panel abbreviates
+  the longest unabbreviated spelling available for that module and locale is taken
+  instead — the catalogue's own previous value where it had one, otherwise the source's
+  other field. French `Laser à impuls.` is stored as `Laser à impulsion`, Russian
+  `Разбрас-ль дип. отражателей` as `Разбрасыватель дипольных отражателей`. An
+  unabbreviated candidate is rejected when it is so much shorter that it is plainly a
+  different label rather than the same one spelled out: German `EGM` does not replace
+  `Elektr. Gegenmaßnahmen`. **Ten values remain abbreviated** because no source spells
+  them out — the Mk II gravity-optimised thrusters in four locales, the Advanced
+  Planetary Approach Suite in three, and three others — and there the alternative is a
+  bare `Schubdüsen` or `Propulseurs` that loses what distinguishes the module.
+- **A rendered capacity or grant marker is not a name.** A longname may carry a module's
+  own capacity or a `(Free)` marker — `Anti-Korrosions-Frachtgestell (KAP.: 1)` — which
+  describes one module rather than naming the family, so it is rejected and the source's
+  other field is read instead.
+- **One record per canonical English name.** Where the source distinguishes in another
+  locale what English spells the same way, the reading most symbols share is stored:
+  `Lightweight Alloy` and `Reinforced Alloy` are singular on 25 hulls and plural on the
+  rest, and the singular is kept, which is also the number the English carries.
+  `Hatch Breaker Limpet Controller` is specific on twenty symbols and generic on one, and
+  the specific is kept.
+- **Coverage:** complete. All 1,194 symbols carry all six locales.
 - **Manual corrections:** none.
 
 ## `blueprint-names.jsonc`
@@ -78,16 +115,29 @@ tag follows the rule above, so `pt-PT` resolves to Brazilian Portuguese.
 
 ## `experimental-effect-names.jsonc`
 
-- **Acquired:** 2026-08-14 UTC.
-- **EDSY revision:** commit `e446fbe6e4597dea7ab0bd3105b9a36642388040`;
-  database version `424009901`, last-modified marker `20260810`.
+- **Acquired:** 2026-08-30 UTC.
+- **In-game localisation revision:** none published; the game ships no immutable
+  identifier for its localisation tables. The acquired table is the evidence.
 - **Derivation:** each of the 86 current keys and its English name comes from
-  `data/ships/experimental-effects.jsonc`. The Frontier symbol joins directly to
-  EDSY's `expeffect.fdname`; that record's id selects an explicit `expeffect-<id>` entry
-  from each language file.
-- **Coverage:** English covers all 86 effects; EDSY covers 84 in German and 85 each in
-  Spanish, French, Brazilian Portuguese and Russian.
-- **Manual corrections:** none.
+  `data/ships/experimental-effects.jsonc`, which stays authoritative for canonical
+  English. The Frontier symbol joins to the in-game experimental-effect name table,
+  which supplies every locale for all 86. The table replaces the EDSY join this
+  catalogue previously used: where the two disagree the in-game value is kept, as
+  everywhere else in this repository. It supplies six values EDSY did not carry — all
+  five non-English `special_super_penetrator` names and the German
+  `special_weapon_rateoffire` — and changes two EDSY already carried: German
+  `special_regeneration_sequence` is "Regenerationssequenz" (EDSY
+  "Regenerierungssequenz") and Brazilian Portuguese `special_lock_breaker` is "Quebra da
+  Trava do Alvo" (EDSY "Quebra de Trava de Alvo"). Every other value agrees.
+- **The three `_cooled` variants take their base effect's names.**
+  `special_feedback_cascade_cooled`, `special_plasma_slug_cooled` and
+  `special_super_penetrator_cooled` are pre-engineered rail-gun variants the game does
+  not name separately, so the source marks them as carrying the base effect's entry.
+  Each takes those values, exactly as a shadowing blueprint id takes its generic's.
+- **Coverage:** complete. All 86 effects carry all six locales.
+- **Manual corrections:** the source appends a `†` to every marked cell of the three
+  `_cooled` variants above; it is the acquisition's own shadow marker rather than part of
+  a name, and is removed here.
 
 ## `material-names.jsonc`
 
@@ -100,12 +150,31 @@ tag follows the rule above, so `pt-PT` resolves to Brazilian Portuguese.
   `locale/material/horizons/{raw,manufactured,encoded}.csv`; only that row's explicit
   localized columns are copied. The source's English column is not copied because the
   owning materials catalogues remain authoritative for canonical names. The canonical
-  English values therefore keep the existing `Segment` spelling and omit the source's
-  parenthetical Guardian and Thargoid category labels where the owning catalogue does;
-  localized columns remain verbatim source values.
-- **Coverage:** English, Spanish and Russian cover all 146 materials. The explicit
-  translations cover 128 in German, and 140 each in French and Brazilian Portuguese.
-- **Manual corrections:** none.
+  English values therefore omit the source's parenthetical Guardian and Thargoid
+  category labels where the owning catalogue does; localized columns remain verbatim
+  source values.
+- **Second source, the in-game material localisation tables**, acquired 2026-08-30 UTC;
+  the game publishes no immutable identifier for them, so the acquired table is the
+  evidence. It covers all 146 materials in all six locales and, as everywhere else in
+  this repository, wins where the two disagree. That fills the 30 values Odyssey
+  Materials Helper did not carry and restyles 30 it did: 23 are the French apostrophe
+  (the in-game tables use `'` throughout, as every other catalogue here does, where
+  Odyssey Materials Helper uses `’`), five are Spanish names the helper title-cased
+  (`Fragmento Caústico` against the game's `Fragmento cáustico`), and the rest are
+  wording.
+- **Coverage:** complete. All 146 materials carry all six locales.
+- **Manual corrections:** six of the in-game values are the outfitting UI's own
+  abbreviations, shortened to fit its widget rather than translated differently —
+  `Comp. de destroços Guardian` against the helper's `Componentes de destroços Sentinela
+  Guardian`, and likewise for `Guardian_Sentinel_WeaponParts` (French and Brazilian
+  Portuguese), `Guardian_TechComponent` (French and Brazilian Portuguese) and
+  `HeatConductionWiring` (Spanish). The unabbreviated value is kept in each.
+- **`Guardian_Sentinel_WreckageComponents` drops `Sentinel` in every locale**, following
+  the owning catalogue's rename (see `data/materials/SOURCES.md`). Its Brazilian
+  Portuguese is the one value here taken from neither source verbatim: the in-game table
+  abbreviates it to `Comp. de destroços Guardian` to fit the widget, so the whole word is
+  kept as it is for the other abbreviated labels above, giving
+  `Componentes de destroços Guardian`.
 
 ## `micro-resource-names.jsonc`
 
@@ -123,66 +192,24 @@ tag follows the rule above, so `pt-PT` resolves to Brazilian Portuguese.
   `SmallCapacityPowerRegulator` do not. All 30 take the explicit in-game `name` values for
   German, Spanish, French and Russian. In both cases the owning catalogue remains
   authoritative for canonical English names.
-- **Coverage:** English, Spanish and Russian cover all 226 micro resources. The explicit
-  translations cover 218 in German, 225 in French and 188 in Brazilian Portuguese. The
-  30 in-game-backed records take Portuguese from Odyssey Materials Helper where it has a
-  row, because the in-game capture supplied no Portuguese; `PowerVirus` and
-  `SmallCapacityPowerRegulator`, which the source does not carry at all, have none.
-- **Manual corrections:** none.
-
-## `ship-names.jsonc`
-
-- **Acquired:** 2026-08-18 UTC.
-- **Odyssey Materials Helper revision:** commit
-  `23343c453938e724f317c56e9eb7db0dbfa71f78`;
-  `application/src/main/resources/locale/ships/ships.csv` has SHA-256
-  `6785f7cea00f36ca0a853091fd88f8ed5481a60f55c269643bff1ab0c3d6993d`.
-- **EDSY revision:** commit `e446fbe6e4597dea7ab0bd3105b9a36642388040`;
-  database version `424009901`, last-modified marker `20260810`.
-- **Derivation:** each of the 48 current ship symbols and canonical English names comes
-  from `data/ships/ships.jsonc`. The symbol is joined to Odyssey Materials
-  Helper's `ships.name.*` key after removing punctuation and folding case. EDSY's
-  `eddb.js` `ship.fdname` supplies the second join, with explicit `ship-<id>` language
-  entries filling locales absent from the CSV. The CSV keys a row by the ship's display
-  name rather than its symbol, which differ for the four hulls whose name carries a mark
-  the symbol omits (`Viper` is `ships.name.viper_mk_iii`), so the name is tried first and
-  the symbol second. The resulting source-backed coverage is 48 ships in Spanish, 44 in
-  French, 38 in Brazilian Portuguese and 48 in Russian; no accepted source carries a
-  German ship-name table.
-- **Standing conclusion:** every source-backed non-English value is byte-for-byte equal
-  to the canonical English ship name. The explicit values remain in the catalogue so a
-  lookup distinguishes a source-backed same spelling from an unavailable translation.
-- **Manual corrections:** none.
-
-## `ship-manufacturer-names.jsonc`
-
-- **Acquired:** 2026-08-18 UTC.
-- **Derivation:** all 48 symbol-to-manufacturer values are projected directly from
-  `data/ships/ships.jsonc`, whose pinned sources and corrections are recorded in
-  `data/ships/SOURCES.md`. Repeated manufacturer strings remain keyed by ship symbol so
-  consumers need no separate manufacturer identity space.
-- **Coverage:** canonical English covers every ship. The accepted sources carry no
-  localized manufacturer labels.
-- **Manual corrections:** none.
-
-## `engineering-group-names.jsonc`
-
-- **Acquired:** 2026-08-18 UTC.
-- **EDSY revision:** commit `e446fbe6e4597dea7ab0bd3105b9a36642388040`;
-  database version `424009901`, last-modified marker `20260810`; `lang-en.json` and
-  `lang-ru.json` have Git blob ids `9b199db635f7b968b75c8e9a14bdce68e37e4120` and
-  `36496372d056754c34da03ca6836e27987c96b6a` respectively.
-- **Derivation:** each of the 48 group ids and its canonical English name is projected
-  from `data/ships/engineering-options.jsonc`. That catalogue derives its group menus
-  from EDSY, with the supplemental sources and corrections recorded in
-  `data/ships/SOURCES.md`. Where a canonical English name matches an EDSY `mtype-*`
-  value in `lang-en.json` byte-for-byte and uniquely, explicit values with the same key
-  are copied from `lang-ru.json`.
-- **Coverage:** canonical English covers every engineering option group; Brazilian
-  Portuguese and Russian each cover 44 of 48. The Guardian power-plant, power-distributor
-  and hull-reinforcement groups have no distinct EDSY label, and EDSY carries no value in
-  either language for `frameShiftDrivesSCO`.
-- **Manual corrections:** none.
+- **Second source, the in-game micro-resource localisation tables**, acquired
+  2026-08-30 UTC; the game publishes no immutable identifier for them, so the acquired
+  table is the evidence. It covers 225 of the 226 in all six locales and wins where the
+  two disagree, on the same footing as the material tables above. That fills all 47
+  remaining values — including the Brazilian Portuguese for `PowerVirus` and
+  `SmallCapacityPowerRegulator`, which no registry carries — and restyles 46, of which 36
+  are the French apostrophe and seven are the French Powerplay term, which the game
+  lower-cases (`Données classifiées de puissance`).
+  `PowerMegashipData` is absent from the micro-resource table and appears in the material
+  one; its values are taken from there.
+- **Coverage:** complete. All 226 micro resources carry all six locales.
+- **Manual corrections:** five in-game values are layout, not names. Four German
+  consumables carry a `<br>` inside a compound word that the UI wraps —
+  `Energie-<br>zelle`, `Splitter-<br>granate`, `Schild-<br>unterbrecher` and
+  `Schild-<br>generator` — and the French `Amm_Grenade_EMP` is abbreviated to
+  `Neutralisat. de bouclier` to fit its widget. The whole word is kept in each:
+  `Energiezelle`, `Splittergranate`, `Schildunterbrecher`, `Schildgenerator` and
+  `Neutralisateur de bouclier`.
 
 ## `module-family-names.jsonc`
 
@@ -209,15 +236,30 @@ tag follows the rule above, so `pt-PT` resolves to Brazilian Portuguese.
 
 ## `experimental-effect-descriptions.jsonc`
 
-- **Acquired:** 2026-08-18 UTC.
-- **EDSY revision:** commit `e446fbe6e4597dea7ab0bd3105b9a36642388040`;
-  database version `424009901`, last-modified marker `20260810`.
-- **Derivation:** the 29 effects with a `description` project that canonical English
-  value from `data/ships/experimental-effects.jsonc`. Effects without a source-backed
-  description remain absent rather than receiving generated prose.
-- **Coverage:** canonical English covers 29 of 86 effects. The accepted sources carry no
-  localized description table.
-- **Manual corrections:** none.
+- **Acquired:** 2026-08-30 UTC.
+- **In-game localisation revision:** none published; the game ships no immutable
+  identifier for its localisation tables. The acquired table is the evidence.
+- **Derivation:** each of the 86 current keys comes from
+  `data/ships/experimental-effects.jsonc`; the Frontier symbol joins to the in-game
+  experimental-effect description table, which supplies every locale for all 86. All six
+  values, English included, are the source's verbatim.
+- **This catalogue no longer projects the ships catalogue's `description`.** The two
+  answer different questions and are deliberately different strings. An effect's
+  `description` in `data/ships/experimental-effects.jsonc` is a mechanical note that
+  states what the `modifiers` list cannot — that High Yield Shell deals 50/50
+  kinetic/explosive damage with module splash, say — and 57 of the 86 effects need no
+  such note and carry none. What the game shows a player is display prose that names no
+  magnitudes ("Modified munitions that convert a portion of damage to explosive …"), and
+  it exists for every effect. Projecting one onto the other would have cost the
+  mechanical notes their numbers; storing the display prose here keeps each field doing
+  its own job, and the ships catalogue is unchanged.
+- **Coverage:** complete. All 86 effects carry all six locales.
+- **Manual corrections:** 26 of the source's descriptions begin with one or more
+  bracketed tokens — `[ShieldRegen]`, and `[SnsrBlinding][Heat]` on
+  `special_radiant_canister`. A token is byte-identical across all six locales and is
+  left untranslated in each, so it is an identifier the game's client consumes rather
+  than text meant for a player; the tokens are removed here. The `†` shadow marker
+  described under `experimental-effect-names.jsonc` is removed from descriptions too.
 
 ## `pre-engineered-variant-names.jsonc`
 
@@ -230,23 +272,67 @@ tag follows the rule above, so `pt-PT` resolves to Brazilian Portuguese.
   names such as the three `Decorative_*` festive launchers remain canonical English.
 - **The 22 Merc-shop rows carry the shop's own names**, in 14 distinct records — the shop
   sells a "Far-Reaching Abrasion Blaster", not an Abrasion Blaster — so they do not reuse
-  their base module's record. English and the German, Spanish, French and Russian values
-  are supplied by the repository owner from the in-game shop listing; no registry
-  publishes them.
-- **Coverage:** English covers every variant. Ordinary names inherit the explicit
-  localized values available for their base module, which now includes Brazilian
-  Portuguese on 51 of the 76 variants; the Merc-shop names carry the five locales the
-  repository owner supplied and no Portuguese; fixed reward names have no accepted
-  translation source.
+  their base module's record. All six locales are supplied by the repository owner from
+  the in-game shop listing; no registry publishes them. The Brazilian Portuguese column
+  was acquired 2026-08-30 UTC and agrees byte-for-byte with the five columns already
+  stored, which it does not change.
+- **A tech-broker unlock may carry an unlock marker**, and 19 of them do — see
+  `data/ships/SOURCES.md`. Those names are not their base module's, so they do not reuse
+  its record. Where the marker is a manufacturer (`Sirius`, `Azimuth`) or a version
+  (`V1`) it is not a translatable word, so the localized value is that marker composed
+  with the base module's own localized name: German `Suchraketenrampe V1`, Spanish
+  `Sirius Lanzamisiles AX`. Composition can only reach as far as the base module does,
+  which is why `Frame Shift Drive (SCO) V1` has Brazilian Portuguese and Russian only and
+  `Azimuth Enhanced AX Multi-Cannon` lacks Spanish and French: those are the base
+  modules' own gaps, not new ones.
+- **Six records carry a translation composed in this repository rather than taken from a
+  source, and are the only values in `data/i18n/` that are.** They are marked here
+  because the rest of this directory is explicit source values, and a reader is entitled
+  to know which is which. The game does not publish either phrase in a form this
+  repository can join to:
+  - The three `Modified` Guardian weapons. Unlike `Sirius`, `Azimuth` and `V1`, `Modified`
+    is a translatable word, so it cannot simply be composed with the base module's
+    localized name. Each locale's adjective agrees with the base noun it qualifies —
+    German `Modifizierter Guardian-Plasmalader` against `Modifizierte Guardian-Gausskanone`,
+    Russian `Модифицированная пушка Гаусса` against `Модифицированное осколочное орудие`.
+  - The three `Decorative_*` festive launchers. The game does not translate their names,
+    so `Festive` and the colour are rendered in each locale and qualify the base module's
+    own localized name.
+
+  Replace any of the twelve with a source-backed value the moment one is published.
+- **Coverage:** English covers every variant, and Brazilian Portuguese and Russian now do
+  too. Ordinary names inherit the explicit localized values available for their base
+  module; the Merc-shop names carry all six locales. The German, Spanish and French gaps
+  that remain are their base modules' own — the SCO drive and the Enhanced AX
+  Multi-Cannon carry no value in those locales for composition to build on.
 - **Manual corrections:** none.
 
+## Names this repository deliberately does not localize
+
+Three catalogues were removed rather than completed, because the game does not translate
+what they held and storing English under five more keys said otherwise.
+
+- **Ship names and manufacturers.** Odyssey Materials Helper and EDSY each publish a
+  per-locale ship column, and every value either one publishes is byte-for-byte the
+  canonical English name: a hull name is a proper noun the game leaves alone, and so is
+  a manufacturer's. No source publishes a localized manufacturer label at all. A lookup
+  that can only ever answer in English is not a translation lookup, so `getShipName` and
+  `getShipManufacturer` are gone; `data/ships/ships.jsonc` carries both strings and stays
+  the one place to read them.
+- **Engineering-group labels.** An engineering group is this repository's own partition
+  of the modules that share one menu; the game heads that menu with the module's
+  outfitting family and publishes no group label of its own. The EDSY `mtype-*` values
+  previously stored here were outfitting labels reached by a name join, which is why they
+  disagreed with `module-family-names.jsonc` in 22 places on wording. A group therefore
+  carries no name at all — see the header of `data/ships/engineering-options.jsonc` — and
+  a consumer names one by joining a module's `familyId` to `module-family-names.jsonc`.
+
 ## Known gaps
 
 Localized coverage follows the accepted sources and is not complete for every catalogue or
-stored locale. A language absent from all eleven catalogues is the locale decision
+stored locale. A language absent from all eight catalogues is the locale decision
 recorded above rather than a gap. The accepted sources carry only canonical English for
-ship manufacturers, experimental-effect descriptions, 19 of the 77 outfitting-family
-labels, some engineering-group labels, slot and restriction labels, fixed reward names,
+19 of the 77 outfitting-family labels, slot and restriction labels, fixed reward names,
 and structured loadout, calculation, SLEF and edit messages. Missing source-backed
 translations remain tracked by
 [#320](https://github.com/DarkSession/Elite-Dangerous-Almanac/issues/320).

package/PROVENANCE/materials/SOURCES.md

@@ -26,6 +26,28 @@
     Phosphorus, Sulphur, Iron, Nickel, Rhenium, Lead** — the convention the in-game raw
     grid columns follow.
 
+### Manual correction — the three Guardian blueprint fragments
+
+FDevIDs' `material.csv` names `Guardian_ModuleBlueprint`, `Guardian_WeaponBlueprint` and
+`Guardian_VesselBlueprint` `… Blueprint Segment`. The game calls them **Fragment**, which
+is the name carried here. The in-game localisation table confirmed by repository-owner
+in-game verification (2026-08-30 UTC) says `Fragment` in every locale, and the French and
+Russian columns Odyssey Materials Helper already supplied said `Fragment de plan …` and
+`Фрагмент чертежа …` while its English, German, Spanish and Portuguese said Segment — the
+disagreement was inside one source, not between the game and this repository.
+
+### Manual correction — Guardian Wreckage Components has no Sentinel
+
+FDevIDs names `Guardian_Sentinel_WreckageComponents` `Guardian Sentinel Wreckage
+Components`; the game calls it **Guardian Wreckage Components**, which is the name
+carried here. The symbol keeps Frontier's own `_Sentinel_` spelling, because that is what
+the journal writes. Repository-owner in-game verification, 2026-08-30 UTC; the in-game
+localisation table drops the word in German, Spanish, French and Brazilian Portuguese
+too, and the Russian column Odyssey Materials Helper already supplied had no equivalent
+of it either — `Обломки кораблекрушения Стражей`, against the `часовых Стражей` it uses
+for `Guardian_Sentinel_WeaponParts`. That sibling **keeps** its Sentinel: the game names
+it `Guardian Sentinel Weapon Parts`, so only the wreckage components are renamed.
+
 ### Secondary source — Thargoid caustic / Titan materials absent from FDevIDs
 
 Several Thargoid caustic and Titan materials are absent from the pinned FDevIDs