fix: upgrade to ai-workflows@v2.0.0 (claude-code-action@v1 GA)

[sfreudenthaler]

Summary

Migrates to dotCMS/ai-workflows@v2.0.0 which upgrades the underlying anthropics/claude-code-action from @beta to @v1 GA.

All three Claude jobs updated:

• claude-interactive: @v1.0.0 → @v2.0.0, allowed_tools → claude_args
• claude-automatic-review: @v1.0.0 → @v2.0.0, direct_prompt → prompt, allowed_tools → claude_args
• claude-rollback-safety-check: already on @v2.0.0 but still had old direct_prompt/allowed_tools — fixed

Breaking changes handled

Before	After
direct_prompt:	prompt:
allowed_tools: (multiline)	claude_args: '--allowedTools "..."'
@v1.0.0 ref	@v2.0.0 ref

New behavior (from v2.0.0)

• Sticky comments: Claude updates a single comment instead of spamming new ones
• Progress tracking: Posts progress updates during automation runs

Test plan

• Open a test PR without @claude mention → verify automatic review runs
• Comment @claude on a PR → verify interactive mode triggers
• Confirm single sticky comment is updated (not multiple new comments)

🤖 Generated with Claude Code

[github-actions]

❌ Issue Linking Required

This PR could not be linked to an issue. All PRs must be linked to an issue for tracking purposes.

How to fix this:

Option 1: Add keyword to PR body (Recommended - auto-removes this comment)
Edit this PR description and add one of these lines:

• This PR fixes #123 or Fixes: #123

• This PR closes #123 or Closes: #123

• This PR resolves #123 or Resolves: #123

• Other supported keywords: fix, fixed, close, closed, resolve, resolved
  Option 2: Link via GitHub UI (Note: won't clear the failed check)

1. Go to the PR → Development section (right sidebar)

2. Click "Link issue" and select an existing issue

3. Push a new commit or re-run the workflow to clear the failed check
   Option 3: Use branch naming
   Create a new branch with one of these patterns:

• 123-feature-description (number at start)

• issue-123-feature-description (issue-number at start)

• feature-issue-123 (issue-number anywhere)

Why is this required?

Issue linking ensures proper tracking, documentation, and helps maintain project history. It connects your code changes to the problem they solve.---

This comment was automatically generated by the issue linking workflow