@elite-dangerous-almanac/core 0.1.0-beta.9 → 0.1.2

package/PROVENANCE/i18n/SOURCES.md

@@ -107,31 +107,90 @@ translation.
   same Brazilian Portuguese game text. `pt-BR` lookups resolve these values through the
   regional-to-language fallback.
 
-## Deliberate absence: ship names
+## `ship-names.jsonc`
 
-- **Acquired:** 2026-08-14 UTC.
+- **Acquired:** 2026-08-18 UTC.
 - **Odyssey Materials Helper revision:** commit
   `23343c453938e724f317c56e9eb7db0dbfa71f78`;
   `application/src/main/resources/locale/ships/ships.csv` has SHA-256
   `6785f7cea00f36ca0a853091fd88f8ed5481a60f55c269643bff1ab0c3d6993d`.
 - **EDSY revision:** commit `e446fbe6e4597dea7ab0bd3105b9a36642388040`;
   database version `424009901`, last-modified marker `20260810`.
-- **Evaluation:** each of the 48 current ship symbols is joined to Odyssey Materials
+- **Derivation:** each of the 48 current ship symbols and canonical English names comes
+  from `data/ships/ships.jsonc`. The symbol is joined to Odyssey Materials
   Helper's `ships.name.*` key after removing punctuation and folding case. EDSY's
   `eddb.js` `ship.fdname` supplies the second join, with explicit `ship-<id>` language
   entries filling locales absent from the CSV. The resulting source-backed coverage is
-  44 ships in Spanish, 42 in French, 38 in Portuguese, 45 in Russian and 44 in Chinese;
+  48 ships in Spanish, 44 in French, 38 in Portuguese, 48 in Russian, 48 in
+  Simplified Chinese and 47 in Georgian;
   no accepted source carries a German ship-name table.
-- **Standing conclusion:** all 213 resulting non-English values are byte-for-byte equal
-  to the canonical English ship names. A ship-name localization catalogue would
-  therefore publish no translated information and is deliberately absent. A source
-  carrying at least one genuinely localized ship name would justify revisiting this
-  conclusion.
+- **Standing conclusion:** every source-backed non-English value is byte-for-byte equal
+  to the canonical English ship name. The explicit values remain in the catalogue so a
+  lookup distinguishes a source-backed same spelling from an unavailable translation.
+- **Manual corrections:** none.
+
+## `ship-manufacturer-names.jsonc`
+
+- **Acquired:** 2026-08-18 UTC.
+- **Derivation:** all 48 symbol-to-manufacturer values are projected directly from
+  `data/ships/ships.jsonc`, whose pinned sources and corrections are recorded in
+  `data/ships/SOURCES.md`. Repeated manufacturer strings remain keyed by ship symbol so
+  consumers need no separate manufacturer identity space.
+- **Coverage:** canonical English covers every ship. The accepted sources carry no
+  localized manufacturer labels.
+- **Manual corrections:** none.
+
+## `engineering-group-names.jsonc`
+
+- **Acquired:** 2026-08-18 UTC.
+- **EDSY revision:** commit `e446fbe6e4597dea7ab0bd3105b9a36642388040`;
+  database version `424009901`, last-modified marker `20260810`; `lang-en.json`,
+  `lang-pt.json` and `lang-ru.json` have Git blob ids
+  `9b199db635f7b968b75c8e9a14bdce68e37e4120`,
+  `493fa09c4d4a11f0282e1e4076a67fed8d7f317e` and
+  `36496372d056754c34da03ca6836e27987c96b6a` respectively.
+- **Derivation:** each of the 48 group ids and its canonical English name is projected
+  from `data/ships/engineering-options.jsonc`. That catalogue derives its group menus
+  from EDSY, with the supplemental sources and corrections recorded in
+  `data/ships/SOURCES.md`. Where a canonical English name matches an EDSY `mtype-*`
+  value in `lang-en.json` byte-for-byte and uniquely, explicit values with the same key
+  are copied from `lang-pt.json` and `lang-ru.json`.
+- **Coverage:** canonical English covers every engineering option group. Portuguese and
+  Russian each cover 44 of 48. The Guardian power-plant, power-distributor and
+  hull-reinforcement groups have no distinct EDSY label, and EDSY carries no Portuguese
+  or Russian value for `frameShiftDrivesSCO`.
+- **Manual corrections:** none.
+
+## `experimental-effect-descriptions.jsonc`
+
+- **Acquired:** 2026-08-18 UTC.
+- **EDSY revision:** commit `e446fbe6e4597dea7ab0bd3105b9a36642388040`;
+  database version `424009901`, last-modified marker `20260810`.
+- **Derivation:** the 29 effects with a `description` project that canonical English
+  value from `data/ships/experimental-effects.jsonc`. Effects without a source-backed
+  description remain absent rather than receiving generated prose.
+- **Coverage:** canonical English covers 29 of 86 effects. The accepted sources carry no
+  localized description table.
+- **Manual corrections:** none.
+
+## `pre-engineered-variant-names.jsonc`
+
+- **Acquired:** 2026-08-18 UTC.
+- **Derivation:** all 76 compound identities and English names come 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 28 distinct display records are stored once. Fixed reward
+  names such as the three `Decorative_*` festive launchers remain canonical English.
+- **Coverage:** English covers every variant. Ordinary names inherit the explicit
+  localized values available for their base module; fixed reward names have no accepted
+  translation source.
 - **Manual corrections:** none.
 
 ## Known gaps
 
 Localized coverage follows the accepted sources and is not complete for every catalogue or
