docs: record Windows CI handoff

Author: robertvokac

NEXT.md

@@ -30,10 +30,9 @@ distribution rather than missing editor breadth.
 
 ## Current priorities
 
-1. Publish and obtain native standalone Windows qualification
-   (`SYS-W11-06`). **Blocked / needs human:** the current worktree must be
-   published before the first remote `windows-2022` CTest/artifact evidence
-   can exist.
+1. Obtain native standalone Windows qualification (`SYS-W11-06`). Commit
+   `34bc0de` is published on `develop`; await the first remote
+   `windows-2022` CTest/artifact evidence.
 
 `SYS-W14-40` is complete: the explicit bounded Event Preview/Play mode is
 covered by `event_preview_runner`. See `plan.md` for the remaining Windows
@@ -112,20 +111,20 @@ relocatable CLI `.tar.gz` from the same install rules. The archive includes
 the two CLI tools, MC3/MCB headers and libraries, package configs, and the
 non-system runtime libraries used by the glTF exporter.
 
-`SYS-W11-06` is blocked / needs human. Its Windows CI job remains
-CNA-independent, builds and CTests all four standalone components, verifies a
-fixed MC3→MCB/GLB fixture before artifact upload, and publishes only the
-qualified Windows CLI executables. This session reconfigured the local MinGW
-14 tree with `BUILD_TESTING=ON`, confirmed its CTest registration uses the
-configured cross-test emulator, and compiled the affected standalone targets.
-The sandbox blocks Wine itself with `SIGSYS`, so it cannot provide runtime
-evidence. The native Linux `cli_cross_platform_fixture`, package-consumer,
-capability-documentation, and plan-consistency CTests passed. Freshly
-relinked XML, JSON, and MCB load-policy tests plus the embedded-GLB and SVG
-safety export tests also passed. The four path-confinement comparisons use
-`generic_string()` rather than Windows-wide `path::native()` strings. A
-maintainer must publish the current worktree and review the first GitHub
-`windows-2022` CTest/artifact run before this task may be marked done.
+`SYS-W11-06` is in progress. Its Windows CI job remains CNA-independent,
+builds and CTests all four standalone components, verifies a fixed
+MC3→MCB/GLB fixture before artifact upload, and publishes only the qualified
+Windows CLI executables. Commit `34bc0de` is pushed to `origin/develop`.
+This session reconfigured the local MinGW 14 tree with `BUILD_TESTING=ON`,
+confirmed its CTest registration uses the configured cross-test emulator, and
+compiled the affected standalone targets. The sandbox blocks Wine itself with
+`SIGSYS`, so it cannot provide runtime evidence. The native Linux
+`cli_cross_platform_fixture`, package-consumer, capability-documentation, and
+plan-consistency CTests passed. Freshly relinked XML, JSON, and MCB
+load-policy tests plus the embedded-GLB and SVG safety export tests also
+passed. The four path-confinement comparisons use `generic_string()` rather
+than Windows-wide `path::native()` strings. Await the first GitHub
+`windows-2022` CTest/artifact run before marking this task done.
 
 ## Practical commands
 
@@ -180,6 +179,6 @@ verified SHAs and must not be treated as a full-editor qualification. The
 normal compiler-cache location is read-only in this environment, and Wine is
 blocked by sandbox `SIGSYS`, so neither a fresh full suite nor native Windows
 runtime tests were completed here. That is not evidence of a source failure.
-The next session should start by publishing this worktree and reviewing the
-first `standalone-windows` GitHub Actions run; use its CTest/artifact result to
+The next session should start by reviewing the first `standalone-windows`
+GitHub Actions run for commit `34bc0de`; use its CTest/artifact result to
 complete or diagnose `SYS-W11-06`.

plan.md

@@ -58,10 +58,9 @@ architecture, distribution, or measurable performance work. `P3` is polish.
 The user authorized this queue on 2026-07-26. Work proceeds one task at a
 time; re-evaluate scope and blockers before starting each item.
 
-1. **SYS-W11-06** `P2` — standalone Windows qualification. **BLOCKED /
-   needs human:** the workflow and local cross-build evidence are ready, but
-   final acceptance requires a maintainer to publish the current changes and
-   obtain the first native `windows-2022` CI CTest/artifact run.
+1. **SYS-W11-06** `P2` — standalone Windows qualification. **In progress:**
+   commit `34bc0de` is published on `develop`; await the first native
+   `windows-2022` CI CTest/artifact run before accepting the release gate.
 
 ---
 
@@ -161,7 +160,7 @@ time; re-evaluate scope and blockers before starting each item.
   smoke plus MC3/MCB and CLI round trips; the installed glTF CLI resolves its
   bundled Manifold runtime through `$ORIGIN/../lib`.
 
-- **SYS-W11-06** `[BLOCKED]` `P2` — Qualify standalone MC3/MCB/tooling builds and
+- **SYS-W11-06** `[IN_PROGRESS]` `P2` — Qualify standalone MC3/MCB/tooling builds and
   tests on a current Windows runner, independent of CNA editor backend
   blockers. The new `windows-2022` CI job configures, builds, and CTests all
   four standalone components, verifies a fixed MC3→MCB/GLB SHA-256 fixture,
@@ -170,9 +169,9 @@ time; re-evaluate scope and blockers before starting each item.
   use the configured emulator. This also exposed and fixed all four
   narrow-string uses of `path::native()` in confinement checks;
   `generic_string()` now works on Windows-wide paths. The local sandbox blocks
-  Wine itself with `SIGSYS`, so it cannot supply runtime evidence. **Needs
-  human:** publish the current worktree and review the first GitHub Windows
-  CTest/artifact run before marking this task done.
+  Wine itself with `SIGSYS`, so it cannot supply runtime evidence. Commit
+  `34bc0de` is now pushed to `origin/develop`; await and review the first
+  GitHub Windows CTest/artifact run before marking this task done.
 
 - **SYS-W11-07** `[DEFERRED]` `P3` — Improve dependency reproducibility with
   immutable revisions or verified archives, third-party notice/SBOM, and an