feedback5 R4: paths after the kit split — DESIGN §7 and SIM.md (layout, §7.2 kit contract, kit citations), research 09, code comments (content/generic, tokens, items/battle, shared/loadoutRecord, render fx / demo), test comments, and the kits' own comments that named tierN.js; DESIGN §17–§23 history citations are left as they are

test/content/kits_alt_t1.test.js

@@ -1,4 +1,4 @@
-// Tier 1 alternate skills & modules (DESIGN §16 operator loadouts; server/sim/content/kits/tier1.js `skills` maps).
+// Tier 1 alternate skills & modules (DESIGN §16 operator loadouts; the `skills` maps of the tier-1 kits, server/sim/content/kits/ops/).
 // Every selectable non-default skill of every visible tier-1 chess runs a real battle — normal (Lv4) and elite (Lv7) —
 // through the harness with its loadout (`skillIndex` / `moduleId` on the board entry, as a BattleSpec carries them),
 // and its signature effect is asserted with numbers from that skill's own blackboard (data/chess.json skills[]).

test/content/kits_alt_t2.test.js

@@ -1,4 +1,4 @@
-// Operator loadouts (DESIGN §16) for the tier-2 kits (server/sim/content/kits/tier2.js): every selectable NON-default
+// Operator loadouts (DESIGN §16) for the tier-2 kits (server/sim/content/kits/ops/): every selectable NON-default
 // skill of every visible tier-2 chess is hand-authored (tools/kit-coverage.mjs) and shows its signature effect for the
 // normal (Lv4) and the elite (Lv7) chess — numbers from the selected skill's blackboard (data/chess.json skills[]) —
 // and the elite's module choice ('none' instead of the default module) changes what the kit / profile does.

test/content/kits_alt_t3.test.js

@@ -1,4 +1,4 @@
-// Tier-3 operator loadouts (DESIGN §16, server/sim/content/kits/tier3.js): every selectable NON-default skill of every
+// Tier-3 operator loadouts (DESIGN §16, server/sim/content/kits/ops/): every selectable NON-default skill of every
 // visible tier-3 chess is hand-authored (`skills[skillId]`) and proves its signature effect for the normal (Lv4) and the
 // elite (Lv7) chess with its own blackboard; non-default modules that change behaviour are exercised too.
 import { test } from 'node:test';

test/content/kits_alt_t4.test.js

@@ -1,5 +1,5 @@
 // Tier-4 operator loadouts (DESIGN §16): every selectable NON-default skill of every visible tier-4 chess has a
-// hand-authored spec in server/sim/content/kits/tier4.js (`skills[skillId]`), proven here by its signature effect for
+// hand-authored spec in its kit file (server/sim/content/kits/ops/, `skills[skillId]`), proven here by its signature effect for
 // the normal (Lv4) and the elite (Lv7) chess; non-default modules (and 'none') change what their text says. Numbers
 // are read back from the data blackboards (the SELECTED skill's `bb`), real battles through the harness.
 import { test } from 'node:test';

test/content/kits_alt_t5.test.js

@@ -1,4 +1,4 @@
-// Tier 5 alternate skills & modules (DESIGN §16 operator loadouts; server/sim/content/kits/tier5.js `skills` maps).
+// Tier 5 alternate skills & modules (DESIGN §16 operator loadouts; the `skills` maps of the tier-5 kits, server/sim/content/kits/ops/).
 // Every selectable non-default skill of every visible tier-5 chess runs a real battle — normal (Lv4) and elite (Lv7) —
 // through the harness with its loadout (`skillIndex` / `moduleId` on the board entry, as a BattleSpec carries them),
 // and its signature effect is asserted with numbers from that skill's own blackboard (data/chess.json skills[]).

test/content/kits_alt_t6.test.js

@@ -1,4 +1,4 @@
-// Operator loadouts (DESIGN §16) for the tier-6 kits (server/sim/content/kits/tier6.js): every selectable NON-default
+// Operator loadouts (DESIGN §16) for the tier-6 kits (server/sim/content/kits/ops/): every selectable NON-default
 // skill of every visible tier-6 chess is hand-authored (tools/kit-coverage.mjs) and shows its signature effect for the
 // normal (Lv4) and the elite (Lv7) chess — numbers from the selected skill's blackboard (data/chess.json skills[]) —
 // and the elite's non-default module choices (Y / RA modules, or 'none') change what the kit does.

test/content/kits_t1t2.test.js

