Add cumulative Truthtrance force-revival commitments

docs/TRUTHTRANCE_REVIVAL_PROMISES.md

@@ -0,0 +1,96 @@
+# Truthtrance native force-revival promises
+
+## Current-phase prototype — 26 October 2026
+
+**Prototyped / Partial.** A structured question binds cumulative future ordinary
+force returns in the current Revival phase, for registered bare native Basic
+and Advanced tables. Choose total, normal or elite physical counters and a
+minimum from1 to20. This adds no game-start permission. Optional modules,
+earlier-phase questions, grouped revival expressions and special/card revival
+claims remain required work.
+
+## Authority and selected interpretation
+
+The [November2020 FAQ p8](https://www.gf9games.com/dune/wp-content/uploads/2020/11/Dune-FAQ-Nov-2020.pdf#page=8)
+supplies general current-turn question/compliance/impossibility authority;
+its previously checked indexed text is recorded in the
+[ordinary-bid contract](TRUTHTRANCE_BID_PROMISES.md). A direct fetch during this
+slice returned403, so it supplies no newly checked dedicated revival ruling.
+The user-authorized Advanced source, physical39 replacement Truthtrance text,
+also requires compliance during the current turn and permits later impossibility
+release. That local passage was read for this slice. Original native revival
+quotes and [Advanced turn order](ADVANCED_REVIVAL_ORDER.md) remain authoritative.
+
+Under standing14October choose-recommended authority, select an explicit
+**cumulative future ordinary-return** question. Count completed returns after
+each definite answer. Splitting a return does not avoid No. Each elite is one
+physical counter; normal means amount minus elites. Already completed returns,
+leaders, Ghola, Emperor-funded extras and other special returns are excluded
+because the question specifically names ordinary force revival. Actual native
+requests, responses, quotes, force transfers and payments remain unchanged.
+
+The phase interval/counting and accepted-order impossibility policy are
+provisional software compositions, not a dedicated publisher clarification.
+Waiting or current participants with a remaining opportunity can answer.
+Basic No persists through phase close because readiness can reopen. An ordered
+Advanced participant's No finishes when its native opportunity closes.
+An unmet Yes prevents voluntary Finish Revival and spending or requests that
+would remove the remaining completion. Completed opposing consequences can
+release only impossible Yes answers, retaining No and feasible answers in
+accepted order. A declaration alone never fulfills a promised return.
+
+## Connected behavior
+
+`game/revival-promises.ts` owns bounded canonical claims, typed physical counting,
+immutable cumulative progress and joint Yes/No checks. The packet is
+`{kind:'revival',target,turn,counter,minimum}` inside the original `truthAsk`.
+Normal declaration, priority, answer, physical discard and continuation remain.
+Each accepted answer has a distinct original event and begins at progress0.
+Only the respondent receives feasible answer choices and its own promises/guide.
+Public question and answer history remains public.
+
+The original native force-request quote is shared with a bounded guide search.
+It retains real typed Tanks, remaining normal/free/elite allowances, actual
+prices and Ixian free-Cyborg allocation. No unknown gift, future draw or foreign
+choice supplies resources. Earlier shipment/movement obligations constrain the
+quoted final return. The guide sends the original `revive` or `ready` packet
+with its own event and waits for actual native turn ownership. Manual requests
+retain their original shape. Stale guided events reject.
+
+The question selector, validated physical-counter fields, public preview,
+target-only answer buttons and persistent promise panel are connected. The
+panel shows progress, fulfillment and release; it does not time out. All four
+existing minimal AI profiles use the same projected answer and native guide.
+Full AI strategy/calibration remains deferred.
+
+## Evidence and remaining gates
+
+Focused pure, original-deal/death runtime and control evidence is recorded in
+`tests/revival-promises.test.ts`, `tests/fixture-truth-revival.ts`,
+`tests/truth-revival-runtime.test.ts` and `tests/truth-revival-controls.test.tsx`.
+Frozen v2 proof passes22files/288cases, `npm run check:quick` and `npm run build`.
+Five native engine/GameTable SSR paths render20 tables and exercise five actual
+hook-free guide callbacks. Original H/A/E Basic53/Advanced58-action sources
+actually ship3 for6, lose3 to the next Storm and reach turn2 Revival with4spice.
+Another9/8 actions bind/return3 with1free and4paid; Advanced returns one actual
+Sardaukar counter. All four minimal policies per source submit a legal return.
+An8-action Advanced No2 path returns1 and finishes below its threshold.
+
+Original native Tleilaxu/Ix47 sources use143 actions;19 allowed or15 stopped
+actions retain pending progress0, then either real return3/payment4 or actual
+opposing special-Karama prevention/release with no return/payment. Original33/47
+cards remain. Seventeen native,10pure,6control and2funding cases cover actual
+return/typed/split/prior semantics, two original Truth copies, Ghola exclusions,
+Basic post-Ready No, waiting ownership, stale callbacks and shipment funding in
+both answer orders. One observed older Nexus Fremen test now follows real
+ordered readiness rather than taking a native return out of turn.
+
+Report/manifest:
+`/home/quintine/.local/share/dune/checkpoints/20261026-truth-revival-proof-v2/`;
+journeys/HTML: adjacent `20261026-truth-revival-runtime/`.
+The final documentation overlay corrects one rules-reference related-topic
+anchor and records this evidence; the exact anchor replacement is asserted.
+
+No complete faction/mode, all combinations,
+recovery/privacy/custody, browser/mobile or deployed acceptance is certified.
+No saved game, database, server or deployment is changed by this prototype.