# Spec 352 Browser Flow Audit — Environment Dashboard Operator Guidance

## Executive Summary
- Overall readiness: nearly ready
- Main flow result: the dashboard consistently surfaces one dominant operator-guidance case, the primary dashboard CTAs route to the expected environment-scoped destinations, Provider Blocker outranks Review Output when both conditions are present, and the No-Urgent-Action state reads as intentional rather than broken.
- Top issues:
  - `P2` Blocked states still carry avoidable action weight. The same primary CTA appears both in the page header and inside the guidance card, while the demoted recommended-actions rail remains visible below with additional buttons. The dominant case is still understandable, but the page is not yet as quiet as the spec intent.
  - `P2` The helper line `No single repo-real follow-up is currently available.` appears beneath guidance cards that already expose a concrete primary CTA, and in the review-output case also expose secondary links. That copy weakens operator confidence.
- Recommendation: patch before close

## Repo State
- Branch: `352-environment-dashboard-operator-guidance-consolidation`
- Safety snapshot captured before audit artifact generation.
- Dirty tracked files:
  - `apps/platform/app/Filament/Pages/EnvironmentDashboard.php`
  - `apps/platform/app/Filament/Widgets/Dashboard/EnvironmentDashboardOverview.php`
  - `apps/platform/app/Support/EnvironmentDashboard/EnvironmentDashboardSummary.php`
  - `apps/platform/app/Support/EnvironmentDashboard/EnvironmentDashboardSummaryBuilder.php`
  - `apps/platform/lang/de/localization.php`
  - `apps/platform/lang/en/localization.php`
  - `apps/platform/resources/views/filament/widgets/dashboard/environment-dashboard-overview.blade.php`
  - `apps/platform/tests/Feature/Filament/Spec330EnvironmentDashboardBaselineCompareProductizationTest.php`
  - `docs/ui-ux-enterprise-audit/page-reports/ui-002-environment-dashboard.md`
- Untracked files before this audit:
  - `apps/platform/tests/Browser/Spec352EnvironmentDashboardGuidanceSmokeTest.php`
  - `apps/platform/tests/Feature/Filament/Spec352EnvironmentDashboardGuidanceTest.php`
  - `apps/platform/tests/Unit/EnvironmentDashboard/`
  - `specs/352-environment-dashboard-operator-guidance-consolidation/`
- `git diff --stat` at snapshot time: `9 files changed, 707 insertions(+), 65 deletions(-)`
- Is Spec 352 active / uncommitted? yes
- Are only Spec-352 files changed? no
- Browser flow ran against the current working tree? yes
- Tests executed? no

## Browser Environment
- Base URL: `http://localhost`
- Login path used for local-only audit: `/admin/local/smoke-login`
- Audit user: `smoke-requester+352@tenantpilot.local`
- Workspace used: `Spec 352 Guidance Browser Audit` (`slug: spec-352-guidance-browser-audit`, `id: 33`)
- Environments used:
  - `Spec 352 Audit Provider Blocker` (`slug: spec-352-audit-provider-blocker`, `id: 51`)
  - `Spec 352 Audit Review Output` (`slug: spec-352-audit-review-output`, `id: 52`)
  - `Spec 352 Audit No Urgent Action` (`slug: spec-352-audit-no-urgent`, `id: 53`)
- Scenarios tested:
  - Provider blocker outranks review output
  - Review output guidance on dashboard
  - No urgent action
  - Secondary action hierarchy
  - Link and scope correctness
  - Responsive / mobile-ish

## Read-only Repo Verification
- `operatorGuidance` is produced in `apps/platform/app/Support/EnvironmentDashboard/EnvironmentDashboardSummaryBuilder.php` via `operatorGuidance()`. `repo-verifiziert`
- Provider Blocker priority is enforced before review-output guidance by calling `providerOperatorGuidance()` before `reviewOutputOperatorGuidance()`. `repo-verifiziert`
- Review Output guidance is reused from the shared resolution-guidance model through `reviewOutputResolutionCaseForDashboard()`, `ReviewPackOutputResolutionAdapter::fromGuidance()`, and `buildOperatorGuidanceFromCase()`. `repo-verifiziert`
- No-Urgent-Action is produced by `noUrgentOperatorGuidance()` when no provider blocker, review-output case, or recommended action wins priority. `repo-verifiziert`
- Dashboard actions are rendered as navigation links. The top guidance CTA, secondary actions, and header action are URL-based. `ResolutionAction::fromArray()` additionally downgrades unsafe executable actions away from the dashboard context. `repo-verifiziert`
- No direct mutating action was introduced on the dashboard itself. `repo-verifiziert`
- The old recommended-actions rail was consciously demoted in `apps/platform/resources/views/filament/widgets/dashboard/environment-dashboard-overview.blade.php` by removing the chosen guidance action from the rail and rendering the remaining actions in a lower section under `Recommended next actions`. `repo-verifiziert`

