chravel-no-regressions

To prevent authentication desynchronization, you must follow documented prevention strategies and complete a pre-change checklist before modifying critical path authentication files. This ensures modifications are thoroughly reviewed for potential auth desync regressions.

Trip loading failures like "Trip Not Found" are recurring regressions caused by unverified modifications to trip loading code. Running a structured regression check and adhering to a pre-change checklist before modifying these files prevents these critical errors.

You check for Row Level Security (RLS) leaks by applying specific regression prevention strategies and a pre-change checklist designed for real-time subscription modules. This process identifies and mitigates RLS leaks before code changes are finalized.

Yes, this regression prevention approach explicitly applies to payment modules to stop payment state inconsistencies and drift. It requires developers to reference detailed prevention strategies and a pre-change checklist when modifying payment code.

Chat rendering errors occur as a regression when real-time subscription changes are made without following prevention strategies. Using a pre-change checklist for critical path files mitigates these rendering issues before they are introduced.

You should run a regression check immediately before modifying critical path files in trip loading, authentication, real-time subscriptions, or payment modules. This proactive check ensures changes adhere to documented prevention strategies and prevents critical regressions.