# Safe material rename conflict fix

Only `public/index.php` was changed.

When renaming a material creates two identical cutting-detail keys, the system now stops before inserting any cutting-detail rows. The existing transaction rolls back the whole recalculation, so no row is merged, deleted, or partially changed and the previous cutting result remains intact.

No database migration is required.
