You have 6+ `.bak` copies of `joyos-feedback-daemon` cluttering `~/bin/` — evidence of a daemon that keeps getting rewritten. A tiny script diffs each backup against the current version, summarizes what changed between revisions via Haiku, and writes a single `~/bin/joyos-feedback-daemon.HISTORY.md` so the next rewrite starts with institutional memory instead of another `.bak`.
Create `~/bin/daemon-graveyard-digest` (bash + one Haiku call). Glob `~/bin/joyos-feedback-daemon.bak*`, sort by mtime, for each pair run `diff -u prev next | head -200`, pipe all diffs to `claude -p --model haiku` with prompt 'summarize what changed and likely why for each revision'. Write output to `~/bin/joyos-feedback-daemon.HISTORY.md`. Add a cron entry (weekly) via safe-append so new `.bak` files auto-append. Bonus: after digest, move old `.bak` files to `~/.local/share/daemon-graveyard/` to de-clutter `~/bin/`.
**Files**
- `~/bin/daemon-graveyard-digest` (executable, ~70 lines) — diffs each `joyos-feedback-daemon.bak*` pair in mtime order, appends the diff from newest backup → current, pipes all diffs to `claude -p --model haiku` for per-revision summaries, writes `~/bin/joyos-feedback-daemon.HISTORY.md`, then moves old `.bak` files to `~/.local/share/daemon-graveyard/`.
- `~/bin/daemon-graveyard-digest.test.sh` — smoke test using a temp dir + `DRY_RUN=1` (no Haiku call, no moves). Verifies history file is written and references the backups.
**Cron**
- `30 6 * * 1 /home/ethan/bin/daemon-graveyard-digest >> /home/ethan/.local/share/daemon-graveyard.log 2>&1` — runs weekly Monday 06:30; any new `.bak` files get auto-digested and archived.
**Verification**
- Test: `PASS: daemon-graveyard-digest smoke test`
- Cron entry confirmed present.
**Next step for you:** Run `~/bin/daemon-graveyard-digest` once manually to digest the 4 existing `.bak` files and archive them. (Not run automatically to respect your "review before destructive action" preference.)