Summary
The ItemViewer type exposes three different UI-thread seams and the codebase uses all three, with
one operation marshalled onto a WPF Dispatcher that may never be pumped and another marshalled not
at all. Out of scope under epic #136's no-behavior-change NFR.
Environment
(not provided in potential file)
Steps to Reproduce
(not provided in potential file)
Expected Behavior
(not provided in potential file)
Actual Behavior
(not provided in potential file)
Logs / Screenshots
(not provided in potential file)
Impact / Severity
(not provided in potential file)
Source
From: docs/features/potential/2026-08-07-itemviewer-ui-thread-marshalling-divergence.md
Summary
The
ItemViewertype exposes three different UI-thread seams and the codebase uses all three, withone operation marshalled onto a WPF
Dispatcherthat may never be pumped and another marshalled notat all. Out of scope under epic #136's no-behavior-change NFR.
Environment
(not provided in potential file)
Steps to Reproduce
(not provided in potential file)
Expected Behavior
(not provided in potential file)
Actual Behavior
(not provided in potential file)
Logs / Screenshots
(not provided in potential file)
Impact / Severity
(not provided in potential file)
Source
From: docs/features/potential/2026-08-07-itemviewer-ui-thread-marshalling-divergence.md