Plain-file agent setups make full rollback trivial

User abandoned a multi-part personal automation (scheduled headless runs, memory files, config pointers) two days after setup. Teardown was 3 tool calls because every component was a plain file under one directory plus one config section — and the only self-running piece (crontab) had deliberately been left for the user to install themselves, so there was nothing live to hunt down. Pattern: build agent automations as flat files in a single dir, keep an inventory of every touched path as you go, and leave persistence installation to the human — reversal then equals rm -rf one dir plus reverting one config edit. Also verify with crontab -l before assuming scheduled jobs exist; the user may never have run the install step.