Respect Fremen group revival grant for bots

docs/CURRENT_STATUS.md

@@ -17,6 +17,19 @@ open mode gates.
 
 ## Current checkpoint and work
 
+**Basic group Fremen revival scheduling — 29 October. Prototyped / Partial.**
+During concurrent Basic Revival, automated group allies wait individually for
+a human Fremen's eligible, useful free-revival grant. Grant, targeted Karama
+prevention, Fremen Ready or no added benefit releases the affected ally;
+unrelated bot actions and responses remain available. The Fremen panel explains
+the wait without exposing Tanks. Four related files pass 40 cases, including
+15 new cases across both allies and all four legal bot profiles; type checking,
+lint and production build pass. The tests form the group through real Nexus
+actions, with staged Revival and conserved Tanks. This is a provisional online
+priority, not strategic AI calibration; ordered Revival, other group interactions
+and deployed acceptance remain open.
+[Scope](FREMEN_REVIVAL_GRANT.md#human-fremen-and-automated-group-allies--29-october-2026).
+
 **Basic dead-leader battle preparation — 29 October. Prototyped / Partial.**
 Fresh classic Basic battles without Harkonnen open the existing neutral
 pre-leader opportunity when a combatant has a dead leader and no available

docs/FREMEN_REVIVAL_GRANT.md

@@ -1,5 +1,21 @@
 # Fremen allied free revival
 
+## Human Fremen and automated group allies — 29 October 2026
+
+**Prototyped / Partial.** In concurrent Basic Revival, each automated ally in
+the supported classic group preview waits for its own useful, available Fremen
+grant. Fremen may grant each ally independently, finish with the existing Ready
+action, or have a targeted grant prevented. Only that recipient's ordinary
+revival and Ready actions wait; unrelated bot actions and Karama responses
+continue. The shared grant quote and normal revival allowances determine when
+waiting is useful. The group panel explains this scheduling without showing
+allied Tanks or balances. This is a provisional online priority, not a printed
+timing rule or strategic AI calibration. The test uses genuine Nexus group
+formation with staged Revival and conserved Tanks; other group interactions,
+ordered Revival and deployed acceptance remain open. The later
+[Basic classic group lobby preview](OPTIONAL_ALLIANCE_VICTORY.md#basic-classic-group-lobby-preview--29-october-2026)
+supersedes older notes below that group starts were unavailable.
+
 ## Human Fremen and an automated ally — 29 October 2026
 
 **Prototyped / Partial.** During concurrent Basic Revival, an automated mutual
@@ -11,7 +27,8 @@ The Fremen's existing Ready for next phase also releases the wait, as do an
 accepted or prevented grant. Other bot actions and responses remain available.
 The Fremen panel explains this scheduling choice. This is a provisional online
 priority policy, not a printed rule or a new mandatory confirmation. Ordered
-Revival, larger alliances and other races are not covered by this policy.
+Revival and other races are not covered by this policy. The group follow-up
+above extends it to supported larger alliances.
 
 ## Staged three-member alliance — 28 October 2026