I would love to see TDD happen with a test committed followed by a commit to pass the test, etc. to get a sense of the full process or write my own passing code for each test and compare against another implementation.
My first reaction was that the screencast itself already covers this level of detail. The screencast has two channels: a "Lessons Learned" channel, which is for concise, information-dense how-tos, and a "Live" channel, which is a live recording of developing a real world web application. The "Live" channel has the play-by-play Azuldo is asking for.
But then I thought, "Why not? I already have a wrapper that runs my build script—I can just modify that to automatically commit every time the build status changes."
And so I did. The result is Autocommit—a neat little hack that shows how a simple Node.js module developed with TDD evolved over time.