@elite-dangerous-almanac/core 0.2.8 → 0.2.10

package/PROVENANCE/astro/SOURCES.md

@@ -24,9 +24,9 @@
 
 ## Nebulae
 
-- **Files:** `nebulae-real.jsonc` (180 catalogued real-world nebulae and dark regions),
-  `nebulae-procgen.jsonc` (166 procedurally generated nebulae) and
-  `nebulae-planetary.jsonc` (5489 planetary nebulae), split by class.
+- **Files:** `nebulae-real.jsonc` (catalogued real-world nebulae and dark regions),
+  `nebulae-procgen.jsonc` (procedurally generated nebulae) and
+  `nebulae-planetary.jsonc` (planetary nebulae), split by class.
 - **Source:** the EDAstro nebulae coordinates dataset (`nebulae-coordinates.csv`, columns
   `Name,System,X,Y,Z,Type,RegionID`). Original observations are community exploration
   data.
@@ -36,10 +36,10 @@
 - **Derivation:** records retain their name, catalogued system, galactic X/Y/Z in
   light-years with Sol at the origin, class and region id. They are grouped by `type`
   into one file per class and sorted by name; the class is represented by that file and
-  is not repeated on every record. In the planetary file, `system` is omitted for the
-  5210 records where it is identical to `name`; all 279 differing systems remain.
+  is not repeated on every record. In the planetary file, `system` is omitted where it
+  is identical to `name`; every differing system remains.
   `regionId` is the galactic codex region id from the source CSV — a column the
-  canonn-signals JSON drops — and all 5835 values were verified to agree with this
+  canonn-signals JSON drops — and every value was verified to agree with this
   project's own codex-region lookup.
 - **Caveat:** a nebula is a volume, but the dataset records a single point — the position
   of the system it is catalogued at.
@@ -52,18 +52,19 @@
   permit flag), so the list is hand-maintained by the community and is best-effort.
 - **Obtained via:** canonn-signals, `src/app/data/permit-locked-systems.ts`, which
   transcribes the sheet into two arrays.
-- **Derivation:** the 54 exact system names are carried over unchanged and sorted
-  case-insensitively. Permit state is split by lookup domain. The 28 region entries are
+- **Derivation:** the exact system names are carried over unchanged and sorted
+  case-insensitively. Permit state is split by lookup domain. The region entries are
   names of regions in
   `hand-authored-regions.jsonc`, which stores their spheres and nothing about permits.
   Each name doubles as the matching prefix, because the game names every system in a
   region after it (`Col 70 Sector AA-D b17-0`). The upstream list matches 19 lower-cased
   stems instead; the two agree except for the digit-suffixed regions, which the region
   names resolve exactly.
-- **System addresses:** `id64` comes from Spansh for 53 of the 54, cross-checked against
-  EDSM for the 38 EDSM holds, with no disagreement in address or coordinates. The
-  remaining 16 are absent from EDSM entirely, which is expected of systems no commander
-  can enter to report. `Plaa Ain HA-Z d46` is in neither service; it is procedurally
+- **System addresses:** `id64` comes from Spansh for every system but one, cross-checked
+  against EDSM wherever EDSM holds the system, with no disagreement in address or
+  coordinates. EDSM holds no entry at all for the rest — expected of systems no commander
+  can enter to report — so their addresses rest on Spansh alone, with one exception.
+  `Plaa Ain HA-Z d46` is in neither service; it is procedurally
   named, so its address is encoded by this project's own procedural system encoder, whose
   output was confirmed against Spansh on the other two procedural entries in the list
   (`Dryio Flyuae IC-B c1-377`, `Scheau Bli NB-O d6-1409`). Values are stored as decimal

package/PROVENANCE/commodities/SOURCES.md

@@ -1,12 +1,14 @@
 # Data sources — `data/commodities/`
 
 **Acquired:** FDevIDs 2026-07-24 UTC; player-journal record 2026-08-02 UTC; in-game
-category verification 2026-08-12 UTC. **Upstream revision:** unavailable. One record
-combines the latter two sources, documented under Standard commodities.
+category verification 2026-08-12 and 2026-09-03 UTC; in-game commodity registry
+2026-08-02 and 2026-09-03 UTC. **Upstream revision:** unavailable. One record combines
+the journal and in-game sources, and the difference between the two registry readings
+supplies the tail; both are documented under Standard commodities.
 
 ## Standard commodities
 
