ahmido/TenantAtlas
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity
platform-dev
TenantAtlas/specs/317-legacy-tenant-environment-context-cleanup/checklists/requirements.md
ahmido b159dacd36 feat: clean up legacy tenant environment context (#372) 
## Summary
- remove legacy tenant-scoped routing and middleware paths in favor of the current environment/workspace context flow
- update Filament pages and resources to use the cleaned-up admin surface and environment filter context
- add the related spec 317 artifacts and targeted tests for environment filter state and legacy context cleanup

## Testing
- not run as part of this commit/push/PR workflow

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #372
2026-05-16 18:25:36 +00:00

3.5 KiB
Raw Permalink Blame History

Specification Quality Checklist: Legacy Tenant / Environment Context Cleanup

Purpose: Validate preparation completeness and quality before implementation Created: 2026-05-16 Feature: spec.md

Candidate Selection

  • CHK001 The selected candidate was directly supplied by the user as Spec 317.
  • CHK002 The selected candidate is not an existing completed spec package.
  • CHK003 Related Specs 313, 314, 315, and 316 are treated as completed historical context and not rewritten.
  • CHK004 The candidate aligns with explicit follow-up notes in Specs 314, 315, and 316.
  • CHK005 The scope is narrowed to legacy Tenant platform-context cleanup and provider-boundary Tenant preservation.
  • CHK006 Durable browser no-drift infrastructure is deferred to Spec 318.

Content Quality

  • CHK007 spec.md exists.
  • CHK008 plan.md exists.
  • CHK009 tasks.md exists.
  • CHK010 Spec Candidate Check is completed.
  • CHK011 Functional requirements are testable and unambiguous.
  • CHK012 Acceptance criteria include inventory, allowlist, query cleanup, helper/class cleanup, route guard, UI copy cleanup, docs cleanup, regression tests, and browser smoke.
  • CHK013 Provider-boundary Tenant terminology is explicitly preserved.
  • CHK014 Hard cutover/no-compatibility posture is explicit.

Repository Alignment

  • CHK015 Laravel, Filament, Livewire, Pest, and PostgreSQL context is recorded.
  • CHK016 Provider registration location remains apps/platform/bootstrap/providers.php.
  • CHK017 Filament v5 / Livewire v4 compliance is recorded.
  • CHK018 Global search behavior is not intentionally changed and has a verification task if resources are touched.
  • CHK019 Destructive actions are not added or changed and have a verification task if touched.
  • CHK020 Asset strategy is unchanged and no new filament:assets requirement is planned.
  • CHK021 Likely affected repo surfaces are named in the plan.
  • CHK022 No migration, seeder, package, env var, queue, scheduler, or storage change is planned by default.

Artifact Requirements

  • CHK023 legacy-inventory.md is required as an implementation artifact and assigned to tasks.
  • CHK024 tenant-usage-allowlist.md is required as an implementation artifact and assigned to tasks.
  • CHK025 Classification values for inventory entries are specified.
  • CHK026 Browser screenshot artifact path is specified.
  • CHK027 Historical completed specs are protected from preparation rewrite.

Test and Validation Readiness

  • CHK028 Static legacy guard is required.
  • CHK029 Workspace hub legacy query alias guard is required.
  • CHK030 Filament tenant / remembered Tenant fallback guard is required.
  • CHK031 Route guard for /admin/t and TenantPanelProvider is required.
  • CHK032 UI copy guard/browser verification is required.
  • CHK033 Spec 314, 315, and 316 regressions are required.
  • CHK034 git diff --check and formatting/static checks are required.

Open Questions

  • CHK035 No blocking preparation questions remain.
  • CHK036 Ambiguous implementation occurrences are handled through needs_product_decision inventory classification instead of guessing.

Review Outcome

  • CHK037 Candidate Selection Gate passes.
  • CHK038 Spec Readiness Gate passes for preparation.
  • CHK039 No application implementation was performed during preparation.