# Requirements Checklist: Post-Cutover Suite Stabilization & Baseline Reconciliation

## Scope and problem framing

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

## Repo-truth anchoring

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

## Failure classification and boundedness

- [x] The pinned failure-classification categories are exactly `cutover-baseline-debt`, `cutover-runtime-regression`, `unrelated-existing-debt`, `flaky-or-environment`, and `resolved-or-not-needed`.
- [x] 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`.
- [x] 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`.
- [x] The same stabilization seams appear across `spec.md`, `plan.md`, `research.md`, `data-model.md`, `tasks.md`, and `failure-classification.md`.
- [x] The package adds only one spec-local failure-classification artifact and does not turn that artifact into runtime truth.
- [x] The package allows minimal runtime fixes only when a current workspace-first primary path is proven broken.
- [x] Remaining unrelated or flaky debt stays explicit instead of being silently absorbed.

## Validation and workflow

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

## Adjacent-spec control

- [x] `293` is described as a stabilization package, not a Package Execution package.
- [x] `293` does not overwrite or renumber `289`.
- [x] `293` does not overwrite or renumber `292`.
- [x] 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.