UI rereview team path does not actually target Kodiai

[keithah]

Summary

The documented UI rereview path says operators can request review from ai-review / aireview to trigger Kodiai, but in practice Kodiai is not actually part of that team path, so the UI rerereview workflow does not work as advertised.

Problem

Current runbooks and handler behavior imply this flow is valid:

• request review from ai-review / aireview
• expect Kodiai to treat the resulting pull_request.review_requested as a manual rereview trigger

In practice, the operator report is that this does not work because Kodiai is not actually a member/target of that team path.

Impact

• UI-based rerereview is misleading/broken for operators
• debugging gets harder because the documented manual trigger path is not actually available
• operators must fall back to comment-based triggers like @kodiai review

Expected

Either:

1. ai-review / aireview is a real working team-based trigger path for Kodiai, or
2. docs/config/behavior stop claiming that it is.

Suggested follow-up

• verify the real GitHub reviewer/team topology
• decide whether to wire Kodiai into a real rereview team path or remove the team-based path from docs/config
• add an operator proof test or runbook check so this cannot silently drift again

[keithah]

Status update: still open, still real.\n\nWe fixed the comment-based explicit review path () and deployed it, but this UI rereview path is separate. The current runbooks still describe / as a valid rereview trigger, and the operator report is that it does not actually target Kodiai in practice.\n\nI think this is the highest-priority remaining open issue in the repo because it leaves a documented operator path that does not work as advertised. The follow-up should be one of:\n1. wire Kodiai into a real working reviewer/team path, or\n2. remove the team-based rereview path from docs/config/tests and make the comment-based trigger the only supported manual rereview path.\n\nUntil one of those is done, operators should treat as the supported manual trigger.

[keithah]

Correction: the previous status comment dropped some literal trigger/team names due to shell quoting.

Clean version:

We fixed the comment-based explicit review path (@kodiai review) and deployed it, but this UI rereview path is separate. The current runbooks still describe ai-review / aireview as a valid rereview trigger, and the operator report is that it does not actually target Kodiai in practice.

Until this is fixed, operators should treat @kodiai review as the supported manual trigger.

[kodiai]

kodiai response

Confirmed — the UI team-based rereview path (ai-review / aireview) is fully wired in code but not working in practice, while the comment-based path (kodiai review) is fixed and deployed.

Current state from codebase:

The team-based rereview implementation exists across multiple layers:

• Handler gate: src/handlers/review.ts:1396 hardcodes the team slugs and src/handlers/review.ts:1514 checks incoming review_requested events for team match
• Config: .kodiai.yml:4 sets uiRereviewTeam: aireview
• Runbook: docs/runbooks/review-requested-debug.md:10,182 documents the team trigger as valid
• Helper module: src/handlers/rereview-team.ts provides team request logic with fallback from aireview → ai-review on 422

The code will accept and process the webhook if it arrives, but the operator evidence shows the GitHub org/team/webhook layer isn't delivering the event to Kodiai.

Decision needed:

Which path do you want?

(1) Fix the GitHub org setup — create/configure the ai-review or aireview team so UI re-requests actually trigger the webhook
(2) Remove the team path — strip uiRereviewTeam from config, remove the team gate code, and update runbooks to document kodiai review as the only manual trigger

If you choose (1), I can investigate the current GitHub org team state and identify what's missing. If you choose (2), I can remove the team-based path from code, config, tests, and docs.