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) When creating the PR for an agentic phase: - **Title:** `[{owner}/{repo}] {slug} · Phase {n}/{total} · {phase_title}` — matches the Issue title shape so VK / GH / PR surfaces align. - **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. The `fr pickup` output below provides the canonical PR title template. ## Label lifecycle (no manual transition verbs in v2) The Issue moves: `vk-ready → in-progress → pr-ready → closed`. v2 has no manual transition verbs — every label flip is derived from what the renderer can observe on the Issue plus its linked PRs: - **`vk-ready`:** the phase has a `tracking_issue` but no assignee, no draft PR, and no open non-draft PR. - **`in-progress`:** the Issue has an assignee OR a draft linked PR. - **`pr-ready`:** an open non-draft, non-merged linked PR exists. - **closed:** `state.completion.at` is set on the phase AND a merged PR is observe