[Bug] Context Reservation Consumes Significant Context Space After /clear

Bug Description
After running /clear in Claude Code, I checked /context immediately and saw that 36% of the context was already being used. I also noticed that "Reserved" alone was taking up 22%. Could you clarify what "Reserved" means? This behavior is quite problematic in practice, since it feels like a large portion of the context is unavailable right from the start.

Environment Info

• Platform: darwin
• Terminal: vscode
• Version: 2.0.0
• Feedback ID: 852df80f-3d15-4286-ba61-5d6691f12c31

Errors

[{"error":"Error: Lock file is already being held\n    at <anonymous> (/$bunfs/root/claude:32:11825)\n    at q (/$bunfs/root/claude:31:10545)\n    at <anonymous> (node:fs:247:13)\n    at processTicksAndRejections (native:7:39)","timestamp":"2025-09-30T01:46:10.131Z"},{"error":"Error: Lock file is already being held\n    at <anonymous> (/$bunfs/root/claude:32:11825)\n    at q (/$bunfs/root/claude:31:10545)\n    at <anonymous> (node:fs:247:13)\n    at processTicksAndRejections (native:7:39)","timestamp":"2025-09-30T01:46:24.702Z"},{"error":"Error: Lock file is already being held\n    at <anonymous> (/$bunfs/root/claude:32:11825)\n    at q (/$bunfs/root/claude:31:10545)\n    at <anonymous> (node:fs:247:13)\n    at processTicksAndRejections (native:7:39)","timestamp":"2025-09-30T01:47:38.223Z"}]