-locale. Missing values are observable as `null`, never an English fallback. Expanding
-source-backed coverage, localized slot labels and higher-level generated text remains
-tracked by [#245](https://github.com/DarkSession/Elite-Dangerous-Almanac/issues/245).
+locale. The accepted sources carry only canonical English for some engineering-group labels,
+slot and restriction labels, fixed reward names, and structured loadout, calculation, SLEF
+and edit messages. Missing source-backed translations remain tracked by
+[#320](https://github.com/DarkSession/Elite-Dangerous-Almanac/issues/320).

package/PROVENANCE/ships/SOURCES.md

@@ -379,11 +379,11 @@ FDevIDs, stats from coriolis-data and EDSY, joined on `symbol`.
     II's `Int_MkIIAgileBoost_Engine_*` thrusters.
   - **A fuel tank is the one module built for two kinds of mount:** it is `fuelTank`
     and also fits any optional slot large enough, exactly as the game sells it.
-- **`kind` is the ordinary engineering-menu family.** The 1026 records mapped by
+- **`kind` is the ordinary engineering-menu family.** The 1005 records mapped by
   `engineering-options.jsonc` repeat that map's group key in the compact on-disk `kind`
-  field. Of the remaining 173 records, 171 carry no `kind` because the pinned sources
-  publish no engineering family for them; the fixed Mining Laser and Abrasion Blaster
-  omit the family as the in-game correction documented under Engineering options below.
+  field. The remaining 194 records carry no `kind` because they have no ordinary
+  engineering menu; this includes the five Enzyme/AX weapons, the fixed Mining Laser and
+  Abrasion Blaster, and the 16 cargo racks documented under Engineering options below.
   The group source, derivation, split
   Guardian families and coverage are documented under Engineering options below; this
   field is a projection of that map, not a separate classification source.
@@ -1100,8 +1100,9 @@ up straight through with no disambiguation at all. Both paths are evidence that
   qualitative descriptions), and `experimental-effect-costs.jsonc` (the matching
   one-application material costs).
   Stored modifier labels use journal `Modifier` **Labels**. Each blueprint is `{ name, grades }`
-  (each grade `{ features, damageDistribution? }`), with its cost file keyed by the same
-  blueprint and grade ids. Each experimental effect is
+  (each grade `{ features, damageDistribution? }`). The cost file uses the same ids and
+  grades for the craftable subset; fixed reward identities without an ordinary cost are
+  absent. Each experimental effect is
   `{ name, modifiers, damageDistribution?, description? }`, with its cost file keyed by
   the same effect ids.
 - **Display names:** each blueprint and experimental effect carries its `name`.
@@ -1150,8 +1151,11 @@ up straight through with no disambiguation at all. Both paths are evidence that
   resolves each to the material's Frontier `symbol` against the `materials` domain at
   generation time, emitting `{ symbol, name, count }` per requirement (join `symbol` to
   `materials` for the material's own grade and category). **Kept as-is:**
-  `CargoRack_IncreasedCapacity` grade 5 has no components upstream, so its `materials`
-  is an empty list (the grade still resolves) rather than being dropped.
+  `CargoRack_IncreasedCapacity` grade 5 has no components upstream. That absence does
+  not establish a zero-cost crafting route: the id describes the two fixed Expanded
+  Cargo Rack community-goal articles in `pre-engineered.jsonc`, so it remains in the
+  mechanics catalogue for their modifier block but is absent from
+  `blueprint-costs.jsonc`.
 - **Operations pre-engineered blueprints — from the in-game / Inara blueprint registry**
   (not in coriolis at the acquired commit): the Merc-Coin weapon rewards and the
   general/core/optional recipes (the **Operations keys**, e.g. `FuelScoop_Efficiency`,
@@ -1346,7 +1350,7 @@ up straight through with no disambiguation at all. Both paths are evidence that
 - **Availability is a property of the module, not of the blueprint.** A Pulse Laser and a
   Rail Gun both take the Efficient blueprint but offer different experimental effects, so
   "which experimentals go with blueprint X" has no single answer. Modules are therefore
-  grouped (52 groups covering 1026 ordinary engineering menus) and each group lists the
+  grouped (48 groups covering 1005 ordinary engineering menus) and each group lists the
   `blueprints` and `experimentals` it offers.
 - **Source:** EDSY `eddb.js`, whose module-group tables carry each group's `blueprints`
   and `expeffects` lists and which modules belong to each group, and whose module records
@@ -1355,14 +1359,14 @@ up straight through with no disambiguation at all. Both paths are evidence that
   `modifications/modules.json`, which carries the same per-group lists keyed by the
   journal `BlueprintName`s this catalogue joins on.
 - **Coverage: every retained group EDSY's `mtype` table gives a `blueprints:` key.** After
-  the Mining Laser and Abrasion Blaster corrections below, that is 52 groups over 1026
+  the corrections below, that is 48 groups over 1005
   modules, including
   bulkheads (the 241 ship armour records), life
-  support, sensors, the Detailed Surface Scanner, cargo racks, refineries, AFMUs, fuel
+  support, sensors, the Detailed Surface Scanner, refineries, AFMUs, fuel
   scoops, FSD interdictors and boosters, Guardian module and shield reinforcement, the
   four engineerable limpet controllers, chaff, heat sink and caustic sink launchers,
-  point defence, ECMs, the KWS/manifest/wake scanners, the Guardian Gauss/Plasma/Shard
-  weapons, the AX missile racks and the Enzyme Missile Rack.
+  point defence, ECMs, the KWS/manifest/wake scanners, and the Guardian
+  Gauss/Plasma/Shard weapons.
   - **A group is one menu, so `noblueprints` splits a family in two.** EDSY denies
     blueprints per module as well as per group (`edsy.js` `setBlueprintID` refuses a
     denied id; `'*'` means the module is not modifiable at all), and for three families
@@ -1381,16 +1385,16 @@ up straight through with no disambiguation at all. Both paths are evidence that
     Anti-Guardian recipe on a non-Guardian module and EDSY denies it. `powerPlants`,
     `powerDistributors` and `hullReinforcements` therefore hold ordinary modules only,
     and the 25 Guardian ones sit in the three groups above.
-  - **14 modules are absent because upstream denies them every blueprint:** eight AX
-    multi-cannons (all but the two gimballed), five of the seven mining tools, and the
-    Mk II Plasma Shock Accelerator — which is why `antiXenoMultiCannons` holds 2 of that
-    family's 10 modules and `plasmaAccelerators` 4 of its 5. The other two mining tools
+  - **14 modules are absent from the registry-derived result because upstream denies them
+    every blueprint:** eight AX multi-cannons, five of the seven mining tools, and the Mk II
+    Plasma Shock Accelerator. The two gimballed AX multi-cannons are removed by the in-game
+    correction below, while `plasmaAccelerators` retains 4 of its 5 modules. The other two mining tools
     are the manually corrected Mining Laser and Abrasion Blaster below, so all seven lack
     an ordinary menu and the empty `miningToolsLasers` group is not retained.
     The ten plain Module Reinforcement Packages are denied their family's only recipe
     and are absent too, which leaves `moduleReinforcements` holding the ten Guardian
     packages.
-  - **The 173 modules absent have no ordinary engineering menu.** For 171 this comes from
+  - **The 194 modules absent have no ordinary engineering menu.** For 171 this comes from
     the pinned registries. Whole families first, both registries
     agreeing: fuel tanks, passenger cabins, the repair/recon/research/decontamination and
     multi-limpet controllers, meta-alloy and ordinary module reinforcement, the Pulse Wave
@@ -1398,11 +1402,12 @@ up straight through with no disambiguation at all. Both paths are evidence that
     vehicle hangars, the docking computers and Supercruise Assist, the module stabilisers,
     the planetary approach suites, the cargo hatch and
     the AX utility modules (Xeno Scanners, Shutdown Field Neutralisers), followed by the
-    individually denied modules described above. The other two are the fixed Mining Laser
-    and Abrasion Blaster, corrected from the registry-derived result below. They and the
-    size-5 class-2 Module Reinforcement Package within the registry-derived 171 have no
-    stock menu, but their purchased Mercenary articles remain upgradeable through their
-    bespoke recipes.
+    individually denied modules described above. The other 23 are the five weapons, fixed
+    Mining Laser, Abrasion Blaster and 16 cargo racks corrected from the registry-derived
+    result below.
+    They and the size-5 class-2 Module Reinforcement Package within the registry-derived
+    171 have no stock menu, but qualifying Mercenary articles remain upgradeable through
+    their bespoke recipes.
   - **EDSY's `_X_` prefix means "not applicable" and is honoured**, not stripped: the
     Detailed Surface Scanner's group lists only `iss_er` (`Sensor_Expanded`), because its
     three other entries are `_X_`-marked. The `Decorative_*` entries on the remote-release
@@ -1428,27 +1433,25 @@ up straight through with no disambiguation at all. Both paths are evidence that
     the nine further groups it carries a list for —
     20 in all, every one an exact match. Chaff, heat sink, point defence and ECMs keep the
     generic `Misc_*` ids: there coriolis agrees with EDSY.
-  - **12 retained groups rest on EDSY alone**, because coriolis carries no blueprint list for
-    them at all: the nine Guardian-only groups (`guardianPowerPlants`,
+  - **Nine retained groups rest on EDSY alone**, because coriolis carries no blueprint list for
+    them at all: the Guardian-only groups (`guardianPowerPlants`,
     `guardianPowerDistributors`, `guardianHullReinforcements`, `moduleReinforcements`,
-    `shieldReinforcements`, `fsdBoosters`, `guardianGauss`, `guardianPlasma`,
-    `guardianShard`), `antiXenoMissileRacks`, `experimentalWeapons` and
-    `antiXenoMultiCannons`. That is coriolis being
-    silent rather than contradicting — its Guardian and anti-xeno groups are empty
-    objects — but it means the second registry corroborates 40 of the 52 groups, not
+    `shieldReinforcements`, `fsdBoosters`, `guardianGauss`, `guardianPlasma` and
+    `guardianShard`). That is coriolis being
+    silent rather than contradicting — its Guardian groups are empty objects — but it
+    means the second registry corroborates 39 of the 48 groups, not
     all of them. The Guardian-weapon menus are independently settled by the in-game
     observations below: stock weapons take Anti-Guardian Zone Resistance alone, while
     the pre-engineered articles are final.
   - **The multi-cannon Overcharged is the one place a group follows coriolis over EDSY.**
     EDSY has a single Overcharged for every weapon; coriolis splits it, and `multiCannons`
-    lists coriolis's `MC_Overcharged`. `antiXenoMultiCannons` lists that key too, but not
-    for that reason — coriolis carries no blueprint list for an anti-xeno group, so it is
-    EDSY being followed into coriolis's spelling. See "Multi-cannon Overcharged: one
-    journal id, two recipes" below for the evidence and for what the split costs.
-  - **The groups name 86 of the 107 blueprints.** The other 21 are accounted for: they are
-    Operations keys of modules sold already engineered rather than offered in a menu. Four
-    Operations keys _are_ named by a group, because they are recipes a player applies — see
-    "Four Operations recipes are listed by a menu" below.
+    lists coriolis's `MC_Overcharged`. See "Multi-cannon Overcharged: one journal id, two
+    recipes" below for the evidence and for what the split costs.
+  - **The groups name 85 of the 107 blueprints.** Of the other 22, 21 are Operations keys
+    of modules sold already engineered rather than offered in a menu; the last is the
+    fixed Expanded Cargo Rack reward identity. Four Operations keys _are_ named by a
+    group, because they are recipes a player applies — see "Four Operations recipes are
+    listed by a menu" below.
   - **14 modules are bound by the family rule, not by a source row.** EDSY has no live
     entry for `Int_Hyperdrive_Size8_Class{1..5}` or `Int_ShieldGenerator_Size1_Class4`
     (both present but commented out, and both naming their `mtype` — `cfsd` and `isg`),
@@ -1486,8 +1489,33 @@ up straight through with no disambiguation at all. Both paths are evidence that
   correction by dropping both module mappings, the now-empty `miningToolsLasers` group,
   both projected `kind` fields in `modules-hardpoint.jsonc`, and the Abrasion Blaster's
   now-unreachable experimental exclusion.
-- **An empty experimental menu is still distinct from no menu.** 30 of the 52 groups offer
-  no experimental at all, so 387 of the 1026 grouped modules have an empty experimental
+- **Expanded Cargo Rack is a fixed reward identity, not an ordinary cargo-rack recipe.**
+  EDSY and coriolis expose `CargoRack_IncreasedCapacity` as the grade-5 identity carried
+  by the size-5 and size-6 community-goal articles catalogued in `pre-engineered.jsonc`.
+  Direct in-game menu confirmation recorded 2026-08-18 UTC establishes that none of the
+  16 stock cargo-rack identities — ordinary, corrosion-resistant, or Mk II — has an
+  ordinary engineering menu; there is no immutable revision for an in-game observation.
+  The fixed articles keep their sourced modifier blocks and remain identifiable without
+  granting the same state to a stock rack. A re-derivation must drop the `cargoRacks`
+  group, all 16 module mappings, and the corresponding projected `kind` fields in
+  `modules-internal.jsonc`.
+- **The Enzyme Missile Rack and AX weapons have no ordinary engineering menu.** Direct
+  in-game confirmation recorded 2026-08-18 UTC establishes that the Enzyme Missile Rack,
+  both plain fixed AX Missile Racks and both gimballed Enhanced AX Multi-Cannons cannot
+  receive ordinary engineering; there is no immutable revision for an in-game observation.
+  The Enzyme Missile Rack bought from a Mercenary contact at grade 1 remains upgradeable
+  through grades 2–5 of its bespoke `EnzymeMissileRack_HighYield` recipe. Its separately
+  catalogued grade-5 High Capacity community-goal article is final. The Enhanced AX
+  Multi-Cannons and AX Missile Racks in `pre-engineered.jsonc` are fixed tech-broker
+  variants and cannot be engineered further. All five fixed articles carry
+  `engineeringLocked: true`; the multi-cannons retain Frontier's journal identity
+  `Weapon_Overcharged`, not the ordinary multi-cannon menu key `MC_Overcharged`. A
+  re-derivation must drop the
+  `experimentalWeapons`, `antiXenoMissileRacks` and `antiXenoMultiCannons` groups, their
+  five module mappings and the corresponding projected `kind` fields in
+  `modules-hardpoint.jsonc`.
+- **An empty experimental menu is still distinct from no menu.** 27 of the 48 groups offer
+  no experimental at all, so 368 of the 1005 grouped modules have an empty experimental
   list while retaining blueprints.
 - **Key form:** the Anti-Guardian blueprint is listed under `GuardianModule_Sturdy`, the id
   a Loadout writes and the one EDSY uses — the same and only spelling `blueprints.jsonc`
@@ -1519,8 +1547,8 @@ up straight through with no disambiguation at all. Both paths are evidence that
     `guardianPowerDistributors` and `guardianHullReinforcements`) therefore carry no
     experimental effects in the catalogue at all. Blueprints are unaffected on every
     module.
-- **Multi-cannon Overcharged uses a distinct stored key.** The `multiCannons` and
-  `antiXenoMultiCannons` menus list `MC_Overcharged`; other weapon menus list
+- **Multi-cannon Overcharged uses a distinct stored key.** The `multiCannons` menu lists
+  `MC_Overcharged`; other weapon menus list
   `Weapon_Overcharged`. Coriolis `modifications/modules.json` assigns the first key to
   multi-cannons and the second to six other weapon groups, while
   `modifications/blueprints.json` gives both the journal fdname
@@ -1529,8 +1557,7 @@ up straight through with no disambiguation at all. Both paths are evidence that
   `modifications/blueprints.json` was acquired 2026-08-07 UTC and has SHA-256
   `cba5a11fc7728e0d1da63fcbbc8d9dfedf9fbc51c99692ee187c7bf0293b3fa1`.
   - EDSY uses one `wpn_oc` recipe and includes the clip reduction on every listed
-    multi-cannon group. Coriolis has no AX multi-cannon menu, so the AX binding combines
-    EDSY's group coverage with coriolis's key for the clip-bearing recipe.
+    multi-cannon group.
   - Frontier journal captures independently show `Weapon_Overcharged` without an
     `AmmoClipSize` modifier on a large gimballed cannon
     (`journal-federation-corvette.jsonc`), a medium fixed fragment cannon
@@ -1539,8 +1566,6 @@ up straight through with no disambiguation at all. Both paths are evidence that
     modifier legs reproduce the published recipe values. EDEngineer's
     `blueprints.json` likewise assigns the clip reduction to multi-cannon types and not
     to cannon, fragment-cannon or plasma-accelerator types.
-  - The two Merc-Coin AX multi-cannon rows in `pre-engineered.jsonc` use
-    `MC_Overcharged`, matching the menu binding and the clip-bearing recipe.
 - **An ordinary recipe on a Guardian weapon identifies a final purchase, not an engineer
   roll.** The three Guardian weapon groups list **only** Anti-Guardian Zone Resistance,
   exactly as the six Guardian _module_ groups do. `Weapon_RapidFire` on `guardianGauss`,
@@ -1664,8 +1689,9 @@ up straight through with no disambiguation at all. Both paths are evidence that
     and several rows are annotated as having been obtainable both ways — the six SCO "V1"
     drives most obviously. `acquisition` records the tag; it is not a claim that no other
     route ever existed.
-- **`engineeringLocked: true` marks all seven pre-engineered Guardian-weapon rows as
-  final.** The source and capture evidence are recorded once under Engineering options.
+- **`engineeringLocked: true` marks 12 final weapon rows:** the seven pre-engineered
+  Guardian weapons and the five fixed Enzyme/AX articles. Their evidence is recorded once
+  under Engineering options.
 - **A reward variant is not reproducible by engineering the same blueprint.** Alongside
   its blueprint and effect, each reward carries hand-set modifier overrides no blueprint
   grants — that is what makes it a reward rather than a shortcut. The `blueprint` /

package/README.md

@@ -48,8 +48,8 @@ The package has six feature areas:
 - `astro`: procedural names, id64 addresses, regions, nebulae and permit locks;
 - `ships`: ships, modules, SLEF loadouts, engineering and build metrics;
 - `equipment`: Odyssey suits, handheld weapons, grade upgrades and modifications;
-- `i18n`: sparse localized module, blueprint, experimental-effect, material and
-  micro-resource names;
+- `i18n`: sparse localized catalogue names, descriptions, slot labels and structured
+  diagnostic messages;
 - `materials`: ship engineering materials and Odyssey micro resources;
 - `commodities`: standard and rare market goods.
 
@@ -67,6 +67,29 @@ assets/ships/<symbol>/schematic-bottom.svg
 package files rather than JavaScript subpath exports, so applications can copy them from
 the installed package into their own public or bundled asset directory.
 
+The two schematics expose a stable annotation contract for hull-anatomy interfaces:
+
+- Each annotated feature is a `<g>` group carrying a `data-feature` category. The
+  current categories are `canopy`, `cargo_hatch`, `engine`, `fighter_bay`, `hardpoint`,
+  `heat_vent`, `landing_gear`, `thruster`, and `utility_mount`.
+- A weapon mount has `data-feature="hardpoint"`; a utility mount has
+  `data-feature="utility_mount"`. Both carry `data-journal-slot`, whose value is the
+  exact journal-compatible slot key returned by `enumerateSlots`. Other feature
+  categories do not carry a journal slot key.
+- Every hardpoint and utility slot in the hull catalogue occurs on at least one of the
+  two schematics. A slot occurs at most once per side, but the same slot may occur once
+  on both sides. Treat those as two views of one game slot, not two mounts.
+- Drawing order, element IDs, `data-model-socket`, coordinates, colours, and other SVG
+  details are presentation data, not stable identities. IDs repeat between asset files,
+  so scope each schematic when inlining more than one. Select interactive geometry by
+  `data-feature` and `data-journal-slot` only.
+
+The schematic documents are safe to embed inline as supplied: they contain only static
+`svg`, `g`, `path`, and `circle` elements; no scripts, styles, event-handler attributes,
+foreign or media elements, links, external references, or CSS `url()` values. This
+content guarantee applies to the unmodified package files; applications remain
+responsible for any transformations or user-supplied replacements.
+
 ## Examples
 
 ```ts
@@ -129,15 +152,19 @@ pinned sources carry no translation instead of silently substituting English:
 ```ts
 import {
     getBlueprintName,
+    getEngineeringGroupName,
     getMaterialName,
     getMicroResourceName,
     getModuleName,
+    getShipName,
 } 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"
+getShipName('empire_trader', 'fr'); // -> "Imperial Clipper"
+getEngineeringGroupName('frameShiftDrives', 'de'); // -> null
 ```
 
 The functions return an explicit source value verbatim, so a source-backed spelling may
@@ -146,6 +173,11 @@ Unqualified `zh` selects the source's Simplified Chinese (`zh-CN`) names. Explic
 different Chinese scripts or regions such as `zh-TW` do not fall back to Simplified
 Chinese and return `null` unless a matching source is added.
 
+The same contract covers ship manufacturers, pre-engineered variant names, engineering
+group names, experimental-effect descriptions, loadout-slot and restriction labels, and
+structured loadout, calculation, SLEF and edit messages. A family whose accepted source
+currently supplies only English returns `null` for every non-English locale.
+
 Registry lookups ignore case and surrounding whitespace. Material, commodity and
 module lookups search their complete registry by default and accept an optional
 catalogue to narrow the results. Nebula queries require an explicit catalogue so the

package/THIRD_PARTY_NOTICES.md

@@ -81,7 +81,7 @@ a verbatim copy produced at build time — edit this file, never the copy.
   engineering menus, per-ship module-count limits and fitted stabiliser increases, the
   baseline per-hull maximum heat dissipation, the
   Lynx Highliner's hull/slot figures and zero-pip minimum pitch, the journal slot names,
-  localized module, blueprint and experimental-effect names, and the
+  localized module, blueprint, experimental-effect and engineering option-group names, and the
   attribute-to-journal-Label mapping. The values are Elite Dangerous game data — see the
   Frontier notice below. Heat dissipation is the one entry the game never shows a player:
   it is community measurement of Frontier's game, described under Algorithms above, and
@@ -193,8 +193,8 @@ and
 [`data/commodities/SOURCES.md`](https://github.com/DarkSession/Elite-Dangerous-Almanac/blob/main/data/commodities/SOURCES.md),
 with the rules those files follow in
 [`data/SNAPSHOTS.md`](https://github.com/DarkSession/Elite-Dangerous-Almanac/blob/main/data/SNAPSHOTS.md).
-Those files live in the repository only — this file is also published inside the npm
-package, where they are not present, so the links are absolute.
+The npm package includes matching copies under `PROVENANCE/` (without the `data/`
+prefix); the links above are absolute so they resolve from inside the package too.
 
 If you add or change data, port an algorithm, or add a dependency that warrants credit,
 add it here and record the provenance where the data lives.