Airstrike pre6a independent gameplay acceptance — 2026-10-24

Accepted producer 770044fdbb409a54d21090c040482daf627c2a35 for bounded movement and firing on the retained historical module. This review used retained evidence without running a guest, allocating a box, compiling, installing packages or reacquiring assets. It adds no current-main build, audio-listening, long-session stability or complete gameplay qualification.

The reviewed report and recovery evidence retain the original execution unchanged. Independently inspected actual gameplay/before.png, movement-fire.png and after.png: the blue human plane moves from approximately (440,580) to (380,505), changes heading, then appears near (315,589). The middle frame shows a stream of discrete black bullets above the plane during held fire. Clouds, balloons, the red plane, smoke and cannonballs also move; whole-image pixel differences alone are insufficient. The Console obscures the upper 336 pixels. The last plane position is near the ground; continued survival is untested.

The raw ordinary-input trace binds these frames to batches 3000, 3600 and 4400. Comma188 acceleration starts at2100, Left37 at3100 and period190 fire at3200. Each input is followed by the corresponding WM_KEYDOWN routed to focus 0x10001; matching WM_KEYUP deliveries occur at3800,3900,4000. Enter13 also has matched down/up at1600/1610. Thus the baseline already accelerates: this supports subsequent movement/turning and held firing, rather than an idle-versus-acceleration experiment. The screenshot byte lengths match the raw capture log and independent SHA-256 checks.

Independently checked all136 artifact seals and ran the retained validate.py and recover.py --verify-local: PASS, all261 inputs /17,345,286 bytes verified against their actual standing files or exact historical Git blobs. Checked the139-file producer change is restricted to this report/evidence directory. Tested identities remain source b41a7c5f4b752d1f0bdab1141a11d4fed4dc6f9a, runner SHA-256 4d7b9587676db38fcf3314807acb2b2a42b5f09d2c98fcf3dccb8a6cde9e1809, full module 8fac39936b6df2418ad86cab118cef19a65a727f649fbc14c412b37818904686, original EXE 0e6f5450109c4c83e97bcf263bc90dc2d64dd83587356dd8a87994cc4246b474. The report checkout revision is distinct from the tested emulator revision.

The preload observes native instantiation without supplying stubs or changing inputs. Its actual successful-instantiation receipt records291 required imports, no missing imports, layout 9a3bc9149d58209c and512MiB shared memory before guest execution. The raw log records all eight DLL initializations,4500 batches and no observed guest trap. Supervisor PID/PGID28336 exited0 in8.192s with no remaining group members. The exercised watchdog control sent TERM, then KILL after5s, returned-9 and reaped the group. A broad post-run substring query matched its own inspector; the later exact-runner-argv receipt records an empty result. This is process cleanup evidence, not a sandbox/security attestation or proof of guest-directed exit: the successful run ended at its batch ceiling.

Reviewed producer resource scope:60,336,902/67,108,864 projected bytes includes8MiB reserve,8MiB session/events and8MiB SQLite growth/future allowance. Completed session3,683,816 bytes plus launcher events385,500 bytes fit the session allowance; measured remote task20,062,591 bytes, local task7,844,474 bytes and both host-free margins fit the retained projection. Initial oversized captures and two corrected pre-guest missing-path failures remain disclosed. Acceptance does not retrospectively assert a universal output guard or erase earlier attempts. Recovery retains identities and recipes rather than redistributing EXE/DLL/wasm/font/archive payloads.

Integration starts from actual remote main e29c89251e917bb15d549c9eb921d32e6f7aa4c1, reconciled again under scratch/usage-watch/shared-integration.lock before publication. Only the reviewed139 producer report/recovery files and this independent note are included. Raw historical receipts, including their whitespace, remain byte-exact. Applicable checks are evidence seals, local recovery hashes, input/PNG/identity/cleanup assertions, authored-note whitespace, merge scope and strict-SSH remote-ref verification; no emulator build is indicated by this documentation change.

Independent admission/evidence/publication receipts are retained under /tmp/airstrike-gameplay-independent-integrate-oct24/, including admission.json, independent-review.json, publication.json and resource-final.json. This worker has no assigned box and performed no box operation. The producer's running-box statement describes its original handoff; the coordinator's subsequent2026-10-24T02:37 messageboard entry records bx_754uted8 stopped with a verified snapshot (original expiry02:47:54.626Z). Shutdown remains coordinator-owned. Root tracked files/index/refs and all donors remain read-only.