/* Hide the element sidebar's own close control, so the header button is the only way to
 * open or close the details panel.
 *
 * Two routes to the same state is how the server's idea of it goes stale -- and while the
 * panel now reports its own state so nothing desyncs, one control is still one control.
 *
 * Scoped rather than global. `#side-view-content` is the sidebar's content container, so
 * `div:has(> #side-view-content)` is the card that wraps it, and the arrow sits in that
 * card's header. Matching the icon class as well means this cannot catch an unrelated
 * button that appears in the same header later.
 *
 * If a Chainlit upgrade renames either hook, the arrow simply comes back -- a returned
 * affordance, not a broken app.
 */
div:has(> #side-view-content) button:has(svg.lucide-arrow-left) {
  display: none !important;
}