Please investigate the repeated deployment failures for the Quest Video Engine staging service.

Repository: questsmartsoluk-stack/quest-content-os

Branch: review/auth-tenant-foundation

Railway service: quest-engine-test

Production must remain untouched.

Last confirmed working staging commit:

f9f5bfc4ddeb7133d1e652c62823cb1a23dbb993

Failed deployment commits:

• 479d14f290c5011f824c9cf8db4357be17f8fddd
• 48aafbea9f2ad238dfa2963d917df8a4966b232f
• 5d69e70ca67351fcdc60ec294ea6227e5f3d6ba2
• 23f52fbbb62ce5f8f8a3fbb694defbf2cf4a937c

Latest failed Railway deployment UUID:

820bcede-53d4-4fb2-807e-015ad9a3d3f9

The latest retry commit, 23f52fbbb62ce5f8f8a3fbb694defbf2cf4a937c, contained no code changes. It reused the same Git tree solely to trigger another deployment, but Railway failed again. This shows the problem is repeatable and not a temporary Git push failure.

Changes waiting to be deployed include:

1. Simplified Scenes & Visuals output cards.
2. Technical scene controls moved into a collapsed “Scene settings and individual retry” section.
3. Main narration moved to Assets & Setup.
4. One “Create Narration for All Scenes” action.
5. Selected voice and generated narration audio shown as separate statuses.
6. Project voice forwarded correctly to the bulk narration service.
7. Individual scene narration retained only as an optional override.
8. Seedance remains animation-only, not an image provider.

Please obtain and inspect the complete Railway build and deployment logs for UUID 820bcede-53d4-4fb2-807e-015ad9a3d3f9 and report:

• the exact failed build or startup command;
• exit code;
• complete error and stack trace;
• whether failure occurs during image build, dependency installation, server startup, migration check, or health check;
• whether package.json and package-lock.json are synchronized;
• whether the previously cached dependency layer is being reused;
• whether the service start command and working directory are correct;
• whether the deployment reaches GET /health;
• the minimum correction required.

Do not make speculative product-code changes before identifying the exact logged error.

Constraints:

• Do not touch production.
• Do not modify migrations 011 or 012.
• Do not touch the Quest Admissions Engine.
• Use mocked providers only.
• Make no paid provider calls.
• Do not alter the intended narration or simplified-output behaviour merely to force a deployment.

The current staging URL may still respond because Railway has retained the last successful deployment. That does not mean the latest commit deployed successfully.

The separate Windows Exact Product compositing assertions are an independent regression-audit matter and should not be treated as the cause of the Railway failure unless the Railway logs explicitly prove a connection.