@elite-dangerous-almanac/core 0.2.7 → 0.2.9

package/PROVENANCE/i18n/SOURCES.md

@@ -1,7 +1,10 @@
 # Localized game-name catalogues
 
 These catalogues keep the canonical English display names already published by the
-ships data domain and add only localized values carried explicitly by accepted sources.
+ships, equipment, materials and commodities data domains and add only localized values
+carried explicitly by accepted sources. Where a catalogue holds display prose rather
+than a name, the owning domain publishes no English for it and all six values are the
+source's own.
 They are deliberately sparse: absence means that no accepted source carried a value, and
 the lookup API returns `null` for that locale rather than treating English as a
 translation.
@@ -26,33 +29,39 @@ tag follows the rule above, so `pt-PT` resolves to Brazilian Portuguese.
 - **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
+- **Derivation:** every current module symbol and English name comes 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.
+  join is exact and total over the symbols the acquired table covers: every one of them
+  resolves. The **unreleased** Large Planetary Vehicle Hangars postdate that table
+  (§`data/ships/SOURCES.md`) and are joined to a later observation of the same
+  localisation identities instead, acquired 2026-09-02 UTC: it names
+  `Int_LargeBuggyBay_Size{2,4,6}_Class3` and their `_Free` twins in all six locales. It
+  does not name the Mk II line, whose three records carry English alone.
   - **`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
+    as upper bounds over the current symbol set 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
+  - **The `(Free)` grants have no name of their own** — theirs is a template wrapping the
+    base module's. Their canonical English is already the base module's, so they share
+    its record. This covers the six Vessel Hangar grants and the three unreleased Large
+    Planetary Vehicle Hangar grants, observed as "Large Planetary Vehicle Hangar (Free)"
+    and its five translations — each the base name plus a rendered marker.
+- **The in-game table is authoritative over the EDDI and EDSY joins.** It carries 349
+  values absent from those registries and differs from them in 3,135 cells 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 are general — Russian `Двигатели` is `Маневровые двигатели`, 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
@@ -66,19 +75,37 @@ tag follows the rule above, so `pt-PT` resolves to Brazilian Portuguese.
   `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.
+  bare `Schubdüsen` or `Propulseurs` that loses what distinguishes the module. The
+  unreleased Large Planetary Vehicle Hangar's Russian
+  `Крупный гараж для планет. транспорта` joins them: its `планет.` is the only spelling
+  observed, and expanding it to match the shipped hangar's `планетарного` would be this
+  repository writing the translation rather than reading it.
 - **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
+  `Lightweight Alloy` and `Reinforced Alloy` are singular on most 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
+  `Hatch Breaker Limpet Controller` is specific on most symbols and generic on one, and
   the specific is kept.
-- **Coverage:** complete. All 1,194 symbols carry all six locales.
-- **Manual corrections:** none.
+- **Coverage:** complete. Every symbol carries all six locales — but five of those
+  values are **constructed rather than read**; see the manual correction below.
+- **Manual corrections:** the **Mk II** Large Planetary Vehicle Hangar's five non-English
+  names are built, not sourced. Nothing acquired names that unreleased module in any
+  locale but English, and rather than leave the lookups answering `null` the repository
+  owner chose to form each as the plain hangar's own translation with `Mk II` appended —
+  `Großer Planetenfahrzeug-Hangar Mk II`, `Hangar de vehículo planetario Mk II`,
+  `Grand hangar des véhicules planétaires Mk II`,
+  `Hangar de veículo planetário grande Mk II`,
+  `Крупный гараж для планет. транспорта Mk II`. Four locales have a precedent for that
+  shape in the shipped Mk II Vessel Hangar and Mk II Cargo Rack, which suffix `Mk II`;
+  **German does not** — Frontier writes `Mk-II-Schiffshangar` for the hangar and
+  `Frachtgestell für Mk II` for the rack, so the German value here matches neither and is
+  the likeliest of the five to be wrong. All five are to be replaced by a real
+  localisation reading on release, and none should be treated as evidence of what
+  Frontier publishes. #16 tracks them with the records themselves.
 
 ## `blueprint-names.jsonc`
 
