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

feat: harden operation run detail hierarchy and Filament UI governance #195

Open
ahmido wants to merge 2 commits from 164-run-detail-hardening into dev
pull from: 164-run-detail-hardening
merge into: ahmido:dev
Conversation 0 Commits 2 Files Changed 39 +2852 -540
ahmido commented 2026-03-26 15:44:25 +00:00
Owner
Copy Link

Summary

  • harden the canonical operation run detail page into a decision-first surface with clearer hierarchy, grouped supporting context, and diagnostics pushed later
  • add the new enterprise-detail decision zone, regroup supporting cards, and replace remaining ad-hoc semantic UI with Filament-native components on the touched surfaces
  • improve baseline compare evidence-gap presentation and related operation detail rendering
  • add Spec 164 artifacts for the run-detail hardening work
  • amend the constitution to v1.13.0 with UI-FIL-001 for Filament-native-first admin/operator UI governance and propagate that rule into the Spec Kit templates and product docs

Testing

  • vendor/bin/sail artisan test --compact tests/Feature/Filament/OperationRunBaselineTruthSurfaceTest.php tests/Feature/Filament/OperationRunEnterpriseDetailPageTest.php

Notes

  • branch is already pushed and was in sync with origin before PR creation
  • this PR targets dev from 164-run-detail-hardening
## Summary - harden the canonical operation run detail page into a decision-first surface with clearer hierarchy, grouped supporting context, and diagnostics pushed later - add the new enterprise-detail decision zone, regroup supporting cards, and replace remaining ad-hoc semantic UI with Filament-native components on the touched surfaces - improve baseline compare evidence-gap presentation and related operation detail rendering - add Spec 164 artifacts for the run-detail hardening work - amend the constitution to v1.13.0 with `UI-FIL-001` for Filament-native-first admin/operator UI governance and propagate that rule into the Spec Kit templates and product docs ## Testing - `vendor/bin/sail artisan test --compact tests/Feature/Filament/OperationRunBaselineTruthSurfaceTest.php tests/Feature/Filament/OperationRunEnterpriseDetailPageTest.php` ## Notes - branch is already pushed and was in sync with origin before PR creation - this PR targets `dev` from `164-run-detail-hardening`
ahmido added 2 commits 2026-03-26 15:44:27 +00:00
This pull request has changes conflicting with the target branch.
  • .github/agents/copilot-instructions.md
  • tests/Feature/Filament/OperationRunBaselineTruthSurfaceTest.php
View command line instructions.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin 164-run-detail-hardening:164-run-detail-hardening
git checkout 164-run-detail-hardening
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#195
No description provided.
Delete Branch "164-run-detail-hardening"

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?