Twilight Thorn across seats (VUH-2569)

Design approved by Clankie on 2026-10-20 (lead message 2); inventory baseline fec5d8e, native implementation based on edf2f2d, rebased onto docs-only main e053a9e (combined wire v30). This records the inventory, ownership contract and limited live qualification below. Live runs are single-PC, two-seat loopback, per the lead's instruction.

The original v30 reaction-only landing deferred native mission4/16 observation and suppression, event315 qualification and exact307 boss-leave fallback. Build19/live10 qualified that trimmed binary's opening and both-seat ground reactions. The v31 cohort now restores the reviewed host-only terminal bundle and includes logical-down XZ holding, lifecycle observations and safe-field recovery. Build34 passed the full203-test suite. Historical attempts below retain their own binary and result boundaries.

Bot01 (20261021-113329_net_twilight_thorn_bots_1, sealed build28, single-PC loopback) achieved a native host kill and three natural friend-to-host revives, but failed shared exit: the friend's expired control lifetime rejected315 and left it behind. Its original safety is not PASS: a movie mtime changed, although the bytes match the installed depot reference. VUH-2628 tracks the recovery boundary. Build34/recovery04 now proves a fresh authenticated rejoin in empty FM00 with a dormant tutorial script; see the bounded result. It does not prove the parent's shared kill, rewards, cleanup or onward movement. VUH-2617 holds the bot series; the sealed human14/build28 packet remains an optional baseline. VUH-2569 stays open for the kill and the captured426 cause.

Lead22 split script-created Creeper parity into VUH-2605. The existing native cull predicate executes child BDX before its authority check; a replica that skips initializer BDX needs a pre-cull fence and qualified native disposal first. Reviewed resource/factory/typed-ledger boundaries remain uncommitted; no child construction is enabled and the global317 deny remains. Creeper population desync is a known gap on VUH-2569, not a kill-proof claim.

The current full-fight cohort uses protocol v31, because limited-RC v30 peers reject the restored terminal semantics. Its original host-only terminal bundle observes signal4, mission4/16 and the authored315 event. Clients never blindly replay4/16. The full type55-only diagnostic scope is approved to locate the captured426 failure without changing wire, native ABI, retries, leases or pilots. The limited landing evidence above does not qualify the terminal bundle. The later failure chronology below is historical; it does not override the current status above.

Victory handoff (VUH-2807)

The retained zr100 kill delivered native315 to the friend with a healthy control channel, but the input consumer read it while the previous death-camera hold's pause was still Closing. It skipped the start and cleared the old release receipt; the friend never played315 and followed the host only at the next room's316. The PAUSE overlay came from that earlier hold. This differs from VUH-2628's heartbeat expiry.

The native consumer now leaves successor records in the existing FIFO during its owned pause close. The close still ticks every callback. Once a fresh sample observes the menu closed, the next callback can supersede OwnerWait and replay the checked start through the existing safety gates. Scope, health, descriptor qualification and native gameplay safety remain required. See the retained diagnosis and offline checks. Live cinematic timing and the overlay acceptance remain unqualified until a scheduled paired-screen kill run.

Installed evidence

Read from PC1's installed packages without launching the game or changing saves. Local extraction receipts, decoded scripts and the previous attempt are under .local/thorn/ in the VUH-2569 worktree. Only findings are committed; extracted game assets remain local.

The extracted ARD SHA-256 is 286a3bba6311910013e17aaa707f839c83bc76a830cf87cf3628fc0cb432b40e; mission 255c50ffd283a981cb635e294238e255ca37299b4e09edd900ae11ffcca26dce; model 271ffe64db2f7d0c23669ab3c44befde9bf1f222bdd18c1c4661f8fa28f22c2f. BDX PCs below are halfword addresses after the 16-byte header, as in OpenKH's BDX decoder. The reused local decoder is OpenKH 7a3b945c; command layout and message encoding are documented in Cmd.cs and InternationalSystemDecode.cs.

Native phase inventory and ownership

Names and entry PCs come from trap_act_table_add (1/6) in the boss's BDX. Visual names group those actions; they do not assert a fixed order or a new replacement boss state machine.

The boss also has mode_battle 6672, mode_revenge 6935, mode_battle_boss 6977, mode_revenge_boss 7043, revenge 7109, near_wait 7505, near 7583, rc_restart_test 7818, freeze 6449, leave 6389, idle_time 6486, talk 7168, info1 8859 and info2 8871. All decision actions remain host-owned, including test/debug actions if reached.