-- **File:** `commodities.jsonc` (257 tradable goods).
+- **File:** `commodities.jsonc` (the tradable goods).
 - **Source:** EDCD FDevIDs, `commodity.csv` (columns `id,symbol,category,name`).
 - **Derivation:** records are carried over in registry order as
   `{ symbol, name, category }`. `symbol` is Frontier's internal id as the market and
@@ -22,14 +24,56 @@ combines the latter two sources, documented under Standard commodities.
   `symbol` (`Type`) and `name` (`Type_Localised`) verbatim. A `MarketBuy` carries **no
   category**; `Industrial Materials` is separately observed in the running game's commodity
   market (2026-08-12 UTC; no immutable revision). The record is appended after the registry
-  order rather than inserted into it, so FDevIDs order is still recoverable by dropping the
-  tail. Standard rather than rare: a `MarketBuy` of 388 units far exceeds any rare's
+  order rather than inserted into it, so FDevIDs order is still recoverable by dropping
+  it and every record after it. Standard rather than rare: a `MarketBuy` of 388 units far exceeds any rare's
   per-station allocation. The event's `Count`, `BuyPrice`, `TotalCost` and `MarketID` are
   dropped — this is an id/name/category registry, not a price sheet.
 
+### The tail, from the running game's own commodity registry
+
+The game defines more commodity units than the FDevIDs snapshot carries. The registry is
+read from the running game (2026-09-03 UTC; the game publishes no immutable identifier
+for it, so the observation is the evidence) and compared against an earlier reading of
+the same registry (2026-08-02 UTC). **The units the registry gained between the two
+readings are appended, in symbol order, after `curatedcommodity`**: `Bastnasite`,
+`Deuterium`, `Diamond`, `Helium`, `Helium3`, `Iridium`, `Magnesite`, `Olivine`,
+`PericlaseDunite`, `QuartzPyroxenite`, `Ruby`, `Sapphire` and `Thortveitite`.
+
+- **The symbol and the English name are the registry's**, and the name comes from the
+  same in-game localisation table that `data/i18n/commodity-names.jsonc` is derived from,
+  so an appended record's `name` and its English localized name are one string by
+  construction.
+- **The category is separately verified in the running game** (2026-09-03 UTC; no
+  immutable revision), exactly as `curatedcommodity`'s is. The registry names a unit and
+  its display name and does not say which market group it belongs to. Every one of these is
+  `Minerals` except `Helium` and `Helium3`, which are `Chemicals`.
+- **They are stored as standard, not rare.** The registry's English description marks a
+  rare good with the phrase "This rare good". No appended unit carries the marker, no
+  appended unit appears in FDevIDs' `rare_commodity.csv`, and every unit the marker does
+  name is already in `rare-commodities.jsonc`. The marker alone would be weak evidence,
+  because its absence does not make a good standard: five records the rare catalogue
+  holds — `GalacticTravelGuide`, `Nanomedicines`, `Duradrives`, `ApaVietii` and
+  `ClassifiedExperimentalEquipment` — are described without the phrase and keep their
+  place, because the CSV lists them. Here every source is silent together.
+- **The units both readings already held are deliberately not carried.** The registry
+  has long held goods no market lists — powerplay cargo, mission and event freight, and
+  legacy units such as `Wood`, `Ceramics` and `Anthracene`. They are not a change the
+  game made, and carrying them is a separate decision about how wide this catalogue
+  reaches rather than a currency update. What would carry them is that decision plus a
+  category for each, not a new source: the same observation already names them.
+- **Units the game names in no language stay out in any case.** The registry holds units
+  whose localisation entry is empty in all six languages — `Advert2`,
+  `BacteriostaticAgents`, `NvidiaTitanBlack` and others of that kind. A record needs a
+  display name, and the only string available for these is the internal symbol, which is
+  not a name. All of them predate this observation, so the rule above already excludes
+  them; it stands as the second reason.
+- **Appending rather than inserting keeps every earlier order recoverable**, exactly as
+  the `curatedcommodity` record does: drop these records and the order that preceded
+  them remains, and drop `curatedcommodity` as well and the FDevIDs order remains.
+
 ## Rare commodities
 
