Q3 orderly original progress, 0924
The Q3 composition pins the released owning caller from d90eb457c literally
at SHA256 d3b9927b17372e74ef0abc8f43b59e709b1822d4927d7793c0153b07cda6509d.
Missing, changed and retired caller controls refuse before launch.
The Q3 composition now supports an explicitly requested ordinary fixture quit
after the whole corrected fixture completes. Its positive command retains ACK0;
the external owning caller verifies that receipt before issuing ordinary quit1
through its released Session.request path. Automatic fixture exit remains
terminal to that caller. No shared client, custody, host or WAT is edited here.
A separate opt-in native cancellation checkpoint waits at most 10 seconds after the whole fixture while its real browser and Workers remain alive. Owning caller cancellation must abort the existing cancellable wait. Expiry fails closed; the marker alone supplies no native cancellation proof. The original is gated on ordinary fixture completion and independent actual cancellation waits/drain.
Focused Node controls exercise both changed paths through the actual composed consumer, including pending quit without ACK, normal browser wait and pipe EOF, prompt sticky cancellation, no later input/capture, and absent cancellation. These controls do not supply native guest or Boat cancellation proof. The unchanged original route and fixture normalize byte-for-byte to accepted 0912 source after removing only the new opt-in fixture completion seam. Accepted startup and input proof are reused by source/hash/size rather than rerun.
Evidence: scratch/runs/20261109-q3-orderly-original-progress-0924/.
The red shape and Enter interval remain fixture evidence, not guest polling or
simulation. Native lifetime is REVOKED; allwriters and edictABA remain UNKNOWN.
The exact shared caller d90eb457cccfbbd917c889e99a7a38dcd67aa0a7 was committed,
tested and released before freezing the 924-provider closure. Integration
b7cb69cb3c46d5471c0a4024f33d2dcb06aba3b9 passed the changed missing/changed/
retired-caller controls, joined fixture controls, cancellation controls and
locked build, then was immediately pulled/pushed on main and authenticated by
explicit strict SSH. The worker's 26 full PIPE controls and unchanged startup/
input proof were verified and reused. One offline preparation mismatch used the
old startup test hash instead of its accepted pin-only update; this was corrected
and retained before allocation. All three local and remote strict prelaunch
checks passed. No repeated qualification or source/media/module archive.
After Redline UUID 63fe41f0-f079-4e9b-8640-59e24075229e was archived and
physically drained under stop_b1519e6df3660c1e, the sole box was
bx_npc7tj6a, immutable UUID a35c3041-10ba-4601-b45c-6e6c86d68149,
initial expiry 2026-11-09T09:59:12.188Z. Its independent 25-minute watchdog
was observably armed before create. Required calc HTTP200, SHA256 and 94208-byte
size were checked before Chrome. Parked preCPU/preDLLmain admission matched the
live owning module/instance/endpoint1/slot0 and all flags, then explicitly released.
First actual unexpected failure was at 2026-11-09T09:36:11.133Z:
input delivery exceeded hold bound, during the fixture's first 100ms Enter.
The physical completion record shows keyup attempted at 101ms, keydown reply
completed at 3546ms, and actual keyup reply completed at 3547ms. There are no
held samples, no positive input capture or ACK, and no whole-fixture completion
or ordinary quit. These reply times do not prove an actual held interval or
guest polling. The personally reviewed pre-failure PNG is only the generated
red GL shape. No cancellation prerequisite run, original, movement/fire/torch,
later native input/capture or retry followed. Cause beyond the bounded delivery
failure remains UNKNOWN. The caller's failure cleanup marker does not prove
the planned actual Boat cancellation prerequisite.
Independent no-input cleanup recorded 166 owned identities and 166 actual
reaps, complete kernel command EOF, no unresolved/remainder/unreaped entries.
The generated parent, prelaunch child and runtime parent actually waited1;
stdout/stderr or combined EOF is recorded separately. Chrome and its owning
consumer were actually reaped with SIGKILL; no normal Browser.close ACK is
claimed. The local owning launch transport actually waited -9 and cancellation
transport0, both with separate stdout/stderr EOF. Closed ports44529/41423,
absent writers/free locks and independently retired profile are separate checks,
never substitutes for waits. Normal shutdown of the box was unforced:
stop_7aeead8279799716, completed 2026-11-09T09:36:58.337Z, ARCHIVED
PHYSICAL_DRAINED. Final archiveAfter null; expiresAt not returned. Allocation
watchdog and its owning lifecycle parent each actually waited0 with separate EOF.
The board-tail watcher actually waited -9 when its independent deadline fired;
its watchdog waited0 and both pipe EOFs were separately recorded.
All 257 remote regular artifacts were accounted for before archive: 161 unique contents were independently retrieved and SHA/size reread, including 26 original gzip CRC/footer checks. The 55 unique task logs/captures/receipts remain retained. The other 106 contents were this task's disposable retired Chrome profile cache blobs; their SHA/size and prearchive verification are retained, while their new local copies were removed to avoid preserving cached source/media. No predecessor archive or unique task evidence was removed. Git base plus relevant small patches and owned run-input patches supply source recovery; media remain path/SHA references.
The concrete blocker is bounded native input delivery, before the repaired orderly completion path could be reached. Next is offline diagnosis of that timing path before another explicitly authorized runtime; no cap relaxation or retry here. Native lifetime REVOKED, allwriters/edictABA UNKNOWN, actual Boat cancellation NOT_PROVEN. SingleTaskSTOP.