/* ==========================================================================
   GTCodes Community Home — v2.3.0 (plugin stylesheet, Reddit-style redesign)
   --------------------------------------------------------------------------
   Full rewrite of the v1.0.4 file on the ACTUAL GTCodes theme tokens
   (plan §1, brief §1 — Kadence palette, Overpass, purple/orange
   gradient buttons). No third palette, no Reddit branding.

   Tokens are defined under :root (fallback) AND .gtcch-home, so this
   file works standalone; every var() keeps a plain fallback. All
   rules are scoped under .gtcch-home, except the injected inner-page
   nav (.gtcch-inner-nav), which is scoped to body.page-id-61583
   #wpforo #wpforo-wrap (see "Inner-page nav" below).

   Class contract (plan §13): .gtcch-home, .gtcch-layout,
   .gtcch-side-nav (+ .is-active, .gtcch-side-nav-sections,
   .gtcch-side-nav-toggle), .gtcch-main, .gtcch-header,
   .gtcch-header-top, .gtcch-auth-bar (+ .gtcch-account,
   .gtcch-account-summary, .gtcch-account-menu), .gtcch-search,
   .gtcch-start (+ .gtcch-start-panel, .gtcch-start-step), .gtcch-nav,
   .gtcch-feed, .gtcch-sort (+ .is-active), .gtcch-filters,
   .gtcch-card (+ .gtcch-card-section, .gtcch-card-image),
   .gtcch-topic-list, .gtcch-topic-wrap,
   .gtcch-empty, .gtcch-pagination, .gtcch-games, .gtcch-game,
   .gtcch-game-pills, .gtcch-crumb, .gtcch-stats-line, .gtcch-inner-nav.
   Existing classes (.gtcch-btn, .gtcch-filter, .gtcch-pill,
   .gtcch-card-*) keep their names.

   v2.2.0 adds (appended at the end of this file): the header auth
   bar + account dropdown, the section/topic .wpf-head-bar card, the
   section topic-list card wrapper, the topic-page cards (topic head,
   posts, reply form, please-login), and the Forum Information hide.

   v2.2.1 adds (appended after the v2.2.0 block): the eight fixes
   for the v2.2.0 verification run — (1) board-home/?game= auth bar
   top-right (nowrap + margin-left:auto at >=769px), (2) section
   head bar as flex so the Start A Discussion button cannot cover
   the description, (3) topic-page wrap belt-and-braces at
   <=1024px, (4) account pill re-scoped past wpForo's summary
   reset on inner pages, (5) guest Reply span cursor (the
   navigation itself is gtcch-guest-reply-2.2.1.js), (6) the
   inner-nav <details> as the card at ALL widths, (7) 320px
   author-column nowrap + full-width attach input, (8)
   text-transform:none on .gtcch-card-title. Root causes are in
   the plugin header comment and the readme changelog.

   v2.3.0 adds (appended after the v2.2.1 block): the unified
   board top bar (brand + centre nav + the existing auth bar, on
   every board page), branded sign-in/sign-up forms (white card,
   gradient primary button, full-width fields), compact section
   breadcrumb + section H1, and the register helper note. The
   v2.2.1 fix-1/fix-2 rules are untouched — the header-top
   nowrap rule is now harmless (the header no longer contains
   an auth bar) and the section head-bar flex rule still guards
   the Start A Discussion button. The duplicate default-blue
   JOIN US! sidebar box is deliberately NOT hidden: no exact
   widget selector for it exists in the plugin, the checklist
   or any prior audit report, and a guessed selector could hide
   the wrong sidebar widget — hiding it needs the live served
   sidebar markup first (see the plugin header comment).

   Markup assumption for the side nav (B's ACTUAL markup, verified
   against gtcodes-community-home.php gtcch_side_nav_html()): the nav
   is <nav class="gtcch-side-nav"> containing a <details
   class="gtcch-side-nav-toggle"> rendered OPEN (v2.0.1) whose
   <summary> reads "Games" and whose <ul class="gtcch-side-nav-list">
   holds the links. The open attribute is what makes the list visible
   on desktop (the summary is hidden there): a closed <details>
   cannot be forced visible with display:block — modern Chrome hides
   closed-details content via content-visibility, which display does
   not override (v2.0.0 defect 1). With open present the UA rule
   (details:not([open])) never applies, in any browser. On mobile the
   details is the card, the summary is the toggle button, and the list
   starts open — tap the summary to close it, tap again to reopen.
   The same pattern applies inside .gtcch-inner-nav on inner pages.
   The inner-page nav itself is a plain <div class="gtcch-inner-nav">
   (NOT a <details>): on mobile it is a static block above the board,
   and the collapse comes from the <details> inside it.
   ========================================================================== */

/* ---------- Tokens ---------- */
:root {
	--gtc-primary: #8920f3;
	--gtc-primary-dark: #6022a0;
	--gtc-primary-darker: #290342;
	--gtc-primary-soft: #f7f2fc;
	--gtc-primary-softer: #e3ddec;
	--gtc-accent: #ff7c58;
	--gtc-accent-soft: #fff1ec;
	--gtc-bg: #f7f2fc;
	--gtc-card: #ffffff;
	--gtc-border: #e3ddec;
	--gtc-border-strong: #d1d5db;
	--gtc-text: #3b383e;
	--gtc-text-soft: #646366;
	--gtc-text-muted: #6d6d6f;
	--gtc-text-faint: #9ca3af;
	--gtc-success: #13612e;
	--gtc-danger: #b82105;
	--gtc-warning: #f5a524;
	--gtc-font-body: 'Overpass', sans-serif;
	--gtc-font-head: 'Overpass', sans-serif;
	--gtc-radius: 10px;
	--gtc-radius-sm: 8px;
	--gtc-radius-pill: 100px;
	--gtc-shadow: 0 1px 2px rgba(17, 24, 39, .06);
	--gtc-shadow-hover: 0 4px 12px rgba(17, 24, 39, .10);
	--gtc-shadow-btn: 0 15px 25px -7px rgba(0, 0, 0, .25);
	--gtc-transition: all 0.2s ease;
	--gtc-container: 1290px;
}
.gtcch-home {
	--gtc-primary: #8920f3;
	--gtc-primary-dark: #6022a0;
	--gtc-primary-darker: #290342;
	--gtc-primary-soft: #f7f2fc;
	--gtc-primary-softer: #e3ddec;
	--gtc-accent: #ff7c58;
	--gtc-accent-soft: #fff1ec;
	--gtc-bg: #f7f2fc;
	--gtc-card: #ffffff;
	--gtc-border: #e3ddec;
	--gtc-border-strong: #d1d5db;
	--gtc-text: #3b383e;
	--gtc-text-soft: #646366;
	--gtc-text-muted: #6d6d6f;
	--gtc-text-faint: #9ca3af;
	--gtc-success: #13612e;
	--gtc-danger: #b82105;
	--gtc-warning: #f5a524;
	--gtc-font-body: 'Overpass', sans-serif;
	--gtc-font-head: 'Overpass', sans-serif;
	--gtc-radius: 10px;
	--gtc-radius-sm: 8px;
	--gtc-radius-pill: 100px;
	--gtc-shadow: 0 1px 2px rgba(17, 24, 39, .06);
	--gtc-shadow-hover: 0 4px 12px rgba(17, 24, 39, .10);
	--gtc-shadow-btn: 0 15px 25px -7px rgba(0, 0, 0, .25);
	--gtc-transition: all 0.2s ease;
	--gtc-container: 1290px;
}

