Summary

In large files, blame annotations don't appear until the entire git blame operation completes, leaving users waiting with no visual feedback.

Impact

Users working in large files experience a noticeable delay before any blame annotations appear. Progressive rendering would show annotations incrementally as results stream in, significantly improving perceived performance and responsiveness. For example, opening ECMA-232 spec files or similarly large documents should show blame annotations appearing almost immediately in the viewport rather than waiting for the full file to process.

Validation

• Open a large file (e.g. the ECMA-232 spec) and toggle gutter blame annotations
• Annotations should begin appearing within the viewport almost immediately, even before the full blame completes
• Avatars should load in parallel rather than sequentially
• No flickering or visual artifacts during incremental updates

Risk

• Partial blame state visible to users during streaming — decorations must update cleanly without flicker
• Viewport-aware rendering logic may interact with rapid scrolling during streaming