ahmido
8a889a863e
## Summary - add the Spec 323 Tenantial enterprise UI audit foundation package - add the UI/UX audit registry artifacts, templates, and supporting brand context placeholder - update Spec Kit prompts/templates plus PR fast-feedback guardrails for ongoing UI productization coverage ## Scope - docs-first audit foundation only - no runtime Laravel, Filament, Livewire, route, auth, or database behavior changes intended ## Validation - [x] `git diff --check` - [ ] application test suite run ## Notes - primary spec: `specs/323-tenantial-enterprise-ui-audit-foundation/` - this branch also updates `.gitea/pull_request_template.md`, `.gitea/workflows/test-pr-fast-feedback.yml`, and `scripts/check-ui-productization-coverage` to make the coverage gate durable for future UI work Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #383
49 lines
1.9 KiB
Markdown
49 lines
1.9 KiB
Markdown
# UI-014 Restore Runs
|
|
|
|
| Field | Value |
|
|
| --- | --- |
|
|
| Route | `/admin/workspaces/{workspace}/environments/{environment}/restore-runs` |
|
|
| Source | `RestoreRunResource` |
|
|
| Area / scope | Backup / restore / environment |
|
|
| Archetype | Backup / Restore |
|
|
| Design depth | Strategic Surface |
|
|
| Repo truth | repo-verified route; browser blocked |
|
|
| Screenshot | `../screenshots/desktop/ui-014-restore-runs.png` |
|
|
| Browser status | Local Spec 180 fixture returned Forbidden. |
|
|
|
|
## First Five Seconds
|
|
|
|
The browser pass could not evaluate the product page because restore capability/state was unavailable. The route is still strategic because restore is the highest-risk operator workflow in the product.
|
|
|
|
## Productization Review
|
|
|
|
- Decision-first: not evaluated in browser.
|
|
- Evidence-first: restore preview, request, result, and recovery proof must be central.
|
|
- Context: environment-bound route.
|
|
- Customer/auditor safety: high after execution.
|
|
- Diagnostics: raw provider responses must stay secondary.
|
|
|
|
## Information Inventory
|
|
|
|
Expected default content should distinguish restore intent, simulation/preview, validation, requested items, execution state, result truth, and recovery evidence.
|
|
|
|
## Dangerous Actions
|
|
|
|
Restore execution is destructive/high-impact. Target state must include dry-run/preview, explicit confirmation, audit, OperationRun continuity, and post-run evidence.
|
|
|
|
## Scores
|
|
|
|
| IA | Density | User Clarity | Sellability | Disclosure | Hierarchy | DS Fit | A11y | Responsive | Components | UX Writing | Perf |
|
|
| ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: |
|
|
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
|
|
|
|
## Top Issues
|
|
|
|
1. Browser review blocked by local capability/data.
|
|
2. Restore workflow needs individual target mockup and safety review.
|
|
3. Preview/result/evidence truth must be separated visually.
|
|
|
|
## Target Direction
|
|
|
|
P0 restore safety target mockup and implementation-wave smoke with an authorized fixture.
|