Fix: add cacheKey prefix to BuildKit cache mount ids

[railway-app]

Problem

The worker build failed with "missing the cacheKey prefix from its id" errors because Dockerfile.worker used bare mount IDs (id=npm, id=pip) in its --mount=type=cache directives, which Railway's BuildKit parser rejects.

Solution

Renamed the cache mount IDs to id=cacheKey_npm (lines 30 and 46) and id=cacheKey_pip (line 60) so they satisfy the required cacheKey_ prefix, allowing the build to proceed and reuse the npm/pip cache mounts.

Changes

• ModifiedDockerfile.worker

---

Generated by Railway

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Free

Run ID: 2caae56f-c360-49c2-8ce8-f8211a9593a7

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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

[supabase]

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[BigSimmo]

Closing as superseded by merged PR #1599. Current main already fixes the Railway BuildKit failure with the stronger compatible approach: it removes the unsupported cache mounts instead of only renaming their IDs, and the replacement container verification passed before #1599 merged. Merging this stale branch would reintroduce cache mounts that the accepted fix deliberately removed.