v0.7.2 — Prisma CLI resolution fix

Hotfix

Quick follow-up to v0.7.1 — the boot-time `prisma migrate deploy` was using a hardcoded path that worked in the prod image but failed in dev, since npm workspaces hoist the prisma binary to the monorepo root in dev (no packages/backend/node_modules/.bin/prisma).

Fix

• ensureMigrated now resolves the prisma CLI via Node's module resolution (require.resolve('prisma/package.json') + pkg.bin) instead of a hardcoded path. Works in both setups:
  • Dev (npm workspaces): finds prisma in <root>/node_modules/prisma
  • Prod image: finds prisma in packages/backend/node_modules/prisma
• No npx dependency reintroduced — the prod image stays free of npm/yarn/corepack.

Production deploys of v0.7.1 weren't affected (the old hardcoded path matched the prod layout). This release future-proofs against any layout change.

---

Full changelog: v0.7.1...v0.7.2

Upgrading

```
docker pull ghcr.io/arediss/oscarr:0.7.2
```
or
```
docker pull ghcr.io/arediss/oscarr:latest
```