My Next.js 15.5.6 application fails to maintain a stable deployment on Railway. The container starts successfully but immediately crashes with an ELIFECYCLE Command failed error. This creates a restart loop that prevents the application from staying online.

Environment Details
Next.js version: 15.5.6
Deployment platform: Railway
Node.js version: v20.17.0
Application name: course-fishing

Error Logs
Starting Container
✓ Starting…
✓ Ready in 862ms

course-fishing@ start /app
▲ Next.js 15.5.6
next start

• Local: http://localhost:8080

• Network: http://10.194.51.16:8080
  Stopping Container
   ELIFECYCLE  Command failed.
  This pattern repeats continuously, indicating the container starts successfully but immediately terminates after becoming ready.
  Context and Troubleshooting Attempts
  Build process: The application builds successfully locally but fails to maintain stability on Railway.
  Configuration attempts:
  Tried various railway.json and railway.toml configurations.
  Verified proper next build is executed before next start.

Expected Behavior
The application should start successfully and remain running after deployment to Railway.

Requested Assistance
Please help identify why the Next.js application terminates immediately after starting on Railway despite showing "Deployed" status.

What causes the ELIFECYCLE Command failed error in this context?
Is there a specific Railway configuration requirement for Next.js 15 applications that I'm missing?
How can I properly configure CSS handling for third-party libraries in a production Next.js build on Railway?
Are there additional logs or diagnostics I can enable to better understand why the process is terminating?
I've already tried standard deployment approaches including direct deployment and various environment variable settings without success.
my github repo if needed https://github.com/gunt4r/course-fishing
if any context is needed,i will give it asap