attack_set_rc (2/51) is called with Reversal 345 (800/500 bounds), 432 (300/300 and 600/300), 666 and 667 (600/300). command_override (1/165) is the direct player-command path. The main cinematic combines obj_hook, obj_camera_start, obj_attach, obj_detach, player motion capture/sync, hide/show and movement. At the inventory baseline, ScriptMirror covered effects and rotation, but none of those actor-owner or attack-trigger operations. Adding object 307 to the census alone would disable the friend's independent script without providing them.

Implementation boundaries and checks

Reuse EnemySync, EnemyMirror, EnemyTargetRemote, ScriptMirror, MissionMirror, and the established room/event/seat bindings. VUH-2418's generic RC/actor-owner routing is still Backlog; it is a missing capability, not an existing API. Build the minimum reusable routing inside the script mirror: host-minted occurrence + trigger sequence + admitted owner slot/connection, bounded lifetime, room/load/session scope, owner acknowledgement and consume-once completion. Never transmit native actor/effect/attack pointers. Receipt loss, replacement, death and reconnect cannot replay a previous command or retain an attachment. Unknown/unqualified calls refuse with a specific diagnostic.

Start with a focused census/classification regression and real native-owned-memory tests. Then extend the codec/relay/ScriptMirror tests for trigger pairing, nearest living selection, seat ties, duplicate completion, changed actor/epoch, timeout, downed and native-RC-over-revive behavior. Deferred mission support will need tests for the single host4/16 observation and exactly one post-fight release before it returns to the product. Native trap replays require static ABI/thread-context checks, pinned bytes and independent D14.4 review before live execution. No BDX workspace copying or guest AI fallback is proposed as a solution to phase synchronization.

Use a checked-in FM-00 rehearsal scenario through real doors. Film both screens through the full kill, caption phase/RC owner and victory from receipts, and retain parity/hit/RC/mission samples. Require both-seat contributions, incoming hits, arena downed/revive, one victory, the same post-fight event and onward control. Full-party down follows VUH-2465 native Continue with fresh authority. The prior VUH-2466 attempt (20261020-002047) is only a failure baseline: host Game Over while the friend continues, no Thorn census/HP evidence. Protected saves and existing desk/run locks remain mandatory.

Implementation status

The reaction-only implementation extends the existing enemy census, one-brain suppression and script resources. Mission end observation, event315 qualification and exact307 boss-leave fallback are deferred; generic main mission/event/boss behavior remains unchanged. Reusable reaction occurrences and actor-owner capture, attachment, camera and command routing live inside ScriptMirror. Protocol v30 preserves the landed owner-vitals layout. Current main's checked entrance-record matching also selects Thorn's raw566 at record1; the boss at record0 cannot supply a player template.

The combined candidate on main650f9ea passed build15: all targets compiled and all 201 registered tests passed. This includes the actual-owner/spectator source-bank correction, native motion policy regressions and main's entrance selectors. Independent native reviews covered resource lifetime/scalar normalization, both command helpers, the complete motion patch and its two enum-conversion corrections. Runtime qualification is partial; the live07 findings below retain the remaining gates.

Live06 (20261020-205110, single-PC loopback) reached Thorn through real doors and reduced shared HP390 to232 with native host damage and actual friend hit claims. Key Counter297, Lunarsault298 and Break Raid299 completed through host validation; the host recorded17 completions in total, including actual friend-owned ground345/432. The host was naturally downed four times and returned through native revival three times, before both pilots timed out on the fourth rescue. There was no kill, mission16, event315 or victory clip. Both inject logs contain no exception. Safety closure passed with four protected saves and484 source inputs unchanged, no remaining owned processes and the relay port free.

The same run produced an enemy-population desync: after native boss-script creation of Creepers317, the host counted three enemies while the friend counted only Thorn for more than12 seconds. Progress hashes agreed. Creeper317 already has a global point-binding exception; turning on that family or the parked general population factory is not a qualified correction. Exact host-owned script birth and binding must extend the existing paths before acceptance.

