fix: auto-purge stale offline workers from fleet page

[GeiserX]

Summary

• Workers offline for > 1 hour are auto-deleted from the database
• Prevents fleet page from filling with stale entries after container recreations
• Immediately purged 6 stale workers from current DB

Test plan

• 880 tests pass
• Manually deleted 6 stale workers from prod DB
• After deploy, fleet page shows only active workers

[coderabbitai]

Warning

Review limit reached

@GeiserX, we couldn't start this review because you've used your available PR reviews for now.

Your plan currently allows 1 review/hour. Refill in 33 minutes and 19 seconds.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more review capacity refills, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than trial, open-source, and free plans. In all cases, review capacity refills continuously over time.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 2c756567-c379-4b0f-a13b-8bb88f4e44f5

📥 Commits

Reviewing files that changed from the base of the PR and between 64677b4 and 5951055.

📒 Files selected for processing (1)

• app/main.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/stale-workers-purge

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

❌ Patch coverage is 69.23077% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 90.96%. Comparing base (9e80688) to head (5951055).
⚠️ Report is 2 commits behind head on main.

Files with missing lines	Patch %	Lines
app/main.py	69.23%	4 Missing ⚠️

❌ Your patch status has failed because the patch coverage (69.23%) is below the target coverage (90.00%). You can increase the patch coverage or adjust the target coverage.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #76      +/-   ##
==========================================
- Coverage   91.08%   90.96%   -0.13%     
==========================================
  Files          25       25              
  Lines        2748     2755       +7     
==========================================
+ Hits         2503     2506       +3     
- Misses        245      249       +4     

Files with missing lines	Coverage Δ
app/main.py	89.82% <69.23%> (-0.33%)	⬇️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.