[Phase 4] Release the reusable feature-ideation change via its channel tag #1213

Story

As a Release Manager,
I want ship the feature-ideation-reusable.yml family-default change to consumers through its normal channel-tag release process, without hand-moving tags,
so that adopting repos pick up the family default in lockstep through the release channel rather than through ad-hoc tag edits.

Acceptance Criteria

1. The feature-ideation-reusable.yml change ships to consumers through its channel tag via the Release Manager's normal release process.
2. Tags are NOT hand-moved; the Release Manager owns tag movement.
3. Behaviour matches ci-standards.md section 9: @main repos pick up the change on their next scheduled run; @v1-pinned repos pick it up only after the v1 tag is advanced, then on their next run.

Tasks / Subtasks

• Once Stories 2-4 have merged, trigger the Release Manager's channel-tag release for the reusable change (no manual tag moves). (AC: Addressing PR comments #1, Add multi-agent isolation strategy using git worktrees #2)
• Confirm the v1 tag advance propagates per the ci-standards section 9 tag model and note it in the release. (AC: Add coding standards & principles section to AGENTS.md #3)

Dev Notes

• HUMAN/Release-Manager action - hands_off. Idea AC feat: add Structured Logging and CQRS standards #6: "The reusable change ships through its channel tag via the Release Manager as usual. Don't hand-move tags."
• ci-standards.md section 9 documents the tag model: repos tracking @main pick up changes on their next scheduled run; repos pinned to @v1 only after v1 is advanced to the new release and then on their next run.
• Blocked on Stories 2, 3 and 4 so the release bundles the completed workflow change plus its docs and lint, not a partial state.

Project Structure Notes

No repo file edits by an agent - this is the org release process (tag advance) for an already-merged change.

References

• https://github.com/petry-projects/.github/blob/main/standards/ci-standards.md
• discussion Standard Proposal: name a model family, never pin a model version #1199

Likely target surface

• petry-projects/.github: release channel tag (v1) for feature-ideation-reusable.yml

Story prepared by the BMAD Scrum Master (Bob) for epic #1208. Status: ready-for-dev.