stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 2 Releases Wiki Activity
Files
dd98d6c3f6c80c4e04cddb4a4427f077ab6d19d4
git.stella-ops.org/docs/features/checked/web/quick-verify-drawer-ui-component.md
master 7943cfb3af chore(docs+devops): cross-module doc sync + sprint archival moves + compose updates 
Bundled pre-session doc + ops work:
- docs/modules/**: sync across advisory-ai, airgap, cli, excititor,
  export-center, findings-ledger, notifier, notify, platform, router,
  sbom-service, ui, web (architectural + operational updates)
- docs/features/**: updates to checked excititor vex pipeline,
  developer workspace, quick verify drawer
- docs top-level: README, quickstart, API_CLI_REFERENCE, UI_GUIDE,
  code-of-conduct/TESTING_PRACTICES updates
- docs/qa/feature-checks/: FLOW.md + excititor state update
- docs/implplan/: remaining sprint updates + new Concelier source
  credentials sprint (SPRINT_20260422_003)
- docs-archived/implplan/: 30 sprint archival moves (ElkSharp series,
  misc completed sprints)
- devops/compose: .env + services compose + env example + router gateway
  config updates

File-level granularity preserved.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-22 16:06:39 +03:00

1.7 KiB
Raw Blame History

Quick-Verify Drawer UI Component

Module

Web

Status

VERIFIED

Description

Slide-out drawer component used by Quick-Verify entry points across the Web UI. The shared drawer now fails closed with an explicit unavailable state when a caller lacks a bound runtime verification contract, instead of simulating a verified receipt.

Implementation Details

  • Feature directory: src/Web/StellaOps.Web/src/app/shared/components/quick-verify-drawer/
  • Components:
    • quick-verify-drawer (src/Web/StellaOps.Web/src/app/shared/components/quick-verify-drawer/quick-verify-drawer.component.ts)
  • Source: batch_38/file_13.md
  • Runtime note: the shared drawer no longer fabricates verification success or a synthetic receipt for heterogeneous caller identifiers such as bundle IDs, verdict IDs, or content hashes.

E2E Test Plan

  • Setup:
    • Log in with a user that has appropriate permissions
    • Navigate to the relevant page/section where this feature appears
    • Ensure test data exists (scanned artifacts, SBOM data, or seed data as needed)
  • Core verification:
    • Verify the panel/drawer opens on trigger (click, keyboard shortcut)
    • Verify the panel displays the correct detail data for the selected item
    • Verify the panel can be closed (X button, Escape key, backdrop click)
  • Edge cases:
    • Verify graceful handling when backend API is unavailable (error state)
    • Verify responsive layout at different viewport sizes
    • Verify accessibility (keyboard navigation, screen reader labels, ARIA attributes)

Verification

  • Run: docs/qa/feature-checks/runs/web/quick-verify-drawer-ui-component/run-001/
  • Date (UTC): 2026-02-11