Plan: AW-3 — Add Redis (BullMQ) to agent-core#

Summary#

Add Redis connectivity via ioredis and BullMQ queue infrastructure to agent-core, registering phase-invoke and phase-result queues and surfacing Redis health in the /health endpoint. This is the shared foundation blocking AW-4, AW-5, AW-7, and AW-9.

Files#

File	Action	Description
`package.json`	modify	Add `@nestjs/bullmq`, `bullmq`, `ioredis` dependencies
`src/config/config.schema.ts`	modify	Add `REDIS_HOST` (string, default `localhost`) and `REDIS_PORT` (number, default `6379`) to Joi schema
`src/app.module.ts`	modify	Register `BullModule.forRootAsync()` with config-driven connection, register `phase-invoke` and `phase-result` queues
`src/health/health.service.ts`	modify	Inject Redis client (`ioredis`), add `ping()` check, return `redis` field in health response
`src/health/health.controller.ts`	modify	Update return type to include `redis` field
`src/health/health.module.ts`	modify	Provide the Redis `IORedis` client via a custom factory provider
`src/health/health.controller.spec.ts`	modify	Update test to mock Redis health and assert new response shape
`src/health/health.service.spec.ts`	create	Unit test for `HealthService` covering connected and disconnected Redis states
`.env`	modify	Append `REDIS_HOST=localhost` and `REDIS_PORT=6379`

Steps#

Install @nestjs/bullmq, bullmq, and ioredis via npm install.
Add REDIS_HOST and REDIS_PORT to configValidationSchema in src/config/config.schema.ts (after EXCLUDED_REPOS, line ~22).
Append REDIS_HOST=localhost and REDIS_PORT=6379 to .env.
Import BullModule from @nestjs/bullmq in src/app.module.ts. Add BullModule.forRootAsync() with ConfigService injection (reading REDIS_HOST and REDIS_PORT) after AppConfigModule. Register phase-invoke and phase-result queues via BullModule.registerQueue().
Create a custom Redis provider in src/health/health.module.ts using ioredis (new Redis({ host, port }) from ConfigService), inject it into HealthService.
Update HealthService.getHealth() to call redis.ping(), return { status, uptime, redis } where redis is "connected" or "disconnected".
Update HealthController return type to match the new response shape.
Update existing health.controller.spec.ts and create health.service.spec.ts — mock Redis client, test connected/disconnected paths.
Run npm run build, npm run test, npm run lint to verify.

Verification#

npm run build compiles cleanly with zero errors.
npm run test passes with no regressions; new health specs pass.
npm run lint reports zero warnings.

Risks#

BullMQ startup failure blocks boot: Redis unavailable at startup should cause a hard failure (fail fast). Verify BullModule.forRootAsync() propagates connection errors to NestJS bootstrap — if it silently swallows, add an onModuleInit Redis ping guard.
ioredis dual usage: Both BullMQ (internal) and HealthService (explicit) use ioredis. Use a separate Redis instance for health checks to avoid coupling health probes to BullMQ's internal connection lifecycle.