Respect Fremen group revival grant for bots
Verify and publish checkpoint container / container (push) Canceled after 0s

This commit is contained in:
Quintine committed 2026-10-29 08:46:52 +11:00
1 parent e439f3f7b6
commit f9ca7ed9a9
6 files changed
+203 -7

No files matched your search

+13
View File
@@ -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