## Scenario Results

### Provider blocker
- Scenario: Provider blocker outranks review output
- URL: `http://localhost/admin/workspaces/spec-352-guidance-browser-audit/environments/spec-352-audit-provider-blocker`
- Environment: `Spec 352 Audit Provider Blocker`
- Visible guidance title: `Provider readiness blocks evidence refresh`
- Guidance severity/status: `Blocked`
- Primary reason: `1 application permission(s) are still missing.`
- Impact: `Provider-backed inventory, verification, and reporting flows stay blocked until consent is restored.`
- Primary action: `Review permissions`
- Secondary actions: none inside the guidance card
- Old recommended rail visible? yes
- Does it compete? mildly. The blocker still dominates, but lower cards and extra buttons remain visible in the same scroll segment. `browser-verifiziert`
- Clicked action: `Review permissions`
- Target URL: `http://localhost/admin/workspaces/spec-352-guidance-browser-audit/environments/spec-352-audit-provider-blocker/required-permissions`
- Expected target: Required Permissions
- Actual target: Required Permissions
- Scope preserved? yes
- Workspace preserved? yes
- Environment preserved? yes
- Any 404/500/login redirect? no in the executed retest
- Back path clear? yes
- Console errors? no visible warn/error logs
- Network/server errors? no visible failure surfaced in the executed flow; no dedicated network trace captured
- Screenshot: `specs/352-environment-dashboard-operator-guidance-consolidation/artifacts/screenshots/browser-flow-audit/01-provider-blocker-guidance.png`
- Finding: Provider readiness clearly dominates. Review-output guidance was seeded in the paired test pattern and does not surface as a second main decision here, matching the intended priority. `browser-verifiziert` + `repo-verifiziert`
- Severity: pass with `P2` polish on action density

### Review output guidance
- Scenario: Review output guidance on dashboard
- URL: `http://localhost/admin/workspaces/spec-352-guidance-browser-audit/environments/spec-352-audit-review-output`
- Environment: `Spec 352 Audit Review Output`
- Visible guidance title: `Draft review exists`
- Guidance severity/status: `Blocked`
- Primary reason: `A successor draft review already exists for this released output and is ready for publication. Open the draft review to publish the next governed outcome.`
- Impact: `The next review cycle is already in progress. Open the draft review and publish it when you are ready to replace the prior released review.`
- Primary action: `Open draft review`
- Secondary actions:
  - `Inspect review blockers`
  - `Open evidence basis`
  - `Open operation proof`
- Old recommended rail visible? yes
- Does it compete? partially. The dominant CTA is still obvious, but the page shows a duplicated top-right primary CTA, three inline secondary links, and further rail buttons below. `browser-verifiziert`
- Clicked action: `Open draft review`
- Target URL: `http://localhost/admin/workspaces/33/environments/spec-352-audit-review-output/environment-reviews/31`
- Expected target: Draft review detail
- Actual target: Draft review detail
- Scope preserved? yes
- Workspace preserved? yes
- Environment preserved? yes
- Any 404/500/login redirect? no
- Back path clear? yes
- Console errors? no visible warn/error logs
- Network/server errors? no visible failure surfaced in the executed flow; no dedicated network trace captured
- Screenshot: `specs/352-environment-dashboard-operator-guidance-consolidation/artifacts/screenshots/browser-flow-audit/03-review-output-guidance.png`
- Finding: Review-output guidance is correctly sourced from the shared resolution-guidance stack, and the browser flow exercised the `Open draft review` path successfully. This audit did not browser-exercise the alternative `Published with limitations` copy variant. `browser-verifiziert` for the successor-draft path, `repo-verifiziert` for the adapter reuse
- Severity: pass with `P2` polish on hierarchy density

