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

Finalize UI truthfulness and bootstrap hardening

Browse Source
This commit is contained in:
master
2026-04-16 16:23:54 +03:00
parent 4799aa2402
commit bc6b1c5959
145 changed files with 10503 additions and 9837 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
docs/features/checked/web/configuration-pane.md
View File

@@ -7,11 +7,13 @@ Web
VERIFIED
## Description
Console-level configuration pane showing integration status grouped by sections with connection health, detail views per integration, and a state management service for tracking configuration changes.
Console-level configuration pane showing live integration status grouped by sections with connection health, detail views per integration, and signal-based state management. The mounted page now derives rows from the integrations API and unified audit instead of seeded connector records.
## Implementation Details
- **Feature directory**: `src/Web/StellaOps.Web/src/app/features/configuration-pane/`
- **Routes**: `configuration-pane.routes.ts`
- **Canonical route**: `/setup/configuration-pane`
- **Legacy alias**: `/settings/configuration-pane`
- **Components**:
- `configuration-pane` (`src/Web/StellaOps.Web/src/app/features/configuration-pane/components/configuration-pane.component.ts`)
- `integration-detail` (`src/Web/StellaOps.Web/src/app/features/configuration-pane/components/integration-detail.component.ts`)
@@ -22,11 +24,15 @@ Console-level configuration pane showing integration status grouped by sections
- **Models**:
- `src/Web/StellaOps.Web/src/app/features/configuration-pane/models/configuration-pane.models.ts`
- **Source**: Feature matrix scan
- **Current runtime source of truth**:
- Registry, vault, and settings-store rows are composed from the live integrations API.
- History is composed from unified audit integration events.
- Database, cache, and telemetry sections remain explicit empty or missing states until a backing contract exists.
## E2E Test Plan
- **Setup**:
- [ ] Log in with a user that has appropriate permissions
- [ ] Navigate to `/console/configuration`
- [ ] Navigate to `/setup/configuration-pane`
- [ ] Ensure test data exists (scanned artifacts, SBOM data, or seed data as needed)
- **Core verification**:
- [ ] Verify settings form loads with current values pre-populated
@@ -51,19 +57,32 @@ Console-level configuration pane showing integration status grouped by sections
- Tier 2 evidence: `docs/qa/feature-checks/runs/web/configuration-pane/run-003/tier2-ui-check.json`
- Notes: `/console/configuration` failed strict end-user assertion because the `Configuration` heading never rendered during the Playwright transaction.
## Recheck (run-004)
## Historical Recheck (run-004)
- Date (UTC): 2026-02-11
- Status: VERIFIED (strict Tier 2 UI replay)
- Tier 1 evidence: Focused configuration-pane suite passed 3/3 across 1 file.
- Tier 2 evidence: `docs/qa/feature-checks/runs/web/configuration-pane/run-004/tier2-ui-check.json`
- Replay scope:
- Navigate to `/settings/configuration-pane` and verify heading, summary metrics, and integration list render.
- Verify `Primary Database` row using scoped `.integration-name` selector.
- Verify the then-current seeded `Primary Database` row using scoped `.integration-name` selector.
- Open integration detail panel and verify `Edit Configuration` action is visible.
## Recheck (run-007)
## Historical Recheck (run-007)
- Date (UTC): 2026-02-11T10:08:09Z
- Status: PASSED (strict Tier 2 UI replay)
- Tier 2 evidence: docs/qa/feature-checks/runs/web/configuration-pane/run-007/tier2-ui-check.json
- Notes: Verified on /settings/configuration-pane with configuration summary and detail-panel interaction assertions.
- Notes: Verified on /settings/configuration-pane with configuration summary and detail-panel interaction assertions against the earlier synthetic configuration-pane service.
## Recheck (run-008)
- Date (UTC): 2026-04-15T17:03:18Z
- Status: VERIFIED (strict Tier 2 UI replay)
- Tier 2 evidence: `docs/qa/feature-checks/runs/web/configuration-pane/run-008/tier2-ui-check.json`
- Replay scope:
- Open `/setup/configuration-pane` and verify the mounted configuration heading and summary copy render from the live integrations-backed page.
- Verify the removed seeded `Primary Database` row does not appear on the mounted route.
## 2026-04-15 Truthful State Cutover
- `configuration-pane-api.service.ts` no longer seeds connector rows, health checks, or history in mounted flows.
- The route now renders only integrations exposed by the live integrations API and shows explicit empty sections where backend coverage does not exist.
- The mounted page returned to `VERIFIED` after the run-008 live replay against `/setup/configuration-pane`.