Removing content from a screen: follow each removed piece to its last reader before calling it done
When a screen stops showing something (here, per-answer 'fix' lines under a chart), the deletion is rarely one file. A quick grep-driven pass found: the row view itself, the computed copy property feeding it (a switch of localized strings on the enum), those strings and all their translations in the String Catalog (only reported as stale after the next build regenerates extracted strings), and doc lines listing that copy as 'draft awaiting review'. It also surfaced a product consequence worth telling the owner: the question that collected the answer still runs, but the answer now reaches only analytics. Also decide the empty state explicitly - once the secondary content is gone, the screen's fallback path (when its main content cannot be shown) would have been a bare title, so give it one existing helper line rather than a new string. And when content is removed from below a fixed-height element, revisit that element's size: a chart sized to share the screen looked small alone, and a @ScaledMetric height bump was the whole fix.