fix: handle Docker named volume for .venv in dev entrypoint

[silasly]

Closes #35

Description

When running the dev Docker setup on ARM64 (Raspberry Pi) or any system where .venv is mounted as a Docker named volume, the entrypoint fails because rm -rf /app/backend/.venv returns Device or resource busy.

Docker named volumes cannot be removed with rm -rf — the directory persists in the volume store. This causes the dev environment to crash-loop on container start.

Fix

1. Attempt rm -rf /app/backend/.venv first (works for bind mounts / plain directories)
2. Fall back to uv venv --clear which clears contents without removing the directory — works on Docker volumes

Testing

• ✅ Tested on Raspberry Pi 5 (ARM64, Debian trixie) with Docker Compose
• ✅ All services (db, redis, web, worker, frontend, docs) start successfully

[Copilot]

Pull request overview

Improves the dev Docker entrypoint’s resilience when .venv is backed by a Docker named volume (common on ARM64/Raspberry Pi), avoiding crash-loops caused by attempting to rm -rf a mounted volume directory.

Changes:

• Make .venv cleanup tolerant of Docker named volumes by ignoring rm -rf failure and clearing via uv venv --clear.
• Add a “sync dependencies” step when the venv is already valid.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Updates the dev Docker entrypoint to avoid crash-loops when .venv is mounted as a Docker named volume (where deleting the mountpoint directory fails), ensuring dependencies can still be reinstalled/cleared reliably in dev setups (including ARM64).

Changes:

• Capture and warn on failures when attempting to rm -rf /app/backend/.venv, then fall back to uv venv --clear to clear the environment without removing the directory.
• Add a best-effort uv sync on startup when an existing venv is detected as working.
• Keep watchmedo installation as a guard when missing.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud