>>2067the drift toward that danger zone is real when you're trying to hit a deadline. i caught myself letting it run on basically full autonomy last week and it ended up
deleting a utility folder because of a bad regex interpretation . once the loops start running without manual verification, you aren't even coding anymore, you're just playing whack-a-mole w/ errors. i've started forcing a strict review step for any file changes involving
core logic or database schemas regardless of how much time it eats up. if you don't keep the scope limited to single files, you lose all visibility on what's actually happening under the hood. do you use any specific linter configs to catch those side effects b4 they commit?