Maintain and validate OpenShell's native Windows MSVC and MXC runtime lane for x64 and ARM64. Use when working on Windows compilation, `windows:*` mise tasks, the MXC supervisor/sandbox pairing, unsupported Windows compute-driver contracts, or Windows build reports. This skill does not implement Docker, Kubernetes, Podman, VM, MSI, or service support on Windows.
79%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/build-openshell-mxc-windows/SKILL.mdThis skill maintains the existing native Windows MSVC build lane in the
OpenShell repository's windows branch.
That branch owns native Windows implementation and releases. Shared docs may
also appear on main; always direct Windows work to windows and use explicit
Windows branch links for implementation details. See
Native Windows support.
Before running the tasks below, use a windows-based checkout and read the
skill from that branch.
The task and runtime descriptions refer to that checkout, not to any older
Windows source snapshot retained on main.
The lane validates that OpenShell can compile and test on Windows MSVC for the supported deliverables:
openshell-gateway.exeopenshell.exeopenshell-supervisor.exe (host RFC 0012 isolation backend)openshell-windows-sandbox.exe (MXC ProcessContainer boundary)It intentionally does not make Windows a Docker, Kubernetes, Podman, or VM runtime host.
The supervisor and supervisor-process libraries participate in native Windows checks and tests. Their gateway session, boundary attachment, and TCP readiness are portable; only the optional Unix SSH/readiness socket adapters are gated. This is compile and control-plane coverage, not Windows isolation qualification. Preserve readiness gating on authenticated gateway acceptance and reconnection. The supervisor process-access multiplexer consumes boundary-provided streams; do not restore local PID, PTY, or process-group operations there. Native process mechanics belong to the sandbox or isolation backend. Keep the optional Unix SSH access adapter separate from portable session orchestration. Shared Sandbox Protocol audit validation defaults to strict Linux evidence; concrete platform validators must be selected by the implementing backend.
MXC control connects outward from the boundary to a generation-scoped host loopback listener, matching the Windows relay's connection direction. Keep the reverse connector in the MXC isolation backend and share it across policy discovery and attachment. Shared transport hooks must retain pinned TLS peer verification and supervisor JWT authentication; do not change host firewall rules to repair host-to-AppContainer control connectivity.
The dedicated Windows sandbox binary links the Windows-only openshell-mxc-boundary
library for process operations, containment confirmation, and loopback
forwarding. The generic sandbox does not link this library and remains a Linux
runtime. Do not reintroduce a dedicated supervisor-relay executable or link
the compute driver into the sandbox. The supervisor remains a separate host
process. Include boundary-library regression tests in native workspace tests;
their real process/socket checks are not qualification of MXC enforcement.
Keep MXC audit schemas and their validators in the Windows boundary library.
Register its MxcRuntimeBackend under openshell-mxc at supervisor composition.
Use the private BackendSetup / PreparedBackend extension for launch decoding,
policy discovery, and client construction. Shared startup must not decode the
MXC descriptor or allocate its connector. Retain the same reverse-TCP connector
in prepared launch state through discovery, attachment, and reconnects.
It reuses the shared authenticated Sandbox Protocol, whose default Linux
backend remains separate. Shared protocol code
must not interpret MXC evidence.
Keep proxy provisioning in MXC-owned host-launch and one-use bootstrap
envelopes. Private Windows backend setup supplies concrete listener options to
shared supervisor networking. Do not add proxy hooks to BoundBoundary, proxy
fields to shared Sandbox Protocol descriptors, or placeholders to other drivers.
Proxy startup remains after authenticated attachment and boundary confirmation.
Do not reintroduce driver-owned proxy startup or gateway create-time credential snapshots. Gateway JSONL audit output is portable and an explicit operator opt-in, independent of the selected driver. Keep platform directory conventions in shared path utilities and ETW capture in the MXC driver. Gateway composition supplies generic connection inputs; the driver resolves its endpoint defaults and TLS server name. Supervisor gateway sessions and main attachment must work without SSH on any host. Gate only the Unix socket adapter, not TCP readiness or authenticated session retries.
Adopt the shared protocol's authenticated policy discovery and monotonic provider-publication generations. Do not order opaque credential revisions numerically. MXC rejects unsupported provider file delivery before launch or environment replacement; it must not acknowledge files it did not install.
Preserve main's shared outer-fence evidence contract. At the user's explicit request, MXC temporarily asserts the required guarantees for Windows-branch parity testing. These MXC-only assertions are stubs, not verified enforcement: broad host loopback and unverified live revocation remain known gaps. Keep the TODOs and unverified audit mechanism visible; never report passing E2E as proof that these gaps are closed. A supported PSEC host alone does not close them.
The Windows build lane is implemented by these tracked files:
| Path | Purpose |
|---|---|
tasks/windows.toml | Mise task entry points for windows:* commands. |
tasks/rust.toml, tasks/test.toml, and tasks/markdown.toml | Windows routing for compiler-bearing checks, explicit Unix-only test skips, and Markdown dependency setup. |
tasks/scripts/windows-msvc.ps1 | PowerShell wrapper that enters the Visual Studio developer environment and invokes Cargo. |
.github/workflows/windows-msvc.yml | Opt-in PR lint and test plus advisory windows branch cache seeding and dependent binary builds on native x64 and ARM64 runners. |
.agents/skills/build-openshell-mxc-windows/ | This skill and companion reference material. |
Use the code that is already in the repo. Do not generate a parallel Windows build system, duplicate the wrapper, or add repository automation that the user did not request.
In scope:
windows.tasks/windows.toml and tasks/scripts/windows-msvc.ps1.openshell-gateway, openshell,
openshell-supervisor, and openshell-windows-sandbox.Out of scope:
#[cfg(target_os = "windows")].#[cfg(unix)] or
#[cfg(target_os = "linux")].mise run ci path unless the user explicitly
asks for it.mise run --skip-tools windows:* for Windows validation. The Windows
toolchain is rustup plus Visual Studio Build Tools, not mise-provisioned Rust.run command when the underlying tool supports it
(for example, npm --prefix). Add run_windows only when the Windows shell
or validation contract genuinely differs.From a fork checkout where upstream points to the official
NVIDIA/OpenShell GitHub repository, use:
git fetch upstream windows
git switch windows
git merge --ff-only upstream/windows
git branch --set-upstream-to=upstream/windows windows
git status --short --branchFor a direct checkout of the official repository, use origin instead of
upstream. Confirm the remote URLs with git remote -v before refreshing.
If there are local changes, preserve or resolve them before refreshing. Do not discard user work unless the user explicitly asks to clean the checkout.
The lane targets a Windows host with Visual Studio Build Tools and rustup.
| Requirement | Check | Notes |
|---|---|---|
| Windows 11 | [System.Environment]::OSVersion.Version | Build 26100+ is recommended for MXC-adjacent validation, but compilation can still surface useful errors on older hosts. |
| Visual Studio 2022 or newer | where.exe cl.exe from a Developer PowerShell | Build Tools, Community, Professional, and Enterprise editions work when the target C++ components are installed. The wrapper discovers VsDevCmd.bat through OPENSHELL_VSDEVCMD, vswhere, or installed release directories such as 18 and 2022. |
| Visual C++ ARM64 tools | vswhere -latest -products * -requires Microsoft.VisualStudio.Component.VC.Tools.ARM64 -property installationPath | Required for native ARM64 check, build, and tests and for x64-to-ARM64 check/build. Tests always require a native runner. |
| Visual C++ ARM64 Spectre-mitigated libraries | vswhere -latest -products * -requires Microsoft.VisualStudio.Component.VC.Runtimes.ARM64.Spectre -property installationPath | Required by regorus through msvc_spectre_libs; the build fails when the selected MSVC toolset lacks lib\spectre\arm64. |
| Visual C++ Clang tools | vswhere -latest -products * -requires Microsoft.VisualStudio.Component.VC.Llvm.Clang -property installationPath | Provides host-native libclang.dll for bindgen and clang-cl.exe for ARM64 crypto dependencies such as aws-lc-sys. On ARM64, the wrapper uses VC\Tools\Llvm\Arm64\bin. |
| Visual C++ CMake tools | vswhere -latest -products * -requires Microsoft.VisualStudio.Component.VC.CMake.Project -property installationPath | Provides CMake and Ninja for native dependencies. The x64-to-ARM64 path adds Ninja to PATH; Z3 uses an architecture-specific prebuilt release. |
| Windows SDK | where.exe rc.exe from a Developer PowerShell | Install an SDK containing target libraries and ARM64 tools. |
| Rust via rustup | rustc --version | Add each target being validated: x86_64-pc-windows-msvc and/or aarch64-pc-windows-msvc. The wrapper also adds the selected target. |
| mise | mise --version | Used as a task runner only. |
| Git | git --version | Needed for checkout and sync work. |
| PowerShell | $PSVersionTable.PSVersion | Windows PowerShell 5.1 works; PowerShell 7 is quieter with mise shell hooks. |
Do not install Visual Studio, Rust, Docker, Kubernetes, Podman, WSL, or Hyper-V from this skill.
| Variable | Default | Purpose |
|---|---|---|
OPENSHELL_VSDEVCMD | unset | Optional explicit path to VsDevCmd.bat. |
OPENSHELL_MXC_SKIP_ARM64 | 0 | Set to 1 to skip ARM64 when using all tasks. |
OPENSHELL_WINDOWS_BUILD_JOBS | CARGO_BUILD_JOBS, then 4 | Positive Cargo job limit used by the wrapper. |
CARGO_TARGET_DIR | target under repo root | Override Cargo output location. Use a short absolute path when x64-to-ARM64 builds approach Windows path-length limits. |
Z3_LIBRARY_PATH_OVERRIDE | unset | Directory containing an x64 system libz3.lib; not valid for ARM64. |
Z3_SYS_Z3_HEADER | unset | Full z3.h path required with a system Z3 library. |
Z3_SYS_Z3_VERSION | 5.1.0 | Pinned official prebuilt Z3 release selected by the wrapper. |
READ_ONLY_GITHUB_TOKEN | unset | Optional token for the Z3 release lookup; GitHub Actions supplies github.token. |
RUSTC_WRAPPER | inherited | The wrapper resolves an available command to an absolute path. If it is unavailable, the wrapper warns and continues without compiler caching. |
Legacy fork variables such as OPENSHELL_UPSTREAM,
OPENSHELL_MXC_FORK_DIR, and OPENSHELL_MXC_FORK_BRANCH are no longer part
of the normal maintenance workflow. Use them only if the user explicitly asks
for a new disposable fork.
Run the smallest useful slice first, then broaden:
mise run --skip-tools windows:check:x64
mise run --skip-tools windows:check:arm64
mise run --skip-tools windows:build:x64
mise run --skip-tools windows:build:arm64
mise run --skip-tools windows:test:x64
mise run --skip-tools windows:test:unsupported:x64The two windows:test:mxc-real:* tasks are host-specific and mutually
exclusive on a single host (each rejects the other architecture -- see the
table below): run windows:test:mxc-real:x64 on an x64 host, or
windows:test:mxc-real:arm64 on an ARM64 host, as part of validating this
subsystem -- run the one matching your host architecture, not both, and not
neither. Both are skip-safe (they print a SKIP reason and exit 0 when
wxc-exec or the matching backend isn't available), so running the
arch-appropriate task is always safe even without real MXC hardware. Neither
is part of windows:ci's ordered contract, so invoke it explicitly.
For full validation, detect the Windows host architecture first and choose the native lane dynamically:
$arch = [System.Runtime.InteropServices.RuntimeInformation]::OSArchitecture
switch ($arch.ToString()) {
"X64" {
mise run --skip-tools windows:ci
if ($LASTEXITCODE -ne 0) { throw "windows:ci failed." }
mise run --skip-tools windows:test:mxc-real:x64
if ($LASTEXITCODE -ne 0) { throw "windows:test:mxc-real:x64 failed." }
mise run --skip-tools windows:e2e:mxc
if ($LASTEXITCODE -ne 0) { throw "MXC E2E validation failed or was incomplete." }
}
"Arm64" {
mise run --skip-tools windows:check:arm64
if ($LASTEXITCODE -ne 0) { throw "windows:check:arm64 failed." }
mise run --skip-tools windows:build:arm64
if ($LASTEXITCODE -ne 0) { throw "windows:build:arm64 failed." }
mise run --skip-tools windows:test:arm64
if ($LASTEXITCODE -ne 0) { throw "windows:test:arm64 failed." }
mise run --skip-tools windows:test:unsupported:arm64
if ($LASTEXITCODE -ne 0) { throw "windows:test:unsupported:arm64 failed." }
mise run --skip-tools windows:test:mxc-real:arm64
if ($LASTEXITCODE -ne 0) { throw "windows:test:mxc-real:arm64 failed." }
mise run --skip-tools windows:artifacts
if ($LASTEXITCODE -ne 0) { throw "windows:artifacts failed." }
mise run --skip-tools windows:e2e:mxc
if ($LASTEXITCODE -ne 0) { throw "MXC E2E validation failed or was incomplete." }
}
default {
throw "Unsupported Windows host architecture for OpenShell MSVC validation: $arch"
}
}Full validation requires an MXC-capable host. E2E exits nonzero when any required runtime scenario fails or skips.
On x64 hosts, windows:ci is the full current CI contract and runs in this
order:
OPENSHELL_MXC_SKIP_ARM64=1.The GitHub Actions jobs layer architecture-specific Swatinem/rust-cache
entries for Cargo registry and dependency target artifacts with sccache's GHA
backend for cacheable Rust compiler outputs. Failed runs also save their usable
dependency artifacts. Pull-request mirrors labeled test:windows run Clippy for the
Windows-supported workspace and e2e crates plus Rust tests. Pushes to windows and
manual dispatches on that branch run the same lint and test commands in a cache-seed job,
followed by a dependent release-binary build job. The seed and PR jobs use the
same cache namespaces, but pull-request mirrors cannot restore the
windows branch cache because GitHub scopes caches by branch. Merge queues do
not run this workflow. Release-branch seed
and build jobs use job-level continue-on-error: true; opt-in PR jobs report
failures normally. Applying the label alone does not start a run: re-run all
jobs in the current mirror push run, or push a new mirrored commit. The binaries are not uploaded or published.
The ARM64 check/build steps in this x64-host contract are cross-builds. The
wrapper discovers and adds host-native LLVM and Ninja to PATH, requires the
ARM64 compiler and Spectre-mitigated libraries, lets ARM64 crypto crates select
clang-cl, and downloads the official prebuilt ARM64 Z3 package.
On ARM64 hosts, validate the native ARM64 check, build, and test path. The
wrapper rejects test targets that do not match the host architecture, so x64
compatibility under emulation is not part of these tasks. The aggregate
windows:ci task remains the x64-host CI contract; run the explicit ARM64
commands above on an ARM64 host.
The repository-wide mise run pre-commit task is also supported on Windows.
Run rust:lockfiles:check and sdk:ts:ci through the Windows-aware tasks
when validating those surfaces. Do not count POSIX permission-bit skips as
security coverage. SDK test dependencies must remain at their lockfile versions.
Its Rust check, Clippy, and test dependencies enter the same MSVC environment
for the native host target and use an inherited compiler wrapper when it is
available. Linux glibc
installer tests and Linux service/RPM packaging-asset tests skip explicitly;
the Linux build-environment shell-helper test also skips; cross-platform checks
continue to run. The blocking Windows Clippy pass excludes unsupported
Windows runtime packages as top-level targets. It allows only unused imports,
dead code, and unused async functions that result from cfg-gated Windows stubs;
other warnings remain errors.
The wrapper limits Cargo to four jobs by default and serializes wrapper-owned
Cargo commands with a host-local mutex. It deliberately does not set CL or
_CL_: those variables are also consumed by clang-cl, where a global MSVC
option such as /MP4 can be interpreted as an input file and break ARM64
crypto dependency builds.
| Task | Expected behavior |
|---|---|
windows:check:x64 | cargo check --workspace for x86_64-pc-windows-msvc, excluding unsupported Windows packages as top-level workspace targets. |
windows:check:arm64 | cargo check --workspace for aarch64-pc-windows-msvc, with the same top-level exclusions. |
windows:build:x64 | Release-builds openshell-gateway.exe, openshell.exe, openshell-supervisor.exe, and openshell-windows-sandbox.exe for x64. |
windows:build:arm64 | Release-builds the same four binaries for ARM64. |
windows:test:x64 | Runs native x64 workspace tests with --no-fail-fast, excluding unsupported Windows packages as top-level workspace targets. |
windows:test:arm64 | Runs native ARM64 workspace tests with --no-fail-fast and the same package exclusions. Rejects non-ARM64 hosts. |
windows:test:unsupported:x64 | Re-runs focused openshell-gateway tests for unsupported Windows driver behavior. |
windows:test:unsupported:arm64 | Re-runs the same focused contracts natively on ARM64. Rejects non-ARM64 hosts. |
windows:test:mxc-real:x64 | Runs the serial, ignored real-wxc-exec integration suite natively on x64 through the MSVC wrapper. Rejects non-x64 hosts. |
windows:test:mxc-real:arm64 | Runs the same real-wxc-exec suite natively on ARM64. Rejects non-ARM64 hosts. |
windows:artifacts | Reports size and SHA256 for release artifacts that exist. |
windows:ci | Runs the full ordered x64-host Windows CI lane, plus ARM64 check/build when not skipped. |
The unsupported driver package excludes are intentional. They prevent standalone driver crates from being top-level Windows check/test targets while allowing required libraries and Windows contracts to compile through gateway dependencies. This includes the Kubernetes Secrets and Vault packages: their libraries remain in the gateway build graph, but their Unix-socket standalone binaries do not.
MXC requests and mapper artifacts use the stable 1.0.0 schema. Upgrade the
native host executor to the signed MXC 1.0.0 release before running E2E; preserve
the old executable for rollback and verify the release checksum, architecture,
signature, and --probe output. Remove default_configuration_id from gateway
configurations: it is retired and rejected. Do not restore alpha-version or
wildcard compatibility knobs. Standalone network mapping emits numeric CIDRs
and TCP ports and reports unrepresentable DNS/L7 semantics as losses; full
network governance remains in the host supervisor. IsolationSession remains
unsupported by this runtime pair, and its filesystem grants are not enforceable.
MXC does not support external-resource label admission. Its factory explicitly
acknowledges admission as disabled; do not add resource_admission to MXC TOML
or weaken admission defaults for other drivers. Caller driver JSON still
requires allow_driver_config = true. This does not waive native isolation,
workload policy, authenticated transport, or outer-fence confirmation.
UI controls remain in SandboxPolicy. Advertise openshell.policy.ui.v1 using
existing extension metadata, not a new per-driver boolean. The shared gateway
checks effective policy before driver validation and provisioning; drivers
without the capability reject explicit UI without implementing UI-specific
handling. Keep native UI validation and mapping in MXC. Omitted UI settings deny
graphical UI, clipboard access, and input injection. UI changes require
recreating the sandbox.
Windows must continue to reject unsupported compute drivers clearly.
The gateway's compute-driver-mxc feature independently links and registers
MXC on Windows. Each other compute-driver-* feature installs its own Windows
rejection stub without linking that driver crate. The default
in-tree-compute-drivers alias enables all five features. An MXC-only build
uses --no-default-features --features compute-driver-mxc (add telemetry
and openshell-server/prebuilt-z3 as needed).
| Driver | Windows build behavior | Runtime behavior |
|---|---|---|
| Docker | Driver crate excluded; gateway registration stub retained. | Gateway construction returns unsupported. |
| Kubernetes | Driver crate excluded; gateway registration stub retained. | Gateway construction returns unsupported. |
| Podman | Driver crate excluded; gateway registration stub retained. | Gateway construction returns unsupported. |
| VM | Driver crate excluded; gateway registration stub retained. | Gateway construction returns unsupported. |
The focused contract tasks for either native architecture run:
windows_builtin_compute_drivers_report_unsupported
default_registry_contains_exactly_the_enabled_compute_driversThe same tasks also run gateway library tests for protocol-only, MXC-only,
Docker-stub-only, and MXC plus Docker-stub builds. Their logs use
test-<target>-selective-<variant>.log.
The default-feature tests are also included in the full workspace test run. The focused task is available for local diagnosis and selective-build validation; GitHub Actions does not re-run it after the full suite.
For a separate qualified Windows test host, use
tasks/scripts/test-mxc-remote.ps1 -HostName <host> -UserName <user>.
It builds locally with the existing Windows tasks, detects native remote
architecture through Windows system configuration (not an emulated SSH shell),
caches uploads by SHA256, and runs the unchanged real E2E harness. Results and
host probes return to target/windows-remote-results, including nonzero test
outcomes. The remote host needs SSH, OpenSSL, and MXC, not a compiler toolchain.
Package the matching libz3.dll from the target-specific Cargo cache alongside
the gateway: Windows prebuilt Z3 uses an import library, not static linkage.
The windows:build:* tasks now stage the pinned DLL, check PE architecture,
reject conflicting cache hashes, and verify the copied hash. Local MXC E2E
requires the adjacent DLL and reports a preflight error if it is missing.
Use -Z3DllPath when discovery is ambiguous. The native Visual C++ runtime
must be present on the remote host. Verify DLL architecture and the gateway
loader before E2E; do not count missing-DLL crashes as MXC enforcement failures.
Verify the SSH host key beforehand. Never send the private SSH key or bundle
the harness signing-key directories. -SkipBuild is an explicit stale-artifact
opt-in, not evidence that artifacts match current sources. See the MXC driver
README for the command and remote dependency contract.
For MXC validation, also run windows:e2e:mxc
after the native release build. The harness uses .NET port discovery, disposable
TOML and CLI registration, and owner-only Ed25519 keys generated by OpenSSL on
PATH. Results live under target/windows-e2e-results; signing keys stay outside
bundles and are deleted unless -KeepRunning is explicitly requested.
E2E has no mock mode and rejects OPENSHELL_MXC_MOCK_WXC=1. Unit-test mocks
are not E2E coverage. Every selected scenario must pass for a successful exit;
any skip reports INCOMPLETE and exits non-zero. Do not broaden the temporary
MXC network-assertion waiver to other audit or authentication checks. Real
runtime scenarios require native ProcessContainer PSEC egress
filtering and ingress host-loopback support. wxc-exec --probe is authoritative,
not the Windows build number. All-skipped real runs are not passes. Separate
test-internal SKIP messages from Cargo's passed count in the real integration
suite, and report a verified unsupported-host rejection independently from
positive admission coverage.
The real forwarding E2E scenario uses a native test-only echo agent inside MXC and
openshell forward service to verify two exact request/reply exchanges through
the gateway, supervisor, and boundary. Dynamic ports and a per-workload nonce
avoid mistaking unrelated listeners for success. This is managed-ingress
coverage, not evidence that direct host ingress is fenced. Use
-Scenario forwarding on the existing local or remote runner for focused checks.
The E2E mise task and remote runner build the mxc-forwarding-agent Cargo example
using windows:build:mxc-fixtures (or its :x64 / :arm64 variant). This fixture
is not one of the four production deliverables; do not package it in releases.
The service-forwarding scenario uses its HTTP mode to test named endpoint
exposure, two exact GET responses through gateway routing, and HTTP 404 after
endpoint deletion. This is distinct from openshell forward service; neither
scenario tests file upload or exclusive ingress enforcement.
The real integration HTTPS test runs the same authenticated gateway harness with
the opt-in https-ca scenario, not an unauthenticated standalone driver. Build
native release binaries first, or select them with OPENSHELL_MXC_TEST_BINARY_DIR.
It requires Internet access to example.com and Windows curl >= 8.3 to explicitly
expand the injected CA bundle into --cacert (Schannel ignores that environment
variable by default). Require both a nonempty response and the OpenShell proxy
CA issuer; never replace these assertions with an insecure TLS request. This
fixture permits unavailable CRL information using best-effort Schannel revocation
for the ephemeral private CA; this is not revocation qualification. This
scenario is not part of the default seven offline-capable E2E scenarios.
The default host-service scenario runs the HTTP fixture on host 127.0.0.1
and a dynamic port, then checks two nonce-bound replies from direct curl requests
inside MXC. Host-side readiness and request proofs stay outside the workload's
writable directory. The service is stopped even after failed runs. Use
-Scenario host-service for focused checks. No Internet access, LAN address, or
firewall modification is required. A failed host health check or workload
request fails the test. This verifies direct localhost connectivity; retain
the existing shared proxy SSRF controls.
When reporting windows:ci, distinguish these categories:
#[cfg(not(target_os = "windows"))]; these often appear as
running 0 tests, not as ignored tests.filtered out counts from focused cargo test invocations.Useful log files:
| Log | Meaning |
|---|---|
build-x86_64-pc-windows-msvc-check.log | x64 check output. |
build-aarch64-pc-windows-msvc-check.log | ARM64 check output. |
build-x86_64-pc-windows-msvc-release.log | x64 release build output. |
build-aarch64-pc-windows-msvc-release.log | ARM64 release build output. |
test-x86_64-pc-windows-msvc.log | Full native x64 workspace test output. |
test-aarch64-pc-windows-msvc.log | Full native ARM64 workspace test output. |
test-x86_64-pc-windows-msvc-unsupported-*.log | Focused unsupported-driver contract output. |
test-aarch64-pc-windows-msvc-unsupported-*.log | Focused native ARM64 contract output. |
test-x86_64-pc-windows-msvc-mxc-real.log | Native x64 real-MXC integration output. |
test-aarch64-pc-windows-msvc-mxc-real.log | Native ARM64 real-MXC integration output. |
The first check downloads the pinned official Z3 archive for the target
architecture through z3-sys. GitHub Actions authenticates the lookup with its
read-only workflow token; local users can set READ_ONLY_GITHUB_TOKEN if an
unauthenticated lookup is rate-limited. Cargo stores the extracted library in
its target tree, so the Windows target cache reuses it. The artifact report
computes SHA256 through .NET directly and does not rely on the Get-FileHash
module being available inside the mise-launched Windows PowerShell process.
Keep supervisor admission fixtures independent of host Linux filesystem paths. Inject deterministic baseline enrichment into startup tests and reuse the production merge routine. Preserve prover runtime-parity assertions when fixing solver timeouts. Mutation-lock stress tests retain their parallel workload and exclusion checks with a larger Windows timer budget.
When Windows validation fails:
#[cfg(unix)] or
#[cfg(target_os = "linux")].cargo fmt --all, git diff --check, and the relevant windows:*
tasks after changes.Do not add broad abstractions or new Windows runtime support to satisfy a build error. If a missing runtime feature is required, stop and propose a follow-on skill or design doc.
When syncing from the windows branch, consult the selective integration
checkpoint in crates/openshell-driver-mxc/WINDOWS-INTEGRATION.md. Preserve
the host-supervisor/Windows-boundary architecture rather than restoring legacy
relay/proxy demo wrappers. The WebSocket, OpenClaw, and inference policy fixtures
have parser/mapper tests; do not report them as live runtime scenarios.
Every substantial Windows build run should report:
| Item | Required detail |
|---|---|
| Git state | Branch, upstream GitHub base commit, and whether local changes existed. |
| Host preconditions | OS, Rust, MSVC discovery, and notable warnings. |
| Commands run | Exact mise run --skip-tools windows:* commands. |
| x64 check/build | Pass/fail and log path. |
| ARM64 check/build | Pass/fail/skipped and log path. |
| Native tests | Passed/failed/ignored/filtered counts and log path for the host architecture. |
| Unsupported contracts | Which focused tests ran and their result. |
| Artifacts | Binary paths, size, and SHA256 when available. |
| Skips | Explicitly explain tests not run for a non-native architecture, unsupported driver package exclusions, and Windows cfg-gated tests. |
| Follow-ups | Only concrete follow-ups tied to failures or requested scope. |
Use mise run --skip-tools windows:test:mxc-boundary for boundary unit tests and
real Windows kernel socket-owner lookup. windows:test:mxc-network requires the
native release build and Internet access; it runs the injected-CA HTTPS test and
the allow-child/deny-child socket-owner regression through the authenticated
harness. windows:test:mxc-loopback executes its test inside a real native MXC
container with host loopback denied, separately from ordinary unit coverage.
Do not enable broad host loopback to turn an unsupported-runtime failure green.
The MSVC wrapper selects native test architecture from the machine environment,
so an emulated SSH PowerShell does not incorrectly reject ARM64 qualification.
Keep Windows kernel calls in the boundary library and retain shared supervisor
unsafe-code bans, per-generation proxy authentication, and executable digests.
Use windows:test:mxc-audit to validate the shipped audit gateway config with
its real parser, test JSONL coverage classification, and run the live seven-event
ETW qualification. Build native release binaries first and set
OPENSHELL_WXC_EXEC_PATH. The runner requires elevation or Performance Log Users
membership and leaves a results bundle under the target directory. Ordinary MXC
E2E success does not establish ETW audit coverage. Coverage must use structured
JSONL and fail when an expected event is absent or has the wrong OCSF class.
NVIDIA/OpenShell
2e5589b
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.