Add Prettier and ESLint tooling (Refs #77)

2026-10-09 15:56:13 -04:00
parent 8ed059b8d3
commit 16469e2d43
711 changed files with 99737 additions and 28286 deletions
@@ -12,10 +12,10 @@ Choose **Add policy**, select the game and scope, and enter an explicit maximum.

 Choose **Save policy** to apply changes directly. Saving checks the current fleet, policy revision, ownership conflicts, and host readiness. If saving is blocked, the form keeps your settings and shows the reason. Saved policies show lobby counts, key availability, and the current status. An active job appears once with its latest stage and a **View job** link. Use **Lobbies** for per-map spare coverage and occupancy evidence, **Activity** for decision changes grouped by job, and **Metrics** for observed capacity and provisioning measurements.

-| Autoscaling | Behavior |
-| --- | --- |
-| Off | No new actions. Unsubmitted work is withdrawn and delivered operations remain tracked until settled. |
-| On | Adds lobbies and removes surplus lobbies after continuous empty evidence and all removal checks pass. |
+| Autoscaling | Behavior                                                                                              |
+| ----------- | ----------------------------------------------------------------------------------------------------- |
+| Off         | No new actions. Unsubmitted work is withdrawn and delivered operations remain tracked until settled.  |
+| On          | Adds lobbies and removes surplus lobbies after continuous empty evidence and all removal checks pass. |

 Plutonium keys belong to a game pool shared by every map, manual launch, collection, beta, and autoscaling policy for that game. An eligible creation uses the lowest available lobby number from 1–20 and reserves any free game key atomically. Key labels do not select a map or lobby. The policy shows saved and available game keys; policy maxima can exceed pool size, and a policy can be saved before any keys are added. An empty or exhausted pool holds new growth with a clear reason; it does not prevent surplus removal. Queued launches reserve their key, stopped instances retain it, and confirmed cleanup returns it to the pool. Failed or uncertain launches keep their reservation until safely reconciled. Existing lobbies and unfinished operations must be healthy and settled before activation. Automatic removal also requires agent **1.7.0 or later** advertising `instance.autoscaling-remove` on each affected host.