feat: provider access hardening (RBAC write gate) #132

Merged
ahmido merged 3 commits from 108-provider-access-hardening into dev 2026-02-23 00:49:38 +00:00
Owner

Implements provider access hardening for Intune write operations:

  • RBAC-based write gate with configurable staleness thresholds
  • Gate enforced at restore start and in jobs (execute + assignments)
  • UI affordances: disabled rerun action, tenant RBAC status card, refresh RBAC action
  • Audit logging for blocked writes
  • Ops UX label: rbac.health_check now displays as “RBAC health check”
  • Adds/updates Pest tests and SpecKit artifacts for feature 108

Notes:

  • Filament v5 / Livewire v4 compliant.
  • Destructive actions require confirmation.
  • Assets: no new global assets.

Tested:

  • vendor/bin/sail artisan test --compact (suite previously green) + focused OpsUx tests for OperationCatalog labels.
  • vendor/bin/sail bin pint --dirty.
Implements provider access hardening for Intune write operations: - RBAC-based write gate with configurable staleness thresholds - Gate enforced at restore start and in jobs (execute + assignments) - UI affordances: disabled rerun action, tenant RBAC status card, refresh RBAC action - Audit logging for blocked writes - Ops UX label: `rbac.health_check` now displays as “RBAC health check” - Adds/updates Pest tests and SpecKit artifacts for feature 108 Notes: - Filament v5 / Livewire v4 compliant. - Destructive actions require confirmation. - Assets: no new global assets. Tested: - `vendor/bin/sail artisan test --compact` (suite previously green) + focused OpsUx tests for OperationCatalog labels. - `vendor/bin/sail bin pint --dirty`.
ahmido added 2 commits 2026-02-23 00:20:42 +00:00
Implements RBAC-based write gating for Intune restore flows, UI affordances, and audit logging; adds tests and specs.
ahmido added 1 commit 2026-02-23 00:22:52 +00:00
ahmido merged commit 0dc79520a4 into dev 2026-02-23 00:49:38 +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#132
No description provided.