I totally agree. Using Git as a diary should be strictly for local development with AI tools, just to track failed attempts and avoid loops. But that messy history shouldn't reach the mainline.

Upstream commits must be clean, squashed, and strictly human-readable—no debugging noise or dead ends. It's essentially two layers: a messy 'AI diary' for local exploration, and a curated history for future maintainers.

'Dirty workshop, clean mainline.' Thanks for highlighting this boundary; I'm making it a permanent rule in my workflow!