# Quickstart: Legacy Runs Removal (Spec 087)

**Branch**: `087-legacy-runs-removal`

## Local Dev (Sail)

1) Start containers:

- `vendor/bin/sail up -d`

2) Run migrations:

- `vendor/bin/sail artisan migrate`

3) Run targeted tests (once implementation exists):

- Minimum required pack:
  - `vendor/bin/sail artisan test --compact tests/Feature/Guards/NoLegacyRunsTest.php tests/Feature/Operations/LegacyRunRoutesNotFoundTest.php tests/Feature/Monitoring/MonitoringOperationsTest.php tests/Feature/Drift`
- Backup + directory regressions:
  - `vendor/bin/sail artisan test --compact tests/Feature/BackupScheduling tests/Feature/DirectoryGroups`
- Canonical run flow checks:
  - `vendor/bin/sail artisan test --compact tests/Feature/Inventory/InventorySyncServiceTest.php tests/Feature/Console/PurgeNonPersistentDataCommandTest.php tests/Feature/Console/ReconcileBackupScheduleOperationRunsCommandTest.php`

## Manual Verification Checklist (once implementation exists)

- Inventory sync run appears in Monitoring → Operations and opens via the canonical viewer.
- Entra group sync run appears in Monitoring → Operations and opens via the canonical viewer.
- Backup schedule run/retention/purge each appear in Monitoring → Operations.
- Legacy run URLs return 404 (no redirects):
  - Inventory sync runs resource route
  - Entra group sync runs resource route
  - Backup schedule run history relation manager is removed from schedule detail

## Notes

- Per spec clarifications, no backfill of legacy run history is performed. Only reference migration from legacy IDs to existing `operation_runs` IDs is expected.