Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@owlplug-client/src/main/resources/fxml/HomeView.fxml`:
- Line 186: The unresolved tile’s alert icon is missing the warning styling and
fixed size that the old asset provided. Update the FontIcon in HomeView.fxml so
it still reads as a danger/alert indicator and matches the neighboring stat icon
sizing, using the existing icon element and its style/size properties rather
than leaving it unstyled.

In `@owlplug-client/src/main/resources/owlplug.css`:
- Line 51: There is an unnecessary blank line before the `-owlplug-color-text`
declaration in the stylesheet block; move `-owlplug-color-text` up to sit
directly with the surrounding custom properties in `owlplug.css` so the block
matches the expected declaration order and passes Stylelint.
- Around line 373-377: Keep the .pane-card surface styling intact in owlplug.css
for now, because multiple views still rely on it. Restore or preserve the
background and radius styling in the .pane-card rule used by
PluginInfoView.fxml, ProjectInfoView.fxml, ComponentInfoView.fxml,
PackageInfoView.fxml, WelcomeView.fxml, SymlinkInfoView.fxml, and
DirectoryInfoView.fxml, and only remove these styles after all of those
consumers have been migrated.

In `@owlplug-theme/src/main/scss/owlplug-dark.scss`:
- Around line 65-75: The danger palette needs to keep the foreground swatch
readable on the dark theme canvas, since $danger-4 currently feeds $danger-fg
and is too low-contrast for text/icons. Update the danger scale in
owlplug-dark.scss by making $danger-4 lighter, or adjust the $danger-fg
assignment to use a lighter danger stop while keeping the rest of the palette
intact. Use the $danger-4 and $danger-fg symbols to locate and change the
mapping consistently.