What was built
Ethan has 400+ custom tools, and many are almost certainly dead — never invoked, or last run months ago. This scans every tool in ~/.local/bin (or wherever they live) for last-execution evidence, cross-references against systemd timers and cron entries, and emails a weekly 'graveyard report' listing tools that are orphaned (no timer, no recent invocation) versus tools that are silently failing (timer exists, but last run errored). It turns invisible tool sprawl into a one-page decision list: revive, retire, or ignore.
How it works
Create ~/.local/bin/tool-autopsy-digest as a bash script. (1) Enumerate tools: `ls ~/.local/bin` plus `systemctl --user list-units 'service:*'`. (2) For each tool, gather last-run evidence from three sources: `journalctl --user -u -n1 --since '90 days ago'`, grep of ~/.claude/history or shell history for the tool name, and file atime via `stat -c %X`. (3) Classify: ACTIVE (run <14d), DORMANT (14-90d), ORPHANED (>90d or never), BROKEN (timer scheduled but last journal entry non-zero exit). (4) Cross-reference `systemctl --user list-timers` to find tools with no scheduler at all. (5) Pipe the classified table into the existing `send-formatted-email` tool as an HTML report, and drop a condensed markdown version into ~/Tablet/ so it syncs to the NXTPAPER for stylus triage — Ethan circles what to kill. (6) Register as a systemd user timer running Sundays at 8am. Reuses existing tool-graveyard-reaper and tool-sprawl-sentinel logic if present rather than duplicating it.
Build status
Build timed out after 5 minutes