MCM explicit reviewed MENU context
Run: 20261120-mcm-menu-reviewed-context-start-quarry.
tools/mcm-bound-input.cjs has an explicit reviewedMenuContext option with
capability mcm-menu-reviewed-context-v1, a mandatory synchronous full-image
sink, and optional cancellation/disk checkpoint. Its default capture/admit
path retains the existing 12 second source limit. GPS preparation remains the
genuine 62d4828c0 host/Worker path; it must complete before a MENU context
source is captured. No host, renderer, WAT, region or other game's code changes.
The new authority retains a private complete source PNG and RGBA buffer, checks the actual document/session, process, Worker/module inventory, endpoint, epoch, HWND object generation, memory, preparation object, viewport and screen geometry. Personal review binds that source to one exact MENU Start intent (left mouse, 100ms physical hold). Its limits are source 30 seconds, review 15 seconds, and each fresh capture 5 seconds. Those timestamps never renew.
Start obtains two genuinely new complete viewport captures, retaining each synchronously and rechecking owners. Both must equal the entire reviewed RGBA buffer byte for byte, including dimensions and orientation. The final capture, owner checks, sink and clock/cancellation checks finish before the exact DOWN is published. Fresh images are explicitly marked not personally reviewed. No tolerance, mask, repaint, source promotion, game input plan or fallback is provided. Source, review, fresh, final and available refused images go to exclusive, read-only files with fsync and SHA readback before any DOWN. Sink failure refuses input. Private handles are session scoped and single use; failure closes the context, and physical UP failure closes the chain.
The 7bca66241 whole-frame equivalence approach informed the private authority,
age fences, detached evidence and final publication fence. Its XGetImage root
capture interface is incompatible with this CDP-bound MCM viewport. Its manual
context variant also permits unequal frames, which this capability forbids.
Neither shared module was changed or imported as authority.
Focused tests exercise complete images, all identity components, exact intent, single pixel and final-capture pixel changes, clock boundaries and reversal, sink refusal, cancellation, forgery, replay and detached evidence. The native test uses an authored static MENU, actual Chrome screenshots, a recovered actual Worker module and trusted DOWN/UP. It compares the unchanged direct 12-second refusal against explicit-context acceptance of identical pixels, then tests native image/owner/clock/sink/cancel/replay/UP-retirement negatives. This fixture is transport evidence; it does not claim original gameplay or a new GPS producer qualification. The run records exact SHA reuse of the prior real GPS creation, CPU Flip/source-copy/publication and eight native controls.
The original driver reconstructs the frozen
f5ae 2,420,767-byte module and 311 media references in memory and pins the
three GPS overlay files to 62d4828c0. It never reopens the prior closed
endpoint. Current display, Escape and ordinary Quit require actual completed
source-copy/publication binding in that new scope. Final results and any
precise blocker are recorded in the run, with result.json written last.
Validation: 52 focused tests and 18 actual-browser controls pass. Complete source/review/fresh/final/refused PNG evidence was retained. The unchanged direct path refused at 12,524ms; the explicit path accepted the identical static MENU, with trusted physical DOWN/UP. The authored fixture's review assertions are test inputs; the agent separately inspected its retained image. It is not an original-game personal review or gameplay claim.
The original was not launched. A fresh shared owner report at 12:07:55Z
recorded actual /home free space 1,499,365,376 bytes, below 1,500,000,000.
This task observed that report and permanently closed runtime admission;
subsequent space recovery did not reopen it. Its own native samples remained
above the floor and its fixtures were already joined and removed. No original
endpoint requests, Start, quarry, Escape, current-display or ordinary Quit
credit is claimed. precise-blocker.json retains the exact owner report and
distinguishes it from this task's own later recovered disk sample.