/* ==========================================================================
   Features shared — Sources: the three materials Bloom reads about a client
   ==========================================================================
   The built-panel take on the family's shared story deck (Features/shared/
   StoryDeck.css, linked by the page shell): same frame, same turn, same pager;
   where the render turntable puts three app screens on the deck, this one puts
   three panels built out of markup, because what it shows — a wire of client
   news, the spine of past exchanges, and open material read forward — happens
   outside the app and has no screen to photograph.

   Three pages tell that story from their own angle (meeting preparation,
   client memory, CRM updates) and only their i18n differs — which is why the
   boards wear the family's own `fsrc-` vocabulary and not any one page's: they
   name the material a rep is prepared with, whichever page is doing the
   telling.

   The copy column is the family's shared story grammar (Features/shared/
   StoryScaffold.css, also linked by the page shell); these sheets own the three
   boards and what they need at every width.

   Entry point only — the sheets below are ordered deck → panels → breakpoints.
   ========================================================================== */

@import url('./styles/deck.css');
@import url('./styles/panels.css');
@import url('./styles/responsive.css');