Add extra names for provinces so DATC parses

MultiversalDiplomacy/Model/Map.cs

@@ -314,13 +314,13 @@ public class Map
                 .AddOceanLocation(),
             Province.Empty("Eastern Mediterranean Sea", "EMS", "EAS")
                 .AddOceanLocation(),
-            Province.Empty("Gulf of Lyons", "GOL", "LYO")
+            Province.Empty("Gulf of Lyons", "Gulf of Lyon", "GOL", "LYO")
                 .AddOceanLocation(),
             Province.Empty("Ionian Sea", "IOS", "ION", "INS")
                 .AddOceanLocation(),
             Province.Empty("Tyrrhenian Sea", "TYS", "TYN")
                 .AddOceanLocation(),
-            Province.Empty("Western Mediterranean Sea", "WMS", "WES")
+            Province.Empty("Western Mediterranean Sea", "Western Mediterranean", "WMS", "WES")
                 .AddOceanLocation(),
 #endregion
         ];

docs/rules.md

@@ -10,6 +10,7 @@ When the adjudicator is in a more complete state, this section will declare the
 
 The MDATC (Multiversal Diplomacy Adjudicator Test Cases) document defines test cases that involve multiversal time travel.
 
+- 4.B.4 (coast specification in support orders): 5dplomacy does not interpret orders by reference to other orders. Therefore, if a coast is not specified in a move or support-move order and the possible coasts are ambiguous, the order is illegal and will be replaced by a hold, even in the case of a support-move order omitting a coast that is specified by the supported move by the same power.
 - 4.C.5 (missing nationality in support order), 4.C.6 (wrong nationality in support order): 5dplomacy does not support specifying the nationality of the supported unit.
 
 ## Variant rules