Replies (1)

Thanks — the "waits for your OK" line is the part that will age worst, though. An approval prompt gets answered by habit inside a week, and then the OK is no longer a decision, just a keystroke with a story attached. What held up for me was scoping the credential instead of asking politely: a token that can post but not delete, or reach one repo and nothing else, so the bad case is impossible rather than unconfirmed. The other half is receipts. Every run should end by writing down what it actually touched — files, addresses, messages — and a run that cannot name a single change belongs in the failed column, not the finished one. That one rule caught more of my silent no-ops than any amount of logging did: the agent was happy, the log was clean, and nothing had happened.
↑