My Laravel application is throwing a database-level JSON error that blocks normal use. The issue shows up whenever the app reads from or writes to MySQL, so it looks isolated to the way JSON fields are being handled rather than a general connectivity problem. What I need right now is a concise, well-documented fix: identify the faulty query, model casting, or migration, correct it, and confirm that the error no longer appears under typical CRUD operations. A short report outlining what went wrong and the exact code changes you made will complete the task. Acceptance criteria: • No JSON-related exceptions in the current feature set • All existing unit or feature tests still pass • A brief changelog or commented pull request describing the solution