LTris normal browser: authored admission transport blocker, 2026-11-18

No original was launched. No real Controls screen, gameplay board, line clear, score/line-count consequence, or ordinary Quit was observed. The required authored controls did not qualify. This task stops at a bounded authored transport failure; it establishes no LTris runtime defect or repair.

Evidence: scratch/runs/20261118-ltris-normal-browser-manual-line-clear/result.json. The previous November 17 native UNKNOWN scopes were never contacted or replayed. Their withdrawn menu-as-board descriptions remain withdrawn.

Concrete boundary

In control3, passive page metadata reported an authored SDL window, slot 0, endpoint 1 and completed 2D publication. Moving the host pointer to (0,0) through an independently connected, shared-admission-guarded transport removed the touch-cursor overlay from the output visibility check. This was pointer motion only, without a button edge; it is not gameplay evidence.

Exact parent discovery found one child Worker with an empty descriptive URL: page 35AEE50C615CEB527E35CADB494E2CFF, child 139692F3CD8CCC9C8D8CB7BE33128187. Request 253, Runtime.enable, was issued at epoch milliseconds 1794996370790 to session E3E39C6A3F720209E0C6B3C5CFAD7468. No reply was retained. The fixed 3000 ms timeout closed shared admission at 1794996373790 and the local record at 1794996373801. There were zero subsequent ordinary requests on that transport. The child's lexical role and executing module were not established. Calling it the main Worker in the progress update was stronger than the available proof.

No whole-frame capture completed, so the metadata is not a personal visual review of an authored window or a gameplay board. No key DOWN/UP was sent. Menu, Pause, release, and Quit controls remain unqualified in this task.

Attempts and limitations

Four authored setups, no original:

Optional stdole type-library requests returned 404 because they were absent from the served allowlist. This limitation and the authored entry mistake are harness problems, not evidence about original gameplay. No production helper or runtime was edited; native/browser old-fail/new-pass repair validation and a new locked build are not claimed.

Frozen inputs and limits

The memory-only source graph used published Git cf132e191c3e795842b824c17f75c0eda3ea5584, excluding foreign worktree changes. The retained compiled module is 2,418,710 bytes, SHA-256 a6002d5dbcfeb534a0eadd223da616e525aa1542dad2bde381fe54e00ee862f8. Use prepared.json for the authoritative size, hash and complete source list. Actual Worker instantiation bytes remain unverified because discovery failed.

The disk owner published/froze tools/browser-disk-admission.cjs in cf132e191 and explicitly permitted hash-matched reuse on the messageboard. It composes with the published ReVolt connection helper and process-input-owner.cjs. dependency-freeze.json verifies those live bytes against the frozen Git. No live unpublished helper was imported. Later foreign overlay changes were not adopted into this frozen graph. The run-local harness is not published or qualified as a reusable controller.

Predeclared limits: startup 180 seconds, authored scope 300 seconds, original 1200 seconds, final 180 seconds reserved for Quit, cleanup 20 seconds, ordinary transport 3000 ms, independent release fallback 5000 ms, hold maximum 1200 ms, 80 captures. No runtime cap was extended. The original clock never started. The authored fixture used the published SDL keyboard PE recipe with only its filesystem-output tail changed to return its bytes into this run directory.

All 43 original EXE/media/manifest/CRT/ZIP pins match afterward, including the unchanged registered ltris_128, cwd C:\LTRIS, argument -w, and all 39 companion mappings. No original settings, clock, save or state was modified. No solver, OCR, guest board memory, autoplay, synthetic score or action replay was used. The preemptive disk boundary was 1.7 GB, above the 1.5 GB floor; control3's watchdog minimum was 1,882,214,400 bytes. Control2/control4 have no final watchdog minimum record because of their retained EEXIST failures.

Cleanup and recovery

All 86 recorded owned process IDs were absent at verification; containment receipts report no leaks. All four Chrome profiles were removed. Browser, enclosing supervisor, independent watchdog and board-watcher child processes have actual close waits and both pipe EOFs. The watchdog failures are not passes. native-supervise.cjs records the direct controller's exit with inherited streams; a separate controller pipe-EOF receipt and outermost launcher EOF receipt were not retained. Complete lifecycle proof is therefore false.

Source recovery uses the exact Git graph plus relevant binary diffs and run-input patches, never a source-tree or media snapshot. There are no retained screenshots, because capture was never admitted. RECOVERY.md describes the fixture and module reconstruction and the run-input provenance limitation. Do not execute the retained harness against a closed endpoint or use it as a tested dependency. No agents, workers, boxes, Python, Wine, public deployment or held-title actions were used. Box ID null, state NOT_CREATED, expiry null, stop receipt null. Ownership released; stop.