ahmido
5248654691
## Summary - retire remaining legacy tenant-panel runtime assumptions in the Filament admin runtime and route resolution paths - centralize canonical admin environment context handling for shared surfaces instead of relying on deprecated `tenant` panel behavior - harden guard coverage so legacy `/admin/t` and `/admin/tenants` route families cannot regress - update scoped navigation, drillthrough, reference-link, and global-search tests to use the admin panel environment runtime - add the Spec 304 package under `specs/304-tenant-panel-dead-code-retirement/` and document the rollout in the product ledger ## Test Coverage Updated - `AdminSharedSurfacePanelParityTest` - `NoActiveTenantResourceRoutesTest` - `NoLegacyTenantPanelRuntimeTest` - `AdminTenantResolverGuardTest` - `PolicyVersionResolvedReferenceLinksTest` - `EntraGroupGlobalSearchScopeTest` - `OperationsDashboardDrillthroughTest` ## Runtime Notes - remains compliant with Filament v5 on Livewire v4 - no provider registration changes; provider registration location remains `apps/platform/bootstrap/providers.php` - no new globally searchable resource was introduced; existing scoped search assertions were updated only - no destructive actions were added or changed - no asset registration changes; deploy posture for `cd apps/platform && php artisan filament:assets` is unchanged ## Validation - updated tests and docs/spec artifacts were committed in this branch - tests were not re-run in this turn Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #359 |
||
|---|---|---|
| .. | ||
| architecture | ||
| audits | ||
| product | ||
| research | ||
| security | ||
| strategy | ||
| ui | ||
| architecture.svg | ||
| HANDOVER.md | ||
| PERMISSIONS.md | ||
| PROJECT_SUMMARY.md | ||
| README.md | ||
TenantPilot Documentation Index
Status: Active
Last reviewed: 2026-04-30
Use for: Navigating current documentation sources and understanding how to maintain them with low overhead
Do not use for: Assuming any document is implementation truth without repo verification
Current Source of Truth
docs/product/roadmap.md- current product roadmap and prioritization contextdocs/product/spec-candidates.md- active spec candidate queuedocs/product/principles.md- product and architecture principlesdocs/strategy/product-vision.md- long-term product visiondocs/strategy/domain-coverage.md- domain and coverage strategy
Product Operations
docs/product/discoveries.mddocs/product/implementation-ledger.mddocs/product/prompts/docs/product/standards/
Technical Research
docs/research/
UI Standards
docs/ui/
Audits
docs/audits/
Security And Access References
docs/PERMISSIONS.mddocs/security/
Historical Or Superseded Material
docs/audits/archive/- audit-derived candidate documents that are marked
Historical,Superseded, orNeeds Review
Lightweight Maintenance Model
- Keep only the current source-of-truth documents actively maintained.
- Update a document when the underlying roadmap, policy, or decision actually changes.
- Mark older material with status headers instead of rewriting it to feel current.
- Prefer archive or superseded markers over deletion.
- Verify implementation claims against repo code, specs, and tests.
Rules For Agents
- Treat docs as guidance, not implementation truth.
- Verify implementation claims against repo code.
- Specs are not automatically implemented.
- Tests are not automatically executed.
- Historical audits may be outdated.
- Prefer current roadmap and spec-candidates for prioritization.