-- **File:** `rare-commodities.jsonc` (142 location-specific luxury goods).
+- **File:** `rare-commodities.jsonc` (the location-specific luxury goods).
 - **Source:** EDCD FDevIDs, `rare_commodity.csv` (columns
   `id,symbol,market_id,category,name`).
 - **Derivation:** records are carried over in registry order as

package/PROVENANCE/equipment/SOURCES.md

@@ -8,19 +8,21 @@ Referred to throughout by source name; the pin is here, once.
 | ------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------- |
 | 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 |
+| 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, and direct observation of what a suit's two defensive layers resist and of what a weapon does when it is fired | panels 2026-08-31 UTC; firing behaviour 2026-09-03 UTC; suit shield resistances 2026-09-04 UTC |
+| EDCD/EDMarketConnector                            | commit `2b6a0ce1ee3ba60c21f3f4e9fa093046da8825e4` (2026-07-26); `monitor.py` sha256 `800720e04e3089ee9a4b57749de56061e8d31ba877e17f1420f994c52bac08ac`                | 2026-09-02 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.
+every material shopping list; the stat values are the ones the game itself shows,
+except where a derivation bullet below names the source that supplies one.
 
 ## Personal suits, handheld weapons and engineering
 
-- **Files:** `suits.jsonc`, `weapons.jsonc`, `upgrade-costs.jsonc`,
+- **Files:** `suits.jsonc`, `weapons.jsonc`, `tools.jsonc`, `upgrade-costs.jsonc`,
   `modifications.jsonc`, `modification-costs.jsonc`,
   `modification-journal-names.jsonc`.
 - **Derivation:**
-  - `Suit.java` supplies the four suit families, journal symbols, weapon-slot counts and
+  - `Suit.java` supplies the four suit families, journal symbols, weapon-mount counts and
     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
@@ -40,6 +42,14 @@ every material shopping list; the stat values are the ones the game itself shows
     `4_5` to their target grades `2` / `3` / `4` / `5`. Weapon upgrade families retain
     the source's `karma`, `takada` and `manticore` identities; `engineeringType` separately
     records the `kinetic`, `laser` or `plasma` suffix used by modification recipes.
+  - `Suit.java`, `StaticStat.java` and `DynamicStat.java` supply the Energylink, the
+    Profile Analyser, the Arc Cutter and the Genetic Sampler.
+    The source models a tool as a suit stat rather than as an item, and that is what
+    supplies the availability: the Arc Cutter figure appears on `MAVERICK` only, the
+    Genetic Sampler figure on `ARTEMIS` only, and the Energylink and Profile Analyser
+    figures sit in the shared `genericStats` list. `suitFamilies` therefore holds
+    `utilitysuit` for the Arc Cutter, `explorationsuit` for the Genetic Sampler, and all
+    four suit families for the other two.
   - `SuitModification.java` and `WeaponModification.java` supply the journal symbols.
     English engineer names come from
     `application/src/main/resources/locale/engineer/names.csv`. A recipe is keyed by its
@@ -49,14 +59,28 @@ every material shopping list; the stat values are the ones the game itself shows
     `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.
-  - **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.
+  - **`mounts` carries Frontier's own journal `SlotName` for each weapon mount.**
+    EDMarketConnector's `monitor.py` quotes verbatim `SuitLoadout`, `CreateSuitLoadout`,
+    `SwitchSuitLoadout`, `LoadoutEquipModule` and `LoadoutRemoveModule` events in its
+    comments; those are Frontier game output rather than that project's own code. They
+    give `PrimaryWeapon1` and `SecondaryWeapon` on `utilitysuit_class1`, and
+    `PrimaryWeapon1`, `PrimaryWeapon2` and `SecondaryWeapon` on `tacticalsuit_class1`.
+    **The secondary mount carries no number**: the game writes `SecondaryWeapon`, not
+    `SecondaryWeapon1`. Each suit's mount list is the weapon-mount counts this catalogue
+    already held, joined to those keys, primary mounts first and numbered from 1.
+  - **In-game observation supplies the stat values** in the suit, weapon and
+    modification sections below: the suit-wide component stats and both resistance sets,
+    the weapon combat stats and damage, and the multipliers each modification applies.
+    The reload times are the exception: the panel shows no reload figure, so
+    `Weapon.java` supplies them. The tool figures are Odyssey Materials Helper's,
+    converted as the suit-tool section states.
 
 - **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.
+  - Odyssey Materials Helper calls the Profile Analyser the “profile scanner”. The
+    in-game name is `Profile Analyser`, which is 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:
@@ -67,7 +91,7 @@ every material shopping list; the stat values are the ones the game itself shows
 
 ### Suit stats read in-game
 
-The suit stats panel is read per suit family and per grade.
+The suit stats are 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),
@@ -75,32 +99,73 @@ The suit stats panel is read per suit family and per grade.
   `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:
+  (50 on every suit) and `losAnalysisTime` in seconds (1 on every suit), plus the four
+  shield resistances described below. 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.
+- **A suit defends in two layers, and each layer has its own four resistances.** The
+  shield takes the damage first, and the armour takes what gets through. The two sets are
+  therefore stored separately, and each names the layer that has it. Damage Resistance is
+  the armour's modification: it moves the armour set and leaves the shield set alone.
+  Frontier's own symbol for it, `suit_improvedarmourrating`, is the evidence for that.
+- **Both sets are stored as fractions** (`0.5` means half the damage taken), matching
+  the ships domain, and a negative value is a weakness.
+- **The armour resistances are the four the suit panel shows.** The panel gives each one
+  as a percentage; the catalogue stores the same figure as a fraction. Every one is the
+  panel's figure, 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.
+  | Artemis 1           | `armourThermalResistance` 0.39→0.4                                      |
+  | Artemis 2           | `armourKineticResistance` -0.42→-0.43; `armourPlasmaResistance` 0→-0.01 |
+  | Artemis 3           | `armourPlasmaResistance` 0.14→0.15                                      |
+  | Artemis 5           | `armourKineticResistance` 0.14→0.15; `armourPlasmaResistance` 0.39→0.4  |
+  | Flight Suit         | `armourThermalResistance` 0.39→0.4                                      |
+  | Dominator 4         | `armourKineticResistance` 0.19→0.11; `armourThermalResistance` 0.78→0.76; `armourPlasmaResistance` 0.46→0.41; `armourExplosiveResistance` 0.46→0.41 |
+  | Maverick 2          | `armourPlasmaResistance` 0.07→0.08                                      |
+  | Maverick 3          | `armourKineticResistance` -0.13→-0.14                                   |
+  | Maverick 5          | `armourKineticResistance` 0.19→0.2                                      |
+
+- **The shield resistances are 0.6 kinetic, -0.5 thermal, 0 plasma and 0.5 explosive.**
+  The suit panel puts no figure on them. Each one is observed in-game as the multiplier
+  the shield applies to that damage type. A resistance is `1 −` that multiplier. Every
+  suit carries the same four multipliers at every grade. Reading each suit at each grade
+  establishes that.
+- **Shield strength and shield regeneration match the panel.** That agreement is also why
+  the armour-resistance disagreements above are read as source rounding rather than as a
+  different snapshot of the game.
+- **A grade changes the armour resistances, the shield's strength and regeneration, the
+  modification slots and the item symbol.** Nothing else on a suit changes with the
+  grade, which is what makes the suit-wide fields safe to store once per family.
+
+### Suit tools
+
+- **A tool has no Frontier symbol, so `id` is this library's own key.** Odyssey Materials
+  Helper models the tools as suit stats and its English locale table has no tool row. The
+  game's own localisation table does name each tool, under an internal identity no
+  journal field carries: a
+  `SuitLoadout` names the suit and its weapon mounts only, and a `BackpackChange` reports
+  consumables, components, data and goods moving in and out of the backpack, never a
+  tool. Each `id` is the English name in lower case — `energylink`, `profile-analyser`,
+  `arc-cutter`, `genetic-sampler` — and joins to no journal field.
+- **Every power figure is normalised to MW, the unit `Suit.batteryCapacity` uses**, so a
+  suit's battery divided by a tool's per-second drain is seconds of use. The source's
+  600 kW/s Energylink discharge rate is stored as `0.6`, and its 40, 150 and 450 kW/s
+  power usages as `0.04`, `0.15` and `0.45`. The Energylink's 2.7 MW/s recharge rate and
+  its 3.0 MW overload cost are already in MW and are stored as the source holds them.
+  Durations stay in seconds.
+- **The tools take no grade.** The source holds one figure per stat with no grade or
+  class axis, and Pioneer Supplies sells no tool, so a tool record carries no `grades`
+  field at all rather than a single-entry one.
+- **Reduced Tool Battery Consumption halves `powerUsage` and the Energylink's
+  `overloadPowerUsage`**, and leaves the Energylink's discharge rate alone: the source
+  holds that rate as a static stat and applies no factor to it. The two are stored under
+  separate names for exactly that reason.
+- **A third modification target is rejected.** The question is whether a tool takes
+  modifications of its own. It does not: Reduced Tool Battery Consumption is a suit
+  modification, offered by the suit engineers and installed in a suit modification slot,
+  and no other recipe touches a tool. `target` therefore stays `suit`, and adding a
+  `tool` value would state something the game does not do.
 
 ### Weapon stats read in-game
 
