Context
#19918 fixes the two causes inferred for the quarantined Workstation film tour: a vessel closed mid-boot kept its tear-out slot bound (#19898), and a window that left mid theme-load held every vdom update (#19899). Its unit arms prove both defects. It also took both film arms out of BRAIN_QUARANTINES, and its first hosted run (job 118662525686, shard 8 of the Brain-gated tier) showed what remains:
- The viewer-driven arm passed on its first attempt. Its journey births and retires every vessel; the old logs stopped at hop 3.
- The autoGates arm failed attempt 1 at hop 4 and passed on its retry:
journey hop 4 (target): the target did not take the drag as one semantic + rendered claim. The new diag line at that failure reads binder=null binderPort=null themeFileLoads=0, with isWindowDragging=false reattachArmed=true lastRatio=1 connects=false staged=false activeVessel=false, and the vessel open at stage granted.
- The shard's step timed out at its 5-minute limit (
The action 'Run the Brain-gated tier' has timed out after 5 minutes). The two film arms, plus a 76 s retry, landed in one shard.
So hop 4 has a third mode that neither fix touches: the slot is free and no theme file is in flight when the target refuses.
The Problem
Until hop 4 is diagnosed, the film arms stay quarantined (#19918 restores both entries with this reason). They also cannot leave quarantine as they are: even when green, the spec takes about three minutes of one shard's five.
The Architectural Reality
- The hop runs
NativeGestureDriver#executeJourneyStep (apps/workstation/tour/NativeGestureDriver.mjs); a target hop polls readCrossWindowGestureSnapshot until it is ready, and ready requires the proxy to have settled (apps/workstation/view/CrossWindowGestureSnapshot.mjs ~121).
- The diag now prints the binder, its port and the theme count at every hop failure, so both inferred causes are excluded per failure.
- Brain-gated shards:
buildScripts/util/e2eCiSelection.mjs selects files, and Playwright shards by file across 10 jobs, each with a 5-minute step.
The Fix
- Diagnose hop 4 from the next failures' diag lines and the target's snapshot (
claim, preview, settled), and fix what it names.
- Give the film spec room: a shard of its own, or a step limit that fits it, agreed with the tier's owner (#19655).
Acceptance Criteria
Out of Scope
The two causes #19918 fixes.
Related
#19898 · #19899 (their AC-3 moves here) · #19918 · #19655 (the tier) · #19543 (the journey cue)
Live latest-open sweep: latest 20 open issues at 2026-10-20T15:47Z, plus gh search issues for "film tour hop 4" and "five-minute step shard"; no equivalent
A2A claim sweep: no claim on the film tour since my 13:44Z #19918 broadcast
MC sweep: "film tour journey hop 4 target did not take the drag, proxy settled false, Brain-gated shard step times out after five minutes", 5 results, the journey's original build only, no prior decision
Own-assignment sweep: #19898 and #19899 are this ticket's parents; nothing else touches the film tour
Retrieval Hint: "film tour hop 4 target refuses drag binder null themeFileLoads 0 shard timeout"
Origin Session ID: dcd54a9c-cc39-4b54-b3f3-f892704cfa86
Context
#19918 fixes the two causes inferred for the quarantined Workstation film tour: a vessel closed mid-boot kept its tear-out slot bound (#19898), and a window that left mid theme-load held every vdom update (#19899). Its unit arms prove both defects. It also took both film arms out of
BRAIN_QUARANTINES, and its first hosted run (job118662525686, shard 8 of the Brain-gated tier) showed what remains:journey hop 4 (target): the target did not take the drag as one semantic + rendered claim. The new diag line at that failure readsbinder=null binderPort=null themeFileLoads=0, withisWindowDragging=false reattachArmed=true lastRatio=1 connects=false staged=false activeVessel=false, and the vessel open at stagegranted.The action 'Run the Brain-gated tier' has timed out after 5 minutes). The two film arms, plus a 76 s retry, landed in one shard.So hop 4 has a third mode that neither fix touches: the slot is free and no theme file is in flight when the target refuses.
The Problem
Until hop 4 is diagnosed, the film arms stay quarantined (#19918 restores both entries with this reason). They also cannot leave quarantine as they are: even when green, the spec takes about three minutes of one shard's five.
The Architectural Reality
NativeGestureDriver#executeJourneyStep(apps/workstation/tour/NativeGestureDriver.mjs); a target hop pollsreadCrossWindowGestureSnapshotuntil it isready, andreadyrequires the proxy to havesettled(apps/workstation/view/CrossWindowGestureSnapshot.mjs~121).buildScripts/util/e2eCiSelection.mjsselects files, and Playwright shards by file across 10 jobs, each with a 5-minute step.The Fix
claim,preview,settled), and fix what it names.Acceptance Criteria
BRAIN_QUARANTINES.Out of Scope
The two causes #19918 fixes.
Related
#19898 · #19899 (their AC-3 moves here) · #19918 · #19655 (the tier) · #19543 (the journey cue)
Live latest-open sweep: latest 20 open issues at 2026-10-20T15:47Z, plus
gh search issuesfor "film tour hop 4" and "five-minute step shard"; no equivalent A2A claim sweep: no claim on the film tour since my 13:44Z #19918 broadcast MC sweep: "film tour journey hop 4 target did not take the drag, proxy settled false, Brain-gated shard step times out after five minutes", 5 results, the journey's original build only, no prior decision Own-assignment sweep: #19898 and #19899 are this ticket's parents; nothing else touches the film tourRetrieval Hint: "film tour hop 4 target refuses drag binder null themeFileLoads 0 shard timeout" Origin Session ID: dcd54a9c-cc39-4b54-b3f3-f892704cfa86