Slurm's jobs in llmgw's accounting: projects as accounts, jobs priced

With slurm.users llmgw, each project is a Slurm account, its organization's
and team's above it, with the project's members and its team's and
organization's on it; slurm.conf holds a job to its user's accounts. The
controller's agent keeps them with sacctmgr, only what it made, and reports
the jobs that ended in the last day; the leader records each once, its
GPU-hours (core-hours without cards) priced at auth.gpu_hour_cost into its
project's usage as model slurm/PARTITION.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

docs/admin-api.openapi.json

@@ -12573,6 +12573,10 @@
           "containers": {
             "type": "string",
             "description": "Containers is whether jobs may run in containers: \"on\" once every machine has pyxis and enroot, \"installing\" until then, empty when slurm.containers is off."
+          },
+          "accounts": {
+            "type": "integer",
+            "description": "Accounts is how many of Slurm's accounts are llmgw's projects'."
           }
         }
       },