b89ad29c41
A data-backed pane swapped its loading spinner, empty message, error message and content with a plain `when`, so content flashed from empty to full and empty/error states popped. Introduce a shared presentation model in ui/components/States.kt: - `LoadPhase` (Loading, Error(message), Empty(message), Content), with message-carrying phases capturing their text at classification so a fading-out branch never recomposes against cleared error/filter state. - `listLoadPhase(loading, error, hasData, emptyMessage)` and `detailLoadPhase(error, hasData)` pure classifiers preserving the existing precedence (failed load with no data, then loading, then empty, else content; stale data keeps the pane on content). - `StateCrossfade(phase)` wraps the branch in a `Crossfade` using the existing `MotionStandard` token; both branches share one box so the resting layout is unchanged and the outgoing phase fades under the incoming one. Apply to PipelineListScreen, RunHistoryScreen, PipelineDetailScreen and RunDetailScreen. Detail panes render the fading-out branch from the last non-null item. The Runs pane keeps its inline empty/error line inside the list, now fading through animateListItem(). Add LoadPhaseTest covering the classifiers and captured messages, and document the change and evidence in android/README.md.