Pawn actual production consumer controls qualified; native progress capacity blocked

Run scratch/runs/20261113-pawn-real-consumer-guard-0640/ qualifies the unchanged parent0600 observer/comparator against actual production consumers. No Pawn original launched, input was sent, or native AI reply was observed. After qualification, the one fresh original-launch decision measured 1,472,294,912 bytes available on /home, below the strict >1,500,000,000 floor by 27,705,089 bytes. This is the distinct causal blocker for native progress. The launch decision was not retried or polled; protected media, Dense0340, LMarbles0620 and recovery bytes were not changed.

The small integration check uses test/render-helper.js with the existing current module SHA-256 04c534192ee3fe39e388536c2ce710c12c47a5cd2ca4d95c19f9d00b1e8f0a17. It evaluates the exact createD3DRenderWorker factory expression extracted from current test/run.js, with its real module, shared memory, instance, signature table and native heap-reclamation callback. createHostImports(ctx) performs the actual createSoftwareWorker wiring and creates the production lib/d3d9-host.js Bridge. A tiny clear packet creates its asynchronous software device and queue, and a queue fence proves actual Worker commands completed. The bridge-level WorkerConsumer is the consumer on this legacy route. sharedWorker stays false throughout; no route predicate was bypassed.

The integration fixture loads existing Notepad only to initialize its allocator, image base and nonzero EIP; its instructions are never run. Its ordinary test renderer window uses the default hwnd0. The 8x8 clear packet is fixture data. These are real production Worker/Bridge/device/queue objects, but this test does not establish Pawn's live window, guest execution or gameplay. The first two development attempts correctly refused Calc's 0x1000000 image base; diagnostic evidence remains in attempt1/ and attempt2/. The fixture was corrected to Notepad's existing 0x400000 base without changing the guard.

actual-consumer-result.json records accepted real binding and refusal after temporarily replacing its Worker with a second real initialized Worker, removing the Worker, replacing/removing the consumer, setting release state, or changing queue/bridge generation. Each reversible control restores the real owner and verifies acceptance again. Actual device Release and recreation produce a different device and incremented generation; the old binding is refused. The same focused integration check's explicit error extension is failed-owner-control.cjs: an invalid fixture viewport causes a real production Bridge error, which the guard refuses even while its Worker remains alive. failed-owner/actual-consumer-result.json records that control, fresh recreated binding acceptance, and refusal of actual closed/retired ownership. These controls observe live objects, rather than editing copies of observation snapshots. Parent0600's snapshot-only mock controls were not promoted to live acceptance evidence or used as its substitute.

Each small check prearmed an independently observable 60-second watchdog before creating its test process. Both successful checks and watchdogs have actual parent wait0 and separate stdout/stderr EOF receipts; all their PIDs were absent afterward. Both initialized Workers retire through the production shutdown path, ending at threadId -1. The main Worker reports one device released, allocatedBytes0 and native heap adoption2; the unused second Worker reports allocatedBytes0 and adoption0. No Present, repaint, mouse/keyboard input, original-game memory/config/clock/AI write, substitute board, automatic player, or historical GetDC reinvestigation occurred.

Before the original capacity decision, frozen.json pinned the exact current04, all 319 relevant source/media paths, six original media and prepared input helpers at Git d86190e8617f6c26d42df1034b6ddd0484aeba2b. The original helpers retain independent finite mouseUP, deadline, identity, no-replay/UNKNOWN and separate fresh full-board/legal-turn review requirements. The original runtime and its 600-second watchdog were not started after floor refusal; their wait/EOF are N/A, not successful completion. The error-control extension was added separately; frozen original-launch helpers remain byte-identical.

postchecks.json, owned-helpers.patch, relevant-source.patch (empty), relevant-untracked.patch, path/SHA pins and SHA256SUMS.json preserve scope and recovery without source archives or copied game media. The parent0600 sealed evidence still verifies. Syntax checks and the focused actual-consumer integration pass. No production files changed; no production fix or locked build is claimed or needed for this note-only commit.

Next: after an actual capacity change, use a fresh namespace, exact pins and independent runtime deadline; bind this qualified guard to one current original, personally review its full board, then make two separately reviewed finite legal moves with independent mouseUP and observe each native AI response.

Box ID none, state NOT_CREATED, expiry null, stop receipt N/A. No task-created box or runtime remains active.