adding resource limits and archers

microservices/LocationsApi/README.md

@@ -28,16 +28,18 @@ locations are unowned `Open` records until claimed by a player.
 
 Player resource state is stored server-side in the `PlayerResources` collection.
 New players start with 100 gold. A player's headquarters generates 10 gold per
-minute. Log Camps generate wood and Mines generate ore. Generation is applied
-lazily when the resource record is read.
+minute. The starting town hall stores up to 500 gold, 100 wood, and 100 ore.
+Log Camps generate wood and Mines generate ore. Generation is applied lazily
+when the resource record is read and clamps at the current storage capacity.
 
 ## Units
 
-Unit training is stored server-side in the `UnitTraining` collection. The first
-unit type is `Scout`, which costs 50 gold and takes 60 seconds to train.
-Finished training is completed lazily when unit state is read. Claiming an
-unclaimed visible location consumes one completed Scout by deleting that Scout's
-training record.
+Unit training is stored server-side in the `UnitTraining` collection. `Scout`
+costs 50 gold and takes 60 seconds to train. `Archer` requires a completed
+Barracks, costs 100 gold and 100 wood, and takes 60 seconds to train. Finished
+training is completed lazily when unit state is read. Claiming an unclaimed
+visible location consumes one completed Scout by deleting that Scout's training
+record.
 
 ## Buildings
 
@@ -53,6 +55,7 @@ Timer settings are stored in the MongoDB `GameSettings` collection and are
 seeded on first read:
 
 - `ScoutTrainingSeconds`
+- `ArcherTrainingSeconds`
 - `LogCampBuildSeconds`
 - `MineBuildSeconds`
 - `BarracksBuildSeconds`