Integrate release recovery, semantic review, coverage and Windows packaging

2026-09-06 16:31:55 -07:00
parent c091f80e6e
commit 2b2d2bc18b
174 changed files with 27635 additions and 127 deletions
@@ -0,0 +1,37 @@
+# Real REST coverage parity acceptance
+
+Executed 2026-09-06 against staged `arcadia-server.exe` SHA256
+`BB775876741FE4A7B07CDE08940AEC8E23F545FDAFEC024FC4DC3BA6DD1AB9FC`, with
+only Windows system directories on PATH and the staged `libunwind.dll` beside the
+binary. A fresh synthetic store and an ephemeral loopback port were used; no user
+server/model was touched. The probe started and stopped only its own hidden server.
+
+All **25 HTTP requests passed**. Evidence is retained under
+`.local/rest-coverage-20260906-160857`: request payloads, response bodies, status/
+ETag metadata, binary provenance, server logs and `result.json`. The prepared runner
+is now tracked at `harness/fixtures/rest-coverage/run-coverage-probe.ps1`; the
+three-bundle payload is adjacent as `coverage-probe.json`. The tracked copy was
+rerun successfully with another fresh store and the same clean PATH: all25 requests
+passed again under `.local/rest-coverage-20260906-161345`. See the adjacent README
+for reproducible invocation.
+
+| Observable behavior | Observed result |
+|---|---|
+| Incomplete bundle candidate | HTTP200, valid:true; exact five advisory code/object/field tuples from the plan, all warnings with submitted `work.arcadia` locations. Accepted model/source/ETag unchanged. |
+| Warning-only bundle commit | HTTP200, changed:true, revision2. Exact three submitted files retained, including comments and explicit IDs. |
+| Current validation, native JSON and canonical Arcadia candidate parity | Same five code/object/field tuples, no structural errors. |
+| Invalid Entity endpoint on Interaction | Candidate200/valid:false with `invalid_endpoints`; all five new completeness codes gated. PUT422; accepted model, source bundle and ETag unchanged. |
+| Repair | HTTP200, revision3; all five completeness codes clear. The independent existing `sequence_gap` warning remains on Process steps2–3, as expected. |
+| Forced server stop and restart, same isolated store | Repaired model/source/validation and opaque ETag identical. |
+| Explicit replacement with incomplete bundle | HTTP200, revision4; exact five warnings reappear. This operation is replacement, not server Undo. |
+
+The first attempt correctly rejected the synthetic alias `parent` as reserved.
+The fixture now uses `activity_group`, retaining all UUIDs and expected semantics;
+the complete probe was rerun from a fresh store. This was fixture repair, not a
+production parser change. The failed attempt remains in
+`.local/rest-coverage-20260906-160838` for provenance.
+
+This verifies the current Windows service and diagnostics parity, admission and
+restart behavior for the representative OA fixture. It does not establish Linux
+runtime, container deployment, production-scale throughput or category/source6
+features. No probe process is intentionally left running.