fix(server): add a real retrieval path for the omitted resolved recovery-action history

The wake prompt told the agent to fetch the recovery-action history for
recovery outcomes dropped by the item cap. GET /issues/:id/recovery-actions
returned only the active action, so the agent had no way to recover the
dropped rows. Add a status=resolved query to the same route, backed by a
new listResolvedForIssue lookup, and update the prompt to name the exact
call.

Co-authored-by: Paperclip <noreply@paperclip.ing>
This commit is contained in:
nickyleachandPaperclip authored and Nicky Leach committed 2026-09-10 19:47:41 -07:00
1 parent 53bf0667b8
commit 3590e26d6b
5 files changed
+82 -6

No files matched your search

+1 -1
View File
@@ -2448,7 +2448,7 @@ export function renderPaperclipWakePrompt(
? [`- omitted unresolved interactions: ${unresolvedInteractionIdsOmittedCount}; more pending interactions exist than the list below shows`]
: []),
...(recoveryOutcomesOmittedCount > 0
? [`- omitted recovery outcomes: ${recoveryOutcomesOmittedCount}; fetch the recovery-action history for the rest`]
? [`- omitted recovery outcomes: ${recoveryOutcomesOmittedCount}; call GET /issues/{id}/recovery-actions?status=resolved for the rest`]
: []),
"Completed actions contain durable results from prior runs. Use those results as completed work; do not issue the same mutation again under a new call id.");
const { interactionOutcomes, completedActions, completedWork, recoveryOutcomes, ...requestContext } = continuation;