/* The bar and the preview for assigning a queue from a spreadsheet.
 *
 * SIZED LIKE EVERY OTHER THING TO PRESS IN THIS PRODUCT: 44px tall, which is
 * what a thumb needs (D67). Written out here rather than borrowed from Item
 * Master's stylesheet, because `k-items__add` on a Products screen reads as a
 * mistake to whoever finds it next.
 *
 * A NOTE THAT IS NOT AN EXCUSE: this is the fifth place a button is described
 * in this product -- Item Master, the table row, the form, the way back, and
 * now here. **That is one thing written five times and it should be one.**
 * Lifting it touches four working stylesheets and their screens, so it is its
 * own job and it is written down in docs/BUILD_QUEUE.md rather than done
 * quietly in the middle of this one.
 *
 * Every colour comes from a token. A class with no rule behind it draws as a
 * bare browser default and no check can see it -- that has already cost this
 * product one undo button (see screen.css).
 */

.k-assign-file {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  gap: 12px;
  margin: 16px 0 0;
  min-width: 0;
}

/* **THIS SAID "THE MAIN ONE" IN ITS OWN COLOURS.** `k-button--main` is that,
 * said in the one place every screen says it (D142) -- so the button that
 * matters on this screen looks like the button that matters on every other. */

/* The file control itself is never drawn. A browser will not let its wording or
 * its size be set, and "Choose file / no file chosen" in the middle of a page
 * built for a phone is neither. The label around it is the button. */
.k-assign-file__pick {
  position: absolute;
  width: 1px;
  height: 1px;
  padding: 0;
  margin: -1px;
  overflow: hidden;
  clip-path: inset(50%);
  white-space: nowrap;
}

.k-assign-file__label {
  display: inline-flex;
  align-items: center;
}

/* ------------------------------------------------------- what would happen */

.k-assign-file__preview {
  margin: 16px 0 0;
  padding: 16px;
  background: var(--surface-raised);
  border: 1px solid var(--border);
  border-radius: var(--radius);
}

.k-assign-file__heading {
  margin: 0 0 8px;
  font-family: var(--font);
  font-size: 16px;
  font-weight: 600;
  color: var(--text);
}

.k-assign-file__line {
  margin: 0 0 6px;
  font-family: var(--font);
  font-size: 14px;
  line-height: 1.45;
  color: var(--text-muted);
  overflow-wrap: anywhere;
}

.k-assign-file__ask {
  margin: 12px 0 0;
  padding: 12px;
  background: var(--surface);
  border: 1px solid var(--border-strong);
  border-radius: var(--radius);
}

.k-assign-file__choices {
  display: flex;
  flex-wrap: wrap;
  gap: 8px;
  margin: 8px 0 0;
}

.k-assign-file__answered {
  font-family: var(--font);
  font-size: 14px;
  font-weight: 600;
  color: var(--brand);
}

/* A SECTION INSIDE A SCREEN, not a screen of its own.
 *
 * Needs Review and the cleaning list both live inside Products now (his
 * decision, 2026-09-01 -- one door, not two), so each needs a heading that says
 * "a part of this page" rather than "a new page". Smaller than the screen's own
 * title, and with room above it so the eye reads a break rather than a run-on.
 *
 * **18 ABOVE, not 32.** His instruction, 2026-09-02: *"reduce the space between
 * the button row and bill of material."* With one section open at a time (D154)
 * there is nothing above it but the buttons that opened it, and a gap that size
 * read as a break between two unrelated things rather than as "this is what
 * that button just opened". */
.k-products__section {
  margin: 18px 0 12px;
  font-size: 1.05rem;
  color: var(--text);
}