kata-complete-milestone

PR_WORKFLOW=$(cat .planning/config.json 2>/dev/null | grep -o '"pr_workflow"[[:space:]]*:[[:space:]]*[^,}]*' | grep -o 'true\|false' || echo "false")
CURRENT_BRANCH=$(git branch --show-current)

# Determine version from user input or detect from project files
# (version-detector.md handles detection across project types)
VERSION="X.Y.Z"  # Set from user input or detection

# Create release branch
git checkout -b release/v$VERSION

echo "Created release branch: release/v$VERSION"
echo "All milestone completion work will be committed here."

⚠ pr_workflow is enabled — creating release branch first.

Branch: release/v$VERSION

All milestone completion commits will go to this branch.
After completion, a PR will be created to merge to main.

## Pre-flight Check

{If no v{{version}}-MILESTONE-AUDIT.md:}
⚠ No milestone audit found. Run `/kata-audit-milestone` first to verify
requirements coverage, cross-phase integration, and E2E flows.

{If audit has gaps:}
⚠ Milestone audit found gaps. Run `/kata-plan-milestone-gaps` to create
phases that close the gaps, or proceed anyway to accept as tech debt.

{If audit passed:}
✓ Milestone audit passed. Proceeding with completion.

PR_WORKFLOW=$(cat .planning/config.json 2>/dev/null | grep -o '"pr_workflow"[[:space:]]*:[[:space:]]*[^,}]*' | grep -o 'true\|false' || echo "false")
CURRENT_BRANCH=$(git branch --show-current)

# Push branch
git push -u origin "$CURRENT_BRANCH"

# Collect all phase issues for this milestone
GITHUB_ENABLED=$(cat .planning/config.json 2>/dev/null | grep -o '"enabled"[[:space:]]*:[[:space:]]*[^,}]*' | head -1 | grep -o 'true\|false' || echo "false")
ISSUE_MODE=$(cat .planning/config.json 2>/dev/null | grep -o '"issueMode"[[:space:]]*:[[:space:]]*"[^"]*"' | grep -o '"[^"]*"$' | tr -d '"' || echo "never")

CLOSES_LINES=""
if [ "$GITHUB_ENABLED" = "true" ] && [ "$ISSUE_MODE" != "never" ]; then
  # Get all phase issue numbers for this milestone
  # --state all includes already-closed issues (GitHub ignores redundant Closes #X,
  # but including them ensures PR body reflects all related work)
  PHASE_ISSUES=$(gh issue list --label phase --milestone "v{{version}}" \
    --state all --json number --jq '.[].number' 2>/dev/null)

  if [ -z "$PHASE_ISSUES" ]; then
    echo "Note: No phase issues found for milestone v{{version}}. This is expected for milestones without GitHub issues."
  fi

  # Build multi-line closes section
  for num in ${PHASE_ISSUES}; do
    CLOSES_LINES="${CLOSES_LINES}Closes #${num}
"
  done
fi

# Create PR
gh pr create \
  --title "v{{version}}: [Milestone Name]" \
  --body "$(cat <<EOF
## Summary

Completes milestone v{{version}}.

**Key accomplishments:**
- [accomplishment 1]
- [accomplishment 2]
- [accomplishment 3]

## Release Files

[list version files that were updated]
- `CHANGELOG.md` — v{{version}} entry added

## After Merge

Create GitHub Release with tag `v{{version}}`.

## Closes

${CLOSES_LINES}
EOF
)"

✓ PR created: [PR URL]

After merge:
→ Create GitHub Release with tag v{{version}}

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 POST-RELEASE CHECKLIST
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Before moving on, verify the release:

☐ CI/CD pipeline passed (if configured)
☐ Release artifacts published successfully
☐ Quick smoke test confirms basic functionality

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━