---
name: abra-chaos-deploy-checkout-gotcha
description: "abra app new moves the recipe checkout to the release tag — checkout the PR branch AFTER app new, or chaos deploys the wrong tree"
metadata: 
  node_type: memory
  type: project
  originSessionId: fc17c9c2-ab6e-4c11-856e-a6a6e160a0ec
---

On cc-ci, `abra app new <recipe>` checks out the latest *published release tag* in
`~/.abra/recipes/<recipe>`, silently discarding whatever commit you had checked out. A
subsequent `abra app deploy --chaos` then deploys that tag's tree, not your WIP.

**Why:** abra pins app creation to the recipe's released version and moves the recipe
checkout to do it; `--chaos` only means "deploy the working tree as-is at deploy time".

**How to apply:** in the step-2b direct-deploy loop, order matters: `abra app new` first,
*then* `git checkout <PR-branch>` in the recipe dir, then `abra app deploy --chaos`.
Verify with the deploy overview (config versions / images) that the intended tree went out.
Also: plausible's `.env.sample` ships `DISABLE_AUTH/DISABLE_REGISTRATION=replace-me`, which
crash-loops the app (`binary_to_existing_atom("replace-me")`) — set them to true/false in
any dev env. See [[regression-canary-cadence]] for related CI cadence.