Add anger-scaled Sarka hunter waves every ten minutes

docs/aggression-ai.md

@@ -2,6 +2,28 @@
 
 Implemented 2026-09-23 in the combined Core addon. These are server-owned mission services; clients do not request spawns or supply casualty counts.
 
+## Šárka reinforcement waves (2026-10-16)
+
+After prison escape, every ten minutes the current anger score sends one Šárka
+per point: anger 3 means three cars, anger 0 means none. Anger still increases by
+one for every three enemy bodies identified and reported to HQ, capped at 30.
+Each car carries four selected-faction response troops total: a driver, two
+soldiers and one medic. Vanilla factions use their special-forces profiles;
+modded factions use their configured ResponseSoldier/ResponseMedic profiles.
+
+Cars spawn on checked clear roads 1–1.25 km from the nearest living player.
+Departures are spread five seconds apart; blocked placement retries within the
+current wave. Unplaced cars do not accumulate across waves. An empty round
+cancels pending departures and starts a new ten-minute wait when play resumes.
+These additional cars use the same radio orders, patrol, combat, dismount and
+capture behavior as other hunters. Player positions guide initial placement;
+subsequent pursuit still requires delivered sightings.
+
+Šárkas have a separate wave allowance from ordinary UAZs, trucks and motorbikes.
+Existing formation-budget limits still apply, so a full ledger can defer a wave.
+Original cars and crew remain physical after loss or capture; waves create new
+teams and never refill casualties in old teams.
+
 ## Coordinated pursuit candidate (2026-10-13)
 
 The new **Coordinated** doctrine organizes available formations into a shared pursuit. It is opt-in for qualification; **Current** remains the compatibility default. The first version runs entirely inside the mod. Python is used for offline replay and performance comparison, with no runtime service or language-model dependency. The intended playtest is two to four players, with a separate solo evasion check. Existing accuracy, damage and native detection settings are unchanged, so comparison can isolate the decisions and their execution.