@@ -87,11 +114,11 @@ tag follows the rule above, so `pt-PT` resolves to Brazilian Portuguese.
   database version `424009901`, last-modified marker `20260810`.
 - **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 107 current keys and its English name comes from
+- **Derivation:** each current key and its English name comes from
   `data/ships/blueprints.jsonc`. Names remain keyed per blueprint because a single
   English phrase can have different grammatical translations for different module
   families. The Frontier symbol joins case-insensitively to the in-game modification
-  name table, which supplies every locale for the 90 recipes it names. The remaining 17
+  name table, which supplies every locale for the recipes it names. The rest
   are ids this repository keys separately because their numbers differ, where the game
   offers only the generic recipe's menu entry and so publishes only its name: each takes
   the locales of the generic id it shadows — `AFM_Shielded`, `Refineries_Shielded` and
@@ -105,7 +132,7 @@ tag follows the rule above, so `pt-PT` resolves to Brazilian Portuguese.
   canonical name is kept, as it is for every other blueprint. Where EDSY and the in-game
   table disagree the in-game value is kept, as everywhere else in this repository: it
   differs for ten values across four locales, all of them wording, none of them meaning.
-- **Coverage:** complete. All 107 blueprints carry all six locales.
+- **Coverage:** complete. Every blueprint carries all six locales.
 - **Manual corrections:** two values in the in-game table carry a stray leading or
   trailing ASCII space, marked in the acquired table and removed here so a successful
   lookup is already trimmed like every other catalogue name: French `FSD_FastBoot` (which
@@ -118,13 +145,12 @@ tag follows the rule above, so `pt-PT` resolves to Brazilian Portuguese.
 - **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
+- **Derivation:** each current key and its English name comes from
   `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
+  which supplies every locale for all of them. Where it and EDSY disagree, the in-game value
+  is kept, as everywhere else in this repository. It supplies six values EDSY does 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
@@ -134,7 +160,7 @@ tag follows the rule above, so `pt-PT` resolves to Brazilian Portuguese.
   `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.
+- **Coverage:** complete. Every effect carries 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.
@@ -144,7 +170,7 @@ tag follows the rule above, so `pt-PT` resolves to Brazilian Portuguese.
 - **Acquired:** 2026-08-16 UTC.
 - **Odyssey Materials Helper revision:** commit
   `23343c453938e724f317c56e9eb7db0dbfa71f78`.
-- **Derivation:** each of the 146 current symbols and its canonical English name comes
+- **Derivation:** each current symbol and its canonical English name comes
   from the three `data/materials/materials-*.jsonc` catalogues. The lower-cased symbol
   joins directly to the final component of Odyssey Materials Helper's message key in
   `locale/material/horizons/{raw,manufactured,encoded}.csv`; only that row's explicit
@@ -155,14 +181,14 @@ tag follows the rule above, so `pt-PT` resolves to Brazilian Portuguese.
   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
+  evidence. It covers every material in all six locales and, as everywhere else in
+  this repository, wins where the two disagree. That fills the values Odyssey Materials
+  Helper did not carry and restyles others it did: most 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
+  Odyssey Materials Helper uses `’`), the next largest group is 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.
+- **Coverage:** complete. Every material carries 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
@@ -183,26 +209,26 @@ tag follows the rule above, so `pt-PT` resolves to Brazilian Portuguese.
   `23343c453938e724f317c56e9eb7db0dbfa71f78`.
 - **Supplemental source:** in-game verification, acquired 2026-08-16 UTC; immutable
   revision unavailable.
-- **Derivation:** each of the 226 current symbols and its canonical English name comes
+- **Derivation:** each current symbol and its canonical English name comes
   from the four `data/materials/micro-resources-*.jsonc` catalogues. The 196 FDevIDs-backed
   records join directly to the final component of Odyssey Materials Helper's message key
   in `locale/material/odyssey/{asset,consumable,data,good}.csv`; only that row's explicit
