chore: remove throwaway ai-workflows v3.3.3 e2e test workflow

[sfreudenthaler]

Cleanup — removes the scratch workflow added directly to main for e2e-verifying dotCMS/ai-workflows v3.3.3 (see closed PRs #505/#506). Both the happy path (Sonnet 5) and the error-surfacing fix (PR #61) verified working; no longer needed.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[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

[claude]

Claude finished @sfreudenthaler's task in 1m 26s —— View job

---

Claude PR Analysis

• Read doc-object schema + rollback-unsafe categories
• Fetch PR metadata & diff
• Check linked issues / epic match — none (no closes/fixes/resolves in body; epics repo not accessible)
• Generate doc object
• Rollback-safety assessment → 🟢 Safe to Rollback (label added)

---

🟢 Rollback Safety: SAFE

This PR deletes a single throwaway GitHub Actions workflow (.github/workflows/zz-e2e-test-v3.3.3.yml, +0/−47) and nothing else. Checked against every category in ROLLBACK_UNSAFE_CATEGORIES.md:

• No DB migrations (no runonce task, no ADD/DROP/RENAME/ALTER — C-1, C-3, C-4, H-1..H-3, H-6, H-7, M-1 N/A)
• No Elasticsearch mapping changes (C-2 N/A)
• No data model / field type / storage provider changes (H-4, H-5 N/A)
• No REST/GraphQL/OSGi API contract changes (M-3, M-4 N/A)
• No push-publishing bundle format changes (M-2 N/A)

It is a CI-only, test-scaffolding deletion with no product-code or runtime surface. N-1 is entirely unaffected. Applied label: AI: Safe To Rollback.

📄 Doc Object Draft (attached to merge commit post-merge)

---
commit: PLACEHOLDER_SHORT_SHA
title: "chore: remove throwaway ai-workflows v3.3.3 e2e test workflow"
type: chore
module: "CI/CD — GitHub Actions workflows"
customer_visible: no
security_relevant: false
breaking_change: false
pr:
  primary: 507
release_notes:
  audience: skip
  priority: low
  reasoning: "Deletes a throwaway internal CI test workflow with no customer-facing or product behavior effect."
provenance:
  generator: doc-object-skill
  model: claude-opus-4-8-20251001
  prompt_version: v0.1
  generated_at: 2026-07-03T17:24:00Z
  source_pr: 507
  source_diff_sha: PLACEHOLDER_FULL_SHA
---

What changed

Removes .github/workflows/zz-e2e-test-v3.3.3.yml, a scratch GitHub Actions workflow that had been added directly to main to e2e-verify dotCMS/ai-workflows v3.3.3. The workflow only ran on PRs whose title contained the [e2e-v3.3.3] marker and exercised two throwaway jobs (a Sonnet 5 positive case and a bogus-model negative case). Both scenarios were verified working, so the file is deleted. No product code, no CI surface used by normal builds, and no test coverage for dotCMS itself is affected.

Related

Follows the closed test PRs #505 and #506; the error-surfacing behavior it validated was delivered in dotCMS/ai-workflows PR #61.

---

Note: per this repo's single-comment constraint, the doc object is embedded here (inside the extraction markers) rather than as a standalone comment.