ahmido/TenantAtlas
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity
platform-dev
TenantAtlas/specs/322-browser-no-drift-regression-guard/checklists/requirements.md
ahmido ec4ff1074c Spec 322: add browser no-drift regression guards (#379) 
## Summary
- add the Spec 322 artifact set for the browser no-drift regression guard
- add Feature navigation guards for admin surface scope, environment CTA URLs, and legacy alias rejection
- add Browser smoke coverage for workspace hubs, environment-owned surfaces, workspace-owned analysis surfaces, and alerts/audit flows
- add the Spec 322 browser support harness used by the new smoke coverage

## Validation
- `cd apps/platform && ./vendor/bin/sail artisan test tests/Feature/Navigation/Spec322AdminSurfaceScopeContractTest.php tests/Feature/Navigation/Spec322LegacyQueryAliasGuardTest.php tests/Feature/Navigation/Spec322EnvironmentCtaUrlContractTest.php --compact`
- `cd apps/platform && ./vendor/bin/sail artisan test tests/Browser/Spec322WorkspaceHubNoDriftSmokeTest.php tests/Browser/Spec322EnvironmentOwnedSurfaceSmokeTest.php tests/Browser/Spec322WorkspaceOwnedAnalysisSmokeTest.php tests/Browser/Spec322AlertsAuditNoDriftSmokeTest.php --compact`
- `cd apps/platform && ./vendor/bin/sail pint --dirty`
- `git diff --check`

## Notes
- a broader filtered regression run still reports existing Baseline Compare feature-test failures outside this diff

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #379
2026-05-17 11:34:31 +00:00

2.9 KiB
Raw Permalink Blame History

Specification Quality Checklist: Browser No-Drift Regression Guard

Purpose: Validate preparation completeness and quality before implementation. Created: 2026-05-17 Feature: specs/322-browser-no-drift-regression-guard/spec.md

Content Quality

  • Spec Candidate Check is completed.
  • The selected candidate is direct user-provided manual promotion.
  • Related completed specs are treated as historical context and not rewritten.
  • The scope is focused on durable guards and no-drift regression coverage.
  • No application implementation is included in preparation artifacts.
  • No migration, seeder, package, env var, queue, scheduler, storage, or deployment asset change is planned.

Requirement Completeness

  • No [NEEDS CLARIFICATION] markers remain.
  • Functional requirements are testable and unambiguous.
  • Non-functional requirements cover browser stability, lane cost, fixture cost, and no Playwright MCP dependency.
  • Success criteria are measurable by artifacts and test results.
  • All user stories include independent test descriptions and acceptance scenarios.
  • Edge cases cover cross-workspace IDs, legacy aliases, stale state, back/forward, old clean URLs, and browser blockers.
  • Dependencies and assumptions are identified.

Feature Readiness

  • spec.md exists.
  • plan.md exists.
  • tasks.md exists.
  • test-plan.md exists.
  • coverage-manifest.md exists.
  • Screenshots artifact directory is represented by .gitkeep.
  • Tasks are ordered, small, and verifiable.
  • Tasks include Feature/static guards and Browser guard coverage.
  • Tasks include validation commands and final report obligations.
  • Tasks include explicit non-goals and stop conditions.

Constitution / Repo Alignment

  • Workspace isolation and cross-workspace rejection are explicit.
  • Legacy Tenant aliases remain invalid and no compatibility layer is allowed.
  • Provider Tenant terminology remains provider-boundary only.
  • Proportionality review covers the new test/manifest ownership cost.
  • Test governance names Browser lane expansion and fixture/helper cost controls.
  • Filament v5 / Livewire v4 compliance is explicitly addressed.
  • Provider registration location remains apps/platform/bootstrap/providers.php; no provider change is planned.
  • Global search and destructive action output-contract points are addressed.
  • Asset strategy is explicit; no filament:assets deployment change is planned.

Preparation Analysis Outcome

  • Preparation artifacts are internally consistent after review.
  • No preparation issue requires application implementation.
  • No open question blocks implementation.

Notes

Runtime acceptance remains pending until implementation, targeted Feature/static tests, targeted Browser tests, formatting, and git diff --check are completed.