Clarify Bene Gesserit cache cancellation

docs/CURRENT_STATUS.md

@@ -17,6 +17,14 @@ open mode gates.
 
 ## Current checkpoint and work
 
+**Bene Gesserit cache cancellation guidance — 29 October. Prototyped / Partial.**
+The rules guide now describes the already supported Worthless-card cancellation
+of Richese's compulsory cache auction and its counter. Staged Bidding journeys
+cover first/last placement, both outcomes, ordinary-lot continuation and legal
+bot responses. Forty-three related cases, quick type/lint checks and the
+production build pass. Full auction modes and deployed acceptance remain open.
+[Scope](RICHESE_AUCTION_RULES.md#bene-gesserit-cache-cancellation-guidance--29-october-2026).
+
 **Native zero-marker battle continuation — 29 October. Prototyped / Partial.**
 The existing staged zero-reserve native No-Field journey now completes the
 actual Traitor decision and final battle opportunity, preserving the physical

docs/RICHESE_AUCTION_RULES.md

@@ -1,5 +1,17 @@
 # Richese auction rules and integration contract
 
+## Bene Gesserit cache cancellation guidance — 29 October 2026
+
+**Prototyped / Partial.** Advanced Bene Gesserit can use an eligible Worthless
+card as Karama to cancel Richese's compulsory cache auction. The existing
+user ruling restores the frozen ordinary-lot count. A printed Karama counter
+instead restores the original Richese response and lets that auction proceed.
+The [focused action journeys](../tests/bg-richese-cache-cancel.test.ts) exercise
+first/last placement, both outcomes, actual lot continuation and minimal legal
+bot responses from a staged pre-Bidding opportunity. This corrects older
+unsupported-cancellation guidance; it does not certify full auction modes.
+
+
 Audit: 2026-09-06. This document covers the complete core bidding pipeline: the compulsory cache lot, both alternative methods, advanced Black Market using all three methods, associated acquisition/payment effects, and the separate special Karama purchase. It is a source audit and implementation contract, not certification that Richese or a combined expansion mode is playable. Existing implementation-status gates remain in force.
 
 ## Evidence and limits