fix(backend): log failedReason when connection sync job fails (#1012)

* fix(backend): log failedReason when connection sync job fails

The error message from a failed connection sync job was being stored in
the DB but never surfaced in the logs, making it impossible to diagnose
failures without querying the database directly.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* chore: update CHANGELOG for #1012

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

---------

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: brendan-kellam

CHANGELOG.md

@@ -10,6 +10,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Changed
 - `filterByFilepaths` in the MCP `search_code` tool now accepts regular expressions matched against the full file path, instead of treating values as escaped literals. [#1008](https://github.com/sourcebot-dev/sourcebot/pull/1008)
 
+### Fixed
+- Connection sync job failures now log the actual error reason instead of a generic message. [#1012](https://github.com/sourcebot-dev/sourcebot/pull/1012)
+
 ## [4.15.7] - 2026-03-16
 
 ### Added

packages/backend/src/connectionManager.ts

@@ -378,7 +378,7 @@ export class ConnectionManager {
             this.promClient.activeConnectionSyncJobs.dec({ connection: connection.name });
             this.promClient.connectionSyncJobFailTotal.inc({ connection: connection.name });
 
-            jobLogger.error(`Failed job ${job.id} for connection ${connection.name} (id: ${connection.id}). Failing job.`);
+            jobLogger.error(`Failed job ${job.id} for connection ${connection.name} (id: ${connection.id}). Reason: ${job.failedReason}`);
 
             const config = connection.config as unknown as ConnectionConfig;
             captureEvent('backend_connection_sync_job_failed', {