fix(initiative-planner): restore discussion→workflow_dispatch redispatch bridge

[don-petry]

Problem

Labelling an Ideas Discussion idea:approved — the documented primary trigger for the planner — fails and never plans the initiative. The run fires correctly but dies inside the Claude action step:

##[error]Action failed with error: Unsupported event type: discussion

This was observed on Discussion #650 (planner run 27479891465, DISCUSSION_NUMBER: 650).

Root cause — a silently reverted fix

This bug was already identified (#591) and fixed (#618, 6feb0fe) with a redispatch bridge job: on a discussion [labeled] event the planner resolves the discussion number and re-invokes itself via workflow_dispatch (which claude-code-action does support); the plan job then runs only on workflow_dispatch.

PR #606 (0407ea5, an unrelated pr-review oversized-PR change) was branched off main before #618 landed and, on merge, silently reverted the entire fix — deleting:

• the redispatch job in initiative-planner.yml (restoring the broken direct-on-discussion if)
• scripts/initiative-planner/redispatch.sh
• tests/test_initiative_planner_redispatch.bats

The later dependabot bump #640 (claude-code-action → v1.0.148) only touched the action SHA; it did not cause the regression.

Fix

Restore #618 verbatim, preserving the current claude-code-action v1.0.148 pin from #640:

• re-add the redispatch job; plan runs only on workflow_dispatch
• restore scripts/initiative-planner/redispatch.sh
• restore tests/test_initiative_planner_redispatch.bats
• restore the README rows for redispatch.sh and its test

The resulting initiative-planner.yml is byte-identical to the post-#618 version except for the action SHA. shellcheck clean.

After merge

Re-trigger Discussion #650 (remove + re-add idea:approved, or dispatch the planner manually with discussion: 650) and it will plan.

Note: the redispatch path requires GH_PAT_WORKFLOWS — a workflow_dispatch fired with the default GITHUB_TOKEN is accepted but never starts a run. The job guards for the PAT and fails loudly if it's missing.

https://claude.ai/code/session_01WRJisJyfNK2CuR4f1n9cao

---

Generated by Claude Code

Summary by CodeRabbit

• New Features

  • Added a new approval-to-run flow that automatically re-dispatches the initiative planning workflow when the right label is applied.
  • Improved handling of manual run inputs so discussion details and dry-run settings are passed consistently.

• Bug Fixes

  • Prevented the planning job from running in unsupported event contexts.
  • Added validation and safer input handling for automated dispatches.

• Documentation

  • Updated setup notes to reflect the new re-dispatch step and expanded test coverage.

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: a7201ac2-2df6-4cf9-accd-296e8df75436

📥 Commits

Reviewing files that changed from the base of the PR and between a682741 and 5c89204.

📒 Files selected for processing (4)

• .github/workflows/initiative-planner.yml
• scripts/initiative-planner/README.md
• scripts/initiative-planner/redispatch.sh
• tests/test_initiative_planner_redispatch.bats

---

📝 Walkthrough

Walkthrough

Adds redispatch.sh, a Bash bridge script that re-dispatches the initiative-planner workflow under workflow_dispatch when a discussion event with the idea:approved label is received. The GitHub Actions workflow gains a redispatch job for this trigger and tightens the plan job to workflow_dispatch only, with updated env var wiring. A Bats test suite and README update accompany the new script.

Changes

Initiative Planner Redispatch Bridge

Layer / File(s)	Summary
redispatch.sh script scripts/initiative-planner/redispatch.sh	New Bash helper that validates REPO and DISCUSSION_NUMBER, derives a dry_run boolean string, optionally builds --ref flags from GITHUB_REF for branch/tag refs, and calls gh workflow run to dispatch initiative-planner.yml with discussion and dry_run inputs.
Workflow redispatch job and plan job wiring .github/workflows/initiative-planner.yml	Adds a redispatch job gated on discussion events labeled idea:approved that validates GH_PAT_WORKFLOWS and calls redispatch.sh. Restricts the existing plan job to workflow_dispatch only and updates env wiring so DISCUSSION_NUMBER comes from dispatch inputs and DRY_RUN is computed solely from inputs.dry_run.
Bats tests and README tests/test_initiative_planner_redispatch.bats, scripts/initiative-planner/README.md	Full Bats test suite covering happy-path dispatch arguments, input validation failures (unset/non-numeric DISCUSSION_NUMBER, unset REPO), WORKFLOW_FILE override, DRY_RUN normalization (1/true → dry_run=true), and GITHUB_REF --ref forwarding only for branch/tag refs. README updated to document redispatch.sh and the new test file.

Sequence Diagram

sequenceDiagram
  participant GH as GitHub (discussion labeled)
  participant RDJob as redispatch job
  participant Script as redispatch.sh
  participant GHCLI as gh CLI
  participant PlanJob as plan job (workflow_dispatch)

  GH->>RDJob: discussion [labeled: idea:approved]
  RDJob->>RDJob: validate GH_PAT_WORKFLOWS secret present
  RDJob->>Script: run with REPO, DISCUSSION_NUMBER, DRY_RUN, GITHUB_REF
  Script->>Script: validate inputs, derive dry_run string, build optional --ref
  Script->>GHCLI: workflow run initiative-planner.yml --repo REPO -f discussion=N -f dry_run=bool
  GHCLI->>PlanJob: triggers workflow_dispatch run
  PlanJob->>PlanJob: reads DISCUSSION_NUMBER from inputs.discussion, DRY_RUN from inputs.dry_run

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related issues

• bug: stale-base merge (#606) silently reverted the initiative-planner discussion→dispatch fix (#618); idea:approved stopped planning #655: This PR directly restores and implements the discussion→dispatch bridge (redispatch job, redispatch.sh, and Bats tests) that the linked issue describes as having been reverted.

Suggested labels

initiative

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and specifically describes the main change: restoring the discussion→workflow_dispatch redispatch bridge for the initiative-planner workflow.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/discussion-initiative-dev-lead-flow-0qv7nu

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[don-petry]

Dev-Lead — review-changes (no-changes)

No changes were needed for this PR.

[gemini-code-assist]

Code Review

This pull request introduces redispatch.sh to bridge the discussion [labeled] event to a workflow_dispatch event, bypassing the limitation where claude-code-action aborts on discussion events. It also updates the README and adds comprehensive BATS unit tests. The reviewer provided several constructive suggestions to improve the Bash script, including strictly validating the discussion number as a positive integer, making the DRY_RUN check case-insensitive, and using standard glob pattern matching instead of regular expressions for prefix matching on GITHUB_REF.

[don-petry]

Dev-Lead — fix-bot-comment (no-changes)

Agent reasoning

Issues addressed: 0
Files changed: 4
- .github/workflows/initiative-planner.yml
- scripts/initiative-planner/README.md
- scripts/initiative-planner/redispatch.sh
- tests/test_initiative_planner_redispatch.bats
No actionable issues found. Quality gate passed with zero new issues and zero security hotspots.
```

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[don-petry]

Dev-Lead — fix-bot-comment (no-changes)

Agent reasoning

Issues addressed: 0
- Codex usage limit notification: not actionable code feedback
Tier 1 blockers: 0
Status: PR is ready — no code changes required
```
The PR can proceed. The bot simply ran out of review quota; this is not a code defect or blocker.

[don-petry]

Dev-Lead — review-changes (applied)

Changes committed and pushed.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[don-petry]

Dev-Lead — waiting on PR blockers (intent: review-changes)

PR: #654
No changes were committed, but the PR still has blocking checks or reviews (failing or cancelled checks, or changes-requested reviews). The retry cron will re-attempt automatically. Next attempt after: 2026-06-13T23:13:16Z

[don-petry]

Note

@don-petry I reviewed this PR and no code changes were needed, but it still has blocking checks or reviews (failing or cancelled checks, or changes-requested reviews), so I cannot mark it done yet. I'll re-check automatically.
Next attempt after: 2026-06-13T23:13:16Z