@@ -1,4 +1,4 @@
-// Content tests for the tier 1 / tier 2 operator kits (server/sim/content/kits/tier1.js, tier2.js).
+// Content tests for the tier 1 / tier 2 operator kits (server/sim/content/kits/ops/chess_char_1_*.js, chess_char_2_*.js).
 // Every chess (normal + elite where the elite adds something) runs a real battle through the harness and the test
 // asserts its signature effect with numbers taken from the chess blackboards (data/chess.json).
 import { test } from 'node:test';

test/content/kits_t3.test.js

@@ -1,4 +1,4 @@
-// Tier-3 operator kits (server/sim/content/kits/tier3.js): every chess runs a real battle through the harness and
+// Tier-3 operator kits (server/sim/content/kits/ops/chess_char_3_*.js): every chess runs a real battle through the harness and
 // its signature skill / talent / module effect is asserted with numbers taken from its own blackboards.
 import { test } from 'node:test';
 import assert from 'node:assert/strict';

test/content/kits_t4.test.js

@@ -1,4 +1,4 @@
-// Tier-4 operator kits (server/sim/content/kits/tier4.js): one signature test per chess (+ elite checks), real battles
+// Tier-4 operator kits (server/sim/content/kits/ops/chess_char_4_*.js): one signature test per chess (+ elite checks), real battles
 // through the harness. Numbers are read back from the data blackboards so the tests follow data changes.
 import { test } from 'node:test';
 import assert from 'node:assert/strict';

test/content/kits_t5.test.js

@@ -1,4 +1,4 @@
-// Tier-5 operator kits (server/sim/content/kits/tier5.js): every chess runs a real battle through the harness and its
+// Tier-5 operator kits (server/sim/content/kits/ops/chess_char_5_*.js): every chess runs a real battle through the harness and its
 // signature effect is asserted with numbers taken from its own blackboards (normal Lv4 / elite Lv7).
 import { test } from 'node:test';
 import assert from 'node:assert/strict';
@@ -998,7 +998,7 @@ test('录武官 S2: ATK +45 %; healed allies heal 80 HP per hit taken for 10 s;
 });
 
 // ------------------------------------------------------------------------------------------------------------------
-// regressions of the 2026-09-28 fidelity review (PRTS 备注 of the base operators; see the tier5.js header)
+// regressions of the 2026-09-28 fidelity review (PRTS 备注 of the base operators; see the kits/shared/tier5.js header)
 
 test('圣约送葬人 T1 受选之人: the extra attack consumes no ammo and never reaches ammoUsed listeners', () => {
   const log = [];

test/content/kits_t6.test.js

@@ -1,4 +1,4 @@
-// Content tests for the tier-6 kits (server/sim/content/kits/tier6.js) + 盟约·辅助干员 (chess_char_1_15).
+// Content tests for the tier-6 kits (server/sim/content/kits/ops/chess_char_6_*.js) + 盟约·辅助干员 (chess_char_1_15).
 // Every test runs a real battle through the harness and checks the signature effect of the kit.
 import { test } from 'node:test';
 import assert from 'node:assert/strict';

test/content/playtest4_summons.test.js

@@ -1,4 +1,4 @@
-// Content tests for user playtest #4 items 11 and 12 (server/sim/content/tokens.js, kits/tier2.js):
+// Content tests for user playtest #4 items 11 and 12 (server/sim/content/tokens.js, kits/ops/…2_02-silent.js):
 //   #11 赫默's 医疗无人机 comes with her S2 — since user playtest #6 it is a hand piece the player places, it deploys
 //       once on that tile at the battle start (PRTS 卫戍协议/帮助 §作战阶段; settled by the user after playtest #6 —
 //       shared/constants.js SKILL_SUMMON_START_DEPLOY) and re-appears there each time S2 fires

test/content/playtest6_summons.test.js

@@ -1,7 +1,7 @@
 // User playtest #6 items 1 and 2 (from a friend): 凯瑟琳's device and 赫默's drone could not be placed by hand. The
 // prep side is test/match/playtest6_summons.test.js; this file is the battle side of the placed pieces
-// (server/sim/content/tokens.js dockSkillSummons / releaseSkillSummon, Battle.start `deferDeploy`, kits tier2 / tier3 /
-// tier4, the 爬行号·防护单元 token kit):
+// (server/sim/content/tokens.js dockSkillSummons / releaseSkillSummon, Battle.start `deferDeploy`, the summoner
+// kits in kits/ops/, the 爬行号·防护单元 token kit):
 //   * PRTS 卫戍协议/帮助 §作战阶段: the board summons deploy after the operators; "若战场区初始部署有召唤物，若召唤物在
 //     战斗期间退场，将在满足条件后立即原地再部署1个" — a placed piece marks the tile its summon deploys on;
 //   * a skill's summon (赫默 医疗探机, 巫恋 诅咒娃娃: "获得一个…") deploys once on its tile at the battle start, for free