re: the EF_IDX_ prefix - ptc_pack has 727 names, and the map reaches 128 of 137

Censusing ptc_pack's own naming vocabulary turned up a third variant of the
prefix trap, and this one had been corrupting a number the corpus carried.

268 of ptc_pack's names do not start with eff_ at all. They start with EF_IDX_,
as in EF_IDX_eff_d001_f. A regex anchored at eff_ chops that prefix off and
merges distinct names, which is exactly where the earlier figure of 532 came
from. Enumerating maximal [A-Za-z0-9_] runs gives 727. The two earlier traps were
a STORED name being longer (rot_n001_break) and a BOUND name being a prefix
(eff_f0002 inside eff_f0002_barnhaze); this is the third - a prefix the pattern
cannot see at all, because its anchor sits in the middle of the real name.

Looking each bound name up bare AND under EF_IDX_ resolves 25 of the 34 that were
unlocated. The map is now 128 of 137, and the residual is 9, small enough to
print: eff_e0044, eff_f0002, eff_f0002_barn, eff_h308, eff_j002_e01,
eff_j002_e02, eff_m010_wep_85, eff_m011_wep_85, eff_n0071. All 17 eff_l### are
among the recovered.

This withdraws my own previous correction. I had recorded Base.xpr (53) as
holding more bound effects than ptc_pack (46), and struck out "ptc_pack is the
effect library". With the prefixed keys counted ptc_pack holds 71 - it IS the
larger library, and the 46 was an undercount from the same truncating pattern.
Two shared libraries remains right; which one is bigger does not.

The suffix vocabulary: 106 distinct tokens over the 727 names - IDX 223 (the
prefix above), _f 137, _e 119, _root 87, _col 54, _mdl 45, _break 43, _ring 38,
_ALL 17, _haze 14, _thunder 10. That census counts ALL tokens rather than
trailing ones, which is precisely how the EF_IDX_ PREFIX surfaced inside what I
had first labelled a suffix list - the mislabel found the bug.

Testing the structural candidates the way _hangar was tested, does the suffixed
name have a bare parent:

  _ALL      17 names    17 of 17
  _root     87          64 of 87
  _break    30          15 of 30
  _e        74           0 of 74
  _f        61           0 of 61

_root is strictly terminal - 87 of 87, and it never appears mid-name. The
compound shapes put it outermost: _e_root 19, _f_root 18, _break_root 13, bare
_root 30. So the order is <stem>_[<faction>|<break>]_root and _root reads as a
hierarchy marker rather than a variant - though 64 of 87 having a bare parent
means it is not simply the parent of an existing node, and _break at 15 of 30 is
likewise not a plain destroyed-twin-of-everything.

_e/_f never have a bare parent, 0 of 135. That is independent asset-side
confirmation of the faction law: an effect is authored per faction and there is
no faction-neutral original for either side to derive from.

effect-homes.txt changes 5/30 and every line pairs: five values changed (103->128,
34->9, ptc_pack 46->71 and its sort position, the residual header, 3-digit
80->105 of 110) plus 25 pure deletions, exactly the 25 recovered names. All are
3-digit, so the 4-digit line is unchanged at 23 of 27. The other sixteen
artefacts are byte-identical.

docs/re/BACKLOG.md

@@ -6794,3 +6794,35 @@ for those kinds; there was nothing to test.
 regex requiring `UN_<l>###_<FACTION>_`; the looser form finds **71**. The extra
 is **`UN_e910_core_ADAN_GeneratorCore`**, which inserts a sub-kind before the
 faction tag. Grammar is `UN_<l>###_[<subkind>_]<FACTION>_<name>`.
+
+---
+
+## ❌✅ 2026-08-28 — `EF_IDX_` prefix: `ptc_pack` has 727 names, and the map reaches 128 of 137
+
+Item (a). Censusing `ptc_pack`'s naming vocabulary found a third prefix trap that
+had been corrupting a carried number.
+
+❌ **`ptc_pack` holds 727 distinct names, not 532.** **268 do not start with
+`eff_`** — they start with **`EF_IDX_`** (e.g. `EF_IDX_eff_d001_f`). A regex
+anchored at `eff_` truncates that and merges distinct names. ⚠️ Third variant of
+the trap: the stored name longer (`rot_n001_break`), the bound name a prefix
+(`eff_f0002`), and now **a prefix the pattern cannot see because its anchor sits
+mid-name**.
+
+✅ **Looking each bound name up bare AND under `EF_IDX_` resolves 25 of the 34.**
+The map is now **128 of 137**, residual **9**: `eff_e0044`, `eff_f0002`,
+`eff_f0002_barn`, `eff_h308`, `eff_j002_e01`, `eff_j002_e02`, `eff_m010_wep_85`,
+`eff_m011_wep_85`, `eff_n0071`.
+
+❌ **Withdraws my own previous correction**: I had recorded `Base.xpr` (53) as
+holding more bound effects than `ptc_pack` (46). With prefixed keys `ptc_pack`
+holds **71** — it *is* the larger library; 46 was an undercount from the same
+pattern.
+
+✅ **Suffix vocabulary** (106 tokens over 727 names): `IDX` 223, `_f` 137, `_e`
+119, `_root` 87, `_col` 54, `_mdl` 45, `_break` 43, `_ring` 38, `_ALL` 17.
+**`_root` is strictly terminal, 87 of 87, never mid-name**; compounds place it
+outermost (`_e_root` 19, `_f_root` 18, `_break_root` 13, bare 30). Bare-parent
+test: **`_ALL` 17/17**, `_root` 64/87, `_break` 15/30, and 🔑 **`_e`/`_f` 0 of
+135** — asset-side confirmation that effects are authored per faction with no
+faction-neutral original.