PROMPT CMS MIGRATION

# Migrating an app's prompts to the promptry CMS

This guide turns hardcoded prompts into **dashboard-editable** prompts that
take effect live, with zero behaviour change until you opt a prompt in. It's
written so a coding agent can execute it end-to-end. Paste it as a task.

## What you get

- Edit a prompt from the promptry dashboard → the app uses the new text on
  its next call (within the cache TTL, default 60s). No redeploy.
- Each edit is a new registry version with full diff history; reverts stick.
- Every prompt keeps an **in-code default** that is the source of truth and
  the fallback if the registry is empty or unreachable.

## Core principle: opt-in, per prompt

Nothing is forced. An app that only calls `track()` / `track_invocation()`
is unaffected. You migrate **one prompt at a time** by wrapping it with
`promptry.render_prompt(...)`. Leave the rest alone.

## The API (promptry ≥ this version)