- Replaced broken ->rules(fn (\$record)) with proper Filament ->unique()
using ignoreRecord:true + modifyRuleUsing scoped to company_id,
applied to both phone and email in MasterResource and UserResource
- Added migration 2026_09_26_000001 to add unique(company_id, phone)
constraint on users table (nulls out duplicate phones before adding,
MySQL allows multiple NULLs in unique index so blank phones are fine)
- Exception catch in Create/EditMaster and Create/EditUser now also
handles UniqueConstraintViolationException on phone
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Vasyka
16fcdb41ed