Allow Richese reveal during selected responses

docs/CURRENT_STATUS.md

@@ -17,6 +17,27 @@ open mode gates.
 
 ## Current checkpoint and work
 
+**Basic Richese reveals during responses — 29 October. Prototyped / Partial.**
+The owner can reveal an existing No-Field during clean CHOAM Charity,
+Atreides normal-auction inspection, Richese cache-auction declaration and
+Fremen allied-revival grant responses. The original response and passes
+continue without a new wait. Real Basic games exercise the paid marker,
+physical reveal, original Karama response and continuation; the Fremen case
+also uses real battle losses and a Nexus alliance. All four minimal bot profiles
+can advance the preserved Charity response. Six related files pass 24 cases;
+type checking, lint and production build pass. Other responses, nested
+children, active commitments, Truthtrance and optional modules remain fenced;
+complete Richese and deployed acceptance remain open.
+[Scope](RICHESE_NO_FIELD_RULES.md#basic-phase-opening-and-economic-interruptions--29-october-2026).
+
+**Gitea HTTP reproduction — 29 October. Open.** A new targeted test follows
+rejected stale-seat and foreign-origin POSTs with authorized reads through a
+single-connection agent, without retrying POSTs. All three discussion HTTP
+cases and 20 repetitions of the new case passed on a temporary Miniflare
+database. This did not reproduce run #103's closed connection or establish its
+cause; no production transport change was made. The temporary server was
+stopped without touching the running development server or existing games.
+
 **Paid current-turn travel deals — 29 October. Prototyped / Partial.** A
 two-human Basic classic offer can pair the recipient's travel term with an
 immediate bribe from the proposer. Final consent binds the existing native
@@ -242,8 +263,9 @@ cases pass. Run #101 succeeded. Run #103 built the container but failed one
 integration test after a revoked-seat POST: the following restored-seat GET
 lost its connection before receiving a response. Unread request-body handling
 on a reused connection is a hypothesis, not a confirmed cause. Run #104 for
-`82c639c` was running at the latest check; publication after the #103 failure
-was skipped. A disposable-container keep-alive reproduction remains open.
+`82c639c` succeeded; run #105 for `a1b2aac` was running at the
+latest check. Publication after the #103 failure was skipped. A
+disposable-container keep-alive reproduction remains open.
 
 **Truthtrance ally funding — 29 October. Prototyped / Partial.**
 Supported quiet Basic Bidding and Shipment/Movement questions can bind a future