post-triage.sh does not apply bug label for bug-category issues

[rh-hemartin]

The sufficient action handler in post-triage.sh applies category-specific labels for feature (adds feature + triaged) but does not add a bug label when triage_summary.category is "bug". It only defers ready-to-code.

This means the bug label only appears if the agent happens to include it in label_actions, which is non-deterministic. The feature path is deterministic because the post-script handles it directly.

Observed in CI: functional-tests on PR #54 failed with required_labels pass rate 75% (3/4). Case 001-bug-url-encoding expects both ready-to-code and bug, but only got ready-to-code. The agent result had category: "bug" with no label_actions for bug.

Fix: Split bug out of the bug|documentation|performance case branch at line 318 and explicitly add_label "bug". Same pattern as the feature branch. Also update post-triage-test.sh: add a sufficient-bug-gets-bug-label test, add bug to the mock label list, and change the nonexistent-label test fixture from bug to a truly nonexistent label name.

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 9:56 AM UTC · Completed 9:59 AM UTC
Commit: e8381e3 · View workflow run →

[fullsend-ai-triage]

Triage Summary

Severity: Medium · Category: Bug

Problem

The sufficient action handler in post-triage.sh applies a feature label deterministically for feature-category issues but does not apply a bug label for bug-category issues. The bug|documentation|performance case branch only defers ready-to-code without adding category-specific labels.

Root Cause

In post-triage.sh (~line 320), the case branch groups bug|documentation|performance together and only sets DEFERRED_LABEL="ready-to-code". The feature branch calls add_label "feature" explicitly, creating an asymmetry where bug-category issues miss their label.

Recommended Fix

1. post-triage.sh: Split bug into its own case branch that calls add_label "bug" and defers ready-to-code
2. post-triage-test.sh: Add bug to the mock label list, add a sufficient-bug-gets-bug-label test, and change the nonexistent-label test fixture from bug to a truly nonexistent name

Proposed Test

# Test: sufficient action with category "bug" applies bug label
run_test "sufficient-bug-gets-bug-label" \
  '{"action":"sufficient",...,"triage_summary":{...,"category":"bug",...},...}' \
  "gh api repos/test-org/test-repo/issues/42/labels -f labels[]=bug --silent"

# Update mock label list to include "bug":
# printf '%s\n' "area/api" "area/cli" "priority/high" "component/parser" "enhancement" "bug"

# Update nonexistent-label test to use a truly nonexistent label:
run_test_stdout "label-actions-nonexistent-label-skipped" \
  '{...,"label_actions":{...,"actions":[{"action":"add","label":"does-not-exist"}]}}' \
  "::warning::Skipping label 'does-not-exist' -- does not exist in repo (will not auto-create)"

---

Labels: This is a confirmed bug in the post-triage script's label application logic.

[fullsend-ai-coder]

🤖 Code · ❌ Terminated · Started 10:00 AM UTC · Ended 10:11 AM UTC
Commit: e8381e3 · View workflow run →

[rh-hemartin]

Rerun of the same commit passed: https://github.com/fullsend-ai/agents/actions/runs/29083643579 — the agent happened to include bug in label_actions this time. Confirms the non-determinism.

[fullsend-ai-coder]

🤖 Finished Code · ✅ Success · Started 10:00 AM UTC · Completed 10:11 AM UTC
Commit: e8381e3 · View workflow run →