v3.0.1
The database protection that prevents overlapping paid enrollments now checks the PostgreSQL catalog before each startup. The same constraint remains active, while routine deploys and restarts complete cleanly.
The issue appeared during the guarded live activation, before any account enrolled and before any charge job existed. Collection was switched off, the restart path was corrected, and the full billing readiness sequence was repeated.
One short email when something meaningful ships. No streaks required.