/*
 * Hubka Theme
 *
 * Phase: 12B — Trust Strip
 * Purpose: A quiet, full-width confidence band between the Hero and
 * Featured Collection — four short statements, no icons, no product
 * data, no headline. Spacing alone marks the boundary from the
 * sections above and below, per HOMEPAGE_EDITORIAL_SPEC.md's "step"
 * (background-secondary) description.
 *
 * Rules:
 * - Reuse theme.json tokens.
 * - Use logical properties.
 * - Keep selectors shallow.
 * - Do not duplicate component styling.
 */

.hubka-trust-strip {
	padding-block: var(--wp--preset--spacing--60);
}

.hubka-trust-strip__row {
	gap: var(--wp--preset--spacing--40);
}

.hubka-trust-strip__label {
	font-weight: 600;
	margin-block-end: var(--wp--preset--spacing--20);
}

.hubka-trust-strip__phrase {
	line-height: 1.5;
}

@media (max-width: 782px) {
	.hubka-trust-strip {
		padding-block: var(--wp--preset--spacing--50);
	}

	.hubka-trust-strip__row {
		flex-wrap: wrap;
		gap: var(--wp--preset--spacing--40);
	}

	/* Real bug, found via live inspection (not the original !important
	 * alone, which looked sufficient on paper but wasn't): WordPress core
	 * ships its own mobile column-stacking rule —
	 * `.wp-block-columns:not(.is-not-stacked-on-mobile) > .wp-block-column
	 * { flex-basis: 100% !important; }` at specificity (0,3,0) — which
	 * beats a single-class !important selector at (0,1,0) regardless of
	 * source order, forcing every item to a full-width single column
	 * instead of 2x2. Matches the exact same class of core-vs-theme
	 * specificity fight already solved once in header.css (see its own
	 * revision notes) — same fix shape: add real ancestor classes until
	 * specificity reaches parity, confirmed live rather than assumed. */
	.hubka-trust-strip .hubka-trust-strip__row .hubka-trust-strip__item {
		flex-basis: calc(50% - var(--wp--preset--spacing--40) / 2) !important;
	}
}
