Make local UI setup truthful and rerunnable

docs/INSTALL_GUIDE.md

@@ -161,6 +161,11 @@ Canonical policy for upgradeable on-prem installs:
 Notes:
 
 - Compose PostgreSQL bootstrap scripts in `devops/compose/postgres-init` run only on first database initialization.
+- `devops/compose/postgres-init/14-platform-environment-settings.sql` now
+  leaves `platform.environment_settings` empty on fresh local databases so the
+  setup wizard owns first-run completion truth. Older local volumes with the
+  legacy `(tenant_id, key)` table shape are converged by Platform release
+  migration `064_EnvironmentSettingsInstallationScopeConvergence.sql`.
 - Startup-hosted migrations are currently wired only for selected modules; CLI coverage is also module-limited.
 - For the authoritative current-state module matrix, use `docs/db/MIGRATION_INVENTORY.md`.
 
@@ -210,6 +215,10 @@ Verified current UI boundary on `2026-04-14`:
   `platform.setup_sessions` and owns only the five control-plane steps the
   running control plane can truthfully converge: PostgreSQL, Valkey, schema
   migrations, admin bootstrap, and crypto profile.
+- The Admin step depends on Platform reaching Authority's internal bootstrap
+  endpoint with the shared bootstrap API key. In local compose, this is wired
+  by forwarding `AUTHORITY_BOOTSTRAP_APIKEY` into Platform as
+  `STELLAOPS_BOOTSTRAP_KEY`.
 - Tenant-scoped onboarding stays on `/setup/*` and other authenticated module
   surfaces instead of being duplicated inside the bootstrap wizard.
 - The inline GitLab path still needs real credential input from the operator.