stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 2 Releases Wiki Activity

docs: module dossier + install/quickstart sync for truthful cutover sprints

Browse Source 
- API_CLI_REFERENCE.md, INSTALL_GUIDE.md, quickstart.md, architecture/integrations.md, dev/DEV_ENVIRONMENT_SETUP.md, integrations/LOCAL_SERVICES.md: reflect real-service wiring.
- docs/modules/**: module dossier updates across the modules touched by SPRINT_20260415_001..007 + SPRINT_20260416_003..017 + SPRINT_20260417_018..024 + SPRINT_20260418_025 + SPRINT_20260419_026.
- docs/features/checked/web/**: update feature notes where UI changed.
- docs/qa/feature-checks/runs/web/evidence-presentation-ux/: QA evidence artifacts.
- docs/setup/**, docs/technical/**: align with setup wizard contracts.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
master
2026-04-19 14:45:09 +03:00
parent ad62ba7f76
commit fdf95e0f46
67 changed files with 590 additions and 360 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
docs/dev/DEV_ENVIRONMENT_SETUP.md
View File

@@ -37,7 +37,7 @@ The setup scripts do not start the optional real-provider compose lane in `devop
On Windows and Linux, the backend image builder now publishes each selected .NET service locally and builds the hardened runtime image from a small temporary context. That avoids repeatedly streaming the whole monorepo into Docker during scratch setup.
### Quick validation + demo seed (first-run path)
### Quick validation + UI setup (first-run path)
```powershell
# 1) Bring platform up quickly (reuse existing images)
@@ -46,15 +46,8 @@ On Windows and Linux, the backend image builder now publishes each selected .NET
# 2) Validate platform health
docker compose -f devops/compose/docker-compose.stella-ops.yml ps
# 3) Preview seed work
dotnet run --project src/Cli/StellaOps.Cli/StellaOps.Cli.csproj -- `
admin seed-demo --dry-run `
--connection "Host=127.1.1.1;Port=5432;Database=stellaops_platform;Username=stellaops;Password=stellaops"
# 4) Execute demo seeding
dotnet run --project src/Cli/StellaOps.Cli/StellaOps.Cli.csproj -- `
admin seed-demo --confirm `
--connection "Host=127.1.1.1;Port=5432;Database=stellaops_platform;Username=stellaops;Password=stellaops"
# 3) Open https://stella-ops.local and complete the setup wizard
# 4) Sign in with the administrator credentials you created
```
### Known warnings vs blocking failures
@@ -65,7 +58,7 @@ dotnet run --project src/Cli/StellaOps.Cli/StellaOps.Cli.csproj -- `
| `SM remote service probe failed (localhost:56080)` during `stella --verbose ...` or crypto diagnostics | Warning | Optional SM remote provider is unavailable | Ignore unless validating China SM remote crypto profile; ordinary CLI payload commands now suppress this startup noise |
| `stellaops-dev-rekor restarting` without `--profile sigstore` | Warning | Optional Sigstore container from prior run | Ignore for default profile or remove stale container |
| `policy ... scheduler_exceptions_tenant_isolation already exists` | Blocking | Outdated Scheduler migration idempotency | Update code and rerun seeding |
| `POST /api/v1/admin/seed-demo` returns 500 after patching source | Blocking | Running stale platform container image | Rebuild/restart platform image |
| Manual `POST /api/v1/admin/seed-demo` returns 500 after patching source | Blocking | Running stale platform container image | Rebuild/restart platform image |
---
@@ -360,9 +353,11 @@ docker compose -f devops/compose/docker-compose.stella-ops.yml ps
---
## 8. Seed demo data and verify endpoint errors
## 8. Optional manual demo data seeding and endpoint verification
Use the CLI seeder for local bootstraps and demo datasets:
This lane is for demo purposes only. It is not part of the default local setup path.
Use the CLI seeder only when you intentionally want demo/sample datasets:
```powershell
# dry-run