Post-triage footer should check for code agent availability before suggesting /fs-code

[fullsend-ai-retro]

What happened

PR #53 added an action-hints footer to triage sufficient comments in scripts/post-triage.sh (lines 517–526) that unconditionally suggests /fs-code and /fs-code <instruction> as next steps. During review, ralphbean commented (Jul 8) that the footer should be conditional on the code agent being installed: "it would be good to do this too, conditionally only when the code agent is installed. We could try to check that in the post script, so that we don't suggest commands for an agent that isn't in place." The multi-agent review squad (waynesun09, Jul 13) independently flagged this as a MEDIUM finding. The PR author acknowledged the gap (Jul 15) but deferred it: "I think this is out of scope, we can open a followup issue as this involves exploring the config, dealing with defaults, etc." No follow-up issue was filed.

What could go better

In repositories that use fullsend for triage but do not have a code agent configured, the triage footer now suggests commands that will not work, creating a confusing user experience. Users would see /fs-code as a suggested next step, try it, and get no response or an error. This is a UX gap that was identified during review but has not been tracked for resolution.

Confidence: high. Both a human reviewer and the multi-agent squad independently identified this gap. The PR author agreed it is valid. The fix requires reading the repo's agent configuration (e.g., config.yaml) in the post-triage script to determine whether a code agent is available.

Proposed change

In scripts/post-triage.sh, modify the sufficient footer block (lines 517–526) to check whether a code agent is configured before appending the /fs-code action hints. The check could:

1. Read the repo's config.yaml (or the equivalent agent configuration source) to determine whether a code agent entry exists.
2. If a code agent is configured, append the current footer with /fs-code suggestions.
3. If no code agent is configured, either omit the footer entirely or append a generic footer without /fs-code suggestions (e.g., just "This issue is ready for implementation").

The implementation needs to handle edge cases: missing config file, config file without an agents section, and the default agent configuration when no explicit config exists.

Validation criteria

After the change: (1) In repos with a code agent configured (like fullsend-ai/agents itself), the triage sufficient footer should still show /fs-code suggestions. (2) In repos without a code agent configured, the triage footer should not suggest /fs-code. This can be validated by running the post-triage script with a mock config that omits the code agent entry and verifying the footer content. A test case should be added to scripts/post-triage-test.sh covering both scenarios.

---

Generated by retro agent from #53

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 8:16 AM UTC · Completed 8:20 AM UTC
Commit: d72d648 · View workflow run →

[fullsend-ai-triage]

Triage Summary

Problem: The post-triage sufficient footer unconditionally suggests /fs-code as a next step, even in repos where no code agent is configured. This creates a confusing experience — users try the suggested command and nothing happens.

Root cause: The action-hints footer block in scripts/post-triage.sh (~line 545) has no conditional guard. It always appends /fs-code suggestions when the action is sufficient.

Recommended fix: Add a code-agent availability check before appending the /fs-code footer. If the code agent is not configured for the target repo, either omit the footer entirely or show a generic "This issue is ready for implementation" message. Handle edge cases: missing config, config without an agents section, and default configuration.

Note: Issue #331 (triage variable to control auto-coding) is related but addresses a different concern — whether triage auto-triggers coding via the ready-to-code label, not whether the footer shows /fs-code hints. Both can coexist.

Proposed test case:

# In scripts/post-triage-test.sh:

# Test 1: With code agent configured → footer includes /fs-code
# (Existing test 'sufficient-appends-action-hints-footer' should continue to pass
#  when the code-agent-available signal is set)

# Test 2: Without code agent configured → footer omits /fs-code
# Simulate no code agent via config/env mechanism
# Assert: comment does NOT contain '/fs-code'
# Assert: comment either omits footer or shows generic ready message

# Test 3: Edge case — config exists but has no agents section
# Should behave like 'no code agent configured'

[fullsend-ai-prioritize]

RICE Priority Score: 0.4

Score breakdown

Dimension	Score	Reasoning
Reach	1	Affects users across repos that use fullsend triage but do not have the code agent installed. This is a moderate subset of all fullsend users — those using triage-only configurations. Not platform-wide since repos with a code agent are unaffected.
Impact	0.5	Low impact per user — the broken suggestion is confusing but not blocking. Users can simply ignore the non-functional /fs-code hint and proceed with manual implementation. A workaround exists (ignore the suggestion) and it is easy to understand once encountered.
Confidence	0.8	High confidence — the issue is exceptionally well-described with clear scope. Both a human reviewer (ralphbean) and the multi-agent review squad independently flagged this gap. The PR author acknowledged it as valid. The fix location (post-triage.sh lines ~517-526) and validation criteria are explicit.
Effort	1	Medium effort — requires reading repo agent configuration (config.yaml or equivalent), adding conditional logic in post-triage.sh, handling edge cases (missing config, missing agents section, defaults), and adding test cases to post-triage-test.sh covering both configured and unconfigured scenarios.

Formula: (1 x 0.5 x 0.8) / 1 = 0.4