ahmido/TenantAtlas
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity
e288a4731f
TenantAtlas/specs/288-quality-gates-no-legacy-enforcement/checklists/requirements.md
Ahmed Darrazi e288a4731f
Some checks failed
PR Fast Feedback / fast-feedback (pull_request) Failing after 1m26s
Details
feat(spec-288): add no-legacy quality gates
2026-05-10 23:23:07 +02:00

3.2 KiB
Raw Blame History

Requirements Checklist: Quality Gates / No-Legacy Enforcement

Scope and problem framing

  • The package describes the real repo problem as missing enforcement over an already-completed cutover baseline.
  • The package keeps scope limited to guards, targeted browser proof, quality-gate docs, and classification-only baseline handling.
  • The package explicitly excludes runtime cutover work, provider-core rewrites, RBAC rewrites, UI copy cleanup, Review Pack export work, Guided Operations, and full-suite repair.
  • The package explicitly moves Package Execution Contract work to Spec 289.

Repo-truth anchoring

  • The package anchors route/path enforcement to exact retired management families instead of broad /admin/t bans.
  • The package anchors helper enforcement to retired tenant-panel bootstrapping patterns on owned seams.
  • The package anchors provider-core enforcement to the existing provider-boundary seams and operation-definition guards.
  • The package anchors role-authority enforcement to the existing workspace-first policy and managed-environment scope tests.
  • The package anchors baseline classification to TestLaneManifest, TestLaneReport, the current classification-contract tests, and README.md.

Enforcement inventory and boundedness

  • The same enforcement categories appear across spec.md, plan.md, research.md, data-model.md, quickstart.md, the logical contract, and tasks.md.
  • Historical and immutable scan exclusions are pinned explicitly.
  • The package keeps provider-owned detail nested and bounded instead of pretending it disappears entirely.
  • The package forbids open-ended route, helper, or source-scan allowlists.
  • The package keeps broader baseline fallout classification-only.

Validation and workflow

  • Planned proof stays bounded to targeted guard tests, targeted browser validation, and formatting.
  • The same validation commands appear in spec.md, plan.md, tasks.md, and quickstart.md.
  • The task package explicitly re-verifies Filament/Livewire/provider-registration invariants and the no-asset-registration boundary.
  • The package keeps review outcome, workflow outcome, and test-governance outcome aligned.
  • The package uses NoLegacyGuardrail as the close-out intent.

Adjacent-spec control

  • Spec 289 is named as the explicit Package Execution Contract follow-up.
  • The package does not silently absorb runtime cutover work from Spec 287.
  • The package does not silently absorb UI copy cleanup from Spec 286.
  • The package does not silently absorb broader provider-core or RBAC rewrites.

Notes

  • Reviewed against .specify/memory/constitution.md, the cutover sequence in Specs 279 through 287, the current guard/browser/lane seams, and the user-corrected 288 scope on 2026-05-10.
  • This artifact package is implementation-ready only when the execution task map exists and the companion artifacts remain aligned.

Outcome

  • Review outcome class: acceptable-special-case
  • Workflow outcome: keep
  • Test-governance outcome: keep
  • Readiness note: implementation is ready as a bounded enforcement slice following Spec 287; broader baseline repair remains out of scope