v3.2: vendor-bundle re-mint under the product-triple rule

Every remaining legacy filament_id outside the BBL/QD_* islands re-derives
from its product triple (filament_vendor / filament_type / family name),
completing the content-addressed id model of filament_id_plan_v3.md:

- Relocation pre-step: 14 fdm_filament_* template forks (Cubicon x3,
  Prusa x6, RH3D x6 minus the pc fork already re-homed) stop declaring
  ids; the 16 presets that rode Prusa's forks now declare the id they
  already resolved (verified zero effective-id drift over all 5892
  instantiated presets).
- --drop-redundant-ids: 6 Custom/MyToolChanger generics drop copied GF
  ids and ride their OFL families.
- --remint over all 62 non-island vendors: 2647 declarations re-derived;
  identical products converge cross-bundle (showcase: PolyLite PLA is now
  OF5CgdDq in OrcaFilamentLibrary, Qidi, OrcaArena and Snapmaker).
- Prusament @XL completions surfaced by the relocation: filament_vendor
  ["Prusa Polymers"] on the 8 @XL declarers; Prusament PA-CF typed
  PA11-CF (the product is Prusament PA11CF) and PC-CF typed PC-CF
  (-CF family typed as base polymer); each family converges on one id.
- Succession: 331 ids retired with mode-rule successors, 355 never-shipped
  v1 mints forgotten with chain splicing, 151 GF-shaped ids released to
  the island space with hints, 27 curated BBL-generic -> OFL-generic
  hints (GFL99 -> OFDSrzZ8 class). New --retire "OLD=NEW" maintenance
  mode records lineage for OGFC99/OGFG99/OGFN99 (the shipped ids of OFL's
  Generic PC/PETG/PA in released versions, whose claims migrated in v3.1
  while Cubicon's inert fork declarations kept them alive).
- Retiring the P-hex system ids removes the last system ids from
  check_ams_filament_valid's destructive P-gate.
- AMS-ambiguity fixes surfaced by convergence (validator -f): 4 presets
  riding another family's id through inherits now declare their true
  family id (Elegoo Generic ASA-CF/PETG-CF, Snapmaker PolyLite Dual PLA /
  PolyLite J1 PLA); 9 Cubicon @base presets and Dremel Generic PLA, which
  duplicate their per-printer variants on the same printers, split onto
  the salt-1 iteration of their triple (sanctioned by the mint-conformance
  check; --remint now leaves salt-conformant declarations alone).

Gates: assign_filament_ids --check 0; orca_extra_profile_check 0;
116 python unit tests; config-equivalence over all 5892 instantiated
presets (byte-identical configs except the 14 sanctioned Prusament
vendor/type corrections; setting_id and compatible_printers unchanged;
per-family convergence and ledger conservation verified); profile
validator base/-f/-r(BBL)/-r(Qidi) all green; libslic3r_tests 48610
assertions; Moonraker OFL generic map check; custom-preset fixture
archives v1.9.0-v2.4.1.

doc/developer-reference/filament_id.md

@@ -112,9 +112,14 @@ python scripts/assign_filament_ids.py --check            # 4. verify — the sam
 `--mint "filament_vendor/filament_type/family_name"` prints the id a triple would mint without
 touching anything. The default run is idempotent and never rewrites a valid existing id.
 Maintenance modes (normally only used by id migrations): `--remint VENDOR` re-derives a
-vendor's declared ids from their triples, `--drop-redundant-ids VENDOR` deletes declarations
-that merely re-declare an inherited OFL id, and `--add-hint "OLD=NEW"` records a cross-island
-succession hint.
+vendor's declared ids from their triples (a declaration already equal to a salt iteration
+of its own triple is conformant and left alone — deliberate salt splits keeping two
+presets of one product apart for per-printer AMS matching survive),
+`--drop-redundant-ids VENDOR` deletes declarations
+that merely re-declare an inherited OFL id, `--add-hint "OLD=NEW"` records a cross-island
+succession hint, and `--retire "OLD=NEW"` records succession for a shipped non-island id
+that vanished while another declarer kept it alive (lineage the automatic claim vote can no
+longer see).
 
 If you skip the tooling, CI fails and prints the remedy: the expected id for your family, and
 the instruction to run `python scripts/assign_filament_ids.py --update-snapshot` and commit
@@ -141,7 +146,8 @@ calibration history, filament-id preset lookup): a live preset always wins first
 installs resolve `GF*` natively and behavior is unchanged wherever the raw id still exists.
 This is what makes identity-driven re-mints (structure rule 5) safe: the old id keeps
 resolving to the family's current preset instead of degrading to a `Generic <type>` fallback.
-The file is append-only and maintained exclusively by `--update-snapshot` / `--add-hint`.
+The file is append-only and maintained exclusively by `--update-snapshot` / `--add-hint` /
+`--retire`.
 
 ## How CI enforces this