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

feat: add findings intake queue and stabilize follow-up regressions #260

Merged
ahmido merged 2 commits from 222-findings-intake-team-queue into dev 2026-04-21 22:54:09 +00:00
Conversation 0 Commits 2 Files Changed 24 +3173 -36
ahmido commented 2026-04-21 22:51:34 +00:00
Owner
Copy Link

Summary

  • add the new admin findings intake queue at /admin/findings/intake with fixed Unassigned and Needs triage views, tenant-safe filtering, claim flow, and continuity into tenant finding detail and My Findings
  • add Spec 222 artifacts (spec, plan, tasks, research, data model, quickstart, contract, checklist) and register the new admin page
  • fix follow-up regressions uncovered during full-suite validation around findings action-surface declarations, findings list default columns, provider-blocked run messaging, operation catalog aliases, and workspace overview query volume

Validation

  • cd apps/platform && ./vendor/bin/sail bin pint --dirty --format agent
  • cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Feature/Findings/FindingsIntakeQueueTest.php tests/Feature/Authorization/FindingsIntakeAuthorizationTest.php tests/Feature/Findings/FindingsClaimHandoffTest.php
  • cd apps/platform && ./vendor/bin/sail artisan test --compact

Notes

  • Filament remains on v5 with Livewire v4-compatible patterns
  • provider registration remains unchanged in apps/platform/bootstrap/providers.php
  • no new assets or schema changes are introduced
## Summary - add the new admin findings intake queue at `/admin/findings/intake` with fixed `Unassigned` and `Needs triage` views, tenant-safe filtering, claim flow, and continuity into tenant finding detail and `My Findings` - add Spec 222 artifacts (`spec`, `plan`, `tasks`, `research`, `data model`, `quickstart`, contract, checklist) and register the new admin page - fix follow-up regressions uncovered during full-suite validation around findings action-surface declarations, findings list default columns, provider-blocked run messaging, operation catalog aliases, and workspace overview query volume ## Validation - `cd apps/platform && ./vendor/bin/sail bin pint --dirty --format agent` - `cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Feature/Findings/FindingsIntakeQueueTest.php tests/Feature/Authorization/FindingsIntakeAuthorizationTest.php tests/Feature/Findings/FindingsClaimHandoffTest.php` - `cd apps/platform && ./vendor/bin/sail artisan test --compact` ## Notes - Filament remains on v5 with Livewire v4-compatible patterns - provider registration remains unchanged in `apps/platform/bootstrap/providers.php` - no new assets or schema changes are introduced
ahmido added 1 commit 2026-04-21 22:51:35 +00:00
feat: add findings intake queue and stabilize follow-up regressions
Some checks failed
PR Fast Feedback / fast-feedback (pull_request) Failing after 49s
Details
a2e855bd81
ahmido added 1 commit 2026-04-21 22:53:39 +00:00
merge: resolve dev into 222-findings-intake-team-queue
Some checks failed
PR Fast Feedback / fast-feedback (pull_request) Failing after 47s
Details
b1af4af25f
ahmido merged commit 712576c447 into dev 2026-04-21 22:54:09 +00:00
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#260
No description provided.
Delete Branch "222-findings-intake-team-queue"

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?