feat: implement issue #301 — Compliance: non-stub-feature-ideation.yml

[don-petry]

Closes #301

Implemented by dev-lead agent. Please review.

[chatgpt-codex-connector]

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

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[coderabbitai]

Warning

Review limit reached

@don-petry, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 51 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 0574a894-d3c9-4703-9f15-c4f2f2aa0005

📥 Commits

Reviewing files that changed from the base of the PR and between 8e2a986 and e1af0b2.

📒 Files selected for processing (1)

• .github/workflows/feature-ideation.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dev-lead/issue-301-20260715-0238

---

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.}

[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 — review-changes (no-changes)

No changes were needed for this PR.

[donpetry-bot]

Advisory bots were rate-limited; auto-approval is withheld until they recover. pr-review-sweep will re-review this PR after 2026-07-15T03:42:16Z.

[Copilot]

Pull request overview

This PR aims to remediate Issue #301 by updating the repo’s centralized feature-ideation.yml workflow so it correctly delegates to the org’s reusable Feature Ideation workflow in a compliant, standardized way.

Changes:

• Added new workflow_dispatch inputs (enhance_backlog, target_discussion) and introduced redispatch + prep jobs to bridge discussion:created into workflow_dispatch and to resolve inputs via job outputs.
• Updated the reusable workflow reference and rewired with: values to use needs.prep.outputs.* (including fromJSON casts for booleans).
• Updated comments/docs within the workflow to describe the new bridging behavior and input-resolution approach.

[don-petry]

Auto-rebase is skipping this PR. It has merge conflicts with main but is not review-ready (draft=false, approved=false, auto-rebase:ready=false), so auto-rebase will not update it — and it cannot be approved while red. Left alone it will not progress.

To unblock, do one of:

• add the auto-rebase:ready label (opts it into auto-rebase without an approval), or
• get it approved, or
• resolve manually:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add . && git commit && git push

[don-petry]

Closing as part of the open-PR drain (50-PR automation cap). This branch has real merge conflicts with main and cannot be rebased automatically; the linked compliance issue remains OPEN so dev-lead can regenerate a clean PR once there is cap headroom. No work is lost.