---
title: OKSTRA Release Handoff Input - {{TASK_KEY}}
id: {{FM_ID}}
tags: {{FM_TAGS}}
status: ready-for-agent
aliases: {{FM_ALIASES}}
date: {{TASK_DATE}}
task-id: "{{TASK_ID}}"
task-group: "{{TASK_GROUP}}"
project-id: "{{PROJECT_ID}}"
taskType: "{{FM_TASK_TYPE}}"
---

# OKSTRA Release Handoff Input

## Identity

- Project ID:
- Task Group:
- Task ID:
- Related Tasks:
- Issue / Ticket:
- Task Type: `release-handoff`
- Requested Outcome:

## Source Verification Report

- Mode: `{{HANDOFF_MODE}}`
- Stages: `{{HANDOFF_STAGES}}`
- Reports (one row per cited `final-verification` final-report; every Verdict Token MUST be `accepted`):

| Stage | Report path (project-relative) | Verdict Token |
|---|---|---|
{{HANDOFF_SOURCE_REPORTS}}

> This section is generated by `okstra render-bundle` from the consumers ledger (`verified` rows) / the latest accepted whole-task report — the lead re-confirms each cited report's `Verdict Token` and MUST end the run immediately (route back to `final-verification`) if any token is not `accepted`. Release-handoff never operates on `conditional-accept` or `blocked` outcomes.

## Working-Tree Snapshot (filled at run start)

- Feature branch (`git rev-parse --abbrev-ref HEAD`):
- `git status --short` output at run start:
- Existing implementation commits (`git log --oneline <base>..HEAD`):
- Existing PR for this head, if any (`gh pr list --head <branch> --state open --json url --jq '.[0].url'`):

## Candidate PR Base Branches

- Default options offered to the user: `staging` | `preprod` | `prod` | `main` | `dev` | custom input
- Repo-specific preference, if known (e.g. `main` is the integration branch):
- Branches that MUST NOT be used as a base in this repo (security / freeze rules):

## PR Draft Inputs

- PR title convention this repo follows (`release-please` types, plain conventional commits, free-form):
- `git log --oneline <base>..HEAD` and `git diff <base>..HEAD --stat` for the lead to ground its PR draft on:
- Files known to be part of the prior `implementation` run's approved plan:
- Files appearing in the diff that were in the prior run's `Out-of-plan edits` block:

## PR Body Drafter Inputs

- Linked issues / tickets the PR should reference (URLs):
- Test plan items the prior `implementation` run already validated:
- Reviewer hints (teams or individuals the PR should request review from):

## User-Selection Defaults (advisory only — the user still chooses interactively)

- Suggested action (Q1): `local checkout` | `push + PR` | `skip`
- Suggested base (Q2): one of the candidate base branches above
- Suggested message handling (Q3): `use as-is` | `edit then proceed`

> These suggestions help the lead phrase its `AskUserQuestion` prompts. They are NOT pre-approvals — every mutating command still requires an explicit user pick at run time.

## Out of Scope

- Actions deliberately excluded from this handoff:
- Items that look related but belong to a separate handoff or release task:
- Reason for exclusion (different release window, separate owner, deferred decision):

> The lead MUST NOT extend handoff actions into items listed here. If an excluded item should ship in this PR, edit this section before the run starts — do not silently fold it in.

## Questions for Lead Drafting

1. What PR title best describes the cumulative committed diff?
2. Which implementation commits should be highlighted in the PR body?
3. What changed at a behavioural level (not just file-level) that reviewers need to know?
4. Which prior commits in this feature branch should be referenced in the PR?
5. Does the diff include any change that requires a follow-up PR (migration squash, config split, etc.) — and if so, should that be noted in the PR body's `## Follow-ups` block?

## Conversion Note

- This document is generated by `okstra render-bundle --task-type release-handoff` and serves as the run's input in place of a task brief (briefs belong to entry phases only).
- It reuses the same `Task Group` and `Task ID` as the originating implementation / final-verification runs so the handoff stays attached to the same task history.
