/*
 * gpluo.cn — the chatbot, in the site's own visual language.
 *
 * The reference is the homepage post card (.post-list-thumb), which is what
 * "the site's look" means here — not the plugin's own chat styling, and not the
 * conversation bubbles the theme also ships (those two use opposite shadow
 * conventions: a bubble rests on a light halo and deepens on hover, a card does
 * the reverse). Measured values, live at 1440, 2026-10-19:
 *
 *   fill      linear-gradient(90deg, transparent 3%, rgba(255,255,255,.7) 15%,
 *             … 85%, transparent 97%)   — the ends dissolve into the fixed
 *             background photo, which is how this site does "liquid glass":
 *             no backdrop-filter anywhere on a card, only on four small
 *             floating controls
 *   radius    30px (var(--style_menu_radius))
 *   at rest   box-shadow 1px 1px 5px rgba(0,0,0,.3), no border
 *   on hover  box-shadow 0 1px 20px 10px var(--post-list-thumb)  — #e8e8e8
 *   buttons   #pagination a: transparent fill, 30px, accent ink, same shadows
 *   chips     .post-date: rgba(185,122,87,.15) fill, #b97a57 ink, 6px radius
 *   avatars   .postava img: 1px solid #E8E8E8 circle
 *   dark      card rgba(51,51,51,var(--theme-dm-background_transparency)),
 *             rest 0 1px 35px -8px rgba(26,26,26,.6),
 *             hover 0 1px 20px 0 var(--post_list_matching_color) — #b97a57,
 *             buttons rgba(26,26,26,.6) + 1.5px #7d7d7d30 border + #ccc ink
 *
 * AI Engine's messages theme is driven by --mwai-* custom properties, which the
 * front end writes inline on the container from the theme's settings in the
 * database. Those inline values are why the variable overrides below carry
 * !important: an important author declaration is the only thing that beats a
 * plain inline style, and confining !important to the variable block keeps it
 * out of every real rule below. The consequence is deliberate — the Messages
 * theme's settings screen no longer decides how the chatbot looks; this file
 * does.
 */

/* -------------------------------------------------------------------------
 * Tokens. Light first, then the dark overrides, then everything is mapped
 * onto the plugin's own variables so the plugin's rules do most of the work.
 * ---------------------------------------------------------------------- */

