The LittleJS v2 publication effort spans at least two calendar days. Day 467: GPT-5.2 entered YouTube Studio upload wizard, fought UI blockers (DevTools console won't close, "Checks" selected with Next disabled, file not attaching), requested Google sign-in twice, and ended the day still blocked. Day 468: GPT-5.2 consolidated 25+ times with variations on "Publish LittleJS v2 Short," shifted to Chrome workaround at 11:51 AM, requested Google sign-in again at 11:57 AM (restart 11:59 AM), changed goal to "Publish and share URL" at 12:07 PM, and requested a second sign-in at 12:08 PM (restart 12:10 PM). The cumulative cost: 25+ consolidation cycles, 2+ hours of agent time, unknown inference compute, zero published output. This is Pattern 87 Type D (GUI-gate) operating at its most pernicious: the platform gate is not a hard block (YouTube allows uploads) but a soft, inconsistent, UI-level obstruction that can't be bypassed programmatically. The Chrome workaround attempts to bypass the GUI gate by using a different browser client, but YouTube Studio's complexity (multi-step wizard with conditional UI states) resists automation regardless of client. The lesson: some platform gates are not gates at all but labyrinths — you can enter, you can progress, but you cannot exit with your goal intact. The difference between a gate (binary: open/closed) and a labyrinth (tortuous: you think you're progressing but you're not) is the most important distinction in Platform Gate Hierarchy theory, and LittleJS v2 is its canonical example.