Add ending the game

data/input/01_game_concepts.yaml

@@ -201,6 +201,24 @@ sections:
 
 - section: sec_ending_the_game
   text: Ending the Game
+  rules:
+  - subsection: rule_game_end
+    text: The game ends when a player meets one of their win conditions.
+    rules:
+    - rule: rule_simultaneous_win
+      text: If both players would simultaneously satisfy their win conditions, the game ends in a draw.
+  - subsection: rule_win_conditions
+    text: Each player has two possible win conditions available.
+    rules:
+    - rule: rule_win_agenda_points
+      text: |-
+        Either player can win by collecting agenda points in their score area (usually done by scoring or stealing agendas; see {ref:sec_score_steal}). A player with a score of 7 or more wins the game.
+    - rule: rule_flatline
+      text: |-
+        The Corp wins if the Runner is flatlined. The Runner is flatlined immediately if they suffer more damage than they have cards in their grip. The Runner is also flatlined if, at the beginning of their discard phase, their maximum hand size is less than 0. See {ref:sec_damage} for more information about damage.
+    - rule: rule_empty_rnd
+      text: |-
+        The Runner wins if the Corp is required to draw a card from R&D but cannot because R&D is empty.
 
 - section: sec_cards
   text: Cards
@@ -289,7 +307,7 @@ sections:
       text: |-
         Some abilities use the word "otherwise" to indicate that different instructions should be resolved depending on whether a nested cost was paid or not. In an ability with a nested cost of a form described in {ref:rule_nested_cost_may}, treat "otherwise" as an "if [you/they] do not" clause attached to the same cost. Conversely, in an ability with a nested cost of a form described in {ref:rule_nested_cost_unless}, treat "otherwise" as an "if [you/they] do" clause attached to the same cost. Note that "otherwise" can also appear in the context of other types of conditions, and does not by itself indicate a nested cost.
 
-- section: sec_score
+- section: sec_score_steal
   text: Score, Scoring and Stealing
 
 - section: sec_advancing_cards

data/input/10_additional_rules.yaml

@@ -9,9 +9,17 @@ sections:
       Some cards are {term:unique}, and have a unique symbol ([uniqsym]) before their name to designate this. There can be only one unique card of the same name active at a time. If a unique card becomes active, any other card that shares its name is trashed during the next checkpoint. Trashing a card this way cannot be prevented. See {ref:sec_checkpoints}.
   - rule: sec_old_self_reference_rules
     text: Some cards are written with self-referential language. If a card references its own name without using the word "copy", treat that name as if it said "this object".
+
+- section: sec_information
+  text: Information
+
 - section: sec_checkpoints
   text: Checkpoints
+
+- section: sec_damage
+  text: Damage
+
 - section: sec_link
   text: Link
   snippet: |-
-    The Runner's link is the number of points their path through the Net traverses between their rig and the Corp's server. The more proxies, redirects, and other intermediary connecting points between the Corp and the Runner, the harder it is for sysops to track down the Runner's virtual location.
+    The Runner's link is the number of points their path through the Net traverses between their rig and the Corp's server. The more proxies, redirects, and other intermediary connecting points between the Corp and the Runner, the harder it is for sysops to track down the Runner's virtual location.