/* ===========================================================================
   Precision Developer Portal — pgc-forms.css

   This file is now just the manifest. The rules live in pgc/*.css.
   Nothing in the Blade layout changes: keep loading this one file.

     <link href="{{ asset('css/pgc-forms.css') }}" rel="stylesheet">

   Deploy as:
     public/css/pgc-forms.css
     public/css/pgc/01-tokens.css   (etc.)

   ⚠ ORDER MATTERS. Several rules rely on cascade position — to beat DaisyUI
   defaults, and to let page-specific styles override the shared layers.
   Do not reorder these imports.

   07-features.css must stay after the shared layers (01-06). 08-editor.css may
   follow it: every selector there is namespaced under .pgc-dev-richtext,
   .pgc-dev-trix or .pgc-rich-text, none of which appear in 07, so the two are
   cascade-disjoint.

   ⚠ Each @import is an extra HTTP request when served as a plain stylesheet.
   If you compile through Mix/Vite it becomes a single file, which is better:
     resources/css/app.css  ->  @import "./pgc/01-tokens.css";  (etc.)

   Brand: #28484f  ·  hover/press: #1e383e  ·  hairline: #C4D0D3
   =========================================================================== */

@import "pgc/01-tokens.css";     /* tokens + host resets — must be first  */
@import "pgc/02-forms.css";      /* inputs, labels, toggles, fieldsets    */
@import "pgc/03-buttons.css";    /* buttons, text actions, links          */
@import "pgc/04-layout.css";     /* page shells, panels, grids, tabs      */
@import "pgc/05-tables.css";     /* shared list view                      */
@import "pgc/06-overlays.css";   /* modals, drawers, toasts               */
@import "pgc/07-features.css";   /* page-specific patterns                */
@import "pgc/08-editor.css";     /* Trix chrome + read-only rich text     */