@@ -114,13 +179,26 @@ The suit stats panel is read per suit family and per grade.
   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.
+- **`projectiles` holds the projectiles one round fires**, observed as the
+  weapon fires. Only `Manticore Intimidator` carries it, with 10: its round is a shotgun
+  shell, and each pellet does the full grade damage. The shot spends one round, not ten,
+  so its magazine of 2 is 2 shots. Every other weapon fires one projectile per round and
+  stores no `projectiles`.
+- **`burstRounds` and `burstRateOfFire` hold the burst shape**, observed as the weapon
+  fires. `TK Zenith` is the only weapon with `fireMode` `burst`. One trigger pull fires
+  3 rounds. A burst fires 12 rounds a second. The two fields are stored together, and
+  every other weapon stores neither.
+- **`rateOfFire` counts trigger pulls**, which is what the panel shows for the Zenith:
+  2.78 bursts a second. Every other weapon fires one round per trigger pull, so for
+  those the two readings are the same figure.
 - **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
+  `Number(x.toFixed(3))` does it; that reproduces every stored figure exactly. The
+  rounding rule has to be stated rather than assumed, because some 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.
+  (`Math.round(x * 1000) / 1000`) re-introduces error and misses some of the stored
+  figures.
 - **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
@@ -133,7 +211,16 @@ The suit stats panel is read per suit family and per grade.
   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
+- **`reloadTime` holds the seconds a reload takes**, stock and with the Reload Speed
+  modification fitted. The panel shows no reload figure, so there is nothing to read
+  these values against. Odyssey Materials Helper's `Weapon.java` carries the stock figure
+  as each weapon's `DynamicStat.RELOAD_SPEED` entry. The upgraded figure is the stock one
+  divided by the factor the same file's `DynamicStat.formatValue` applies: `1.20` for
+  `TK Aphelion` and `1.25` for every other weapon. Each quotient is taken in
+  double-precision floating point and rounded to three decimals, as
+  `Number(x.toFixed(3))` does it. Reload Speed stores no modifier of its own because the
+  factor differs per weapon.
+- **`scopeMagnification` holds 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
@@ -152,19 +239,24 @@ that changes nothing — is never stored.
   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.
+  `0.55`. This is the same convention the ships domain uses for resistances. Damage
+  Resistance's four factors name the armour stats, because that is the layer it moves. No
+  recipe moves a shield resistance.
 - **`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
+- **Some recipes name a stat no catalogue field carries**, because the panel shows no
+  base for it: the melee damage and sprint duration multipliers, 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. `toolEnergyDrain` names no field either, and its
+  bases are catalogued rather than panel-only: a tool's `powerUsage` and the Energylink's
+  `overloadPowerUsage` in `tools.jsonc`.
+- **Some 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.
+  - Night Vision, Scope, Reload Speed, 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`, Reload
+    Speed's is the weapon's own `reloadTime`, 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