singularity/singularity-forge
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

docs(sf): better message when /sf escalate resolve hits an already-resolved entry

Browse source 
The "already-resolved" branch returned a bare timestamp with no
guidance. Auto-accepted escalations especially leave the user wondering
what to do — the carry-forward was already injected into the next
task, so this command can't retroactively undo the choice.

Now the message distinguishes auto-accepted vs user-resolved and, for
the auto-accepted case, points to `/sf memory note "..."` as the
forward-looking corrective surface (it lands in memory_embeddings on
next backfill and influences future ranking).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Mikael Hugo 2026-05-02 23:32:01 +02:00
parent daa192a572
commit c1ce9aac15
1 changed files with 5 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
src/resources/extensions/sf/escalation.ts
View file

@ -328,9 +328,13 @@ export function resolveEscalation(
}; };
} }
if (art.respondedAt) { if (art.respondedAt) {
const wasAuto = art.userRationale?.startsWith("auto-mode:");
const detail = wasAuto
? ` (auto-accepted in auto-mode → choice="${art.userChoice}"; the carry-forward was already injected into the downstream task, so this can't be retroactively changed via /sf escalate resolve. Capture the corrective decision as \`/sf memory note "..."\` so future tasks pick it up.)`
: ` (resolved by user → choice="${art.userChoice}").`;
return { return {
status: "already-resolved", status: "already-resolved",
message: `Escalation for ${taskId} was already resolved at ${art.respondedAt}.`, message: `Escalation for ${taskId} was already resolved at ${art.respondedAt}${detail}`,
}; };
} }