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

- 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

View File

@@ -105,9 +105,9 @@ node src/Web/StellaOps.Web/scripts/live-integrations-ui-bootstrap.mjs
- The separate first-run setup wizard (`/setup-wizard/wizard`) now reaches the
Platform setup API through the frontdoor and uses persisted,
installation-scoped setup sessions for the five truthful control-plane steps.
- The wizard's Admin step uses Authority's internal bootstrap API, so the local
Platform container must receive the same bootstrap key via
`STELLAOPS_BOOTSTRAP_KEY` that Authority exposes through
- The wizard's Admin and Advisory/VEX Sources steps use internal bootstrap APIs,
so both the local Platform and Concelier containers must receive the same
bootstrap key via `STELLAOPS_BOOTSTRAP_KEY` that Authority exposes through
`AUTHORITY_BOOTSTRAP_APIKEY`.
CLI convergence path: