[Bug] Session limit termination loses multi-agent workflow output despite quota consumption

Bug Description
I'm declining the resolution Fin offered (refund with immediate account cancellation). I don't want to close my account — I want the service to work. Please escalate this to a human agent. On 31 July 2026 I lost a full week's Max quota on a Claude Code session that produced substantial rework and two product-level failures. I have the complete exported transcript and have already filed three in-product /feedback reports from that session. Two of these are defects, not quality complaints: Multi-agent workflows consumed quota and then lost their own output. In one case seven refuter agents and the synthesiser died on the session limit and the journal recorded value: None; results had to be salvaged from raw agent transcripts. In a second, a workflow ran 1h 6m 47s and terminated with "You've hit your session limit" — the compute was billed, the deliverable was not retained. Two files in my repository were modified with no attributable cause: a cd .. corrupted to cd ..m in an operations manual (on a line my customer demo depends on), and reordered arrays in a committed JSON artefact. Claude audited its own agents' tool calls and could not account for either. Separately, a substantial share of the week's token spend went on claims the assistant generated without verifying and then spent further tokens discovering were wrong — an entire design-document section was retracted, PR metadata was wrong three times, and an explicit instruction of mine was dropped twice. What I'm asking for: restoration of the weekly usage quota consumed by the two failed workflow runs, or an equivalent service credit applied to my account. Not a refund, and not cancellation. I'm happy to supply the full transcript on request.

Environment Info

• Platform: darwin
• Terminal: iTerm.app
• Version: 2.1.220
• Feedback ID: 6c9475fb-eef5-4b69-919c-f0ba1631531c

Errors

[]