[plan] Remove 'experimental' label from Claude/Codex engines documentation

[github-actions]

Context

As identified in discussion #12027 (Claude Code User Documentation Review), the "experimental" label on Claude and Codex engines creates unnecessary perception of instability, despite evidence of production viability (29 Claude workflows and 9 Codex workflows exist in the repository).

Current State

In docs/src/content/docs/reference/engines.md:12, there is a banner stating:

"Claude and Codex engines are available but marked as experimental. They are not documented here but can still be used by setting engine: claude or engine: codex in your workflow frontmatter. For production workflows, we recommend using the GitHub Copilot CLI engine."

Problem

• Creates perception that Claude/Codex are unstable or risky
• Discourages production use despite evidence of stability
• States "not documented here" which is confusing (they ARE documented in the same file)
• Contradicts repository evidence (29 Claude workflows in active use)

Objective

Replace the "experimental" warning with a neutral, welcoming note about multi-engine support.

Proposed Solution

Replace the current experimental banner with:

> [!NOTE]
> Multiple AI Engines Supported
> GitHub Agentic Workflows supports multiple AI engines: GitHub Copilot CLI (default), Anthropic Claude, and OpenAI Codex. All engines support the same tools, triggers, and safe outputs. Choose the engine that best fits your needs and API access.

Files to Modify

• docs/src/content/docs/reference/engines.md (line 12 area)

Acceptance Criteria

• Remove "experimental" language from engines.md
• Replace with neutral multi-engine note
• Verify documentation renders correctly
• No changes to actual engine functionality (docs-only change)

References

• Discussion 🔍 Claude Code User Documentation Review - January 27, 2026 #12027 - Priority 1 recommendation
• Evidence: 29 Claude workflows, 9 Codex workflows in repository

AI generated by Plan Command for discussion #12027

[github-actions]

🍪 Issue Monster has assigned this to Copilot!

I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot agent.

The Copilot agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

AI generated by Issue Monster