Rewrite fallback strategy in plain English instead of pseudocode

Address PR feedback: Replace confusing Python-like pseudocode with clear
plain English description of the fallback logic.

Author: janisz

workflows/acs-triage/.claude/commands/triage.md

@@ -235,17 +235,10 @@ After Stage 1, spawn specialized RCA agents for each CI_FAILURE issue:
 
 **Fallback Strategy:**
 
-If multi-agent approach fails (TeamCreate unavailable or agents error):
-```python
-try:
-    # Multi-agent approach (above)
-except:
-    # Fall back to single sequential analysis
-    if exists("/tmp/triage/stackrox/.claude/agents/stackrox-ci-failure-investigator.md"):
-        runSingleAgentAnalysis()  # Old 5-minute sequential approach
-    else:
-        descriptionOnlyAnalysis()  # Minimal analysis from JIRA description only
-```
+If the multi-agent approach fails (TeamCreate unavailable or agents error), fall back to a simpler analysis method:
+
+- If the CI failure investigator agent file exists at `/tmp/triage/stackrox/.claude/agents/stackrox-ci-failure-investigator.md`, use the old single-agent sequential analysis approach (takes approximately 5 minutes per issue)
+- If the CI failure investigator agent file does not exist, perform minimal analysis using only the JIRA issue description
 
 **Sanitization rules:** NEVER include API tokens, passwords, secrets, internal URLs with credentials, IP addresses, or employee emails in `deep_analysis` output. Use `[REDACTED]` for any sensitive values found.