Twilight Thorn live11: no kill

Single-PC loopback, build23/protocol31, run 20261021-020601_net_twilight_thorn_rehearsal_1. The fight ended in native full-party defeat at step39. Boss HP fell from390 to268; seven friend damage claims applied38 damage. Earlier native revives worked in both directions. Later, the host's second downing stayed airborne atY=-251.985 while the friend was usually nearY=0, outside the unchanged3D revive range.

All11 remote reaction completions reached host application: nine succeeded, including one426 and one432. Two later426 replies were refused because their host roles had already retired. The exact retirement trigger was not logged. There was no trace saturation. This proves neither network loss nor an incorrect retirement. Opening297/298 completed;299, the kill, terminal16/315, rewards and cleanup remain unproved.

Four protected saves,514 source files,14 game-root files and527 assets were unchanged. Closure found no remaining owned processes or relay listener. The decisive reports contain the scenario reports, independent reviews, safety and build receipts, raw logs and sampled reaction rows. The source archive preserves the exact514 non-build inputs for523 pins; it contains no protected save bytes.

Four inspected gameplay stills are indexed in evidence.json. HOST seat0 and FRIEND seat1 use offsets in their independent block03 recordings, not synchronized frame pairs. Friend+10s extraction crashed ffmpeg; the eight raw recordings remain in the run directory. There is no captioned kill clip or claim of full-video review.

VUH-2569 stays open for the kill and426 retirement cause. Subsequent approved work adds retirement observations and holds only downed XZ, leaving native Y movement intact. A fresh full suite, Computer Room grounded down/revive regression and Thorn live12 are required. Creeper parity remains the documented VUH-2605 gap.