/*
* openrouter-embed/transcribe.css — the Transcribe tool's own styling.
*
* Register item 43, iteration 3. Until this file existed the tool shipped with
* NO stylesheet of its own: it borrowed four .imgdesc-upload-* rules from the
* Image Describer and carried four transcribe-* classes that nothing styled.
* Both tools.html comments covering this tool said "No new CSS." in terms, and
* this file knowingly ends that, for the reason item 43's strand 3 gives.
*
* WHY THIS FOLDER. The one-sheet-per-tool convention puts a tool's sheet in
* the tool's own folder — image-describer/image-describer.css, chat/chat.css,
* local-chat/local-chat.css, setup-tool/setup-tool.css — each a plain
* unconditional in tools.html's . Both Transcribe files live in
* openrouter-embed/, so this does too. Stated because openrouter-embed/ had
* never carried a stylesheet before: the convention supplies the shape without
* supplying a precedent for this folder.
*
* =========================================================================
* COLOUR: THERE IS NONE. THIS IS THE LOAD-BEARING DECISION IN THIS FILE.
* =========================================================================
*
* NO TEXT COLOUR IS DECLARED ANYWHERE IN THIS FILE, and none may be. Every
* text-bearing rule inherits or uses `currentColor`, which is the house
* pattern in image-describer.css and is what makes a sheet theme-correct
* without knowing the theme.
*
* UNIT 2 OF ITEM 55 ADDED TWO ACHROMATIC SURFACE TINTS — a 6% grey panel on
* .transcribe-list and a 25% grey row separator — written as rgba greys so
* they composite over whatever the theme supplies and carry no hue of their
* own. THEY TOUCH SURFACES, NEVER TEXT. The prohibition above is unchanged
* for text, and the numbers below are measured with those tints in force.
*
* The pairs that actually reach the screen, measured ON THE PAGE in both
* themes rather than computed on paper. The background is the COMPOSITED
* surface — `main` with this file's 6% panel tint over it — because that is
* what the text is actually read against:
*
* light #00131d on rgb(247, 247, 237) = 17.58:1
* dark #e1e8ec on rgb(41, 37, 38) = 12.27:1
*
* All three of .transcribe-time, .transcribe-speaker and .transcribe-text
* measure identically, because none of them declares a colour.
*
* WITHOUT the panel tint the same text reads 18.78:1 and 13.16:1 on bare
* `main`. So the tint costs 1.20 in light and 0.89 in dark, which is the
* number to spend against — NOT the bare-main pair — if a later unit adds
* anything of its own on top of this panel.
*
* THE EARLIER BODY-BASED PAIRS WERE WITHDRAWN IN UNIT 2 OF ITEM 55, because
* the transcript paints on `main`, not on `body`. They read `#00131d on
* #f0f2e8 = 16.72:1` and `#e1e8ec on #161415 = 14.81:1`; against the surface
* that actually composites, light was understated and dark was OVERSTATED by
* 1.65 — the unsafe direction for anyone budgeting headroom against it.
*
* A MUTED TIMESTAMP IS THE OBVIOUS INSTINCT AND THE OBVIOUS WAY TO FAIL
* SC 1.4.3, so the numbers are recorded here rather than the intention.
* Compositing the body text over the body background:
*
* opacity 0.7 light 6.74:1 dark 7.66:1 both pass
* opacity 0.6 light 4.80:1 dark 5.94:1 both pass
* opacity 0.5 light 3.46:1 dark 4.51:1 LIGHT FAILS, DARK PASSES
*
* That last row is the trap in its most dangerous form: a dimmed timestamp
* looks correct to anyone working in dark theme and is a real failure for
* everyone else. So the timestamp is distinguished by TYPOGRAPHY AND POSITION
* — tabular figures, a hanging indent — and never by dimming. Do not add an
* opacity, a grey, or a --muted token to anything in this file without
* recomputing both themes and writing the numbers here.
*
* NO :focus OR :focus-visible RULE APPEARS IN THIS FILE, deliberately. The app
* already gives every control an inverted fill plus a coloured glow, measured
* at 7.3:1 light and 11.2:1 dark. A component-level box-shadow REPLACES that
* glow rather than adding to it, so a well-meant override is usually less
* prominent than doing nothing, plus one control that signals focus unlike
* every other. See AGENTS.md § Focus indicators.
*
* NOTHING HERE CHANGES THE ACCESSIBILITY TREE. No display:none, no
* visibility, no `content` that inserts text, nothing that folds or unfolds a
* node. The single rule that touches semantics at all is `list-style: none` —
* see the note on .transcribe-list.
*/
/* =========================================================================
THE UPLOAD AREA
========================================================================= */
/*
* Transcribe borrows the four .imgdesc-upload-* CHILD rules from
* image-describer.css but not the wrapper rule, because its wrapper is
* .transcribe-upload-area and image-describer.css scopes the frame to
* .imgdesc-upload-area. The result today is the CONTENTS of a drop zone with
* no drop zone around them.
*
* The frame is reproduced here rather than by widening the Image Describer's
* selector: that file belongs to another tool, and a shared selector would
* make either tool's restyle a change to both. Duplicating four declarations
* is the cheaper coupling.
*
* Values match image-describer.css:36-42 so the two tools look like siblings.
* The `transition` is deliberately NOT copied — Transcribe has no drag-over
* state to transition to, so it would animate nothing.
*/
.transcribe-upload-area {
border: 2px dashed currentColor;
border-radius: 0.5rem;
padding: 2rem;
text-align: center;
}
/* =========================================================================
PRE-RUN OPTIONS
========================================================================= */
.transcribe-options {
display: flex;
flex-wrap: wrap;
gap: 1rem;
margin: 1rem 0;
}
/*
* Each option takes a line's worth of width and is free to be narrower.
*
* `min-width: 0` IS LOAD-BEARING AND WAS ADDED AFTER MEASUREMENT, NOT BEFORE.
* A flex item defaults to `min-width: auto`, which refuses to shrink below its
* content's minimum — and the