b15d325701
Added browser captures, scorecard, recommendations, and follow-up spec candidates for the UI signal-to-noise browser audit.
30 lines
2.0 KiB
Markdown
30 lines
2.0 KiB
Markdown
# Recommendations
|
|
|
|
Verification level: derived from browser-verified screenshots plus repo-verified route/provider inventory.
|
|
|
|
## Recommended Global UI Rules
|
|
|
|
1. Decision-first header: every operator/customer detail page should answer status, reason, impact, and next action before metadata.
|
|
2. Metadata separation: IDs, timestamps, run context, provider capability details, and normalization lineage belong in a sidebar or collapsed technical detail by default.
|
|
3. Zero-state suppression: do not show 0 errors, 0 degraded, 0 active, or 0 follow-up cards when the primary decision already says no action needed.
|
|
4. Customer-safe default: customer/auditor views show outcome, readiness, risk, limitations, and export/handoff actions; diagnostics and internal IDs stay collapsed.
|
|
5. Diagnostic contract: diagnostics pages lead with what failed, why it likely failed, what to check next, and related evidence/operation.
|
|
6. Shell density guard: notification replay and navigation chrome should not dominate the first viewport of decision/report pages.
|
|
7. Provider readiness rule: provider configuration surfaces need a single readiness decision before lifecycle/capability columns.
|
|
|
|
## Prioritized Refactor Candidates
|
|
|
|
1. Baseline Profile View: high technical density and weak primary decision.
|
|
2. Backup Set View: restore-critical but metadata/lifecycle compete with usability.
|
|
3. OperationRun View: strong foundation; metadata needs stronger separation.
|
|
4. Customer Review Workspace: already productized, but first viewport should be calmer.
|
|
5. Provider Connections List/View: readiness should be more prominent than provider field inventory.
|
|
6. Environment Diagnostics / Required Permissions: diagnostic access and guidance need a consistent contract.
|
|
7. Evidence Snapshot View: route/fixture reachability must be resolved before UI quality can be trusted.
|
|
|
|
## Out of Scope
|
|
|
|
- No runtime changes were made.
|
|
- No CSS, Blade, PHP, policy, migration, seeder, or navigation changes are recommended for immediate implementation in this audit artifact.
|
|
- Detailed remediation belongs in follow-up specs.
|