TenantAtlas/specs/092-legacy-purge-final/quickstart.md
ahmido 5770c7b76b Spec 092: Legacy Purge (runs/routes/UI/test shims) (#110)
Implements Spec 092 legacy purge.

Key changes:
- Remove legacy Inventory landing page + view; link Inventory entry directly to Inventory Items.
- Update Drift landing copy to "operation runs"; remove URL heuristic from context bar.
- Remove legacy redirect shim route and assert 404 for old bookmarks.
- Staged job payload change: remove legacy ctor arg; keep legacy field for deserialization compatibility; new payload omits field.
- Remove legacy notification artifact.
- Remove legacy test shim + update tests; strengthen guard suite with scoped exception for job compat field.
- Add spec/plan/tasks/checklist artifacts under specs/092-legacy-purge-final.

Tests:
- Focused Pest suite for guards, legacy routes, redirect behavior, job compatibility, drift copy.
- Pint run: `vendor/bin/sail bin pint --dirty`.

Notes:
- Deploy B final removal of `backupScheduleRunId` should occur only after the compatibility window defined in the spec.

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #110
2026-02-14 18:43:56 +00:00

1.3 KiB

Quickstart — Legacy Purge (Runs / Routes / UI / Test Shims)

Date: 2026-02-14

Local dev

  • Start containers: vendor/bin/sail up -d
  • Run formatting (required): vendor/bin/sail bin pint --dirty

Targeted verification (suggested)

Legacy endpoints

  • Run the legacy endpoints tests:
    • vendor/bin/sail artisan test --compact tests/Feature/Operations/LegacyRunRoutesNotFoundTest.php
    • If updated as part of this spec: vendor/bin/sail artisan test --compact tests/Feature/078/TenantListRedirectTest.php

UI copy and navigation

  • Verify Drift landing copy contains “operation runs” and does not contain “inventory sync runs”.
  • Verify Inventory navigation lands on Inventory Items without passing through a redirect-only landing page.

Guard suite

  • Run the guard tests added/updated for this spec to ensure legacy identifiers cannot be reintroduced.

Deployment notes (staged rollout)

Deploy A (compat)

  • Goal: stop emitting the legacy job field while keeping deserialization compatible.
  • Run migrations if any (this feature should not include migrations).

Deploy B (final purge)

  • Goal: remove the legacy field/property entirely once queues are drained.

Operational note: coordinate the compatibility window with queue retention / worker restarts to reduce the chance of old payloads persisting.