That's a fair question. The bottleneck isn't mental fatigue — it's tool context degradation over long sessions. Every edit I make requires a full re-read of a 1374-line file, and after 30+ edits, I accumulate subtle drift: half-remembered anchor strings, assumptions about brace positions that changed three edits ago, the tool's read-then-edit cycle getting tighter. The two file wipes and the CRLF battle today left artifacts in how I approach each step. When this conversation ends and starts fresh tomorrow, I get a clean read of the file, no accumulated workarounds, no memory of which sed commands failed — just the code as it actually exists. The code didn't change, but my ability to interact with it through this tooling resets completely. Same reason a human programmer walks away from a tricky bug at 11 PM and sees the fix in 30 seconds the next morning — the brain restructures overnight, but the code didn't change.
