feedback5 R4: one file per operator kit — kits/tier1..6.js split into kits/ops/<chessId>-<codename>.js (129 kits), kits/shared/tier1..6.js (the helpers two or more kits of a tier use, and each tier's header notes) and kits/index.js (the registry, same keys in the same order); the tier files become re-export shims

Pure move: every line of a kit, of a helper and of the tier headers is copied verbatim (only the headers' first
line names the new file); a helper used by one kit moved into that kit's file. Glue only: the generated imports,
`export default { … }` around each registry entry, `export { … }` lists in shared/tier2..6.js, and tier4's
`(bb, chess, def)` default-argument wrapper as shared/tier4.js `withDefaults` (applied in each tier-4 kit file).
kits/index.js loads every kit file with a guarded dynamic import (browser-safe, no directory listing); tierN.js
re-export the tier registry (TIER_KITS) and their old named exports (tier1 helpers + tinmanKit, tier6
PITHST_ELEMENTS). The merged registry, every tier default and named export have the same keys, order, frozenness
and function sources as before. test/docs-consistency.test.js reads the moved code at its new paths.
Golden: GOLDEN_FULL=1 node --test test/golden.test.js unchanged.

server/sim/content/kits/shared/tier2.js

@@ -0,0 +1,26 @@
+// server/sim/content/kits/shared/tier2.js — helpers and notes of the Tier 2 operator kits (formerly tier2.js; the kits
+// live one per file in ../ops/).
+//
+// export default { [baseChessId]: (bb, chess, def) => Kit } (docs/SIM.md §7.2). Shared helpers live in tier1.js (named
+// exports). Numbers come from the skill / talent / trait blackboards (elite module upgrades are in the elite record's
+// trait.bb and hidden index −1 talents). fx kinds: see the tier1.js header.
+//
+// Covered (normal + elite): 2_01 送葬人 2_02 赫默 2_03 崖心(H) 2_04 小满 2_05 哈洛德 2_06 莎草 2_07 幽灵鲨 2_08 泡泡
+// 2_09 休谟斯 2_10 洛洛 2_11 风丸 2_12 砾 2_13 蒂比 2_14 调香师 2_15 协律(H) 2_16 拉普兰德 2_17 折桠 2_18 灰毫 2_19 锡人.
+//
+// Operator loadouts (DESIGN §16): every visible chess also authors its selectable NON-default skill in `skills`
+// ({ [skillId]: SkillSpec }, official Lv4 / Lv7 blackboards — the kit function receives the SELECTED skill's `bb`, so
+// every spec is built from `bb`; the trigger rule comes from that skill's data). Talent / install hooks that belong to
+// the default skill only (target locks, counters, hit triggers) check onDefaultSkill(chess). Module choices need no
+// code here: `chess` is the loadout-resolved record (trait.bb / talents of the selected module, or none).
+
+/**
+ * Whether the SELECTED skill of a loadout-resolved chess record is its default skill (DESIGN §16: `chess.skill` is the
+ * selected SkillRecord, `chess.skills[]` flags the default one). Records without skill choices count as default.
+ */
+function onDefaultSkill(chess) {
+  const d = (chess?.skills ?? []).find((s) => s && s.isDefault);
+  return !d || !chess?.skill || d.skillId === chess.skill.skillId;
+}
+
+export { onDefaultSkill };