ahmido/TenantAtlas
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity

074-verification-checklist #91

Closed
ahmido wants to merge 3 commits from 074-verification-checklist into dev
pull from: 074-verification-checklist
merge into: ahmido:dev
Conversation 0 Commits 3 Files Changed -
ahmido commented 2026-02-04 23:52:16 +00:00
Owner
Copy Link

PR: 074 — Verification Checklist (DB-only Reports)

Summary
This PR adds a DB-only verification checklist/report system that can be rendered safely in the UI without triggering outbound calls. Verification produces a stored report (sanitized), and the UI provides a viewer for that report.

What’s included
Verification report model + schema (stored, sanitized, safe to render)
Viewer component / support to render reports DB-only in Filament
Badge semantics for verification-related statuses centralized via the badge domain/catalog (no ad-hoc mappings)
Tests (Pest) covering the verification flows and badge mappings
Safety & RBAC notes
UI rendering is DB-only; any external verification work happens in background jobs / service layer, not during page render.
Authorization remains server-enforced; UI affordances are informational only.
Validation
vendor/bin/sail bin pint --dirty
vendor/bin/sail artisan test --compact --no-ansi tests/Feature/Verification tests/Unit/Badges/VerificationBadgesTest.php (14 passed, 95 assertions)
Deployment notes
No special ops steps beyond normal deploy; if assets were registered, ensure php artisan filament:assets is part of deployment (standard Filament v5 practice).
If du willst, passe ich den Body noch an euren PR-Template-Stil an (z.B. “Why / How / Screenshots / Rollout / Risks”).

PR: 074 — Verification Checklist (DB-only Reports) Summary This PR adds a DB-only verification checklist/report system that can be rendered safely in the UI without triggering outbound calls. Verification produces a stored report (sanitized), and the UI provides a viewer for that report. What’s included Verification report model + schema (stored, sanitized, safe to render) Viewer component / support to render reports DB-only in Filament Badge semantics for verification-related statuses centralized via the badge domain/catalog (no ad-hoc mappings) Tests (Pest) covering the verification flows and badge mappings Safety & RBAC notes UI rendering is DB-only; any external verification work happens in background jobs / service layer, not during page render. Authorization remains server-enforced; UI affordances are informational only. Validation vendor/bin/sail bin pint --dirty vendor/bin/sail artisan test --compact --no-ansi tests/Feature/Verification tests/Unit/Badges/VerificationBadgesTest.php (14 passed, 95 assertions) Deployment notes No special ops steps beyond normal deploy; if assets were registered, ensure php artisan filament:assets is part of deployment (standard Filament v5 practice). If du willst, passe ich den Body noch an euren PR-Template-Stil an (z.B. “Why / How / Screenshots / Rollout / Risks”).
ahmido added 3 commits 2026-02-04 23:52:17 +00:00
ahmido closed this pull request 2026-02-05 00:59:11 +00:00

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
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#91
No description provided.
Delete Branch "074-verification-checklist"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?