### No urgent action
- Scenario: No urgent action
- URL: `http://localhost/admin/workspaces/spec-352-guidance-browser-audit/environments/spec-352-audit-no-urgent`
- Environment: `Spec 352 Audit No Urgent Action`
- Visible guidance title: `No urgent operator action`
- Guidance severity/status: `Calm`
- Primary reason: `No immediate environment blocker is visible.`
- Impact: `Current findings, permissions, recovery posture, and recent operations do not show an urgent follow-up path.`
- Primary action: `Review environment`
- Secondary actions: none inside the guidance card
- Old recommended rail visible? yes
- Does it compete? no. The rail collapses into a quiet informational state rather than another action stack. `browser-verifiziert`
- Clicked action: `Review environment`
- Target URL: `http://localhost/admin/workspaces/33/environments/spec-352-audit-no-urgent/environment-reviews`
- Expected target: Environment review index
- Actual target: Environment review index
- Scope preserved? yes
- Workspace preserved? yes
- Environment preserved? yes
- Any 404/500/login redirect? no
- Back path clear? yes
- Console errors? no visible warn/error logs
- Network/server errors? no visible failure surfaced in the executed flow; no dedicated network trace captured
- Screenshot: `specs/352-environment-dashboard-operator-guidance-consolidation/artifacts/screenshots/browser-flow-audit/05-no-urgent-action.png`
- Finding: The calm state reads as intentional, not empty. Supporting signals remain usable, and the page still offers a neutral next step. `browser-verifiziert`
- Severity: pass

### Secondary action hierarchy
- Scenario: Secondary actions hierarchy
- URL: `http://localhost/admin/workspaces/spec-352-guidance-browser-audit/environments/spec-352-audit-review-output`
- Environment: `Spec 352 Audit Review Output`
- Visible guidance title: `Draft review exists`
- Guidance severity/status: `Blocked`
- Primary reason: same as review-output scenario
- Impact: same as review-output scenario
- Primary action: `Open draft review`
- Secondary actions: three text links below the primary button, plus lower recommended-action cards
- Old recommended rail visible? yes
- Does it compete? yes, mildly. The operator can still identify the next step within five seconds, but the visual system still presents more action affordances than necessary for a decision-first surface. `browser-verifiziert`
- Clicked action: none for this hierarchy-only observation
- Target URL: n/a
- Scope preserved? n/a
- Console errors? no visible warn/error logs
- Network/server errors? no visible failure surfaced in the executed flow; no dedicated network trace captured
- Screenshot: `specs/352-environment-dashboard-operator-guidance-consolidation/artifacts/screenshots/browser-flow-audit/06-secondary-actions-hierarchy.png`
- Finding: The old recommended rail is demoted, but not yet fully quiet. The page still feels busier than the single-case operator-start goal. `browser-verifiziert` + `repo-verifiziert`
- Severity: `P2`

### Link/scope correctness
- Provider blocker:
  - From URL: `http://localhost/admin/workspaces/spec-352-guidance-browser-audit/environments/spec-352-audit-provider-blocker`
  - Clicked label: `Review permissions`
  - Target URL: `http://localhost/admin/workspaces/spec-352-guidance-browser-audit/environments/spec-352-audit-provider-blocker/required-permissions`
  - Expected target: Required Permissions
  - Actual target: Required Permissions
  - Workspace preserved? yes
  - Environment preserved? yes
  - Any 404/500/login redirect? no
  - Back path clear? yes
  - Classification: `browser-verifiziert`
- Review output:
  - From URL: `http://localhost/admin/workspaces/spec-352-guidance-browser-audit/environments/spec-352-audit-review-output`
  - Clicked label: `Open draft review`
  - Target URL: `http://localhost/admin/workspaces/33/environments/spec-352-audit-review-output/environment-reviews/31`
  - Expected target: draft review detail
  - Actual target: draft review detail
  - Workspace preserved? yes
  - Environment preserved? yes
  - Any 404/500/login redirect? no
  - Back path clear? yes
  - Classification: `browser-verifiziert`
- No urgent action:
  - From URL: `http://localhost/admin/workspaces/spec-352-guidance-browser-audit/environments/spec-352-audit-no-urgent`
  - Clicked label: `Review environment`
  - Target URL: `http://localhost/admin/workspaces/33/environments/spec-352-audit-no-urgent/environment-reviews`
  - Expected target: environment review index
  - Actual target: environment review index
  - Workspace preserved? yes
  - Environment preserved? yes
  - Any 404/500/login redirect? no
  - Back path clear? yes
  - Classification: `browser-verifiziert`

### Responsive check
- Scenarios checked:
  - Provider blocker at narrow width
  - Review output at narrow width
