Skip to main content

Regression Notes

Last reviewed: 2026-05-13
Maintained by: Engineering

Track recurring engineering regression patterns here so reviews and smoke tests can target them earlier.

Current watch areas

  • environment contract drift between code, .env.example, and docs
  • migration drift between database/migrations and database/schema.snapshot.sql
  • startup regressions caused by stale local build artifacts
  • auth and role-scope regressions across manager, tenant, technician, and super_admin flows
  • hosted-only integrations that should remain optional in local development, such as Sentry and external email delivery

Usage rule

When the team finds a repeated class of regression, add:

  • what breaks
  • where it usually surfaces
  • the fastest local verification step