fix: handle context.Canceled in gemini backend to report "aborted" status

[kuishou68]

Closes #928

Problem

The geminiBackend.Execute goroutine in server/pkg/agent/gemini.go does not handle context.Canceled (user-initiated cancellation). When a task is stopped externally, runCtx.Err() returns context.Canceled, but the code only checks for context.DeadlineExceeded. As a result, user cancellations fall through to the else branch and are reported as "failed" instead of "aborted".

The inline comment says "Distinguish context cancellation (timeout) from exit errors" but the implementation only partially fulfilled that intent.

Fix

Added a context.Canceled branch to mirror the behaviour already present in claude.go:

} else if runCtx.Err() == context.Canceled {
    result.Status = "aborted"
    result.Error = "execution cancelled"
}

This ensures user-initiated cancellations are correctly reported as "aborted" rather than "failed", consistent with all other backends.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
multica-web	Ignored		Apr 14, 2026 1:12am
multica-web-production	Ignored		Apr 14, 2026 1:12am