feat: Add progress bar for file parsing workers (PR-04)

[shivasurya]

Summary

Replaces noisy per-file worker status messages with clean progress bar tracking during code graph initialization. Workers now report progress via callbacks instead of direct logging.

Why this change?

• Much cleaner output: Eliminates spam like "Worker 1 ....... Done processing file X"
• Better UX: Single progress bar shows overall file parsing status
• Consistent design: Matches other progress indicators added in PR-02
• Performance visibility: Users see real-time progress through all files
• Less log pollution: Stderr stays clean for actual errors/warnings

Before (PR-03)

2026/01/19 22:11:42 Worker 1 ....... Done processing file generate_stdlib_registry.py []
2026/01/19 22:11:42 Worker 2 ....... Done processing file test_generator.py []
2026/01/19 22:11:42 Worker 3 ....... Done processing file process_rules_for_r2.py []
2026/01/19 22:11:42 Worker 4 ....... Done processing file sample.py []
2026/01/19 22:11:42 Worker 5 ....... Done processing file utils.py []

After (PR-04)

Building code graph ████████████████████ 100% | 245/245 files

Changes

• Add ProgressCallbacks struct with OnStart/OnProgress callbacks
• Update Initialize() signature: func Initialize(directory string, callbacks *ProgressCallbacks)
• Remove statusChan and all worker status logging
• Integrate progress callbacks in scan.go and ci.go
• Update all 16 test files to pass nil callbacks where progress tracking not needed
• Add 10 comprehensive tests for callback functionality (90.9% coverage)
• Fix: Remove noisy "No container rules found" warning

Technical Details

Callback Design:

type ProgressCallbacks struct {
    OnStart func(totalFiles int)    // Called once before processing
    OnProgress func()                // Called after each file (success or error)
}

Integration:

graph.Initialize(projectPath, &graph.ProgressCallbacks{
    OnStart: func(totalFiles int) {
        logger.StartProgress("Building code graph", totalFiles)
    },
    OnProgress: func() {
        logger.UpdateProgress(1)
    },
})
logger.FinishProgress()

Testing

• 10 new callback-specific tests:
  • Progress callback invocation verification
  • Nil callbacks handling
  • Partial callbacks (OnStart/OnProgress only)
  • Dockerfile read errors with callbacks
  • Docker-compose parse errors with callbacks
  • Valid Docker file processing
  • Java/Python file read errors
  • Java/Python file processing
• Coverage: 90.9% for initialize.go (up from 75%)
• Remaining 9.1% is defensive code (unreachable paths)
• All existing tests pass with nil callbacks

Stack

• Depends on: PR-03 (Logging cleanup)
• Final PR in CLI Output Enhancement initiative (PR-04 of 4)

---

🤖 Generated with Claude Code

[safedep]

SafeDep Report Summary

No dependency changes detected. Nothing to scan.

_{This report is generated by SafeDep Github App}

[codecov]

Codecov Report

❌ Patch coverage is 44.73684% with 21 lines in your changes missing coverage. Please review.
✅ Project coverage is 79.94%. Comparing base (2b8e9fc) to head (f0e70c3).
⚠️ Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
sast-engine/cmd/scan.go	0.00%	8 Missing ⚠️
sast-engine/cmd/ci.go	0.00%	7 Missing ⚠️
sast-engine/graph/initialize.go	80.95%	4 Missing ⚠️
sast-engine/cmd/resolution_report.go	0.00%	1 Missing ⚠️
sast-engine/cmd/serve.go	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #476      +/-   ##
==========================================
- Coverage   79.97%   79.94%   -0.03%     
==========================================
  Files         101      101              
  Lines       11114    11107       -7     
==========================================
- Hits         8888     8880       -8     
- Misses       1874     1879       +5     
+ Partials      352      348       -4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[shivasurya]

• feat: Add progress bar for file parsing workers (PR-04) #476 👈 (View in Graphite)
• feat: Clean up verbose logging for better CLI output (PR-03) #475
• feat: Add progress bars for scan/CI operations (PR-02) #474
• feat: Add banner system and TTY detection for CLI output (PR-01) #473
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[shivasurya]

Merge activity

• Jan 20, 3:40 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Jan 20, 3:46 AM UTC: Graphite rebased this pull request as part of a merge.
• Jan 20, 3:47 AM UTC: @shivasurya merged this pull request with Graphite.