/* Inline chip row */
.md-typeset .doc.doc-heading .api-chip-row {
  display: inline-flex;
  gap: 0.375rem;
  vertical-align: middle;
  margin-left: 0.5rem;
}

/* Chip styling */
.md-typeset .doc.doc-heading .api-chip {
  display: inline-block;
  padding: 0.1rem 0.55rem;
  border-radius: 999px;
  font-size: 0.72rem;
  line-height: 1.3;
  white-space: nowrap;

  /* Use palette variables so it works in both light + dark */
  background-color: var(--md-code-bg-color);
  color: var(--md-typeset-a-color);
  border: 1px solid var(--md-typeset-a-color);
}

/* Optional: make text slightly bolder for readability */
.md-typeset .doc.doc-heading .api-chip {
  font-weight: 500;
}

/* Cross-reference links (mkdocstrings autorefs) — e.g. tqt_nmr.Signal1D and the
 * returned data types in API signatures. Inside code signatures they otherwise
 * inherit the plain syntax colour with no affordance, so they read as static
 * text. Give them an accent colour, a dotted underline, and a pointer cursor so
 * it's clear they navigate to the type's documentation. */
.md-typeset a.autorefs-internal,
.md-typeset a.autorefs-external {
  color: var(--md-typeset-a-color);
  text-decoration: underline dotted;
  text-underline-offset: 0.15em;
  cursor: pointer;
  pointer-events: auto;
}

.md-typeset a.autorefs-internal:hover,
.md-typeset a.autorefs-external:hover {
  color: var(--md-accent-fg-color);
  text-decoration: underline solid;
}