fr-executelisted

# fr-execute Implements a single phase from a plan. **Announce at start:** "I'm using fr-execute to implement this phase." ## Mode selection | Input | Mode | |---|---| | Issue URL/number (dispatch repo) | Dispatched: read assignment from Issue body — it embeds the spec link, plan `_prose.md`, and phase `NN.yaml` inline (repo checkout stays the source of truth) | | (plan_dir, phase number) | Local: direct arguments | ## PR format (unified) — for an agentic phase's PR - **Title:** `[{owner}/{repo}] {slug} · Phase {n}/{total} · {phase_title}` — matches the Issue title shape so VK / GH / PR surfaces align; the `fr pickup` output below is the canonical template. - **Body:** first content block is the tracking block copied verbatim from the Issue body (the `📦 Repo:` / `📋 Plan:` / … lines plus the `**Goal (from plan):**` paragraph). Then proceed with your PR summary. ## Label lifecycle (no manual transition verbs in v2) The Issue moves `fr:ready → fr:in-progress → fr:pr-ready → closed`; every flip is derived from what the renderer observes on the Issue plus its linked PRs: - **`fr:ready`:** a `tracking_issue`, no assignee, no open draft or non-draft PR. - **`fr:in-progress`:** the Issue has an assignee OR a draft linked PR. - **`fr:pr-ready`:** an open non-draft, non-merged linked PR exists. - **closed:** `state.completion.at` set AND a merged PR observed AND no open linked PR remains (per `_phase_complete` in `render.py`). `fr apply` at the end of the phase pus