## Summary
Implements and polishes the Platform Ops Runbooks feature (Spec 113) — the operator control plane for safe backfills and data repair from `/system`.
## Changes
### UX Polish (Phase 7 — US4)
- **Filament-native components**: Rewrote `runbooks.blade.php` and `view-run.blade.php` using `<x-filament::section>` instead of raw Tailwind div cards. Cards now render correctly with Filament's built-in borders, shadows and dark mode.
- **System panel theme**: Created `resources/css/filament/system/theme.css` and registered `->viteTheme()` on `SystemPanelProvider`. The system panel previously had no theme CSS registered — Tailwind utility classes weren't compiled for its views, causing the warning icon SVG to expand to full container size.
- **Live scope selector**: Added `->live()` to the scope `Radio` field so "Single tenant" immediately reveals the tenant search dropdown without requiring a Submit first.
### Core Feature (Phases 1–6, previously shipped)
- `/system/ops/runbooks` — runbook catalog, preflight, run with typed confirmation + reason
- `/system/ops/runs` — run history table with status/outcome badges
- `/system/ops/runs/{id}` — run detail view with summary counts, failures, collapsible context
- `FindingsLifecycleBackfillRunbookService` — preflight + execution logic
- AllowedTenantUniverse — scopes tenant picker to non-platform tenants only
- RBAC: `platform.ops.view`, `platform.runbooks.view`, `platform.runbooks.run`, `platform.runbooks.findings.lifecycle_backfill`
- Rate-limited `/system/login` (10/min per IP+username)
- Distinct session cookie for `/system` isolation
## Test Coverage
- 16 tests / 141 assertions — all passing
- Covers: page access, RBAC, preflight, run dispatch, scope selector, run detail, run list
## Checklist
- [x] Filament v5 / Livewire v4 compliant
- [x] Provider registered in `bootstrap/providers.php`
- [x] Destructive actions require confirmation (`->requiresConfirmation()`)
- [x] System panel theme registered (`viteTheme`)
- [x] Pint clean
- [x] Tests pass
Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #137
36 lines
1.0 KiB
Markdown
36 lines
1.0 KiB
Markdown
# Quickstart — Spec 113 (Operator Runbooks)
|
||
|
||
## Prereqs
|
||
- Docker + Laravel Sail
|
||
|
||
## Boot the app
|
||
- `vendor/bin/sail up -d`
|
||
- `vendor/bin/sail composer install`
|
||
- `vendor/bin/sail artisan migrate`
|
||
|
||
## Seed a platform operator
|
||
- `vendor/bin/sail artisan db:seed --class=PlatformUserSeeder`
|
||
|
||
This creates:
|
||
- Workspace: `default`
|
||
- Tenant: `platform` (used for platform-plane audit context)
|
||
- PlatformUser: `operator@tenantpilot.io` / password `password`
|
||
|
||
## Open the System panel
|
||
- Visit `/system` and login as the platform operator.
|
||
|
||
## Run the findings lifecycle backfill
|
||
1. Go to `/system/ops/runbooks`
|
||
2. Select scope (All tenants or Single tenant)
|
||
3. Run preflight
|
||
4. Confirm and start
|
||
5. Use “View run” to monitor progress
|
||
|
||
## CLI (existing)
|
||
- Tenant-scoped backfill (existing behavior):
|
||
- `vendor/bin/sail artisan tenantpilot:findings:backfill-lifecycle --tenant={tenant_id|external_id}`
|
||
|
||
## Notes
|
||
- In production-like environments, `/admin` must not expose maintenance/backfill actions.
|
||
- If UI changes don’t show up, run `vendor/bin/sail npm run dev`.
|