ahmido 1c27af4f5f spec: add admin surface scope shell context audit (#373 )

## Summary
- add Spec 318 audit artifacts for admin surface scope and shell context consistency after Specs 314-317
- document browser-backed findings for workspace hubs, environment-scoped pages, filtered workspace hubs, and mismatch cases
- capture recommended follow-up specs for baseline compare, baseline ownership, alerts/audit filter contracts, classifier regression coverage, and sidebar scope declarations

## Testing
- not run; analysis-only spec artifacts with no runtime or test code changes

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #373

2026-05-16 18:32:11 +00:00

1.8 KiB

Raw Blame History

Spec 318: Admin Surface Scope and Shell Context Audit

Purpose

This is an analysis-only audit artifact for the Admin Surface Scope and Shell Context consistency work following Specs 314-317. It records browser-backed evidence for reachable TenantPilot admin surfaces and classifies each surface as workspace-scoped hub, environment-scoped page, filtered workspace hub, system/platform scoped page, ambiguous/mixed surface, dead/unreachable surface, or out of scope with reason.

Constraints

Do not modify runtime code.
Do not modify tests.
Do not create migrations.
Do not create commits.
Do not fix findings in this spec.
Audit artifacts, screenshots, matrices, and recommendations may live in this folder only.

Scope

Audited surfaces were discovered from AdminPanelProvider, WorkspaceSidebarNavigation, WorkspaceHubRegistry, AdminSurfaceScope, route definitions, Filament Pages, Filament Resources, Filament Clusters, environment dashboard actions, workspace hub links, and contextual link helpers.

Acceptance Criteria

Every discovered admin surface has a final status or documented blocker.
Browser evidence exists for workspace sidebar, environment sidebar, environment CTA, direct clean URL, direct filtered URL, reload, and back/forward origins where reachable.
Baseline Compare and Decision Register have dedicated findings.
Recommended remediation is split into safe follow-up specs.

Platform Notes

Laravel: 12.52.0.
Filament: 5.2.1.
Livewire: 4.1.4, satisfying the Filament v5 Livewire v4.0+ requirement.
Panel providers are registered in apps/platform/bootstrap/providers.php; AdminPanelProvider is registered there for Laravel 11+/12 style provider registration.
No Filament assets were added or changed in this audit, so no new filament:assets deployment step is introduced.

1.8 KiB Raw Blame History