feedback7 R22-FIELDS: boss-field portals teleport — a route ending on a portal entrance comes out of the far exit and leaks at that side's blue door, the four appear-less crossings reappear at the exit (GitHub #336, PR #337 by @2321Robin); golden: 8 fields, 6 matches

PR #337 by @2321Robin (GitHub #336, both with a recording of the official game), applied with small changes: the exit
distance uses detmath hypot (PR #373 bans Math.hypot in the sim), comments cite the data counts as measured here
(137 routes end on [1,3] / [1,17]; 95 explicit DISAPPEAR / APPEAR pairs, all → [5,10]), the end-teleport's zero wait
is marked [ASSUMED] beside the pairing, and the test reads the test enemy's own leaks (the templates' escorts leak too)
and checks the entrance itself is no leak.

- simdata.js portalAppear: act1autochess_h07_02 #4, act1autochess_h08_02 #5 / #9 and act2autochess_h07_05 #6 write
  DISAPPEAR → WAIT → MOVE[5,10] with no APPEAR (the level files too); the exit APPEAR is inserted before that move.
  Before, the enemy walked the rest of its route hidden and leaked unseen.
- ai.js portalPickup: a route that ends on tile_telin (the boss / Hidden Core circuits) vanishes the enemy, brings it
  out of the farthest telout ([5,10]) and walks it to the nearest blue door ([2,2] / [2,18]), where it leaks. Before,
  stepping into the corner portal was the leak. Mid-route crossings are unchanged (every MOVE onto an entrance in the
  data is followed by an explicit DISAPPEAR).

Golden — only boss / Hidden Core fields and the matches' final rounds move (no round row of any match moves):
- fields boss-boss_2-solo (铳): the 2 lrrook escorts still leak, now at the door after the portal, and take 120652
  damage instead of 66943; leader left 2761255 → 2763024.
- fields boss-boss_4-solo (昆图斯): the 2 dspred leaks now happen at the door; one more operator death (6 → 7);
  leader left 3759559 → 3759921.
- fields boss-boss_6-pair (阿利斯泰尔): the 2 hllevi_2 that leaked at the portals are killed on the way back:
  killed 4 → 6, both players perfect (1 leak each → 0); leader left 7017881 → 6972383.
- fields boss-boss_6-solo: killed 5 → 8, leaks 5 → 2 (the 3 msfshu that leaked are killed; the 2 hllevi_2 leak at the
  door); leader damage 105194 → 75209.
- fields hidden-boss_8-pair (胄): p2's one vtsk leak is gone — that vtsk is still walking to the door at the 200 s
  cap; p2 perfect.
- fields hidden-boss_8-solo: killed 3 → 8, total 13 → 19 (more sfshu die, so more msfshu split off: 3 → 9), leaks
  10 → 10; leader damage 402606 → 191576 (the escorts that come back out of [5,10] draw the fire).
- fields hidden-boss_9-pair (铳): from portalAppear alone — h08_02's routes #5 / #9 no longer count the portal hop as
  8 tiles of walking, so the targeting order of those escorts changes; leader left 3570058 → 3511007.
- fields hidden-boss_10-solo (管): the yokai_3 escort crosses back (taken 68252 → 101682), 4 more operator deaths;
  leader left 7323878 → 7323370.
- matches solo-FUNNY-2 (boss_5 Final Assault, lost at 8 rounds): pool left 94860 → 94412, kills 143 → 144.
- matches solo-NORMAL-1 (m03, hidden boss_8 胄, act1autochess_h08_01_s): the Hidden Core goes from cleared to failed
  (hiddenCleared true → false, team LP 26 → 0, roundsPassed 15 → 14, pool left 0 → 99894; victory stays true — the
  Final Assault was won). The fight is identical until 105 s, when the third vtsk escort reaches the corner portal
  [1,3]: before, it leaked there (27 → 26 LP) and the leader died at 214 s. Now it comes out of [5,10], walks through
  the team's line to the blue door [2,2] and leaks at 170 s; meanwhile only 0–2 of the 8 operators stand (2–4 before),
  the leader stalls near 120000 HP, the fight passes the 150 real-second mark (300 game s) and the overtime drain (1 LP
  per real second) plus two drone leaks at the door take the last 25 LP at 348 s with 99894 HP left.
- matches solo-HARD-1 (m03, hidden boss_8): still failed at 0 LP after 14 rounds; pool left 3046117 → 2839368, kills
  419 → 422.
