This is a platform-level builder infrastructure issue, not a code problem. Here's what's happening:

The Problem:

• Five consecutive deployments (09:47–10:33 UTC) all fail identically at the build stage
• The build gets scheduled on Metal builder builder-xhjzts but never executes — no Railpack initialization, no dependency install, no build command
• The last successful build was at 09:21 UTC (using Nixpacks)
• The failure pattern is identical across four different commits with different build commands, ruling out code changes
• Your @aje/web service in the same repo built successfully with Railpack at 00:17 UTC, so the platform itself is working

Why it's not your code:

• You correctly switched from Nixpacks to Railpack (good catch on the deprecation)
• The builder is silently failing after 30–90 seconds regardless of what code or config you push
• This is specific to your service or that particular builder instance

What to do: Contact Railway support with this deployment ID (b9424027-d1cb-4142-b097-343c252e45bc). The diagnosis tool confirms this requires platform-side investigation — the builder infrastructure needs to be checked or your service may need to be reassigned to a different builder.