[P0.16] Fix the production deploy path (missing `ecosystem.production.config.js` + broken uv PATH)

[frankbria]

Severity: high | Category: infra | Phase: P0.16

Problem

Verified: pm2 start ecosystem.production.config.js is referenced twice but the file does not exist (only ecosystem.staging.config.js), so a fresh production host aborts under set -e. The production job also exports PATH="$HOME/.cargo/bin:$PATH" with an unescaped $HOME (expands on the runner, not the host) pointing at the wrong dir, while the installer targets ~/.local/bin — so uv is not found on a clean host.

Evidence

.github/workflows/deploy.yml:546 and :494

Acceptance criteria

• A real ecosystem.production.config.js exists (or the job points at a parameterized/staging config).
• The uv PATH export matches staging: export PATH="\$HOME/.local/bin:\$PATH".
• The production deploy path is dry-run/smoke-tested before the first tagged release.

Dependencies

None

---

_{Filed from the SaaS launch-readiness audit. Atomic: one developer, one session. Work order: strictly P0.1 → P3.12 (no forward dependencies).}

[coderabbitai]

🔗 Related PRs

#95 - feat(ci): Add deployment workflow for staging and production [merged]
#189 - ci: Add npm security audit gate to deployment pipelines [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!