szn

Bug 201 — eraseDisplay force_clear triggered by any image in the registry, not the erased region

201. eraseDisplay force_clear triggered by any image in the registry, not the erased region

File: src/screen.zig:984–1009, src/screen.zig:528–549 Severity: LOW Status: ✅ FIXED — eraseDisplay now tracks whether an image overlapping the erased region was actually removed and only sets force_clear in that case, instead of whenever any image existed in the registry. Added unit test.

eraseDisplay sets force_clear = true whenever had_sixels is true — i.e. whenever any image exists in the registry, regardless of whether the erased region (mode 0/1/2/3) actually overlapped it. This guarantees a full \x1b[2J repaint (see #196) on every erase operation in a session that has ever shown sixel, even for trivial clear-style erases in a different region. The force_clear should be set only when an image that overlaps the erased region was actually removed.