/*
 * Propshaft auto-loads every .css file in this directory via
 * `stylesheet_link_tag :app` in the layout. Add new files alongside:
 *
 *   variables.css  — design tokens (:root custom properties)
 *   main.css       — structural element and layout styles
 *   utilities.css  — atomic/utility classes
 *   feed.css       — the message feed: day chips, message cards, the
 *                    attachment card and the staff-only unsent panel
 *   forms.css      — the .form-item pattern for page forms
 *   list-blocks.css — list cards, filter bar, secondary-nav callout
 *   line-items.css  — line-item rows, the panel they sit on, and its bands:
 *                     a header, a body, a footer and their empty states
 *   attendance.css  — the attendance record's percentage stat, and the two
 *                     columns of students on its own page
 *   course-dashboard.css — the lede, status banner and attendance grid on a
 *                          class's details page
 *   collection-picker.css — the multi-select field, for a bounded set of options
 *   record-search.css — type-to-find, for a set too big to render in full.
 *                       The picker's counterpart: pick between them on whether
 *                       the candidate list has a ceiling.
 *   action-panel.css — the action panel closing a record's show page.
 *                      Distinct from list-blocks' .action-group, which is a
 *                      button cluster inside a card and stays unboxed.
 *   copy-button.css — the click-to-copy pill, and .copy-row, the field-plus-
 *                     pill line it usually sits in.
 *   invitations.css — a class's sign-up link at two distances: the .share-panel
 *                     at the top of the invitations page, and the .present
 *                     projector screen the QR code is shown on.
 *   people.css — a person's own page: the identity band, and the two line-item
 *                variants and the disclosure fold its class list needs.
 *   oauth-button.css — the "Sign in with Google" button and the labelled rule
 *                      that separates it from the password form.
 *   editor.css — the rich text editor: what the site adds on top of the gem's
 *                lexxy.css, which is linked separately (see below).
 *
 * CSS custom properties cascade at compute time, so file load order
 * does not matter for variables defined under :root.
 *
 * It DOES matter for everything else: Propshaft sorts logical paths
 * alphabetically, so the files load in the order
 *
 *   action-panel, application, attendance, collection-picker, copy-button,
 *   course-dashboard, document-picker, documents, editor, feed, forms, home,
 *   invitations, line-items, list-blocks, main, oauth-button, people,
 *   record-search, utilities, variables
 *
 * A rule in an alphabetically earlier file has to beat a same-specificity
 * rule in a later one on specificity, not on order.
 *
 * The rich text editor's stylesheet (lexxy.css, from the gem) is not in this
 * directory and is linked separately, BEFORE :app, in the layout. That makes
 * it the vendor layer: every one of these files loads after it, and its
 * --lexxy-* tokens are redefined in variables.css.
 */