Live07 (20261020-213855, build15, single-PC loopback) reached shared225/390HP: 45 damage from the three opening RCs and120 from ordinary combat, including69 from12 accepted native friend claims. The host was downed once; neither seat revived. Both pilots reached their60-second cooperative timeout. No revive hold or blocked-approach probe began. The friend's raw and visible Reversal432 persisted while the host later offered345; native revival also yielded to432 inside100 units. Callback eligibility after those roles ended was not recorded, so prompt lifetime is under investigation rather than classified as pilot skill. There was no kill, mission16 or event315. Safety closure passed: four saves, 498 source inputs,14 game-root entries and527 assets unchanged; owned instances closed and relay port free. The exact507-pin source archive is retained with the run under build/rig/vuh2569-live07/.

Ground Reversals are authored evasive movement, not boss damage. The three432 callbacks inspected in live05 each advanced and released their host and friend roles. A plateau alone therefore does not establish a stuck callback; live07's persistent prompt and native revival starvation are the more specific evidence.

The friend-side borrowed-motion gap is tracked on VUH-2580, with the analysis. The actor-role path now selects the captured source's motion bank for both the actual owner and a separately validated spectator clone, retaining owner-only cameras/commands and callback-free visuals. Live07's read-only trace observed 93 host-owner and93 clone samples with Thorn's borrowed roots, followed by restoration to each actor's own roots. Sparse footage leaves the captured clone mostly occluded or cropped, so this does not qualify its full rendered skeleton or a friend-owned cinematic capture. A later paired frame also shows a standing, arms-horizontal remote actor while its host is downed; that separate pose mismatch remains unqualified. Temporary hidden B_EX200 and hide/show parity remain open.

The approved script-child design keeps the global317 deny and extends existing birth, manifest and mirror ownership. Once adopted, a child follows its own authenticated manifest, HP and death; parent retirement stops new births only. A fresh reconnect after the parent has gone is refused in this initial scope. That is a known limit, not permission to infer a historical parent or relabel an old native body. Resource reservation and constructor/initializer boundaries must be qualified before enabling the new admission.

Earlier run181620 exhausted the friend's native effect arena after missing stored-resource cleanup calls. The own-PID dump attributed the original fault to allocation failure, beneath secondary CLR exception recursion. Registry-first stored-handle admission and wrapper-specific scalar normalization now deliver cleanup: live05 applied1060 effect-fade and1066 attack-free records without an exception. These are delivered-call receipts, not a measurement of recovered native pool occupancy. Camera admission also now uses the exact role-owned native context, preserving story/loading/menu/frozen guards; retirement waits for the finite authored camera and native idle.

VUH-2707's diagnostic run 20261023-123953 reached friend-owned capture257 and camera40, then refused registration at the scope check after the native call. The client identity proof indirectly required SafeToWarp, which rejects that active camera. The correction uses the existing full-tuple/epoch arrival proof only after the client has already arrived; first arrival and ACK remain on the strict warp gate. Camera registration explicitly checks native field, menu, frozen, load and exact owner/source/asset identity. Gameplay still requires the registered camera proof. The production-client regression and exact-binary friend299/opening replay must qualify this correction before it is considered proved; the diagnostic fight failed, with install and saves unchanged.

Acceptance still requires a successful two-seat kill, one host mission16 and native315 publication, the same authored exit and onward control, qualified owner/clone motion and cleanup, and a captioned two-screen clip explicitly labelled single-PC loopback. Existing30-second recordings have encoder gaps; they must not be presented as uninterrupted footage.

Live08 candidate extends the existing RC path with native last-winner receipts and preaccept validation before action installation. Revival and both pilots observe that same product-qualified actionable reaction through the existing read-only version7 prompt fields. This changes the observation source only: routes, reach, timing and strategy remain live07's. Both seats must report the new hooks installed before leaving the boot room. Full native ABI/pin/refusal review and the governed build precede the attempt; no passing run is claimed. An interrupted accepted action without a qualified callback can conservatively fence later same-scope reactions. Late decision/cache/active-request traces cover that remaining runtime risk. Creeper birth integration remains separate from this kill attempt and is still required for final population parity.

Live08 (20261020-225646, build16, single-PC loopback) reached shared235/390HP. Opening297/298/299 passed the native acceptance and inline callback checks. The host was naturally downed three times and returned through native revival twice; the friend was then downed once and both pilots stopped after the full-party timeout. Neither log contains an exception. There was no kill, mission16, event315 or victory clip. Four protected saves,525 source inputs, 14 game-root entries and527 assets stayed unchanged; owned processes closed and the relay port was free. The534-pin source archive is retained with the run.

