From 8f67b39735ad4e51215812c7ca99c954de1c38a0 Mon Sep 17 00:00:00 2001
From: Quintine <15965533+Quintine@users.noreply.github.com>
Date: Wed, 30 Sep 2026 14:34:26 +1000
Subject: [PATCH] Record container HTTP pass and local Wrangler proxy caveat

---
 docs/CURRENT_STATUS.md        | 19 +++++++++++++++----
 docs/IMPLEMENTATION_STATUS.md | 10 ++++++----
 2 files changed, 21 insertions(+), 8 deletions(-)

diff --git a/docs/CURRENT_STATUS.md b/docs/CURRENT_STATUS.md
index 413a5dbf..c082612e 100644
--- a/docs/CURRENT_STATUS.md
+++ b/docs/CURRENT_STATUS.md
@@ -39,10 +39,21 @@ The completed CHOAM card-sale reaction passed two- and three-spice
 engine cases, canceled-sale exclusion, authenticated SQLite recovery,
 direct engine smoke and rendered phone-width guide inspection.
 `npm run check` passed types, lint and 5,843 offline tests; the build
-passed. The isolated built-worker HTTP suite passed 50/55; four
-origin/validation cases returned 503 instead of 403/400 and one
-Advanced-lobby request timed out after 15 seconds. Full HTTP
-acceptance remains open.
+passed. A direct Wrangler-dev HTTP suite passed 50/55; four
+origin/validation requests returned 503 and one Advanced-lobby
+request timed out after 15 seconds. This local proxy run is not
+a green suite; the proxy-free container run below passed.
+
+One diagnostic POST returned Wrangler's literal "Your worker restarted
+mid-request" 503 body; 100 subsequent identical requests returned the
+application's expected 400. [Cloudflare workers-sdk issue #14641](https://github.com/cloudflare/workers-sdk/issues/14641)
+documents a local dev-proxy disconnect with this misleading status.
+This points to the proxy for those transient failures, not to a
+verified application fix. The existing [container verifier](../tools/verify-container.mjs)
+runs the **full** HTTP suite against isolated Docker without that
+Wrangler dev proxy. Revision `4c07e1b` passed workflow
+`36668822954`, including this full HTTP suite, and published its
+image. Live NAS deployment and acceptance remain open.
 
 The private normal-auction Ixian ally reaction passed genuine-setup
 engine, authenticated SQLite and direct engine smoke checks. The full
diff --git a/docs/IMPLEMENTATION_STATUS.md b/docs/IMPLEMENTATION_STATUS.md
index 6d6004a4..9bfa5e93 100644
--- a/docs/IMPLEMENTATION_STATUS.md
+++ b/docs/IMPLEMENTATION_STATUS.md
@@ -23,11 +23,13 @@ expansion and complete Semuta gates remain closed.
 `npm run check` passed types, lint and 5,843 offline tests; the
 production build passed. The phone-width built-worker guide showed
 the sold-card timing. Independent review found no scoped defect.
-The isolated built-worker HTTP suite passed 50/55: four origin/
+The direct Wrangler-dev HTTP suite passed 50/55: four origin/
 validation requests returned 503 instead of expected 403/400,
-and one Advanced-lobby request timed out after 15 seconds.
-Full HTTP and production acceptance remain open; no production
-game was touched.
+and one Advanced-lobby request timed out after 15 seconds. The
+proxy-free container workflow `36668822954` passed its isolated
+storage checks and **full** HTTP integration suite, then published
+the `4c07e1b` image. This is not a live NAS deployment or
+production acceptance; no production game was touched.
 
 ## 30 September 2026 — Semuta before private Ixian ally replacement