Reconcile contradictory insufficient-action rules in triage prompt

[guyoron1]

What happened

The triage prompt contains contradictory rules about when to use action: "insufficient":

1. Question classification (from PR fix(#2024): triage agent must not ask reporters implementation questions fullsend-ai/fullsend#2214): Only use insufficient for implementation-facing questions if the gap "materially prevents triage"
2. Anti-premature-resolution HARD CONSTRAINT (~line 146): MUST use insufficient for "ANY open questions or information gaps — regardless of whether they seem minor"

These directly contradict each other.

Proposed change

In internal/scaffold/fullsend-repo/agents/triage.md, scope the anti-premature-resolution HARD CONSTRAINT to user-facing information gaps. Change the rule from "ANY open questions or information gaps" to "ANY open user-facing questions or information gaps." Add an explicit carve-out: implementation-facing questions that cannot be self-resolved should be noted in reasoning but do not require action: "insufficient" unless they materially prevent triage.

Validation criteria

1. The triage prompt contains no contradictory instructions about action: "insufficient"
2. In the next 5 triage runs on issues with implementation-facing ambiguity, the agent should proceed with best-available information

---

Mirrored from fullsend-ai#2237

[guyoron1]

/fs-triage

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 3:30 PM UTC · Completed 3:32 PM UTC
Commit: bb5c185 · View workflow run →

[fullsend-ai-triage]

Triage Summary

Status: Fix already applied

The contradiction described in this issue has already been resolved in the current codebase. In internal/scaffold/fullsend-repo/agents/triage.md (line 146), the anti-premature-resolution HARD CONSTRAINT now reads:

If your assessment identifies ANY open user-facing questions or information gaps...

It also includes the explicit carve-out:

Implementation-facing questions that cannot be self-resolved from repository context should be noted in reasoning but do not require action: "insufficient" unless they materially prevent triage.

This aligns with the question-classification section and eliminates the contradiction.

Validation criteria

The issue's second validation criterion — observing 5 triage runs where the agent proceeds with best-available information on implementation-facing ambiguity — can be tracked separately or verified against recent triage runs.

Recommendation

This issue can likely be closed as already resolved. If the validation criteria need formal tracking, consider converting them into a follow-up task.

Test case: Submit an issue with clear symptoms but ambiguous internal
component ownership. Verify the triage agent emits action: "sufficient"
(noting the ambiguity in reasoning) rather than action: "insufficient"
with an implementation-facing question directed at the reporter.

---

Labels: This issue targets triage prompt documentation and the fix is already applied in the codebase.

[fullsend-ai-coder]

🤖 Finished Code · ✅ Success · Started 3:35 PM UTC · Completed 3:37 PM UTC
Commit: bb5c185 · View workflow run →