ahmido
ba7622a158
## Summary\n- Implements the ReviewPublicationResolutionWorkflow for Spec 386.\n- Adds resolution case/step persistence, policies, services, audit action IDs, and Filament integration.\n- Updates specs, UI/UX documentation, screenshots, and Pest coverage.\n\n## Tests\n- Not run during this handoff; branch was already clean and pushed.\n\n## Target\n- Base: platform-dev\n- Head/topic: 386-review-publication-resolution-workflow-v1 Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #457
49 lines
3.5 KiB
Markdown
49 lines
3.5 KiB
Markdown
# UI-101 Review Publication Resolution
|
|
|
|
| Field | Value |
|
|
| --- | --- |
|
|
| Route | `/admin/workspaces/{workspace}/environments/{environment}/environment-reviews/{record}/resolve-publication` |
|
|
| Source | `EnvironmentReviewResource::resolve-publication` |
|
|
| Area / scope | Reviews / environment record workflow |
|
|
| Archetype | Reviews |
|
|
| Design depth | Strategic Surface |
|
|
| Repo truth | browser-verified route; feature-tested |
|
|
| Screenshot | [desktop](../../../specs/386-review-publication-resolution-workflow-v1/artifacts/screenshots/01-resolution-page-desktop.png), [mobile](../../../specs/386-review-publication-resolution-workflow-v1/artifacts/screenshots/02-resolution-page-mobile.png) |
|
|
| Browser status | Browser smoke passed for blocked-review CTA handoff, decision-first resolution page rendering, compact preparation progress, confirmation copy, technical disclosure, and narrow viewport readability. |
|
|
|
|
## First Five Seconds
|
|
|
|
The page should answer five operator questions immediately: can I publish, why not, what is missing, what should I do now, and whether the action publishes automatically.
|
|
|
|
## Productization Review
|
|
|
|
- Decision-first: operator-state page title, blocked reason, missing required reports, next safe action, compact preparation progress, and no-auto-publish copy lead the page.
|
|
- Evidence-first: report, evidence, review, pack, and operation proof remain available without becoming the default workflow source of truth.
|
|
- Context: route is owned by the Environment Review record and remains environment-scoped.
|
|
- Customer/auditor safety: high, because internal remediation details stay in the admin plane and customer workspace does not expose the case.
|
|
- Diagnostics: proof and operation links are available in collapsed technical disclosure, secondary to the guided fix.
|
|
|
|
## Information Inventory
|
|
|
|
Default content shows publication blocked state, required reports, compact preparation progress, the next safe action, what happens after the action, and the back-to-review action. Case status, proof links, operation links, and implementation terms such as report-backed evidence are technical details behind disclosure or normalized out of operator copy.
|
|
|
|
## Dangerous Actions
|
|
|
|
`Cancel resolution` is destructive to the local resolution case only, is demoted into the grouped More action, and requires confirmation plus `ENVIRONMENT_REVIEW_MANAGE`. Step execution is high-impact and uses the owning source action: provider verification or Entra scan for required reports, evidence snapshot generation for evidence, review refresh for composition, review-pack generation for export proof, and a non-publishing return-to-review completion step.
|
|
|
|
## Scores
|
|
|
|
| IA | Density | User Clarity | Sellability | Disclosure | Hierarchy | DS Fit | A11y | Responsive | Components | UX Writing | Perf |
|
|
| ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: |
|
|
| 9 | 8 | 9 | 8 | 9 | 9 | 8 | 8 | 8 | 8 | 9 | 7 |
|
|
|
|
## Top Issues
|
|
|
|
1. Long-running operation states should be rechecked once real queue workers and provider failures are exercised in staging.
|
|
2. Report-step copy may need more specific provider wording if operators repeatedly hit provider-verification prerequisites.
|
|
3. The page intentionally stays sequential in v1; parallel report actions would require a new spec update.
|
|
|
|
## Target Direction
|
|
|
|
Keep this as a subject-owned admin workflow attached to Environment Review. Do not promote it into top-level navigation, a generic workflow resource, global search, or a customer-facing remediation surface.
|