From 5913f3fc03621fae062da0ddeb3f8c0ecaf1c7bd Mon Sep 17 00:00:00 2001
From: Sebastian Szewczyk <sebryu@gmail.com>
Date: Fri, 1 May 2026 21:34:49 +0200
Subject: [PATCH] ci: remove broken oz-for-oss adapter workflows superseded by
 webhook

Removes two GitHub Actions adapters whose upstream reusable workflows in
warpdotdev/oz-for-oss were deleted by their PR #400 on 2026-04-30:

- .github/workflows/respond-to-triaged-issue-comment-local.yml
- .github/workflows/comment-on-unready-assigned-issue-local.yml

Both have been failing on every trigger since the upstream deletion. The
oz-for-oss maintainer confirmed the deletions were intentional and asked
us to remove the warp-side adapters; respond-to-triaged-issue-comment is
already covered by the new Vercel webhook (verified empirically on
issues 8642/9576/9688 with sub-15s bot response latency post-cutover),
and comment-on-unready-assigned-issue is being rewired upstream.

Three other broken adapters (update-dedupe, update-pr-review,
update-triage) are intentionally left in place pending confirmation
from oz-for-oss on the replacement scheduled agents.

Refs: warpdotdev/oz-for-oss#418
---
 ...omment-on-unready-assigned-issue-local.yml | 16 --------------
 ...respond-to-triaged-issue-comment-local.yml | 22 -------------------
 2 files changed, 38 deletions(-)
 delete mode 100644 .github/workflows/comment-on-unready-assigned-issue-local.yml
 delete mode 100644 .github/workflows/respond-to-triaged-issue-comment-local.yml

diff --git a/.github/workflows/comment-on-unready-assigned-issue-local.yml b/.github/workflows/comment-on-unready-assigned-issue-local.yml
deleted file mode 100644
index 9b4b39bae..000000000
--- a/.github/workflows/comment-on-unready-assigned-issue-local.yml
+++ /dev/null
@@ -1,16 +0,0 @@
-name: Comment on Unready Assigned Issue (Local)
-on:
-  issues:
-    types: [assigned]
-concurrency:
-  group: comment-on-unready-assigned-issue-${{ github.event.issue.number || github.run_id }}
-  cancel-in-progress: false
-jobs:
-  comment_when_unready:
-    if: github.event.assignee.login == 'oz-agent' && !contains(github.event.issue.labels.*.name, 'ready-to-spec') && !contains(github.event.issue.labels.*.name, 'ready-to-implement')
-    permissions:
-      issues: write
-    uses: warpdotdev/oz-for-oss/.github/workflows/comment-on-unready-assigned-issue.yml@main
-    secrets:
-      OZ_MGMT_GHA_APP_ID: ${{ secrets.OZ_MGMT_GHA_APP_ID }}
-      OZ_MGMT_GHA_PRIVATE_KEY: ${{ secrets.OZ_MGMT_GHA_PRIVATE_KEY }}
diff --git a/.github/workflows/respond-to-triaged-issue-comment-local.yml b/.github/workflows/respond-to-triaged-issue-comment-local.yml
deleted file mode 100644
index c47b9e45b..000000000
--- a/.github/workflows/respond-to-triaged-issue-comment-local.yml
+++ /dev/null
@@ -1,22 +0,0 @@
-name: Respond to Triaged Issue Comment (Local)
-on:
-  issue_comment:
-    types: [created]
-concurrency:
-  group: respond-to-triaged-issue-comment-${{ github.event.comment.id || github.run_id }}
-  cancel-in-progress: false
-jobs:
-  # Mention, bot, event-type, and trust gates all live in the reusable
-  # workflow (``respond-to-triaged-issue-comment.yml``). This adapter
-  # exists only to subscribe to the GitHub event that can carry an
-  # ``@oz-agent`` mention on a triaged issue and delegate it through
-  # ``workflow_call``.
-  respond_inline:
-    permissions:
-      contents: read
-      issues: write
-    uses: warpdotdev/oz-for-oss/.github/workflows/respond-to-triaged-issue-comment.yml@main
-    secrets:
-      OZ_MGMT_GHA_APP_ID: ${{ secrets.OZ_MGMT_GHA_APP_ID }}
-      OZ_MGMT_GHA_PRIVATE_KEY: ${{ secrets.OZ_MGMT_GHA_PRIVATE_KEY }}
-      OSS_WARP_API_KEY: ${{ secrets.OSS_WARP_API_KEY }}