- matches solo-HARD-9-boosted (hidden boss_10 管): still cleared; team LP 383 → 361 — the 管 echoes (acdums) leaked
  7 times at the portal before and once at the door now, but the longer fight pays 37 overtime LP instead of 9.
- matches coop2-ABYSS-10-boosted (hidden boss_9 铳): from portalAppear alone (the remaining-distance change above);
  still cleared at 800 LP, the two seats' leader damage shifts (6609998 / 7282442 → 7523075 / 6369365) and their
  titles swap (坚若磐石 / 卫戍之星 → 卫戍之星 / 不朽盟约).
- matches coop2-NORMAL-14-standins (boss_5 Final Assault, lost at 13 rounds): pool left 107915 → 97588.

Tests: test/sim/portal-appear.test.js (new, 9; 7 fail on the parent: the APPEAR insertion, the four real routes,
the two route-end portals).

server/sim/ai.js

@@ -28,10 +28,11 @@
 // (PRTS 状态机: an enemy's COMBAT state ends with its attack, not with its blocker); the candidates pass the
 // enemy's own rule (`e.profile.canTarget`) and are ordered
 // blocker → taunt → latest deployed (targeting.js sortAllyTargets). An enemy's damage type is its data's unless content
-// arms it (`e.profile.dmgType`: 转译基底's forms, whose data never attacks). Reaching the final leg's end = leak. A `fear` (恐惧) status suspends the route: the
-// enemy runs between random checkpoints away from the fear's source (fear.js moveFeared; a self-inflicted fear
-// flutters inside its own tile); an `attract` (诱导) status walks it to the status point instead (moveAttracted);
-// both re-plan the route when released (恐惧 outranks 诱导).
+// arms it (`e.profile.dmgType`: 转译基底's forms, whose data never attacks). Reaching the final leg's end = leak — on a
+// portal entrance it is a teleport to the far exit and a walk to that side's blue door instead (portalPickup). A `fear`
+// (恐惧) status suspends the route: the enemy runs between random checkpoints away from the fear's source (fear.js
+// moveFeared; a self-inflicted fear flutters inside its own tile); an `attract` (诱导) status walks it to the status
+// point instead (moveAttracted); both re-plan the route when released (恐惧 outranks 诱导).
 
 import { ATTACK_PAUSE, ALLY_COLLIDER_RADIUS, MOVE_SCALE, PROJECTILE_SPEEDS, PROJECTILE_SPEED, BOOMERANG_RETURN_SPEED, COLS, CHAIN_RADIUS } from './constants.js';
 import { sortEnemyTargets, sortAllyTargets, canTargetEnemy, canTargetAlly, tileKeyOf } from './targeting.js';
