ahmido/TenantAtlas
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity
platform-dev
TenantAtlas/specs/314-workspace-hub-navigation-context-contract/checklists/requirements.md
ahmido d85ef4cc1c Spec 314: enforce workspace hub navigation context contract (#369) 
## Summary
- add a shared workspace hub registry for canonical workspace-scoped navigation entry
- keep sidebar and global workspace hub URLs free of inherited environment query and filter state
- add focused feature and browser coverage for workspace hub shell and data-scope contracts

## Validation
- 54 focused feature tests passed (205 assertions)
- 1 browser smoke test passed (361 assertions)
- `cd apps/platform && ./vendor/bin/sail bin pint --dirty --format agent`
- `git diff --check`

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #369
2026-05-16 09:54:29 +00:00

3.9 KiB
Raw Permalink Blame History

Requirements Checklist: Workspace Hub Navigation Context Contract

Purpose: Preparation-readiness checklist for Spec 314. Scope: Spec Kit artifacts only. Runtime implementation runs later.

Candidate Selection Gate

  • CHK001 The selected candidate was directly supplied by the user as Spec 314.
  • CHK002 The candidate is not an existing completed spec package.
  • CHK003 Related Specs 311, 312, and 313 are treated as completed historical context, not rewritten.
  • CHK004 The candidate aligns with Spec 313 recommended remediation order.
  • CHK005 The scope is narrowed to sidebar/global workspace hub navigation context hardening.
  • CHK006 Environment CTA standardization, universal clear-filter behavior, legacy cleanup, and durable browser guard work are deferred to Specs 315-318.
  • CHK007 The product-candidate queue note about no safe automatic target is respected because this is an explicit manual promotion from Spec 313 evidence.

Spec Readiness

  • CHK008 spec.md exists.
  • CHK009 plan.md exists.
  • CHK010 tasks.md exists.
  • CHK011 Spec Candidate Check is completed.
  • CHK012 Functional requirements are behavior-oriented and testable.
  • CHK013 Acceptance criteria cover registry, sidebar URLs, shell/data scope, persisted filter safety, critical pages, tests, and browser verification.
  • CHK014 Hard cutover posture is explicit.
  • CHK015 No backwards compatibility layer or legacy sidebar/global query alias support is allowed.
  • CHK016 Decision Register clean workspace URL behavior is specified as in scope.

Repo Alignment

  • CHK017 The plan identifies WorkspaceSidebarNavigation, AdminPanelProvider, TenantPageCategory, NavigationScope, OperateHubShell, WorkspaceContext, and CanonicalAdminTenantFilterState.
  • CHK018 The plan identifies critical pages/resources: Provider Connections, Finding Exceptions Queue, Operations, Decision Register, Customer Review Workspace, Review Register, Evidence Overview, Governance Inbox, Audit Log, and Alerts.
  • CHK019 Filament v5 / Livewire v4 compliance is stated.
  • CHK020 Provider registration location remains apps/platform/bootstrap/providers.php; no provider registration move is planned.
  • CHK021 Global search behavior is not modified.
  • CHK022 Destructive actions are not added or changed.
  • CHK023 Asset strategy is unchanged unless implementation unexpectedly registers Filament assets.

Registry and Scope Readiness

  • CHK024 Workspace hub registry contents are listed.
  • CHK025 Explicit exclusions are listed for environment-owned pages, Stored Reports environment route, and Support Request action-only surface.
  • CHK026 The forbidden sidebar/global query params are named.
  • CHK027 Environment-like persisted filter keys are named.
  • CHK028 The registry proportionality review is completed.

Test and Browser Readiness

  • CHK029 Required Pest Feature/Livewire tests are named.
  • CHK030 Focused Browser smoke scope is named.
  • CHK031 Planned validation commands are listed.
  • CHK032 Tests are scoped to contract behavior and do not require a broad suite rebaseline.
  • CHK033 Browser verification repeats focused Spec 313 critical flows.

Safety

  • CHK034 No migration, seeder, package, env var, queue, scheduler, storage, or asset-bundle work is planned.
  • CHK035 Existing workspace and Managed Environment RBAC/isolation semantics remain required.
  • CHK036 Existing Provider Connections credential-adjacent action authorization remains untouched.
  • CHK037 The tasks include no-compatibility validation.
  • CHK038 The tasks require git diff --check and changed-file review.

Review Outcome

  • CHK039 Review outcome class: acceptable-special-case.
  • CHK040 Workflow outcome: keep.
  • CHK041 Candidate Selection Gate passes.
  • CHK042 Spec Readiness Gate passes for preparation.