/*
 * Where this plugin's own panel puts a control the theme has no slot for.
 *
 * Token-only, like every sheet in this product: nothing here invents a colour, a size or a
 * rhythm. It is deliberately almost empty. Every shape the calendar control wears — the row it
 * stands in, the link stretched over that row, the track the ledger grows for it and the
 * outlined circle itself — is the theme's markup vocabulary, and lives in the theme's
 * `style.css` beside the rest of the ledger, so a static pattern and a rendered block are
 * dressed by one sheet and a plugin update can never disagree with a theme it has not seen.
 *
 * What is left is the one thing the theme cannot know: where the control sits inside the
 * decision panel this plugin renders, where there is room for its words. Loaded only on the
 * pages whose blocks emit it.
 */

.lue-decision-panel__calendar {
	margin-block: var(--wp--preset--spacing--20) 0;
}

.lue-decision-panel__calendar .lue-calendar__label {
	margin-inline-start: var(--wp--preset--spacing--10);
}

/*
 * A board with nothing on it is not a board. Every programme is written into the frame and the
 * ones the filter dropped carry `hidden`, so the enhancement can bring a row back without
 * fetching anything — but the frame's own `display: flex` outranks the user agent's `[hidden]`
 * rule, and a 1.5px ink rule closed around a column header with no rows under it reads as a
 * rendering fault rather than as a result.
 */
.lue-board[hidden] {
	display: none;
}

/*
 * A session that has already run is a record, not an offer. The signal is spent on decisions, so
 * the past group's heading and its calendar glyph drop to ink-soft and its rows go with them;
 * the group keeps the ledger's shape, which is what says it is the same kind of thing.
 */
.lue-ledger > .lue-intake-row--past,
.lue-ledger__month--past > :where(h2, h3, h4) {
	color: var(--wp--preset--color--muted-foreground);
}

.lue-ledger-groups .lue-ledger__month--past > :where(h2, h3, h4) .lue-icon {
	color: inherit;
}

/*
 * The instructor seam's two columns are written by hand and never pass through core's layout
 * support, which is where a columns block's gap and its cleared bottom margin come from. Without
 * them the tile's right edge and the heading beside it sat on the same x, and core's 1.75em
 * bottom margin doubled the 64px section gap under the seam. 56px is the gap the theme's static
 * twin declares.
 */
.lue-instructor-seam .wp-block-columns {
	column-gap: var(--wp--preset--spacing--70);
	margin-block-end: 0;
	row-gap: var(--wp--preset--spacing--50);
}