ci: remove broken oz-for-oss adapter workflows superseded by webhook

[sebryu]

Summary

Removes two GitHub Actions adapter workflows that delegate to reusable workflows in warpdotdev/oz-for-oss that no longer exist:

• .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 2026-04-30, when warpdotdev/oz-for-oss#400 deleted the upstream targets as part of migrating to a Vercel webhook control plane.

Context

The oz-for-oss maintainer confirmed the upstream deletions were intentional and asked us to remove the warp-side adapters rather than restoring upstream. Per-workflow disposition (her words):

• respond-to-triaged-issue-comment — "covered by the issue_comment hook" of the new Vercel webhook.
• comment-on-unready-assigned-issue — "currently being rewired" upstream.

Root-cause issue: warpdotdev/oz-for-oss#418.

Verification

Empirical confirmation that the new webhook is live and handling @oz-agent mentions on triaged warp issues — sub-15s response latency from the oz-for-oss bot, well below GHA cold-start times:

• Issue Renaming Conversations #8642 (2026-05-01 15:24 UTC): @oz-agent → bot reply 13s later
• Issue Show current zoom level (%) when zooming in/out #9576 (2026-04-30 23:33 UTC): @oz-agent → bot reply 8s later
• Issue Right-clicking anywhere in terminal input should open the prompt editor #9688 (2026-04-30 23:33 UTC): @oz-agent → bot reply 8s later

Meanwhile every fire of respond-to-triaged-issue-comment-local.yml since 2026-04-30 has logged failure (e.g. run 25207261218) — the GHA path is purely noise.

For comment-on-unready-assigned-issue there is a brief coverage gap until oz-for-oss finishes rewiring the issues.assigned event handler. Failing-and-noisy is worse than absent, so removing now improves signal.

Scope note

Three additional broken adapters exist for update-dedupe, update-pr-review, update-triage (weekly scheduled skill-refresh workflows). Those are intentionally left in place pending confirmation from oz-for-oss on whether the new control plane runs equivalent scheduled jobs against warp, or whether the replacement scheduled agents are still upcoming work. Those three have never executed for warp (gh run list returns [] for each), so leaving them does not affect any current automation.

Test plan

• No required status checks affected — verified via repo ruleset 15469325; only Check CI results is required.
• No PRs blocked: these workflows trigger on issue_comment and issues, never on pull_request.
• Empirical webhook coverage verified for respond-to-triaged-issue-comment (see Verification).
• Reviewer to sanity-check that removing these workflows is acceptable given the brief coverage gap for comment-on-unready-assigned-issue flagged above.

[oz-for-oss]

@sebryu

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I reviewed this pull request and requested human review from: @warpdotdev/oss-maintainers.

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[captainsafia]

LGTM!

@sebryu What agent did you use to do this and what was your prompt? I'm intrigued by the way the agent did verification on this task (analyzing response times) and am curious if you did something intentional here to guide it to this approach.

[oz-for-oss]

Overview

This PR removes two GitHub Actions adapter workflows that delegated issue automation to upstream reusable workflows that no longer exist.

Concerns

• No blocking concerns found in the changed workflow deletions.
• Security pass: removing these adapters also removes workflow paths that passed repository secrets into deleted external reusable workflows; no new secret exposure or permission expansion was introduced.
• Stakeholder matching: the changed .github/workflows paths only match the catch-all team rule, so no single eligible human reviewer could be identified from the provided rules.

Verdict

Found: 0 critical, 0 important, 0 suggestions

Approve

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[sebryu]

@captainsafia I've sent you a DM on X