feat: finalize customer review workspace consumption (342) #414

Merged
ahmido merged 1 commits from 342-customer-review-workspace-final-consumption-productization into platform-dev 2026-06-01 08:15:12 +00:00
Owner

Summary

  • finalize the existing Customer Review Workspace as a customer-safe first-screen consumption surface
  • lead the page with one review decision card, readiness flow, findings summary, accepted-risk summary, and secondary proof instead of diagnostics-first presentation
  • keep evidence, review-pack, export, audit, and operation proof states explicit and separate so the page does not make false readiness or evidence claims
  • add focused Spec 342 Feature and Browser coverage plus the spec-local truth map, state contract, and screenshot artifacts
  • preserve the existing workspace-wide route with canonical environment_id filtering only and no new portal, backend generation flow, or navigation rewrite

Validation

  • cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Feature/Filament/Spec342CustomerReviewWorkspaceConsumptionTest.php tests/Feature/Reviews/CustomerReviewWorkspacePageTest.php
  • cd apps/platform && ./vendor/bin/sail php vendor/bin/pest tests/Browser/Spec342CustomerReviewWorkspaceConsumptionSmokeTest.php tests/Browser/Reviews/CustomerReviewWorkspaceSmokeTest.php --compact
  • cd apps/platform && ./vendor/bin/sail bin pint --dirty --format agent
  • git diff --check

Notes

  • screenshot artifacts are included under specs/342-customer-review-workspace-final-consumption-productization/artifacts/screenshots/
  • Livewire v4 compliance unchanged
  • Filament provider registration remains in apps/platform/bootstrap/providers.php
  • no globally searchable resource behavior changed in this slice
  • no new destructive action behavior was introduced
  • no new Filament assets; deploy filament:assets posture is unchanged
  • full suite was not run in this turn; validation stayed on the focused Spec 342 slices
## Summary - finalize the existing Customer Review Workspace as a customer-safe first-screen consumption surface - lead the page with one review decision card, readiness flow, findings summary, accepted-risk summary, and secondary proof instead of diagnostics-first presentation - keep evidence, review-pack, export, audit, and operation proof states explicit and separate so the page does not make false readiness or evidence claims - add focused Spec 342 Feature and Browser coverage plus the spec-local truth map, state contract, and screenshot artifacts - preserve the existing workspace-wide route with canonical `environment_id` filtering only and no new portal, backend generation flow, or navigation rewrite ## Validation - `cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Feature/Filament/Spec342CustomerReviewWorkspaceConsumptionTest.php tests/Feature/Reviews/CustomerReviewWorkspacePageTest.php` - `cd apps/platform && ./vendor/bin/sail php vendor/bin/pest tests/Browser/Spec342CustomerReviewWorkspaceConsumptionSmokeTest.php tests/Browser/Reviews/CustomerReviewWorkspaceSmokeTest.php --compact` - `cd apps/platform && ./vendor/bin/sail bin pint --dirty --format agent` - `git diff --check` ## Notes - screenshot artifacts are included under `specs/342-customer-review-workspace-final-consumption-productization/artifacts/screenshots/` - Livewire v4 compliance unchanged - Filament provider registration remains in `apps/platform/bootstrap/providers.php` - no globally searchable resource behavior changed in this slice - no new destructive action behavior was introduced - no new Filament assets; deploy `filament:assets` posture is unchanged - full suite was not run in this turn; validation stayed on the focused Spec 342 slices
ahmido added 1 commit 2026-06-01 07:59:39 +00:00
feat: finalize customer review workspace consumption (342)
Some checks failed
PR Fast Feedback / fast-feedback (pull_request) Failing after 4m1s
b203e050d9
ahmido merged commit bf10645dc3 into platform-dev 2026-06-01 08:15:12 +00:00
Sign in to join this conversation.
No reviewers
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: ahmido/TenantAtlas#414
No description provided.