/* SECTION - Section Page
   ========================================================================
   THIS FILE IS INTENTIONALLY EMPTY. Every rule the section page needs now
   lives in the "Brand refresh: shared page components" section at the foot of
   css-components.css, scoped to `html.category-page, html.section-page`. The
   hero band, the section heading, the subsection cards and the article cards
   are all literally the category page's -- there is no Figma frame for either
   page, and the two are the same page one level apart in the tree.

   WHAT THIS FILE HELD FOR ONE DAY, AND WHY IT IS GONE. It was the article list:
   .kb-article-list plus .kb-article-row* -- one bordered box with
   hairline-separated rows and a single chevron per row, written on 2026-10-23.
   The argument for it was scale, and it was explicit: a section here holds up
   to 41 articles (measured against the live API the same day -- 1,137 articles
   across 213 sections, one section at 41 and another at 29), and 41 shadowed
   cards is a scrollbar rather than a list.

   Joy previewed it and asked for cards anyway: "let's make them cards in the
   same format as the recent updates cards." That is the right call and the
   scale argument was wrong, not overruled -- the rows were full-width, so 41 of
   them is 41 rows deep, while the card grid is
   repeat(auto-fit, minmax(17rem, 1fr)) and 41 cards is about eleven rows of
   four on a laptop. The cards make the page shorter, not longer. The list also
   bought a second bespoke component for a page that otherwise had none, and
   .kb-update-card already existed and was already the answer to "a link to one
   article".

   So the rows are deleted rather than kept alongside: nothing in the theme
   renders .kb-article-list or .kb-article-row* any more. #tmpl-section-articles
   at the foot of section_page.hbs emits .kb-updates-grid / .kb-update-card
   instead, and the only difference from the category page's cards is that these
   carry no badge -- see .kb-badge in css-components.css for why.

   (The version before *that* was 58 lines of rules for markup that no longer
   existed, four of which styled the output of a micro-template the theme never
   defined. That history is in git; it is not worth repeating here now that
   none of the names survive.)

   WHY THE FILE IS STILL HERE AT ALL, rather than deleted along with its
   <link>. The Contact support CTA is commented out in this template awaiting a
   refreshed design, and that round is the next thing to land on this page; if
   its treatment differs from the category page's, this is where this page's
   half goes. And deleting the asset means editing document_head.hbs, which is
   the one file whose line numbers half the comments in assets/ cite. Worth
   revisiting once the CTA round has settled, not before.

   SO: TO CHANGE HOW THIS PAGE LOOKS, EDIT css-components.css -- and expect the
   change to land on the category page too. That is the point of the sharing
   rather than a side effect.
   ===================================================================== */