Packaged Windows server acceptance, 865483b
Owner: Codex-ytr83r /root/windows_release_gap_review. Root owns release and native Studio acceptance. This directory is the only write scope; no compiler, tracked edits, UI, WSL, Linux, global environment, or root GUI/profile operations were performed.
Target: extracted ArcadiaStudio-0.2.0-preview.lifecycle-childwork.20260911-x86_64-pc-windows-gnullvm. Server SHA256 ABA87A5FB795DEB995029A737C2EBB9D2B44C8D274EDAA2295363B226D9AF6BE; adjacent libunwind.dll AA282FA47BB2C4E210CEA5E470CDBDCA58568F0BE0BC73E404D86AB9CD95EF6A. preflight.json and postflight.json record exact package/input hashes before and after execution.
run.py adapts the existing REST coverage and semantic HTTP schema runners only for isolated launch, output retention and instrumentation. All contract assertions remain. coverage-probe.json is an unchanged copy of the current source7 fixture, previously accepted with this immutable server at321897f. The scripts use explicit bundled Python and PowerShell executable paths. Python adds .local/python-deps through sys.path; it does not add it to the server PATH. Every server runs from the empty private unrelated-cwd directory and a private data store. No default user store is opened.
The first REST run (rest) passed its 25 assertions, but its launch readback exposed PowerShell startup prepending PSHOME to PATH. Preserve those receipts as a harness correction, not strict PATH acceptance. retry-rest.py reuses the same assertions with an explicit process-local PATH reset immediately before every server start. rest-strict is the authoritative restricted-PATH REST run. The schema run used the exact restricted PATH on its first launch.
Acceptance requires successful runner-status.json, readback.json, process-readback.json and unchanged hashes. readback.py independently compares seven complete raw HTTP response pairs (candidate no-commit, invalid-write preservation, repaired model/source/validation across restart), checks ETags, and verifies saved bundle files against the exact fixture. The readback source directories retain UTF-8 source text from the actual matching HTTP bundles. evidence-sha256.json inventories the closed evidence files.
The REST fixture retains an unrelated sequence_gap warning after its five allocation/coverage warnings are repaired; this was also present in the accepted prior coverage probe and is not a zero-warning assertion. Actual schema validation compares the served OpenAPI document to the unchanged local contract, validates204 schemas and19 actual/typed values, and rejects9 invalid shapes. schema-http.json retains all actual HTTP exchanges from that runner. The schema negative-shape cases are validator checks against served/local schemas, not nine separate invalid HTTP mutations.
Server stop records include nonzero codes from intentional probe termination (PowerShell Stop-Process or Python terminate). Runner success codes and explicit stopped-process/readback checks distinguish planned cleanup from an unexpected startup/runtime exit. These tests establish this packaged server's launch and scoped REST/schema/persistence behavior on this Windows host. They do not establish GUI acceptance, graceful shutdown handling, remote deployment, or Linux runtime behavior.