This attempt exposed two product defects, independently verified against that archive. Ground completion consumed the host occurrence, then an unused null third candidate with default ownerSlot0 overwrote its valid canonical player. Client acceptance used the host-only targeting table for its local-seat liveness, refusing even received owner1 occurrences. Build17 uses shared canonical seat resolution and checked local roots for both attack and captured command proofs, with regressions for two/three seats and empty client tables. Pilots remain unchanged. The lead's revised landing gate allows qualified product fixes after the full suite and live09 reaction completions on both seats; VUH-2569 stays open for the kill and Creeper parity.

Lead17 requires a newly built full suite and exact trimmed-binary short reaction proof before landing the qualified RC slice. Existing full-source run history above is retained as history and cannot be transferred to that trimmed binary. The archived live09 scenario and its strict kill/reward/exit assertions stay unchanged; the separate short proof fixture belongs to the lead. Deferred static terminal findings remain recorded below and require their own future qualification.

Live09 (20261020-233058, build17, single-PC loopback) reached shared158/390HP. Opening297/298/299 and ground reactions completed for both owners: host432 and345, friend345. A later friend-owned captured426 passed local native acceptance and callback checks but has no host completion record. Both pilots eventually stopped at the120-second no-progress guard; the friend remained below the arena. The available trace cannot distinguish a failed send from a silent host refusal, so this remains a product coverage gap, not an established pilot failure. There was no kill, reward, mission16 or event315 proof.

All six paired clip blocks finalized. Four protected saves,531 source inputs, 14 game-root entries and527 assets stayed unchanged, with no exceptions, remaining owned processes or occupied relay port. The exact540-pin source is archived with the run. Build18 removes the reviewed terminal bundles and adds diagnostic completion receipts from immutable claims, because native callbacks can retire or reuse their role/binding before returning. Its full suite and separate short no-kill reaction proof must qualify that exact binary before landing. Live09 evidence does not qualify the trimmed build.

Build18 passed202/202 tests. Before its short proof, main added the Day3 Sandlot/Serenity encounter rows; build19 integrates those additions and repeats the full suite for the final trimmed binary. The native RC code is unchanged. The separate short fixture has independent offline review of exact occurrence joins, two-pilot stopping, neutral release, clip drain and a sampled prelethal boss-HP guard.

Build19 passed202/202 serial tests (153.01s). Exact trimmed live10 (20261021-001728_net_twilight_thorn_reactions_1, single-PC two-seat loopback) passed all34 steps. Host-minted opening297/298/299 completed; ground432 completed for owner0 and owner1. The owner1 completion joins the exact host offer, client queued receipt and host callback for resource67/occurrence31. Inputs stopped at93.531s, both neutral releases succeeded, and the four raw clips finalized as two30-second paired blocks with recording gaps. Native completion records do not imply every event is visible in those blocks.

One earlier client queued432/resource28/occurrence14 has no host completion; its cause remains unknown. The host naturally went down once and no revive occurred. This qualifies the selected reaction milestones, not every reaction window, sustained survival, captured426, Creepers or a kill. All four protected saves,575 source inputs,14 game-root entries and527 assets stayed unchanged; closure found no remaining owned processes or relay listener. Independent result review also verified all584 pins and the575-file source archive. See the limited reaction result.

Deferred terminal static evidence

The installed mission routes boss signal4 through4/16 to native event315. Its source is world2/room34/event157, event ID0x353133, flags0x12, with semantic parameters {2,2,00330033,33,1,FFFFFFFF,3,0,0} (hex). Native39FBC0 leaves destination byte3 unwritten; the pinned3A4BD0 copies the destination into the descriptor. Only params1 high byte was ignored in the deferred exact-row qualification; full raw host publication/replay was retained. The authored exit is world2/room0/door0/programs51. These installed-data/native findings are not a runtime victory start receipt and do not enable the row in this slice. The full prior implementation/tests/docs are retained in the terminal-trim21 baseline and deferred reverse patch.

VUH-2807 defeat handoff: failed r1 qualification

The original zr100 kill lost the host's checked315 while the friend's generic death-event pause was Closing. The retained FIFO fix landed as4408b80 after Sage's exact-range approval. The subsequent kill run 20261025-140035_net_twilight_thorn_vuh2807_315_handoff_1 drained that handoff, but did not qualify acceptance. The friend still paused for the host's initial death camera and began its own defeat roughly7–10s later. Exact wall-time pixel skew remains UNQUALIFIED because the recordings lacked native capture-time receipts and had decode warnings.