-  localized columns are copied. Twenty-eight of the 30 in-game-backed records also have
-  rows in Odyssey Materials Helper, while `PowerVirus` and
-  `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.
+  localized columns are copied. All but two of the in-game-backed records also have
+  rows in Odyssey Materials Helper, the exceptions being `PowerVirus` and
+  `SmallCapacityPowerRegulator`. Every in-game-backed record takes the explicit in-game
+  `name` values for German, Spanish, French and Russian. In both cases the owning
+  catalogue remains authoritative for canonical English names.
 - **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
+  table is the evidence. It covers all but one symbol in all six locales and wins where the
+  two disagree, on the same footing as the material tables above. That fills every
+  remaining value — including the Brazilian Portuguese for `PowerVirus` and
+  `SmallCapacityPowerRegulator`, which no registry carries — and restyles others, mostly
+  the French apostrophe and 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.
+- **Coverage:** complete. Every micro resource carries 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
@@ -223,9 +249,9 @@ tag follows the rule above, so `pt-PT` resolves to Brazilian Portuguese.
   labels are copied verbatim. The join is on family identity rather than on English
   string equality, because the English column of the in-game table *is* the canonical
   English name the ships catalogue took from it.
-- **Coverage:** English covers all 77 families; the five other locales cover the same 58.
-  The 19 without a source-backed label are the families the in-game outfitting screen
-  does not name separately: `axMissileRacks`, `axMultiCannons`, `cargoHatches`,
+- **Coverage:** English covers every family; the five other locales cover only the
+  families the in-game outfitting screen names. The families without a source-backed
+  label are: `axMissileRacks`, `axMultiCannons`, `cargoHatches`,
   `causticSinkLaunchers`, `guardianGaussCannons`, `guardianHybridPowerDistributors`,
   `guardianHybridPowerPlants`, `guardianNaniteTorpedoPylons`, `guardianPlasmaChargers`,
   `guardianShardCannons`, `guardianShieldReinforcementPackages`,
@@ -239,21 +265,21 @@ tag follows the rule above, so `pt-PT` resolves to Brazilian Portuguese.
 - **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
+- **Derivation:** each current key 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
+  experimental-effect description table, which supplies every locale for all of them.
+  All six values, English included, are the source's verbatim.
+- **This catalogue does not project 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
+  kinetic/explosive damage with module splash, say — and most 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.
+- **Coverage:** complete. Every effect carries 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
@@ -264,19 +290,19 @@ tag follows the rule above, so `pt-PT` resolves to Brazilian Portuguese.
 ## `pre-engineered-variant-names.jsonc`
 
 - **Acquired:** 2026-08-18 UTC; the Merc-shop names 2026-08-22 UTC.
-- **Derivation:** all 76 compound identities and English names come from
+- **Derivation:** every compound identity and English name comes from
   `data/ships/pre-engineered.jsonc`. An identity combines the base module symbol,
   blueprint, optional experimental effect and acquisition route. When a variant name
   exactly matches its base module's canonical name, it reuses that record from
-  `module-names.jsonc`; the 41 distinct display records are stored once. Fixed reward
+  `module-names.jsonc`; each distinct display record is stored once. Fixed reward
   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
+- **The Merc-shop rows carry the shop's own names** — the shop
   sells a "Far-Reaching Abrasion Blaster", not an Abrasion Blaster — so they do not reuse
   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
+- **A tech-broker unlock may carry an unlock marker**, and some 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
@@ -300,39 +326,268 @@ tag follows the rule above, so `pt-PT` resolves to Brazilian Portuguese.
     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
+- **Coverage:** English, Brazilian Portuguese and Russian cover every variant. 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.
 
+## `suit-names.jsonc`
+
+- **Acquired:** 2026-09-01 UTC.
+- **In-game localisation revision:** none published; the game ships no immutable
+  identifier for its localisation tables. The acquired table is the evidence.
+- **Derivation:** the four suit families and their canonical English names come from
+  `data/equipment/suits.jsonc`, which stays authoritative for canonical English. Each
+  family's grade symbols join case-insensitively to the in-game suit localisation
+  identity, which carries a `name`, a `longname` and an `info` string per locale. The
+  join is exact and total: every grade symbol resolves.
+  - **`name` is the value taken.** It is the suit's own name and equals the canonical
+    English on all four families.
+  - **The manufacturer is not part of the name.** `longname` prefixes one —
+    `Remlok Maverick Suit`, `Supratech Artemis Suit`, `Manticore Dominator Suit` — which
+    names a Pioneer Supplies listing rather than the suit, so it is rejected the way a
+    rendered capacity is in `module-names.jsonc`. The brand is a proper noun the game
+    leaves in English in every locale, so composing it back on costs nothing but the
+    name it would displace.
+- **A suit is named per family, not per grade.** Every grade of a family carries
+  byte-identical values in all six locales, so one record is stored per family and
+  `nameKeys` maps the family id and every grade symbol onto it. Both forms a consumer
+  holds therefore resolve: `Suit.family` and the `utilitysuit_class3` a journal line
+  writes. The flight suit has a single grade whose symbol *is* the family id, so it
+  contributes one identifier where the other families contribute their family id and
+  each grade symbol.
+- **Coverage:** complete. Every identifier carries all six locales.
+- **Two suits are not stored**, because `data/equipment/suits.jsonc` does not carry them:
+  the five `specialistsuit_class{1..5}` grades, which the source does name
+  (`Specialist Suit`, listed as `Remlok Paragon Specialist Suit`), and `hyperspacesuit`,
+  which carries no text at all. Storing a name for equipment no catalogue owns would
+  leave a lookup answering for something the library cannot otherwise describe.
+- **Manual corrections:** none.
+
+## `suit-descriptions.jsonc`
+
+- **Acquired:** 2026-09-01 UTC.
+- **In-game localisation revision:** none published; the game ships no immutable
+  identifier for its localisation tables. The acquired table is the evidence.
+- **Derivation:** the same four families and the same identifier set as
+  `suit-names.jsonc`, joined to the `info` string of the in-game suit localisation
+  identity. All six values, English included, are the source's verbatim: the owning
+  catalogue publishes no description for a suit, so there is no canonical English here
+  to be authoritative for.
+- **This is display prose, not the suit's stats.** `data/equipment/suits.jsonc` answers
+  what a suit does — shield strength, battery capacity, the four resistances — and the
+  description answers what it is for, naming no figure at all. Neither is projected onto
+  the other.
+- **Coverage:** complete. Every identifier carries all six locales, and every grade of a
+  family shares its record exactly as in `suit-names.jsonc`.
+- **The Specialist Suit grades carry no description at all**, which is a second reason
+  they are absent here beyond the owning catalogue not carrying them.
+- **Manual corrections:** none. The English keeps the source's own mixed apostrophes
+  (`Manticore's`, `a user’s`); they are the game's prose and are stored as published.
+
+## `personal-weapon-descriptions.jsonc`
+
+- **Acquired:** 2026-09-01 UTC.
+- **In-game localisation revision:** none published; the game ships no immutable
+  identifier for its localisation tables. The acquired table is the evidence.
+- **Derivation:** every current weapon symbol comes from `data/equipment/weapons.jsonc`.
+  Each joins case-insensitively to the in-game weapon localisation identity and takes its
+  `info` string; the join is exact and total. All six values, English included, are the
+  source's verbatim, because the owning catalogue publishes no weapon description.
+- **No sibling name catalogue exists**, and that is a decision rather than a gap — see
+  §Names this repository deliberately does not localize.
+- **Coverage:** complete. Every weapon carries all six locales.
+- **Two entries the source carries are not stored:** `wpn_h_launcher_rocket_sauto`
+  (`Karma HL-9`), the heavy rocket launcher no current catalogue owns, and
+  `wpn_m_submachinegun_kinetic_burst`, which the table lists with no text at all.
+- **Manual corrections:** none.
+
+## `personal-modification-names.jsonc`
+
+- **Acquired:** 2026-09-01 UTC.
+- **In-game localisation revision:** none published; the game ships no immutable
+  identifier for its localisation tables. The acquired table is the evidence.
+- **Derivation:** every recipe symbol and its canonical English name comes from
+  `data/equipment/modifications.jsonc`, which stays authoritative for canonical English.
+  A symbol joins case-insensitively to the in-game modification identity as
+  `humanoidmod_<symbol>`, which carries a `name` and a `description` per locale.
+- **The nine technology-specific recipes share the entry the game publishes.** Greater
+  Range, Headshot Damage and Improved Hip Fire Accuracy are one engineering option each
+  in game; this repository keys the Kinetic, Laser and Plasma recipes separately because
+  their material costs differ (§`data/equipment/SOURCES.md`). The `_kinetic`, `_laser`
+  and `_plasma` suffix is dropped before the join, so each of the three takes its generic
+  entry's locales — exactly as a shadowing blueprint id takes its generic's in
+  `blueprint-names.jsonc`. A smaller set of source entries therefore covers every recipe,
+  and the catalogue stores them once each: `nameKeys` maps a recipe symbol onto the entry the
+  game publishes, as `module-names.jsonc` maps a module symbol onto a shared name.
+- **That shape is about visibility, not bytes.** Storing each shared entry three times
+  instead costs about the same, because the duplicate name records weigh roughly what
+  the `nameKeys` map does; the descriptions save about a fifteenth. What the
+  deduplicated form buys is that the sharing is stated in the data, rather than sitting in
+  six duplicate records a later edit could silently pull apart.
+- **`Headshot Damage` is the one English value the game spells differently.** The in-game
+  menu reads `Headshot damage`; the owning catalogue's canonical `Headshot Damage` is
+  kept, as canonical English is kept everywhere in this directory. The lower-case
+  `Stowed reloading` the owning catalogue already carries *is* the game's own spelling
+  and agrees with it.
+- **Coverage:** complete. Every recipe carries all six locales.
+- **One in-game modification is not stored:** `humanoidmod_suit_headshotresistance`
+  (`Increased Helmet Protection`), which `data/equipment/modifications.jsonc` does not
+  carry as a recipe.
+- **Manual corrections:** two German names are the engineering panel's own layout rather
+  than translations. `Kampf-Bewegungs-geschwindigkeit` and `Geräusch-unterdrückung` break
+  a compound word mid-noun, leaving a lower-case second half no German spelling has. The
+  whole word is kept in each, as it is for the wrapped consumables in
+  `micro-resource-names.jsonc`: `Kampfbewegungsgeschwindigkeit` and
+  `Geräuschunterdrückung`.
+
+## `personal-modification-descriptions.jsonc`
+
+- **Acquired:** 2026-09-01 UTC.
+- **In-game localisation revision:** none published; the game ships no immutable
+  identifier for its localisation tables. The acquired table is the evidence.
+- **Derivation:** the same recipe symbols as `personal-modification-names.jsonc`,
+  joined the same way and sharing the generic entry across the nine technology-specific
+  recipes for the same reason. Each takes the identity's `description` string. All six
+  values, English included, are the source's verbatim.
+- **This is display prose, not the recipe's magnitudes.** The game says a modification
+  "allows more ammo to be carried for each weapon" and never how much more; the
+  `modifiers` list in `data/equipment/modifications.jsonc` is what states the multiplier,
+  and the two are deliberately different strings. It is also the only account of the ten
+  recipes whose `modifiers` list is empty — some switch a capability on, the rest move a
+  stat the panel puts no number on (§`data/equipment/SOURCES.md`).
+- **Coverage:** complete. Every recipe carries all six locales.
+- **Manual corrections:** none. The French
+  `weapon_backpackreloading` description keeps the non-breaking space the source sets
+  between a figure and its unit (`5 secondes`), which is French typography rather than
+  layout.
+
+## `personal-tool-names.jsonc`
+
+- **Acquired:** 2026-09-03 UTC.
+- **In-game localisation revision:** none published; the game ships no immutable
+  identifier for its localisation tables. The acquired table is the evidence.
+- **Derivation:** every tool id and its canonical English name comes from
+  `data/equipment/tools.jsonc`, which stays authoritative for canonical English. Each id
+  joins by name to the tool's row in the in-game localisation table, which carries a
+  `name` per locale. The join is exact and total: every id resolves, and every row's
+  English `name` equals the canonical English.
+- **The library id is the only key.** The localisation table keys a tool row by an
+  internal identity no journal field carries (§`data/equipment/SOURCES.md`), so a
+  consumer never holds one and it is not stored. The library id is the single identifier
+  both `getPersonalToolName` and `getPersonalToolById` take, and a second key set would
+  let one of the two answer where the other cannot.
+- **A value equal to the English is the game's own.** The game leaves `Arc Cutter` in
+  English in German, Spanish, French and Brazilian Portuguese, and `Genetic Sampler` in
+  German; Russian translates both. Storing them verbatim is what the sparse contract
+  requires: the lookup answers with a source value and never manufactures an English
+  fallback.
+- **Coverage:** complete. Every tool carries all six locales.
+- **Manual corrections:** none.
+
+## `commodity-names.jsonc`
+
+- **Acquired:** 2026-09-03 UTC.
+- **In-game localisation revision:** none published; the game ships no immutable
+  identifier for its localisation tables. The acquired table is the evidence.
+- **Derivation:** every symbol and canonical English name comes from
+  `data/commodities/commodities.jsonc` and `rare-commodities.jsonc`, which stay
+  authoritative for canonical English. Each symbol joins case-insensitively to the
+  in-game commodity localisation identity, which carries a `name` and an `info` string
+  per locale. `name` is the value taken. The join is exact and total: every commodity the
+  two catalogues hold resolves. The game also names commodity units no catalogue here
+  carries (§`data/commodities/SOURCES.md`); a name with no owning record is not stored,
+  so the key set is the catalogues' and not the game's.
+- **Standard and rare share one catalogue here**, because they share one symbol space
+  and the game names them from one table.
+- **The owning catalogues win the six English disagreements**, as this file's opening
+  rule requires. The game's English name is the shorter or the differently cased
+  spelling in all but the last of them: `Drones` keeps `Limpets` against `Limpet`,
+  `LowTemperatureDiamond` keeps `Low Temperature Diamonds` against
+  `Low Temp. Diamonds`, `AerialEdenApple`,
+  `WatersOfShintara` and `HIPOrganophosphates` keep their `of`, `of` and `HIP` against
+  `Of`, `Of` and `Hip`, and `ThargoidPod` keeps `Xenobiological Prison Pod` against
+  `Thargoid Bio-storage Capsule`. The last is a different name rather than a different
+  spelling, and it is the one to revisit first if the owning catalogue is ever re-derived
+  from the game.
+- **Nine stored non-English values are the game's own abbreviations** — the German
+  `Fortschr. Katalysatoren` and `Histor. Kamorin-Waffen`, the Spanish
+  `Interconect. de eyector térmico` and `Conductos de transf. de energía`, the French
+  `Sys. surveillance animale`, `Sys. enrichissement sols` and
+  `Interconnexion dissipateur therm.`, and the Russian
+  `Агенты нервно-паралит. действия` and `Детали оборон. беспилотников` — and they stay
+  abbreviated because no source spells them out. This is the same position
+  `module-names.jsonc` records for its own abbreviated labels. The English `H.E. Suits`
+  is not one of them: it is the owning catalogue's own name.
+- **Coverage:** complete. Every commodity carries all six locales, and no commodity has
+  five non-English values all byte-identical to its English, so no commodity name is a
+  proper noun the game leaves alone.
+- **The registry's `info` prose is not stored.** Each commodity also carries an `info`
+  string per locale — the market panel's production, consumption and description text. A
+  commodity description catalogue would take those six values verbatim, the way
+  `suit-descriptions.jsonc` does; none exists, so the prose is absent rather than
+  partial.
+- **Manual corrections:** one. The Spanish `BuckyballBeerMats` is published as
+  `"Posavasos Buckyball "` with a trailing space, which is layout and not part of the
+  name; it is stored trimmed. Every other value is verbatim.
+
 ## 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.
