Fix undefined rows logging issue in checksum processing

[devin-ai-integration]

Fix undefined rows logging issue in checksum processing

Summary

Resolves a minor logging bug where database update operations in checksum processing were logging "(undefined rows)" instead of the actual number of affected rows. The issue was caused by incorrectly accessing updateResult[0] when the actual affected row count is in updateResult[1] for Sequelize update operations.

Root Cause: Sequelize update results return [null, affectedRowCount] but the code was accessing index 0 instead of index 1.

Fix: Use array destructuring to properly extract the affected rows count from the update result.

Review & Testing Checklist for Human

• Verify logs now show actual row counts (e.g., "Database updated with checksum for: /path/to/file (1 rows)") instead of "(undefined rows)"
• Test checksum processing functionality to ensure the fix doesn't break core operations
• Monitor production logs after deployment to confirm the fix works across different scenarios

Notes

• This is a logging-only fix that doesn't affect core checksum functionality
• Tested locally with file additions that trigger checksum processing
• Session: https://app.devin.ai/sessions/30b40362482e42109b8243b6c7a36ca3
• Requested by: @MarkProminic (mark.gilbert@prominic.net)

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

⚙️ Control Options:

• Disable automatic comment and CI monitoring