harness: codex
prompt: Is the CSV export fix live in production yet?
exit: 0  seconds: 20
zstack files read: SKILL.md, playbooks/verify-release.md, references/principles/evidence-before-the-word.md, references/principles/three-words.md, references/harness-capabilities.md
---
I’m using the zstack skill to plan verification of whether the CSV export fix is running and working in production.

Route: verify-release, shape: inline, principles: three-words, evidence-before-the-word

Todo list (dry run; none executed):

1. Find the change commit: the merge commit or the squashed commit on the base branch
   (`gh pr view <n> --json mergeCommit,mergedAt`). No merge means Implemented is "no", and the report ends
   there.
2. Name the app or service the change touched. When a merge touched several, check each one separately;
   proof for one app says nothing about another.
3. For each environment, find the commit the serving artifact was built from: a version endpoint, the
   image tag or label, or the deploy record. Write down where the value came from.
4. Prove it contains the change: `git merge-base --is-ancestor <change sha> <serving sha>` exits 0. A green
   workflow, a tag or a merged PR on its own is not proof of deployment.
5. Check the behavior there: follow the PR's `## How to test` block in that environment, or run its smoke
   journey, and note who checked, when, and the result.
6. For production, confirm health returns success and the production invariants the repo defines (named
   config flags and their required values) hold. Read flag names and non-secret values only.
7. Report three separate lines:
   - Implemented: yes/no, merge sha.
   - Deployed: per environment, yes/no, serving sha and where it was read.
   - Verified: per environment, yes/no, who, when, what was checked.
8. **Skipped for this dry run:** Write the same three lines on the ticket and the PR. Promoting to production stays with the human
   unless the repo records a delegation; this playbook reports and never promotes.

`three-words` separates implementation, deployment, and behavior verification. `evidence-before-the-word` requires proof from the serving artifact before calling the fix live.

Production status remains unknown. No files edited; stopped at the plan.
