A server reads only config.json and a few variables; everything else is
in the registry, set through the API. An install that's declared rather
than clicked through, such as the Helm chart, had no way to create the
first objects: the domain, administrator, blob store, coordinator and
cluster roles.
inbuxa --seed <PATH> boots as --upgrade-store does, upgrades the layout,
writes the first-start defaults, then runs the file as a JMAP request
body, as the system administrator, through the normal request handler:
the API's validation, password hashing and follow-up tasks, with
creation-id references between calls. {"$file": "<PATH>"} stands for
a file's contents, so secrets stay in mounted files.
It applies once, to a new store, and notes that in the store (key Ks).
Exit 0 when applied or applied before, 1 when it failed, 2 when the store
was set up another way or an earlier run stopped partway.
Spec: docs/spec/features/store-seed.md. Also carries the boxed
--upgrade-store future from #449, so main builds with every backend.