Compose native Stone and Reinforcements without a physical-token bonus

docs/REINFORCEMENTS_RUNTIME.md

@@ -11,7 +11,8 @@ nor a defense: Prescience of a category receives **None**, while the physical
 slot stays occupied and hidden until reveal. A named-card inspection still
 fixes the exact card. Harass & Withdraw may share the plan under the
 [provisional original-cost-first policy](#combined-utility-plan--16-october-2026).
-Stone Burner, Homeworld and other optional-module combinations remain gated.
+Original or copied Stone Burner composes in the existing native Advanced Occupy
+envelope; Homeworld, other profile and optional-module boundaries remain.
 
 The [combined-army follow-up](ECAZ_OCCUPY_RULES.md#independent-cards-with-combined-armies--2-october-2026)
 retains own-holder reserve cost and selected lead card/payment ownership.
@@ -45,7 +46,8 @@ provisional all-outcome policy.
 Both slot orders compose in the existing Basic/Advanced and selected Advanced
 Occupy envelopes. Only the card user's reserves and undialed forces change;
 original fixed Ecaz commitment and the other ally's pool stay separate.
-Stone/Reinforcements, Basic/unprofiled co-side and other module gates stay.
+Basic/unprofiled co-side and other module gates stay; Stone uses the
+[physical-token composition below](#native-stone-composition--16-october-2026).
 No persisted state or fresh/public profile is added.
 
 ### Scoped proof
@@ -74,3 +76,53 @@ HTTP, recovery/privacy/custody assurance campaign ran. Private proof artifacts
 remain outside Git; the owned source host and throwaway scripts were removed.
 
 
+## Native Stone composition — 16 October 2026
+
+Reinforcements now composes with same-plan or opposing Stone Burner, including
+a physical Mirror Weapon copying Stone. This uses the existing fresh native
+Advanced Occupy envelope with the independent Ecaz cards and actual Richese
+cache. No new profile, Basic Richese eligibility, public start or optional
+module is enabled.
+
+Stone still compares only physical undialed counters, including original
+fixed Ecaz and native variable ally contributions. Reinforcements adds no
+physical tokens, extra dial, support or on-board casualties; its +2 normal-score
+bonus is inactive for Stone comparison. Its original own-reserve cost still
+pays once under the existing provisional all-outcome policy. Original/copy
+kill-or-ignore modes and Traitor precedence remain unchanged. Reinforcements
+discards once; a winning physical Stone or Mirror keeps ordinary retention.
+
+The printed physical-token instruction and the existing score-only reserve
+card implementation are composed here. The reserve-payment question remains
+unanswered; no new publisher ruling or user answer is implied.
+
+### Scoped native Stone proof
+
+The affected sixteen-file offline union passes **167/167**, with types/lint
+and production build passing (module-register, large-chunk and Unknown-route
+warnings). New pure/native cases cover physical-token victory despite +2,
+same-plan/opposing cost, original elite reserves, fixed/variable card users,
+copied kill mode, Traitor precedence and physical retention.
+
+Eight fresh Node programs cover both lead roles and all four legal profiles,
+with original/Mirror attacks and36 accepted continuation actions. The native
+fixture initially exceeded hand capacity when a third selected card was added;
+it now returns unselected real hands to the conserved deck before lead choice
+and checks four-card limits. The actual390px journey was repeated on that
+corrected fixture, starting with only three held cards.
+
+Original total dial4/support1 compares five undialed coalition counters against
+four, never seven. All three native voters decline Traitor through actual
+controls. Ecaz pays reserves15→12 plus original fixed3 losses (Tanks6);
+Guild loses only variable1, leaving Ecaz2/Guild3 in the territory. Support
+costs Ecaz9→8. Reinforcements discards once; Stone is retained through its
+original choice, and battle/decision clear into collection. No root overflow,
+browser/application error or over-capacity hand occurs in the corrected journey.
+The earlier overfull fixture is not accepted evidence of a legal hand.
+
+Current reference parses; the composition anchor and23 evidence paths across
+both topics resolve, with all ten facets Partial. No human server, saved room,
+D1, deployment, public profile or new broad/HTTP/recovery/privacy/custody
+assurance campaign changed. Owned hosts/scripts are removed; private proof
+artifacts stay outside Git.
+