Critical regression in v2.1.12 - Destructive behavior causing production data corruption

Bug Report: Critical regression in Claude Code v2.1.12 - Destructive behavior causing production data corruption

Environment

• Claude Code version: v2.1.12
• Model: Claude Opus 4.5

Description

Since updating to Claude Code v2.1.12, I've experienced severe regression in intelligence and extremely destructive behavior that has corrupted my production application.

What happened

1. I requested a minor improvement to a specific section of an existing page
2. Instead, Claude deleted the entire page
3. Claude then created numerous non-existent schemas/collections that were never part of my application's data structure
4. This completely corrupted my app's data architecture

Impact

• My production application is now broken
• I need to spend the entire night recovering and restoring the production environment
• Data structure has been fundamentally corrupted by fabricated schemas

Important notes

• There was NOT A SINGLE context compaction during this session - this was not a context length issue
• The agent hallucinated schemas and collections that never existed in my codebase
• The agent deleted files instead of modifying them as requested

Expected behavior

When asked to improve a specific part of a page, the agent should:

1. Only modify the requested section
2. Not delete entire files
3. Not create fictional schemas/collections
4. Not fabricate data structures that don't exist

Request

I am requesting a refund for this session. The destructive behavior has caused significant damage that requires extensive manual recovery work.

---

This is a serious regression that makes Claude Code unsafe for production codebases. The agent should never delete files or create non-existent schemas without explicit user confirmation.