@elite-dangerous-almanac/core 0.2.7 → 0.2.8

package/PROVENANCE/equipment/SOURCES.md

@@ -1,33 +1,38 @@
 # Data sources — `data/equipment/`
 
+## Upstream snapshots this domain is pinned to
+
+Referred to throughout by source name; the pin is here, once.
+
+| Source                                            | Pin                                                                                                                                                            | Acquired       |
+| ------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------- |
+| Odyssey Materials Helper                          | commit `2e6d4c3e767d2b714ffddc5c9386831d66812916` (2026-08-09), the last revision before the project extracted its core data into a separately distributed dependency | 2026-08-13 UTC |
+| Frontier Elite Dangerous Gamestore                | no immutable revision; the displayed weapon names were read on the acquisition date                                                                            | 2026-08-13 UTC |
+| Elite Dangerous in-game observation               | no game version recorded; direct reading of the suit and weapon stats panels, the sight magnification they show, and the on-foot engineering options            | 2026-08-31 UTC |
+
+**Where a source and the game disagree, the in-game reading governs.** Odyssey Materials Helper
+supplies the identities, the slot and grade structure, the engineer availability and
+every material shopping list; the stat values are the ones the game itself shows.
+
 ## Personal suits, handheld weapons and engineering
 
 - **Files:** `suits.jsonc`, `weapons.jsonc`, `upgrade-costs.jsonc`,
   `modifications.jsonc`, `modification-costs.jsonc`,
   `modification-journal-names.jsonc`.
-- **Acquired:** 2026-08-13.
-- **Source:** Odyssey Materials Helper.
-- **Upstream revisions:**
-  - Odyssey Materials Helper commit `2e6d4c3e767d2b714ffddc5c9386831d66812916`
-    (2026-08-09), the last revision before the project extracted its core data into a
-    separately distributed dependency.
-  - Frontier Elite Dangerous Gamestore product pages have no immutable revision; their
-    displayed weapon names were read on the acquisition date above.
 - **Derivation:**
   - `Suit.java` supplies the four suit families, journal symbols, weapon-slot counts and
-    grade-dependent shield strength, shield regeneration, resistances and modification
-    slots. English suit display names come from
+    the grade-dependent modification slots, shield strength and shield regeneration.
+    English suit display names come from
     `application/src/main/resources/locale/loadout/equipment.csv`. `family` removes
     `_class{grade}` from the grade-specific Frontier `symbol`; the exact symbol remains
     on every grade. Shield strength is in shield points, shield regeneration in shield
-    points per second. The source's resistance percentage points are divided by 100 into
-    fractions, matching the resistance convention used by the ships domain (`0.5` means
-    50% resisted).
+    points per second.
   - `Weapon.java` supplies the eleven handheld weapons, their exact journal symbols,
-    class, slot, damage type, fire mode and combat stats. English weapon display names
-    come from `application/src/main/resources/locale/loadout/equipment.csv`. Damage is
-    per projectile or pellet, rate of fire is shots per second, effective range is
-    metres, and the source's headshot percentages are divided by 100 into multipliers.
+    class, slot, damage type, fire mode, magazine size, headshot multiplier and effective
+    range. English weapon display names come from
+    `application/src/main/resources/locale/loadout/equipment.csv`. Damage is per
+    projectile or pellet, rate of fire is shots per second, effective range is metres,
+    and the source's headshot percentages are divided by 100 into multipliers.
   - `OdysseyBlueprintConstants.java` supplies each one-step suit and manufacturer-family
     weapon upgrade recipe, all engineer-applied modification recipes, and the engineers
     who offer them. Enum names are joined to the lower-case Frontier micro-resource
@@ -36,17 +41,134 @@
     the source's `karma`, `takada` and `manticore` identities; `engineeringType` separately
     records the `kinetic`, `laser` or `plasma` suffix used by modification recipes.
   - `SuitModification.java` and `WeaponModification.java` supply the journal symbols.
