# Branch expiration: the default differs by creation path

## The trap
An engineer tests branch creation in the Console, sees tidy auto-deletion, then ships a pipeline using the API. The pipeline's branches never expire, because API and CLI branches have no expiration by default. Months later the storage bill tells the story.

## The rule
- Console: "Automatically delete branch after" defaults to checked, 1 day.
- API/CLI: no expiration by default; set it explicitly (1 hour, 1 day, 7 days) or schedule deletion.
- Pick the lifetime from the use case: PR previews = 1 day, CI test runs = 1 hour, dev branches = 7 days or manual.

## Checklist
- Every automation that creates branches sets expiration or deletes in a cleanup step; no exceptions.
- Audit existing branches for ancient API-created ones with no expiration.
- Expiration deletes the branch permanently, same as manual deletion; make sure nothing durable lives only on an expiring branch.
- For branches that must persist (staging, prod), uncheck expiration deliberately, not by accident.