+No catalogues are stored for the following names, either because the game does not
+translate them — storing English under five more keys would say otherwise — or because no
+record in this repository is keyed by them.
 
 - **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.
+  a manufacturer's. No source publishes a localized manufacturer label at all.
+  `data/ships/ships.jsonc` is the one place to read both strings.
 - **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
+  outfitting family and publishes no group label of its own. EDSY's `mtype-*` values are
+  outfitting labels reached by a name join and disagree 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`.
+- **Handheld personal-weapon names.** The in-game weapon localisation table publishes all
+  six locales for every weapon, and every non-English value
+  is byte-for-byte the English: `Karma P-15`, `TK Aphelion` and `Manticore Executioner`
+  are product names the game leaves alone, exactly as it does a hull's. `PersonalWeapon`
+  in `data/equipment/weapons.jsonc` is the one place to read the name; the weapons'
+  *descriptions* are prose and are localized, in `personal-weapon-descriptions.jsonc`.
+- **Personal-equipment manufacturers.** `Supratech`, `Remlok`, `Manticore` and
+  `Kinematic Armaments` are byte-for-byte identical in all six locales wherever the game
+  names them, which is why `suit-names.jsonc` stores a suit's own name and not the
+  outfitting list's manufacturer-prefixed listing.
+- **Suit and weapon stat labels, the on-foot loadout panel's rows other than the weapon
+  mounts, and engineer dialogue.** These are the second reason rather than the first: the
+  game does publish all six locales for each, and none of them names a record in any
+  catalogue here. A stat label names a field of `Suit` or `PersonalWeapon`, a panel row
+  names a line of the on-foot loadout screen, and an engineer's line is spoken flavour
+  attached to an offer. Storing them would mean inventing keys this repository does not
+  otherwise own, so a consumer that needs a field label supplies its own. The weapon-mount
+  rows are outside this conclusion: `Suit.mounts` carries Frontier's own journal
+  `SlotName` for each one, so a mount row names a record this repository holds and its
+  localization is a gap rather than an invented key. **This is not the ship slot and
+  restriction gap of [#320](https://github.com/DarkSession/Elite-Dangerous-Almanac/issues/320)**,
+  which is about labels no source translates at all.
 
 ## Known gaps
 
 Localized coverage follows the accepted sources and is not complete for every catalogue or
-stored locale. A language absent from all eight catalogues is the locale decision
+stored locale. A language absent from every catalogue is the locale decision
 recorded above rather than a gap. The accepted sources carry only canonical English for
-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
+the outfitting-family labels listed above, slot and restriction labels, the suit
+weapon-mount labels, fixed reward names, and structured loadout, calculation, SLEF and
+edit messages. A missing source-backed translation that has no issue of its own
+remains tracked by
 [#320](https://github.com/DarkSession/Elite-Dangerous-Almanac/issues/320).
+
+Every suit, handheld weapon, tool and modification the personal-equipment catalogues
+hold is complete in all six locales. That area carries these gaps:
+
+- **The suit weapon-mount labels are English only.** The game publishes all six locales
+  for them, so the values exist to be read. The gap is tracked by
+  [#26](https://github.com/DarkSession/Elite-Dangerous-Almanac/issues/26).