REFACTOR AWS transcription to local transcription

[SergioNR]

Description

Types of Changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update (if applicable)
• Refactor (non-breaking change that improves the code structure)

Related issue

Explanation of changes/Implementation

Screenshots (if applicable)

Pull Request Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

Additional Notes

[kiloconnect]

⚠️ 3 Issues Found

Severity	Issue	Location
WARNING	Incorrect status rollback on transcription failure	server/controllers/transcriptionController.js:39
WARNING	Missing error object logging	server/controllers/analysisEntryController.js:33
WARNING	Potential null pointer access	server/integrations/whisper-asr-webservice/transcribe.js:8

Recommendation: Address critical issues before merge

Review Details (18 files)

Files:

• server/controllers/transcriptionController.js (1 issue)
• server/controllers/analysisEntryController.js (1 issue)
• server/integrations/whisper-asr-webservice/transcribe.js (1 issue)
• compose.yaml, package.json, .env.example, server/integrations/s3-client/s3.js, and others

Checked: Security, bugs, performance, error handling

Key Issues Found:

1. Incorrect Status Rollback (WARNING)

File: server/controllers/transcriptionController.js:39
When transcription fails, the status is incorrectly set back to IN_PROGRESS instead of PENDING, preventing retry attempts.

Fix: Change status to PENDING for failed jobs.

2. Missing Error Details (WARNING)

File: server/controllers/analysisEntryController.js:33
Error logging does not include the actual error object, making debugging difficult.

Fix: Include error parameter in logError call.

3. Potential Null Pointer (WARNING)

File: server/integrations/whisper-asr-webservice/transcribe.js:8
Accessing transcriptionJob.AnalysisEntry without null check could cause runtime errors.

Fix: Add null check before accessing nested properties.

Positive Changes:

• Good separation of concerns with new transcription controller
• Improved S3 client architecture (external/internal split)
• Removed AWS dependencies, reducing external service costs
• Simplified transcription normalizer logic
• Docker compose properly configured for local transcription

Fix these issues in Kilo Cloud