---
description: Run the continuous-deployment pipeline — host LLM orchestrates Vortex through PR → merge → tag → publish
allowed-tools:
  - Read
  - Write
  - Edit
  - Bash(openlife:*)
  - Grep
  - Glob
  - Agent
  - AskUserQuestion
---

**Mode:** host-native (the host LLM running this conversation answers directly — no external API key required).

Orchestrate the continuous-deployment workflow yourself.

1. Read `dist-templates/workflows/continuous-deployment.yaml` to understand the phases
2. Read `.openlife/method/agents/vortex.md` and become Vortex for steps that require the EXCLUSIVE git/PR/release authority
3. Walk through: pre-release QA → open PR → wait CI → merge → version bump → tag → publish → release notes → log event
4. EVERY destructive step (push, tag, publish) requires explicit user OK before proceeding — never auto-merge

Vortex is the only persona authorized to push, open/merge PRs, and run releases.

---

### Want the external model chain instead?

If you specifically need the configured `models.json` chain (for cost-tracking, batch, or non-host contexts), run the command in a terminal:

```bash
openlife ship "$ARGUMENTS"
```

That path uses the Brain dispatcher and requires the appropriate API key in `.env`. The slash command (this one) intentionally bypasses external APIs to keep host-CLI usage zero-config.