- Screenshots:
  - `specs/352-environment-dashboard-operator-guidance-consolidation/artifacts/screenshots/browser-flow-audit/07-mobile-provider-blocker.png`
  - `specs/352-environment-dashboard-operator-guidance-consolidation/artifacts/screenshots/browser-flow-audit/08-mobile-review-output.png`
- Result: the guidance card remains readable, the primary CTA stays visible, and the stacked layout avoids obvious horizontal overflow. `browser-verifiziert`
- Residual concern: the same duplicated CTA + extra lower actions create more scroll weight on small screens than strictly necessary. `browser-verifiziert`
- Severity: `P2`

## Screenshot Index
| Scenario | Screenshot | Notes |
| --- | --- | --- |
| Provider blocker guidance | `specs/352-environment-dashboard-operator-guidance-consolidation/artifacts/screenshots/browser-flow-audit/01-provider-blocker-guidance.png` | Dominant blocker card |
| Provider blocker target | `specs/352-environment-dashboard-operator-guidance-consolidation/artifacts/screenshots/browser-flow-audit/02-provider-blocker-target.png` | Required permissions target |
| Review output guidance | `specs/352-environment-dashboard-operator-guidance-consolidation/artifacts/screenshots/browser-flow-audit/03-review-output-guidance.png` | Shared review-output guidance surfaced on dashboard |
| Review output target | `specs/352-environment-dashboard-operator-guidance-consolidation/artifacts/screenshots/browser-flow-audit/04-review-output-target.png` | Draft review target |
| No urgent action | `specs/352-environment-dashboard-operator-guidance-consolidation/artifacts/screenshots/browser-flow-audit/05-no-urgent-action.png` | Calm fallback |
| Secondary actions hierarchy | `specs/352-environment-dashboard-operator-guidance-consolidation/artifacts/screenshots/browser-flow-audit/06-secondary-actions-hierarchy.png` | Action-density assessment |
| Mobile provider blocker | `specs/352-environment-dashboard-operator-guidance-consolidation/artifacts/screenshots/browser-flow-audit/07-mobile-provider-blocker.png` | Narrow-width stack |
| Mobile review output | `specs/352-environment-dashboard-operator-guidance-consolidation/artifacts/screenshots/browser-flow-audit/08-mobile-review-output.png` | Narrow-width stack |

## Findings

### P0 Blockers
- None observed in the executed browser flows.

### P1 High
- None observed in the executed browser flows.

### P2 Medium
- Blocked states still show more action weight than the spec intent suggests. The duplicated primary CTA and still-visible lower recommended-action buttons dilute the otherwise clear dominant case.
- The helper line `No single repo-real follow-up is currently available.` conflicts with the presence of a concrete CTA, and in the review-output state conflicts with visible secondary links as well.

### P3 Polish
- Review and calm targets use a numeric workspace segment (`/workspaces/33/...`) rather than the slug route used by the dashboard URL. Scope still resolves correctly, so this is consistency polish rather than a functional defect.

## Productization Assessment
- Decision-first quality: mostly good. The operator can identify the top case quickly in all tested states. `browser-verifiziert`
- Next-action clarity: good on destination correctness, slightly noisier than ideal on action count. `browser-verifiziert`
- Priority correctness: Provider Blocker outranks Review Output in code and in the exercised blocker scenario. `repo-verifiziert` + `browser-verifiziert`
- Scope correctness: workspace and environment scope held across all executed primary CTA paths. `browser-verifiziert`
- UI density: improved versus a flat recommended-actions rail, but still not fully quiet in blocked states. `browser-verifiziert`
- Resolve vs dashboard overview balance: healthy overall. The dashboard points to deeper operational surfaces instead of trying to resolve issues inline. `browser-verifiziert` + `repo-verifiziert`

## Recommended Fix Scope
- Must fix before close:
  - Reduce action density in blocked states so the dashboard presents one obvious next step and quieter supporting actions.
  - Replace or remove the contradictory helper copy under the guidance CTA.
- Can defer:
  - Route-format consistency between slug-based dashboard URLs and numeric workspace target URLs.
- Should not change:
  - Provider-over-review priority order
  - Navigation-only dashboard action model
  - Calm-state fallback structure
  - Reuse of shared review-output resolution guidance

## Final Recommendation
- Close Spec 352? not yet
- Patch before close? yes
- Next suggested spec? none implied by this audit; the remaining work is a focused polish patch on hierarchy and helper copy, not a new feature spec