Friend log180988 records a315 replay at owner frame32178, then a separate native 315 at32756 (578frames later). Footage showed one continuous camera/bonus/story sequence; permanent reward uniqueness and exact context replacement were not proved. The friend resumed with mission host=-, missing the transient end16 snapshot, so the expected host-led end seal was absent and step63 failed. Story/reward equality, cleanup and onward-control assertions were not reached. Full install541→541 and all four protected saves were unchanged; owned processes and relay closed. The paired clip, decisive log lines and follow-up proposal are attached to VUH-2807.

The r2 candidate retains the validated end16 occurrence and gives one qualified native owner the initial death camera through315. The exact content, native last-dead-boss focus, helper pins, control lifetime and unchanged input safety requirements are documented in Mission mirror. Its read-only native audit and owned-memory checks do not qualify live timing, reward equality or onward control. A new exact-range review and scheduled live run remain required. The Closing FIFO and ordinary safety gates remain required; Shan-Yu's4/16 exclusion remains unchanged.

Full-fight candidate and live11

The subsequent full-fight candidate restores the reviewed host-only terminal path under protocol31: signal4, mission4/16 and the exact authored315 event. Clients do not blindly replay4/16. These semantics remain unqualified by a kill.

Build23 passed all202 tests. Live11 (20261021-020601, single-PC loopback) ended in native full-party defeat at step39 with shared boss HP268/390. Earlier revives worked in both directions. The host's later downing remained at Y=-251.985 while the friend was usually near0, outside the unchanged3D revive range. In this coordinate system negative Y is upward; earlier wording describing a negative-Y player as below the arena was incorrect.

All eleven remote reaction completions reached host application. Nine applied; two captured426 replies were refused after host-role retirement, before the producer-frame guard. The retirement trigger remains unknown. There was no trace saturation, kill, mission16/315, reward or cleanup proof. Four protected saves and all source/game baselines were unchanged; closure was clean. See published reports and stills.

The approved next candidate holds only downed XZ and preserves native Y. Static qualification shows the old XYZ hold prevented settling away from the lethal height; it does not establish that this alone caused live11's loss. Additional observational retirement rows retain the original reads and order. The combined full suite and a short FM-02 Computer Room grounded down/revive regression must pass before Thorn live12. Pilots and3D revive range stay unchanged. Creepers remain the documented VUH-2605 gap; VUH-2569 stays open for the kill and426 cause.

Build24 passed all 202 tests. Its separate Computer Room regression 20261021-035356_net_downed_grounded_pair_1 passed all 105 steps in 163.6 seconds. Each owner entered logical downing through a real lethal hit damage, retained grounded native XYZ during attempted movement, then revived once through the normal Triangle/network path to 5/22 HP, Ready state, fault0 and 120-frame grace. Both regained ordinary movement. Four protected saves and all recorded baselines were unchanged; closure and the exact 538-file source archive passed independent review. Four native stills were inspected. This calm check has no actual enemy shove or airborne landing; Thorn live12 remains required on the same binary.

Live12 (20261021-040907_net_twilight_thorn_rehearsal_1, exact build24, single-PC loopback) failed step41 after five paired combat blocks. Both seats ended at boss176/390. Opening297/298/299 and four friend-owned ground reactions completed; eleven accepted friend hit claims contributed64 damage. The host was naturally downed twice and revived once through the normal request/native path to5/20 HP, Ready state and fault0. The final recovery never reached another hold or request: sampled separation remained492-1175 units while native RCs retained their intended priority. All56 sampled host HP1 rows had Y0. No lethal-Y trajectory or native grounding/attachment state was recorded, so this does not prove an airborne landing or a new height defect.

All six remote reaction completions reached host application; four succeeded. Captured426 occurrence63 was accepted by the friend's native leaf and callback, but found its host role already retired. The new immutable row identifies the first D48 read returning zero against its saved coroutine, two frames before host application. Later predicates were unevaluated. This is a remaining product qualification investigation, not proof that retirement was wrong, that a packet was lost, or that it alone caused the loss. The native writer/BDX exit remains unproven; the whole run cannot yet be certified pilot-only. Pilots are unchanged.

