fix(#2797): create ready-for-triage label before use in post-retro.sh

internal/scaffold/fullsend-repo/scripts/post-retro-test.sh

@@ -37,6 +37,11 @@ done
 
 echo "gh $*" >> "${GH_LOG}"
 
+# Label creation calls — succeed silently (mimics --force behavior).
+if [[ "$1" == "label" && "$2" == "create" ]]; then
+  exit 0
+fi
+
 # Issue creation calls — return a fake issue URL.
 if [[ "$1" == "issue" && "$2" == "create" ]]; then
   echo "https://github.com/test-org/target-repo/issues/99"
@@ -219,6 +224,11 @@ run_test "happy-path-triage-label" \
   "${FIXTURE_ONE_PROPOSAL}" \
   "ready-for-triage"
 
+# Verify that gh label create is called before gh issue create.
+run_test "label-created-before-issue" \
+  "${FIXTURE_ONE_PROPOSAL}" \
+  "gh label create ready-for-triage"
+
 # Happy path: no proposals, comment posted successfully.
 run_test "happy-path-no-proposals" \
   "${FIXTURE_NO_PROPOSALS}" \

internal/scaffold/fullsend-repo/scripts/post-retro.sh

@@ -93,6 +93,15 @@ for i in $(seq 0 $((PROPOSAL_COUNT - 1))); do
     echo "::warning::proposal[$i] targets a .fullsend repo (${TARGET_REPO}). Filing in .fullsend repos is discouraged until per-repo customization patterns are stable. Consider filing in the source repo or fullsend-ai/fullsend upstream instead."
   fi
 
+  # Ensure the label exists in the target repo before applying it.
+  # Follows the same pattern as post-review.sh for ready-for-merge.
+  # --force makes this idempotent (no error if the label already exists).
+  gh label create "ready-for-triage" \
+    --repo "${TARGET_REPO}" \
+    --description "Retro-filed issue awaiting triage agent" \
+    --color "ededed" \
+    --force 2>/dev/null || true
+
   echo "Filing issue in ${TARGET_REPO}: ${TITLE}"
   if ! ISSUE_URL=$(gh issue create \
     --repo "${TARGET_REPO}" \