[Phase 3] Cut ci-failure-analyst v1.0.0 + stable tags and extend the channel ruleset

[github-actions]

Story

As a OrganizationAdmin,
I want cut the immutable and channel release tags for ci-failure-analyst and bring them under the release-channel-tags ruleset,
so that callers have a real, protected channel tag to pin to, with the same supply-chain guarantees as the agent channels.

Acceptance Criteria

1. Immutable ci-failure-analyst/v1.0.0 is cut from an on-main commit via scripts/cut-release.sh and pushed.
2. Moving ci-failure-analyst/stable is created pointing at the same commit and pushed.
3. The release-channel-tags repository ruleset target set is extended to include ci-failure-analyst/** (update + deletion restricted; bypass limited to OrganizationAdmin and the automation Integration app).

Tasks / Subtasks

• Run cut-release.sh ci-failure-analyst 1.0.0 --channel stable --push from an on-main ref. (AC: test issue from agent #1, Go-live improvements for PR review agent #2)
• Edit the release-channel-tags ruleset to add the ci-failure-analyst/** tag target. (AC: Add @claude delegation, auto-merge, and rebase handling #3)
• Verify the tags resolve and the ruleset blocks non-admin moves. (AC: test issue from agent #1, Go-live improvements for PR review agent #2, Add @claude delegation, auto-merge, and rebase handling #3)

Dev Notes

• HUMAN-GATED: pushing release/channel tags and editing the repository ruleset require OrganizationAdmin per AGENTS.md — the dev-lead/pr-review agents (as GITHUB_TOKEN) cannot move or delete release tags.
• Depends on the generalized cut-release.sh from story id 3.
• Open question (surfaced for the reviewer): cut manually by an admin (as today) vs. via a release workflow — this story assumes the manual admin path.

Project Structure Notes

No file changes in-repo; this is a tag + ruleset operation performed by an admin.

References

• scripts/cut-release.sh
• AGENTS.md#release-channel-tags-the-mutable-ref-exception

Likely target surface

• scripts/cut-release.sh

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