self-development: scope kelos-planner, kelos-reviewer, and kelos-api-reviewer with commentOn

[kelos-bot]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Adds the commentOn filter field (introduced in #1081) to the three remaining webhook-driven TaskSpawners that previously relied on prompt-side workarounds or no guard at all:

• kelos-planner.yaml — adds commentOn: Issue to the issue_comment filter and deletes the now-redundant ### 0. Confirm the target is an issue prompt block. /kelos plan typed on a PR is now rejected at the webhook layer instead of spawning an Opus task that bails at step 0.
• kelos-reviewer.yaml — adds commentOn: PullRequest to the issue_comment filter. /kelos review typed on a plain issue can no longer spawn a task whose prompt unconditionally calls gh pr view and git diff origin/main...HEAD. The pull_request_review filter entry is already PR-only by event type, so no change is needed there.
• kelos-api-reviewer.yaml — splits the issue_comment filter into two entries with explicit commentOn: Issue and commentOn: PullRequest. This spawner is intentionally dual-mode (the prompt dispatches on gh pr view to handle both issues and PRs), so the filter cannot collapse to a single subject; two explicit filters make the dual-mode intent visible at the webhook layer instead of relying on commentOn being absent.

kelos-squash-commits.yaml already gained commentOn: PullRequest in 1a61816, so no further change is needed for that spawner.

After this change, every webhook-driven TaskSpawner declares its intended subject at the filter layer.

Which issue(s) this PR is related to:

Fixes #1089

Special notes for your reviewer:

• Supersedes Configuration Alignment: kelos-reviewer accepts /kelos review on plain issues — missing PR-vs-issue guard and unsafe branch template #1060 (the older proposal to add a step-0 prompt guard plus a safer branch fallback for kelos-reviewer); Configuration Alignment: kelos-reviewer accepts /kelos review on plain issues — missing PR-vs-issue guard and unsafe branch template #1060 can be closed once this lands.
• The kelos-reviewer branch template already uses the safe {{with index . "Branch"}}{{.}}{{else}}main{{end}} fallback, so no change is needed there.
• For kelos-api-reviewer, the prompt-side gh pr view dispatch is retained because both subjects are accepted on the same event/bodyPattern and the prompt still needs to know which subject it is handling.

Does this PR introduce a user-facing change?

NONE

[kelos-bot]

🤖 Kelos Worker Agent @gjkim42

Review Summary

Verdict: COMMENT (cannot self-approve)
Overall correctness: patch is correct
Scope: Adds commentOn to the issue_comment filters of kelos-planner (Issue) and kelos-reviewer (PullRequest), and deletes the now-redundant step-0 PR-vs-issue guard from the planner prompt. Completes the cleanup deferred by #1081 / partially started in 1a61816.

Findings Overview

Priority	Count	File:Line	Summary
P0	0	—	none
P1	0	—	none
P2	0	—	none
P3	0	—	none

Key takeaways

• Both filter values (Issue, PullRequest) match the +kubebuilder:validation:Enum=Issue;PullRequest marker on WebhookFilter.CommentOn (api/v1alpha1/taskspawner_types.go:484).
• Removing the ### 0. Confirm the target is an issue block from kelos-planner.yaml is safe — the filter now enforces the same constraint at the webhook layer, and no other prompt step depends on that guard.
• kelos-reviewer.yaml's branch template already uses the safe {{with index . "Branch"}}{{.}}{{else}}main{{end}} fallback (line 82), so no additional change is needed there.
• kelos-squash-commits.yaml is correctly out of scope — it already got commentOn: PullRequest in 1a61816 (verified at line 16).
• /kind cleanup + release-note: NONE is the right classification for a self-development/-only change.

[gjkim42]

Let'a apply this to kelos api reviewer as well
/kelos pick-up

[kelos-bot]

🤖 Kelos Task Status

Task kelos-pr-responder-pull-request-review-542771071540 has succeeded. ✅

[kelos-bot]

🤖 Kelos Agent @gjkim42

All review feedback was addressed in commit ba5c0c6 (added commentOn filters to kelos-api-reviewer.yaml with the dual-mode pattern). PR title and body are updated; CI checks (build, verify, test, test-integration) are green. Ready for re-review.

[gjkim42]

Does kelos api reviewer work for an issue as well? (Based on the prompt?)

/kelos pick-up
then squash commits

[kelos-bot]

🤖 Kelos Task Status

Task kelos-pr-responder-pull-request-review-b36ee724e682 has succeeded. ✅