[helpcodeai]

Summary

Unit tests build services by hand, so a dependency Nest cannot resolve only shows up when a process boots. Two of these reached production in three days:

• Store a trial that has already ended as expired, not active #1483: @Injectable() on the wrong class. The blue/green check caught it on Cloud.
• Add management-scoped API keys and an amcp management CLI #1508: a guard needing RedisService in SettingsModule, which the File Search worker loads. The worker crash-looped for 14 hours (fixed by Let the files worker boot: make Redis optional in the management-key guard #1526), because the blue/green check and the CI image boot only start the backend. The CI image boot also runs on PRs only when dependencies or the Dockerfile change.

This adds a step to the backend job, so it runs on every pull request. After the build, it starts dist/src/main.js (waits for /health) and dist/src/ee/file-search/files-worker.main.js (waits for "files-worker ready"), with the Cloud settings (NODE_ENV=production, DEPLOYMENT_MODE=cloud, MCP_AUTH_MODE=oauth2) against the job's test database. The step fails if a process exits first, or isn't ready within 120 s, and prints the last 80 log lines.

Changes

• .github/workflows/ci.yml: new step "Boot the backend and the files worker from the build" in the Backend job. It adds CI-only FILES_WORKER_TOKEN, ports and URLs, and no secrets.
• No application code, no ee/ change.

Type

• Other: CI

Testing

• Proof that it catches the bug: a throwaway branch with this step plus Let the files worker boot: make Redis optional in the management-key guard #1526 reverted (tmp/boot-check-proof, run 42004181698). The step failed with the production error: Nest can't resolve dependencies of the JwtOrManagementKeyGuard (PrismaService, ?). The branch is deleted.
• This branch (run 42006310245): "backend ready after 5s", "files-worker ready after 2s". The Backend job is green, and the step adds about 10 s.
• The YAML parses with js-yaml.

Checklist

• My code follows the existing code style
• I have tested my changes locally (and in CI on both branches)
• I have updated documentation (if applicable): comment on the step
• All existing tests pass
• This PR has a descriptive title

Related Issues

Follow-up to #1526 (files-worker crash loop) and #1483. Daily check 2026-11-05, decided by Matteo.

Deployment: CI only. Nothing changes on Cloud or self-hosted.