/* Research organisations page. Page-only rules, tokens only, .pg-ro- prefix. */

/* The member's question above an answer. A plain paragraph would read as body copy;
   this is the voice of the person asking, so it takes the UI size in ink at semibold. */
.pg-ro-ask { margin: 0; font-size: var(--fs-ui); font-weight: var(--fw-semibold); line-height: var(--lh-snug); color: var(--fg-1); }
.pg-ro-ask--small { font-size: var(--fs-sm); color: var(--fg-2); }

/* A library's result list: file names and years and nothing else, which is the point.
   Paper rows on the panel, title left, year right (the pattern from knowledgebases.css). */
.pg-ro-results { list-style: none; margin: 0; padding: 0; display: flex; flex-direction: column; gap: var(--sp-1); }
.pg-ro-results li { display: flex; justify-content: space-between; align-items: baseline; gap: var(--sp-3); padding: 10px 14px; border-radius: var(--r-control); background: var(--paper); font-size: var(--fs-sm); }
.pg-ro-results b { font-weight: var(--fw-semibold); color: var(--fg-1); min-width: 0; }
.pg-ro-results span { flex-shrink: 0; font-size: var(--fs-micro); color: var(--fg-2); }

/* The connection line and tool list an MCP client shows. Tool names are code, so they
   take the system monospace stack; the description sits under each name. */
.pg-ro-conn { display: flex; align-items: center; gap: var(--sp-2); margin: 0; font-size: var(--fs-sm); font-weight: var(--fw-semibold); color: var(--teal-text); }
.pg-ro-tools { list-style: none; margin: 0; padding: 0; display: flex; flex-direction: column; gap: var(--sp-1); }
.pg-ro-tools li { display: flex; flex-direction: column; gap: 2px; padding: 10px 14px; border-radius: var(--r-control); background: var(--paper); }
.pg-ro-tools code { font: var(--fw-semibold) var(--fs-sm)/1.3 ui-monospace, SFMono-Regular, Menlo, Consolas, monospace; color: var(--fg-1); }
.pg-ro-tools span { font-size: var(--fs-sm); color: var(--fg-2); line-height: 1.45; }

/* Two quotations from a named person, bare on the page under the section they support.
   The quote takes the h4 size; the attribution sits under it at caption size. */
.pg-ro-quotes { align-items: start; }
.pg-ro-quote { margin: 0; }
.pg-ro-quote blockquote { margin: 0; }
.pg-ro-quote blockquote p { margin: 0; max-width: 40ch; font-size: var(--fs-h4); font-weight: var(--fw-semibold); line-height: var(--lh-snug); color: var(--fg-1); }
.pg-ro-quote figcaption { margin-top: var(--sp-2); font-size: var(--fs-sm); color: var(--fg-2); }

/* Rows inside a paper demo card. --_bg and --pad are inherited, so a plain .tint nested in
   .tint--paper would paint paper on paper; name the cloud ground and the row padding. */
.pg-ro-rule > .tint:not([class*="tint--"]), .pg-ro-returned { --_bg: var(--bg-tint); }
.pg-ro-rule > .tint { --pad: 12px 16px; font-size: var(--fs-sm); color: var(--fg-2); }
.pg-ro-rule > .tint b { color: var(--fg-1); }
.pg-ro-rule + .answer__cites { margin-top: var(--sp-3); }

/* The results table keeps each citation under its value so the page number stays in a
   phone column. */
.pg-ro-table th[scope="row"] { text-align: left; padding: 8px 12px; border-bottom: 1px solid var(--line); vertical-align: top; }
.pg-ro-table tbody tr:last-child th { border-bottom: 0; }
.pg-ro-table td { vertical-align: top; }
.pg-ro-table td .chip { margin-top: var(--sp-1); white-space: normal; }

/* Long citation chips wrap instead of pushing the card wider than a phone. */
[class*="pg-ro"] .chip, .answer__cites .chip { white-space: normal; line-height: 1.35; }

/* The spec grid's one-column phone rule loses the cascade to flat.css's 1100px rule
   (see knowledgebases.css); restated for this page. */
@media (max-width: 600px) { .specs { grid-template-columns: 1fr; } }