Finalize UI truthfulness and bootstrap hardening
This commit is contained in:
@@ -7,9 +7,9 @@ This document defines the functional requirements for the Stella Ops Setup Wizar
|
||||
The Setup Wizard provides a guided, step-by-step configuration experience that:
|
||||
- Validates infrastructure dependencies (PostgreSQL, Valkey)
|
||||
- Runs database migrations
|
||||
- Configures required integrations
|
||||
- Sets up environments and agents
|
||||
- Verifies each step via Doctor checks
|
||||
- Bootstraps the initial admin and crypto profile
|
||||
- Exposes a truthful required-readiness summary for setup completion
|
||||
- Hands tenant onboarding to authenticated `/setup/*` and integration command surfaces instead of pretending they are bootstrap steps
|
||||
|
||||
---
|
||||
|
||||
@@ -27,7 +27,7 @@ The system enters "Operational" state when:
|
||||
| Admin user exists | At least one admin user with `admin:*` scope | `check.auth.admin.exists` |
|
||||
| Crypto profile valid | At least one signing key configured | `check.crypto.profile.valid` |
|
||||
|
||||
**Gating Behavior:** UI blocks access to operational features until Operational threshold met.
|
||||
**Gating Behavior:** Setup status and finalize gate only on this operational threshold. Optional post-boot services may still be degraded and are surfaced through health diagnostics instead of blocking bootstrap completion.
|
||||
|
||||
### 2.2 Production-Ready (Recommended)
|
||||
|
||||
@@ -58,7 +58,9 @@ The system reaches "Production-Ready" state when:
|
||||
| `admin` | Admin Bootstrap | Yes | No | Security |
|
||||
| `crypto` | Crypto Profile | Yes | No | Security |
|
||||
|
||||
### 3.2 Integration Steps
|
||||
Only these five core steps are current runtime setup step IDs. The integration and orchestration catalogs below are historical handoff targets and are no longer accepted by the current setup APIs or `stella setup` command group.
|
||||
|
||||
### 3.2 Integration Handoffs (Not current setup steps)
|
||||
|
||||
| Step ID | Name | Required | Skippable | Category |
|
||||
|---------|------|----------|-----------|----------|
|
||||
@@ -69,7 +71,7 @@ The system reaches "Production-Ready" state when:
|
||||
| `notifications` | Notification Channels | No | Yes | Integration |
|
||||
| `identity` | Identity Provider (OIDC/LDAP) | No | Yes | Security |
|
||||
|
||||
### 3.3 Orchestration Steps
|
||||
### 3.3 Orchestration Handoffs (Not current setup steps)
|
||||
|
||||
| Step ID | Name | Required | Skippable | Category |
|
||||
|---------|------|----------|-----------|----------|
|
||||
@@ -81,6 +83,8 @@ The system reaches "Production-Ready" state when:
|
||||
|
||||
## 4. Step Specifications
|
||||
|
||||
Sections 4.1-4.5 describe the current installation-scoped setup steps. Sections 4.6 and later remain useful as onboarding capability notes, but those inputs now belong to authenticated post-bootstrap surfaces rather than the setup wizard step catalog.
|
||||
|
||||
### 4.1 Database Setup (`database`)
|
||||
|
||||
**Purpose:** Configure PostgreSQL connection and verify accessibility.
|
||||
|
||||
Reference in New Issue
Block a user