Accept gate 32 evidence and correct F8 package verification (#259)

* Fix F8 verification for alpha.19 package identity

* Reconcile owner-approved physical gate 32 completion

* Normalize status document line endings

Author: iteathen

STATUS.md

@@ -2,7 +2,7 @@
 
 **Status:** Active operational state
 
-**Updated:** 2026-09-07
+**Updated:** 2026-09-09
 
 ## Current package and support truth
 
@@ -15,7 +15,7 @@ native Linux x86-64:         testing-unconfirmed / not-qualified
 production support:          no
 performance claims:          none beyond exact recorded evidence
 current generic source gap:  #251 lower Device-JS inspection stud implemented; protected integration pending
-current physical gate:       #32 exact CUDA-MCGS/CUDA-JS compatible-pair qualification
+physical pair #32:          passed, reviewed and owner-approved; exact Windows profile only
 ```
 
 `package.json` owns package identity. `packaging/compatibility-manifest.json` owns the public capability projection. The exact protected branch/commit/tree identity is read from GitHub when exact identity matters; this file does not own a self-updating live SHA.
@@ -48,13 +48,11 @@ CUDA-JS owns only its **producer facts**: what public capability exists, its exa
 
 Therefore CUDA-JS does **not** sequence CUDA-MCGS #124 behind UCI-Arena-Vector numerical qualification. Vector's independent checkpoint oracle remains Vector-owned product evidence. CUDA-MCGS independently owns the readiness and work ordering of its product-neutral evaluator/runtime composition. If either consumer demonstrates a genuinely consumer-neutral CUDA-JS defect, that defect routes back here without moving consumer policy into CUDA-JS.
 
-## Current CUDA-JS steady-state focus — #32 physical compatible pair
+## Accepted physical compatible pair — #32
 
-Outside the bounded #251 producer correction, CUDA-JS #32 remains the steady CUDA-JS-owned execution seam. The runner is ready and portable-qualified, but exact physical qualification is blocked on an accepted directly exposed NVIDIA environment. Hosted, VM, mock, package, Tensor or downstream product evidence cannot substitute for that physical evidence.
+The exact protected pair passed on Windows x64 / GTX 1660 Ti / driver 610.74 / CUDA 13.3 / Node 26.7.0. The [published review and evidence](https://github.com/iteathen/CUDA-MCGS/blob/main/docs/evidence/gate-32-2026-09-09/README.md) record all source/tree/package/API identities, one 4 × 256 launch, 4096 terminal bytes, Channel release/acquire publication and graceful cleanup. The project owner approved the review and gate completion.
 
-Immediately before a hardware run, read the live protected CUDA-JS and CUDA-MCGS heads/trees plus package/API/toolchain/environment identities and freeze only the tuple actually executed. A failure that demonstrates a generic lower defect belongs here; absence of hardware does not.
-
-CUDA-JS #4 native Ubuntu qualification remains a separate physical support cell. CUDA-JS #68 remains external operational security evidence.
+This qualifies only the recorded pair. The later F8 verifier correction updates its stale alpha.18 expectation to alpha.19; its full Windows hardware run is separate from the protected pair evidence. Future materially changed pairs require fresh qualification. CUDA-JS #4 native Ubuntu qualification and #68 operational security evidence remain separate.
 
 ## Claim limits
 

conformance/f8/verify.mjs

@@ -9,7 +9,7 @@ import { evidenceRoot, nativePackageEvidenceName, nativeProfile } from './eviden
 
 assert.equal(packageJson.name, compatibility.package.name);
 assert.equal(packageJson.version, compatibility.package.version);
-assert.equal(packageJson.version, '0.1.0-alpha.18');
+assert.equal(packageJson.version, '0.1.0-alpha.19');
 assert.equal(packageJson.dependencies.acorn, '8.15.0');
 assert.equal(packageJson.engines.node, '>=26.1.0');
 assert.equal(packageJson.private, false);

next_step.yaml

@@ -1,8 +1,8 @@
 {
   "schema_version": 72,
-  "updated": "2026-09-07",
-  "status": "device_js_inspection_candidate_physical_pair_blocked",
-  "objective": "Preserve CUDA-JS as the consumer-neutral CUDA runtime/toolchain and Device-JS language owner, expose the lower-owned pure Device-JS inspection stud demonstrated necessary by CUDA-MCGS #124, and retain the separate exact physical CUDA-MCGS/CUDA-JS qualification gap until suitable hardware exists.",
+  "updated": "2026-09-09",
+  "status": "physical_pair_passed_reviewed_owner_approved",
+  "objective": "Preserve consumer-neutral CUDA-JS mechanisms and the accepted exact physical pair; qualify future changed profiles separately.",
   "package_candidate": "cuda-js@0.1.0-alpha.19",
   "public_api_schema": 1,
   "live_state_policy": {
@@ -19,7 +19,11 @@
     "meaning": "Protected design-governance provenance, not a self-updating current-main field. Exact live protected branch/commit/tree identity is always read from GitHub before qualification or cross-repository freezing."
   },
   "durable_architecture_provenance": {
-    "foundation": ["CJS-F0", "CJS-F1A", "ADR-0002-node-ffi-first-host-binding.md"],
+    "foundation": [
+      "CJS-F0",
+      "CJS-F1A",
+      "ADR-0002-node-ffi-first-host-binding.md"
+    ],
     "external_nn_ownership": "CJS-CUDA-NN-EXTERNAL",
     "meaning": "Durable architecture/evidence routing markers retained for governance validation only; not a live package, support or downstream-readiness dashboard."
   },
@@ -33,9 +37,10 @@
     "repository": "iteathen/CUDA-JS",
     "issue": 32,
     "name": "exact physical CUDA-MCGS/CUDA-JS compatible-pair qualification",
-    "state": "runner-ready and portable-qualified; blocked only on an accepted directly exposed physical NVIDIA environment; bounded #251 producer correction is independently qualifying",
-    "next_action": "Protect the independently qualified #251 pure Device-JS inspection correction, then return to the existing physical-pair wait state. When accepted physical hardware is available, freeze the exact live CUDA-JS/CUDA-MCGS revisions and environment and run the existing physical compatible-pair qualification.",
-    "exit": "Issue #32 receives reviewed exact-profile physical evidence or the physical runner demonstrates another concrete consumer-neutral CUDA-JS defect."
+    "state": "passed-reviewed-owner-approved",
+    "next_action": "Publish accepted evidence and reconcile #32 closure; retain separate #4 native Ubuntu and #68 operational evidence gates.",
+    "exit": "Exact-profile physical evidence passed review and received project-owner approval.",
+    "evidence": "https://github.com/iteathen/CUDA-MCGS/blob/main/docs/evidence/gate-32-2026-09-09/README.md"
   },
   "producer_boundary": {
     "owns": [