Stabilize meeting-agenda workflow by targeting the created issue directly

[Copilot]

The meeting agenda workflow intermittently failed because the update step resolved the target issue via gh issue list --limit 1, which is non-deterministic when multiple open meeting issues exist. This change makes issue selection deterministic by wiring the update step to the exact issue created earlier in the job.

• Root cause addressed: non-deterministic issue lookup

  • Replaced label-based issue discovery in Update meeting date in issue with the issue-number output from peter-evans/create-issue-from-file.

• Workflow wiring update

  • Added id: create-issue to the issue-creation step.
  • Consumed ${{ steps.create-issue.outputs.issue-number }} in the follow-up update step.

• Failure mode hardening

  • Added an explicit guard that exits when issue-number is empty, preventing silent updates against an unintended issue.

- name: Create issue from template
  id: create-issue
  uses: peter-evans/create-issue-from-file@v6

- name: Update meeting date in issue
  run: |
    ISSUE_NUMBER="${{ steps.create-issue.outputs.issue-number }}"
    if [ -z "$ISSUE_NUMBER" ]; then
      echo "Failed to get issue number from create issue step."
      exit 1
    fi
    # ...update body for ISSUE_NUMBER

[netlify]

✅ Deploy Preview for angry-raman-7c44f6 canceled.

Name	Link
🔨 Latest commit	87f2c59
🔍 Latest deploy log	https://app.netlify.com/projects/angry-raman-7c44f6/deploys/6a3d06d293f50d0007578041