/* ---------- Base ---------- */
.gtcch-home {
	font-family: var(--gtc-font-body, 'Overpass', sans-serif);
	font-size: 16px;
	line-height: 1.55;
	color: var(--gtc-text, #3b383e);
}
.gtcch-home *,
.gtcch-home *::before,
.gtcch-home *::after {
	box-sizing: border-box;
}
.gtcch-home img {
	max-width: 100%;
	height: auto;
}
.gtcch-home a {
	color: var(--gtc-primary, #8920f3);
	text-decoration: none;
	overflow-wrap: break-word;
}
.gtcch-home a:hover {
	text-decoration: underline;
}
.gtcch-home a:focus-visible,
.gtcch-home button:focus-visible,
.gtcch-home input:focus-visible,
.gtcch-home summary:focus-visible {
	outline: 3px solid var(--gtc-primary-softer, #e3ddec);
	outline-offset: 2px;
}
.gtcch-screen-reader-text {
	position: absolute;
	width: 1px;
	height: 1px;
	padding: 0;
	margin: -1px;
	overflow: hidden;
	clip: rect(0, 0, 0, 0);
	white-space: nowrap;
	border: 0;
}

/* ---------- Buttons ----------
   Site CTA style: purple-to-orange gradient, white text, Overpass
   600, capitalize, 100px pill, 13px 28px, no border. Hover flips
   the gradient to 135deg and adds the theme shadow. */
.gtcch-btn {
	display: inline-flex;
	align-items: center;
	justify-content: center;
	gap: 6px;
	min-height: 44px;
	padding: 13px 28px;
	font-family: var(--gtc-font-head, 'Overpass', sans-serif);
	font-size: 16px;
	font-weight: 600;
	line-height: 1.2;
	text-transform: capitalize;
	color: #fff;
	background: linear-gradient(43deg, #8920f3 0%, #ff7c58 100%);
	background-color: var(--gtc-primary, #8920f3);
	border: 0;
	border-radius: 100px;
	cursor: pointer;
	text-decoration: none;
	white-space: nowrap;
	transition: var(--gtc-transition, all 0.2s ease);
}
.gtcch-btn:hover,
.gtcch-btn:focus-visible {
	background: linear-gradient(135deg, #8920f3 0%, #ff7c58 100%);
	background-color: var(--gtc-primary, #8920f3);
	box-shadow: var(--gtc-shadow-btn, 0 15px 25px -7px rgba(0, 0, 0, .25));
	color: #fff;
	text-decoration: none;
	transform: translateY(-1px);
}
/* v2.0.0 — carried over from the v1.0.1 fix, re-scoped to the new
   tokens: the per-game "Start a Discussion" button is an
   <a class="gtcch-btn">, and its white label loses to link-color
   rules at (0,1,1) — the plugin's own .gtcch-home a rule AND the
   theme's .entry-content a rule — unless this (0,3,2) rule wins
   for the base, hover and focus states. No !important needed. */
body.page-id-61583 .gtcch-home a.gtcch-btn,
body.page-id-61583 .gtcch-home a.gtcch-btn:hover,
body.page-id-61583 .gtcch-home a.gtcch-btn:focus-visible {
	color: #fff;
}
.gtcch-btn-small {
	min-height: 40px;
	padding: 8px 14px;
	font-size: 14px;
}
/* Secondary / outline button: white fill, primary border + text. */
.gtcch-btn-secondary {
	color: var(--gtc-primary, #8920f3);
	background: #fff;
	background-image: none;
	border: 2px solid var(--gtc-primary, #8920f3);
	box-shadow: none;
}
.gtcch-btn-secondary:hover,
.gtcch-btn-secondary:focus-visible {
	color: var(--gtc-primary-dark, #6022a0);
	background: var(--gtc-primary-soft, #f7f2fc);
	background-image: none;
	border-color: var(--gtc-primary-dark, #6022a0);
	box-shadow: none;
}
body.page-id-61583 .gtcch-home a.gtcch-btn-secondary,
body.page-id-61583 .gtcch-home a.gtcch-btn-secondary:hover,
body.page-id-61583 .gtcch-home a.gtcch-btn-secondary:focus-visible {
	color: var(--gtc-primary, #8920f3);
}
body.page-id-61583 .gtcch-home a.gtcch-btn-secondary:hover,
body.page-id-61583 .gtcch-home a.gtcch-btn-secondary:focus-visible {
	color: var(--gtc-primary-dark, #6022a0);
}

/* ---------- Board-home layout ----------
   Left game nav 220px + main feed 1fr. The Kadence right sidebar
   stays as the page's right column; the plugin does not move it. */
.gtcch-layout {
	display: grid;
	grid-template-columns: 220px minmax(0, 1fr);
	gap: 20px;
	align-items: start;
	min-width: 0;
}
.gtcch-main {
	min-width: 0;
}

/* ---------- Left side nav ----------
   "Home / All Discussions" + the 5 games; when a game is selected
   its sections list under it (live data, never hardcoded). */
.gtcch-side-nav {
	position: sticky;
	top: 16px;
	background: #fff;
	border: 1px solid var(--gtc-border, #e3ddec);
	border-radius: 10px;
	box-shadow: var(--gtc-shadow, 0 1px 2px rgba(17, 24, 39, .06));
	padding: 12px;
}
.gtcch-side-nav ul,
.gtcch-side-nav .gtcch-side-nav-list {
	list-style: none;
	margin: 0;
	padding: 0;
}
.gtcch-side-nav li {
	margin: 0;
	padding: 0;
}
.gtcch-side-nav a {
	display: flex;
	align-items: center;
	gap: 8px;
	padding: 9px 10px;
	font-size: 15px;
	font-weight: 600;
	line-height: 1.4;
	color: var(--gtc-text, #3b383e);
	border-radius: 8px;
	text-decoration: none;
	overflow-wrap: break-word;
}
.gtcch-side-nav a:hover {
	background: var(--gtc-primary-soft, #f7f2fc);
	color: var(--gtc-primary, #8920f3);
	text-decoration: none;
}
/* Current game AND current section: tinted fill, primary text,
   primary left bar; aria-current is styled the same as .is-active
   so either marker works. */
.gtcch-side-nav a.is-active,
.gtcch-side-nav a[aria-current="page"],
.gtcch-side-nav a[aria-current="true"] {
	background: var(--gtc-primary-soft, #f7f2fc);
	color: var(--gtc-primary, #8920f3);
	box-shadow: inset 3px 0 0 var(--gtc-primary, #8920f3);
}
/* Sections of the selected game, indented under it. */
.gtcch-side-nav-sections {
	margin: 2px 0 6px 12px;
	padding-left: 10px;
	border-left: 2px solid var(--gtc-border, #e3ddec);
}
.gtcch-side-nav-sections a {
	padding: 7px 10px;
	font-size: 14px;
	font-weight: 600;
}
/* The <details> toggle (B's markup: <details
   class="gtcch-side-nav-toggle"> INSIDE <nav class="gtcch-side-nav">,
   rendered OPEN by gtcch_side_nav_html() since v2.0.1). The open
   attribute — not CSS — is what keeps the list visible on desktop:
   the UA hiding rule only matches details:not([open]), so with open
   present it never applies, in any browser. v2.0.0 tried to force a
   CLOSED details visible with display:block on the list; that does
   NOT work — modern Chrome hides closed-details content via
   content-visibility, which display does not override (Step 1A
   defect 1: empty left nav on desktop). Do NOT remove the open
   attribute from the markup, and do NOT set display:none on the
   details itself — that would hide the whole nav. The display:block
   rules below are belt-and-braces for older UAs only. */
.gtcch-side-nav .gtcch-side-nav-toggle {
	display: block;
}
.gtcch-side-nav .gtcch-side-nav-toggle > summary {
	display: none;
	list-style: none;
}
.gtcch-side-nav .gtcch-side-nav-toggle > summary::-webkit-details-marker {
	display: none;
}
.gtcch-side-nav .gtcch-side-nav-toggle > .gtcch-side-nav-list {
	display: block;
}

/* ---------- Header ---------- */
.gtcch-header {
	background: #fff;
	border: 1px solid var(--gtc-border, #e3ddec);
	border-radius: 10px;
	box-shadow: var(--gtc-shadow, 0 1px 2px rgba(17, 24, 39, .06));
	padding: 16px 12px;
	margin: 0 0 16px;
}
.gtcch-header h1 {
	font-size: 40px;
	font-weight: 700;
	line-height: 1.2;
	font-family: var(--gtc-font-head, 'Overpass', sans-serif);
	text-transform: capitalize;
	color: var(--gtc-primary-darker, #290342);
	margin: 0 0 4px;
}

/* v2.1.0 (audit S14/S15): H1 injected by the plugin on the Members /
   sign-in / sign-up pages, which have no H1 of their own. Same H1
   tokens as the board-home header. The stylesheet loads on every
   board page, so this rule applies on those inner pages too. */
.gtcch-page-h1 {
	font-size: 40px;
	font-weight: 700;
	line-height: 1.2;
	font-family: var(--gtc-font-head, 'Overpass', sans-serif);
	text-transform: capitalize;
	color: var(--gtc-primary-darker, #290342);
	margin: 0 0 12px;
}
.gtcch-subtitle {
	font-size: 15px;
	line-height: 1.5;
	color: var(--gtc-text-muted, #6d6d6f);
	margin: 0 0 12px;
}
.gtcch-header-row {
	display: flex;
	flex-wrap: wrap;
	align-items: center;
	gap: 12px;
}
.gtcch-search {
	display: flex;
	gap: 8px;
	flex: 1 1 280px;
	max-width: 340px;
}
.gtcch-search input[type="search"] {
	flex: 1 1 auto;
	min-width: 0;
	height: 44px;
	padding: 0 14px;
	font-family: var(--gtc-font-body, 'Overpass', sans-serif);
	font-size: 15px;
	line-height: 1.4;
	color: var(--gtc-text, #3b383e);
	background: #fff;
	border: 1px solid var(--gtc-border, #e3ddec);
	border-radius: 100px;
}
.gtcch-search input[type="search"]:focus {
	outline: 2px solid var(--gtc-primary, #8920f3);
	outline-offset: 1px;
	border-color: var(--gtc-primary, #8920f3);
}

/* ---------- Breadcrumb (board home / game-filtered views) ----------
   Plugin breadcrumb only; inner pages keep wpForo's own breadcrumb. */
.gtcch-crumb {
	display: flex;
	flex-wrap: wrap;
	align-items: center;
	gap: 4px 8px;
	font-size: 13px;
	line-height: 1.5;
	color: var(--gtc-text-muted, #6d6d6f);
	margin: 0 0 12px;
	padding: 0;
	list-style: none;
}
.gtcch-crumb li {
	margin: 0;
	padding: 0;
}
.gtcch-crumb li + li::before {
	content: "\203A";
	color: var(--gtc-text-faint, #9ca3af);
	margin-right: 8px;
}
.gtcch-crumb a {
	color: var(--gtc-text-muted, #6d6d6f);
	font-weight: 500;
}
.gtcch-crumb a:hover {
	color: var(--gtc-primary, #8920f3);
}
.gtcch-crumb [aria-current="page"],
.gtcch-crumb li:last-child {
	color: var(--gtc-text, #3b383e);
	font-weight: 600;
}

/* ---------- Game page (?game=<slug>) ----------
   Breadcrumb + intro paragraph + section pills. v2.1.0: the game
   H1 ("[Game] Community") is the header H1 now (one H1 per page),
   so this block no longer renders its own title; the intro is the
   same muted 15px line the game cards use. .gtcch-game-title is
   retained (unused since v2.1.0) for compatibility. */
.gtcch-game-page {
	margin: 0 0 4px;
}
.gtcch-game-title {
	font-size: 30px;
	font-weight: 700;
	line-height: 1.3;
	font-family: var(--gtc-font-head, 'Overpass', sans-serif);
	text-transform: capitalize;
	color: var(--gtc-primary-darker, #290342);
	margin: 0 0 4px;
}
.gtcch-game-line {
	font-size: 15px;
	line-height: 1.5;
	color: var(--gtc-text-muted, #6d6d6f);
	margin: 0 0 10px;
}

/* v2.1.0: game-page introduction (built from the live game name +
   section titles). Same muted 15px line as .gtcch-game-line. */
.gtcch-game-intro {
	font-size: 15px;
	line-height: 1.5;
	color: var(--gtc-text-muted, #6d6d6f);
	margin: 0 0 10px;
}

/* ---------- Stats line ---------- */
.gtcch-stats-line {
	font-size: 13px;
	line-height: 1.5;
	color: var(--gtc-text-muted, #6d6d6f);
	margin: -6px 0 12px;
}
.gtcch-stats-line b {
	color: var(--gtc-text, #3b383e);
}

/* ---------- Start a Discussion chooser ----------
   Two-step picker (plan §3): Step 1 lists the 5 games, Step 2
   lists ALL live sections of the picked game; Other Games adds a
   "Which game is this about?" text field. Steps are .gtcch-start-step
   blocks; only the active step is shown (PHP/JS toggles [hidden]). */
.gtcch-start {
	position: relative;
	flex: 0 0 auto;
}
.gtcch-start-summary {
	list-style: none;
}
.gtcch-start-summary::-webkit-details-marker {
	display: none;
}
.gtcch-start-panel {
	position: absolute;
	top: calc(100% + 8px);
	right: 0;
	z-index: 20;
	min-width: 280px;
	max-width: calc(100vw - 32px);
	background: #fff;
	border: 1px solid var(--gtc-border, #e3ddec);
	border-radius: 10px;
	box-shadow: 0 4px 12px rgba(17, 24, 39, .10);
	padding: 12px 14px;
}
.gtcch-start-step[hidden],
.gtcch-start-step-1[hidden],
.gtcch-start-step-2[hidden] {
	display: none;
}
.gtcch-start-step p {
	font-size: 13px;
	font-weight: 600;
	line-height: 1.5;
	color: var(--gtc-text-muted, #6d6d6f);
	margin: 0 0 8px;
}
.gtcch-start-step ul {
	list-style: none;
	margin: 0;
	padding: 0;
}
.gtcch-start-step li {
	margin: 0;
	padding: 0;
}
.gtcch-start-step li a,
.gtcch-start-step li button,
.gtcch-start-step .gtcch-start-section,
.gtcch-start-step .gtcch-start-game {
	display: block;
	width: 100%;
	padding: 8px 10px;
	font-family: var(--gtc-font-body, 'Overpass', sans-serif);
	font-size: 14px;
	font-weight: 600;
	line-height: 1.4;
	text-align: left;
	color: var(--gtc-text, #3b383e);
	background: transparent;
	border: 0;
	border-radius: 8px;
	cursor: pointer;
}
.gtcch-start-step li a:hover,
.gtcch-start-step li button:hover {
	background: var(--gtc-primary-soft, #f7f2fc);
	color: var(--gtc-primary, #8920f3);
	text-decoration: none;
}
.gtcch-start-step .gtcch-start-back {
	display: inline-flex;
	align-items: center;
	gap: 4px;
	padding: 6px 0;
	font-size: 13px;
	font-weight: 600;
	color: var(--gtc-text-muted, #6d6d6f);
	background: transparent;
	border: 0;
	cursor: pointer;
}
.gtcch-start-step .gtcch-start-back:hover {
	color: var(--gtc-primary, #8920f3);
}
.gtcch-start-step label {
	display: block;
	font-size: 13px;
	font-weight: 600;
	line-height: 1.5;
	color: var(--gtc-text-soft, #646366);
	margin: 0 0 6px;
}
.gtcch-start-step input[type="text"] {
	width: 100%;
	min-height: 44px;
	padding: 10px 12px;
	font-family: var(--gtc-font-body, 'Overpass', sans-serif);
	font-size: 15px;
	line-height: 1.4;
	color: var(--gtc-text, #3b383e);
	background: #fff;
	border: 1px solid var(--gtc-border-strong, #d1d5db);
	border-radius: 8px;
}
.gtcch-start-step input[type="text"]:focus {
	outline: none;
	border-color: var(--gtc-primary, #8920f3);
	box-shadow: 0 0 0 3px var(--gtc-primary-softer, #e3ddec);
}
/* "Which game is this about?" panel (Other Games step). The picker
   JS toggles the native [hidden] attribute on .gtcch-start-other —
   NOTHING here may override [hidden] to display:block; the
   [hidden] rule below only reinforces the browser default. */
.gtcch-start-other[hidden] {
	display: none;
}
.gtcch-start-other {
	padding-top: 4px;
}
.gtcch-start-other label {
	display: block;
	font-size: 13px;
	font-weight: 600;
	line-height: 1.5;
	color: var(--gtc-text-soft, #646366);
	margin: 0 0 6px;
}
.gtcch-other-game-name {
	width: 100%;
	min-height: 44px;
	padding: 10px 12px;
	font-family: var(--gtc-font-body, 'Overpass', sans-serif);
	font-size: 15px;
	line-height: 1.4;
	color: var(--gtc-text, #3b383e);
	background: #fff;
	border: 1px solid var(--gtc-border-strong, #d1d5db);
	border-radius: 8px;
}
.gtcch-other-game-name:focus {
	outline: none;
	border-color: var(--gtc-primary, #8920f3);
	box-shadow: 0 0 0 3px var(--gtc-primary-softer, #e3ddec);
}
.gtcch-start-other-go {
	margin-top: 8px;
}
.gtcch-start-other-cancel {
	display: inline-flex;
	align-items: center;
	min-height: 44px;
	padding: 10px 8px;
	margin-left: 6px;
	font-family: var(--gtc-font-body, 'Overpass', sans-serif);
	font-size: 13px;
	font-weight: 600;
	line-height: 1.4;
	color: var(--gtc-text-muted, #6d6d6f);
	background: transparent;
	border: 0;
	border-radius: 8px;
	cursor: pointer;
}
.gtcch-start-other-cancel:hover {
	color: var(--gtc-primary, #8920f3);
}
.gtcch-start-other-note {
	font-size: 12px;
	line-height: 1.5;
	color: var(--gtc-text-muted, #6d6d6f);
	margin: 8px 0 0;
}

/* ---------- Forum nav ----------
   Fit constraint (v2.0.1, Step 1A defect 2 — measured from the live
   Kadence layout): at a 1919px viewport the main column is ~500px
   wide (1290px container, 5fr/2fr content/sidebar grid with a 63px
   gap, 32px article padding, 220px left nav + 20px grid gap), and
   the header card takes 12px padding each side — so the nav row has
   roughly 490px for six items (Forums, Recent Discussions,
   Unanswered, Members, Register/Login or My Profile/Logout). The
   v2.0.0 sizing (14px, 10px 14px padding) needed ~560px, so the last
   items clipped ("Regist", "My Pro"). 13px type with 9px 7px padding
   (login pill 8px 10px) brings the logged-in row to ~478px — inside
   the available width with slack at desktop widths. Do NOT grow the
   padding or font back without re-measuring. overflow-x:auto stays
   as the fallback for narrower desktop viewports (1025–1280px the
   column shrinks and the row scrolls, as the Phase 1 wpForo menu
   already does); the hidden scrollbars match that menu. */
.gtcch-nav {
	display: flex;
	align-items: center;
	gap: 2px;
	overflow-x: auto;
	overflow-y: hidden;
	white-space: nowrap;
	scrollbar-width: none;
	-webkit-overflow-scrolling: touch;
	margin: 0 0 8px;
	padding: 0;
	border-bottom: 1px solid var(--gtc-border, #e3ddec);
}
.gtcch-nav::-webkit-scrollbar {
	display: none;
}
.gtcch-nav a {
	display: inline-flex;
	align-items: center;
	flex: 0 0 auto;
	padding: 9px 7px;
	font-size: 13px;
	font-weight: 600;
	line-height: 1.4;
	color: var(--gtc-text-soft, #646366);
	border-bottom: 2px solid transparent;
	text-decoration: none;
	white-space: nowrap;
}
.gtcch-nav a:hover {
	color: var(--gtc-primary, #8920f3);
	text-decoration: none;
}
.gtcch-nav a.is-active {
	color: var(--gtc-primary, #8920f3);
	border-bottom-color: var(--gtc-primary, #8920f3);
}
.gtcch-nav a.gtcch-nav-login {
	margin-left: auto;
	margin-bottom: 6px;
	padding: 8px 10px;
	font-size: 13px;
	font-weight: 700;
	color: #fff;
	background: linear-gradient(43deg, #8920f3 0%, #ff7c58 100%);
	background-color: var(--gtc-primary, #8920f3);
	border: 0;
	border-bottom: 0;
	border-radius: 100px;
}
.gtcch-nav a.gtcch-nav-login:hover {
	background: linear-gradient(135deg, #8920f3 0%, #ff7c58 100%);
	background-color: var(--gtc-primary, #8920f3);
	box-shadow: var(--gtc-shadow-btn, 0 15px 25px -7px rgba(0, 0, 0, .25));
	color: #fff;
}

/* ---------- Section headings ---------- */
.gtcch-feed > h2,
.gtcch-games > h2 {
	font-size: 30px;
	font-weight: 700;
	line-height: 1.3;
	font-family: var(--gtc-font-head, 'Overpass', sans-serif);
	text-transform: capitalize;
	color: var(--gtc-primary-darker, #290342);
	margin: 16px 0 12px;
}
.gtcch-feed-count {
	font-size: 13px;
	color: var(--gtc-text-muted, #6d6d6f);
	margin: -6px 0 12px;
}

/* ---------- Sort controls (Latest / Popular / Unanswered / All) ---------- */
.gtcch-sort {
	display: flex;
	flex-wrap: wrap;
	gap: 6px;
	margin: 0 0 14px;
}
.gtcch-sort a,
.gtcch-sort button,
.gtcch-sort .gtcch-sort-link {
	display: inline-flex;
	align-items: center;
	padding: 6px 12px;
	font-family: var(--gtc-font-body, 'Overpass', sans-serif);
	font-size: 13px;
	font-weight: 600;
	line-height: 1.4;
	color: var(--gtc-text, #3b383e);
	background: #fff;
	border: 1px solid var(--gtc-border, #e3ddec);
	border-radius: 100px;
	cursor: pointer;
	text-decoration: none;
}
.gtcch-sort a:hover,
.gtcch-sort button:hover {
	border-color: var(--gtc-primary, #8920f3);
	color: var(--gtc-primary, #8920f3);
	text-decoration: none;
}
.gtcch-sort a.is-active,
.gtcch-sort button.is-active,
.gtcch-sort .is-active {
	background: linear-gradient(43deg, #8920f3 0%, #ff7c58 100%);
	background-color: var(--gtc-primary, #8920f3);
	border-color: var(--gtc-primary, #8920f3);
	color: #fff;
}

/* ---------- Game filter pills ---------- */
.gtcch-filters {
	display: flex;
	flex-wrap: wrap;
	gap: 6px;
	margin: 0 0 14px;
}
.gtcch-filter {
	display: inline-flex;
	align-items: center;
	padding: 6px 12px;
	font-size: 13px;
	font-weight: 600;
	line-height: 1.4;
	color: var(--gtc-text, #3b383e);
	background: #fff;
	border: 1px solid var(--gtc-border, #e3ddec);
	border-radius: 100px;
	text-decoration: none;
}
.gtcch-filter:hover {
	border-color: var(--gtc-primary, #8920f3);
	color: var(--gtc-primary, #8920f3);
	text-decoration: none;
}
.gtcch-filter.is-active {
	background: linear-gradient(43deg, #8920f3 0%, #ff7c58 100%);
	background-color: var(--gtc-primary, #8920f3);
	border-color: var(--gtc-primary, #8920f3);
	color: #fff;
}

/* Feed list wrapper (cards live inside it). */
.gtcch-feed-list {
	display: block;
	min-width: 0;
}

/* ---------- Discussion cards ---------- */
.gtcch-card {
	display: flex;
	gap: 12px;
	background: #fff;
	border: 1px solid var(--gtc-border, #e3ddec);
	border-radius: 10px;
	box-shadow: var(--gtc-shadow, 0 1px 2px rgba(17, 24, 39, .06));
	padding: 14px 16px;
	margin: 0 0 10px;
	min-width: 0;
	overflow-wrap: break-word;
}
.gtcch-card:hover {
	border-color: var(--gtc-border-strong, #d1d5db);
}
.gtcch-card-avatar {
	flex: 0 0 40px;
}
.gtcch-card-avatar img.avatar {
	width: 40px;
	height: 40px;
	border-radius: 50%;
	object-fit: cover;
	display: block;
}
.gtcch-card-main {
	flex: 1 1 auto;
	min-width: 0;
}
.gtcch-card-meta {
	display: flex;
	flex-wrap: wrap;
	align-items: center;
	gap: 4px 8px;
	font-size: 13px;
	line-height: 1.5;
	color: var(--gtc-text-muted, #6d6d6f);
	margin-bottom: 2px;
}
.gtcch-card-author {
	font-weight: 600;
	color: var(--gtc-text, #3b383e);
}
.gtcch-card-sep {
	color: var(--gtc-text-muted, #6d6d6f);
}
/* Game pill: purple tint. Section label: white with border, so the
   two labels stay visually distinct on the same card. */
.gtcch-card-game {
	display: inline-flex;
	align-items: center;
	padding: 2px 8px;
	font-size: 12px;
	font-weight: 700;
	line-height: 1.5;
	color: var(--gtc-primary-dark, #6022a0);
	background: var(--gtc-primary-soft, #f7f2fc);
	border-radius: 100px;
	white-space: nowrap;
	text-decoration: none;
}
.gtcch-card-game:hover {
	text-decoration: none;
}
.gtcch-card-section {
	display: inline-flex;
	align-items: center;
	padding: 2px 8px;
	font-size: 12px;
	font-weight: 700;
	line-height: 1.5;
	color: var(--gtc-text-soft, #646366);
	background: #fff;
	border: 1px solid var(--gtc-border, #e3ddec);
	border-radius: 100px;
	white-space: nowrap;
	text-decoration: none;
}
.gtcch-card-section:hover {
	border-color: var(--gtc-primary, #8920f3);
	color: var(--gtc-primary, #8920f3);
	text-decoration: none;
}
.gtcch-card-title {
	font-size: 18px;
	font-weight: 600;
	line-height: 1.4;
	color: var(--gtc-primary-darker, #290342);
	margin: 0 0 2px;
}
.gtcch-card-title a {
	color: var(--gtc-primary-darker, #290342);
}
.gtcch-card-title a:hover {
	color: var(--gtc-primary, #8920f3);
}
.gtcch-card-excerpt {
	display: -webkit-box;
	-webkit-line-clamp: 2;
	-webkit-box-orient: vertical;
	overflow: hidden;
	font-size: 15px;
	line-height: 1.5;
	color: var(--gtc-text-muted, #6d6d6f);
	margin: 2px 0 6px;
}
/* Optional image preview: first image of the topic's first post,
   lazy-loaded by the markup; constrained so cards stay compact.
   The link wrapper is a plain block (the <img> itself carries
   .gtcch-card-image and the sizing). */
.gtcch-card-image-link {
	display: block;
	text-decoration: none;
}
.gtcch-card-image-link:hover {
	text-decoration: none;
}
.gtcch-card-image {
	display: block;
	width: 100%;
	max-height: 180px;
	margin: 8px 0 6px;
	object-fit: cover;
	border: 1px solid var(--gtc-border, #e3ddec);
	border-radius: 8px;
	overflow: hidden;
}
.gtcch-card-image img {
	display: block;
	width: 100%;
	max-height: 180px;
	object-fit: cover;
	border-radius: 8px;
}
.gtcch-card-foot {
	display: flex;
	flex-wrap: wrap;
	gap: 4px 14px;
	font-size: 13px;
	color: var(--gtc-text-muted, #6d6d6f);
}
.gtcch-card-foot .gtcch-card-likes {
	white-space: nowrap;
}

/* ---------- Empty state ---------- */
.gtcch-empty {
	background: #fff;
	border: 1px dashed var(--gtc-border-strong, #d1d5db);
	border-radius: 10px;
	padding: 32px 20px;
	text-align: center;
}
.gtcch-empty-title {
	font-size: 17px;
	font-weight: 700;
	line-height: 1.45;
	color: var(--gtc-text, #3b383e);
	margin: 0 0 6px;
}
.gtcch-empty p {
	font-size: 14px;
	color: var(--gtc-text-muted, #6d6d6f);
	margin: 0 0 14px;
}
.gtcch-empty .gtcch-start {
	display: inline-block;
	text-align: left;
}
.gtcch-empty .gtcch-start-panel {
	left: 50%;
	right: auto;
	transform: translateX(-50%);
}
.gtcch-empty-clear {
	margin: 14px 0 0;
}

/* ---------- Pagination ---------- */
.gtcch-pagination {
	display: flex;
	flex-wrap: wrap;
	align-items: center;
	gap: 6px;
	margin: 16px 0 0;
}
.gtcch-pagination a,
.gtcch-pagination .gtcch-page-num,
.gtcch-pagination span.gtcch-page-current,
.gtcch-pagination span.gtcch-page-gap {
	display: inline-flex;
	align-items: center;
	justify-content: center;
	min-width: 36px;
	min-height: 36px;
	padding: 6px 10px;
	font-size: 14px;
	font-weight: 600;
	line-height: 1.4;
	border: 1px solid var(--gtc-border, #e3ddec);
	border-radius: 8px;
	background: #fff;
	color: var(--gtc-text, #3b383e);
	text-decoration: none;
}
.gtcch-pagination a:hover {
	border-color: var(--gtc-primary, #8920f3);
	color: var(--gtc-primary, #8920f3);
	text-decoration: none;
}
.gtcch-pagination span.gtcch-page-current {
	background: var(--gtc-primary, #8920f3);
	border-color: var(--gtc-primary, #8920f3);
	color: #fff;
}
.gtcch-pagination span.gtcch-page-gap {
	border-color: transparent;
	background: transparent;
	color: var(--gtc-text-muted, #6d6d6f);
}
.gtcch-pagination .gtcch-page-info {
	border: 0;
	background: transparent;
	font-weight: 400;
	color: var(--gtc-text-muted, #6d6d6f);
	padding-left: 0;
}
.gtcch-pagination .gtcch-page-prev,
.gtcch-pagination .gtcch-page-next {
	padding: 6px 12px;
}

/* ---------- Browse Games cards ----------
   Simplified per spec §10: one short line per game at most, no
   repeated full section descriptions. The old "What each section
   is for" details block keeps its styles for backwards
   compatibility, but the v2 template does not render it. */
.gtcch-games-grid {
	display: block;
}
.gtcch-game {
	background: #fff;
	border: 1px solid var(--gtc-border, #e3ddec);
	border-radius: 10px;
	box-shadow: var(--gtc-shadow, 0 1px 2px rgba(17, 24, 39, .06));
	padding: 14px 16px;
	margin: 0 0 12px;
	min-width: 0;
}
.gtcch-game-head {
	display: flex;
	flex-wrap: wrap;
	align-items: center;
	gap: 8px 12px;
	padding-bottom: 10px;
	border-bottom: 1px solid var(--gtc-border, #e3ddec);
}
.gtcch-game-name {
	flex: 1 1 auto;
	font-size: 18px;
	font-weight: 700;
	line-height: 1.3;
	color: var(--gtc-primary-darker, #290342);
	margin: 0;
	min-width: 0;
}
.gtcch-game-name a {
	color: var(--gtc-primary-darker, #290342);
}
.gtcch-game-name a:hover {
	color: var(--gtc-primary, #8920f3);
}
.gtcch-game-counts {
	font-size: 13px;
	color: var(--gtc-text-muted, #6d6d6f);
	white-space: nowrap;
}
.gtcch-game-desc {
	font-size: 14px;
	line-height: 1.5;
	color: var(--gtc-text-muted, #6d6d6f);
	margin: 10px 0 0;
}
.gtcch-game-pills {
	display: flex;
	flex-wrap: wrap;
	gap: 6px;
	padding-top: 10px;
}
.gtcch-pill {
	display: inline-flex;
	align-items: center;
	padding: 6px 10px;
	font-size: 13px;
	font-weight: 600;
	line-height: 1.4;
	color: var(--gtc-text, #3b383e);
	background: #fff;
	border: 1px solid var(--gtc-border, #e3ddec);
	border-radius: 100px;
	text-decoration: none;
}
.gtcch-pill:hover {
	border-color: var(--gtc-primary, #8920f3);
	background: var(--gtc-primary-soft, #f7f2fc);
	color: var(--gtc-primary, #8920f3);
	text-decoration: none;
}
.gtcch-game-details {
	margin-top: 10px;
}
.gtcch-game-details summary {
	cursor: pointer;
	font-size: 13px;
	font-weight: 600;
	color: var(--gtc-primary, #8920f3);
	list-style: none;
}
.gtcch-game-details summary::-webkit-details-marker {
	display: none;
}
.gtcch-game-details dl {
	margin: 8px 0 0;
	display: grid;
	gap: 6px;
}
.gtcch-game-details dt {
	font-size: 14px;
	font-weight: 600;
	line-height: 1.4;
}
.gtcch-game-details dd {
	font-size: 14px;
	line-height: 1.5;
	color: var(--gtc-text-muted, #6d6d6f);
	margin: 0;
}

/* ---------- Inner-page injected nav ----------
   The plugin injects .gtcch-inner-nav via the wpforo_content_start
   hook INSIDE .wpforo-content. There is no wrapper, so NO grid is
   used on .wpforo-content or .entry-content (unverified children):
   on desktop the nav is an absolute left column inside the
   relatively-positioned .wpforo-content, which gets ~240px of left
   padding; on mobile the div is a static block above the board and
   the collapse comes from the <details class="gtcch-side-nav-toggle">
   inside it (the div itself is NOT a <details> and has no [open]
   state). Everything is scoped to body.page-id-61583. The injected
   nav contains a <nav class="gtcch-side-nav"> of its own, so its
   card/sticky styling is neutralised below — the outer
   .gtcch-inner-nav is the card. */
body.page-id-61583 .gtcch-inner-nav {
	box-sizing: border-box;
	background: #fff;
	border: 1px solid var(--gtc-border, #e3ddec);
	border-radius: 10px;
	box-shadow: var(--gtc-shadow, 0 1px 2px rgba(17, 24, 39, .06));
	padding: 12px;
}
body.page-id-61583 .gtcch-inner-nav ul {
	list-style: none;
	margin: 0;
	padding: 0;
}
body.page-id-61583 .gtcch-inner-nav li {
	margin: 0;
	padding: 0;
}
body.page-id-61583 .gtcch-inner-nav a {
	display: flex;
	align-items: center;
	gap: 8px;
	padding: 9px 10px;
	font-family: var(--gtc-font-body, 'Overpass', sans-serif);
	font-size: 15px;
	font-weight: 600;
	line-height: 1.4;
	color: var(--gtc-text, #3b383e);
	border-radius: 8px;
	text-decoration: none;
	overflow-wrap: break-word;
}
body.page-id-61583 .gtcch-inner-nav a:hover {
	background: var(--gtc-primary-soft, #f7f2fc);
	color: var(--gtc-primary, #8920f3);
	text-decoration: none;
}
body.page-id-61583 .gtcch-inner-nav a.is-active,
body.page-id-61583 .gtcch-inner-nav a[aria-current="page"],
body.page-id-61583 .gtcch-inner-nav a[aria-current="true"] {
	background: var(--gtc-primary-soft, #f7f2fc);
	color: var(--gtc-primary, #8920f3);
	box-shadow: inset 3px 0 0 var(--gtc-primary, #8920f3);
}
body.page-id-61583 .gtcch-inner-nav .gtcch-side-nav-sections {
	margin: 2px 0 6px 12px;
	padding-left: 10px;
	border-left: 2px solid var(--gtc-border, #e3ddec);
}
body.page-id-61583 .gtcch-inner-nav .gtcch-side-nav-sections a {
	padding: 7px 10px;
	font-size: 14px;
}
/* The injected nav contains a <nav class="gtcch-side-nav"> of its
   own: neutralise its card styling and sticky positioning (the
   outer .gtcch-inner-nav IS the card). The inner <details> is
   rendered open in the markup (v2.0.1), so its content is visible
   on desktop and its summary is hidden by the generic rules above;
   no display:none lives here — one used to, and it hid the whole
   inner nav on desktop. */
body.page-id-61583 .gtcch-inner-nav .gtcch-side-nav {
	position: static;
	background: transparent;
	border: 0;
	border-radius: 0;
	box-shadow: none;
	padding: 0;
}
@media (min-width: 1025px) {
	/* v2.1.1 defect 5: this used to be min-width: 769px, but at
	   768px the injected nav stayed a fixed ~320px left sidebar
	   (its 240px content padding + the Kadence sidebar) leaving
	   ~235px for the content — H1 clipped, reply Title field
	   clipped, author column unstacked, stat labels breaking
	   mid-word. The absolute left nav now starts at 1025px;
	   below that the nav is a static block above the board (see
	   the 769-1024px block below). Desktop >=1280px unchanged. */
	body.page-id-61583 #wpforo #wpforo-wrap .wpforo-content:has(> .gtcch-inner-nav) {
		position: relative;
		padding-left: 240px;
	}
	body.page-id-61583 #wpforo #wpforo-wrap .wpforo-content > .gtcch-inner-nav {
		position: absolute;
		left: 0;
		top: 0;
		width: 220px;
	}
}
/* v2.1.2 defect A (continued): the 240px left padding for the
   desktop absolute nav lives only in the min-width: 1025px block
   above — state the other side explicitly so the padding can
   never leak below 1025px: at <=1024px the board content carries
   NO left padding for the nav, so a sidebar layout cannot
   squeeze the topic-page content at tablet widths. Same
   high-specificity :has() selector as the desktop rule. */
@media (max-width: 1024px) {
	body.page-id-61583 #wpforo #wpforo-wrap .wpforo-content:has(> .gtcch-inner-nav) {
		padding-left: 0;
	}
}
/* v2.1.1 defect 5 (continued): at 769-1024px the injected nav is
   a static block ABOVE the board (as it already was at <=768px),
   so the topic page content gets the full width — full H1, full
   reply form, room for the author column and the stat labels.
   The "Games" toggle is visible here (same styling as the
   <=768px rules, scoped to the inner nav only) so the full
   11-12-link list does not push the content ~480px down. The
   board-home grid (.gtcch-layout) is untouched: at 769-1024px
   it keeps its 220px left column — only the INNER nav changes.
   v2.1.2: the outer-div rule below now uses the SAME
   high-specificity selector as the desktop absolute rule
   (body.page-id-61583 #wpforo #wpforo-wrap .wpforo-content > ...)
   instead of the bare body.page-id-61583 .gtcch-inner-nav, with
   left/top/float stated explicitly — so the static state wins
   any specificity contest at <=1024px and no sidebar layout can
   survive below 1025px. (Root-cause note: the v2.1.1 browser run
   reported the topic-page nav as a ~220px left sidebar at
   "768px", but the served 2.1.1 CSS was verified byte-identical
   to this file, the injection markup/parent is IDENTICAL on
   forum and topic pages (wpforo_content_start, direct child of
   .wpforo-content — wpForo 3.2.5 themes/2026/index.php:20), no
   competing rule exists in the inline Additional CSS or
   colors.css, and the same run's (a)-(d) conditions passing
   proves the <=768px media query WAS active — the only rule
   that produces a 220px sidebar is the min-width: 1025px
   absolute rule, so that observation was rendered at a >=1025px
   effective viewport, i.e. the Customizer device preview did
   not stick at tablet width for the topic page. The re-scoping
   here makes the <=1024px static behaviour unambiguous
   regardless, and the re-verify checklist now requires the
   board home to be confirmed single-column in the SAME session
   before the topic page is judged, so a desktop-width session
   cannot be mistaken for a 768px one again.) */
@media (min-width: 769px) and (max-width: 1024px) {
	body.page-id-61583 #wpforo #wpforo-wrap .wpforo-content > .gtcch-inner-nav {
		position: static;
		left: auto;
		top: auto;
		float: none;
		width: auto;
		padding: 0;
		background: transparent;
		border: 0;
		box-shadow: none;
		margin: 0 0 12px;
	}
	body.page-id-61583 .gtcch-inner-nav .gtcch-side-nav {
		position: static;
		padding: 0;
		background: transparent;
		border: 0;
		box-shadow: none;
	}
	body.page-id-61583 .gtcch-inner-nav .gtcch-side-nav-toggle {
		display: block;
		background: #fff;
		border: 1px solid var(--gtc-border, #e3ddec);
		border-radius: 10px;
		box-shadow: var(--gtc-shadow, 0 1px 2px rgba(17, 24, 39, .06));
	}
	body.page-id-61583 .gtcch-inner-nav .gtcch-side-nav-toggle > summary {
		display: flex;
		align-items: center;
		justify-content: space-between;
		gap: 8px;
		width: 100%;
		min-height: 44px;
		padding: 10px 14px;
		font-family: var(--gtc-font-head, 'Overpass', sans-serif);
		font-size: 15px;
		font-weight: 600;
		line-height: 1.4;
		color: var(--gtc-primary-darker, #290342);
		cursor: pointer;
		list-style: none;
	}
	body.page-id-61583 .gtcch-inner-nav .gtcch-side-nav-toggle > summary::-webkit-details-marker {
		display: none;
	}
	body.page-id-61583 .gtcch-inner-nav .gtcch-side-nav-toggle > summary::after {
		content: "\25BE";
		font-size: 13px;
		color: var(--gtc-text-muted, #6d6d6f);
		transition: transform 0.2s ease;
	}
	body.page-id-61583 .gtcch-inner-nav .gtcch-side-nav-toggle[open] > summary {
		padding-bottom: 10px;
		margin-bottom: 4px;
		border-bottom: 1px solid var(--gtc-border, #e3ddec);
	}
	body.page-id-61583 .gtcch-inner-nav .gtcch-side-nav-toggle[open] > summary::after {
		transform: rotate(180deg);
	}
	body.page-id-61583 .gtcch-inner-nav .gtcch-side-nav-toggle > .gtcch-side-nav-list {
		padding: 0 2px 4px;
	}
}

/* ---------- Responsive ---------- */
/* 2-column game grid at desktop and tablet; 1 column below 481px
   (base display:block). Carried over from the v1.0.1 fix. */
@media (min-width: 769px) {
	.gtcch-games-grid {
		display: grid;
		grid-template-columns: 1fr 1fr;
		gap: 12px;
	}
	.gtcch-game {
		margin-bottom: 0;
	}
}
@media (min-width: 481px) and (max-width: 768px) {
	.gtcch-games-grid {
		display: grid;
		grid-template-columns: 1fr 1fr;
		gap: 12px;
	}
	.gtcch-game {
		margin-bottom: 0;
	}
}
@media (max-width: 768px) {
	/* Theme type scale on small screens: H1 35px, H2 25px. */
	.gtcch-header h1,
	.gtcch-page-h1 {
		font-size: 35px;
	}
	.gtcch-feed > h2,
	.gtcch-games > h2 {
		font-size: 25px;
	}
	/* Board home becomes a single column; the side nav collapses
	   to its <details> toggle at the top of the main column.
	   B's markup: <nav class="gtcch-side-nav"> is the (now
	   unstyled) wrapper; <details class="gtcch-side-nav-toggle">
	   is the card and its <summary> is the toggle button. */
	.gtcch-layout {
		grid-template-columns: 1fr;
		gap: 12px;
	}
	.gtcch-side-nav {
		position: static;
		padding: 0;
		background: transparent;
		border: 0;
		box-shadow: none;
	}
	.gtcch-side-nav .gtcch-side-nav-toggle {
		display: block;
		background: #fff;
		border: 1px solid var(--gtc-border, #e3ddec);
		border-radius: 10px;
		box-shadow: var(--gtc-shadow, 0 1px 2px rgba(17, 24, 39, .06));
	}
	.gtcch-side-nav .gtcch-side-nav-toggle > summary {
		display: flex;
		align-items: center;
		justify-content: space-between;
		gap: 8px;
		width: 100%;
		min-height: 44px;
		padding: 10px 14px;
		font-family: var(--gtc-font-head, 'Overpass', sans-serif);
		font-size: 15px;
		font-weight: 600;
		line-height: 1.4;
		color: var(--gtc-primary-darker, #290342);
		cursor: pointer;
		list-style: none;
	}
	.gtcch-side-nav .gtcch-side-nav-toggle > summary::-webkit-details-marker {
		display: none;
	}
	.gtcch-side-nav .gtcch-side-nav-toggle > summary::after {
		content: "\25BE";
		font-size: 13px;
		color: var(--gtc-text-muted, #6d6d6f);
		transition: transform 0.2s ease;
	}
	.gtcch-side-nav .gtcch-side-nav-toggle[open] > summary {
		padding-bottom: 10px;
		margin-bottom: 4px;
		border-bottom: 1px solid var(--gtc-border, #e3ddec);
	}
	.gtcch-side-nav .gtcch-side-nav-toggle[open] > summary::after {
		transform: rotate(180deg);
	}
	.gtcch-side-nav .gtcch-side-nav-toggle > .gtcch-side-nav-list {
		padding: 0 2px 4px;
	}
	/* Inner-page nav: a static block above the board (the div is
	   NOT a <details>, so there is no [open] state on it); the
	   collapse comes from the <details> inside it, styled by the
	   generic mobile rules above. No left padding on the board
	   content at this width. v2.1.2: same high-specificity
	   selector as the desktop absolute rule (see the 769-1024px
	   block) so the static state wins any specificity contest. */
	body.page-id-61583 #wpforo #wpforo-wrap .wpforo-content > .gtcch-inner-nav {
		position: static;
		left: auto;
		top: auto;
		float: none;
		width: auto;
		padding: 0;
		background: transparent;
		border: 0;
		box-shadow: none;
		margin: 0 0 12px;
	}
	.gtcch-header-row {
		flex-direction: column;
		align-items: stretch;
	}
	.gtcch-search {
		/* v2.0.2 defect 2: the base rule is flex: 1 1 280px, and in
		   this column-direction row that 280px basis became the
		   form's HEIGHT (~280px); the button, with no explicit
		   height, stretched to fill it (flex align-items: stretch)
		   while the input kept its 44px height. flex: 0 0 auto
		   kills the vertical basis so the form is content-height.
		   v2.0.3 defect 2: the height was fixed, but at 320px the
		   button was STILL cut off at the right edge (only ~18px
		   visible). Root cause: the form is a flex item of this
		   column row, and its automatic minimum (min-width: auto)
		   is its min-content — the input's default size (~180-240px,
		   size=20 with Chrome's search decoration) + 8px gap +
		   button (~111px), about 300px — wider than the ~216px
		   header content box at 320px, so the form overflowed the
		   card to the right and the button, the LAST child, slid
		   past the viewport edge. The v2.0.2 fix only put
		   min-width: 0 on the INPUT; the FORM itself still could
		   not shrink below its min-content. min-width: 0 on the
		   FORM is the actual fix: it lets the form shrink to the
		   stretched width, the input (min-width: 0 already)
		   absorbs all narrowing, and flex-shrink: 0 +
		   align-self: center keep the button whole. width and
		   max-width 100% are belt-and-braces so the form never
		   exceeds the header content box. */
		flex: 0 0 auto;
		align-items: center;
		width: 100%;
		max-width: 100%;
		min-width: 0;
	}
	.gtcch-search .gtcch-btn {
		align-self: center;
		flex: 0 0 auto;
	}
	.gtcch-start {
		/* v2.0.3: min-width: 0 so the chooser can never force the
		   header row (and the page) wider than the viewport at
		   320px; the summary button itself is trimmed at <=480px
		   below so it still fits inside the card. */
		align-self: flex-start;
		min-width: 0;
	}
	.gtcch-start-panel {
		min-width: 260px;
	}
	.gtcch-card-avatar {
		flex-basis: 32px;
	}
	.gtcch-card-avatar img.avatar {
		width: 32px;
		height: 32px;
	}
	.gtcch-game-head .gtcch-btn-small {
		margin-left: 0;
	}
	.gtcch-card-image,
	.gtcch-card-image img {
		max-height: 160px;
	}
}
@media (max-width: 480px) {
	.gtcch-header {
		padding: 14px 16px;
	}
	/* v2.0.3 defect 2: "Start a Discussion" at full button padding
	   is ~216px wide — as wide as the whole header content box at
	   320px (320 - Kadence/article padding - 32px header padding).
	   Trim the padding (and a touch of type size) so the button
	   fits inside the card with room to spare. */
	.gtcch-start-summary {
		padding: 12px 18px;
		font-size: 15px;
	}
	/* v2.1.0 (R5/R6): the chooser panel's min-width (260px at
	   <=768px) is wider than its card at 320px (card ~248px), so
	   the panel sticks out past the card edge. Cap the min-width
	   at the card width (100vw - 88px = 232px at 320px).
	   NOTE v2.1.1 defect 3: this cap did NOT fix the clipping —
	   the cause was the panel's POSITIONING (right-aligned to a
	   ~188px button), not its width. The cap is kept (harmless)
	   but the real fix is the re-anchoring block after this one,
	   which overrides min-width to 0 at <=768px. */
	.gtcch-start-panel {
		min-width: min(260px, calc(100vw - 88px));
	}
	.gtcch-card {
		padding: 12px 14px;
	}
	.gtcch-card-title {
		font-size: 17px;
	}
}

/* v2.1.1 defect 3: the chooser panel was STILL clipped at the left
   viewport edge at 320px even after the v2.1.0 min-width cap above
   (that comment's claim is superseded — the cap did not fix it).
   The cause is POSITIONING, not width: the panel is
   `position: absolute; right: 0` relative to `.gtcch-start`,
   which at <=768px is a left-aligned flex item (~188-216px wide)
   in the column header row, while the panel's preferred width is
   ~280-295px (step-1 heading max-content + 28px padding) — so
   `right: 0` pushes its left edge ~40px past the viewport's left
   side at 320px. (The empty-state instance was centred on its
   inline-block button, so it stuck out past its card edges
   instead.) Fix: re-anchor the panel to its CARD, not the button.
   The header and the empty state become the positioning context
   (position: relative), the button wrapper goes static, and the
   panel stretches left:0/right:0 with max-width:320px — with
   left+right over-constrained, the used width is min(320px, card
   padding-box), left-aligned at the card edge, directly below the
   summary button (top:auto = its static position). Geometry at
   320px: header padding-box ~284px, so the panel is 284px wide,
   flush inside its card; at 768px it is 320px wide, left-aligned.
   The panel still overlays the content below while open (normal
   dropdown behaviour, same as desktop); the acceptance criterion
   is horizontal containment + no clipping. This block sits AFTER
   the <=480px block so its min-width:0 wins over the cap above
   at equal specificity. */
@media (max-width: 768px) {
	.gtcch-header,
	.gtcch-empty {
		position: relative;
	}
	.gtcch-start,
	.gtcch-empty .gtcch-start {
		position: static;
	}
	.gtcch-start-panel,
	.gtcch-empty .gtcch-start-panel {
		left: 0;
		right: 0;
		top: auto;
		transform: none;
		min-width: 0;
		max-width: 320px;
		width: auto;
	}
}

/* v2.1.1 defect 4: on a section page at 320px the topic-list
   title collapsed to ~1 character per line — the flex row's
   fixed columns (icon 50px + stats ~110px + toggle ~32px) left
   the title block almost nothing in a ~248px row, and the row
   does not wrap. At <=480px let the row wrap and give the title
   block a full line when it needs one: flex-basis 160px (larger
   than the longest word, so the title never breaks mid-word on
   its own line) with flex-grow, so it shares line 1 with the
   icon when there is room and wraps to its own full-width line
   when there is not. Covers both layout 1 (Extended, live) and
   layout 2 rows for robustness; layout 2's 60% width on the
   info block is overridden. Desktop topic lists untouched. */
@media (max-width: 480px) {
	body.page-id-61583 #wpforo #wpforo-wrap .wpfl-1 .wpforo-topic,
	body.page-id-61583 #wpforo #wpforo-wrap .wpfl-2 .wpforo-topic {
		flex-wrap: wrap;
	}
	body.page-id-61583 #wpforo #wpforo-wrap .wpfl-1 .wpforo-topic-info,
	body.page-id-61583 #wpforo #wpforo-wrap .wpfl-2 .wpforo-topic-info {
		flex: 1 1 160px;
		min-width: 0;
		width: auto;
	}
	body.page-id-61583 #wpforo #wpforo-wrap .wpfl-1 .wpforo-topic-icon,
	body.page-id-61583 #wpforo #wpforo-wrap .wpfl-2 .wpforo-topic-icon,
	body.page-id-61583 #wpforo #wpforo-wrap .wpfl-2 .wpforo-topic-avatar,
	body.page-id-61583 #wpforo #wpforo-wrap .wpfl-1 .wpforo-topic-stat-combined,
	body.page-id-61583 #wpforo #wpforo-wrap .wpfl-2 .wpforo-topic-stat-posts,
	body.page-id-61583 #wpforo #wpforo-wrap .wpfl-2 .wpforo-topic-stat-views,
	body.page-id-61583 #wpforo #wpforo-wrap .wpfl-2 .wpforo-topic-stat-lastpost,
	body.page-id-61583 #wpforo #wpforo-wrap .wpfl-1 .wpforo-topic-toggle,
	body.page-id-61583 #wpforo #wpforo-wrap .wpfl-2 .wpforo-topic-toggle {
		flex: 0 0 auto;
	}
	body.page-id-61583 #wpforo #wpforo-wrap .wpforo-topic-title a {
		overflow-wrap: break-word;
	}
}

/* v2.1.1 defect 5 (continued): with the nav static below 1025px
   the topic page content is full-width again, but the author
   column needs its own rule at <=768px: it must STACK above the
   post body at 768px — the theme only stacks it at <=620px, so
   extend the stacking to 768px (float:none, full width, body
   margin removed). At 769-1024px the 160px floated author column
   stays (the theme's tablet layout, now with room). v2.1.2
   defect B: the stat-label rules that used to live in this block
   moved to the unscoped base rule below (they must never break
   mid-word at ANY width, desktop included). */
@media (max-width: 768px) {
	body.page-id-61583 #wpforo #wpforo-wrap .wpfl-1 .wpforo-post .wpf-left,
	body.page-id-61583 #wpforo #wpforo-wrap .wpfl-2 .wpforo-post .wpf-left {
		float: none;
		width: 100%;
	}
	body.page-id-61583 #wpforo #wpforo-wrap .wpfl-1 .wpforo-post .wpf-right,
	body.page-id-61583 #wpforo #wpforo-wrap .wpfl-2 .wpforo-post .wpf-right {
		float: none;
		width: 100%;
		margin-left: 0;
	}
}

/* v2.1.2 defect B: stat labels ("Posts", "Users", "Reactions",
   "Views") must never break mid-word at ANY width — at desktop
   they wrapped ("Pos/ts", "Use/rs", "Reac/tions", "View/s") in
   the narrow meta column, because the nowrap/flex-wrap treatment
   was <=768px-only in v2.1.1. It is now an UNSCOPED base rule:
   the stat boxes wrap to a new line instead, with labels kept
   whole. Scoped to the topic-header stats only (.wpf-post-stat
   exists only on topic pages, rendered by wpforo_topic_head());
   the meta column's width and the desktop topic layout are
   untouched. */
body.page-id-61583 #wpforo #wpforo-wrap .wpf-post-stat {
	flex-wrap: wrap;
}
body.page-id-61583 #wpforo #wpforo-wrap .wpf-post-stat .wpf-tlabel {
	white-space: nowrap;
}

/* ---------- Accessibility + motion ---------- */
@media (prefers-reduced-motion: reduce) {
	.gtcch-home *,
	.gtcch-home *::before,
	.gtcch-home *::after {
		transition: none !important;
		transform: none !important;
		animation: none !important;
	}
}

/* ==========================================================================
   v2.2.0 — Phase 3: inner-page redesign + header auth bar
   --------------------------------------------------------------------------
   A. Section topic lists render the plugin's own card template
      (templates/topic-list-cards.php, via the wpforo_wpftpl filter),
      so they use the exact .gtcch-card classes — no extra card rules
      needed here, only the wrapper + the last-post foot link.
   B. Topic pages: the topic head, each post/reply, the reply form
      and the guest please-login prompt become white cards in the
      same language.
   C. Forum Information block: hidden (scoped display:none).
   D. Header auth bar: guest Login/Register + logged-in avatar and
      account dropdown, on the board-home header and on every inner
      board page (injected .gtcch-auth-bar-wrap).
   ========================================================================== */

/* ---------- Header top row (board home) ----------
   Titles left, auth bar right; wraps on narrow screens (the auth
   bar drops below the titles, still inside the header card). */
.gtcch-header-top {
	display: flex;
	align-items: flex-start;
	justify-content: space-between;
	gap: 12px;
	flex-wrap: wrap;
}
.gtcch-header-titles {
	flex: 1 1 auto;
	min-width: 0;
}

/* ---------- Header auth bar ----------
   One renderer (gtcch_auth_bar_html()), two call sites: inside the
   board-home header card, and inside .gtcch-auth-bar-wrap on inner
   pages. The bar is the positioning context for the account menu:
   the menu is anchored to the BAR's right edge (not the summary's),
   so it lands at the header/content right edge on desktop AND on
   mobile, where the bar stretches full-width in the column header.
   Guest buttons reuse .gtcch-btn (gradient Register) and
   .gtcch-btn-secondary (outlined Login) — the layout here is only
   the row + gap. */
.gtcch-auth-bar {
	position: relative;
	display: flex;
	align-items: center;
	gap: 8px;
	flex: 0 0 auto;
}
/* Inner-page button text colours: the base .gtcch-btn colour rule is
   (0,1,0), so the theme's .entry-content a rule (0,1,1) would win
   for the gradient button's white label on inner pages (the bar is
   NOT inside .gtcch-home there, so the v1.0.1 (0,3,2) home rule does
   not apply). This (2,1,2) rule is the inner-page equivalent. */
body.page-id-61583 #wpforo #wpforo-wrap a.gtcch-btn,
body.page-id-61583 #wpforo #wpforo-wrap a.gtcch-btn:hover,
body.page-id-61583 #wpforo #wpforo-wrap a.gtcch-btn:focus-visible {
	color: #fff;
}
body.page-id-61583 #wpforo #wpforo-wrap a.gtcch-btn-secondary,
body.page-id-61583 #wpforo #wpforo-wrap a.gtcch-btn-secondary:hover,
body.page-id-61583 #wpforo #wpforo-wrap a.gtcch-btn-secondary:focus-visible {
	color: var(--gtc-primary, #8920f3);
}
body.page-id-61583 #wpforo #wpforo-wrap a.gtcch-btn-secondary:hover,
body.page-id-61583 #wpforo #wpforo-wrap a.gtcch-btn-secondary:focus-visible {
	color: var(--gtc-primary-dark, #6022a0);
}
/* Inner-page injected bar: a slim right-aligned row above the board
   content (first child of .wpforo-content, priority 8 — before the
   H1 at 9 and the inner nav at 10). At >=1025px it spans the padded
   content box, so its right edge is the board's right edge; the
   220px absolute nav sits at the left and never overlaps it (the
   buttons are ~200px wide at the right). */
.gtcch-auth-bar-wrap {
	display: flex;
	justify-content: flex-end;
	margin: 0 0 12px;
}

/* ---------- Account dropdown (logged in) ----------
   Pure <details>, no JS: the <summary> is the toggle (avatar +
   name + caret), the menu is absolutely positioned below the bar.
   The default details marker is hidden; the caret rotates when
   open. Known <details> limitation, accepted: the menu does NOT
   auto-close on an outside click — the user closes it by clicking
   the summary again. */
.gtcch-account {
	position: static;
}
.gtcch-account-summary {
	display: flex;
	align-items: center;
	gap: 8px;
	min-height: 44px;
	padding: 2px 10px 2px 2px;
	font-family: var(--gtc-font-head, 'Overpass', sans-serif);
	font-size: 15px;
	font-weight: 600;
	line-height: 1.4;
	color: var(--gtc-text, #3b383e);
	background: #fff;
	border: 1px solid var(--gtc-border, #e3ddec);
	border-radius: 100px;
	cursor: pointer;
	list-style: none;
	white-space: nowrap;
}
.gtcch-account-summary::-webkit-details-marker {
	display: none;
}
.gtcch-account-summary:hover {
	border-color: var(--gtc-primary, #8920f3);
}
.gtcch-account-summary:focus-visible {
	outline: 3px solid var(--gtc-primary-softer, #e3ddec);
	outline-offset: 2px;
}
.gtcch-account[open] > .gtcch-account-summary {
	border-color: var(--gtc-primary, #8920f3);
}
.gtcch-account-avatar {
	display: flex;
	flex: 0 0 auto;
}
.gtcch-account-avatar img.avatar {
	width: 40px;
	height: 40px;
	border-radius: 50%;
	object-fit: cover;
	display: block;
}
.gtcch-account-name {
	min-width: 0;
	overflow: hidden;
	text-overflow: ellipsis;
}
.gtcch-account-caret {
	display: inline-flex;
	flex: 0 0 auto;
	transition: transform 0.2s ease;
}
.gtcch-account-caret::after {
	content: "\25BE";
	font-size: 12px;
	color: var(--gtc-text-muted, #6d6d6f);
}
.gtcch-account[open] .gtcch-account-caret {
	transform: rotate(180deg);
}
.gtcch-account-menu {
	position: absolute;
	top: calc(100% + 6px);
	right: 0;
	min-width: 200px;
	max-width: 90vw;
	background: #fff;
	border: 1px solid var(--gtc-border, #e3ddec);
	border-radius: 10px;
	box-shadow: 0 8px 24px rgba(17, 24, 39, .12);
	padding: 6px;
	z-index: 60;
}
/* Menu links: scoped to body.page-id-61583 (0,1,2) so the theme's
   .entry-content a rule (0,1,1) can never recolour them, on home
   or inner pages. */
body.page-id-61583 .gtcch-account-menu a {
	display: flex;
	align-items: center;
	padding: 9px 12px;
	font-size: 15px;
	font-weight: 600;
	line-height: 1.4;
	color: var(--gtc-text, #3b383e);
	border-radius: 8px;
	text-decoration: none;
	white-space: nowrap;
}
body.page-id-61583 .gtcch-account-menu a:hover {
	background: var(--gtc-primary-soft, #f7f2fc);
	color: var(--gtc-primary, #8920f3);
	text-decoration: none;
}

/* ---------- Section / topic header card ----------
   The .wpf-head-bar is wpForo's own header on category, section and
   topic pages (H1 + description + Start a Discussion button, or H1
   + pagination on topic pages). Same white card as the board-home
   header. The inline border-left: 3px solid {forum colour} survives
   (inline styles beat this rule's border shorthand) and stays as the
   per-forum colour accent. */
body.page-id-61583 #wpforo #wpforo-wrap .wpf-head-bar {
	background: #fff;
	border: 1px solid var(--gtc-border, #e3ddec);
	border-radius: 10px;
	box-shadow: var(--gtc-shadow, 0 1px 2px rgba(17, 24, 39, .06));
	padding: 14px 16px;
	margin: 0 0 12px;
}
body.page-id-61583 #wpforo #wpforo-wrap #wpforo-description {
	font-size: 15px;
	line-height: 1.5;
	color: var(--gtc-text-muted, #6d6d6f);
	margin: 4px 0 0;
}
/* The Add Topic button in the head bar (a <button class="wpf-button
   add_wpftopic"> for members, an <a class="wpf-button"> for guests)
   becomes the gradient pill. Scoped to .wpf-head-bar ONLY — .wpf-button
   is wpForo's generic button class (reply submit, etc.) and must not
   be restyled globally. */
body.page-id-61583 #wpforo #wpforo-wrap .wpf-head-bar .wpf-button {
	display: inline-flex;
	align-items: center;
	justify-content: center;
	gap: 6px;
	min-height: 44px;
	padding: 13px 28px;
	font-family: var(--gtc-font-head, 'Overpass', sans-serif);
	font-size: 16px;
	font-weight: 600;
	line-height: 1.2;
	text-transform: capitalize;
	color: #fff;
	background: linear-gradient(43deg, #8920f3 0%, #ff7c58 100%);
	background-color: var(--gtc-primary, #8920f3);
	border: 0;
	border-radius: 100px;
	cursor: pointer;
	text-decoration: none;
	white-space: nowrap;
	transition: var(--gtc-transition, all 0.2s ease);
}
body.page-id-61583 #wpforo #wpforo-wrap .wpf-head-bar .wpf-button:hover,
body.page-id-61583 #wpforo #wpforo-wrap .wpf-head-bar .wpf-button:focus-visible {
	background: linear-gradient(135deg, #8920f3 0%, #ff7c58 100%);
	background-color: var(--gtc-primary, #8920f3);
	box-shadow: var(--gtc-shadow-btn, 0 15px 25px -7px rgba(0, 0, 0, .25));
	color: #fff;
	text-decoration: none;
	transform: translateY(-1px);
}

/* ---------- Section topic-list cards ----------
   The override renders .gtcch-card markup, so the cards need no new
   rules — only the stock .topic-wrap margins are zeroed (the card
   itself carries the 10px bottom margin) and the last-post foot link
   is muted like the rest of the foot. The v2.1.1 defect-4
   .wpforo-topic flex-wrap rules above stay as a fallback: they
   simply match nothing while the override is active, and they cover
   a layout-2/3/5 section if one ever appears. */
body.page-id-61583 #wpforo #wpforo-wrap .gtcch-topic-list .gtcch-topic-wrap {
	margin: 0;
}
body.page-id-61583 #wpforo #wpforo-wrap .gtcch-card-foot a {
	color: var(--gtc-text-muted, #6d6d6f);
	text-decoration: none;
}
body.page-id-61583 #wpforo #wpforo-wrap .gtcch-card-foot a:hover {
	color: var(--gtc-primary, #8920f3);
	text-decoration: none;
}

/* ---------- Topic page cards ----------
   Topic head (.wpforo-topic-head-wrap, rendered by
   wpforo_topic_head()): white card; the info row wraps (section
   chip + game pill + Last Post line); the stat boxes become soft
   pills. The section label (.wpf-post-info-forum, a plain span)
   becomes a chip matching .gtcch-card-section; the game pill
   injected by gtcch_topic_head_game_pill() reuses .gtcch-card-game
   and needs no rule here. */
body.page-id-61583 #wpforo #wpforo-wrap .wpforo-topic-head-wrap {
	background: #fff;
	border: 1px solid var(--gtc-border, #e3ddec);
	border-radius: 10px;
	box-shadow: var(--gtc-shadow, 0 1px 2px rgba(17, 24, 39, .06));
	padding: 14px 16px;
	margin: 0 0 12px;
}
body.page-id-61583 #wpforo #wpforo-wrap .wpf-post-info {
	display: flex;
	flex-wrap: wrap;
	align-items: center;
	gap: 6px 12px;
}
body.page-id-61583 #wpforo #wpforo-wrap .wpf-post-info-forum {
	display: inline-flex;
	align-items: center;
	gap: 6px;
	padding: 2px 8px;
	font-size: 12px;
	font-weight: 700;
	line-height: 1.5;
	color: var(--gtc-text-soft, #646366);
	background: #fff;
	border: 1px solid var(--gtc-border, #e3ddec);
	border-radius: 100px;
	white-space: nowrap;
}
body.page-id-61583 #wpforo #wpforo-wrap .wpf-post-stat .wpf-post-stat-box {
	background: var(--gtc-primary-soft, #f7f2fc);
	border: 1px solid var(--gtc-border, #e3ddec);
	border-radius: 8px;
	padding: 6px 10px;
}
/* Each post/reply (.wpforo-post: floated author column + body):
   white card, same tokens. The author column keeps the theme's
   float layout at desktop and the <=768px stacking rule above. */
body.page-id-61583 #wpforo #wpforo-wrap .wpforo-post {
	background: #fff;
	border: 1px solid var(--gtc-border, #e3ddec);
	border-radius: 10px;
	box-shadow: var(--gtc-shadow, 0 1px 2px rgba(17, 24, 39, .06));
	padding: 14px 16px;
	margin: 0 0 12px;
}
body.page-id-61583 #wpforo #wpforo-wrap .wpforo-post-content img {
	max-width: 100%;
	height: auto;
	border-radius: 8px;
}
/* Reply form: white card, theme-token title, gradient submit.
   Scoped to the form wrapper only — the editor internals
   (TinyMCE) are untouched. */
body.page-id-61583 #wpforo #wpforo-wrap .wpf-form-wrapper {
	background: #fff;
	border: 1px solid var(--gtc-border, #e3ddec);
	border-radius: 10px;
	box-shadow: var(--gtc-shadow, 0 1px 2px rgba(17, 24, 39, .06));
	padding: 14px 16px;
	margin: 0 0 12px;
}
body.page-id-61583 #wpforo #wpforo-wrap .wpf-reply-form-title {
	font-family: var(--gtc-font-head, 'Overpass', sans-serif);
	font-size: 18px;
	font-weight: 700;
	line-height: 1.3;
	color: var(--gtc-primary-darker, #290342);
	margin: 0 0 10px;
}
body.page-id-61583 #wpforo #wpforo-wrap .wpf-form-wrapper .wpf-buttons-wrap input.wpf-button[type="submit"] {
	min-height: 44px;
	padding: 13px 28px;
	font-family: var(--gtc-font-head, 'Overpass', sans-serif);
	font-size: 16px;
	font-weight: 600;
	line-height: 1.2;
	text-transform: capitalize;
	color: #fff;
	background: linear-gradient(43deg, #8920f3 0%, #ff7c58 100%);
	background-color: var(--gtc-primary, #8920f3);
	border: 0;
	border-radius: 100px;
	cursor: pointer;
	text-decoration: none;
	white-space: nowrap;
	transition: var(--gtc-transition, all 0.2s ease);
}
body.page-id-61583 #wpforo #wpforo-wrap .wpf-form-wrapper .wpf-buttons-wrap input.wpf-button[type="submit"]:hover,
body.page-id-61583 #wpforo #wpforo-wrap .wpf-form-wrapper .wpf-buttons-wrap input.wpf-button[type="submit"]:focus-visible {
	background: linear-gradient(135deg, #8920f3 0%, #ff7c58 100%);
	background-color: var(--gtc-primary, #8920f3);
	box-shadow: var(--gtc-shadow-btn, 0 15px 25px -7px rgba(0, 0, 0, .25));
	color: #fff;
	transform: translateY(-1px);
}
/* Guest reply prompt: white card, centred; its Login/Register
   links (which carry redirect_to to the topic) become small
   outlined pills. */
body.page-id-61583 #wpforo #wpforo-wrap .wpf-please-login {
	background: #fff;
	border: 1px solid var(--gtc-border, #e3ddec);
	border-radius: 10px;
	box-shadow: var(--gtc-shadow, 0 1px 2px rgba(17, 24, 39, .06));
	padding: 14px 16px;
	margin: 0 0 12px;
	font-size: 15px;
	line-height: 1.5;
	color: var(--gtc-text-muted, #6d6d6f);
	text-align: center;
}
body.page-id-61583 #wpforo #wpforo-wrap .wpf-please-login a {
	display: inline-block;
	padding: 6px 14px;
	font-size: 14px;
	font-weight: 600;
	line-height: 1.4;
	color: var(--gtc-primary, #8920f3);
	background: #fff;
	border: 2px solid var(--gtc-primary, #8920f3);
	border-radius: 100px;
	text-decoration: none;
	white-space: nowrap;
}
body.page-id-61583 #wpforo #wpforo-wrap .wpf-please-login a:hover {
	background: var(--gtc-primary-soft, #f7f2fc);
	color: var(--gtc-primary-dark, #6022a0);
	text-decoration: none;
}

/* ---------- Forum Information block: removed ----------
   The block is themes/2026/footer.php: #wpforo-footer >
   #wpforo-stat-header ("Forum Information" title + Mark-all-read /
   Recent / Unread / Tags buttons) + #wpforo-stat-body (Forums /
   Topics / Posts / Online / Members boxes, newest member, latest
   post, icon legends). It is gated by the wpForo
   `components.footer` setting and no hook filters it, so scoped
   display:none is the removal mechanism — no wpForo file is edited.
   The wpForo copyright line (a direct child of #wpforo-footer,
   outside both hidden divs) stays visible. Side effect, accepted:
   the footer "Mark all as read" link goes with the header (it
   exists nowhere else). The per-game counts on the homepage cards
   and the feed count lines are untouched. */
body.page-id-61583 #wpforo #wpforo-wrap #wpforo-stat-header,
body.page-id-61583 #wpforo #wpforo-wrap #wpforo-stat-body {
	display: none;
}

/* ---------- v2.2.0 responsive ---------- */
@media (max-width: 768px) {
	/* Header top row stacks: titles full-width, auth bar below them,
	   left-aligned, still inside the header card. */
	.gtcch-header-top {
		flex-direction: column;
		align-items: stretch;
	}
	.gtcch-auth-bar {
		justify-content: flex-start;
	}
	/* Compact auth buttons: smaller padding/font, 40px min-height —
	   both still visible in the header, never in the menu. */
	.gtcch-auth-bar .gtcch-btn {
		min-height: 40px;
		padding: 8px 14px;
		font-size: 14px;
	}
	.gtcch-account-summary {
		min-height: 40px;
		padding: 2px 8px 2px 2px;
		font-size: 14px;
	}
	.gtcch-account-avatar img.avatar {
		width: 32px;
		height: 32px;
	}
	/* Tighter card padding on small screens. */
	body.page-id-61583 #wpforo #wpforo-wrap .wpforo-topic-head-wrap,
	body.page-id-61583 #wpforo #wpforo-wrap .wpforo-post,
	body.page-id-61583 #wpforo #wpforo-wrap .wpf-form-wrapper,
	body.page-id-61583 #wpforo #wpforo-wrap .wpf-head-bar,
	body.page-id-61583 #wpforo #wpforo-wrap .wpf-please-login {
		padding: 12px 14px;
	}
	/* Head-bar Add Topic button + reply submit: same compact sizing
	   as the auth buttons, so they fit at 320px. */
	body.page-id-61583 #wpforo #wpforo-wrap .wpf-head-bar .wpf-button,
	body.page-id-61583 #wpforo #wpforo-wrap .wpf-form-wrapper .wpf-buttons-wrap input.wpf-button[type="submit"] {
		min-height: 40px;
		padding: 8px 14px;
		font-size: 14px;
	}
}

/* ==========================================================================
   v2.2.1 — FIX RELEASE (8 fixes for the v2.2.0 verification run,
   2026-11-18 10:19-10:39 EST; root causes verified against wpForo
   3.2.5 source + the live served HTML/CSS — full notes in the
   plugin header comment and the readme changelog). Everything
   below is appended, never edited in place, so the v2.2.0 rules
   above stay byte-identical and the diff stays reviewable.
   ========================================================================== */

/* --- Fix 1: board-home / ?game= auth bar TOP-RIGHT of the header card ---
   Root cause: .gtcch-header-top is display:flex with
   flex-wrap:wrap, and the H1 (40px, ~360px) + the auth bar
   (~240px) do not fit the ~490px main column, so the bar wrapped
   to a second row — where justify-content:space-between with a
   single item puts it at flex-start (LEFT-aligned beneath the
   subtitle). Fix: no wrapping at >=769px + margin-left:auto on
   the bar, so the bar stays on the title row at the right and
   the H1 wraps to two lines instead. The <=768px column layout
   (flex-direction:column) is deliberately untouched: with the
   direction column, nowrap only stops wrapping of the vertical
   stack, so the rule is scoped to min-width:769px anyway. */
@media (min-width: 769px) {
	.gtcch-header-top {
		flex-wrap: nowrap;
	}
	.gtcch-header-top .gtcch-auth-bar {
		margin-left: auto;
	}
}

/* --- Fix 8: feed-card titles render as written (no title-case) ---
   Root cause: Kadence sets text-transform:capitalize on ALL h3
   elements, and wpForo's own style.css:308 resets h3 to
   text-transform:none inside #wpforo-wrap — so the board-home
   card (outside #wpforo-wrap) title-cased while the identical
   section card did not. (0,1,0) beats Kadence's h3 (0,0,1).
   H1s keep the theme's capitalize (unchanged). */
.gtcch-card-title {
	text-transform: none;
}

/* --- Fix 2: section header — Start A Discussion cannot overlap the description ---
   Root cause: wpForo's own head bar is floats —
   .wpf-head-bar-left float:left width:69% +
   .wpf-head-bar-right float:right width:30%
   (themes/2026/style.css:399-401) — and the gradient pill
   (~186px, white-space:nowrap) is wider than the 30% column, so
   it overflows leftward over the description. Fix: the section
   head bar becomes flex with wrapping. The .wpft-topic class
   lands on both <body> and #wpforo-wrap via wpforo_wrap_class /
   body_class (includes/functions-template.php:368-373), so the
   body scope is exact for section pages only — category, topic,
   recent and auth pages are untouched. Left column flex:1 1 260px
   min-width:0 (description wraps inside it), right column
   flex:0 0 auto padding:0 (button keeps its size, never shrinks);
   with flex-wrap the button drops to its own line if it does not
   fit beside the description — it can never cover the text. */
body.wpft-topic #wpforo #wpforo-wrap .wpf-head-bar {
	display: flex;
	flex-wrap: wrap;
	align-items: flex-start;
	gap: 8px 12px;
}
body.wpft-topic #wpforo #wpforo-wrap .wpf-head-bar-left {
	float: none;
	width: auto;
	flex: 1 1 260px;
	min-width: 0;
}
body.wpft-topic #wpforo #wpforo-wrap .wpf-head-bar-right {
	float: none;
	width: auto;
	flex: 0 0 auto;
	padding: 0;
}

/* --- Fix 3: topic page cannot overflow at <=1024px (belt-and-braces) ---
   Finding: the <=768px author-stacking rule and the unscoped
   .wpf-post-stat flex-wrap rule ALREADY exist in the v2.2.0
   block (high specificity, verified), and the served 2.2.0.css
   is byte-identical to the shipped file — so a "768px author
   column does not stack" observation cannot be produced by the
   shipped CSS at a true 768px viewport; it has the same
   signature as the v2.1.2 Customizer-preview artifact (the
   preview iframe not holding its width for inner pages). Added
   anyway, so the page provably cannot overflow: wpForo renders
   .wpf-post-head-top and .wpf-post-head-bottom as no-wrap flex
   rows (themes/2026/style.css:649/661), so both get
   flex-wrap:wrap here; .wpf-post-info flex:1 1 auto min-width:0
   (title shrinks, wraps inside it) and .wpf-post-stat
   flex:0 1 auto min-width:0 (stat pills wrap/shrink instead of
   pushing the row past the viewport). The author-stacking rule
   at <=768px is NOT duplicated — it already exists above. */
@media (max-width: 1024px) {
	body.page-id-61583 #wpforo #wpforo-wrap .wpforo-post-head .wpf-post-head-top {
		flex-wrap: wrap;
	}
	body.page-id-61583 #wpforo #wpforo-wrap .wpforo-post-head .wpf-post-head-top .wpf-post-info {
		flex: 1 1 auto;
		min-width: 0;
	}
	body.page-id-61583 #wpforo #wpforo-wrap .wpforo-post-head .wpf-post-head-top .wpf-post-stat {
		flex: 0 1 auto;
		min-width: 0;
	}
	body.page-id-61583 #wpforo #wpforo-wrap .wpforo-post-head .wpf-post-head-bottom {
		flex-wrap: wrap;
	}
}

/* --- Fix 4: account pill on inner pages — beat wpForo's summary reset ---
   Verified cascade defect: wpForo's reset
   (themes/2026/style.css:292) sets margin/padding/border:0 on
   `summary` inside #wpforo-wrap at specificity (2,0,1), which
   beats the plugin's (0,1,0) .gtcch-account-summary
   padding/border rules — so on inner pages the account pill
   loses its padding and border and renders tighter than on the
   board home. These re-scoped rules are (2,3,1)+ and restore
   the intended geometry on inner pages; the details gets
   min-width:max-content so it can never shrink below its
   content and clip the name under the avatar. The exact pixel
   mechanism of the observed overlap could not be reproduced
   from files alone — the browser re-verify (checklist Step 4)
   is the decisive check. */
body.page-id-61583 #wpforo #wpforo-wrap .gtcch-auth-bar .gtcch-account {
	min-width: max-content;
}
body.page-id-61583 #wpforo #wpforo-wrap .gtcch-auth-bar .gtcch-account-summary {
	display: flex;
	align-items: center;
	gap: 8px;
	border: 1px solid var(--gtc-border, #e3ddec);
	white-space: nowrap;
}
body.page-id-61583 #wpforo #wpforo-wrap .gtcch-auth-bar .gtcch-account-avatar {
	flex: 0 0 auto;
}
body.page-id-61583 #wpforo #wpforo-wrap .gtcch-auth-bar .gtcch-account-name {
	flex: 0 1 auto;
	min-width: 0;
	white-space: nowrap;
}
body.page-id-61583 #wpforo #wpforo-wrap .gtcch-auth-bar .gtcch-account-caret {
	flex: 0 0 auto;
}
/* Sizing only (padding, min-height, avatar 40px) is scoped to
   >=769px so it does not override the <=768px compact sizing
   (40px pill, 32px avatar) that the v2.2.0 responsive block sets. */
@media (min-width: 769px) {
	body.page-id-61583 #wpforo #wpforo-wrap .gtcch-auth-bar .gtcch-account-summary {
		min-height: 44px;
		padding: 2px 10px 2px 2px;
	}
	body.page-id-61583 #wpforo #wpforo-wrap .gtcch-auth-bar .gtcch-account-avatar img.avatar {
		width: 40px;
		height: 40px;
	}
}

/* --- Fix 5 (CSS half): guest Reply button gets a pointer cursor ---
   The navigation itself is gtcch-guest-reply-2.2.1.js (enqueued
   on topic pages for guests only). This rule only makes the
   span look clickable. */
body.page-id-61583 #wpforo #wpforo-wrap .wpforo-post .wpf-action.not_reg_user {
	cursor: pointer;
}

/* --- Fix 6: inner-nav <details> is the card at ALL widths ---
   Finding: the served 2.2.0.css is byte-identical to the shipped
   file; the served pages carry exactly ONE nav instance with
   <details open>; the stylesheet already provides a white card
   at every width (outer .gtcch-inner-nav div >=1025px, the
   <details> below that) — no rule in the shipped CSS can produce
   a background-less nav at desktop, and no second nav instance
   exists. Same signature as the v2.1.2 Customizer-preview
   artifact. Fix (belt-and-braces): the <details> is now the card
   at ALL widths (base rule, same tokens + box-sizing:border-box)
   and the outer .gtcch-inner-nav is a transparent positioning
   wrapper at all widths — one card element, no width-dependent
   handoff. The 769-1024px and <=768px blocks' outer-div
   transparent declarations now restate the base state
   (harmless); the 769-1024px <details> card rule restates this
   base rule (harmless). The board-home nav is untouched. */
body.page-id-61583 #wpforo #wpforo-wrap .gtcch-inner-nav {
	background: transparent;
	border: 0;
	box-shadow: none;
	padding: 0;
	box-sizing: border-box;
}
body.page-id-61583 #wpforo #wpforo-wrap .gtcch-inner-nav .gtcch-side-nav-toggle {
	display: block;
	background: #fff;
	border: 1px solid var(--gtc-border, #e3ddec);
	border-radius: 10px;
	box-shadow: var(--gtc-shadow, 0 1px 2px rgba(17, 24, 39, .06));
	padding: 12px;
	box-sizing: border-box;
}

/* --- Fix 7: 320px topic-page cosmetics ---
   The "Admin" badge broke mid-word ("Admi"/"n") and "(@admin)"
   wrapped as "(@admin"/")". Both are short strings that fit the
   ~170px author-data column at 320px, so white-space:nowrap on
   the title, the member-title pill, the nicename and the rating
   badge keeps each whole without risking overflow. The "Choose
   File" button text clipped ("Choos File") because the native
   file input was squeezed inside the reply form; at <=768px it
   gets the full row width so its button renders whole. */
body.page-id-61583 #wpforo #wpforo-wrap .wpforo-post .author-title,
body.page-id-61583 #wpforo #wpforo-wrap .wpforo-post .author-title .wpf-member-title,
body.page-id-61583 #wpforo #wpforo-wrap .wpforo-post .wpf-author-nicename,
body.page-id-61583 #wpforo #wpforo-wrap .wpforo-post .author-rating-full {
	white-space: nowrap;
}
@media (max-width: 768px) {
	body.page-id-61583 #wpforo #wpforo-wrap .wpf-default-attachment #wpf_file {
		width: 100%;
		max-width: 100%;
		box-sizing: border-box;
	}
}

/* ==========================================================================
   v2.3.0 — UNIFIED TOP BAR + BRANDED AUTH PAGES + SECTION POLISH
   (user brief 2026-11-18, Parts 2/3/4/6/8; audit 2026-11-18
   12:39-12:43 EST; registration test PASSED 2026-11-18 12:44-12:45
   EST). Everything below is appended, never edited in place, so
   the v2.2.0/v2.2.1 rules above stay byte-identical and the diff
   stays reviewable. Full notes in the plugin header comment and
   the readme changelog. SEO/sitemap code is untouched.
   ========================================================================== */

/* --- Unified board top bar ---
   One bar on every board page: brand left, centre nav, the
   existing auth bar right. Board home: rendered by
   templates/community-home.php above the header card. Inner
   pages: injected via wpforo_content_start priority 8 (inside
   .wpforo-content, so still under body.page-id-61583). Scoped to
   body.page-id-61583 so nothing leaks onto the rest of the site;
   tokens come from the :root block at the top of this file on
   inner pages and from .gtcch-home on the board home. */
body.page-id-61583 .gtcch-topbar {
	display: flex;
	align-items: center;
	gap: 12px;
	min-width: 0;
	background: #fff;
	border: 1px solid var(--gtc-border, #e3ddec);
	border-radius: 10px;
	box-shadow: var(--gtc-shadow, 0 1px 2px rgba(17, 24, 39, .06));
	padding: 8px 14px;
	margin: 0 0 12px;
	box-sizing: border-box;
}
body.page-id-61583 .gtcch-topbar-brand {
	flex: 0 0 auto;
	font-family: var(--gtc-font-head, 'Overpass', sans-serif);
	font-size: 17px;
	font-weight: 800;
	line-height: 1.2;
	color: var(--gtc-primary-darker, #290342);
	text-decoration: none;
	white-space: nowrap;
}
body.page-id-61583 .gtcch-topbar-brand-mark {
	color: var(--gtc-primary, #8920f3);
}
body.page-id-61583 .gtcch-topbar-brand:hover,
body.page-id-61583 .gtcch-topbar-brand:focus-visible {
	color: var(--gtc-primary-darker, #290342);
	text-decoration: none;
}
/* Centre nav: the links scroll horizontally INSIDE the bar
   (overflow-x:auto, min-width:0) so the bar itself never pushes
   the page past the viewport — the page never scrolls
   horizontally, at any width. */
body.page-id-61583 .gtcch-topbar-nav {
	display: flex;
	align-items: center;
	gap: 2px;
	flex: 1 1 auto;
	min-width: 0;
	justify-content: center;
	overflow-x: auto;
	scrollbar-width: thin;
	-webkit-overflow-scrolling: touch;
}
body.page-id-61583 .gtcch-topbar-link {
	flex: 0 0 auto;
	padding: 8px 12px;
	font-family: var(--gtc-font-head, 'Overpass', sans-serif);
	font-size: 15px;
	font-weight: 600;
	line-height: 1.4;
	color: var(--gtc-text, #3b383e);
	border-radius: 8px;
	text-decoration: none;
	white-space: nowrap;
}
body.page-id-61583 .gtcch-topbar-link:hover,
body.page-id-61583 .gtcch-topbar-link:focus-visible {
	background: var(--gtc-primary-soft, #f7f2fc);
	color: var(--gtc-primary, #8920f3);
	text-decoration: none;
}
body.page-id-61583 .gtcch-topbar-link.is-active {
	background: var(--gtc-primary-soft, #f7f2fc);
	color: var(--gtc-primary, #8920f3);
}
/* The auth bar inside the top bar keeps its own rules (row +
   gap, guest buttons, account dropdown anchored to the bar's
   right edge); it only needs to stay a non-shrinking flex item
   so the buttons are never squeezed. */
body.page-id-61583 .gtcch-topbar .gtcch-auth-bar {
	flex: 0 0 auto;
}
/* .gtcch-auth-bar-wrap (v2.2.0) is unused in v2.3.0 — the top
   bar replaces the auth-bar-only injection — but the rule is
   kept so nothing breaks if an older template ever renders it. */

/* --- Branded sign-in / sign-up pages ---
   Scoped to body.wpft-login / body.wpft-register (the
   wpft-{template} class lands on <body> and #wpforo-wrap,
   functions-template.php:368-373) plus the form elements
   themselves — no assumed wpForo field classes. The form becomes
   a white card in GTCodes branding: dark-purple heading (the
   injected .gtcch-page-h1, already styled), gradient primary
   button, full-width fields, no horizontal overflow at 320px.
   No wpForo setting, URL or redirect behaviour is changed. */
body.wpft-login #wpforo #wpforo-wrap form,
body.wpft-register #wpforo #wpforo-wrap form {
	background: #fff;
	border: 1px solid var(--gtc-border, #e3ddec);
	border-radius: 10px;
	box-shadow: var(--gtc-shadow, 0 1px 2px rgba(17, 24, 39, .06));
	padding: 20px;
	max-width: 520px;
	margin: 0 auto 12px;
	box-sizing: border-box;
}
body.wpft-login #wpforo #wpforo-wrap form *,
body.wpft-register #wpforo #wpforo-wrap form * {
	box-sizing: border-box;
}
body.wpft-login #wpforo #wpforo-wrap form label,
body.wpft-register #wpforo #wpforo-wrap form label {
	display: block;
	font-family: var(--gtc-font-head, 'Overpass', sans-serif);
	font-size: 15px;
	font-weight: 600;
	line-height: 1.4;
	color: var(--gtc-primary-darker, #290342);
	margin: 0 0 4px;
}
body.wpft-login #wpforo #wpforo-wrap form input[type="text"],
body.wpft-login #wpforo #wpforo-wrap form input[type="email"],
body.wpft-login #wpforo #wpforo-wrap form input[type="password"],
body.wpft-register #wpforo #wpforo-wrap form input[type="text"],
body.wpft-register #wpforo #wpforo-wrap form input[type="email"],
body.wpft-register #wpforo #wpforo-wrap form input[type="password"] {
	width: 100%;
	max-width: 100%;
	height: 44px;
	padding: 0 14px;
	font-family: var(--gtc-font-body, 'Overpass', sans-serif);
	font-size: 15px;
	line-height: 1.4;
	color: var(--gtc-text, #3b383e);
	background: #fff;
	border: 1px solid var(--gtc-border, #e3ddec);
	border-radius: 10px;
	margin: 0 0 12px;
}
body.wpft-login #wpforo #wpforo-wrap form input[type="text"]:focus,
body.wpft-login #wpforo #wpforo-wrap form input[type="email"]:focus,
body.wpft-login #wpforo #wpforo-wrap form input[type="password"]:focus,
body.wpft-register #wpforo #wpforo-wrap form input[type="text"]:focus,
body.wpft-register #wpforo #wpforo-wrap form input[type="email"]:focus,
body.wpft-register #wpforo #wpforo-wrap form input[type="password"]:focus {
	outline: 2px solid var(--gtc-primary, #8920f3);
	outline-offset: 1px;
	border-color: var(--gtc-primary, #8920f3);
}
body.wpft-login #wpforo #wpforo-wrap form input[type="submit"],
body.wpft-login #wpforo #wpforo-wrap form button[type="submit"],
body.wpft-login #wpforo #wpforo-wrap form .wpf-button,
body.wpft-register #wpforo #wpforo-wrap form input[type="submit"],
body.wpft-register #wpforo #wpforo-wrap form button[type="submit"],
body.wpft-register #wpforo #wpforo-wrap form .wpf-button {
	width: 100%;
	min-height: 44px;
	padding: 13px 28px;
	font-family: var(--gtc-font-head, 'Overpass', sans-serif);
	font-size: 16px;
	font-weight: 600;
	line-height: 1.2;
	text-transform: capitalize;
	color: #fff;
	background: linear-gradient(43deg, #8920f3 0%, #ff7c58 100%);
	background-color: var(--gtc-primary, #8920f3);
	border: 0;
	border-radius: 100px;
	cursor: pointer;
	text-decoration: none;
	white-space: nowrap;
	transition: var(--gtc-transition, all 0.2s ease);
}
body.wpft-login #wpforo #wpforo-wrap form input[type="submit"]:hover,
body.wpft-login #wpforo #wpforo-wrap form button[type="submit"]:hover,
body.wpft-login #wpforo #wpforo-wrap form .wpf-button:hover,
body.wpft-register #wpforo #wpforo-wrap form input[type="submit"]:hover,
body.wpft-register #wpforo #wpforo-wrap form button[type="submit"]:hover,
body.wpft-register #wpforo #wpforo-wrap form .wpf-button:hover,
body.wpft-login #wpforo #wpforo-wrap form input[type="submit"]:focus-visible,
body.wpft-login #wpforo #wpforo-wrap form button[type="submit"]:focus-visible,
body.wpft-login #wpforo #wpforo-wrap form .wpf-button:focus-visible,
body.wpft-register #wpforo #wpforo-wrap form input[type="submit"]:focus-visible,
body.wpft-register #wpforo #wpforo-wrap form button[type="submit"]:focus-visible,
body.wpft-register #wpforo #wpforo-wrap form .wpf-button:focus-visible {
	background: linear-gradient(135deg, #8920f3 0%, #ff7c58 100%);
	background-color: var(--gtc-primary, #8920f3);
	box-shadow: var(--gtc-shadow-btn, 0 15px 25px -7px rgba(0, 0, 0, .25));
	color: #fff;
	text-decoration: none;
	transform: translateY(-1px);
}
body.wpft-login #wpforo #wpforo-wrap form a,
body.wpft-register #wpforo #wpforo-wrap form a {
	color: var(--gtc-primary, #8920f3);
	font-weight: 600;
}
body.wpft-login #wpforo #wpforo-wrap form a:hover,
body.wpft-register #wpforo #wpforo-wrap form a:hover {
	color: var(--gtc-primary-dark, #6022a0);
}
/* Helper note inserted by gtcch-register-2.3.0.js under the
   Password row (register page only). */
body.wpft-register #wpforo #wpforo-wrap .gtcch-register-note {
	font-size: 13px;
	line-height: 1.5;
	color: var(--gtc-text-muted, #6d6d6f);
	margin: -4px 0 12px;
}

/* --- Inner section pages: compact breadcrumb + section H1 ---
   CSS only, no template override. Scoped to body.wpft-topic
   (section pages only — category, topic, recent and auth pages
   are untouched). The v2.2.1 fix-2 flex head bar is untouched,
   so Start a Discussion still cannot overlap the description;
   the empty state is already correct and is left alone. */
body.wpft-topic #wpforo #wpforo-wrap .wpf-breadcrumb {
	display: flex;
	flex-wrap: wrap;
	align-items: center;
	gap: 2px 8px;
	font-size: 13px;
	line-height: 1.5;
	color: var(--gtc-text-muted, #6d6d6f);
	margin: 0 0 8px;
	padding: 0;
}
body.wpft-topic #wpforo #wpforo-wrap .wpf-breadcrumb a {
	color: var(--gtc-text-muted, #6d6d6f);
	font-weight: 500;
}
body.wpft-topic #wpforo #wpforo-wrap .wpf-breadcrumb a:hover {
	color: var(--gtc-primary, #8920f3);
}
body.wpft-topic #wpforo #wpforo-wrap #wpforo-title {
	font-family: var(--gtc-font-head, 'Overpass', sans-serif);
	font-size: 26px;
	font-weight: 700;
	line-height: 1.25;
	color: var(--gtc-primary-darker, #290342);
	margin: 0 0 4px;
}

/* --- v2.3.0 responsive: top bar + auth pages ---
   The top bar never overflows the page: brand and auth stay
   compact, the centre nav scrolls inside its own bar. The
   v2.2.0 compact auth sizing (<=768px) is reused, not
   duplicated. The injected auth-page H1 drops to 28px at
   <=480px so it fits at 320px. */
@media (max-width: 768px) {
	body.page-id-61583 .gtcch-topbar {
		gap: 8px;
		padding: 6px 10px;
	}
	body.page-id-61583 .gtcch-topbar-brand {
		font-size: 15px;
	}
	body.page-id-61583 .gtcch-topbar-link {
		padding: 8px 8px;
		font-size: 14px;
	}
	body.wpft-login #wpforo #wpforo-wrap form,
	body.wpft-register #wpforo #wpforo-wrap form {
		padding: 16px 14px;
	}
}
@media (max-width: 480px) {
	body.page-id-61583 .gtcch-topbar {
		gap: 6px;
		padding: 6px 8px;
	}
	body.page-id-61583 .gtcch-topbar-brand {
		font-size: 14px;
	}
	.gtcch-page-h1 {
		font-size: 28px;
	}
}

/* ==========================================================================
   v2.3.1 — FIX RELEASE (3 defects from the v2.3.0 verification
   run, 2026-11-18 12:49-12:53 EST; root causes proved by the
   inspection run 2026-11-18 12:54-13:06 EST against the live
   served HTML/CSS). Everything below is appended, never edited
   in place, so the v2.3.0 rules above stay byte-identical and
   the diff stays reviewable. Same-specificity rules here win
   over the v2.3.0 block purely by coming later in the file.
   Full notes in the plugin header comment and the readme
   changelog. SEO/sitemap code is untouched.
   ========================================================================== */

/* --- D1: two-row top bar ---
   Root cause: the v2.3.0 bar was ONE flex row inside
   .gtcch-main (~545-572px on the board home, 524px on
   /sign-in/) while its content is ~695px (brand ~170 + nav
   ~235 + auth ~238 + gaps/padding), and the nav was the only
   shrinkable item (flex 1 1 auto, min-width 0, overflow-x
   auto), so it shrank to ~85-90px showing only "issions"/"Ga",
   and on /sign-in/ the overflow cut the Register pill.
   Fix: gtcch_top_bar_html() now renders two rows. Row 1 is
   brand left + auth right (~408px together, fits even the
   narrowest 524px bar). Row 2 gives the ~235px nav the full
   bar width, so all four links are visible with no scrolling
   inside the bar and no clipping. The bar itself becomes a
   block; each row is a flex row. The nav no longer shrinks
   or scrolls: it wraps (flex-wrap:wrap) instead, so at the
   narrowest widths the links reflow to a second line rather
   than clipping or pushing the page past the viewport. */
body.page-id-61583 .gtcch-topbar {
	display: block;
	padding: 8px 14px 6px;
}
body.page-id-61583 .gtcch-topbar-row {
	display: flex;
	align-items: center;
	min-width: 0;
	box-sizing: border-box;
}
body.page-id-61583 .gtcch-topbar-row-1 {
	justify-content: space-between;
	gap: 8px;
}
body.page-id-61583 .gtcch-topbar-row-2 {
	justify-content: center;
	margin-top: 2px;
}
body.page-id-61583 .gtcch-topbar-brand {
	flex: 0 1 auto;
	min-width: 0;
}
body.page-id-61583 .gtcch-topbar-nav {
	flex: 0 0 auto;
	width: 100%;
	max-width: 100%;
	justify-content: center;
	flex-wrap: wrap;
	overflow: visible;
	scrollbar-width: auto;
}
body.page-id-61583 .gtcch-topbar .gtcch-auth-bar {
	flex: 0 0 auto;
	margin-left: auto;
}

/* --- D2: hide the duplicate Login/Register pairs ---
   Root cause: inner pages render THREE-FOUR Login/Register
   pairs — the top bar, the wpForo tab-row pills (WordPress
   menu "wpForo Navigation", ID 727: #wpf-menu > li:nth-child(6)
   Register to /sign-up/, li:nth-child(7) Login to /sign-in/),
   the Kadence sidebar JOIN US! box (wpforo_profile instance 2),
   and on topic pages the "Please Login or Register" prompt.
   Fix: hide the tab-row Register/Login items and, for guests
   only, the whole sidebar JOIN US! widget. BOTH the nth-child
   selectors AND href-based selectors are used for the tab row,
   so either survives a menu reorder; the href selectors use
   *= (not $=) because the live hrefs carry a ?redirect_to=
   query string, so they do not end in "/sign-up/" — the $=
   variants are kept as well for bare links. The sidebar widget
   is hidden only under body:not(.logged-in), so logged-in
   members keep their My Profile widget. Board home does NOT
   render #wpforo-menu, so the tab-row rules are no-ops there.
   DELIBERATELY NOT HIDDEN: the topic-page "Please Login or
   Register to reply" prompt card (.wpf-please-login —
   contextual, keep it), My Profile / Account / Activity /
   Subscriptions / Logout in the tab row or the top-bar avatar
   dropdown (their hrefs match neither sign-up nor sign-in),
   and the top bar itself. */
body.page-id-61583 #wpf-menu > li:nth-child(6),
body.page-id-61583 #wpf-menu > li:nth-child(7),
body.page-id-61583 #wpf-menu li:has(a[href$="/sign-up/"]),
body.page-id-61583 #wpf-menu li:has(a[href$="/sign-in/"]),
body.page-id-61583 #wpf-menu li:has(a[href*="/sign-up/"]),
body.page-id-61583 #wpf-menu li:has(a[href*="/sign-in/"]) {
	display: none !important;
}
body.page-id-61583:not(.logged-in) #wpforo_profile-2.widget_wpforo_profile,
body.page-id-61583:not(.logged-in) div#wpforo_profile-2 {
	display: none !important;
}

/* --- D1 responsive: two-row top bar at small widths ---
   Row 1 (brand + auth) is ~408px at desktop sizing and
   shrinks with the compact auth buttons at <=768px; row 2
   (nav) wraps instead of scrolling, so the page never scrolls
   horizontally at 320px. Link padding/font step down at
   <=480px so all four links still fit on one row at 320px
   wherever possible (Home ~52 + Discussions ~96 + Games ~62 +
   Search ~62 + gaps ≈ 280px at 13px, inside a ~288px bar);
   if a theme font renders wider, the links wrap to a second
   line inside the bar — visible, never clipped. */
@media (max-width: 768px) {
	body.page-id-61583 .gtcch-topbar {
		padding: 6px 10px 4px;
	}
	body.page-id-61583 .gtcch-topbar-row-1 {
		gap: 6px;
	}
	body.page-id-61583 .gtcch-topbar-row-2 {
		margin-top: 0;
	}
	body.page-id-61583 .gtcch-topbar-link {
		padding: 8px 8px;
		font-size: 14px;
	}
}
@media (max-width: 480px) {
	body.page-id-61583 .gtcch-topbar {
		padding: 6px 8px 4px;
	}
	body.page-id-61583 .gtcch-topbar-brand {
		font-size: 14px;
	}
	body.page-id-61583 .gtcch-topbar-link {
		padding: 6px 6px;
		font-size: 13px;
	}
}

/* ==========================================================================
   v2.3.2 — FIX RELEASE (1 remaining defect from the v2.3.1
   verification run, 2026-11-18 13:08-13:14 EST: on /sign-in/ and
   /sign-up/ ONLY, the top bar's row-1 Register pill is still cut
   at the bar's right edge — gradient ends x=1124, lavender begins
   x=1125, identical to the 2.3.0 measurement; the pill's
   "Register" text is fully visible, only its right rounded end is
   missing. The bar card there is 524px wide (x≈600-1124), inside
   .wpforo-content rather than .gtcch-main; on the board home,
   game, section, topic and /recent/ pages the pill is whole.
   Everything below is appended, never edited in place, so the
   v2.3.1 rules above stay byte-identical. Same-specificity rules
   here win over the v2.3.1 block purely by coming later in the
   file. Full notes in the plugin header comment and the readme
   changelog. SEO/sitemap code is untouched.
   ========================================================================== */

/* --- Row 1 can no longer overflow its card ---
   ROOT CAUSE (from the local CSS + the live measurements —
   what is certain, and what is inferred, are separated in the
   header comment / changelog): the v2.3.1 two-row fix moved the
   centre nav out of row 1, but it left row 1 itself exactly as
   v2.3.0 had it — a NOWRAP flex row (.gtcch-topbar-row has no
   flex-wrap anywhere) whose auth bar is flex:0 0 auto (cannot
   shrink) and whose buttons are white-space:nowrap with fixed
   13px 28px padding, while the brand is white-space:nowrap too.
   Row 1 therefore has NO way to get narrower: when brand + gap
   + auth exceed the row's content box, the excess overflows to
   the right, and the last item — the Register pill — is the one
   that crosses the bar's border-box edge, where it is cut (the
   plugin sets no overflow on the bar, so the clipper is an
   ancestor context on the auth pages, most plausibly
   .wpforo-content / #wpforo-wrap, which on the auth pages also
   carries the 240px injected-nav left padding; that last step
   is INFERRED, not proved — no ancestor rule is visible from
   the plugin's own files). The identical x=1124 cut in 2.3.0
   and 2.3.1 is consistent with this: row 1's overflow
   mechanism was unchanged between the two versions, and the
   auth pages' 524px bar is the one container where brand+auth
   exceed the row. FIX (belt and braces, CSS only): (a) row 1
   wraps, so the auth bar drops to its own line — right-aligned
   there by its existing margin-left:auto — instead of crossing
   the card edge; where brand+auth already fit (the other five
   pages) the wrap never engages and the bar looks exactly as
   in 2.3.1; (b) the bar and its rows are restated as
   border-box / max-width:100% so padding can never push the
   card past its containing block; (c) the auth bar gets
   min-width:0; (d) on the auth templates only, the guest auth
   buttons use the existing compact sizing (40px / 8px 14px /
   14px — the same values as the <=768px rule, no new sizing
   invented), shrinking guest auth from ~241px to ~200px and
   giving ~40px of extra slack inside the 496px content box
   before the wrap even engages. The buttons are deliberately
   NOT given flex-shrink below their min-content: their labels
   are white-space:nowrap, so shrinking the box would spill
   the text out of the pill — the wrap, not button shrinkage,
   is what guarantees the pill stays whole. */
body.page-id-61583 .gtcch-topbar {
	box-sizing: border-box;
	max-width: 100%;
}
body.page-id-61583 .gtcch-topbar-row {
	max-width: 100%;
}
body.page-id-61583 .gtcch-topbar-row-1 {
	flex-wrap: wrap;
	gap: 6px 8px;
}
body.page-id-61583 .gtcch-topbar-brand {
	max-width: 100%;
}
body.page-id-61583 .gtcch-topbar .gtcch-auth-bar {
	min-width: 0;
}
/* Compact auth buttons on the auth pages, at every width
   (body.wpft-login / body.wpft-register are the wpForo
   template classes on <body>; the v2.3.0 branded-form rules
   already rely on them, so they are proved to exist). */
body.wpft-login .gtcch-topbar .gtcch-auth-bar .gtcch-btn,
body.wpft-register .gtcch-topbar .gtcch-auth-bar .gtcch-btn {
	min-height: 40px;
	padding: 8px 14px;
	font-size: 14px;
}

/* ==========================================================================
   v2.3.4 — FIX RELEASE (Register pill cut on inner pages — ROOT CAUSE
   PROVED by the v2.3.3 diagnostic, read live 2026-11-18 13:32-13:36 EST).
   Everything below is appended, never edited in place, so the
   v2.3.2 rules above stay byte-identical. Same-specificity rules
   here win over the earlier blocks purely by coming later in the
   file; the new inner-page rules below win over wpForo's reset by
   specificity (see below). Full notes in the plugin header comment
   and the readme changelog. SEO/sitemap code is untouched.
   ========================================================================== */

/* --- Inner-page padding re-assertion (desktop, all widths) ---
   ROOT CAUSE (proved, not inferred): the v2.3.3 diagnostic showed
   that on /sign-in/ the top bar and BOTH auth buttons compute to
   padding 0 on all four sides (bar 619-1125.1, auth bar 104.7px,
   Register pill 1066.9-1125.1 = 58.3px wide, Login 38.5px), while
   on /community/ the SAME elements compute the plugin's stated
   padding (bar 8px/14px/6px/14px, buttons 13px/28px, pill 118.1px,
   pillMinusBar=-15). Properties NOT in wpForo's reset — background,
   display, border-radius, min-height, gap — still applied on inner
   pages, which is why the gradient/flex layout looked right while
   the padding was 0; min-height:40px from the v2.3.2 compact rule
   also survived, which is why the diagnostic pill is 40px tall.
   The reset is wpForo 2026 theme style.css (Meyer-style reset,
   every selector TWO IDs + one type = (2,0,1)):
     #wpforo #wpforo-wrap div, #wpforo #wpforo-wrap a, ... (and
     ~80 more elements) {margin: 0; padding: 0; border: 0;
     font-size: 100%; vertical-align: baseline;}
   It zeroes margin/padding/border/font-size on every div and a
   inside #wpforo-wrap. The plugin's padding rules all lose to it:
   topbar body.page-id-61583 .gtcch-topbar (0,1,1), .gtcch-btn
   (0,1,0), topbar links (0,1,1), brand font-size (0,1,1),
   secondary border (0,1,0), auth-template compact (0,3,1).
   The right-aligned, padding-less pill (58px instead of ~118px)
   therefore ends exactly on the bar's border edge (pillRight =
   barRight = 1125.1), its right cap flush against the border,
   reading as a straight cut. The v2.3.2 wrap fix could never
   work: row-1 content (~408px) fits the 496px content box; this
   was never row overflow, it was zero padding. The same reset
   also explains the Login link rendering as plain purple text on
   inner pages (padding 0 + border 0 + inherited 13px font =
   text-width link). #wpforo-wrap's own overflow-x:hidden is NOT
   the clipper: its border box ends at 1141.1, 16px beyond the
   pill — the pill's own border box ends at the bar's edge.
   FIX: re-assert the SAME values (no new sizing invented) with
   selectors at (2,1,1)/(2,2,2)/(2,3,1) — two IDs + class(es) +
   type — which beat the reset's (2,0,1). No !important is needed
   (and none is used). Same pattern as the existing inner-page
   colour rules at (2,2,2). Scoped to #wpforo #wpforo-wrap, so
   the board home and game pages (outside #wpforo-wrap, where
   the diagnostic shows the padding already applies) are
   untouched; the button rules are scoped to .gtcch-topbar so no
   other .gtcch-btn inside the board is touched. Also re-asserted
   (the same reset zeroes them): the bar's border + bottom
   margin, the brand and link font-sizes, the button font-size,
   the secondary button's 2px border, and row-2's 2px top margin.
   Responsive variants below mirror the existing <=768px / <=480px
   values (v2.3.0 + v2.3.1 blocks), re-scoped the same way. */
body.page-id-61583 #wpforo #wpforo-wrap .gtcch-topbar {
	padding: 8px 14px 6px;
	margin: 0 0 12px;
	border: 1px solid var(--gtc-border, #e3ddec);
}
body.page-id-61583 #wpforo #wpforo-wrap .gtcch-topbar-brand {
	font-size: 17px;
}
body.page-id-61583 #wpforo #wpforo-wrap .gtcch-topbar-row-2 {
	margin-top: 2px;
}
body.page-id-61583 #wpforo #wpforo-wrap a.gtcch-topbar-link {
	padding: 8px 12px;
	font-size: 15px;
}
body.page-id-61583 #wpforo #wpforo-wrap .gtcch-topbar a.gtcch-btn {
	padding: 13px 28px;
	font-size: 16px;
}
body.page-id-61583 #wpforo #wpforo-wrap .gtcch-topbar a.gtcch-btn-secondary {
	border: 2px solid var(--gtc-primary, #8920f3);
}
/* Auth-template compact buttons (same values as the v2.3.2 rule,
   re-scoped so they survive the reset). Specificity (2,3,1) beats
   the base button rule (2,2,2) above, so the compact sizing still
   wins on /sign-in/ and /sign-up/. */
body.wpft-login #wpforo #wpforo-wrap .gtcch-topbar .gtcch-auth-bar .gtcch-btn,
body.wpft-register #wpforo #wpforo-wrap .gtcch-topbar .gtcch-auth-bar .gtcch-btn {
	min-height: 40px;
	padding: 8px 14px;
	font-size: 14px;
}

/* --- Inner-page padding re-assertion, <=768px ---
   Same values as the existing <=768px rules (v2.3.0 block:
   topbar 6px 10px, brand 15px, link 8px 8px/14px; v2.3.1 block:
   topbar 6px 10px 4px; v2.2.0 block: compact auth buttons
   40px/8px 14px/14px), re-scoped to beat the reset. */
@media (max-width: 768px) {
	body.page-id-61583 #wpforo #wpforo-wrap .gtcch-topbar {
		padding: 6px 10px 4px;
	}
	body.page-id-61583 #wpforo #wpforo-wrap .gtcch-topbar-brand {
		font-size: 15px;
	}
	body.page-id-61583 #wpforo #wpforo-wrap a.gtcch-topbar-link {
		padding: 8px 8px;
		font-size: 14px;
	}
	body.page-id-61583 #wpforo #wpforo-wrap .gtcch-topbar .gtcch-auth-bar .gtcch-btn {
		min-height: 40px;
		padding: 8px 14px;
		font-size: 14px;
	}
}

/* --- Inner-page padding re-assertion, <=480px ---
   Same values as the existing <=480px rules (v2.3.0 + v2.3.1
   blocks), re-scoped to beat the reset. */
@media (max-width: 480px) {
	body.page-id-61583 #wpforo #wpforo-wrap .gtcch-topbar {
		padding: 6px 8px 4px;
	}
	body.page-id-61583 #wpforo #wpforo-wrap .gtcch-topbar-brand {
		font-size: 14px;
	}
	body.page-id-61583 #wpforo #wpforo-wrap a.gtcch-topbar-link {
		padding: 6px 6px;
		font-size: 13px;
	}
}

/* ==========================================================================
   v2.3.5 — FIX RELEASE (user report 2026-11-18 14:20 EST — 7 issues;
   this release covers the 6 that are buildable: powered-by footer,
   inner tab row, registration robustness, wp-login register
   redirect, logged-in auth redirect, header consistency).
   Everything below is appended, never edited in place, so the
   v2.3.4 rules above stay byte-identical. SEO/sitemap code is
   untouched. Full notes in the plugin header comment and the
   readme changelog.
   ========================================================================== */

/* --- 1. Hide the "Powered by wpForo" footer on inner pages ---
   Live markup (verified from the served section/topic/auth HTML
   2026-11-18): <div id="wpforo-poweredby"><p class="wpf-by">
   <a id="bywpforo" ...> Powered by wpForo version 3.2.5</a></p>
   </div>, inside #wpforo-wrap (inside .wpforo-footer). Only this
   div is hidden — nothing else in the footer is touched. The board
   home does not render #wpforo-wrap, so this is a no-op there.
   Selector (3,1,1) beats any theme rule for the footer. */
body.page-id-61583 #wpforo #wpforo-wrap #wpforo-poweredby {
	display: none;
}

/* --- 2. Inner tab row restyled to match the board-home feed nav ---
   LIVE STATE (verified from the served section HTML + the live
   Customizer skin 2026-11-18): the Customizer Additional CSS
   (§2 "Single navigation" + the "Issue 2" block) ALREADY makes
   #wpforo-menu a transparent flex row — 12px/600 links, padding
   12px 8px, min-height 44px, purple active underline on the li —
   so the row is NOT the stock wpForo look. What still differs
   from the board-home feed nav (.gtcch-nav: 13px/600, padding
   9px 7px, inside the white header card) is (a) NO white card
   background — the row sits transparent on the lavender page
   background, reading as a flat bar — and (b) link size/padding.
   FIX: the row becomes the same white card as the top bar / hero
   card (background, border, radius, shadow, bottom margin), and
   at desktop the links take the home nav's 13px/600 + 9px 7px
   with the same purple active/hover state. The 44px min-height
   from the Customizer is deliberately KEPT (tap target; the
   theme's #wpforo-menu min-height:55px keeps the row tall
   anyway). Sizing is scoped to min-width:769px so the
   Customizer's compact 11px tablet sizing (<=768px) and its
   search-overlay behaviour stay exactly as tested; the card
   background applies at all widths (no overflow is set, so the
   <=768px search overlay below the bar is not clipped). The
   hamburger stays as the Customizer leaves it (hidden <=620px,
   scrolling flex row instead). Links are NOT changed — same four
   items + search, same hrefs. The v2.3.1 hide rules for the
   Register/Login tab items are untouched (they target the li
   display; these rules never touch li display). Specificities:
   container (3,1,1) beats the Customizer §2 rule (3,0,0) and the
   theme rule (2,1,0); link rules (4,3,3) beat the Customizer
   link rules (4,1,2) and the theme li-a rule (2,1,2); active
   rules (4,2,2)/(4,3,3) beat the Customizer active rules. No
   !important is used. */
body.page-id-61583 #wpforo #wpforo-wrap #wpforo-menu {
	background: #fff;
	border: 1px solid var(--gtc-border, #e3ddec);
	border-radius: 10px;
	box-shadow: var(--gtc-shadow, 0 1px 2px rgba(17, 24, 39, .06));
	margin: 0 0 12px;
	padding: 0 6px;
}
@media (min-width: 769px) {
	body.page-id-61583 #wpforo #wpforo-wrap #wpforo-menu #wpf-menu > li > a:not([href*=sign-in]):not([href*=sign-up]) {
		padding: 9px 7px;
		font-family: var(--gtc-font-head, 'Overpass', sans-serif);
		font-size: 13px;
		font-weight: 600;
		line-height: 1.4;
		color: var(--gtc-text-soft, #646366);
	}
	body.page-id-61583 #wpforo #wpforo-wrap #wpforo-menu #wpf-menu > li.wpforo-active {
		border-bottom-color: var(--gtc-primary, #8920f3);
	}
	body.page-id-61583 #wpforo #wpforo-wrap #wpforo-menu #wpf-menu > li.wpforo-active > a:not([href*=sign-in]):not([href*=sign-up]) {
		color: var(--gtc-primary, #8920f3);
	}
	body.page-id-61583 #wpforo #wpforo-wrap #wpforo-menu #wpf-menu > li > a:not([href*=sign-in]):not([href*=sign-up]):hover {
		color: var(--gtc-primary, #8920f3);
		text-decoration: none;
	}
}

/* --- 3. Registration: CSS hide for the confirm-password wrapper ---
   Server-side removal is IMPOSSIBLE (proven from wpForo 3.2.5
   source: Members::create() hard-codes user_pass1 != user_pass2
   -> "Password mismatch." with no filter, and
   wpforo_register_fields() has no filter to remove the field —
   the field MUST be submitted, so it is hidden + auto-filled,
   never removed). The JS (gtcch-register-2.3.5.js) does the
   auto-fill and hides the wrapper; this CSS rule hides the SAME
   wrapper even if JS is slow or blocked, so the field never
   flashes visible. Live markup (verified from the served
   /sign-up/ HTML 2026-11-18): the confirm input
   input[name="wpfreg[user_pass2]"] sits in its OWN
   <div style="position:relative">, a direct child of
   .wpf-field-wrap inside .wpf-field-name-user_pass inside
   form[name="wpfreg"]; the Password input sits OUTSIDE that
   div, so hiding it CANNOT hide the Password field. Specificity
   (2,5,4) — far above the reset's (2,0,1). NOTE: with JS fully
   off the CSS hide still applies, so the confirm field stays
   hidden and empty and registration would fail wpForo's
   server-side match check. Accepted: reCAPTCHA already requires
   JS, so a JS-off visitor cannot complete registration anyway.
   reCAPTCHA is NOT touched by this release. */
body.wpft-register #wpforo #wpforo-wrap form[name="wpfreg"] .wpf-field-name-user_pass .wpf-field-wrap > div:has(> input[name="wpfreg[user_pass2]"]) {
	display: none;
}

/* --- 6. Header consistency: breadcrumb on topic + recent pages,
   H1 card padding matches the hero card ---
   (a) The compact breadcrumb rule from v2.3.0 was scoped to
   body.wpft-topic (section pages only). Topic pages
   (body.wpft-post) and /recent/ (body.wpft-recent) render the
   SAME .wpf-breadcrumb markup (verified from the served topic
   and recent HTML 2026-11-18) but got the theme's default
   11px/floated treatment. This rule extends the identical
   compact treatment (flex, wrap, 13px, grey #6d6d6f, 8px bottom
   margin — the theme's chevron :after on each crumb is kept)
   to every board page via body.page-id-61583, so the breadcrumb
   reads the same everywhere it appears. Specificity (2,2,1),
   same as the section rule, later in the file wins where both
   apply (identical declarations, so section pages are
   unchanged). (b) The section/topic H1 card (.wpf-head-bar)
   padding was 14px 16px with margin 0 0 12px; the board-home
   hero card (.gtcch-header) is padding 16px 12px, margin
   0 0 16px. The head-bar now uses the hero's exact values, so
   the H1 card sits in the same rhythm on every page. Same
   selector as the v2.2.0 head-bar rule (2,2,1), later wins.
   H1 font-sizes are NOT changed (hero ~40px, section/topic
   ~28px hierarchy is intentional); the left Games nav is NOT
   touched. The <=768px Customizer .wpf-head-bar display:block
   / padding-right:0 rule (2,1,0) was already beaten by the
   v2.2.0/v2.2.1 rules at (2,2,1), so this changes nothing
   there beyond the padding-right value (12px instead of 16px). */
body.page-id-61583 #wpforo #wpforo-wrap .wpf-breadcrumb {
	display: flex;
	flex-wrap: wrap;
	align-items: center;
	gap: 2px 8px;
	font-size: 13px;
	line-height: 1.5;
	color: var(--gtc-text-muted, #6d6d6f);
	margin: 0 0 8px;
	padding: 0;
}
body.page-id-61583 #wpforo #wpforo-wrap .wpf-breadcrumb a {
	color: var(--gtc-text-muted, #6d6d6f);
	font-weight: 500;
}
body.page-id-61583 #wpforo #wpforo-wrap .wpf-breadcrumb a:hover {
	color: var(--gtc-primary, #8920f3);
}
body.page-id-61583 #wpforo #wpforo-wrap .wpf-head-bar {
	padding: 16px 12px;
	margin: 0 0 16px;
}

/* ==========================================================================
   v2.3.6 — FIX RELEASE (register form two-column on desktop)
   ROOT CAUSE (proven from the live /sign-up/ HTML, 2026-11-18): the
   register form renders two-column on desktop — label floated left,
   input right — while /sign-in/ is single-column branded. The cause
   is the wpForo 2026 theme CSS line 2008:
   #wpforo #wpforo-wrap .wpf-field .wpf-label-wrap {display:
   inline-block; width: 38%; float: left; ...} (2,2,0), plus line
   2010 (.wpf-field-wrap inline-block, 62%) and line 2009
   (.wpf-label white-space: nowrap). The plugin's v2.3.0 branded
   rule `form label {display:block; ...}` NEVER matched anything
   here: the register form has NO <label> elements at all — its
   labels are <p class="wpf-label wpfcl-1"> inside .wpf-label-wrap
   (verified live: 0 <label> in form[name="wpfreg"], 3
   .wpf-label-wrap, 4 .wpf-field-wrap, all three fields in one
   full-width .wpf-td.wpfw-1 cell). The plugin had no
   .wpf-label-wrap / .wpf-field-wrap rules. Pre-existing wpForo
   default behaviour, NOT a 2.3.5 regression.
   FIX: stack each field's label above its input on the register
   page only, and style the <p class="wpf-label"> with the same
   values the branded `form label` rule was meant to give
   (Overpass, 15px/600, 1.4, #290342; white-space normal beats
   the theme's nowrap). Selectors are (2,3,1) and beat the
   theme's (2,2,0) — no !important. Scoped to body.wpft-register
   so login/profile/account forms are untouched. The 520px card,
   gradient button, helper note and confirm-field hide (CSS :has()
   + JS 2.3.5) are NOT changed. The description text (.wpf-desc)
   and the reCAPTCHA widget are NOT touched. At <=768px the theme
   already stacks the label (line 2336), so this changes nothing
   there beyond making desktop match. */
body.wpft-register #wpforo #wpforo-wrap .wpf-field .wpf-label-wrap {
	display: block;
	width: 100%;
	float: none;
	padding: 0 0 4px;
}
body.wpft-register #wpforo #wpforo-wrap .wpf-field .wpf-field-wrap {
	display: block;
	width: 100%;
}
body.wpft-register #wpforo #wpforo-wrap .wpf-field .wpf-label {
	font-family: Overpass, sans-serif;
	font-size: 15px;
	font-weight: 600;
	line-height: 1.4;
	color: #290342;
	white-space: normal;
	margin: 0;
}