The known enemy-only Creeper317 population desync recurred with equal progress hashes. Its automatic bundle was partial because of a changing log tail and busy capture leases. There was no kill, mission16/315, reward, final role/camera cleanup or onward-control proof. Four protected saves and all540 source inputs, 14 game-root entries and527 assets were unchanged; closure left no owned processes or relay listener. The exact540-file/553-pin source archive predates edits and passed independent verification. Subsequent Ivo VUH-2580 source changes are integrated on mainf42c3f9; live12 does not qualify that rebuilt composition.

Live13/build25 failed after523.5s, boss194/390 on both seats. Both pilots reached the60-second recovery guard; no normal revive request or native return occurred. All seven remote reaction completions reached host application; five succeeded and two found their occurrence missing. Three captured426 roles reached the native scheduler cancel leaf before the first zero D48 retirement read. This identifies that cancellation path, not the authored cancellation reason or the earlier live12 writer. The whole run remains unqualified as pilot-only.

Published live13 evidence includes the bounded two-screen failure clip, decisive logs/reviews and exact pre-edit source archive. The actual1/238 observer and sole3D6F80 cancel hook installed on both seats; no associated1/14 row was captured. Its argument-based association missed a different operand shape. Four protected saves and all recorded baselines stayed unchanged; owned processes and relay listener closed. No kill/16/315/reward/final cleanup or onward-control proof follows from this run.

Lead43 approved an observation-only1/14 correction: select the unique currently executing admitted VM, log raw input/output, and label the target unresolved. Never decode/dereference that alias or infer command authority from it. The correction has independent offline reviews; its next build and runtime proof remain required. See Script Mirror. The next kill attempt is human-piloted FRIEND/seat1 with the unchanged HOST bot, using a reviewed handoff and exact owned-process abort. No extra bot run is scheduled for diagnostics. Ivo's main724ddcb residue changes are composed and independently reviewed; live13 does not qualify that later composition. Pilots, protocol31 and3D revive range stay unchanged; Creepers remain VUH-2605.

Mainc07d8da (VUH-2610r2) extends only spectator playback for chained captures. A changed capture remembers its previous motion until the first heartbeat naming anything else. A still-previous heartbeat selects the newer authored capture and cannot write its old motion time. Once caught up, a later old ID is judged by the unchanged borrowed-bank/refusal rule. Consumed reactions remain refused; camera, commands, local-owner native calls and wire31 are unchanged. Independent composition36 preserves the corrected observation and existing cleanup paths. Build27 and the human14 packet refresh qualify the combined inputs separately; old build26 evidence does not become a result for that new binary. Missing262/263 capture descriptors and Creeper population parity remain separate gaps.

Combined build27 on c07d8da passed all202 tests with its320 native inputs unchanged. The refreshed human14 packet remains held by lead51: Ivo's separate VUH-2611 visual12 candidate achieved a kill, then HOST crashed in clr.dll after the post-boss event began. Its cause and applicability to build26/27 are unknown. No human14 run or baseline is claimed. Packet postvictory checks introduce no managed call into KH2; process-exit detection is independent of the inject crash filter, but no dump or recovery is guaranteed. Investigate before asking James.

After the kill: the post-Thorn scene chain (VUH-2617, bot04)

Bot04 (20261021-192441) killed Thorn and both seats played native315, but the friend stayed in 02/34. After315 the host loaded seven event-only locations in a row, each started by the previous one's native start: 02/00 51, 02/04 83, 02/02 67, 02/06 168, 02/02 167, 02/15 142, then 02/01 54 (rooms in hex as the log prints them, so 02/15 is room 21; map, battle and event program, decimal, equal in each). None reached field play: the gameplay gate never opened, so the host's census and progress samples never ran. An unqualified room is announced only from field play, so the host announced none of them, and the friend waited at its own blocked native exit to the first one, 02/00 51 (the authored exit above). The first six are now qualified scenes (EventScenes.hpp): the host announces each at its load and the friend loads and plays it natively, as in the prologue's post-Axel chain. The chain's end was observed in the VUH-2763 qualification (run 20261027-114125, VUH-2918): after 02/15 142 the host loads 02/01 54, where it plays the me4 movie (Roxas to Sora), then 02/01 59, both event-only (the gameplay gate stays closed; field play lasts only the frame of the next native start). With 02/01 54 unqualified the friend waited at its own blocked exit to it for the rest of that run and never played the movie. 02/01 54 and 59 are now qualified scenes too, so the chain is qualified through 02/01 59. After it the host plays two more event loads, 02/03 door 50 map 2 evt 2 (an opening dialog that waits for input) and 02/05 evt 1, and reaches field play at 02/05 door 50 evt 2, which it announces. Proof run 20261027-125601 (VUH-2918, accepted from receipts; its scenario runner was red because it expected the field at 02/03): the host announced 02/01 54 and 59 (epochs 10/11), the friend loaded both from its own blocked exits and played its own me4 through its SaveGuard twin, and both seats ended in 02/05 door 50 evt 2 with field play and no event. The friend currently skips 02/03 door 50 and 02/05 evt 1: its blocked exit to 02/03 takes the host's 02/05 field announcement instead. Whether they should be qualified scenes is a follow-up under VUH-2569. A returning seat's recovery capture is refused in a qualified scene (it waits, epoch unspent, for a later field), so post-Thorn recovery now waits past this chain too; its convergence after the chain is unproven.

