Feedback reaper kills headless agents

The CreatorTrack dev-slot reaper (idle 45m / cap 4 per reference_creatortrack_dev_slot_reaper.md) only treats an open browser tab as a liveness signal. Headless background agents (spawned via Agent tool, no browser attached) look idle even while actively working, so the reaper deletes their worktree + DB out from under them.

Why: confirmed across 3 of 4 parallel Fable agents in the 2026-07-06 fitness/social/clips/sales-crm session; each had to detect the deletion, re-bootstrap the slot, replay all uncommitted work from context, and re-commit. One agent (Social Analytics) worked around it by holding a keepalive TCP connection to the dev port so the reaper can't strike again.

How to apply: when spawning a headless background agent that will hold a CreatorTrack worktree for a long session, either (a) instruct it to commit very frequently so a reap loses minimal work, or (b) have it open/hold a keepalive connection to its assigned dev port. The reaper itself should eventually be fixed to recognize active agent sessions (not just browser connections) as non-idle; that fix hasn't been made yet as of 2026-07-06.

[auto-memory session 1dde0e49-1ddb-40b9-89f1-05336898db9f, confidence 0.85, mode direct]