-    English modification display names come from
-    `application/src/main/resources/locale/loadout/modification.csv`; English engineer
-    names come from `application/src/main/resources/locale/engineer/names.csv`. A recipe
-    is keyed by its symbol rather than by a derived library id. Greater Range, Headshot
-    Damage and Higher Accuracy retain their nine distinct Kinetic, Laser and Plasma
+    English engineer names come from
+    `application/src/main/resources/locale/engineer/names.csv`. A recipe is keyed by its
+    symbol rather than by a derived library id. Greater Range, Headshot Damage and
+    Improved Hip Fire Accuracy retain their nine distinct Kinetic, Laser and Plasma
     recipe symbols. The journal writes only three unsuffixed symbols, so
     `modification-journal-names.jsonc` records that collision once for resolution against
     the weapon. `modification-costs.jsonc` is split from recipe metadata so an identity
     lookup does not bundle every shopping list, matching the ships engineering boundary.
-- **Manual corrections:** Odyssey Materials Helper's English locale calls the four Karma
-  weapons “Kinematic” and expands the three TK weapon names to “Takada”. The Frontier
-  Elite Dangerous Gamestore confirms the in-game prefixes are `Karma` and `TK`, which are
-  stored here. Frontier's misspelled `surveilleancelogs` symbol is kept verbatim so it
-  joins to journal inventory data and the micro-resource catalogue.
+  - **In-game observation supplies every stat value** described in the three sections
+    below: the suit-wide component stats and the four resistances, the weapon combat
+    stats and damage, and the multipliers each modification applies.
+
+- **Manual corrections:**
+  - Odyssey Materials Helper's English locale calls the four Karma weapons “Kinematic”
+    and expands the three TK weapon names to “Takada”. The Frontier Elite Dangerous
+    Gamestore confirms the in-game prefixes are `Karma` and `TK`, which are stored here.
+  - Frontier's misspelled `surveilleancelogs` symbol is kept verbatim so it joins to
+    journal inventory data and the micro-resource catalogue.
+  - Three modification display names are the in-game text rather than the source's:
+    `Faster Shield Regeneration`→`Faster Shield Regen`,
+    `Higher Accuracy`→`Improved Hip Fire Accuracy`, and `Stowed Reloading`→
+    `Stowed reloading`. The last keeps Frontier's own lower-case second word; it reads
+    like a typo and is not one, so do not "fix" it back.
+
+### Suit stats read in-game
+
+The suit stats panel is read per suit family and per grade.
+
+- **Suit-wide, identical at all five grades**, so they are stored once per family rather
+  than per grade: `health` (30 on every suit), `mass` (100 kg on every suit),
+  `batteryCapacity` in energy units, `oxygenTime` in seconds of emergency air,
+  `boostAcceleration` for the jump assist, the three backpack capacities
+  (`goodsCapacity`, `assetsCapacity`, `dataCapacity`), `footstepAudibleRange` as a
+  multiplier of the base audible range (1 on every suit), `losAnalysisRange` in metres
+  (50 on every suit) and `losAnalysisTime` in seconds (1 on every suit). The constant
+  ones are stored anyway: a suit-stats view reads them like any other field, and a value
+  that is the same everywhere is still the value.
+- **Resistances are stored as fractions** (`0.5` means half the damage taken),
+  matching the ships domain. The panel's own figure is the same fraction as a
+  percentage, so a negative resistance is a weakness. Every resistance is now the
+  panel's, which corrects nine grade rows against Odyssey Materials Helper:
+
+  | Suit and grade      | Field → stored value                                                    |
+  | ------------------- | ------------------------------------------------------------------------- |
+  | Artemis 1           | `thermalResistance` 0.39→0.4                                            |
+  | Artemis 2           | `kineticResistance` -0.42→-0.43; `plasmaResistance` 0→-0.01             |
+  | Artemis 3           | `plasmaResistance` 0.14→0.15                                            |
+  | Artemis 5           | `kineticResistance` 0.14→0.15; `plasmaResistance` 0.39→0.4              |
+  | Flight Suit         | `thermalResistance` 0.39→0.4                                            |
+  | Dominator 4         | `kineticResistance` 0.19→0.11; `thermalResistance` 0.78→0.76; `plasmaResistance` 0.46→0.41; `explosiveResistance` 0.46→0.41 |
+  | Maverick 2          | `plasmaResistance` 0.07→0.08                                            |
+  | Maverick 3          | `kineticResistance` -0.13→-0.14                                         |
+  | Maverick 5          | `kineticResistance` 0.19→0.2                                            |
+
+- **Shield strength and shield regeneration are unchanged.** Every stored value already
+  matches the panel, which is also why the resistance disagreements are read as source
+  rounding rather than as a different snapshot of the game.
+- **A grade changes the armour, the shield generator, the modification slots and the
+  item symbol.** Nothing else on a suit moves with the grade, which is what makes the
+  suit-wide fields safe to store once per family.
+
+### Weapon stats read in-game
+
+- **Rate of fire** is the panel's, correcting `Karma AR-50` 9.5→9.52,
+  `TK Aphelion` 5.7→5.71, `Manticore Oppressor` 6.7→6.67, `Manticore Intimidator`
+  1.3→1.25, `Manticore Tormentor` 1.7→1.67, `Manticore Executioner` 0.8→0.833 and
+  `TK Zenith` 5.7→2.78. The Zenith is the one large disagreement and it is not a
+  rounding difference: it fires bursts, and 2.78 is the rate the panel shows.
+- **Reserve ammunition** is the panel's, correcting `Karma P-15` 120→240,
+  `Karma AR-50` 200→250, `TK Eclipse` 280→315 and `TK Zenith` 90→180. It is the reserve
+  a stock suit carries, before the Extra Ammo Capacity modification.
+- **Magazine size, effective range, class, slot, damage type and headshot multiplier**
+  are unchanged: every one already matches the panel.
+- **Damage** is the grade-1 figure read in-game, times the grade multiplier the game
+  applies to it — `1`, `1.31`, `1.73`, `2.27`, `2.98` for grades 1 to 5. Each product is
+  taken in double-precision floating point and rounded to three decimals, as
+  `Number(x.toFixed(3))` does it; that reproduces all 55 stored figures exactly. The
+  rounding rule has to be stated rather than assumed, because twelve products land on a
+  half and are therefore broken in both directions, and because scaling before rounding
+  (`Math.round(x * 1000) / 1000`) re-introduces error and misses eight of the 55.
+- **The multipliers are what Odyssey Materials Helper's own figures follow.** On the four
+  weapons whose grade-1 damage needed no correction — `Karma L-6`,
+  `Manticore Executioner`, `Manticore Tormentor` and `Manticore Oppressor` — its grades 2
+  to 5 sit within 0.05 of the same progression on 15 of those 16 rows, which is half of
+  one decimal — the most a figure rounded to one decimal can move. The exception is `Karma L-6` grade 4: 90.8 here, and
+  90 in that source alone.
+- **Every weapon's damage therefore changes**, and by more than rounding wherever the
+  grade-1 figure itself had been rounded: `Karma C-44` 0.6→0.65, `Karma AR-50` 1→0.95,
+  `TK Eclipse` 0.9→0.85, `Karma P-15` 1.4→1.38, `TK Aphelion` 1.6→1.572, `TK Zenith`
+  1.7→1.668 and `Manticore Intimidator` 1.8→1.75. Damage is stored at the precision the
+  game reports it, which is why two of those grade-1 figures carry three decimals where
+  the panel shows one.
+- **`scopeMagnification` is new**: the aim-down-sights magnification the panel shows with
+  the sight the weapon ships with, and with the sight the Scope modification fits, both
+  to two decimals. Scope stores no modifier of its own because its magnitude is this
+  pair, and it differs per weapon — `Manticore Executioner` gains 1.61x→3.75x where
+  `Manticore Intimidator` gains 1.08x→1.25x.
+
+### Modification magnitudes
+
+Each recipe carries `modifiers`, the stat multipliers it applies. A modification is
+applied in one step and has no grade or quality roll, so a modifier is a single factor
+rather than the `[min, max]` band a ship blueprint feature carries, and `1` — a factor
+that changes nothing — is never stored.
+
+- **Enhanced Tracking effectively removes the analysis delay** rather than shortening
+  it proportionally: its factor on `losAnalysisTime` is `0.001`, which takes the 1 second
+  every suit needs down to a thousandth of one. It is recorded as the factor it applies,
+  like every other modifier.
+- **A resistance factor multiplies the damage taken**, not the stored resistance
+  fraction. Damage Resistance is `×0.9` on damage taken, so a `0.5` resistance becomes
+  `0.55`. This is the same convention the ships domain uses for resistances.
+- **`roundUp` marks the one result the game rounds up**: Magazine Size multiplies by 1.5
+  and rounds the magazine up to a whole number, so 45 rounds become 68 rather than 67.5.
+- **Six recipes name a stat no catalogue field carries**, because the panel shows no
+  base for it: the melee damage, sprint duration and tool energy drain multipliers, the
+  reload speed, and the pressurised and unpressurised firing audible ranges. The factor
+  is recorded against the stat it moves; the base has to come from the panel.
+- **Ten recipes carry an empty modifier list**, for two different reasons, and both are
+  a statement rather than a gap:
+  - Night Vision, Scope, Stowed reloading and Combat Movement Speed apply no factor to
+    any stat. Night Vision and Stowed reloading switch a capability on, Scope's whole
+    numeric effect is the weapon's own `scopeMagnification`, and Combat Movement Speed
+    changes how a suit moves while aiming without moving a displayed stat.
+  - Faster Handling, Improved Hip Fire Accuracy, Stability and Improved Jump Assist do
+    change stats, but ones the panel puts no number on — weapon handling, hip-fire
+    jitter and recoil, and the jump assist's boost drain and recharge. Improved Jump
+    Assist notably leaves the panel's Jump Assist Boost Acceleration exactly where it
+    was, so recording it against that field would be wrong.
+- **Extra Ammo Capacity multiplies a weapon's `reserveAmmo`**, which is why the reserve
+  stored on a weapon is the stock figure and not an engineered one.

