/* style-section-label.css — the outlined section label.

   Paired with the `valencia-section-label` block style registered in
   functions.php. The registration carries the same values in style_data,
   which is what makes them visible and adjustable in Global Styles; this
   sheet is what makes them RENDER IN THE EDITOR CANVAS.

   Both are needed, and the reason is worth keeping. style_data reaches
   the front end through theme.json's generated stylesheet, but none of
   it reaches the editor canvas on this install: checked against
   get_block_editor_settings() for core/edit-site, `valencia-eyebrow`
   (pure style_data, no sheet) has ZERO selector hits there, while
   `valencia-chip` appears only via style-chip.css. Every block style in
   this theme that looks right in the editor has a companion sheet — the
   ones without one are invisible there.

   So: keep the two in sync. style_data is the editable surface, this is
   the canvas rendering. If you retune one, retune the other.

   Single class throughout, so the sidebar controls still out-specify it. */
.is-style-valencia-section-label {
  /* Not in the style_data schema at all. */
  display: block;
  width: fit-content;
  margin: 0;

  /* Mirrors the style_data in functions.php. */
  border: 1.5px solid var(--wp--preset--color--contrast);
  border-radius: 4px;
  /* The vertical pad is 4px and the radius 4px: both sit BELOW the
     spacing scale, whose smallest step is xs at 8px. A chip this size
     needs a tighter inset than the scale reaches, so these stay literal
     rather than being forced onto a token that would double them.
     Horizontal uses xs, which the scale does reach. */
  padding: 4px var(--wp--preset--spacing--xs);
  font-family: var(--wp--preset--font-family--display);
  font-size: var(--wp--preset--font-size--small);
  font-weight: 700;
  letter-spacing: 0.02em;
  text-transform: none;
  color: var(--wp--preset--color--contrast);
}