Context
BRAIN_QUARANTINES (buildScripts/util/e2eCiSelection.mjs) holds six entries, all accountable to me. One of them has met its exit, "a diagnosis lands as a fix or a ticket": the fix is #19713, merged via #19715. connectToApp had silently bound the oldest same-name session whenever the page's App Worker id was not readable on the first try.
Evidence, WorkstationReclaimEmbodimentNL :148 on the fixed fixture: first-try passes in all 3 full-tier runs, the two runs of probe #19716 (never merged) and #19719's run 38422728929. Before its quarantine it had needed the retry in 3 consecutive dev runs.
Narrowed 2026-10-13. This ticket first took DockMotionNL's rail reveal out too, because it passed both probe runs. In #19719's run 38422728929, on dev with the fix, it failed both attempts with its quarantine symptom: "the entry witness must have observed the revealed overlay". The two probe passes were intermittent luck; the fixture fix is not its cause, so it stays quarantined.
The Problem
A quarantined spec does not run in the Brain-gated tier, so whatever it covers is unguarded until it is un-quarantined. The entry dates from 2026-10-13, and every receipt flags it stale from 2026-10-20.
The Architectural Reality
Each BRAIN_QUARANTINES entry becomes a test-list line through testListLine, and the full tier skips it. Removing an entry is the whole un-quarantine. The retry bridge (BRAIN_RETRY_BRIDGE, until 2026-10-25) still covers a single intermittent failure, and a spec red on both attempts fails the run.
The Fix
Delete ReclaimEmbodiment :148's entry. The other five stay, each with its own reason:
- DockMotion's rail reveal: red on both attempts on the fixed fixture.
- FiveBeat dwell previews: still intermittent.
- PopOutSparklines: red on both attempts with its own symptom.
- FilmTour: two entries, a deterministic stop at hop 3.
Acceptance Criteria
Out of Scope
- The diagnoses of DockMotion's rail reveal, FiveBeat dwell previews and PopOutSparklines.
- FilmTour's two entries.
- The retry bridge.
Related
#19655 (parent) · #19713 · #19715 · #19716 · #19719
Live latest-open sweep: the latest 20 open issues at 2026-10-13T15:29Z, plus an open search for "quarantine"; no equivalent. A2A claim sweep (latest 15): no claim on this scope. Own open assignments: none overlapping.
Retrieval Hint: "Brain quarantine exit ReclaimEmbodiment after connectToApp identity fix; DockMotion rail reveal not cured"
Context
BRAIN_QUARANTINES(buildScripts/util/e2eCiSelection.mjs) holds six entries, all accountable to me. One of them has met its exit, "a diagnosis lands as a fix or a ticket": the fix is #19713, merged via #19715.connectToApphad silently bound the oldest same-name session whenever the page's App Worker id was not readable on the first try.Evidence,
WorkstationReclaimEmbodimentNL:148 on the fixed fixture: first-try passes in all 3 full-tier runs, the two runs of probe #19716 (never merged) and #19719's run 38422728929. Before its quarantine it had needed the retry in 3 consecutivedevruns.Narrowed 2026-10-13. This ticket first took
DockMotionNL's rail reveal out too, because it passed both probe runs. In #19719's run 38422728929, ondevwith the fix, it failed both attempts with its quarantine symptom: "the entry witness must have observed the revealed overlay". The two probe passes were intermittent luck; the fixture fix is not its cause, so it stays quarantined.The Problem
A quarantined spec does not run in the Brain-gated tier, so whatever it covers is unguarded until it is un-quarantined. The entry dates from 2026-10-13, and every receipt flags it stale from 2026-10-20.
The Architectural Reality
Each
BRAIN_QUARANTINESentry becomes a test-list line throughtestListLine, and the full tier skips it. Removing an entry is the whole un-quarantine. The retry bridge (BRAIN_RETRY_BRIDGE, until 2026-10-25) still covers a single intermittent failure, and a spec red on both attempts fails the run.The Fix
Delete ReclaimEmbodiment :148's entry. The other five stay, each with its own reason:
Acceptance Criteria
BRAIN_QUARANTINESno longer listsWorkstationReclaimEmbodimentNL:148. The other five entries are unchanged.devruns it is never red on both attempts. If it is, it goes back into quarantine with the new symptom.Out of Scope
Related
#19655 (parent) · #19713 · #19715 · #19716 · #19719
Live latest-open sweep: the latest 20 open issues at 2026-10-13T15:29Z, plus an open search for "quarantine"; no equivalent. A2A claim sweep (latest 15): no claim on this scope. Own open assignments: none overlapping.
Retrieval Hint: "Brain quarantine exit ReclaimEmbodiment after connectToApp identity fix; DockMotion rail reveal not cured"