Deploy discussion:created trigger to .github-private feature-ideation workflow (+ bump v1 tag)

[don-petry]

Background

A new Idea Discussion created in petry-projects/.github-private (Discussion #656) did not trigger the Feature Ideation workflow. Root cause: PR #448 (feat: auto-enhance new Ideas Discussions on creation) added the on: discussion: [created] trigger and target_discussion single-idea mode only to the canonical template (standards/workflows/feature-ideation.yml). The live deployed callers were never re-synced, and the v1 tag was never bumped to publish the feature.

PR #457 fixes this repo's own caller + corrects the template pin. This issue tracks the two remaining gaps that could not be done from that session (repo out of scope / tag force-push blocked).

Tasks

1. Deploy the trigger to .github-private

Update .github-private's .github/workflows/feature-ideation.yml to mirror PR #457:

• Add to on::

    discussion:
      types: [created]

• Add the job-level guard as the first line of the ideate: job:

      if: >-
        github.event_name != 'discussion' ||
        (github.event.discussion.category.slug == 'ideas' &&
         github.event.discussion.user.type != 'Bot')

• Add as the first with: input:

        target_discussion: ${{ github.event.discussion.number }}

• Pin the reusable to a SHA that contains the feature: ...feature-ideation-reusable.yml@897e4dede3518cdd7273b9dc63e607d0d05cbdda # v1 (or literal @v1 once the tag is bumped — see task 2).
• Preserve that repo's own project_context / sources_file.
• Confirm GitHub Discussions is enabled with an "Ideas" category.

2. Bump the v1 tag

The v1 tag currently points to d3d768da (2026-05-12), which does not contain the target_discussion reusable commit (f471b21 / #448) — git merge-base confirms neither v1 nor v2 contains it. So every @v1 consumer is on a reusable without single-idea support. Move the tag:

git tag -f v1 897e4dede3518cdd7273b9dc63e607d0d05cbdda && git push origin v1 --force

(Could not be done from the originating session — the push proxy rejects tag force-pushes with 403.)

3. (Optional) Backfill Discussion #656

The trigger only fires on new discussions, so #656 won't retro-fire. After task 1, run the workflow via workflow_dispatch with target_discussion: 656 to enhance it on demand.

References

• PR fix(feature-ideation): deploy discussion:created trigger to live caller + correct reusable pin #457 — caller + template fix in this repo
• PR feat(feature-ideation): auto-enhance new Ideas Discussions on creation #448 — original feature that added the trigger to the template only

https://claude.ai/code/session_01PhN5QmeoX3CkfL6iPkzdzb