@@ -633,7 +634,10 @@ function advanceRoute(b, e, dt, R, standing = false) {
   let guard = 16;
   while (budget > 1e-9 && guard-- > 0 && e.alive) {
     const leg = R.legs[R.legIdx];
-    if (!leg) { b.leak(e); return; }
+    if (!leg) {
+      if (!portalPickup(b, e)) { b.leak(e); return; }
+      continue;
+    }
     if (leg.t === 'wait') {
       if (R.waitLeft == null) R.waitLeft = leg.time;
       const use = Math.min(budget, R.waitLeft);
@@ -682,13 +686,47 @@ function advanceRoute(b, e, dt, R, standing = false) {
     }
     budget = dist / speed;
     if (R.pts && R.ptIdx >= R.pts.length) {
-      if (leg.final) { b.leak(e); return; }
+      if (leg.final) {
+        if (!portalPickup(b, e)) { b.leak(e); return; }
+      }
       R.legIdx++;
       R.pts = null;
     }
   }
 }
 
+/**
+ * Boss-field portal pickup (tile_telin / tile_telout; GitHub #336, PR #337 by @2321Robin, both with a recording of the
+ * official game): a route that ENDS on a portal entrance does not leak there — the enemy is teleported out of the far
+ * exit and walks on to the blue door on the entrance's side, where it leaks. The boss / Hidden Core circuits end on
+ * an entrance ([1,3] / [1,17]; 137 routes of data/waves.json); their mid-route crossings are the routes' own DISAPPEAR /
+ * WAIT / APPEAR steps, every MOVE onto an entrance being followed by a DISAPPEAR, so only the route's end needs this.
+ * Appends vanish → reappear → walk-to-door legs to the live route and returns true (false: not on an entrance, or no
+ * exit in the field). The exit is the telout farthest from the entrance, the door the end tile nearest to it: every
+ * explicit pair of the data (95, routes and extra routes) reads [1,3] / [1,17] → [5,10] — the farther of the two
+ * telouts [5,10] / [2,10] of the battle stages — and the doors [2,2] / [2,18] stand beside the entrances.
+ * [ASSUMED] the pairing (no tile carries a link) and no wait inside this portal (the explicit crossings write their
+ * own: 3 s in 85 of the 95, 5 s in 9, 1 s in 1).
+ */
+function portalPickup(b, e) {
+  const r = Math.round(e.y), c = Math.round(e.x);
+  if (!b.grid.inBounds(r, c) || b.grid.tile(r, c).special !== 'telin') return false;
+  const outs = b.grid.specialTiles('telout');
+  if (!outs.length) return false;
+  const dist = (p) => hypot(p[0] - r, p[1] - c);
+  const out = outs.reduce((a, x) => (dist(x) > dist(a) ? x : a));
+  const R = e.route;
+  R.legs.splice(R.legIdx + 1, 0, { t: 'disappear' }, { t: 'appear', r: out[0], c: out[1] });
+  const ends = b.grid.specialTiles('end');
+  if (ends.length) {
+    const door = ends.reduce((a, x) => (dist(x) < dist(a) ? x : a));
+    R.legs.push({ t: 'move', r: door[0], c: door[1], final: true });
+  }
+  R.pts = null;
+  R.tailVersion = -1;   // the appended tail invalidates the cached remaining-distance suffixes
+  return true;
+}
+
 /**
  * How long an enemy stands for one attack: an unblocked ranged enemy for its whole clip (GitHub #58 — the owner's
  * decision of 2026-10-04 from first-hand memory of the official game: a ranged enemy stops for each attack's animation

server/sim/simdata.js

@@ -394,6 +394,7 @@ export function normalizeRoute(r) {
       const t = String(st.t ?? st.type ?? 'move').toUpperCase();
       cps.push({ type: normCpType(t), pos: pairOf(st.p ?? st.pos) ?? [0, 0], time: num(st.s ?? st.time, 0) });
     }
+    portalAppear(cps);
     return { motion, start, end, checkpoints: cps };
   }
   for (const cp of r.checkpoints ?? r.cp ?? []) {
@@ -406,9 +407,29 @@ export function normalizeRoute(r) {
       cps.push({ type: normCpType(cp.type), pos: pairOf(cp.pos ?? cp.position ?? [cp.row, cp.col]) ?? [0, 0], time: num(cp.time ?? cp.t, 0) });
     }
   }
+  portalAppear(cps);
   return { motion, start, end, checkpoints: cps };
 }
 
+/**
+ * The boss / Hidden Core templates' 传送门 (GitHub #336, PR #337 by @2321Robin): the twin routes spell a crossing as
+ * DISAPPEAR → WAIT → APPEAR[exit], but four official routes leave the APPEAR out and go straight to MOVE-to-the-exit
+ * (act1autochess_h07_02 #4, act1autochess_h08_02 #5 / #9, act2autochess_h07_05 #6; the level files themselves have no
+ * APPEAR_AT_POS there). Taken literally, such a route walks the enemy's whole remaining run hidden (untargetable,
+ * unblockable) and it leaks unseen — the crossing must read "reappear on the far side". Re-insert the exit APPEAR
+ * ahead of that MOVE, at the MOVE's own target, where the twins appear ([5,10]; the leftover MOVE becomes a
+ * zero-length hop, and the hop no longer counts as walking distance for the targeting order). A DISAPPEAR followed by
+ * an APPEAR, or by no MOVE, stays as it is; idempotent.
+ */
+function portalAppear(cps) {
+  for (let i = 0; i < cps.length; i++) {
+    if (cps[i].type !== 'DISAPPEAR') continue;
+    let j = i + 1;
+    while (j < cps.length && cps[j].type === 'WAIT') j++;
+    if (cps[j] && cps[j].type === 'MOVE') cps.splice(j, 0, { type: 'APPEAR', pos: cps[j].pos.slice(), time: 0 });
+  }
+}
+
 function normCpType(t) {
   const s = String(t ?? 'MOVE').toUpperCase();
   if (s.includes('DISAPPEAR')) return 'DISAPPEAR';