Make local UI setup truthful and rerunnable

devops/compose/README.md

@@ -115,6 +115,13 @@ This sequence is the canonical migration gate for on-prem upgradeable deployment
 Current behavior details:
 
 - `./postgres-init` scripts execute only during first PostgreSQL initialization (`/docker-entrypoint-initdb.d` mount).
+- `postgres-init/14-platform-environment-settings.sql` now creates the
+  canonical installation-scoped `platform.environment_settings` table without
+  pre-seeding `SetupComplete=true`; fresh local databases therefore enter the
+  setup wizard until the Platform setup session is finalized. Existing local
+  volumes that still carry the legacy `(tenant_id, key)` table shape are
+  auto-converged by Platform release migration
+  `064_EnvironmentSettingsInstallationScopeConvergence.sql`.
 - Some services run startup migrations via hosted services; others are currently CLI-only or not wired yet.
 - Use `docs/db/MIGRATION_INVENTORY.md` as the authoritative current-state matrix before production upgrades.
 - Consolidation target policy and module cutover waves are defined in `docs/db/MIGRATION_CONSOLIDATION_PLAN.md`.
@@ -331,7 +338,10 @@ The harness now supports inline GitLab secret staging through the browser when
 `STELLAOPS_UI_BOOTSTRAP_GITLAB_REGISTRY_BASIC` are supplied. The separate
 first-run setup wizard now reaches the Platform setup API through the
 frontdoor and uses persisted installation-scoped setup sessions for the five
-truthful control-plane steps.
+truthful control-plane steps. The local compose lane also forwards
+`AUTHORITY_BOOTSTRAP_APIKEY` into Platform as `STELLAOPS_BOOTSTRAP_KEY` so the
+wizard can call Authority's `/internal/users` bootstrap endpoint during the
+Admin step.
 
 **Hosts file entries** (add to `C:\Windows\System32\drivers\etc\hosts`):
 ```