ahmido/TenantAtlas
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity
platform-dev
TenantAtlas/specs/293-post-cutover-suite-stabilization/checklists/requirements.md
ahmido 83ab4690d5 fix: stabilize post-cutover suite baseline (#348) 
## Summary
- stabilize the active spec 293 post-cutover suite baseline around the current admin-panel and workspace-first runtime
- align operations, provider, required-permissions, and action-surface expectations to canonical workspace-aware routes
- add the monitoring operations workspace-membership guard and update the spec 293 classification artifacts
- include the browser smoke screenshots captured during verification

## Validation
- `cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Feature/Filament/PanelNavigationSegregationTest.php tests/Feature/ManagedEnvironment/LegacyTenantCoreGuardTest.php`
- `cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Feature/OpsUx/CanonicalViewRunLinksTest.php tests/Feature/OpsUx/OperateHubShellTest.php tests/Feature/OpsUx/FailureSanitizationTest.php tests/Feature/OpsUx/NonLeakageWorkspaceOperationsTest.php`
- `cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Feature/Guards/ActionSurfaceContractTest.php tests/Feature/ProviderConnections/NavigationPlacementTest.php tests/Feature/ProviderConnections/ProviderConnectionListAuthorizationTest.php tests/Feature/Verification/VerificationAuthorizationTest.php`
- `cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Feature/Guards/Spec288NoLegacyRouteAndHelperGuardTest.php tests/Feature/Guards/Spec288ProviderCoreAndRoleAuthorityGuardTest.php tests/Feature/Guards/AdminWorkspaceRoutesGuardTest.php tests/Feature/Guards/ProviderBoundaryPlatformCoreGuardTest.php tests/Feature/ProviderConnections/LegacyRedirectTest.php tests/Feature/ManagedEnvironment/LegacyTenantCoreGuardTest.php tests/Feature/Spec080WorkspaceManagedTenantAdminMigrationTest.php tests/Feature/Rbac/ProviderConnectionWorkspaceFirstPolicyTest.php tests/Feature/Filament/ManagedEnvironmentAccessScopeManagementTest.php tests/Feature/Guards/BrowserLaneIsolationTest.php tests/Feature/Guards/CiLaneFailureClassificationContractTest.php tests/Feature/Guards/CiHeavyBrowserWorkflowContractTest.php tests/Unit/Auth/NoRoleStringChecksTest.php`
- `cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Browser/Spec281ProviderConnectionScopeSmokeTest.php tests/Browser/Spec285WorkspaceRbacEnvironmentAccessSmokeTest.php`
- `cd apps/platform && ./vendor/bin/sail bin pint --dirty --format agent`

## Notes
- remaining provider/verification failures are classified in `specs/293-post-cutover-suite-stabilization/failure-classification.md` as unrelated existing debt and are not folded into this slice

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #348
2026-05-11 06:41:47 +00:00

3.8 KiB
Raw Permalink Blame History

Requirements Checklist: Post-Cutover Suite Stabilization & Baseline Reconciliation

Scope and problem framing

  • The package describes the remaining problem as cutover-driven suite and baseline debt after Specs 287 and 288.
  • The package keeps scope limited to stabilization, classification, bounded rebaselines, and explicit documentation of remaining debt.
  • The package explicitly excludes Package Execution, Guided Operations, UI expansion, broad refactors, and legacy reactivation.
  • The package keeps 289 untouched and 292 untouched.

Repo-truth anchoring

  • The package anchors retired panel and /admin/t/... cleanup to current admin-panel and workspace-aware runtime truth.
  • The package anchors operations route cleanup to current workspace-aware operations links.
  • The package anchors provider and required-permissions cleanup to current canonical surfaces rather than tenant-scoped fallbacks.
  • The package anchors action-surface rebaseline to current workspace-first and managed-environment semantics.
  • The package anchors regression proof to the existing Spec 288 proof pack and existing browser anchors.

Failure classification and boundedness

  • The pinned failure-classification categories are exactly cutover-baseline-debt, cutover-runtime-regression, unrelated-existing-debt, flaky-or-environment, and resolved-or-not-needed.
  • The pinned stabilization seams are exactly tenant_panel_baseline, legacy_admin_t_routes, workspace_aware_operations_routes, legacy_required_permissions_provider_connections, and action_surface_rebaseline.
  • The same failure-classification category names appear across spec.md, plan.md, research.md, data-model.md, quickstart.md, tasks.md, checklists/requirements.md, and failure-classification.md, with authoritative meanings owned by data-model.md and failure-classification.md.
  • The same stabilization seams appear across spec.md, plan.md, research.md, data-model.md, tasks.md, and failure-classification.md.
  • The package adds only one spec-local failure-classification artifact and does not turn that artifact into runtime truth.
  • The package allows minimal runtime fixes only when a current workspace-first primary path is proven broken.
  • Remaining unrelated or flaky debt stays explicit instead of being silently absorbed.

Validation and workflow

  • Planned proof begins with baseline classification before fixes.
  • The same validation commands appear across spec.md, plan.md, tasks.md, and quickstart.md.
  • The package re-verifies the Spec 288 proof pack and the browser anchors explicitly.
  • The package ends with broad confidence and formatting checks.
  • The package keeps review outcome, workflow outcome, and test-governance outcome aligned.

Adjacent-spec control

  • 293 is described as a stabilization package, not a Package Execution package.
  • 293 does not overwrite or renumber 289.
  • 293 does not overwrite or renumber 292.
  • The package does not silently absorb Guided Operations, Microsoft Starter Pack, or other future follow-on work.

Notes

  • Reviewed against .specify/memory/constitution.md, the existing Specs 287 and 288, the current product docs, and the repo-real panel, OpsUx, provider, verification, RBAC, and browser test surfaces on 2026-05-10.
  • This package is implementation-ready only when tasks.md preserves the same proof commands, failure categories, stabilization seams, and bounded-scope rules.

Outcome

  • Review outcome class: acceptable-special-case
  • Workflow outcome: keep
  • Test-governance outcome: keep
  • Readiness note: implementation is ready as one bounded stabilization slice after Specs 287 and 288; Package Execution remains separate.