History
| Date | Author | Commit Message | ||
|---|---|---|---|---|
|
|
|
2026-09-15 13:43:39 42f3a4 | Anonymous | Align expedition renewal and combat growth with the owner answers |
|
|
|
2026-09-14 19:13:23 7609d1 | Anonymous | Remove text slop: disclaimers, process metadata, restatements and hedge tags; no rule changes (owner readability review, 14 Sep) |
|
|
|
2026-09-10 17:27:19 a1e62f | Anonymous | Remove review history and align superseded prose with current design rules |
|
|
|
2026-09-08 10:46:15 2bc44e | Anonymous | Integrate combat review and correct remaining encounter scope claims |
|
|
|
2026-09-08 10:39:07 f720e3 | Anonymous | Response to review 161 and PM 162/165: owner automatic-fire decision integrated, journal capture boundary corrected, clearance scope bounded, condition cost stated, alcove claim narrowed, frequency lever named through placement |
|
|
|
2026-09-08 10:27:11 e8f40d | Anonymous | Horde Encounters: route crowd and contested mechanism in one area, built on contract 157; staged interruption, caused pressure, successes that stay successes; route crowd argued as the common case |