Stale logs are easy to trust because they look specific

A short debugging note about timestamp, run marker, command, and input checks before reading a stack trace.

The most persuasive bad evidence in debugging is an old stack trace that still looks precise. Line numbers, error names, and file paths feel convincing even when they belong to yesterday’s run or a watcher that restarted with a different input. I now try to clear the terminal or add a small run marker before reading deeply: current time, command, working directory, and input file. If the marker and the error are not from the same run, I treat the log as suspect. It is a small habit, but it prevents a lot of wrong fixes.