# Requirements Checklist: Spec 391 - Operations Hub Stability and Debug-Safe Runtime

**Purpose**: Validate that Spec 391 is scoped, implementable, constitution-aligned, and ready for a later implementation loop.  
**Created**: 2026-06-20  
**Feature**: `specs/391-operations-hub-stability-debug-safe-runtime/spec.md`

## Scope And Candidate Gate

- [ ] CHK001 The selected candidate is directly backed by browser audit BUG-001 and BUG-009.
- [ ] CHK002 The package does not reopen completed Operations productization specs except as context.
- [ ] CHK003 Out-of-scope Evidence, Provider, Review Pack, Restore, dashboard, system-login branding, and customer-facing delivery topics remain excluded.
- [ ] CHK004 No application implementation is included in the preparation package.

## UI And Operations Surface

- [ ] CHK005 The UI Surface Impact decision is coherent and names the existing Operations hub surface.
- [ ] CHK006 Existing UI-016 coverage is treated as still valid unless implementation materially changes route/archetype.
- [ ] CHK007 The Operations hub remains a read-only monitoring/registry surface with no new dangerous actions.
- [ ] CHK008 The environment filter is explicit route/page state, not hidden global context.
- [ ] CHK009 Controlled empty/error/loading states are required without masking the expensive render path or flashing raw framework/debug output.

## RBAC, Isolation, And OperationRun Truth

- [ ] CHK010 Workspace membership and environment entitlement are required before rows, counts, filters, or links reveal tenant-bound runs.
- [ ] CHK011 Non-member/non-entitled access remains deny-as-not-found according to existing route contract.
- [ ] CHK012 OperationRun execution truth is preserved; no status/outcome/lifecycle semantics are changed to satisfy performance.
- [ ] CHK013 Existing OperationRun detail/view links remain delegated to `OperationRunLinks` / tenantless viewer paths.

## Runtime And Test Governance

- [ ] CHK014 Feature/Livewire tests cover route render, scope, bounded index behavior, no debug page, no Graph calls, empty state, and safe detail links.
- [ ] CHK015 Browser tests cover HTTP success, render timing, console/runtime globals, Vite dev-client failure, Debugbar/source links, stack traces, and network 500s.
- [ ] CHK016 Productization-smoke controls are opt-in and do not disable normal local Debugbar/Vite workflow.
- [ ] CHK017 Fixtures do not require seeders, real provider access, provider syncs, restore jobs, exports, deletes, archives, or notifications.
- [ ] CHK018 Browser lane addition is explicit and bounded to Spec 391.

## Proportionality And Architecture

- [ ] CHK019 No new persisted entity, migration, enum/status family, taxonomy, domain abstraction, or cross-domain framework is introduced by the spec.
- [ ] CHK020 Any migration/index need discovered later must update spec/plan before implementation continues.
- [ ] CHK021 The plan requires identifying the actual expensive render path instead of increasing timeouts or adding a catch-all.
- [ ] CHK022 Existing shared OperationRun, badge, table pagination, asset, and smoke-login patterns are reused first.

## Review Outcome

- [ ] CHK023 Review outcome class selected: `acceptable-special-case` if artifacts remain bounded; otherwise document finding.
- [ ] CHK024 Workflow outcome selected: `keep` if artifacts remain implementation-ready; otherwise `split` or `document-in-feature`.
- [ ] CHK025 Manual reviewer confirms Spec Readiness Gate before implementation begins.

## Notes

- Intended review outcome after preparation: `acceptable-special-case`.
- Intended workflow outcome after preparation: `keep`.
- Final implementation close-out target: `Guardrail / Exception / Smoke Coverage`.