Independent stage-zero DISABLE review — 2026-10-24

Verdict: PASS for the bounded software routing/combiner and legacy GPU lowering repair from producer a656ac9013f0c47f22d3c5691afe06ef67ae90dd, based on eb0c0a71c93c98bb2e394629e2c093bdcd4a9baf. Strict authenticated SSH verified both actual remote refs before review. No other game or subsystem qualification is implied.

Microsoft's operation contract and blending contract require COLOROP=DISABLE to terminate the cascade, including alpha. Stage-zero output is incoming diffuse RGBA. ALPHAOP=DISABLE with enabled color remains undefined. The early software resolver exit avoids texture/color-key access without clearing the stored binding. The standalone combiner returns incoming RGBA before selecting operands. The JS guard independently prevents texture activation even with bound metadata. Existing enabled operations, modifier fallback and later-stage limitations remain; the capability mask is still 0xe.

Fresh independent execution reproduced exact-main failures: software a0485038 versus 8060a0e0 for COLOROP=1/ALPHAOP=2, and GPU one texture versus zero. Candidate passed eight bound/unbound × alpha configurations, direct real software span RGBA, both front-end diffuse routing checks, and three semantic rejecting reversions (resolver, combiner, independent GPU activation). Re-enabling on the same object restores the stored texture with independent diffuse alpha (80c08040). The nearby suite passed nine RGB/alpha pairs, 144 argument configurations, six remaining unsupported diagnostics and 15 rejecting controls. Batching, points and the byte-identical historical argument reproducer passed; its absolute donor paths were redirected with a retained preload, without changing assertions. The reproducer receipt's legacy loweredSelectionRGBA field is hardcoded historical text, not a measured candidate pixel.

The producer's nearby wrapper removed only the obsolete DISABLE-bug diagnostic at execution. Review replaced that mechanism with an explicit test update: remove operation 1 from the unsupported list/map, update the printed count, and run the nearby test directly. All enabled assertions and 15 controls remain. The new test retains its authentic fixture extraction and three semantic mutations. Generated machine-specific receipts were removed from the final source tree; all originals remain sealed locally and recoverable from the published producer revision.

Before compilation, independent --manifest-only bound the authentic compiler Git blobs/full-file SHA-256 and exact ordered source excerpt offsets/hashes. They matched the producer: assembled 104827 bytes, SHA-256 997006b0cb75e170a9d05a1501fe2c4b45e4076eb76fbb89d89425299b5ff225. All 31 producer local seals verified. Each test used installed Node v24.18.1 with --max-old-space-size=256, CPU/wall 60 seconds, one 64KiB fixture memory and MemAvailable admission. No packages or full build.

Scope limits: software untextured rasterization is a fixture double; actual textured triangle/raster/span output is checked separately. GPU submission is mocked lowering, not actual WebGL pixels. No native, COM, full VM, browser or gameplay acceptance; no assigned box (ID/state/expiry N/A), coordinator retains lifecycle ownership. Unsupported operations are not newly claimed or silently substituted by this repair.

Independent evidence: /tmp/legacy-texture-disable-independent-integrate-oct24/ contains resource-initial.json, compiler-preexecution.json, baseline/candidate logs, runs.jsonl, evidence-retention.json, final resource/publication/seal receipts and the recovery driver. Producer originals: /tmp/legacy-texture-disable-current-main-oct24/seal.json. Recover baseline files with git show eb0c0a71:src/09ab-handlers-d3dim-core.wat and git show eb0c0a71:lib/d3dim-gpu.js; run new test and direct nearby --negative-controls, batching and points with the limits above. Producer generated receipts can be recovered with git show a656ac90:docs/re-notes/legacy-texture-disable-20261024/FILE.

The private checkout uses explicit sparse paths and read-only donor alternates. Initial recursive Git alternate-depth failure was corrected by flattening only the existing declared read-only chain in the new checkout; no donor mutation or object copy. Initial oversized instruction/board display is retained and conservatively charged; capture history is never reset. Root tracked files/index/refs and other lanes remain untouched. Conditional integration must hold the shared flock through fresh remote-main reconciliation, focused final checks and normal fast-forward push with exact ref verification.