body {
	--gpluo-ai-ink: rgba(0, 0, 0, .66);
	--gpluo-ai-title: #504e4e;
	--gpluo-ai-meta: #888888;
	--gpluo-ai-accent: var(--theme-skin, #b97a57);
	--gpluo-ai-accent-ink: #b97a57;
	--gpluo-ai-wash: rgba(185, 122, 87, .15);
	--gpluo-ai-wash-soft: rgba(185, 122, 87, .08);
	--gpluo-ai-line: rgba(185, 122, 87, .2);
	--gpluo-ai-radius: var(--style_menu_radius, 30px);
	--gpluo-ai-chip: 6px;
	--gpluo-ai-fill: linear-gradient(90deg, rgba(255, 255, 255, 0) 3%, rgba(255, 255, 255, .7) 15%, rgba(255, 255, 255, .7) 85%, rgba(255, 255, 255, 0) 97%);
	--gpluo-ai-surface: rgba(255, 255, 255, .8);
	--gpluo-ai-bubble-ai: #e3bbae;
	--gpluo-ai-bubble-user: #b97a57;
	--gpluo-ai-head: rgba(240, 217, 204, .75);
	--gpluo-ai-edge: rgba(255, 255, 255, 0);
	--gpluo-ai-rest: 1px 1px 5px rgba(0, 0, 0, .3);
	--gpluo-ai-bloom: 0 1px 20px 10px var(--post-list-thumb, #e8e8e8);
	--gpluo-ai-ease: all .8s ease;
}

body.dark {
	--gpluo-ai-ink: #999999;
	--gpluo-ai-title: #cccccc;
	--gpluo-ai-meta: #888888;
	--gpluo-ai-wash: #333333;
	--gpluo-ai-wash-soft: rgba(255, 255, 255, .05);
	--gpluo-ai-line: rgba(255, 255, 255, .1);
	--gpluo-ai-fill: rgba(51, 51, 51, var(--theme-dm-background_transparency, .55));
	--gpluo-ai-surface: rgba(51, 51, 51, .8);
	--gpluo-ai-bubble-ai: rgba(255, 255, 255, .07);
	--gpluo-ai-bubble-user: rgba(185, 122, 87, .3);
	--gpluo-ai-head: rgba(51, 51, 51, .8);
	--gpluo-ai-edge: #7d7d7d30;
	--gpluo-ai-rest: 0 1px 35px -8px rgba(26, 26, 26, .6);
	--gpluo-ai-bloom: 0 1px 20px 0 var(--post_list_matching_color, #b97a57);
}

/* The plugin's variables, retargeted at the tokens above. */
.mwai-messages-theme {
	--mwai-spacing: 15px !important;
	--mwai-fontSize: 15px !important;
	--mwai-lineHeight: 1.6 !important;
	--mwai-borderRadius: var(--gpluo-ai-radius) !important;
	--mwai-width: 420px !important;
	--mwai-maxHeight: 62vh !important;
	--mwai-fontColor: var(--gpluo-ai-ink) !important;
	--mwai-backgroundPrimaryColor: var(--gpluo-ai-surface) !important;
	--mwai-backgroundHeaderColor: var(--gpluo-ai-accent) !important;
	--mwai-bubbleColor: var(--gpluo-ai-accent) !important;
	--mwai-headerButtonsColor: #ffffff !important;
	--mwai-conversationsBackgroundColor: rgba(255, 255, 255, 0) !important;
	--mwai-conversationsTextColor: var(--gpluo-ai-ink) !important;
	--mwai-backgroundUserColor: var(--gpluo-ai-bubble-user) !important;
	--mwai-backgroundAiColor: var(--gpluo-ai-bubble-ai) !important;
	--mwai-backgroundAiSecondaryColor: var(--gpluo-ai-head) !important;
	--mwai-backgroundSecondaryColor: var(--gpluo-ai-wash-soft) !important;
	--mwai-iconTextColor: var(--gpluo-ai-title) !important;
	--mwai-iconTextBackgroundColor: var(--gpluo-ai-surface) !important;
	--mwai-errorBackgroundColor: var(--gpluo-ai-wash) !important;
	--mwai-errorTextColor: var(--gpluo-ai-accent-ink) !important;
}

body.dark .mwai-messages-theme {
	--mwai-fontSize: 14px !important;
	--mwai-spacing: 12px !important;
}

/* -------------------------------------------------------------------------
 * The panel is a card. In discussions mode (which this site has on) the
 * surface is the outer wrapper; without it, the .mwai-content inside is
 * transparent, so both get the same treatment.
 * ---------------------------------------------------------------------- */

.mwai-messages-theme.mwai-discussions,
.mwai-messages-theme .mwai-content {
	background: var(--gpluo-ai-fill);
	border-radius: var(--gpluo-ai-radius);
	box-shadow: var(--gpluo-ai-rest);
	transition: var(--gpluo-ai-ease);
}

.mwai-messages-theme.mwai-discussions:hover,
.mwai-messages-theme .mwai-content:hover {
	box-shadow: var(--gpluo-ai-bloom);
}

.mwai-messages-theme.mwai-discussions .mwai-content {
	background: none;
}

.mwai-messages-theme .mwai-conversation {
	background: none;
}

/* The theme draws a speech tail on every bubble in the panel's surface colour.
   On this site the card has no tail, and the tail's colour variable is not the
   bubble's, so it reads as a mistake rather than as a tail. */
.mwai-messages-theme .mwai-conversation .mwai-reply.mwai-ai::before,
.mwai-messages-theme .mwai-conversation .mwai-reply.mwai-ai::after,
.mwai-messages-theme .mwai-conversation .mwai-reply.mwai-user::before,
.mwai-messages-theme .mwai-conversation .mwai-reply.mwai-user::after {
	display: none;
}

.mwai-messages-theme .mwai-conversation .mwai-reply {
	box-shadow: var(--gpluo-ai-rest);
	transition: var(--gpluo-ai-ease);
}

.mwai-messages-theme .mwai-conversation .mwai-reply:hover {
	box-shadow: 1px 1px 12px rgba(0, 0, 0, .18);
}

body.dark .mwai-messages-theme .mwai-conversation .mwai-reply:hover {
	box-shadow: 0 1px 14px -4px rgba(26, 26, 26, .8);
}

.mwai-messages-theme .mwai-conversation .mwai-reply .mwai-name-text {
	color: var(--gpluo-ai-accent-ink);
	font-weight: var(--global-font-weight, 500);
}

/* Avatars follow .postava img: a plain circle with a hairline edge. */
.mwai-messages-theme .mwai-conversation .mwai-reply img {
	border: 1px solid var(--post-list-thumb, #e8e8e8);
	border-radius: 50%;
	transition: var(--gpluo-ai-ease);
}

/* -------------------------------------------------------------------------
 * Secondary actions — the opening questions and the download button — are the
 * pagination pills: transparent, 30px, accent ink, the same shadow pair. The
 * theme styles every button as a filled accent one, so these need enough
 * specificity to undo that.
 * ---------------------------------------------------------------------- */

.mwai-messages-theme .mwai-shortcuts .mwai-shortcut {
	height: auto;
	padding: 8px 18px;
	background: var(--gpluo-ai-wash-soft);
	border: 1.5px solid var(--gpluo-ai-edge);
	border-radius: var(--gpluo-ai-radius);
	color: var(--gpluo-ai-accent-ink);
	box-shadow: var(--gpluo-ai-rest);
	filter: none;
	transition: var(--gpluo-ai-ease);
}

.mwai-messages-theme .mwai-shortcuts .mwai-shortcut:hover {
	background: var(--gpluo-ai-wash);
	color: var(--gpluo-ai-accent-ink);
	box-shadow: var(--gpluo-ai-bloom);
	filter: none;
}

body.dark .mwai-messages-theme .mwai-shortcuts .mwai-shortcut {
	background: rgba(26, 26, 26, .6);
	border-color: var(--gpluo-ai-edge);
	color: #cccccc;
}

body.dark .mwai-messages-theme .mwai-shortcuts .mwai-shortcut:hover {
	background: rgba(26, 26, 26, .8);
	color: var(--post_list_matching_color, #b97a57);
}

/* The primary action stays filled — that is what the accent is for. */
.mwai-messages-theme .mwai-input .mwai-input-submit {
	background-color: var(--gpluo-ai-accent);
	border-radius: var(--gpluo-ai-radius);
	box-shadow: var(--gpluo-ai-rest);
	filter: none;
	transition: var(--gpluo-ai-ease);
}

.mwai-messages-theme .mwai-input .mwai-input-submit:hover {
	box-shadow: var(--gpluo-ai-bloom);
	filter: none;
}

/* Copy-on-hover on a single reply becomes a chip, not another pill. */
.mwai-messages-theme .mwai-reply-actions .mwai-copy-button {
	background: var(--gpluo-ai-wash);
	border-radius: var(--gpluo-ai-chip);
	color: var(--gpluo-ai-accent-ink);
	filter: none;
}

/* -------------------------------------------------------------------------
 * The conversation tabs are the .post-date chips: accent wash, accent ink,
 * 6px. The theme paints the active one in the header colour, which is the
 * loudest thing in the widget when it is left at the plugin's default blue.
 * ---------------------------------------------------------------------- */

.mwai-messages-theme.mwai-discussions .mwai-header {
	background: var(--gpluo-ai-head);
}

.mwai-messages-theme.mwai-discussions .mwai-discussion.mwai-active .mwai-discussion-title,
.mwai-messages-theme.mwai-discussions .mwai-discussion:hover .mwai-discussion-title {
	background: var(--gpluo-ai-wash);
	border-radius: var(--gpluo-ai-chip);
	color: var(--gpluo-ai-accent-ink);
}

/* -------------------------------------------------------------------------
 * Input, footer line, errors.
 * ---------------------------------------------------------------------- */

.mwai-messages-theme .mwai-input .mwai-input-text {
	background: var(--gpluo-ai-surface);
	border: 1.5px solid var(--gpluo-ai-edge);
	border-radius: var(--gpluo-ai-radius);
	box-shadow: var(--gpluo-ai-rest);
	transition: var(--gpluo-ai-ease);
}

.mwai-messages-theme .mwai-input .mwai-input-text:focus-within {
	box-shadow: var(--gpluo-ai-bloom);
}

.mwai-messages-theme .mwai-input .mwai-input-text textarea::placeholder {
	color: var(--gpluo-ai-meta);
}

.mwai-messages-theme .mwai-compliance {
	color: var(--gpluo-ai-accent-ink);
	opacity: .7;
}

.mwai-messages-theme .mwai-error {
	background: var(--gpluo-ai-wash);
	border-radius: var(--gpluo-ai-radius);
	color: var(--gpluo-ai-accent-ink);
}

.mwai-messages-theme .mwai-text pre,
.mwai-messages-theme .mwai-text p code {
	background: var(--gpluo-ai-wash-soft);
	border-radius: 12px;
}

/* -------------------------------------------------------------------------
 * The floating launcher. It is the site's own third floating button, so it is
 * built to the same spec as the two on the right, measured live at 1440 on
 * 2026-10-19:
 *
 *   #changskin    (bottom right) 45x42, right:10px bottom:15px, radius 30px
 *                            rest  background rgba(255,255,255,0)
 *                                 box-shadow 1px 1px 5px rgba(0,0,0,.3)
 *                            hover background rgba(255,255,255,.85)
 *                                 box-shadow 0 1px 20px 10px #e8e8e8
 *   #moblieGoTop  (above it)     45x28, right:10px bottom:65px, same rest/hover
 *   dark, both:    background rgba(26,26,26,.6), border 1px solid #7d7d7d30,
 *                  box-shadow 0 1px 20px 2px rgba(26,26,26,.8); on hover
 *                  background rgba(26,26,26,.8), shadow 0 1px 30px -2px
 *                  var(--theme-skin-dark)
 *
 * So: same 45x42 box, mirrored to left:10px bottom:15px, same radius, same
 * rest/hover pair, and the picture inset by 7px so it does not run to the edge.
 * The plugin's own trigger styling (a drop-shadow glow and a scale(1.05) on
 * hover) is dropped — the site's buttons neither glow nor move.
 *
 * The 45x42 comes from offsetWidth/offsetHeight, not from the CSS: #changskin
 * starts at transform:scale(0) and is scaled in by the theme's script, and
 * --virtual-time-budget does not advance that transition, so a
 * getBoundingClientRect measure returns 0x0.
 * ---------------------------------------------------------------------- */

.mwai-messages-theme .mwai-trigger .mwai-icon-container {
	box-sizing: border-box;
	display: flex;
	align-items: center;
	justify-content: center;
	width: 45px;
	height: 42px;
	padding: 7px;
	background: rgba(255, 255, 255, 0);
	border: 1px solid rgba(255, 255, 255, 0);
	border-radius: var(--style_menu_radius, 30px);
	box-shadow: 1px 1px 5px rgba(0, 0, 0, .3);
	transition: var(--gpluo-ai-ease);
}

.mwai-messages-theme .mwai-trigger .mwai-icon-container .mwai-icon {
	width: 100%;
	height: 100%;
	object-fit: contain;
	border: 0;
	border-radius: 0;
	filter: none;
	transform: none;
	transition: var(--gpluo-ai-ease);
}

.mwai-messages-theme .mwai-trigger .mwai-icon-container:hover {
	background: rgba(255, 255, 255, .85);
	box-shadow: 0 1px 20px 10px var(--post-list-thumb, #e8e8e8);
}

.mwai-messages-theme .mwai-trigger .mwai-icon-container:hover .mwai-icon {
	transform: none;
}

body.dark .mwai-messages-theme .mwai-trigger .mwai-icon-container {
	background: rgba(26, 26, 26, .6);
	border-color: #7d7d7d30;
	box-shadow: 0 1px 20px 2px rgba(26, 26, 26, .8);
}

body.dark .mwai-messages-theme .mwai-trigger .mwai-icon-container:hover {
	background: rgba(26, 26, 26, .8);
	box-shadow: 0 1px 30px -2px var(--theme-skin-dark, #b97a57);
}

/* An empty icon-text slot would hang 6px of line-height under the button and
   push it off the 15px bottom line the right-hand buttons sit on. */
.mwai-messages-theme .mwai-trigger .mwai-icon-text-container:empty {
	display: none;
}

.mwai-messages-theme .mwai-trigger .mwai-icon-text-container .mwai-icon-text {
	border-radius: var(--gpluo-ai-radius);
	box-shadow: var(--gpluo-ai-rest);
	color: var(--gpluo-ai-accent-ink);
}

/* -------------------------------------------------------------------------
 * Geometry. The window sits where the old widget sat, on the same two lines the
 * theme's own right-hand buttons use: left:10px bottom:15px is the mirror of
 * #changskin's right:10px bottom:15px, which is what "对称" means here.
 *
 * The placement rule has to carry .mwai-bottom-left as well as .mwai-window, and
 * that was learned by measuring, not by reading: the plugin's own placement rule
 * is .mwai-messages-theme.mwai-window.mwai-bottom-left (messages.css:786), three
 * classes, and a two-class rule loses to it no matter how much later it prints.
 * Measured live on 2026-10-19 with the two-class version, the container still sat
 * at 30/30 — the launcher moved to 45x42 (those rules are three-class on both
 * sides, so the later file wins) while the box behind it did not move.
 * ---------------------------------------------------------------------- */

.mwai-messages-theme.mwai-window {
	width: var(--mwai-width);
	max-height: var(--mwai-maxHeight);
}

.mwai-messages-theme.mwai-window.mwai-bottom-left {
	bottom: 15px;
	left: 10px;
	right: auto;
}

.mwai-messages-theme.mwai-window .mwai-content {
	border-radius: var(--gpluo-ai-radius);
}

/* One thing this does not need, checked rather than assumed: a click-through rule.
 * The plugin forces `width: var(--mwai-width)` on .mwai-window whether the window
 * is open or closed (messages.css:696-702), which sounds like a 420px-wide
 * invisible box at z-index 9999 sitting over the page and swallowing clicks — the
 * theme's own floaters are only at z-index 99 (style.css:685). Measured closed on
 * 2026-10-19 it is 420x0: the launcher is position:absolute, so it is out of flow
 * and gives the container no height at all. Nothing to swallow anything. If a
 * future version puts an in-flow child in there, that is when
 * `:not(.mwai-open) { pointer-events: none }` earns its place. */

/* The title bar is gone.
 *
 * The plugin paints it in --mwai-backgroundHeaderColor (messages.css:704-710, a
 * solid #F0D9CC written inline on the container from the bot's own settings) with
 * radius on its top two corners, while .mwai-content carries radius on all four —
 * so a band of one colour met a card of another with two sets of rounded corners
 * facing each other. That is the "最上面一栏和下面的圆角没有连在一起" the site owner
 * described, and no amount of colour matching fixes two radii meeting; hiding the
 * bar leaves one surface with one radius.
 *
 * The bar held the only two controls, so both go with it. The maximize button is
 * deleted outright, and the window bot's fullscreen param is switched off so the
 * setting in the database matches what is on screen (off means the empty string,
 * not '0' — the front end tests it with Boolean(), where "0" is true). Closing
 * becomes "click anywhere else on the page", implemented in gpluo-ai.php by
 * gpluo_ai_window_js() clicking the now-invisible close button: a synthetic click
 * still reaches React's handler, which is the point — the open/closed state stays
 * the plugin's own and this file never has to fight it. */
.mwai-messages-theme.mwai-window.mwai-open .mwai-header {
	display: none !important;
}

/* The two pages that embed a bot inline (/ichigo/ and /studio/) are otherwise
   empty, so an empty conversation leaves the visitor with a banner over a strip
   of input box. /ichigo/ used to hold the page up with eight empty [br]
   paragraphs; this replaces them. The window is position:fixed and sizes itself
   from --mwai-maxHeight, so it is deliberately left alone.

   The height goes on .mwai-conversation, not on the outer container, and that
   was learned the hard way: measured on /ichigo/ at 1440 on 2026-10-19, a
   min-height on .mwai-chatbot made the container 497px while its own
   .mwai-content stopped at 400px, so 97px of empty card sat under the input —
   "底下多出来一截". The container is display:block and nothing stretches it, so
   the only honest way to size these two pages is to size the part that is
   actually meant to grow.

   45vh is arithmetic, not taste: the input row is 85px and the compliance line
   24px, so 45vh + 109px lands on the ~58vh of card the page wants, with nothing
   left over. The plugin already gives .mwai-conversation flex:1 1 auto, so it
   keeps growing on its own once there are messages; the plugin's own
   max-height (70vh) still caps it and scrolls.

   The container is .mwai-conversation, singular — measured in the live DOM,
   where the inline bot prints .mwai-content > .mwai-conversation >
   .mwai-shortcuts. The plural .mwai-conversations is the discussion tab list,
   which only exists with the plugin's discussions mode on, and it is off here.
   Both are listed so the rule keeps working if that mode is ever switched on. */
.mwai-messages-theme:not(.mwai-window) .mwai-conversation,
.mwai-messages-theme:not(.mwai-window) .mwai-conversations {
	min-height: 45vh;
}

@media (max-width: 760px) {
	.mwai-messages-theme {
		--mwai-spacing: 10px !important;
		--mwai-maxHeight: 68vh !important;
	}

	.mwai-messages-theme.mwai-window {
		right: 12px;
		width: auto;
	}

	/* Same three-class selector as the desktop placement rule, for the same
	   reason: the plugin's .mwai-bottom-left is 0,3,0 and would otherwise keep
	   left:30px bottom:30px on phones. */
	.mwai-messages-theme.mwai-window.mwai-bottom-left {
		left: 12px;
		bottom: 12px;
	}

	.mwai-messages-theme .mwai-input .mwai-input-submit {
		width: 56px;
	}
}

@media (prefers-reduced-motion: reduce) {
	.mwai-messages-theme,
	.mwai-messages-theme * {
		transition-duration: .01ms !important;
	}
}

/* -------------------------------------------------------------------------
 * Ichigo drawn on the wall next to her chat (owner, 2026-10-20, item 5).
 *
 * /ichigo/ was asked back to the theme's own background — no cover, no picture —
 * and in light mode that is fine, because the light theme has a photograph behind
 * everything anyway. In dark mode the page is a #333 board from edge to edge with
 * one card in the middle, which the owner calls 太朴素: nothing of hers is on it.
 *
 * So the left margin gets a portrait. gpluo-ichigo-outline.svg is a big-headed
 * chibi drawn in outline only, from the persona in gpluo-ai.php: the closed happy
 * eyes and the two tufts are ꒰ᐢ. ̫ .ᐢ꒱ drawn rather than typed, the arcs under the
 * eyes are 鼓起脸颊, the flower at the fingertip is 收到夸夸时又会从指尖开出小花, the
 * leaf at her left temple is the site's own Ichigo mark (the media-library avatar
 * is a pastel-gradient ginkgo leaf), the berry at her right temple is her name,
 * and the three crosses are the 亮片 she sticks to other people's boards.
 *
 * "轮廓不要和背景对比太强烈，这样就喧宾夺主了" is handled inside the file, not
 * here: the strokes are a pastel gradient at 0.17-0.22 alpha, which composites to
 * about #515151 over the #333 board — a 30-level line, so it reads as a pencil
 * sketch on the wall rather than as a second focal point. The url is relative, so
 * it resolves against /wp-content/mu-plugins/ where this stylesheet lives.
 *
 * The box is 820px wide and centred, so the left margin is (viewport − 820)/2:
 * 310px at 1440, 230px at 1280, 90px at 1000 (ai_geom.py, GEOM_W). The width
 * below is that margin minus an 8px gap, capped at 360px so a 1920 screen does not
 * get a 550px drawing, and the whole thing disappears under 1280 where there is no
 * margin left to draw in — the outline is deliberately not allowed to overlap the
 * chat card, which is why there is no z-index anywhere in this rule.
 *
 * The 830 in the formula is 820 plus 10 for the scrollbar: 100vw is the viewport
 * width *including* the scrollbar, while the margin the drawing has to fit in is
 * computed from the layout width, which excludes it. Measured on the live page
 * with the first version (dark_six_probe.py): width 305px, left −313px, so the
 * drawing started 3px outside the viewport on a scrollbar-less headless frame and
 * about 10px outside on a desktop Chrome with a classic scrollbar. Nothing is lost
 * either way — the leftmost ink in the file is the ginkgo leaf, 24px inside the
 * art — but the slack is what makes that true, so the divisor now gives 7px at
 * every width instead of none.
 * ---------------------------------------------------------------------- */
body.dark .entry-content > .mwai-chatbot-container::before {
	--gpluo-ichigo-w: min(360px, (100vw - 850px) / 2);
	content: "";
	position: absolute;
	left: calc(-1 * (var(--gpluo-ichigo-w) + 8px));
	top: 50%;
	transform: translateY(-50%);
	width: var(--gpluo-ichigo-w);
	height: calc(var(--gpluo-ichigo-w) * 1.25);
	background: url("gpluo-ichigo-outline.svg") no-repeat left center / contain;
	pointer-events: none;
}

@media (max-width: 1279px) {
	body.dark .entry-content > .mwai-chatbot-container::before {
		content: none;
	}
}