furina-dsh-theme

LIMITATIONS

Known limitations

* Screenshots are 1600×900 headless-Chromium captures of throwaway profiles; they prove mount + paint + switching, not every component state (dialogs, streaming transcripts) in every skin. * `splash-boot.png` is a **real boot** capture (isolated instance with the installed `dsh-startup-screen` kept in the bundle list, splash forced to `mode: always`, captured at ~6.6 s). The port-3083/3084 instances are throwaway: the live GUI and the installed theme copy under `~/.dsh/profiles/web/node_modules/furina-dsh-theme` were never touched. * `file-card.png` renders the changed-file and presented-file cards in a live page using the installed deliverables plugin's own class names (`hz8-rW_*`, `nyYjTG_*`, loaded from its `data-plugin-css` modules) and data attributes; there is no agent transcript in a throwaway profile, so the card content is seeded rather than produced by a real tool call. * The settings page is injected into the app's dialog (a cloned nav row + an absolutely positioned Shadow DOM pane). It follows the app's DOM contract, not a public plugin slot, so a future Settings redesign may need the selectors refreshed; the fallback launcher keeps the controls reachable in that case. * The isolated instance runs with the two full-page competitor themes removed — that is the supported configuration, not a hidden workaround (see [Coexistence](#coexistence-with-other-themes)). * The theme is CSS-first: it re-skins DSH's design tokens and a bounded set of surfaces. It does not restyle third-party plugin UI that hard-codes its own colours.