karvey-deploylisted

# Karvey Deploy ## Purpose PHASE 11 of the Karvey Method, between `karvey-qa` (PHASE 10) and `karvey-archive` (PHASE 12). It executes the **ordered deployment flow** (feature branch → `dev` → PR to `master`) honoring the team's hard rules to the letter: never commit directly to `dev`/`master`, never deploy manually (the deploy is triggered by the pipeline), `pull` before starting and before each merge/PR, and **prod never without explicit human OK**. It runs **only after** `karvey-qa` has passed with no open critical/high findings. The central rule is `karvey/rules/deploy-workflow.md`; follow it exactly. ## Execution steps ### Step 0 — Pre-checks (release gate) BEFORE touching git, read: - `docs/spec/changes/{change-id}/spec.json` - `docs/spec/project.json` If `project.json` does not exist, stop and indicate to run `karvey-init` first (see `karvey/rules/project-config.md`). Verify the release gate. If **anything fails, STOP and report what is missing. Do not deploy.** 1. **QA approved with no open critical/high findings.** - Locate the most recent review document: `REVISION_PR_*_{date}.md` at the root of each affected repo (`ls -t REVISION_PR_*.md | head -1`). - The `karvey-qa` security gate must be OK: **0 critical findings and 0 unresolved high findings** in the severity table / pre-merge checklist. - Confirm QA status in `spec.json` (`approvals.qa` / `phase`). 2. **Tests PASS.** Review `docs/test_evidence.md`: there must be entries for the `{change-id}`