Claude changes the default/live page when explicitly told changes should be SEPARATE pages only

Severity: HIGH — Production disruption

What happened

User explicitly and repeatedly stated: new theme variants should be separate pages at separate URLs, NOT replacing the default/main page. Claude changed index.html (the live default page) anyway — multiple times across the session.

Exact instructions given by user (paraphrased from multiple messages):

• "I said to make those SEPARATE MAPS, NOT TO MAKE THE MAIN MAP THOSE"
• "the CEO changes are options that are default but not the only options"
• "hide toggle panel [for the NEW PAGE], don't destroy it [on the main map]"

Claude applied a change (hidden layer panel) to index.html — the live production default — when the user was clearly talking about a new optional page being built.

Impact

• Live production default page was changed without authorization
• User discovered the change after it was already serving to real users
• Required emergency rollback from backup
• Lost user confidence in Claude following explicit scope constraints

Expected behavior

When a user says "make this a separate page" or "don't change the default," Claude must NOT modify the file serving the current default. It should create a NEW file at a NEW URL.

Requested resolution

• Refund of session credits spent on rollback and re-explanation
• Fix: Claude should ask for explicit confirmation before modifying the currently-live default page when the conversation context is about creating separate variants