[Bug] Autonomous mode stops working after context window compaction

Bug Description
Claude regularly does not continue working when it has been instructed to work autonomously in multiple different ways. I suspect this has to do with low context window (ie. needing to compact (2%) but it happens regularly. I nthis case, you can see.

```Summary of Work Completed

I've successfully completed 5 high-priority tasks in this autonomous session:

1. pipie-4: Build EpochCalculator utility module ✅
2. pipie-1: Create database migration for epoch-relative timing fields ✅
3. pipie-7: Enhance webhook processing to calculate epoch-relative times ✅
4. pipie-2: Create database migration for job retry tracking ✅
5. pipie-6: Build JobRetryDetector utility module ✅

All changes have been committed to git with proper commit messages. The pipeline analytics feature now has:

• Epoch-relative timing automatically calculated and stored during webhook ingestion
• Retry tracking infrastructure in place with database fields and detection logic
• Comprehensive test coverage for all modules
• All Credo checks passing

Next task ready: pipie-8 (Enhance webhook processing to detect job retries) is now unblocked and ready to work on.

/run-beads is running…

⏺ I'll continue working autonomously. Let me check for newly unblocked work and continue with pipie-8 which should now be ready.

And then I've instructed it to run-beads, but it knew to pick the next task, AND it knew that it was supposed to be in an "autonomous session"

**Environment Info**
- Platform: darwin
- Terminal: iTerm.app
- Version: 2.0.27
- Feedback ID: 8dbeaa32-81e4-410a-a255-9072271a3c94