The same run's other failure (step69: the friend's own HP never fell during Thorn) is not explained yet. The friend's mirrored Thorn built no hit at all on the friend ([enemy-mirror] hit 0, [hit] attacker B_EX100 0, with 18 of the 60 per-room rows unused), while the host's Thorn hit the friend's clone 12 times (eleven attack 1014 during motion 202 at the arena edge, one 448). 1014 and 448 are not script attacks (Thorn's script creates 631, 1305, 1015 and 1041, which hit the host); in bot02 the friend was hit natively by motion attacks 1034/1035 (motions 204/226). Thorn was never retargeted at the friend (bosses keep their own targeting), the friend never guarded, and its ScriptMirror replay kept pace with the host. Static analysis (headless Ghidra on the existing kh2_full project): the mirror's brain skip removes only the boss's BDX script tick (0x419750 -> FUN_1403b4460, the script at actor+0x5B0); native motion playback still runs. The one hit gate found is on the victim: FUN_1403d35f0/FUN_1403d2a20 nullify a hit when (+0xD10 | +0xD14) & ~+0xD18 has bit 9, which Thorn's script sets on the canonical player and itself during atk_thorn (obj_pattern_enable, trap 1/211, not mirrored). That explains the host side (its player immune, the clone not), not the friend's. Motion 202 is atk_ground, aimed at the boss's own target. KH2COOP_THORN_HIT_TRACE=1 (default off, reads only) gathers observations for the next live run. Every 30 frames each seat logs [thorn-trace] host|client hostFrame=... with its local player, both clones and (on the friend) the driven boss copy: position, motion, hit-pattern mask and the boss copy's motion time. Each actor is read only inside its own update, after its identity is proven there (the list head and canonical player; the driver's applied, current clone whose metadata still matches its binding; the boss copy the mirror bound in that update), never through a cached pointer; anything unproven prints -. hostFrame is the host's frame counter, and on the friend the mirror cursor sampled when the boss copy was captured: a sample, not exact per-actor frame alignment. The 3D2060 hook also logs the first check of some enemy attacks against a player ([thorn-trace] canhit ... atkp=... victim=...(local|clone) native=0|1). These are positive observations only: the rows have a 400-row budget and a 64-entry pointer-pair deduplication, so they are not a census of attacks (an unreadable or unclassified input, an upstream filter or a reused pointer also yields no row), and a native yes there precedes the later victim and damage gates, including the pattern gate above. The same hook also traces every check of an attack against Thorn (B_EX100), as [thorn-trace] victim ... attacker=...(local|clone|other) source=... atkp=... pattern=0x... native=0|1 answer=0|1. Each row carries:

• the attack's owner and source;
• Thorn's hit pattern at that check (bit 9 nullifies the hit in the later victim gate);
• the native answer and the answer the hook returns.

An (attack, Thorn) pointer pair gets at most two rows while it stays in the 64-entry seen table: its first check, and its first native yes. Thorn's own attacks refused against itself aren't rows, except its 202 projectile (atkp 1041). A refused 1041 check is a row, so a run can tell an orb that never reaches Thorn's check from one that reaches it while still Thorn's and is refused. pattern=0xFFFFFFFF means the pattern was unreadable, not that every bit was set. The budget is 600 rows (VUH-2617 live09: nothing damaged Thorn in 202).

These are positive observations only, as with the rows above. Eviction can let an old pair log again, pointer reuse can hide a new attack, and a missing row doesn't prove that an attack never reached Thorn.