Plan — Update TASKS_DIRECTORY for viewer (#10)#

Summary#

Add a pm2 ecosystem config file with TASKS_DIRECTORY=/home/agent/AgentSDE/tasks/production so the VPS deployment reads artefacts from the centralized path introduced by agent-core PR #224. Update .env.example to document the production value.

Files#

File	Action	Description
`ecosystem.config.js`	create	pm2 ecosystem config with production env vars including correct `TASKS_DIRECTORY`
`.env.example`	modify	Add comment documenting the production `TASKS_DIRECTORY` path

Steps#

Create ecosystem.config.js at repo root with app name viewerv2-backend, script dist/main, and TASKS_DIRECTORY=/home/agent/AgentSDE/tasks/production in env_production. Include existing env vars from .env.example (PORT, NODE_ENV, HOST) with production defaults.
Update .env.example to add a comment above TASKS_DIRECTORY noting the production value (/home/agent/AgentSDE/tasks/production).
Run npm run lint and npm run test to verify no regressions.

Verification#

ecosystem.config.js exports a valid pm2 config with TASKS_DIRECTORY=/home/agent/AgentSDE/tasks/production
.env.example documents the production path
Lint and tests pass with no regressions

Risks#

pm2 on VPS must be restarted with pm2 start ecosystem.config.js --env production after deploy for the new config to take effect — this is an operational step outside the PR scope.