# Findings

Verification convention: each finding states browser-verified/repo-verified status explicitly.

## UI-AUDIT-368-F01 - Evidence Snapshot detail not reachable in smoke browser context

- Severity: P1
- Surface/Page: Evidence Snapshot View
- Screenshot: artifacts/screenshots/blocked-or-error/010-evidence-surface-view-evidence-snapshot-error.png
- Browser verified: yes
- Repo verified: yes
- Problem: Evidence detail route redirected to admin login for available review/evidence fixture context.
- Why it matters: Evidence/audit surfaces cannot be evaluated or trusted as customer-ready if fixture access is unclear.
- User impact: Auditors and operators may be unable to verify evidence details during review flows.
- Recommended fix direction: Document/repair evidence fixture reachability; keep evidence route authorization explicit.
- Should be global rule: no
- Candidate spec: Spec C

## UI-AUDIT-368-F02 - System panel not browser-auditable with available fixtures

- Severity: P1
- Surface/Page: System dashboard and operations
- Screenshot: artifacts/screenshots/blocked-or-error/031-system-surface-dashboard-system-dashboard-error.png
- Browser verified: yes
- Repo verified: yes
- Problem: /system and /system/ops/runs redirected to /system/login; no system smoke auth route was found.
- Why it matters: System surfaces are high-risk operational views and need separate productization evidence.
- User impact: Platform-admin UI quality cannot be scored from the current browser pass.
- Recommended fix direction: Provide a documented system-panel browser fixture or audit procedure.
- Should be global rule: no
- Candidate spec: Spec D

## UI-AUDIT-368-F03 - Baseline Profile view is too technical by default

- Severity: P1
- Surface/Page: Baseline Profile View
- Screenshot: artifacts/screenshots/admin/008-decision-surface-view-baseline-profile.png
- Browser verified: yes
- Repo verified: yes
- Problem: The first viewport emphasizes long profile naming, capture mode, normalization lineage, foundations, and metadata over an operator decision.
- Why it matters: Baselines should answer whether a standard is assigned, ready, comparable, and actionable.
- User impact: Operators must parse internal terms before knowing what to do.
- Recommended fix direction: Add decision-first baseline summary; move normalization lineage and metadata to details.
- Should be global rule: yes
- Candidate spec: Spec B

## UI-AUDIT-368-F04 - Backup Set view mixes usability with lifecycle/technical metadata

- Severity: P2
- Surface/Page: Backup Set View
- Screenshot: artifacts/screenshots/admin/005-workflow-surface-view-backup-set.png
- Browser verified: yes
- Repo verified: yes
- Problem: Usability, timing, lifecycle, related context, and technical detail all appear as peer sections.
- Why it matters: Backup views should answer whether the backup is usable and what it contains.
- User impact: Restore decisions require extra scanning before trust.
- Recommended fix direction: Make backup usability and item inventory primary; demote IDs/timing to sidebar/details.
- Should be global rule: yes
- Candidate spec: Spec B

## UI-AUDIT-368-F05 - Zero and no-attention metrics repeat already-clear outcomes

- Severity: P2
- Surface/Page: Environment Dashboard and Operations Hub
- Screenshot: artifacts/screenshots/admin/002-operator-surface-list-operations-hub.png
- Browser verified: yes
- Repo verified: yes
- Problem: Pages show no-attention/no-pressure decisions while also showing zero cards or zero metrics.
- Why it matters: Zero-card spam lowers signal and makes healthy pages look busy.
- User impact: Operators spend attention on confirming absence rather than acting.
- Recommended fix direction: Suppress zero-state metric cards when the decision summary already communicates healthy/no-action.
- Should be global rule: yes
- Candidate spec: Spec A

## UI-AUDIT-368-F06 - Navigation and notification chrome overwhelms first viewport

- Severity: P2
- Surface/Page: Most admin/customer captured pages
- Screenshot: artifacts/screenshots/customer/011-customer-surface-report-customer-review-workspace.png
- Browser verified: yes
- Repo verified: yes
- Problem: Captured body samples repeatedly begin with global search, navigation groups, environment selector, language actions, and notification text.
- Why it matters: A page audit should see the page question before shell utility text.
- User impact: Customer and operator pages feel denser than their actual domain content.
- Recommended fix direction: Reduce notification replay and consider customer/report modes with quieter shell chrome.
- Should be global rule: yes
- Candidate spec: Spec A

## UI-AUDIT-368-F07 - Provider Connections list lacks a dominant readiness decision

- Severity: P2
- Surface/Page: Provider Connections List
- Screenshot: artifacts/screenshots/admin/017-configuration-surface-list-provider-connections.png
- Browser verified: yes
- Repo verified: yes
- Problem: Table defaults expose provider, target scope, lifecycle, consent, verification, and capability fields without a single provider readiness answer.
- Why it matters: Provider health/configuration should answer whether Graph-backed operations are ready or blocked.
- User impact: Support/operator users must map technical columns into readiness themselves.
- Recommended fix direction: Add provider readiness summary; keep lifecycle/capability fields secondary.
- Should be global rule: yes
- Candidate spec: Spec D

## UI-AUDIT-368-F08 - Diagnostics page needs stronger operator guidance first

- Severity: P2
- Surface/Page: Environment Diagnostics
- Screenshot: artifacts/screenshots/admin/015-diagnostic-surface-diagnostics-environment-diagnostics.png
- Browser verified: yes
- Repo verified: yes
- Problem: The page is correctly diagnostic, but the visible summary should lead with what failed, likely cause, and what to check next.
- Why it matters: Diagnostics can be technical, but they still need action framing.
- User impact: Support users may start in raw context rather than remediation path.
- Recommended fix direction: Add what failed / why likely / next check decision block.
- Should be global rule: yes
- Candidate spec: Spec D

## UI-AUDIT-368-F09 - Customer Review Workspace is good but too dense

- Severity: P2
- Surface/Page: Customer Review Workspace
- Screenshot: artifacts/screenshots/customer/011-customer-surface-report-customer-review-workspace.png
- Browser verified: yes
- Repo verified: yes
- Problem: Customer outcome and limitations are present, but many status phrases/actions compete in the first viewport.
- Why it matters: Customer/auditor surfaces need especially calm defaults.
- User impact: Customers may miss the exact review state and next handoff action.
- Recommended fix direction: Keep outcome, readiness, limitation, export/action; demote supporting flow details.
- Should be global rule: yes
- Candidate spec: Spec C

## UI-AUDIT-368-F10 - Operation detail is strong but still shows metadata too early

- Severity: P2
- Surface/Page: OperationRun View
- Screenshot: artifacts/screenshots/admin/003-operator-surface-view-operation-run.png
- Browser verified: yes
- Repo verified: yes
- Problem: Decision/guidance appears early, but lifecycle, timing, metadata, related context, and monitoring detail are visible as peer concepts.
- Why it matters: Operation pages should resolve whether action is needed before showing run mechanics.
- User impact: Operators can over-focus on run internals instead of next action.
- Recommended fix direction: Move lifecycle/timing/metadata into a technical aside; preserve decision and guidance pattern.
- Should be global rule: yes
- Candidate spec: Spec B