package/PROVENANCE/i18n/SOURCES.md

@@ -1,7 +1,9 @@
 # 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.
+These catalogues keep the canonical English display names already published by the ships
+and equipment 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.
@@ -46,13 +48,12 @@ tag follows the rule above, so `pt-PT` resolves to Brazilian Portuguese.
     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
+    module's, so they share its record.
+- **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
@@ -121,10 +122,9 @@ tag follows the rule above, so `pt-PT` resolves to Brazilian Portuguese.
 - **Derivation:** each of the 86 current keys 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 86. 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
@@ -300,39 +300,188 @@ 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: all 16 grade symbols resolve.
+  - **`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 the four
+  families and 16 grade symbols make 19 distinct identifiers rather than 20.
+- **Coverage:** complete. All 19 identifiers carry 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. All 19 identifiers carry 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:** all 11 current weapon symbols come 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. All 11 weapons carry 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:** all 31 recipe symbols and their canonical English names come 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`. 25 distinct source entries therefore cover all 31 recipes, 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 six duplicate name records weigh roughly what
+  the 31-entry `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. All 31 recipes carry 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 31 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. All 31 recipes carry 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.
+
 ## 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 one of the eleven weapons, and each of the 55 non-English values
+  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 row labels, 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 row label names a line of the
+  on-foot loadout panel, 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. **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 all thirteen catalogues 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
+and structured loadout, calculation, SLEF and edit messages. Personal equipment carries
+no gap: every suit, handheld weapon and modification the owning catalogues hold is
+complete in all six locales. Missing source-backed translations remain tracked by
 [#320](https://github.com/DarkSession/Elite-Dangerous-Almanac/issues/320).

package/PROVENANCE/ships/SOURCES.md

@@ -489,8 +489,7 @@ FDevIDs, stats from coriolis-data and EDSY, joined on `symbol`.
   `Manifest Scanners`, `Torpedo Pylons` is `Torpedoes` and `Mine Launchers` is `Mines`.
   The remaining 19 keep the Almanac's own descriptive name, because the outfitting
   screen does not name them separately. Each id is the camelCase form of its English
-  name with punctuation removed, which `modules.test.ts` asserts, so an id and its
-  label cannot drift apart.
+  name with punctuation removed.
 - **Merged families.** Where the game lists several Almanac families under one category,
   they are one family here: the operations, rescue, universal and xeno multi-limpet
   controllers are `multiLimpetControllers`; mining volley repeaters and seismic charge
@@ -856,8 +855,7 @@ damage for the small 1D cannon and **38.5** for the medium 2B cannon. Those read
 settle the registry disagreement in favour of coriolis-data's 22 / 38.5 rather than
 EDSY's 40 / 70. The catalogue stores the displayed values without further derivation and
 applies the same correction to their exact thermal and anti-xeno components. The two
-records are pinned in `fixtures/ships/module-stats.jsonc`. A panel reading has no upstream
-immutable revision.
+panel readings have no upstream immutable revision.
 
 **Values that look wrong and are not.** Three records break the pattern their family
 follows and are confirmed outright by EDSY. Recorded so the "breaks its family's curve"
@@ -951,8 +949,8 @@ and bulkhead name because those records carry no symbol upstream.
     where both registries publish a multiple of 10 still differ by 10
     (`Int_FighterBay_Size{6,7}_Class1`, `Int_PassengerCabin_Size6_Class1`), which no
     rounding explains: whatever the real price is, at least one of the two registries is
-    wrong about it by five credits or more, and neither says which. Two of the three are
-    now settled by in-game readings, and coriolis is exactly right in both:
+    wrong about it by five credits or more, and neither says which. In-game readings
+    settle two of the three, with coriolis exactly right in both:
     `Int_FighterBay_Size7_Class1` is 2 369 320 and `Int_FighterBay_Size6_Class1` is
     1 869 340, so EDSY's 2 369 330 is the wrong member of that pair (see "Prices read from
     an in-game purchase capture" below). So treat 12 560 as
@@ -1073,7 +1071,7 @@ and size-6 racks): here the discount is stated rather than solved for.
 - **The size-8 SCO drives are priced identically to their size-7 siblings.** All four
   distinct readings land exactly on coriolis's size-7 figures (6 838 548, 20 515 645,
   61 546 935), and EDSY's size-8 numbers are those same figures rounded to 10. The
-  catalogue previously carried the EDSY rounding; it now carries the readings.
+  catalogue carries the exact readings rather than EDSY's rounded figures.
 - **A known residual.** `Int_CorrosionProofCargoRack_Size4_Class1` at 94 330 predicts
   82 775 under this rule where `journal-the-deep-black.jsonc` reads **82 774**. It is one
   of a minority of records whose catalogue list price appears to sit a credit or two above
@@ -1234,9 +1232,8 @@ Records not in coriolis-data / FDevIDs at the acquired revisions:
     modules checked numerically, and "every FSD field 72/72" — figures that could not have
     been true of five records the game does not offer. The corrected accounting is 1188
     identity matches, 947 non-armour modules and 67/67 FSD fields, with
-    `registryOnlyIdentities` unchanged at 6; `fixtures/ships/module-stats.jsonc` carries
-    the same numbers. This is a manual correction to previously published provenance, not
-    a re-derivation from a new capture.
+    `registryOnlyIdentities` at 6. Those are the standing audit figures; the source
+    capture itself has not changed.
 - **1B Shield Generator** (`Int_ShieldGenerator_Size1_Class4`) — a gap in FDevIDs, not
   in the game: every other shield-generator size carries all five ratings, and size 1
   ran E/D/C/A with **B missing**. The module is real, so the record is carried with the
@@ -1638,9 +1635,9 @@ up straight through with no disambiguation at all. Both paths are evidence that
   `blueprints` and `experimentals` it offers.
 - **A group carries no display name.** The grouping is this repository's own partition of
   the modules sharing one menu; the game publishes no engineering-group label, heading
-  each menu with the module's outfitting family instead. EDSY's `mtype-*` strings, which
-  this file previously stored as group names, are outfitting labels reached by a name
-  join — which is why they disagreed with `module-families.jsonc` in 22 places on wording
+  each menu with the module's outfitting family instead. EDSY's `mtype-*` strings are
+  outfitting labels reached by a name join and disagree with `module-families.jsonc` in
+  22 places on wording
   (`cannons` Russian "Пушки" against the family's "Орудия", `moduleReinforcements`
   Brazilian Portuguese title case against the family's sentence case). Consumers name a
   group by joining a module's `familyId` to `module-families.jsonc`. The two partitions
@@ -1919,11 +1916,6 @@ whose thermal-cascade tech-broker row is a Seeker Missile Rack V1 while its thre
 community-goal rows are plain. Two tech-broker rows carry no marker at all and keep their
 base module's name: the Mining Laser and the size-5 Frame Shift Drive.
 
-This repository's own fixtures already described several of these under the corrected
-names — `pre-engineered.jsonc` calls one row "the tech-broker 'Modified Guardian Shard
-Cannon'" and another "a V1 FSD" — while `name` carried the plain module's. The data now
-agrees with the prose.
-
 ### Festive variants
 
 - **File:** `pre-engineered.jsonc`. Three grade-5 records pair

package/README.md

@@ -141,11 +141,12 @@ data-free leaf modules under `ships/jump-range`, `ships/power`, `ships/shields`,
 
 `build.validation()` reports validity and operational completeness. `cargoCapacity`,
 `passengerCapacity`, `fuelCapacity` and `unladenMass` always have an answer, because no
-article the catalogue cannot weigh reaches a build; the eight metrics that depend on
-build state (`mobilityMetrics`, `mobilityCapacitorMetrics`, `shieldMetrics`,
-`shieldCapacitorMetrics`, `shieldRecovery`, `heatMetrics`, `distributorMetrics` and
-`standardLoad`) are nullable and each has a `…Result` counterpart naming what is
-missing, switched off, shed or unpowered. `parseSlef`
+article the catalogue cannot weigh reaches a build. The eight build-state methods
+(`mobilityMetricsResult`, `mobilityCapacitorMetricsResult`, `shieldMetricsResult`,
+`shieldCapacitorMetricsResult`, `shieldRecoveryResult`, `heatMetricsResult`,
+`distributorMetricsResult` and `standardLoadResult`) return a diagnostic result whose
+value is either complete or `null`, with issues naming what is missing, unresolved,
+switched off, shed or invalid. `parseSlef`
 is strict; `inspectSlef` is the tolerant importer for mixed files and returns indexed
 diagnostics instead of silently dropping entries.
 
@@ -172,16 +173,30 @@ import {
     getMicroResourceName,
     getModuleName,
     getOutfittingFamilyName,
+    getPersonalModificationName,
+    getSuitName,
 } from '@elite-dangerous-almanac/core/i18n';
 
 getModuleName('Int_Hyperdrive_Size6_Class5', 'de-DE'); // -> "Frameshiftantrieb"
 getBlueprintName('FSD_LongRange', 'fr-FR'); // -> "Portée FSD améliorée"
 getMaterialName('GridResistors', 'de'); // -> "Gitterwiderstände"
 getMicroResourceName('graphene', 'fr'); // -> "Graphène"
+getSuitName('explorationsuit_class3', 'de'); // -> "Artemis-Anzug"
+getPersonalModificationName('suit_nightvision', 'fr'); // -> "Vision nocturne"
 getOutfittingFamilyName('shieldGenerators', 'de'); // -> "Schildgeneratoren"
 getOutfittingFamilyName('xenoScanners', 'de'); // -> null
 ```
 
