Extracted canvas/repair package: bounded server acceptance
Fresh Windows REST check of the server inside v0.2.0-preview.canvas-repair.20260912, completed2026-09-12T11:37:33.2147578Z with runner exit0 and25 requests. Studio's source label33e30c1 identifies the package milestone; the unchanged server SHA256 ABA87A5FB795DEB995029A737C2EBB9D2B44C8D274EDAA2295363B226D9AF6BE retains its original source/build attribution. Adjacent DLL SHA256 AA282FA47BB2C4E210CEA5E470CDBDCA58568F0BE0BC73E404D86AB9CD95EF6A.
The runner used only Windows system directories and this extraction in child PATH, an unrelated cwd, loopback port53675 and a fresh private store. It checks warning-only source acceptance, validation without mutation, JSON/text diagnostic parity, invalid-write atomicity, exact authored-source persistence, repair and restart. Seven complete raw response pairs were independently byte-compared. The remaining sequence_gap warning is expected; this is not zero-diagnostic acceptance. All559 extracted package files retained exact inventory/size/SHA256 in postflight.json.
Two test-owned server processes856/2088 were stopped intentionally using Stop-Process, recorded exit-1/has_exited=true, and were absent in the independent readback. No graceful-shutdown claim is made. Outer stderr is empty; both server stderr files contain startup messages. No GUI, duplicate schema-suite, remote-deployment or Linux check was run.
result-report.md, runner-status.json, all25 response/metadata pairs and nine request bodies preserve the closed assertions and scope. Bodyless GET requests have no request JSON; method/path/status/ETag are in their metadata. coverage-probe-strict.original.ps1, exact fixture, adapted runner and adaptation.diff preserve the prior source and bounded launch adaptation. preparation-README.md is the untouched pre-execution note; its “not executed” status is historical.
The archive excludes the private store envelope/lock because the served model/source, committed revisions and before/after restart response comparisons already bind the tested persistence behavior; no archived physical store snapshot is claimed. The fixed synthetic credential is omitted as a separate file because it is already literal in the runner. Empty cwd and all package binaries/ZIP are excluded. Original private evidence is preserved.
manifest.json binds each exact original/copy payload; readback.json is a separate process reread of originals, payloads and final metadata inventory. Copying and readback execute no application, oracle or test. Root owns exact-byte Git attributes, integration and publication.