+Display prose the game shows a player — a suit's or a handheld weapon's blurb, what an
+experimental effect or an engineer's modification does — has its own lookups in the same
+`i18n` area, each on its own subpath, complete in all six locales:
+
+```ts
+import { getSuitDescription } from '@elite-dangerous-almanac/core/i18n/suits';
+
+getSuitDescription('utilitysuit', 'en')?.slice(0, 20); // -> "The Maverick suit is"
+```
+
 The functions return an explicit source value verbatim, so a source-backed spelling may
 happen to equal English; the library itself never supplies an English fallback. The
 catalogues carry English, French, German, Portuguese, Russian and Spanish, each stored

package/THIRD_PARTY_NOTICES.md

@@ -161,7 +161,10 @@ a verbatim copy produced at build time — edit this file, never the copy.
   with its [announcement](https://x.com/EliteDangerous/status/1812792503776489745).
   Frontier's own **in-game localisation** supplies the outfitting category labels behind
   the module families and their German, Spanish, French, Brazilian Portuguese and Russian
-  display text, and the engineering modification names in the six stored locales.
+  display text, the engineering modification names in the six stored locales, and the
+  personal-equipment display text in `data/i18n/`: the suit names and descriptions, the
+  handheld-weapon descriptions, and the names and descriptions of the engineer-applied
+  suit and weapon modifications.
   Values read directly from the running game are Frontier's too — see the notice below.
 - **A [community description](https://www.reddit.com/r/EliteDangerous/comments/1uk2zhp/plasma_laser_theorycrafting_following_new/)
   by u/Techno3020** — linked only as corroboration that the Operations Plasma conversion's