
/* ══ value scale ══  95 distinct clamp() triples and 16 near-identical
   light tints had accumulated here, each reasonable on its own. That
   spread is what reads as "close but not quite" next to a template:
   the reference gets its tightness from having very few values and
   reusing them, not from any single measurement. Snapped to six
   spacing steps, eight type steps and three surfaces. */
:root{
  --sp1:clamp(12px,1.4vw,16px);  --sp2:clamp(20px,2.2vw,28px);
  --sp3:clamp(32px,3.6vw,48px);  --sp4:clamp(48px,5.4vw,72px);
  --sp5:clamp(64px,7.5vw,104px); --sp6:clamp(88px,10vw,152px);
  --fs1:13px; --fs2:15px; --fs3:clamp(16px,1.2vw,18px);
  --fs4:clamp(18px,1.5vw,22px);  --fs5:clamp(22px,2.2vw,30px);
  --fs6:clamp(28px,3.4vw,44px);  --fs7:clamp(36px,5vw,64px);
  --fs8:clamp(44px,7vw,96px);
  --raise:#FAF7F0;  /* lifted surface on cream */
  --sunk:#FAF7F0;   /* recessed: tab wells, thumbs */
}

:root{
  --void:#0B1222;
  --hive:#14213D;
  --honey:#F0A500;
  --honey-lo:#845B00;
  --cream:var(--raise);
  --line:#14213D;
  --dim:#9CA2AE;
  --e:var(--ease);
  --r:18px;
}
*{box-sizing:border-box}
html{background:var(--void)}
body{margin:0;background:var(--void);color:#fff;overflow-x:hidden;
  font-family:var(--sans);-webkit-font-smoothing:antialiased}
a{color:inherit;text-decoration:none}
img{display:block;max-width:100%}
h1,h2,h3{margin:0;font-family:var(--display);font-weight:700;
  letter-spacing:-.05em;line-height:.95}
p{margin:0}
button{font:inherit;color:inherit;background:none;border:0;cursor:pointer}
.mono{font-family:var(--mono)}
/* One measure for the whole page. The hero was already opting out of
   this with its own 1400px wrap, so every section below it sat 40px
   inside the hero's text and the nav capsule — visible as two ragged
   vertical lines down the page. 1400 is now the shared value and the
   hero's override is gone. */
.wrap{max-width:1400px;margin:0 auto;padding:0 var(--sp3)}
::selection{background:var(--honey);color:var(--hive)}
:focus-visible{outline:2px solid var(--honey);outline-offset:3px}
[data-fade]{opacity:0}
.no-gsap [data-fade]{opacity:1!important;transform:none!important}
/* ── labels ── */
.tag{display:inline-flex;align-items:center;gap:10px;font-family:var(--mono);
  font-size:11px;letter-spacing:.18em;text-transform:uppercase;color:var(--honey)}
.tag::before{content:"";width:20px;height:1px;background:currentColor}
.tag.dk{color:var(--honey-lo)}

.sec-top{display:flex;align-items:center;justify-content:space-between;gap:20px;
  padding:var(--sp5) 0 var(--sp3)}
.sec-top .no{display:flex;align-items:baseline;gap:14px;font-family:var(--mono);
  font-size:11px;letter-spacing:.16em;text-transform:uppercase}
.sec-top .no .d{color:var(--honey)}
.sec-top .no .t{color:var(--dim)}
.sec-top .hash{font-family:var(--mono);font-size:11px;letter-spacing:.14em;
  text-transform:uppercase;color:#646C7F}
.sec-top.dk .no .d{color:var(--honey-lo)}
.sec-top.dk .no .t,.sec-top.dk .hash{color:#646C7F}
/* ── buttons ── */
.btn{display:inline-flex;align-items:center;gap:9px;padding:15px 28px;border-radius:var(--r-pill);
  font-family:var(--display);font-size:15px;font-weight:600;white-space:nowrap;
  transition:transform .3s var(--e),background .3s,color .3s,border-color .3s}
.btn svg{width:14px;height:14px;transition:transform .3s var(--e)}
.btn:hover svg{transform:translateX(4px)}
.b-honey{background:var(--honey);color:var(--hive)}
.b-honey:hover{transform:translateY(-2px);background:#F5C457}
.b-line{border:1px solid var(--line);color:#fff}
.b-line:hover{border-color:var(--honey);color:var(--honey)}
.b-ink{background:var(--hive);color:#fff}
.b-ink:hover{transform:translateY(-2px);background:#101A30}
/* ═════ NAV ═════ */
/* ═════ floating capsule nav ═════ */
.nav{position:fixed;top:var(--sp1);left:0;right:0;z-index:90;
  display:flex;justify-content:center;padding:0 var(--sp2);pointer-events:none}
.cap{pointer-events:auto;display:flex;align-items:center;gap:var(--sp2);
  max-width:100%;background:rgba(20,33,61,.92);border:1px solid rgba(255,255,255,.09);
  border-radius:var(--r-pill);padding:7px 7px 7px var(--sp2);
  backdrop-filter:blur(16px) saturate(150%);-webkit-backdrop-filter:blur(16px) saturate(150%);
  box-shadow:var(--sh-dark);
  transition:background .4s var(--e),box-shadow .4s var(--e),transform .4s var(--e)}
.nav.stuck .cap{background:rgba(13,22,41,.96);transform:scale(.97);
  box-shadow:var(--sh-dark)}
.cap .brand{display:flex;align-items:center;flex-shrink:0}
.cap .brand img{height:21px;width:auto;transform:translateY(-2px)}
.nav-links{display:flex;align-items:center;gap:var(--sp2)}
.nav-links a{display:inline-flex;align-items:center;line-height:1;
  font-family:var(--display);
  font-size:14px;font-weight:500;letter-spacing:-.01em;color:#CBCED4;
  white-space:nowrap;transition:color .25s}
.nav-links a:hover{color:var(--honey)}
.cap .btn{padding:11px 22px;font-size:13.5px;flex-shrink:0}
@media(max-width:1080px){.nav-links{display:none}}
/* ═════ HERO ═════ */
.hero .aura{position:absolute;left:50%;top:-14%;transform:translateX(-50%);
  width:min(1050px,150vw);aspect-ratio:1;border-radius:50%;pointer-events:none;
  background:radial-gradient(circle,rgba(245,184,0,.15),transparent 58%)}
.hero .wrap{position:relative;z-index:1}
.hero h1 sup{font-size:.18em;vertical-align:super;color:var(--honey);letter-spacing:0}
/* ── photo marquee (full-bleed) ── */
.strip:hover @keyframes slide{to{transform:translateX(calc(-50% - clamp(7px,.8vw,11px)))}}
/* ═════ TEXT MARQUEE ═════ */
@keyframes slide2{to{transform:translateX(-50%)}}
/* ═════ 001 STATEMENT ═════ */
.statement{font-family:var(--display);font-weight:600;
  font-size:var(--fs6);line-height:1.16;letter-spacing:-.04em;max-width:22ch}
.statement em{font-style:normal;color:var(--honey)}
.stmt-row{display:flex;flex-wrap:wrap;gap:30px;align-items:flex-end;
  justify-content:space-between;padding-bottom:var(--sp4)}
.counts{display:grid;grid-template-columns:repeat(4,1fr);gap:1px;background:var(--line);
  border-top:1px solid var(--line);border-bottom:1px solid var(--line)}
.ct{background:var(--void);padding:var(--sp3) var(--sp2)}
.ct .n{font-family:var(--mono);font-size:var(--fs7);
  letter-spacing:-.05em;line-height:1}
.ct .n em{font-style:normal;color:var(--honey)}
.ct .l{margin-top:10px;font-family:var(--mono);font-size:11px;
  letter-spacing:.1em;text-transform:uppercase;color:var(--dim);line-height:1.6}
@media(max-width:760px){.counts{grid-template-columns:1fr 1fr}}
/* ═════ 003 ESIM — cream ═════ */
.cream{background:var(--cream);color:var(--hive)}
.cream h2,.cream h3{color:var(--hive)}
.fg{width:26px;height:19px;border-radius:var(--r-sm);overflow:hidden;flex-shrink:0;
  box-shadow:var(--sh-hair)}
.fg svg{width:100%;height:100%}
/* ═════ 004 HOW — photo + steps ═════ */


/* ═════ FAQ ═════ */
.faq-grid{display:grid;grid-template-columns:.72fr 1.28fr;gap:var(--sp3);
  align-items:start;padding-bottom:var(--sp5)}
.faq-card{background:var(--hive);border-radius:var(--r-md);
  padding:32px;overflow:hidden}
.faq-card .thumb{border-radius:var(--r-sm);overflow:hidden;aspect-ratio:16/10;margin-bottom:24px}

.faq-card h3{font-size:23px;letter-spacing:-.035em}
.faq-card p{margin-top:12px;font-size:14.5px;line-height:1.7;color:var(--dim)}
.faq-card .btn{margin-top:24px}
.qa{border-bottom:1px solid var(--line)}
.qa:first-child{border-top:1px solid var(--line)}
.qa .q{width:100%;display:flex;align-items:center;justify-content:space-between;gap:22px;
  padding:25px 2px;text-align:left;font-family:var(--display);
  font-size:var(--fs4);font-weight:600;letter-spacing:-.03em;transition:color .3s}
.qa .q:hover{color:var(--honey)}
.qa .ic{position:relative;width:16px;height:16px;flex-shrink:0}
.qa .ic::before,.qa .ic::after{content:"";position:absolute;background:var(--honey);
  border-radius:var(--r-sm);transition:transform .4s var(--e)}
.qa .ic::before{left:0;right:0;top:7px;height:2px}
.qa .ic::after{top:0;bottom:0;left:7px;width:2px}
.qa.open .ic::after{transform:rotate(90deg)}
.qa .a{max-height:0;overflow:hidden;transition:max-height .45s var(--e)}
.qa .a p{padding:0 2px 27px;font-size:15.5px;line-height:1.78;color:var(--dim);max-width:62ch}
@media(max-width:880px){.faq-grid{grid-template-columns:1fr}}
/* ═════ BAND + CTA ═════ */
.band{background:var(--honey);color:var(--hive);padding:var(--sp3) 0;overflow:hidden}
.band-t{display:flex;width:max-content;animation:slide2 26s linear infinite}
.band-g{display:flex;align-items:center;gap:var(--sp3);
  padding-right:var(--sp3)}
.band-g b{font-family:var(--display);font-weight:700;
  font-size:var(--fs8);letter-spacing:-.055em;white-space:nowrap;line-height:1}
.band-g i{width:clamp(9px,1.3vw,18px);height:clamp(9px,1.3vw,18px);border-radius:var(--r-pill);
  background:var(--hive);flex-shrink:0}
.cta{text-align:center;padding:var(--sp5) 0}
.cta h2{margin:22px auto 0;font-size:var(--fs7);max-width:15ch}
.cta p{margin:22px auto 34px;font-size:16.5px;line-height:1.7;color:var(--dim);max-width:44ch}
.cta .row2{display:flex;flex-wrap:wrap;gap:13px;justify-content:center}
.cta .fine{margin-top:28px;font-family:var(--mono);font-size:11px;
  letter-spacing:.17em;text-transform:uppercase;color:#646C7F}
/* ═════ FOOTER ═════ */
footer{border-top:1px solid var(--line);padding:var(--sp4) 0 0}
.f-grid{display:grid;grid-template-columns:1.6fr 1fr 1fr 1fr;gap:36px}
.f-tag{margin-top:0;max-width:26em;font-size:14px;line-height:1.75;color:var(--dim)}
.f-grid h4{margin:0 0 15px;font-family:var(--mono);font-size:10.5px;
  letter-spacing:.17em;text-transform:uppercase;color:var(--honey);font-weight:500}
.f-grid a{display:block;padding:7px 0;font-size:14.5px;color:var(--dim);transition:color .25s}
.f-social{display:flex;gap:14px;margin-top:22px}
.f-social a{display:grid;place-items:center;width:38px;height:38px;padding:0;
  border-radius:var(--r-pill);color:var(--dim);
  box-shadow:inset 0 0 0 1px rgba(255,255,255,.14);
  transition:color .25s var(--e),box-shadow .25s var(--e),background .25s var(--e)}
.f-social a:hover{color:var(--navy);background:var(--honey);
  box-shadow:inset 0 0 0 1px var(--honey)}
/* each icon now carries a viewBox centred on its own artwork, so a
   single square here lands all three on the same axis. 18px because
   the glyphs sit inside their boxes with a little air. */
.f-social svg{width:18px;height:18px}
.f-grid a:hover{color:#fff}
.f-btm{margin-top:36px;border-top:1px solid var(--line);padding:24px 0;
  display:flex;flex-wrap:wrap;gap:12px;justify-content:space-between;
  font-family:var(--mono);font-size:10.5px;letter-spacing:.1em;
  text-transform:uppercase;color:#646C7F}
@media(max-width:860px){.f-grid{grid-template-columns:1fr 1fr}}
@media(max-width:520px){.f-grid{grid-template-columns:1fr}}

@media(prefers-reduced-motion:reduce){
  *{animation:none!important;transition:none!important}
  [data-fade]{opacity:1!important;transform:none!important}
}
.px{display:block;width:100%;height:100%;background-size:cover;background-position:center;transition:transform .8s var(--e),filter .5s var(--e)}
.px-number{background-image:url(/home/home-73d5e1790187.webp)}
.px-esim{background-image:url(/home/home-957c98ecdbd7.webp)}
.px-rewards{background-image:url(/home/home-cc9cd023fdae.webp)}
.px-partner{background-image:url(/home/home-73f79bf5a45d.webp)}
/* ── language switcher ── */
.langsw{display:flex;align-items:center;gap:1px;margin-left:auto;flex-shrink:0;
  background:rgba(255,255,255,.06);border-radius:var(--r-pill);padding:2px}
.langsw button{font-family:var(--mono);font-size:10.5px;letter-spacing:.04em;
  padding:6px 10px;border-radius:var(--r-pill);color:#9CA2AE;white-space:nowrap;
  transition:background .25s var(--e),color .25s var(--e)}
.langsw button:hover{color:#fff}
.langsw button[aria-pressed="true"]{background:rgba(255,255,255,.14);color:#fff}
@media(max-width:420px){.langsw button{padding:5px 7px;font-size:10px}}
/* ── CJK: latin tracking is far too tight for Han ── */
:is(html[lang^="zh"],html[lang^="ja"]) body{font-family:var(--display)}
html[lang="zh-CN"] body{font-family:var(--display)}
:is(html[lang^="zh"],html[lang^="ja"]) h2,:is(html[lang^="zh"],html[lang^="ja"]) h3,:is(html[lang^="zh"],html[lang^="ja"]) .statement,:is(html[lang^="zh"],html[lang^="ja"]) .band-g b{font-family:var(--display);font-weight:700;
  letter-spacing:-.005em;line-height:1.2}
html[lang="zh-CN"] h2,html[lang="zh-CN"] h3,html[lang="zh-CN"] .statement,
html[lang="zh-CN"] .band-g b{font-family:var(--display)}
:is(html[lang^="zh"],html[lang^="ja"]) .statement{max-width:24ch;line-height:1.5}
:is(html[lang^="zh"],html[lang^="ja"]) .cta h2{max-width:20ch}
/* ══════════════════════════════════════════════════════════
   LIGHT — cream is the field, navy is the accent
   ══════════════════════════════════════════════════════════ */
:root{
  --void:#FAF7F0;          /* page */
  --hive:#14213D;          /* dark surfaces + primary text */
  --honey:#F0A500;         /* fills, on dark */
  --honey-lo:#845B00;      /* honey as *text* on cream */
  --line:#ECEDEF;          /* hairline on cream */
  --dim:#646C7F;           /* body copy on cream */
}
html,body{background:var(--void)}
body{color:var(--hive)}
/* type + rules that assumed a dark field */
.tag,.sec-top .no .d,.step .k,.cp,.ct .n em,.hero h1 sup,
.qa .q:hover,.plan-outside{color:var(--honey-lo)}
.qa .ic::before,.qa .ic::after{background:var(--honey-lo)}
.mq{border-top-color:var(--line);border-bottom-color:var(--line)}
.b-line{border-color:#CBCED4;color:var(--hive)}
.b-line:hover{border-color:var(--hive);color:var(--hive)}
.cta .fine{color:var(--dim)}
.hero .aura{background:radial-gradient(circle,rgba(245,184,0,.30),transparent 62%)}
/* ── eSIM: the one dark section ── */
.cream{background:var(--hive);color:#fff}
.cream h2,.cream h3{color:#fff}
.cream .sec-top.dk .no .d{color:var(--honey)}
.cream .sec-top.dk .no .t,.cream .sec-top.dk .hash{color:#9CA2AE}
.plan .dur,.fg{box-shadow:inset 0 0 0 1px rgba(255,255,255,.24)}
.cream p.mono{color:#9CA2AE!important}
.cream .b-ink{background:var(--honey);color:var(--hive)}
.cream .b-ink:hover{background:#F5C457}
/* ── FAQ side card stays dark ── */
.faq-card{background:var(--hive);border-color:transparent;color:#fff;
  box-shadow:var(--sh-amb-lift)}
.faq-card h3{color:#fff}
.faq-card p{color:#9CA2AE}
/* ── footer stays dark ── */
footer{background:var(--hive);color:#fff;border-top:0}
.f-tag,.f-grid a{color:#9CA2AE}
.f-grid a:hover{color:#fff}
.f-btm{color:#9CA2AE;border-top-color:rgba(255,255,255,.14)}
/* ── CJK weights read heavy on cream ── */
:is(html[lang^="zh"],html[lang^="ja"]) h2,:is(html[lang^="zh"],html[lang^="ja"]) .statement{font-weight:700}
/* ═════ price comparison ═════ */
.badge{display:inline-flex;align-items:center;gap:9px;background:var(--hive);color:#fff;
  border-radius:var(--r-pill);padding:11px 20px;font-family:var(--display);
  font-size:13.5px;font-weight:600;letter-spacing:-.01em}
.badge::before{content:"";width:7px;height:7px;border-radius:var(--r-pill);background:var(--honey);
  animation:blink 2.2s ease-in-out infinite}
@keyframes blink{0%,100%{opacity:1}50%{opacity:.3}}
.cmp-head h2{margin-top:22px;font-size:var(--fs6);max-width:20ch}
.cmp-head p{margin-top:18px;font-size:16.5px;line-height:1.7;color:var(--dim);max-width:52ch}
.cmp{margin-top:var(--sp3);overflow-x:auto;
  border-radius:var(--r-lg);background:#fff;-webkit-overflow-scrolling:touch}
.cmp table{width:100%;border-collapse:collapse;min-width:760px}
.cmp th,.cmp td{padding:var(--sp2) var(--sp2);text-align:center;
  border-bottom:1px solid var(--line);font-size:15px;vertical-align:middle}
.cmp th:first-child,.cmp td:first-child{text-align:left}
.cmp thead th{font-family:var(--mono);font-size:12px;letter-spacing:.06em;
  color:var(--dim);font-weight:500;background:var(--raise)}
.cmp thead th.us{font-family:var(--display);font-size:17px;font-weight:700;
  letter-spacing:-.025em;color:var(--hive)}
.cmp tbody tr:last-child td{border-bottom:0}
.cmp td:first-child{font-weight:600;color:var(--hive);white-space:nowrap}
.cmp .us{background:#FEF8EB}
.cmp .val{font-family:var(--mono);font-size:17px;color:var(--hive)}
.cmp .us .val{font-size:20px;font-weight:600}
.cmp .sm{font-size:12.5px;color:#9CA2AE;margin-left:4px}
.cmp .win{color:var(--honey-lo);font-weight:700}
.cmp .no{color:#9CA2AE}
.cmp-note{margin-top:20px;font-family:var(--mono);font-size:11.5px;
  line-height:1.9;color:#646C7F;max-width:88ch}
@media(max-width:820px){.cmp{border-radius:var(--r-md)}}

/* ── comparison table on a narrow screen ──
   The table is 760px wide and the container scrolls, but nothing said
   so: on a phone you saw three of the five columns and had no reason
   to think Airalo and Holafly existed. Three fixes — pin the label
   column so a scrolled row still says what it is, fade the right edge
   so there is visibly more to reach, and say it in words underneath. */
.cmp{position:relative}
.cmp th:first-child,.cmp td:first-child{position:sticky;left:0;z-index:1}
.cmp thead th:first-child{background:var(--raise)}
.cmp tbody td:first-child{background:#fff}
.cmp th:first-child::after,.cmp td:first-child::after{content:"";
  position:absolute;top:0;right:0;bottom:-1px;width:14px;
  transform:translateX(100%);pointer-events:none;
  background:linear-gradient(90deg,rgba(20,33,61,.07),rgba(20,33,61,0))}
/* the value and its bracketed term belong on one line */
.cmp .val,.cmp .sm{white-space:nowrap}
.cmp-more{display:none;margin-top:12px;font-family:var(--mono);
  font-size:11.5px;letter-spacing:.06em;color:var(--honey-lo)}
@media(max-width:820px){
  .cmp-more{display:block}
  .cmp th,.cmp td{padding:14px 13px;font-size:14px}
  .cmp td:first-child{font-size:13.5px}
  .cmp .val{font-size:15.5px}
  .cmp .us .val{font-size:17px}
}
@media(hover:none){
  /* a shadow on the pinned column reads better than a gradient on touch */
  .cmp th:first-child,.cmp td:first-child{box-shadow:6px 0 12px -8px rgba(20,33,61,.18)}
}
/* section label: a name, not a catalogue number */
.sec-top{justify-content:flex-start}
.sec-top .no{gap:0}
.sec-top .no .t{display:inline-flex;align-items:center;gap:11px;color:var(--honey-lo)}
.sec-top .no .t::before{content:"";width:22px;height:1px;background:currentColor}
.sec-top.dk .no .t{color:var(--honey)}
.cream .sec-top.dk .no .t{color:var(--honey)}
/* language control gets a name */
.langbox{display:flex;align-items:center;gap:10px;margin-left:auto;flex-shrink:0}
.langsw{margin-left:0}
/* nav CTA carries two words now — keep it from crowding the capsule */
.cap .navcta{padding:11px 20px;font-size:13px;letter-spacing:-.015em}
@media(max-width:560px){.cap .navcta{padding:10px 15px;font-size:12.5px}}
/* ══ less dark: the eSIM block returns to light, set apart by white + hairlines ══ */
.cream{background:#FFFFFF;color:var(--hive);
  border-top:1px solid var(--line);border-bottom:1px solid var(--line)}
.cream h2,.cream h3{color:var(--hive)}
.cream .sec-top.dk .no .t{color:var(--honey-lo)}
.plan .dur,.fg{box-shadow:var(--sh-hair)}
.cream p.mono{color:#646C7F!important}
.cream .b-ink{background:var(--hive);color:#fff}
.cream .b-ink:hover{background:#101A30}
/* the comparison table sits on cream — lift it with white + a soft shadow instead */
.cmp{box-shadow:var(--sh-hair),var(--sh-amb)}
/* footer: still dark, but shorter and lighter in weight */
footer{padding-top:var(--sp4)}
/* ══ language dropdown ══ */
.lang{position:relative;flex-shrink:0}
.lang-btn{display:flex;align-items:center;gap:8px;padding:8px 12px 8px 11px;
  border-radius:var(--r-pill);background:rgba(255,255,255,.07);color:#CBCED4;
  font-family:var(--display);font-size:13px;font-weight:500;white-space:nowrap;
  transition:background .25s var(--e),color .25s var(--e)}
.lang-btn:hover{background:rgba(255,255,255,.13);color:#fff}
.lang-btn svg{width:15px;height:15px;flex-shrink:0;opacity:.8}
/* the globe is the only cue a non-reader gets — do not fade it */
.lang-btn .globe{width:17px;height:17px;opacity:1}
.lang-btn .caret{width:13px;height:13px;transition:transform .3s var(--e)}
.lang.open .lang-btn{background:rgba(255,255,255,.15);color:#fff}
.lang.open .caret{transform:rotate(180deg)}

.lang-menu{position:absolute;right:0;top:calc(100% + 12px);min-width:196px;
  max-height:min(58vh,320px);overflow-y:auto;padding:6px;
  background:rgba(18,29,53,.98);border:1px solid rgba(255,255,255,.13);border-radius:var(--r-md);
  box-shadow:var(--sh-dark-lift);
  opacity:0;transform:translateY(-8px) scale(.97);transform-origin:top right;
  pointer-events:none;transition:opacity .25s var(--e),transform .25s var(--e)}
.lang.open .lang-menu{opacity:1;transform:none;pointer-events:auto}
.lang-menu button{display:flex;align-items:center;gap:10px;width:100%;
  padding:10px 12px;border-radius:var(--r-sm);text-align:left;color:#CBCED4;
  font-family:var(--display);font-size:14px;font-weight:500;
  transition:background .2s,color .2s}
.lang-menu button:hover{background:rgba(255,255,255,.09);color:#fff}
.lang-menu button[aria-selected="true"]{color:#fff}
/* the check icon: fixed box, only visible on the active row */
.lang-menu .lang-tick{width:15px;height:15px;flex:0 0 15px;opacity:0;
  transition:opacity .2s var(--e)}
.lang-menu button[aria-selected="true"] .lang-tick{opacity:1}
/* the name must never wrap */
.lang-menu .name{white-space:nowrap}
/* the ISO tag lives on the button, and only once the name is gone */
.lang-tag{display:none;font-family:var(--mono);font-size:11px;letter-spacing:.08em}
@media(max-width:560px){
  #langCur{display:none}
  .lang-tag{display:inline}
  .lang-btn{padding:9px 11px;gap:6px}
  .lang-menu{min-width:170px}
}
/* ══════════════════════════════════════════════════════════
   The page opens dark and turns light after the hero.
   ══════════════════════════════════════════════════════════ */
.hero{background:#101A30;color:#fff}
.hero .aura{background:radial-gradient(circle,rgba(245,184,0,.22),transparent 60%)}
.hero h1 sup{color:var(--honey)}
.hero .b-line{border-color:rgba(255,255,255,.22);color:#fff}
.hero .b-line:hover{border-color:var(--honey);color:var(--honey)}
/* capsule has to sit on dark hero and on cream further down */
.cap{background:rgba(24,38,68,.94);border-color:rgba(255,255,255,.15)}
.nav.stuck .cap{background:rgba(16,26,47,.97)}
/* first light element after the hero — give it a clean edge */

/* ══════════════════════════════════════════════════════════
   Hero rebuilt: one centred column, no split title
   ══════════════════════════════════════════════════════════ */
.hero .aura{left:50%;top:-4%;width:min(880px,120vw);
  background:radial-gradient(circle,rgba(245,184,0,.16),transparent 64%)}

.pill{display:inline-flex;align-items:center;gap:10px;
  border:1px solid rgba(255,255,255,.17);border-radius:var(--r-pill);padding:8px 18px 8px 14px;
  font-family:var(--mono);font-size:11.5px;letter-spacing:.09em;
  text-transform:uppercase;color:#9CA2AE;white-space:nowrap;max-width:100%;
  overflow:hidden;text-overflow:ellipsis}
/* the dot is decoration, so it lives in CSS — innerHTML swaps cannot wipe it */
.pill::before{content:"";width:7px;height:7px;border-radius:var(--r-pill);background:var(--honey);
  flex-shrink:0;animation:blink 2.4s ease-in-out infinite}
@media(max-width:600px){.pill{font-size:10.5px;letter-spacing:.05em}}
/* ══════════════════════════════════════════════════════════
   Catalogue: fixed panel on the left, long list on the right
   ══════════════════════════════════════════════════════════ */
.anchor{display:block;height:0}
.cat-grid{display:grid;grid-template-columns:minmax(0,.82fr) minmax(0,1.18fr);
  gap:var(--sp4);align-items:start;
  padding:var(--sp5) var(--sp3) var(--sp5)}
.cat-sticky{position:sticky;top:118px}

.cat-tabs{display:inline-flex;gap:3px;background:var(--sunk);border-radius:var(--r-pill);padding:4px;
  margin-bottom:var(--sp2)}
.cat-tabs button{padding:10px 20px;border-radius:var(--r-pill);white-space:nowrap;
  font-family:var(--display);font-size:14px;font-weight:600;letter-spacing:-.015em;
  color:#646C7F;transition:background .3s var(--e),color .3s var(--e)}
.cat-tabs button:hover{color:var(--hive)}
.cat-tabs button[aria-selected="true"]{background:var(--hive);color:#fff}

.cat-copy h2{font-size:var(--fs6);line-height:1.06;letter-spacing:-.045em}
.cat-copy p{margin-top:20px;font-size:16px;line-height:1.75;color:var(--dim);max-width:40ch}
.cat-copy .btn{margin-top:28px}
/* rows */
.cat-list{border-top:1px solid var(--line)}
.crow{position:relative;display:grid;
  grid-template-columns:auto minmax(0,1fr) auto auto auto;
  align-items:center;gap:var(--sp1);
  padding:var(--sp2) 2px;border-bottom:1px solid var(--line)}
.cflagx{width:26px;height:26px;border-radius:var(--r-pill);overflow:hidden;flex-shrink:0;
  box-shadow:var(--sh-hair);opacity:.55;
  transition:opacity .35s var(--e),transform .35s var(--e)}
.cflagx svg{width:100%;height:100%}
.cname{font-family:var(--display);font-weight:700;
  font-size:var(--fs6);letter-spacing:-.04em;line-height:1.1;
  color:rgba(20,33,61,.34);transition:color .35s var(--e),transform .35s var(--e)}
.cmeta{font-family:var(--mono);font-size:14px;letter-spacing:-.01em;
  color:rgba(20,33,61,.36);white-space:nowrap;transition:color .35s var(--e)}
.cprice{font-family:var(--mono);font-size:15px;font-weight:500;
  color:var(--honey-lo);white-space:nowrap;opacity:.6;transition:opacity .35s var(--e)}
.crow .go{width:17px;height:17px;color:var(--hive);opacity:0;
  transform:translateX(-8px);transition:opacity .35s var(--e),transform .35s var(--e)}
.crow:hover .cflagx{opacity:1;transform:scale(1.06)}
.crow:hover .cname{color:var(--hive);transform:translateX(6px)}
.crow:hover .cmeta{color:var(--hive)}
.crow:hover .cprice{opacity:1}
.crow:hover .go{opacity:1;transform:none}

:is(html[lang^="zh"],html[lang^="ja"]) .cname{font-family:var(--display);
  font-weight:700;letter-spacing:0}
html[lang="zh-CN"] .cname{font-family:var(--display)}
:is(html[lang^="zh"],html[lang^="ja"]) .cat-copy h2{line-height:1.3}

.cat-tabs{align-items:center}
/* ══ problem list / scenarios / trust grid ══ */


.whygrid{display:grid;grid-template-columns:repeat(3,1fr);gap:var(--sp2)}
.why{border-top:1px solid var(--line);padding-top:24px}
.why h3{font-size:var(--fs4);letter-spacing:-.03em;line-height:1.32}
.why p{margin-top:12px;font-size:14.5px;line-height:1.78;color:var(--dim)}

section#why,section#cases,section#trust{padding-bottom:var(--sp5)}
:is(html[lang^="zh"],html[lang^="ja"]) .item h3,:is(html[lang^="zh"],html[lang^="ja"]) .pillar h3,:is(html[lang^="zh"],html[lang^="ja"]) .why h3{
  font-family:var(--display);font-weight:700;letter-spacing:0;line-height:1.5}
html[lang="zh-CN"] .item h3,html[lang="zh-CN"] .pillar h3,html[lang="zh-CN"] .why h3{
  font-family:var(--display)}
@media(max-width:900px){.pillars,.whygrid{grid-template-columns:1fr}
  .whygrid{gap:0}.why{padding-bottom:20px}}
/* ══ scenario chips ══ */
.chips{display:flex;flex-wrap:wrap;align-items:center;gap:9px;
  padding-bottom:var(--sp3)}
.chipk{font-family:var(--mono);font-size:11px;letter-spacing:.15em;
  text-transform:uppercase;color:var(--honey-lo);margin-right:6px}
.chip{box-shadow:var(--sh-hair);border-radius:var(--r-pill);padding:9px 16px;
  font-size:14px;color:var(--dim);background:#fff;white-space:nowrap}
/* three steps across, no photo */

/* the page is shorter now — ease the section rhythm to match */
section#trust{padding-bottom:var(--sp4)}
.counts{margin-top:var(--sp3)}
/* ══ compact "how it works" strip under the catalogue ══ */
/* ══ trust cards carry a face ══ */
.whygrid{grid-template-columns:repeat(3,1fr)}
.why{border-top:0;padding-top:0}
.wshot{aspect-ratio:5/4;border-radius:var(--r-md);overflow:hidden;background:#ECEDEF;
  margin-bottom:20px}
.wshot .px{transition:transform .8s var(--e)}
.why:hover .wshot .px{transform:scale(1.05)}
@media(max-width:900px){.whygrid{grid-template-columns:1fr;gap:34px}}
/* ══ page-cut: the next section scrolls up over the pinned one ══ */
.hero{position:relative}
/* ══════════════════════════════════════════════════════════
   HERO — copy on the left, images sliding up on the right
   ══════════════════════════════════════════════════════════ */
.hero{background:#101A30;color:#fff;position:relative}
.hero .aura{position:absolute;left:22%;top:6%;width:min(760px,90vw);aspect-ratio:1;
  border-radius:50%;pointer-events:none;z-index:0;
  background:radial-gradient(circle,rgba(245,184,0,.15),transparent 62%)}
.hero-h{height:280vh;position:relative;z-index:1}
.hero-s{position:sticky;top:0;height:100svh;display:flex;align-items:center;overflow:hidden}
/* left: stacked copy panels */
.pill{display:inline-flex;align-items:center;gap:10px;align-self:flex-start;
  border:1px solid rgba(255,255,255,.17);border-radius:var(--r-pill);padding:8px 18px 8px 14px;
  font-family:var(--mono);font-size:11.5px;letter-spacing:.09em;
  text-transform:uppercase;color:#9CA2AE;margin-bottom:var(--sp2)}
/* the dot is decoration, so it lives in CSS — innerHTML swaps cannot wipe it */
.pill::before{content:"";width:7px;height:7px;border-radius:var(--r-pill);background:var(--honey);
  flex-shrink:0;animation:blink 2.4s ease-in-out infinite}
#numbers{position:relative;z-index:3;background:var(--void)}
/* ── left column: a clear hierarchy instead of one heavy block ── */
.hpk{display:inline-flex;align-items:center;gap:10px;align-self:flex-start;
  margin-bottom:18px;font-family:var(--mono);font-size:12px;letter-spacing:.14em;
  text-transform:uppercase;color:var(--honey)}
.card{width:100%;height:100%;border-radius:var(--r-md);overflow:hidden;background:#101A30;
  opacity:.14;box-shadow:var(--sh-dark);
  transform:rotate(calc(-1 * var(--a) - var(--rot,0deg))) scale(var(--sc,.86));
  transition:transform 1.15s var(--e),opacity .8s var(--e),box-shadow .8s var(--e)}
.slot.off{pointer-events:none}
/* ── the answer now rides on the focused photo ── *//* ── hero: fit one viewport, clear of the floating nav ── */
.hero-cta{margin-top:var(--sp2);display:flex;flex-wrap:wrap;gap:12px}

.hp h1{font-size:var(--fs7);line-height:1.1;letter-spacing:-.04em;max-width:13ch}
.hp h2{font-size:var(--fs6);line-height:1.18;letter-spacing:-.03em;max-width:14ch;
  color:#fff}
/* Han text must not break mid-word, and needs looser leading */
:is(html[lang^="zh"],html[lang^="ja"]) .hp h1,:is(html[lang^="zh"],html[lang^="ja"]) .hp h2,:is(html[lang^="zh"],html[lang^="ja"]) .hp p,
:is(html[lang^="zh"],html[lang^="ja"]) :is(html[lang^="zh"],html[lang^="ja"]) .hp h1,:is(html[lang^="zh"],html[lang^="ja"]) .hp h2{
  font-family:var(--display);font-weight:700;
  letter-spacing:.01em;line-height:1.46}
html[lang="zh-CN"] .hp h1,html[lang="zh-CN"] .hp h2{font-family:var(--display)}
:is(html[lang^="zh"],html[lang^="ja"]) .hp h1{font-size:var(--fs6);max-width:14ch}
:is(html[lang^="zh"],html[lang^="ja"]) .hp h2{font-size:var(--fs6);max-width:14ch}
/* ── the ring: neighbours should still read as photographs ── */

/* ── panels share one grid cell: the tallest one sets the height,
      nothing is out of flow, nothing can overlap ── */
.hero-text{display:grid;align-items:center}
.hp{grid-area:1/1;display:flex;flex-direction:column;justify-content:center;
  opacity:0;transform:translateY(22px);pointer-events:none;visibility:hidden;
  transition:opacity .6s var(--e),transform .6s var(--e),visibility 0s .6s}
.hp.on{opacity:1;transform:none;pointer-events:auto;visibility:visible;
  transition:opacity .6s var(--e),transform .6s var(--e),visibility 0s}
/* ══════════════════════════════════════════════════════════
   AUTHORITATIVE — hero, ring and CJK typography.
   Kept in one place so later edits do not have to hunt for
   scattered overrides.
   ══════════════════════════════════════════════════════════ */

/* CJK: latin tracking and leading are wrong for Han */
:is(html[lang^="zh"],html[lang^="ja"]) body{font-family:var(--display)}
html[lang="zh-CN"] body{font-family:var(--display)}
:is(html[lang^="zh"],html[lang^="ja"]) p,:is(html[lang^="zh"],html[lang^="ja"]) .qa .a p{line-height:1.9}
:is(html[lang^="zh"],html[lang^="ja"]) .tag,:is(html[lang^="zh"],html[lang^="ja"]) .sec-top .no,:is(html[lang^="zh"],html[lang^="ja"]) .mq-g span,
:is(html[lang^="zh"],html[lang^="ja"]) .cm,:is(html[lang^="zh"],html[lang^="ja"]) .ct .l,:is(html[lang^="zh"],html[lang^="ja"]) .cta .fine,
:is(html[lang^="zh"],html[lang^="ja"]) .plan .dur,:is(html[lang^="zh"],html[lang^="ja"]) .f-grid h4,
:is(html[lang^="zh"],html[lang^="ja"]) .pill,:is(html[lang^="zh"],html[lang^="ja"]) .hpk,:is(html[lang^="zh"],html[lang^="ja"]) :is(html[lang^="zh"],html[lang^="ja"]) h2,:is(html[lang^="zh"],html[lang^="ja"]) h3,:is(html[lang^="zh"],html[lang^="ja"]) .statement,
:is(html[lang^="zh"],html[lang^="ja"]) .band-g b{
  font-family:var(--display);font-weight:700;
  letter-spacing:.005em;line-height:1.4}
html[lang="zh-CN"] h2,html[lang="zh-CN"] h3,html[lang="zh-CN"] .statement,
html[lang="zh-CN"] .band-g b{
  font-family:var(--display)}
:is(html[lang^="zh"],html[lang^="ja"]) .item h3,:is(html[lang^="zh"],html[lang^="ja"]) .why h3,:is(html[lang^="zh"],html[lang^="ja"]) .cat-copy h2{line-height:1.5}
.f-grid a,.cat-tabs button,.lang-menu button,.nav-links a{
  font-family:var(--display);
  display:flex;align-items:center;line-height:1.3}
.nav-links a{display:inline-flex}
/* hero copy */
.hero-text{display:grid;align-items:center}
.hp{grid-area:1/1;display:flex;flex-direction:column;justify-content:center;
  opacity:0;transform:translateY(22px);pointer-events:none;visibility:hidden;
  transition:opacity .6s var(--e),transform .6s var(--e),visibility 0s .6s}
.hp.on{opacity:1;transform:none;pointer-events:auto;visibility:visible;
  transition:opacity .6s var(--e),transform .6s var(--e),visibility 0s}
.hp h1{font-size:var(--fs7);line-height:1.1;letter-spacing:-.04em;max-width:13ch}
.hp h2{font-size:var(--fs6);line-height:1.18;letter-spacing:-.03em;
  max-width:14ch;color:#fff}
:is(html[lang^="zh"],html[lang^="ja"]) .hp h1,:is(html[lang^="zh"],html[lang^="ja"]) .hp h2,:is(html[lang^="zh"],html[lang^="ja"]) .hp p,
:is(html[lang^="zh"],html[lang^="ja"]) :is(html[lang^="zh"],html[lang^="ja"]) .hp h1,:is(html[lang^="zh"],html[lang^="ja"]) .hp h2{
  font-family:var(--display);font-weight:700;
  letter-spacing:.01em;line-height:1.46}
html[lang="zh-CN"] .hp h1,html[lang="zh-CN"] .hp h2{font-family:var(--display)}
:is(html[lang^="zh"],html[lang^="ja"]) .hp h1{font-size:var(--fs6);max-width:14ch}
:is(html[lang^="zh"],html[lang^="ja"]) .hp h2{font-size:var(--fs6);max-width:14ch}
/* the ring on the right */
.slot.off{pointer-events:none}
/* ── number rows: term, list price, member price, stock ── */
.crow{grid-template-columns:auto auto minmax(0,1fr) auto auto auto;
  gap:var(--sp1);align-items:center;padding:var(--sp2) 2px}
.ccode{font-family:var(--mono);font-size:var(--fs3);
  font-weight:500;letter-spacing:-.02em;color:rgba(20,33,61,.32);width:2.4em;
  transition:color .35s var(--e)}
.cflagx{width:24px;height:24px}
.cmain{display:flex;flex-direction:column;gap:3px;min-width:0}
.cname{font-family:var(--display);font-weight:700;
  font-size:var(--fs5);letter-spacing:-.035em;line-height:1.15;
  color:rgba(20,33,61,.4);transition:color .35s var(--e)}
.cterm{font-family:var(--mono);font-size:12px;letter-spacing:.02em;
  color:rgba(20,33,61,.42);white-space:nowrap}
.cmoney{display:flex;flex-direction:column;align-items:flex-end;gap:2px;white-space:nowrap}
.clist{font-family:var(--mono);color:var(--hive)}
.clist b{font-size:var(--fs4);font-weight:600;letter-spacing:-.03em}
.clist i{font-style:normal;font-size:12px;color:rgba(20,33,61,.5);margin-left:4px}
.cmem{font-family:var(--mono);font-size:12px;color:var(--honey-lo);
  font-weight:500}
.cstock{display:inline-flex;align-items:center;gap:6px;padding:5px 11px;border-radius:var(--r-pill);
  background:#EAF4EE;color:#2F6B4F;font-size:11.5px;font-weight:600;white-space:nowrap}
.cstock::before{content:"";width:6px;height:6px;border-radius:var(--r-pill);background:#3E9A6E}
.crow:hover .cname,.crow:hover .ccode{color:var(--hive)}
:is(html[lang^="zh"],html[lang^="ja"]) .cname{font-family:var(--display);
  font-weight:700;letter-spacing:.01em}
html[lang="zh-CN"] .cname{font-family:var(--display)}
:is(html[lang^="zh"],html[lang^="ja"]) .cterm,:is(html[lang^="zh"],html[lang^="ja"]) .cmem,:is(html[lang^="zh"],html[lang^="ja"]) .cstock{letter-spacing:.03em}
@media(max-width:820px){
  .crow{grid-template-columns:auto minmax(0,1fr) auto;row-gap:10px}
  .ccode,.crow .go{display:none}
  .cmoney{grid-column:2/4;align-items:flex-start}
  .cstock{grid-column:2/4;justify-self:start}
}
/* ── eSIM: a destination picker, not a price list ── */
.dflag{width:21px;height:21px;border-radius:var(--r-pill);overflow:hidden;flex-shrink:0;
  box-shadow:var(--sh-hair)}
.dflag svg{width:100%;height:100%;display:block}
/* ── hero composition: text gets real room, ring sits inside its column ── */
.hero-grid{width:100%;display:grid;
  grid-template-columns:minmax(0,1.02fr) minmax(0,1fr);
  gap:var(--sp4);align-items:center;padding-top:clamp(78px,9vh,104px)}
.hp p{margin-top:20px;font-size:16.5px;line-height:1.75;color:#9CA2AE;max-width:38ch}
:is(html[lang^="zh"],html[lang^="ja"]) .hp p{font-size:16px;line-height:1.95;max-width:26ch}
/* the focused card is genuinely bigger — no transform scaling, so text
   wraps at the size you actually see it */
.hero-vis{position:relative;height:min(84vh,700px)}
.wheel{--R:clamp(150px,15.5vw,205px);
  position:absolute;top:50%;left:calc(50% + var(--R));
  width:0;height:0;transform:rotate(var(--rot,0deg));
  transition:transform 1.15s var(--e)}
.slot{position:absolute;left:0;top:0;margin:0;
  width:clamp(232px,24vw,440px);aspect-ratio:3/4;
  transform:translate(-50%,-50%) rotate(var(--a)) translate(0,calc(-1 * var(--R)))}
.card{position:relative;width:100%;height:100%;border-radius:var(--r-lg);overflow:hidden;
  background:#101A30;
  transform:rotate(calc(-1 * var(--a) - var(--rot,0deg))) scale(var(--sc,.58));
  transition:transform 1.15s var(--e),opacity .8s var(--e),
             box-shadow .8s var(--e),filter .8s var(--e)}
.slot.on .card{--sc:1;opacity:1;filter:none;box-shadow:var(--sh-dark-lift)}
.slot.near .card{--sc:.58;opacity:.3;filter:blur(1.5px) saturate(.75);
  box-shadow:var(--sh-dark)}
.slot.off .card{--sc:.5;opacity:0;filter:blur(4px)}
/* caption now sizes against the real card width */
.shotcap{position:absolute;left:0;right:0;bottom:0;z-index:2;padding:44px 22px 20px;
  background:linear-gradient(180deg,transparent,rgba(6,11,22,.55) 32%,rgba(6,11,22,.92))}
.shotcap .k{display:block;font-family:var(--mono);font-size:11px;
  letter-spacing:.16em;text-transform:uppercase;color:var(--honey)}
.shotcap strong{display:block;margin-top:8px;font-family:var(--display);
  font-size:17px;font-weight:700;letter-spacing:-.01em;line-height:1.42;color:#fff}
:is(html[lang^="zh"],html[lang^="ja"]) .shotcap strong{font-family:var(--display);
  font-weight:700;letter-spacing:.01em;line-height:1.6;font-size:16.5px}
html[lang="zh-CN"] .shotcap strong{font-family:var(--display)}
@media(max-width:1180px){.wheel{--R:clamp(132px,14vw,172px)}
  .slot{width:clamp(210px,23vw,300px)}}
/* mobile last, so it always wins */

/* ══ page-cut: the next section slides up over the still-pinned hero ══ */
@media(min-width:901px){
  .hero-h{height:380vh}          /* 280vh of panels + 100vh of overhang */
  .hero-s{will-change:transform}
  /* This is pulled up a full viewport to cover the last screen of the
   hero track, so it has to be at least that tall or the hero shows
   through underneath. It used to clear the bar only because the
   content happened to be long enough — trimming two rows and a
   thumbnail was all it took to open a gap. Now it is guaranteed. */
  /* whichever section follows the hero owns this, and that is the
     use-case block now rather than the catalogue */
  #trust{margin-top:-100svh;min-height:100svh;position:relative;z-index:3}
}
/* mobile last, so it always wins */
@media(max-width:900px){
  .hero-h{height:auto}
  .hero-s{position:static;height:auto;padding:118px 0 var(--sp4);transform:none!important}
  .cut-veil{display:none}
  .hero-grid{grid-template-columns:1fr;gap:30px;padding-top:0}
  .hero-text{display:flex;flex-direction:column;gap:52px}
  .hp{opacity:1;transform:none;pointer-events:auto;visibility:visible}
  .hero-vis,.wheel{display:none}
  #trust{margin-top:0}
}
/* the hidden attribute must beat any author display rule */
[hidden]{display:none!important}
/* ── destination rows: same rhythm as the number rows ── */
.dests{display:block}
.crow.dst{grid-template-columns:auto minmax(0,1fr) auto auto}
.crow.dst .cgo{font-family:var(--mono);font-size:12.5px;letter-spacing:.02em;
  color:var(--honey-lo);white-space:nowrap;opacity:.65;transition:opacity .35s var(--e)}
.crow.dst:hover .cgo{opacity:1}
.crow.dst .cname{font-size:var(--fs4)}
@media(max-width:820px){
  .crow.dst{grid-template-columns:auto minmax(0,1fr)}
  .crow.dst .cgo{grid-column:1/3;justify-self:start}
}

/* ══════════════════════════════════════════════════════════
   Tokens taken from the Bees Mobile system file (ph-join-b).
   Four radii, three shadows, one easing pair — do not add more.
   ══════════════════════════════════════════════════════════ */
:root{
  --white:#FFFFFF;
  --navy:#14213D;
  --honey:#F0A500;
  --honey-lift:#F9D994;
  --honey-soft:#FEF8EB;
  --r-sm:10px; --r-md:16px; --r-lg:24px; --r-pill:999px;
  --line:#ECEDEF;
  --body:#111827;
  --slate:#646C7F;
  --display:'Inter','Noto Sans TC','Noto Sans SC','Segoe UI',system-ui,sans-serif;
  --sans:'Inter','Noto Sans TC','Noto Sans SC','Segoe UI',system-ui,-apple-system,sans-serif;
  --mono:'IBM Plex Mono','Noto Sans TC',ui-monospace,SFMono-Regular,Menlo,monospace;
  --sh-hair:0 0 0 1px rgba(20,33,61,.05);
  --sh-amb:0 8px 30px rgba(20,33,61,.06);
  --sh-amb-lift:0 14px 40px rgba(20,33,61,.08);
  --ease:cubic-bezier(.22,.68,.24,1);
  --out:cubic-bezier(.17,.84,.44,1);
  /* the dark hero needs its own pair — a 6% navy shadow is invisible on navy */
  --sh-dark:0 18px 44px rgba(6,11,22,.45);
  --sh-dark-lift:0 34px 80px rgba(6,11,22,.6);
}


/* ── carrier band (ph-join-b) ── */
.marq{background:var(--navy);padding:26px 0}
.marqRow{display:flex;flex-direction:row;align-items:center;gap:var(--sp4);
  text-align:left}
.marqLab{flex:0 0 auto;font-family:var(--sans);font-size:14px;font-weight:600;
  line-height:1.45;color:#fff;letter-spacing:0}
.marqView{position:relative;flex:1;min-width:0;overflow:hidden;
  -webkit-mask-image:linear-gradient(90deg,transparent 0,#000 18px,#000 calc(100% - 46px),transparent 100%);
  mask-image:linear-gradient(90deg,transparent 0,#000 18px,#000 calc(100% - 46px),transparent 100%)}
.track{display:flex;width:max-content;animation:marqSlide 60s linear infinite}
.marqView:hover .track{animation-play-state:paused}
@keyframes marqSlide{to{transform:translateX(-50%)}}
.set{display:flex;align-items:center;flex:0 0 auto}
.it{font-family:var(--sans);font-size:14.5px;font-weight:600;letter-spacing:.2px;
  color:rgba(255,255,255,.82);white-space:nowrap;padding:0 34px}
@media(max-width:760px){
  .marqRow{flex-direction:column;gap:14px;align-items:center;text-align:center}
  .marqLab{font-size:13px}
  .it{font-size:13px;padding:0 22px}
}

/* the carrier band belongs to the first screen — pinned to its floor */
.hero-s .marq{position:absolute;left:0;right:0;bottom:0;z-index:4;
  background:rgba(20,33,61,.72);
  backdrop-filter:blur(8px);-webkit-backdrop-filter:blur(8px);
  border-top:1px solid rgba(255,255,255,.08);padding:20px 0}
.hero-grid{padding-bottom:clamp(86px,10vh,104px)}
@media(max-width:900px){
  .hero-s .marq{position:static;background:var(--navy);border-top:0;
    backdrop-filter:none;-webkit-backdrop-filter:none;margin-top:34px}
  .hero-grid{padding-bottom:0}
}

/* the focused card always sits on top — DOM order must not decide this */
.slot{z-index:1}
.slot.near{z-index:2}
.slot.on{z-index:3}

/* ══ nav: bare at the top, capsule once you scroll ══ */
.nav{padding:var(--sp2) var(--sp2) 0;top:0}
.cap{width:min(100%,1320px);
  background:transparent;border-color:transparent;box-shadow:none;
  backdrop-filter:none;-webkit-backdrop-filter:none;
  padding:7px 7px 7px var(--sp1);
  transition:width .5s var(--ease),background .45s var(--ease),
             border-color .45s var(--ease),box-shadow .45s var(--ease),
             padding .45s var(--ease),transform .45s var(--ease)}
.cap .brand{margin-right:auto}
.nav-links{margin-left:0}

.nav.stuck{padding-top:var(--sp1)}
.nav.stuck .cap{width:auto;
  background:rgba(18,29,53,.94);border-color:rgba(255,255,255,.14);
  backdrop-filter:blur(16px) saturate(150%);-webkit-backdrop-filter:blur(16px) saturate(150%);
  box-shadow:0 16px 40px rgba(6,11,22,.4),inset 0 1px 0 rgba(255,255,255,.06);
  padding:7px 7px 7px var(--sp2);transform:none}
@media(max-width:1080px){
  .cap{width:auto;padding-left:var(--sp1)}
  .cap .brand{margin-right:0}
}

/* ══ nav: identical geometry in both states — only the surface changes ══ */
.cap{width:min(100%,1320px);padding:7px 7px 7px var(--sp1);
  transform:none;
  transition:background .45s var(--ease),border-color .45s var(--ease),
             box-shadow .45s var(--ease),backdrop-filter .45s var(--ease)}
.nav.stuck{padding-top:var(--sp2)}
.nav.stuck .cap{width:min(100%,1320px);
  padding:7px 7px 7px var(--sp1);transform:none}
@media(max-width:1080px){
  .cap,.nav.stuck .cap{width:auto;padding-left:var(--sp1)}
  .cap .brand{margin-right:0}
}

/* ══ scrolled state: a white capsule on the light sections ══ */
.cap .brand{position:relative;display:flex;align-items:center}
.cap .brand img{height:21px;width:auto;transform:translateY(-2px);
  transition:opacity .35s var(--ease)}
.cap .brand .mark-dark{position:absolute;left:0;top:50%;
  transform:translateY(calc(-50% - 2px));opacity:0}
.nav.stuck .cap .brand .mark-light{opacity:0}
.nav.stuck .cap .brand .mark-dark{opacity:1}

.nav.stuck .cap{background:var(--white);border-color:transparent;
  box-shadow:var(--sh-hair),var(--sh-amb-lift);
  backdrop-filter:none;-webkit-backdrop-filter:none}
.nav.stuck .nav-links a{color:var(--body)}
.nav.stuck .nav-links a:hover{color:var(--navy)}
.nav.stuck .lang-btn{background:var(--sunk);color:var(--body)}
.nav.stuck .lang-btn:hover{background:#ECEDEF;color:var(--navy)}
.nav.stuck .lang{color:var(--body)}

/* ══ full-bleed hero: the active photo fills the screen ══ */
.bgstage{position:absolute;inset:0;z-index:0;overflow:hidden}
.bgshot{position:absolute;inset:0;opacity:0;transform:scale(1.08);
  transition:opacity 1.1s var(--ease),transform 8s linear}
.bgshot.on{opacity:1;transform:scale(1)}
.hero-scrim{position:absolute;inset:0;z-index:1;pointer-events:none;
  background:
    linear-gradient(100deg,rgba(9,15,28,.96) 0%,rgba(9,15,28,.88) 34%,
                    rgba(9,15,28,.5) 62%,rgba(9,15,28,.22) 100%),
    linear-gradient(180deg,rgba(9,15,28,.62) 0%,transparent 22%,
                    transparent 62%,rgba(9,15,28,.78) 100%)}
.hero-grid{position:relative;z-index:2}
.hero-s .marq{z-index:4}
.cut-veil{z-index:9}

/* the ring steps aside — dots and the message card stay */
.wheel{display:none}
.hero-vis{height:min(72vh,620px)}

/* the photographs used to be dropped on a phone, back when the hero was
   a stack of panels on a flat navy field; it is a slideshow now, so the
   picture belongs on the small screen too — see the mobile pass below
   for its framing and the scrim that keeps the copy readable. */

/* ══ oversized wordmark, barely there ══
   Latin and untranslated on purpose: it is the company name, not a
   sentence, so it does not change with the language. Clipped at the
   baseline so it reads as the page running out rather than as a word
   that happens to be enormous. */
.f-ghost{margin-top:var(--sp1);
  user-select:none;pointer-events:none;line-height:0}
/* The reference wordmark is sharp — what reads as softness there is
   low contrast plus the fade at its foot, not a blur. A real blur was
   the wrong tool and turned the letters to mush. Crisp edges, low
   opacity, and a gradient mask doing the fade. The mask is a gradient
   rather than a block of background colour laid over the top, so it
   keeps working if the footer ever stops being navy. */
.f-ghost .f-logo{display:block;width:min(1400px,92vw);height:auto;
  margin:0 auto;opacity:.17;
  -webkit-mask-image:linear-gradient(180deg,#000 42%,rgba(0,0,0,0) 96%);
          mask-image:linear-gradient(180deg,#000 42%,rgba(0,0,0,0) 96%)}

/* ══ floating support ══ */
.help{position:fixed;right:clamp(16px,2.4vw,28px);bottom:var(--sp2);z-index:80;
  display:flex;flex-direction:column;align-items:flex-end;gap:12px;
  opacity:0;transform:translateY(14px);pointer-events:none;
  transition:opacity .45s var(--ease),transform .45s var(--ease)}
.help.show{opacity:1;transform:none;pointer-events:auto}

.help-btn{display:inline-flex;align-items:center;gap:9px;
  padding:13px 20px;border-radius:var(--r-pill);
  background:var(--honey);color:var(--navy);
  font-family:var(--display);font-size:14px;font-weight:600;
  box-shadow:var(--sh-hair),0 14px 34px rgba(20,33,61,.22);
  transition:transform .25s var(--ease),background .25s var(--ease)}
.help-btn:hover{transform:translateY(-2px);background:var(--honey-lift)}
.help-btn svg{width:18px;height:18px;flex-shrink:0}
.help-btn .help-close{display:none}
.help.open .help-btn .help-open{display:none}
.help.open .help-btn .help-close{display:block}
.help.open .help-label{display:none}
.help.open .help-btn{padding:14px}

.help-panel{width:min(300px,calc(100vw - 40px));padding:22px;
  background:var(--white);border-radius:var(--r-lg);
  box-shadow:var(--sh-hair),0 26px 60px rgba(20,33,61,.18);
  transform-origin:bottom right}
.help-title{font-family:var(--display);font-size:17px;font-weight:700;color:var(--navy)}
.help-sub{margin-top:8px;font-size:13.5px;line-height:1.7;color:var(--slate)}
.help-item{display:flex;align-items:center;gap:11px;margin-top:12px;
  padding:12px 14px;border-radius:var(--r-md);background:var(--raise);
  font-size:14px;font-weight:600;color:var(--navy);
  transition:background .2s var(--ease)}
.help-item:first-of-type{margin-top:18px}
.help-item:hover{background:var(--honey-soft)}
.help-ico{display:grid;place-items:center;width:30px;height:30px;flex-shrink:0;
  border-radius:var(--r-sm);background:var(--honey);color:var(--navy)}
.help-ico svg{width:16px;height:16px}
.help-note{margin-top:14px;font-family:var(--mono);font-size:11px;color:var(--slate)}
@media(max-width:560px){.help-btn .help-label{display:none}.help-btn{padding:14px}}

/* ══ list rows read as live links, not disabled ones ══ */
.cname{color:var(--navy)}
.ccode{color:var(--slate)}
.cterm{color:var(--slate)}
.cflagx{opacity:1}
.crow.dst .cgo{opacity:1}
.crow .go{opacity:.45;transform:none}

/* hover changes the surface, not the legibility */
.crow{position:relative;border-radius:var(--r-md);
  transition:background .25s var(--ease)}
.crow::before{content:"";position:absolute;left:calc(-1 * clamp(10px,1.4vw,18px));
  right:calc(-1 * clamp(10px,1.4vw,18px));top:0;bottom:0;z-index:-1;
  border-radius:var(--r-md);background:transparent;
  transition:background .25s var(--ease)}
.crow:hover::before{background:var(--sunk)}
.crow:hover .cname{color:var(--navy);transform:translateX(4px)}
.crow:hover .ccode{color:var(--navy)}
.crow:hover .cflagx{transform:scale(1.06)}
.crow:hover .go{opacity:1;transform:translateX(3px);color:var(--honey-lo)}

/* short titles must not break — give them room */
.hp h2{max-width:24ch}
:is(html[lang^="zh"],html[lang^="ja"]) .hp h2{max-width:16ch}
@media(min-width:1200px){
  .hp[data-i="3"] h2{white-space:nowrap;max-width:none}
}

/* ══ free vs member ══ */
.plans{display:grid;grid-template-columns:1fr 1fr;gap:var(--sp2);
  text-align:left;margin:var(--sp3) 0 var(--sp2)}
.plan-card{padding:var(--sp2);border-radius:var(--r-lg);
  display:flex;flex-direction:column}
.plan-free{background:var(--white);box-shadow:var(--sh-hair),var(--sh-amb)}
.plan-member{background:var(--navy);box-shadow:var(--sh-hair),var(--sh-amb-lift)}
.plan-head{display:flex;align-items:center;gap:13px}
.plan-badge{display:grid;place-items:center;width:42px;height:42px;flex-shrink:0;
  border-radius:var(--r-md)}
.plan-badge svg{width:20px;height:20px}
.plan-free .plan-badge{background:var(--honey);color:var(--navy)}
.plan-member .plan-badge{background:var(--honey);color:var(--navy)}
.plan-card h3{font-family:var(--display);font-size:var(--fs4);font-weight:700;
  letter-spacing:-.02em}
.plan-free h3{color:var(--navy)}
.plan-member h3{color:var(--white)}

.plan-price{margin-top:22px;padding:20px 22px;border-radius:var(--r-md);
  display:flex;align-items:baseline;justify-content:space-between;gap:14px;flex-wrap:wrap}
.plan-free .plan-price{background:var(--honey-soft)}
.plan-member .plan-price{background:rgba(255,255,255,.08)}
.plan-price b{font-family:var(--mono);font-size:var(--fs5);font-weight:500;
  letter-spacing:-.03em;line-height:1}
.plan-free .plan-price b{color:var(--navy)}
.plan-member .plan-price b{color:var(--honey)}
.plan-price span{font-size:13px;font-weight:500}
.plan-free .plan-price span{color:var(--slate)}
.plan-member .plan-price span{color:#9CA2AE}

.plan-list{list-style:none;margin:24px 0 0;padding:0;display:flex;flex-direction:column;gap:13px}
.plan-list li{display:flex;align-items:flex-start;gap:11px;font-size:14.5px;line-height:1.6}
.plan-free .plan-list li{color:var(--body)}
.plan-member .plan-list li{color:#CBCED4}
.plan-list b{font-weight:700}
.plan-free .plan-list b{color:var(--navy)}
.plan-member .plan-list b{color:var(--white)}
.pk{display:grid;place-items:center;width:19px;height:19px;flex-shrink:0;margin-top:1px;
  border-radius:var(--r-pill)}
.pk svg{width:11px;height:11px}
.plan-free .pk{background:var(--honey);color:var(--navy)}
.plan-member .pk{background:rgba(245,184,0,.18);color:var(--honey)}

.plan-cta{margin-top:auto;padding-top:28px}
.plan-cta{display:block;text-align:center;margin-top:auto;
  padding:14px 22px;border-radius:var(--r-pill);
  font-family:var(--display);font-size:14.5px;font-weight:600;
  transition:transform .25s var(--ease),background .25s var(--ease)}
.plan-free .plan-cta{background:var(--navy);color:var(--white);margin-top:28px}
.plan-free .plan-cta:hover{transform:translateY(-2px);background:#101A30}
.plan-member .plan-cta{background:var(--honey);color:var(--navy);margin-top:28px}
.plan-member .plan-cta:hover{transform:translateY(-2px);background:var(--honey-lift)}
@media(max-width:820px){.plans{grid-template-columns:1fr}}

/* real hero photography — 1600x1000, subject right, quiet left third */
.px-hero{background-image:url(/home/home-ee9a824cb6ad.webp)}
.px-room{background-image:url(/home/home-6570bb95a24e.webp)}

/* the carrier-room frame is much brighter than the rest — grade it to match */



/* ══ lighter hero: keep the left readable, let the photo breathe ══ */


.bgshot.px-number,.bgshot.px-partner{filter:brightness(.9)}
.hero-scrim{background:
  linear-gradient(100deg,
    rgba(9,15,28,.90) 0%,
    rgba(9,15,28,.76) 34%,
    rgba(9,15,28,.34) 62%,
    rgba(9,15,28,.06) 100%),
  linear-gradient(180deg,
    rgba(9,15,28,.42) 0%,
    transparent 20%,
    transparent 64%,
    rgba(9,15,28,.68) 100%)}

/* right side clears almost completely; the left keeps just enough for the copy */
.hero-scrim{background:
  linear-gradient(100deg,
    rgba(9,15,28,.90) 0%,
    rgba(9,15,28,.74) 32%,
    rgba(9,15,28,.20) 55%,
    rgba(9,15,28,0)   78%),
  linear-gradient(180deg,
    rgba(9,15,28,.34) 0%,
    transparent 18%,
    transparent 68%,
    rgba(9,15,28,.60) 100%)}



/* ══ carrier band: frosted glass, photo showing through ══ */
.hero-s .marq{background:rgba(9,15,28,.30);
  backdrop-filter:blur(20px) saturate(150%);
  -webkit-backdrop-filter:blur(20px) saturate(150%);
  border-top:1px solid rgba(255,255,255,.13);
  box-shadow:inset 0 1px 0 rgba(255,255,255,.09);
  padding:16px 0}
.marqRow{gap:var(--sp3)}
.marqLab{display:flex;align-items:center;gap:10px;flex:0 0 auto;
  font-family:var(--sans);font-size:13.5px;line-height:1.3;letter-spacing:0}
.marqIco{display:grid;place-items:center;width:22px;height:22px;flex-shrink:0;color:var(--honey)}
.marqIco svg{width:100%;height:100%}
.marqLab b{font-weight:700;color:#fff;white-space:nowrap}
.marqLab i{font-style:normal;font-weight:400;color:rgba(255,255,255,.62);white-space:nowrap}
.it{color:rgba(255,255,255,.9)}
@media(max-width:900px){
  /* one line on a phone: the icon, the claim and the coverage note stay
     on the same row, with a dot between the two pieces of text, and the
     type steps down far enough for the row to fit a 360px screen. The
     old rule wrapped the note onto a second line. */
  .marqLab{flex-wrap:nowrap;justify-content:center;gap:7px;max-width:100%;
    font-size:clamp(10.5px,3vw,12.5px)}
  .marqLab i{width:auto;text-align:left;min-width:0;overflow:hidden;
    text-overflow:ellipsis}
  .marqLab b{min-width:0;overflow:hidden;text-overflow:ellipsis}
  .marqLab i::before{content:"·";margin-right:7px;opacity:.5}
  .marqIco{width:17px;height:17px}
}

/* hero button pair: same height, same padding, width follows the label */
.hero-cta .btn{min-height:50px;padding:0 26px;justify-content:center;
  line-height:1;letter-spacing:.01em}
.hero-cta .btn svg{margin-left:2px}
:is(html[lang^="zh"],html[lang^="ja"]) .hero-cta .btn{letter-spacing:.06em;padding:0 24px}
@media(max-width:560px){.hero-cta .btn{min-height:46px;padding:0 20px}}

.px-home{background-image:url(/home/home-7fc1b1fc5190.webp)}
.px-friends{background-image:url(/home/home-dc80374530f3.webp)}



.hero-grid{grid-template-areas:"copy visual" "rail visual"}
.hero-text{grid-area:copy}
.hero-vis{grid-area:visual}
.hero-grid{grid-template-rows:auto auto;align-items:center}
@media(max-width:900px){
  .hero-grid{grid-template-areas:"copy";grid-template-rows:auto}
}

/* copy and its progress form one block */
.hero-grid{grid-template-areas:none;grid-template-rows:auto;
  grid-template-columns:minmax(0,1.02fr) minmax(0,1fr)}
.hero-left{display:flex;flex-direction:column;align-items:flex-start;min-width:0}
.hero-text{grid-area:auto;width:100%}
.hero-vis{grid-area:auto}
@media(max-width:900px){.hero-left{display:block}}


/* ══ hero progress — bottom-left, aligned with the copy ══ */
.hero-rail{position:absolute;left:0;right:0;z-index:5;pointer-events:none;
  bottom:calc(clamp(56px,7vh,72px) + 20px)}
.hd-bars{display:flex;align-items:center;gap:7px}
.hd{width:30px;height:3px;border-radius:var(--r-pill);
  background:rgba(255,255,255,.26);
  transition:background .35s var(--ease),width .35s var(--ease)}
.hd.on{background:var(--honey);width:46px}
@media(max-width:900px){.hero-rail{display:none}}

/* ══ catalogue section on white ══ */
#numbers{background:var(--white)}
#numbers .cat-tabs{background:var(--sunk)}
#numbers .crow:hover::before{background:var(--raise)}
#numbers .dest,#numbers .plan{background:var(--white)}
#numbers #numbers .cat-list,#numbers .crow{border-color:#ECEDEF}

/* ══ plans section on navy ══ */
.cta{background:var(--navy)}
.cta .tag{color:var(--honey)}
.cta h2{color:var(--white)}
.cta p{color:#9CA2AE}
.cta .fine{color:#646C7F}
/* member card must lift off a navy field, not vanish into it */
.plan-member{background:#14213D;
  box-shadow:inset 0 0 0 1px rgba(245,184,0,.35),0 22px 50px rgba(6,11,22,.4)}
.plan-free{box-shadow:0 22px 50px rgba(6,11,22,.34)}
.plan-price b{line-height:1.15}
:is(html[lang^="zh"],html[lang^="ja"]) .plan-price b{letter-spacing:.02em}

/* the $40 is the single biggest objection on the page, and it has an
   answer — so the answer belongs against the price, not in the note. */
/* hidden unless the section carries data-promo="fee-waiver", so pulling
   the offer is one attribute and cannot be half-removed. */
.plan-waive{display:none}
[data-promo~="fee-waiver"] .plan-waive{display:block;
  margin:10px 0 0;padding:11px 14px;border-radius:var(--r-sm);
  background:rgba(245,184,0,.12);border:1px solid rgba(245,184,0,.28);
  font-size:13px;line-height:1.65;color:var(--honey-lift)}
:is(html[lang^="zh"],html[lang^="ja"]) .plan-waive{font-size:13.5px;line-height:1.8}
/* terms, set like terms: small, dim, and ranged left so they line up
   with the ticks above rather than floating loose in the middle. They
   stay on the page because they cost money — you must also open a
   number, and the fee does not come back. */
.plan-note{margin:14px 0 2px;font-size:11px;line-height:1.75;
  color:#646C7F;text-align:left}
.plan-free .plan-note{color:#646C7F}
.plan-price b{white-space:nowrap}

.plan-actions{margin-top:auto;display:flex;flex-direction:column;align-items:center;gap:12px}
.plan-actions .plan-cta{margin-top:0;width:100%}
.plan-more{font-family:var(--display);font-size:14px;font-weight:600;
  letter-spacing:-.005em;color:var(--honey);transition:color .2s}
.plan-more:hover{color:var(--honey)}

/* Filipino runs on the Latin stack — keep the CJK tracking rules off it */
html[lang="fil-PH"] body{font-family:var(--sans)}
html[lang="fil-PH"] h1,html[lang="fil-PH"] h2,html[lang="fil-PH"] h3{font-family:var(--display)}
html[lang="fil-PH"] .hp h1{font-size:var(--fs6);max-width:16ch}
html[lang="fil-PH"] .hp h2{font-size:var(--fs5);max-width:17ch}
html[lang="fil-PH"] .hp p{max-width:40ch;font-size:15px;line-height:1.75}

/* ══ section eyebrows: one size, readable ══ */
.tag,.sec-top .no,.sec-top .no .t,.hpk,.chipk{
  font-family:var(--mono);font-size:13px;letter-spacing:.14em;font-weight:500}
.tag::before{width:26px}
.sec-top .no .t::before{width:26px}
:is(html[lang^="zh"],html[lang^="ja"]) .tag,:is(html[lang^="zh"],html[lang^="ja"]) .sec-top .no,:is(html[lang^="zh"],html[lang^="ja"]) .sec-top .no .t,
:is(html[lang^="zh"],html[lang^="ja"]) .hpk,:is(html[lang^="zh"],html[lang^="ja"]) .chipk{
  font-family:var(--display);font-size:14px;font-weight:700;letter-spacing:.08em}

/* ══ hero: capability pills on a continuous loop ══ */
.ticks-track{list-style:none;margin:0;padding:0;
  display:flex;flex-direction:column;align-items:flex-end;
  will-change:transform}
.ticks:hover .ticks-track{animation-play-state:paused}

/* uniform margin, never gap — gap breaks the -50% wrap */
:is(html[lang^="zh"],html[lang^="ja"]) .tick{font-weight:700;letter-spacing:.04em}
@media(max-width:1100px){.ticks{display:none}}
@media(prefers-reduced-motion:reduce){.ticks-track{animation:none}}

/* ticker: a small block in the lower right, uniform pills */
.ticks{position:absolute;z-index:6;right:clamp(18px,3vw,44px);
  bottom:calc(clamp(56px,7vh,72px) + 34px);
  width:min(250px,26vw);height:150px;overflow:hidden;
  -webkit-mask-image:linear-gradient(180deg,transparent,#000 32%,#000 68%,transparent);
  mask-image:linear-gradient(180deg,transparent,#000 32%,#000 68%,transparent)}
.tick{margin:0 0 8px;padding:9px 16px;border-radius:var(--r-pill);white-space:nowrap;
  background:rgba(255,255,255,.12);color:rgba(255,255,255,.82);
  font-family:var(--display);font-size:12.5px;font-weight:600;letter-spacing:.02em;
  backdrop-filter:blur(8px);-webkit-backdrop-filter:blur(8px)}
:is(html[lang^="zh"],html[lang^="ja"]) .tick{font-weight:700;letter-spacing:.04em;font-size:12.5px}

/* ── marquee, CJK ──
   The 84px ceiling is a Latin size. A Han glyph fills its whole em
   square while lowercase Latin sits at about half of it, so the same
   font-size carries roughly twice the ink — and at 700 the strokes in
   dense characters start to merge. Smaller, lighter, slightly tracked
   out, with the dots and padding scaled to match. */
:is(html[lang^="zh"],html[lang^="ja"]) .band-g b{font-size:var(--fs6);
  font-weight:600;letter-spacing:.03em;line-height:1.15}
:is(html[lang^="zh"],html[lang^="ja"]) .band-g i{width:clamp(6px,.75vw,10px);height:clamp(6px,.75vw,10px)}
:is(html[lang^="zh"],html[lang^="ja"]) .band-g{gap:var(--sp2);
  padding-right:var(--sp2)}
:is(html[lang^="zh"],html[lang^="ja"]) .band{padding:var(--sp3) 0}

/* ── hero: more light on the right ──
   The right half is the photograph doing the selling; the left only
   has to stay readable behind the headline. So the horizontal scrim
   clears earlier, the bottom vignette eases off, and each slide gets
   lifted — px-room was carrying the heaviest hand at .88. The two
   left-most stops keep their values so the copy loses no contrast,
   and the top stop is untouched because the nav sits on it. */
.hero-scrim{background:
  linear-gradient(100deg,
    rgba(9,15,28,.90) 0%,
    rgba(9,15,28,.74) 30%,
    rgba(9,15,28,.12) 52%,
    rgba(9,15,28,.05) 68%),
  linear-gradient(180deg,
    rgba(9,15,28,.34) 0%,
    rgba(9,15,28,.05) 18%,
    rgba(9,15,28,.05) 72%,
    rgba(9,15,28,.46) 100%)}


/* The photograph goes up as shot — no lift, no saturation, no
   contrast. The aisle is meant to be dark. */
.bgshot.px-room{filter:none}
.bgshot.px-friends{filter:brightness(.94) saturate(1)}

/* ══════════════════════════════════════════════════════════
   TRUST SECTION — hierarchy pass.
   The stats, the chips and the three cards were three
   full-width bands of identical weight. Nothing led, so
   nothing landed. One focal point; the rest steps back.
   ══════════════════════════════════════════════════════════ */

/* stats: no box grid. One hairline, the label above the number,
   and the carrier count given the room to be the lead — it is
   the claim the whole section rests on. */
.counts{grid-template-columns:1.4fr 1fr 1fr 1fr;
  gap:var(--sp3);background:none;
  border-top:1px solid var(--line);border-bottom:0;
  padding-top:var(--sp3)}
.ct{background:none;padding:0;display:flex;flex-direction:column;gap:9px}
/* the label now reads as the first half of a sentence the number
   finishes, so it comes first in the markup too. */
.ct .n{line-height:.92}
.ct .l{margin-top:0}
.ct:first-child .n{font-size:var(--fs7)}
@media(max-width:760px){
  .counts{grid-template-columns:1fr 1fr;row-gap:var(--sp2)}
  .ct:first-child .n{font-size:var(--fs6)}
}
/* latin caps survive 11px; Han does not, and bolding it only
   thickens the blur. Bigger and lighter reads as smaller. */
:is(html[lang^="zh"],html[lang^="ja"]) .ct .l{font-size:12.5px;font-weight:500;
  letter-spacing:.02em;line-height:1.7}

/* the stat numbers were set in IBM Plex Mono, whose dotted zero is a
   code-editor feature — at 72px it reads as a glitch, and monospaced
   advance widths leave 1 sitting in the same box as 0. Inter instead,
   with tabular figures so the count-up animation does not shuffle the
   row while the digits change width. Mono stays where it belongs, on
   the labels and the price table. */
.ct .n{font-family:var(--display);font-weight:600;
  letter-spacing:-.035em;font-variant-numeric:tabular-nums;
  font-feature-settings:"tnum" 1}
.ct .n em{font-weight:500;letter-spacing:-.02em}

/* ── common situations: six cards, text on the one you point at ──
   The cards sit above the stats, so the section opens with a
   picture of the problem and closes with the size of it. */
section#trust{padding-top:var(--sp5)}
.uses-grid{display:grid;grid-template-columns:repeat(6,1fr);
  gap:var(--sp1);list-style:none;margin:0;padding:0}
/* the dim state hangs off .armed, which the script adds only when it
   is actually going to run — so a failure leaves every card visible
   rather than every card at 14%. */
.use{min-width:0;transition:opacity .5s var(--e),transform .7s var(--out)}
/* placeholder: swap for a real photo by setting background-image
   on .ushot and dropping the data-ph attribute. */
.ushot{aspect-ratio:3/4;border-radius:var(--r-md);position:relative;
  overflow:hidden;isolation:isolate;display:flex;align-items:flex-end;
  background-size:cover;background-position:center;
  background-color:#ECEDEF;
  background-image:linear-gradient(150deg,#FEF8EB,#ECEDEF 55%,#CBCED4);
  box-shadow:var(--sh-hair)}
/* the caption sits on the photo, so it needs a scrim of its own —
   a photo cannot be trusted to be dark where the text lands. */
.ushot::before{content:"";position:absolute;inset:0;pointer-events:none;
  background:linear-gradient(180deg,
    rgba(11,18,32,0) 30%,rgba(11,18,32,.42) 62%,rgba(11,18,32,.8) 100%);
  opacity:.7;transition:opacity .45s var(--e)}
.use.is-on .ushot::before,.use:hover .ushot::before{opacity:1}

/* The title always shows — a card that says nothing until you point
   at it is unreadable on a phone, where there is no pointer. Only the
   sentence underneath is held back. 0fr to 1fr animates the row
   height without needing a hard-coded max-height. */
.ucap{position:relative;z-index:1;padding:var(--sp1);
  display:grid;grid-template-rows:auto 0fr;
  transition:grid-template-rows .5s var(--e)}
.use.is-on .ucap,.use:hover .ucap,.use:focus-within .ucap{grid-template-rows:auto 1fr}
.ucap h3{margin:0;color:#fff;font-size:var(--fs2);
  letter-spacing:-.02em;line-height:1.4;text-wrap:balance}
.ucap p{margin:0;overflow:hidden;opacity:0;
  font-size:12.5px;line-height:1.65;color:rgba(255,255,255,.84);
  transition:opacity .35s var(--e)}
.use.is-on .ucap p,.use:hover .ucap p,.use:focus-within .ucap p{opacity:1;padding-top:7px}
:is(html[lang^="zh"],html[lang^="ja"]) .ucap p{line-height:1.8}
/* placeholder marker stays clear of the caption */
.ushot[data-ph]::after{content:attr(data-ph);
  position:absolute;left:12px;top:10px;z-index:1;
  font-family:var(--mono);font-size:10.5px;letter-spacing:.14em;
  color:rgba(20,33,61,.32)}

@media(max-width:1100px){.uses-grid{grid-template-columns:repeat(3,1fr);
  gap:var(--sp1)}}
@media(max-width:600px){.uses-grid{grid-template-columns:repeat(2,1fr)}
}
/* no pointer means no hover: show everything and drop the hint */
/* if GSAP never loads, the spotlight never runs — so show everything */
.no-gsap .ucap{grid-template-rows:auto 1fr}
.no-gsap .ucap p{opacity:1;padding-top:7px}
.no-gsap .uses-grid.armed .use{opacity:1;transform:none}
@media(hover:none){
  .ucap{grid-template-rows:auto 1fr}
  .ucap p{opacity:1;padding-top:7px}
}

/* ── nav: links centred on the bar, not on the leftover space ──
   brand and langbox have very different widths, so a pair of auto
   margins pushes the links well left of centre. Take them out of
   the flow and pin them to 50% instead. Below 1080px the links
   are already hidden, so this only applies where they exist. */
@media(min-width:1081px){
  .cap{position:relative}
  .nav-links{position:absolute;left:50%;transform:translateX(-50%);
    margin:0;white-space:nowrap}
}
/* the bar is fixed, so an anchor would otherwise land underneath it */
section[id],.anchor,header[id]{scroll-margin-top:clamp(88px,9vw,112px)}

/* ── closing ring: six shots on the points of a hexagon ──
   Six is not arbitrary here — it is the honeycomb the mark is built
   from. Each shot is placed by rotating out to a radius and rotating
   back, so the picture stays upright; --t then tilts it a few degrees
   so the ring reads as scattered rather than machined. On a phone a
   ring of six is unreadable, so it unwinds into a plain grid. */
.ring{background:var(--hive);color:#fff;overflow:hidden;
  padding:var(--sp5) 0}
.ring-stage{position:relative;aspect-ratio:1/1;
  width:min(1080px,94vw);margin:0 auto}
.ring-shot{position:absolute;left:50%;top:50%;
  width:clamp(148px,17vw,246px);aspect-ratio:4/3;
  border-radius:var(--r-md);overflow:hidden;
  background-size:cover;background-position:center;background-color:#14213D;
  background-image:linear-gradient(150deg,#646C7F,#14213D 58%,#101A30);
  box-shadow:0 22px 60px rgba(6,11,22,.55),
             inset 0 0 0 1px rgba(255,255,255,.09);
  transform:translate(-50%,-50%)
            rotate(var(--a)) translateY(calc(var(--r,32%) * -1))
            rotate(calc(var(--a) * -1)) rotate(var(--t,0deg))}
.ring-stage{--r:clamp(200px,25vw,360px)}
.ring-shot[data-ph]::after{content:attr(data-ph);position:absolute;
  left:12px;top:10px;font-family:var(--mono);font-size:10.5px;
  letter-spacing:.14em;color:rgba(255,255,255,.34)}
.ring-copy{position:absolute;left:50%;top:50%;transform:translate(-50%,-50%);
  width:min(430px,46%);text-align:center;z-index:2}

.ring-copy h2{margin-top:0;font-size:var(--fs6);
  letter-spacing:-.035em;line-height:1.15;color:#fff}
.ring-copy .btn{margin-top:26px}
@media(max-width:900px){
  .ring-stage{aspect-ratio:auto;display:grid;
    grid-template-columns:repeat(3,1fr);gap:10px}
  .ring-copy{position:static;transform:none;width:auto;
    grid-column:1/-1;order:-1;margin-bottom:30px}
  .ring-shot{position:static;width:auto;transform:none;
    box-shadow:var(--sh-dark)}
}

/* ── entrance: masked rise for text, wipe for images ──
   Both offsets sit behind .armed, which the script only adds when it
   is going to run them, so nothing is left hidden if it never does. */
/* headings arrive a line at a time, sliding up out of the mask that
   SplitText wraps around each line. 105% rather than 100% so the
   descenders clear the mask edge before they become visible. The
   per-line delay is written inline by onSplit, so the whole cascade
   is defined in one place and survives a re-split on resize. */
.split .sl{transition:transform .78s var(--out),opacity .5s var(--e),
  filter .6s var(--e)}
.split.armed .sl{transform:translateY(105%);opacity:0;filter:blur(5px)}
.split.armed.is-in .sl{transform:none;opacity:1;filter:blur(0)}
.no-gsap .split.armed .sl{transform:none;opacity:1;filter:none}
.wipe{transition:clip-path 1s var(--out)}
.wipe.armed{clip-path:inset(0 100% 0 0)}
.wipe.armed.is-in{clip-path:inset(0 0 0 0)}
.no-gsap .wipe.armed{clip-path:none;transform:none;opacity:1}
@media(prefers-reduced-motion:reduce){
  .split.armed .sl,.wipe.armed{clip-path:none;transform:none;opacity:1;
    transition-delay:0s}
}

/* the table values were left in IBM Plex Mono on the argument that a
   comparison needs the column alignment monospace gives for free. It
   does — but tabular-nums gives the same fixed advance width without
   the dotted zero, which is a code-editor feature and reads as a
   defect at $8.50. Same fix as the stat row above. */
.cmp .val{font-family:var(--display);font-weight:500;letter-spacing:-.02em;
  font-variant-numeric:tabular-nums;font-feature-settings:"tnum" 1}
.cmp .us .val{font-weight:600}

/* ── nav over the hero photo ──
   The links were #CBCED4 and the language pill a 7% white wash, both
   picked for a dark field. The hero photo is bright at the top right,
   where the scrim has already faded to nothing, so neither survived.
   Links go white; the pill becomes actual frosted glass — a blur of
   whatever is behind it plus a thin white edge, which holds up over a
   light photo and a dark one without changing value. */
.nav-links a{color:#fff}
.nav-links a:hover{color:var(--honey)}
.lang-btn{background:rgba(255,255,255,.16);color:#fff;
  box-shadow:inset 0 0 0 1px rgba(255,255,255,.24);
  backdrop-filter:blur(16px) saturate(150%);
  -webkit-backdrop-filter:blur(16px) saturate(150%);
  transition:background .25s var(--e),color .25s var(--e),
             box-shadow .25s var(--e)}
.lang-btn:hover{background:rgba(255,255,255,.26);color:#fff}
.lang-btn svg{opacity:1}
/* the white capsule takes over on scroll: no glass, no shadow */
.nav.stuck .nav-links a{color:var(--body);text-shadow:none}
.nav.stuck .nav-links a:hover{color:var(--navy)}
.nav.stuck .lang-btn{background:var(--sunk);color:var(--body);box-shadow:none;
  backdrop-filter:none;-webkit-backdrop-filter:none}
.nav.stuck .lang-btn:hover{background:#ECEDEF;color:var(--navy)}

/* ── logo sizing after the move to vector ──
   A percentage margin resolves against the container's WIDTH, not its
   height, so -4% of a 1400px block was 56px — a quarter of the 221px
   logo, sliced straight through the letters. Fixed units instead.
   And the mark is three overlapping hexagons: at 21px tall they merge
   into a blob, so the nav gets a few more pixels. */
.cap .brand img{height:24px}

/* the open rate endpoint is free on condition of attribution */
.fx-src{color:inherit;opacity:.72;text-decoration:underline;
  text-underline-offset:3px;transition:opacity .2s var(--e)}
.fx-src:hover{opacity:1}

/* ── currency picker ──
   Sits beside the language pill and borrows its shell. It carries no
   globe: two icons side by side would read as one control. */
.lang.cur .lang-btn{gap:6px}
.cur-sym{font-family:var(--mono);opacity:.7}
#curNow{letter-spacing:.02em}
.cur-menu-note{padding:11px 14px 12px;font-size:11px;line-height:1.6;
  color:var(--dim);border-bottom:1px solid var(--line);margin-bottom:4px;
  max-width:210px}
.nav.stuck .cur-menu-note{color:var(--slate)}
@media(max-width:900px){.lang.cur{display:none}}

/* ── FAQ topic filter ──
   Same pill shell as the catalogue tabs, recoloured for the navy
   field. Filtering hides rows rather than reordering them, so an
   answer someone already opened stays open when they switch back. */
.faq-tabs{display:inline-flex;gap:3px;align-items:center;
  background:rgba(255,255,255,.07);border-radius:var(--r-pill);padding:4px;
  margin:0 0 var(--sp2)}
.faq-tabs button{padding:9px 18px;border-radius:var(--r-pill);white-space:nowrap;
  font-family:var(--display);font-size:13.5px;font-weight:600;letter-spacing:-.015em;
  color:#9CA2AE;line-height:1.3;
  transition:background .3s var(--e),color .3s var(--e)}
.faq-tabs button:hover{color:#fff}
.faq-tabs button[aria-selected="true"]{background:var(--honey);color:var(--navy)}
.faq-list[data-filter="num"]  .qa:not([data-topic~="num"]),
.faq-list[data-filter="esim"] .qa:not([data-topic~="esim"]){display:none}

/* entrance: the row slides in from the right, each card starting a
   little further out than the one after it, so they land left to
   right instead of all at once. body already clips overflow-x. */
.uses-grid.armed .use{opacity:0;transform:translateX(var(--in,60px));
  filter:blur(5px)}
.uses-grid.armed .use.is-in{filter:blur(0)}
.uses-grid.armed .use:nth-child(1){--in:118px}
.uses-grid.armed .use:nth-child(2){--in:104px}
.uses-grid.armed .use:nth-child(3){--in: 90px}
.uses-grid.armed .use:nth-child(4){--in: 76px}
.uses-grid.armed .use:nth-child(5){--in: 62px}
.uses-grid.armed .use:nth-child(6){--in: 48px}
.uses-grid.armed .use.is-in{opacity:1;transform:none}

/* ── the section rises over the hero instead of cutting across it ──
   It used to arrive as a flat horizontal edge. Here it lies back and
   comes upright as it covers, so its top edge is briefly narrower
   than its bottom — that trapezoid is the whole effect, and it only
   exists under perspective. A translate can never produce it: moving
   a rectangle keeps it a rectangle.

   transform-origin is the top edge, so the panel hinges up from
   where it meets the hero rather than pivoting about its middle and
   pushing its own bottom off screen. The rounded corners flatten on
   the way in, which is what makes it read as a panel settling into
   the page rather than a card that happens to be tilted. */
/* The pivot sits 820px BELOW the top edge, not on it. With the origin
   on the top edge — which is what this had — the visible seam is the
   one line that cannot move, so the tilt ran entirely off-screen and
   the edge stayed dead straight. A fixed px origin rather than 100%
   because the section is thousands of pixels tall and a percentage
   would make the angle depend on how much content is in it. */
/* the pivot the tilt used is no longer needed; the curve has no origin
   to set. Left as a note rather than a rule so the history is legible. */
@media(max-width:900px){
  /* the hero is not pinned here, so there is nothing to rise over */
  #trust{transform:none!important;border-radius:0!important}
}
@media(prefers-reduced-motion:reduce){
  #trust{transform:none!important;border-radius:0!important}
}

/* the pool holds ten destinations; six show at a time, and which six
   depends on the language. Hidden rather than removed so switching
   language is instant and nothing has to be rebuilt. */
.crow.dst[hidden]{display:none}

/* ── hero, to the mock ──
   Three differences from what was here, all in the same direction:
   the photo carries more of the frame and the overlays stop
   apologising for sitting on it.

   1. The pills were a 12% white wash at 12.5px — a tint on a tint,
      which disappears over a bright sky. Dark glass instead: they
      read against a pale photo and a dark one without changing value,
      which a light tint cannot do.
   2. Bigger, because in the mock they are a third voice in the hero,
      not a footnote.
   3. The left scrim eases off. It was built when the panels were
      darker; at .90 it was flattening the picture into a backdrop.
      Not removed though — see the note below. */
.tick{margin:0 0 10px;padding:11px 20px;font-size:14.5px;font-weight:600;
  letter-spacing:.01em;color:#fff;
  background:rgba(16,26,46,.62);
  backdrop-filter:blur(10px) saturate(140%);
  -webkit-backdrop-filter:blur(10px) saturate(140%);
  box-shadow:inset 0 0 0 1px rgba(255,255,255,.10)}
:is(html[lang^="zh"],html[lang^="ja"]) .tick{font-size:13.5px;letter-spacing:.02em}
.ticks{width:min(360px,36vw);height:184px}

/* The picture is the argument on this page — "real telecom
   infrastructure" is carried by the photograph as much as the copy —
   so the veil over it comes down. It does not come off: the headline
   is white, the photos change on a timer, and one bright frame with
   no scrim would strand the text. .72 still guarantees contrast on
   the worst of the four. */
.hero-scrim{background:
  linear-gradient(100deg,
    rgba(9,15,28,.72) 0%,
    rgba(9,15,28,.56) 30%,
    rgba(9,15,28,.10) 54%,
    rgba(9,15,28,.04) 70%),
  linear-gradient(180deg,
    rgba(9,15,28,.30) 0%,
    rgba(9,15,28,.04) 18%,
    rgba(9,15,28,.04) 70%,
    rgba(9,15,28,.42) 100%)}

/* ── hero copy ──
   The max-width on the headline was not what was holding it to three
   lines; the column was. At a 1.42:1 split the left column measured
   704px, and "wherever you need one." needs about 731px at 64px. Off
   by 27 pixels, which is enough to push one word onto its own line —
   and a heading that breaks early looks smaller than one the same
   size that does not. Widened to 1.9:1, which gives 786px.

   The paragraph was #9CA2AE, a slate grey chosen for text on a navy
   panel. Over a photograph it is the dimmest thing in the frame. */
/* .hero .wrap: folded into .wrap */
@media(min-width:901px){
  .hero-grid{grid-template-columns:minmax(0,1.9fr) minmax(0,1fr);
    align-items:center}
}
.hero h1{max-width:20ch}
/* ch is the width of "0" — about .55em in Inter — so 15ch was barely
   eight Han glyphs and the second line broke after nine. A Chinese
   character is 1em wide, so the measure has to be written in em or it
   means nothing here. The longest line is 都有一個屬於你的號碼。 at
   12 glyphs; 13em holds it with a character to spare, and the size is
   capped at 58px so 13em stays inside the 786px column. */
:is(html[lang^="zh"],html[lang^="ja"]) .hero h1{max-width:13em;
  font-size:clamp(30px,4.4vw,58px);line-height:1.28}
.hero .hp p{color:rgba(255,255,255,.92);font-size:clamp(17px,1.4vw,20px);
  line-height:1.7;max-width:48ch;margin-top:22px}
:is(html[lang^="zh"],html[lang^="ja"]) .hero .hp p{font-size:clamp(16px,1.25vw,18.5px);
  line-height:1.9;max-width:32ch}

/* the buttons carry the same weight as the rest of the block */
.hero .hero-cta{margin-top:clamp(28px,3vw,40px)}
.hero .hero-cta .btn{padding:15px 28px;font-size:15.5px}

/* the carrier strip lies over the photograph rather than sealing it
   off with a solid bar */
.hero .band,.band.on-hero{background:rgba(11,18,32,.42);color:#fff;
  backdrop-filter:blur(14px) saturate(130%);
  -webkit-backdrop-filter:blur(14px) saturate(130%)}

/* ── the pills once the nav has gone white ──
   These were filled with --sunk, the recessed tone from the cream
   page. That tone is warm on purpose, and it works on the cream — but
   the stuck capsule is pure white, and a warm beige on white reads as
   dirty rather than as a surface. The whole capsule already separates
   the nav from the page, so the controls inside it do not need a fill
   of their own: a hairline is enough to say "this is a control", and
   the fill arrives on hover, where it means something. */
.nav.stuck .lang-btn{background:transparent;color:var(--body);
  box-shadow:inset 0 0 0 1px rgba(20,33,61,.15)}
.nav.stuck .lang-btn:hover{background:rgba(20,33,61,.05);color:var(--navy);
  box-shadow:inset 0 0 0 1px rgba(20,33,61,.24)}
.nav.stuck .lang-btn[aria-expanded="true"]{background:rgba(20,33,61,.06)}

/* ── the hero pills: rolling, and actually frosted ──
   The frost was in the CSS all along and never rendered, because of
   the fade mask on the container. mask-image establishes a backdrop
   root, and backdrop-filter can only sample inside its own backdrop
   root — the photograph sits outside it, so the blur was sampling
   nothing. will-change:transform on the track does the same thing in
   Chrome. So frosted glass and a gradient fade cannot both be here;
   the mask goes and overflow:hidden does the clipping instead, which
   creates no backdrop root.

   The fill also had to come down. At 66% opaque there is almost
   nothing left for the blur to show through — frosted glass reads
   because you can see the shapes behind it moving, and that needs the
   surface to be genuinely transparent. */
.ticks{height:184px;overflow:hidden;
  -webkit-mask-image:none;mask-image:none}
.ticks-track{will-change:auto;gap:0}
.ticks-track .tick:nth-child(n+4){display:block}
.tick{margin:0 0 10px;padding:12px 22px;font-size:15px;font-weight:600;
  letter-spacing:.01em;color:#fff;
  background:rgba(16,26,46,.38);
  backdrop-filter:blur(14px) saturate(150%);
  -webkit-backdrop-filter:blur(14px) saturate(150%);
  box-shadow:inset 0 0 0 1px rgba(255,255,255,.16)}
:is(html[lang^="zh"],html[lang^="ja"]) .tick{font-size:14px;letter-spacing:.02em}

/* ── the new hero photograph, unveiled ──
   The dark wash across the left is gone. It was there because the old
   panel was a dim server room and white text needed a floor to stand
   on; over a sky it just makes the picture look overcast, which is
   the opposite of what the photograph was chosen for.

   Contrast now comes from the type itself rather than from dimming
   everything behind it — a soft, wide shadow under the headline and
   the paragraph. A shadow costs nothing where the background is
   already dark and only shows up where it is needed, which a flat
   gradient cannot do.

   What is left is a thin band at the very top and bottom. The nav is
   white text sitting directly on the photo with no capsule until you
   scroll, and the carrier strip has to separate from whatever is
   behind it — those two need a floor. The middle does not. */
/* The brightness(.9) here was doing the contrast work back when the
   headline had no shadow — the sky measures 161/255 where the type
   sits and white on that is only 2.58:1. The navy text-shadow now
   takes that job and gets to 4.97:1 on the untouched photograph, so
   the dimming comes off and the sky is the brightness it was shot at.
   Saturation stays up a little: it flatters the blue and costs no
   contrast. */
.bgshot.px-hero{filter:brightness(1) saturate(1.08)}
/* The second panel is a lamp-lit interior: 40/255 across the left half
   where the copy sits, so it needs lifting, not dimming. Saturation
   stays near neutral — the scene already carries a heavy amber cast
   and a normal boost just turns it orange. */
.bgshot.px-home{filter:brightness(1.1) saturate(1.02) contrast(1.02)}
/* The top band is gone too. The only thing that needed it was the nav
   — white text sitting straight on the photo before the capsule
   appears — so that moves to a shadow on the nav itself, which shows
   up only where the sky behind it is pale. The bottom stays: the
   carrier strip is a solid element and needs an edge to sit against,
   not legibility help. */
.hero-scrim{background:
  linear-gradient(180deg,
    rgba(9,15,28,0)   0%,
    rgba(9,15,28,0)   76%,
    rgba(9,15,28,.28) 100%)}
/* ── shadows only where the type is thin or small ──
   The headline is 58px at weight 700 — it holds its own against the
   sky and the shadow there is for shape, not rescue. The badge is
   12px, which does need help. Everything else comes off: the
   paragraph, the nav, the carrier strip. A shadow under every piece
   of text is not contrast, it is a haze over the whole photograph,
   and it was undoing the point of taking the scrim away. */
/* The headline and the paragraph get a navy shadow at 40%. The sky in
   this frame measures 161/255 across the left half, which puts white
   type at 2.58:1 — under the 3:1 large text needs — so something had
   to give, and a shadow tinted with the brand navy rather than black
   keeps the sky reading as sky instead of smudged.

   Only those two. The nav, the badge and the carrier strip stay
   clean: they each sit on their own surface or are small enough that
   a shadow reads as blur rather than as contrast. */
.hero h1,.hero h2{text-shadow:0 2px 18px rgba(20,33,61,.4),
                              0 1px 3px rgba(20,33,61,.4)}
.hero .hp p{text-shadow:0 1px 14px rgba(20,33,61,.4),
                        0 1px 2px rgba(20,33,61,.4)}

/* Same navy at the same 40% on everything else over the photograph.
   The spread is not the same, though: it scales with the type. A
   18px bloom under 12px text swamps the letterforms and reads as
   blur, not as contrast — so the small stuff gets a tight halo and
   the tick pills, which already sit on frosted glass, get the least
   of all. */
.hero .pill,.hero .hpk{text-shadow:0 1px 8px rgba(20,33,61,.4),
                                   0 1px 2px rgba(20,33,61,.4)}
.nav:not(.stuck) .nav-links a,
.nav:not(.stuck) .brand{text-shadow:0 1px 10px rgba(20,33,61,.4),
                                    0 1px 2px rgba(20,33,61,.4)}
.marqLab,.marqLab b,.marqLab i,
.it{text-shadow:0 1px 6px rgba(20,33,61,.4)}
.tick{text-shadow:0 1px 4px rgba(20,33,61,.4)}

/* white capsule underneath once it sticks — a shadow there is dirt */
.nav.stuck .nav-links a,.nav.stuck .brand{text-shadow:none}

/* ── where the pill stack sits ──
   It was pinned with right: clamp(18px,3vw,44px) — that is the
   viewport edge, so on a wide screen it drifted further and further
   from the content it belongs to. Anchored to the container instead:
   the stack's right edge now lines up with the right edge of .wrap,
   the same line the nav and the copy are measured against.

   Two knobs to move it from there. Positive --tick-x goes right,
   positive --tick-y goes up.

   Deliberately NOT done with transform: a transformed ancestor stops
   backdrop-filter sampling the photograph in Chrome, and the frost on
   these pills is the whole point. margin does the same job with no
   side effect. */
.ticks{
  --tick-w: min(360px, 36vw);
  --tick-x: 0px;      /* → right  |  negative → left  */
  --tick-y: 0px;      /* → up     |  negative → down  */
  width:var(--tick-w);
  right:auto;
  left:50%;
  margin-left:calc(min(1400px, 100vw - 48px) / 2 - var(--tick-w) + var(--tick-x));
  bottom:calc(clamp(56px,7vh,72px) + 34px + var(--tick-y));
}

/* ── the hero badge ──
   The label was #9CA2AE — grey-blue, chosen for a navy panel. Over a
   sky it reads as switched off. English hid it: uppercase mono at
   .09em tracking is airy enough to look deliberate at any weight.
   Chinese has no uppercase and no tracking to spare, so the same
   colour just looks dim. White, and let the border do the softening.

   The dot only blinked. Now it glows: two shadows, a tight one for
   the bloom right at the edge and a wide one for the halo, both in
   the honey so the light has a colour rather than being a grey
   smudge. The blink drives the glow as well, so the dot pulses
   instead of flickering. */
.hero .pill{color:#fff;border-color:rgba(255,255,255,.42);
  background:rgba(255,255,255,.06);
  backdrop-filter:blur(8px);-webkit-backdrop-filter:blur(8px)}
:is(html[lang^="zh"],html[lang^="ja"]) .hero .pill{letter-spacing:.06em;font-weight:600}

.hero .pill::before{width:8px;height:8px;
  box-shadow:0 0 6px 1px rgba(245,184,0,.95),
             0 0 16px 4px rgba(245,184,0,.55);
  animation:dotGlow 2.4s ease-in-out infinite}
@keyframes dotGlow{
  0%,100%{opacity:1;
    box-shadow:0 0 6px 1px rgba(245,184,0,.95),
               0 0 16px 4px rgba(245,184,0,.55)}
  50%    {opacity:.72;
    box-shadow:0 0 3px 0 rgba(245,184,0,.6),
               0 0 9px 2px rgba(245,184,0,.28)}
}
@media(prefers-reduced-motion:reduce){
  .hero .pill::before{animation:none}
}

/* ── the headline goes Black ──
   900 had to be added to the font request first. Without the file the
   browser fakes it by smearing the 700 outline, which thickens the
   stems unevenly and fills the counters — the difference shows worst
   at exactly the size a hero headline runs at.

   Black needs its tracking pulled in further than Bold: heavier
   strokes leave less white between letters, so the same -.04em that
   looks right at 700 looks loose at 900. Chinese keeps its own value
   as always — the glyphs already fill the em box. */
h1{font-weight:900;letter-spacing:-.045em}
:is(html[lang^="zh"],html[lang^="ja"]) h1{font-weight:900;letter-spacing:-.01em}

/* ══ proportion, after the values were consolidated ══
   These are the reference's own numbers, which are far more restrained
   than they look: -0.13rem on a 6.5rem hero is -2%, and -0.0375rem on
   a 3.75rem heading is -1%. The counterpart, and the part usually
   missed, is that their small text gets POSITIVE tracking — +1.5% on
   12px footnotes. Tighten the large, loosen the small.

   Applied only to Latin. A Han glyph already fills its em box, so
   negative tracking collides the strokes; CJK gets its own line.
   Three radii instead of five, on the same principle as the values
   above: the gap between a small radius and a large one is what reads
   as considered, a spread of five just reads as inconsistent. */
:root{--r-sm:8px; --r-md:16px; --r-lg:24px}

html[lang="en"] h1,html[lang^="fil"] h1,html[lang^="tl"] h1{letter-spacing:-.02em;line-height:1.02}
html[lang="en"] h2,html[lang^="fil"] h2,html[lang^="tl"] h2{letter-spacing:-.011em;line-height:1.04}
:is(html[lang^="zh"],html[lang^="ja"]) h1,:is(html[lang^="zh"],html[lang^="ja"]) h2{letter-spacing:-.004em;line-height:1.2}
.cmp-note,.plan-note,.fine,.ct .l,.f-btm,.cmp-more{letter-spacing:.015em}

/* ── comparison on white ──
   The page is cream and the table was white, which is what separated
   them. On a white band that difference is gone, so the table has to
   be held by its edge instead: a real hairline rather than the 5%
   ghost, and a slightly deeper ambient shadow. */
section#compare{background:#fff;
  padding:var(--sp3) 0 var(--sp4)}
section#compare .cmp{box-shadow:0 0 0 1px rgba(20,33,61,.09),
  0 10px 34px rgba(20,33,61,.07)}
section#compare .cmp thead th{background:var(--raise)}
section#compare .cmp thead th:first-child{background:var(--raise)}
/* overflow-x:auto makes overflow-y compute to auto too, which was
   drawing a vertical scrollbar down the side of a table that does
   not scroll vertically */
.cmp{overflow-y:hidden}

/* ── FAQ on navy ──
   Everything inside was coloured for the cream page: navy questions,
   a cream hairline, dim grey answers. On a dark field all three
   invert, and the sticky card can no longer be navy-on-navy, so it
   lifts to a lighter surface with a hairline of its own. */
section#faq{background:var(--hive);color:#fff;
  padding:var(--sp5) 0 0}
/* the heading lives in the question column rather than centred over
   the whole section: it names the list, not the support card beside
   it, and left-aligned it starts on the same line the questions do. */
.faq-title{color:#fff;margin:0 0 var(--sp3);
  font-size:var(--fs7);letter-spacing:-.04em}
/* the photo used to sit on top of the card, so the first thing the
   column said was a picture of nobody in particular. Card first, with
   the question and the button, then the photo as its own block. */
.faq-side{position:sticky;top:110px;display:grid;
  gap:var(--sp2);align-content:start}
.faq-side .thumb{margin-bottom:0}
@media(max-width:880px){.faq-side{position:static}}
section#faq .qa{border-bottom-color:rgba(255,255,255,.13)}
section#faq .qa:first-child{border-top-color:rgba(255,255,255,.13)}
section#faq .qa .q{color:#fff}
section#faq .qa .q:hover{color:var(--honey)}
section#faq .qa .ic::before,section#faq .qa .ic::after{background:var(--honey)}
section#faq .qa .a p{color:#9CA2AE}
/* a warning inside an answer has to read as one: the body copy is
   deliberately muted, so weight alone barely registers against it */
section#faq .qa .a p b{font-weight:700;color:#DDE2EA}
/* the support card was navy on cream — on navy it needs to separate */
section#faq .faq-card{background:rgba(255,255,255,.06);
  box-shadow:inset 0 0 0 1px rgba(255,255,255,.12)}
section#faq .faq-card p{color:#9CA2AE}

/* ══ hero photo framing ══
   Every offset here is a percentage, and background-repeat is off.

   They used to be pixels: 20px up on all of them, 120px on the server
   room, 266px on the Paris shot. With background-size:cover the image is
   scaled to just cover the box, which on a 16:9 stage leaves these files
   between 0 and 12px of vertical slack — so a 266px shift pushed the
   image clean off its own bottom edge and the default background-repeat
   tiled the sky back in underneath. On a 900px-tall window the exposed
   strip happened to be plain blue and nobody noticed; on a shorter one
   it is a flat band across the page.

   A percentage cannot do that: with cover, 0% to 100% only ever slides
   the image within whatever slack exists, and the box stays covered. The
   framing that the pixels were reaching for is done by scaling the layer
   instead, which .bgstage clips. */
.bgstage .px{background-position:50% 44%;background-repeat:no-repeat}
/* The Paris frame is shot wide — the group sits in the right third and
   most of the left is sky and trees. Scaling the layer up crops in on
   the subjects while keeping background-size:cover, so the aspect ratio
   is untouched at any viewport. The resting scale is what changes; the
   entrance still starts a step above it, so the push-in on arrival is
   the same movement it always was. .bgstage clips the overflow. */
/* Another 50px left, as seen on screen. The numbers here
   are smaller than that because this layer is scaled 1.22 — a
   background-position offset is scaled along with everything else, so
   100px of CSS would land as 122px in the frame. The running total on
   screen is 300px up and 20px left; divided by 1.22 that is 246 and
   66, plus the 20px the whole stage already carries vertically. */
/* Back to the layer scale this always had. The 1.46 that replaced it was
   me over-correcting: the flat band was caused by the pixel offsets, not
   by the zoom, so there was never any reason to crop in further. On a
   tablet-shaped window the extra scale pushed the group past the frame.

   100% on the vertical is bottom alignment, which is where the old
   266px offset was trying to get to. As a percentage it lands exactly on
   the edge instead of past it, so the bottom of the picture meets the
   bottom of the frame at every window size and nothing is exposed. */
.bgstage .px-friends{background-position:56% 100%}
.bgstage .bgshot.px-friends.on{transform:scale(1.22)}
.bgstage .bgshot.px-friends{transform:scale(1.32)}
/* the server-room frame wants to sit higher; this one has no vertical
   slack at all under cover, so the lift is on the layer as well */
.bgstage .px-room{background-position:50% 50%}
.bgstage .bgshot.px-room.on{transform:scale(1.18) translateY(-5%)}
.bgstage .bgshot.px-room{transform:scale(1.26) translateY(-5%)}

/* panels 2-4 carry the same headline scale as panel 1 */
.hp h2{font-size:var(--fs7);line-height:1.1;letter-spacing:-.04em;max-width:18ch}
/* The Chinese hero h1 has its own size and measure further up, written in
   em because ch is the width of "0" and means nothing for full-width
   glyphs. That rule names h1 only, so panels 2-4 stayed on --fs6 and came
   out 44px against panel 1's 58px. Same treatment, same numbers. */
:is(html[lang^="zh"],html[lang^="ja"]) .hero .hp h2{max-width:13em;
  font-size:clamp(30px,4.4vw,58px);line-height:1.28}
:is(html[lang^="zh"],html[lang^="ja"]) .hp h2{font-size:var(--fs6);max-width:14ch}
html[lang="fil-PH"] .hp h2{font-size:var(--fs6);max-width:26ch}
/* Filipino runs about 40% longer than the English. With the 16ch cap the
   hard breaks landed inside each half and the headline went to four
   lines, so the cap has to clear the longer of the two halves. */
html[lang="fil-PH"] .hp h1{max-width:26ch}
@media(min-width:1200px){
  .hp[data-i="3"] h2{white-space:normal;max-width:18ch}
}

/* ══════════════════════════════════════════════════════════
   COMPARE TABLE: THREE COLUMNS ON A PHONE
   Five columns in a 326px viewport meant a 760px sideways scroller and
   a "swipe for the rest" note — the two hidden brands were, in
   practice, never seen. On a phone the table shows the label column,
   Bees Mobile, and one rival at a time; the rival header becomes a
   picker.

   The rival columns are marked data-rival 1-3 and the wrapper carries
   the active one, so the switch is a single attribute and no cell
   contents are moved or copied. Each of the three headers holds its own
   <select> — only the visible column's is on screen, so the control is
   always sitting in the column it controls. On desktop every column is
   back and the selects are hidden.
   ══════════════════════════════════════════════════════════ */
.rivalpick{display:none}
@media(max-width:820px){
  /* no scroller: the table now fits */
  .cmp table{min-width:0}
  .cmp-more{display:none}
  .cmp .rname{display:none}
  .cmp [data-rival]{display:none}
  .cmp[data-rival="1"] [data-rival="1"],
  .cmp[data-rival="2"] [data-rival="2"],
  .cmp[data-rival="3"] [data-rival="3"]{display:table-cell}
  .cmp .rivalpick{display:inline-block;max-width:100%;
    font-family:var(--display);font-size:14px;font-weight:700;
    letter-spacing:-.02em;color:#FFFFFF;
    background:rgba(255,255,255,.10);border:0;
    box-shadow:inset 0 0 0 1px rgba(255,255,255,.22);
    border-radius:var(--r-pill);padding:7px 26px 7px 12px;
    -webkit-appearance:none;appearance:none;cursor:pointer;
    background-image:url("data:image/svg+xml;charset=utf-8,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='%23F0A500' stroke-width='2.5' stroke-linecap='round'%3E%3Cpath d='M6 9l6 6 6-6'/%3E%3C/svg%3E");
    background-repeat:no-repeat;background-position:right 8px center;
    background-size:13px 13px}
  /* the native list renders on the OS surface, so its own colours have
     to be set or the options come out white-on-white */
  .cmp .rivalpick option{background:#101A30;color:#FFFFFF}
  .cmp th,.cmp td{padding:14px 10px}
  .cmp td:first-child{white-space:normal}
}

/* ══════════════════════════════════════════════════════════
   LINE BREAKING, HANDLED BY THE BROWSER
   Hand-placing a <br> per string means four strings to re-check every
   time a word changes, and it is wrong the moment the viewport is a
   size you did not test. Three properties do most of it:

   text-wrap:balance evens the lines of a heading, so a 2-line headline
   no longer leaves five words on top and one underneath. It is capped
   at a handful of lines by the spec, which is why it goes on headings
   and short labels, not body copy.

   text-wrap:pretty runs the paragraph case: it forbids a last line
   holding a single word and avoids breaking the same word repeatedly.

   word-break:auto-phrase is the one that matters for Chinese. CJK has
   no spaces, so by default a line can break between any two
   characters, splitting words in half. auto-phrase uses the browser's
   own dictionary to break at phrase boundaries instead. Chromium-only
   for now, and it degrades to the old behaviour everywhere else, so it
   costs nothing to ask for.
   ══════════════════════════════════════════════════════════ */
h1,h2,h3,h4,
.hp h1,.hp h2,.cmp-head h2,.faq-title,.ring-copy h2,
.badge,.tag,.hpk,.pill,.tick,.plan-head h3,.qa .q,.cname{
  text-wrap:balance}

p,.qa .a p,.f-tag,.cmp-note,.plan-note,.fine{
  text-wrap:pretty}

/* pretty only forbids a one-word last line; it will still split a
   phrase across the break, which is what "Public list / prices" was.
   Short intro paragraphs are two or three lines, inside balance's
   line cap, so they get the same even-lengths treatment as a heading
   and the break lands near the middle of the sentence instead. */
.hp p,.cmp-head p,.ring-copy p,.cta > .wrap > p,.plan-card > p{
  text-wrap:balance}

:is(html[lang^="zh"],html[lang^="ja"]) h1,:is(html[lang^="zh"],html[lang^="ja"]) h2,:is(html[lang^="zh"],html[lang^="ja"]) h3,
:is(html[lang^="zh"],html[lang^="ja"]) p,:is(html[lang^="zh"],html[lang^="ja"]) .qa .q,:is(html[lang^="zh"],html[lang^="ja"]) .tick{
  word-break:auto-phrase;line-break:strict}

/* the member price is the one figure on the page that only members
   see, so it is the one that carries the brand gold and the star. The
   star reuses the membership card's icon rather than a ★ glyph, which
   renders as a different shape on every platform and would have been
   read aloud by a screen reader. */
section#compare .cmp .memberprice .val{color:#F0A500}
/* The star marks the row, so it belongs on the row label. It has to be
   a ::before rather than an <svg> child: the language switch rewrites
   this cell with innerHTML from its data-* attributes, which would
   delete any element sitting inside it. A pseudo-element is not in the
   DOM the swap touches, so it survives. */
.cmp .mlabel::before{content:"";display:inline-block;
  width:14px;height:14px;margin-right:8px;vertical-align:-2px;
  background-color:#F0A500;
  -webkit-mask:var(--star) center/contain no-repeat;
          mask:var(--star) center/contain no-repeat}
:root{--star:url("data:image/svg+xml;charset=utf-8,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24'%3E%3Cpath fill='%23000' d='M12 2.6l2.95 5.98 6.6.96-4.77 4.65 1.13 6.57L12 17.66l-5.91 3.1 1.13-6.57L2.45 9.54l6.6-.96z'/%3E%3C/svg%3E")}

/* the plans eyebrow was a .tag — a mono rule-and-caps label — and now
   uses the same .badge pill as the data-pricing section. .badge is
   navy-on-navy by default, built for the cream page, so on a dark
   section it takes the same white wash the compare badge does. */
.cta .badge{background:rgba(255,255,255,.10);color:#FFFFFF;
  box-shadow:inset 0 0 0 1px rgba(255,255,255,.18)}

/* the data-pricing heading breaks at its comma and the whole block
   centres. h2 and p both carry a max-width in ch, so centring the text
   is not enough on its own — the boxes have to be centred too or they
   stay pinned left with centred text inside them. */
section#compare .cmp-head{text-align:center}
section#compare .cmp-head h2,
section#compare .cmp-head p{margin-left:auto;margin-right:auto}

/* ══════════════════════════════════════════════════════════
   LANGUAGE AND CURRENCY MENUS ON WHITE
   Both dropdowns shared one shell built for a dark panel: a 98% navy
   background, a 13% white border, a white-wash hover and white text.
   On white every one of those inverts. The scroll note above the
   currency list was reading var(--line) for its rule, which is now the
   same value as the menu it sits in, so it takes a real hairline.
   ══════════════════════════════════════════════════════════ */
.lang-menu{background:#FFFFFF;
  border-color:#CBCED4;
  box-shadow:0 18px 44px rgba(20,33,61,.18),
             0 2px 6px rgba(20,33,61,.08)}
.lang-menu button{color:#646C7F}
.lang-menu button:hover{background:#ECEDEF;color:#14213D}
.lang-menu button[aria-selected="true"]{color:#14213D}
.cur-menu-note{color:#646C7F;border-bottom-color:#CBCED4}
.nav.stuck .cur-menu-note{color:#646C7F}

/* ══════════════════════════════════════════════════════════
   BRAND PALETTE
   Every colour in the sheet is now one of the fifteen values below.
   Sixty-odd near-duplicates collapsed into them: eleven greys within a
   few percent of each other became four steps of the navy ramp, four
   creams became one, three golds became the ramp.

   Two rules govern the substitutions that were not one-to-one:

   Lifted surfaces on navy do not get their own hex. #14213D through
   #0B1222 are three fixed steps, so anything that needs to sit "just
   above" its background uses a white alpha wash instead of a new
   colour. The compare table is the exception — its first column is
   position:sticky and must be opaque, so it takes ramp steps outright.

   Gold on a light field is always #845B00. The brand gold is 2.2:1 on
   cream, which fails for text at any size; the ramp provides the dark
   end for exactly this.
   ══════════════════════════════════════════════════════════ */
:root,html,body{
  /* core */
  --hive:#14213D;   --navy:#14213D;   --honey:#F0A500;
  --void:#FAF7F0;   --cream:#FAF7F0;  --raise:#FFFFFF;
  /* navy ramp */
  --n1:#ECEDEF; --n2:#CBCED4; --n3:#9CA2AE; --n4:#646C7F;
  --n5:#14213D; --n6:#101A30; --n7:#0B1222;
  /* gold ramp */
  --g1:#FEF8EB; --g2:#FCEBC7; --g3:#F9D994; --g4:#F5C457;
  --g5:#F0A500; --g6:#BB8100; --g7:#845B00;
  --honey-lo:#845B00; --honey-soft:#FEF8EB;
  /* roles */
  --sunk:#ECEDEF;   --line:#ECEDEF;
  --body:#111827;   --dim:#646C7F;
}

/* the outlined button needs a border a step stronger than a hairline */
.b-line{border-color:#CBCED4}
/* photo placeholders: neutral, and flat rather than a three-stop
   gradient that would have needed three greys */
.ushot{background-color:#ECEDEF;background-image:none}
.wshot{background:#ECEDEF}
.ring-shot{background-color:#ECEDEF;background-image:none;
  box-shadow:0 18px 44px rgba(20,33,61,.13),
             inset 0 0 0 1px #CBCED4}
.ring-shot[data-ph]::after{color:#646C7F}

/* compare table: opaque steps, because the frozen column cannot be
   a translucent wash */
section#compare{background:#14213D}
section#compare .cmp{background:#101A30;
  box-shadow:inset 0 0 0 1px rgba(255,255,255,.10),
             0 18px 44px rgba(11,18,34,.45)}
section#compare .cmp thead th{background:#0B1222;color:#9CA2AE}
section#compare .cmp thead th:first-child{background:#0B1222}
section#compare .cmp thead th.us{background:#14213D;color:#FFFFFF;
  box-shadow:inset 0 3px 0 #F0A500}
section#compare .cmp tbody td:first-child{background:#101A30}
section#compare .cmp .us{background:#14213D}
section#compare .cmp .win{color:#F0A500}
section#compare .cmp .no{color:#646C7F}
section#compare .cmp th,
section#compare .cmp td{border-bottom-color:rgba(255,255,255,.09)}

/* ══════════════════════════════════════════════════════════
   CLOSING RING AND FOOTER ON WHITE
   Both were navy. Three things do not survive a straight background
   swap:

   The six ring tiles are placeholders — a dark blue gradient standing
   in until real photographs land. Six navy blocks on white read as
   holes, so the placeholder becomes a pale neutral. Once a real
   background-image goes on a .ring-shot it covers this anyway, so
   nothing here has to be undone later.

   The ghost wordmark at the foot is a white SVG. No amount of CSS
   colour reaches inside an <img>, and filter: invert() is off the
   table, so the fill in the SVG source is now navy. Its gradient mask
   was already written to survive a background change and needed
   nothing.

   The social buttons were outlined in 14% white, which is invisible
   here; they take a navy hairline instead.
   ══════════════════════════════════════════════════════════ */
.ring{background:#fff;color:var(--hive)}
.ring-copy h2{color:var(--hive)}
.ring-shot{background-color:#ECEDEF;
  background-image:linear-gradient(150deg,#ECEDEF,#ECEDEF 58%,#CBCED4);
  box-shadow:0 18px 44px rgba(20,33,61,.13),
             inset 0 0 0 1px rgba(20,33,61,.08)}
.ring-shot[data-ph]::after{color:rgba(20,33,61,.30)}

footer{background:#fff;color:var(--hive);
  border-top:1px solid rgba(20,33,61,.10)}
.f-tag,.f-grid a{color:#646C7F}
.f-grid a:hover{color:var(--hive)}
.f-grid h4{color:var(--honey-lo)}
.f-social a{color:#646C7F;box-shadow:inset 0 0 0 1px rgba(20,33,61,.14)}
.f-social a:hover{color:var(--navy);background:var(--honey);
  box-shadow:inset 0 0 0 1px var(--honey)}
.f-btm{color:#646C7F;border-top-color:rgba(20,33,61,.10)}
/* the wordmark runs at full strength. The fade at its foot is the
   gradient mask, not the opacity, so raising one leaves the other
   intact — but the mask now has to start further down and travel
   further, because at .17 the letters were faint everywhere and at 1
   the cut would read as a hard edge. */
.f-ghost .f-logo{opacity:1;
  -webkit-mask-image:linear-gradient(180deg,#000 18%,rgba(0,0,0,0) 92%);
          mask-image:linear-gradient(180deg,#000 18%,rgba(0,0,0,0) 92%)}

/* ══════════════════════════════════════════════════════════
   FAQ ON WHITE
   The block further up had flipped this section to navy and recoloured
   everything inside it for a dark field. That inversion is undone here
   rather than deleted, so the original dark-field values stay on record
   above and this reads as one decision in one place.

   The support card is the exception: it stays navy. It was navy on the
   original cream page, it is the only saturated surface in the column,
   and turning it white would leave a white card on a white section
   with nothing but a hairline holding it.
   ══════════════════════════════════════════════════════════ */
section#faq{background:#fff;color:var(--hive);
  padding:var(--sp5) 0 var(--sp5)}
.faq-title{color:var(--hive)}

section#faq .qa{border-bottom-color:rgba(20,33,61,.12)}
section#faq .qa:first-child{border-top-color:rgba(20,33,61,.12)}
section#faq .qa .q{color:var(--hive)}
section#faq .qa .q:hover{color:var(--honey-lo)}
/* the plus sign drops to honey-lo: full honey on white is 1.9:1 and
   the icon is a 2px stroke, so it disappears */
section#faq .qa .ic::before,
section#faq .qa .ic::after{background:var(--honey-lo)}
section#faq .qa .a p{color:#646C7F}
section#faq .qa .a p b{font-weight:700;color:#444E65}

section#faq .faq-tabs{background:rgba(20,33,61,.06)}
section#faq .faq-tabs button{color:#646C7F}
section#faq .faq-tabs button:hover{color:var(--hive)}
section#faq .faq-tabs button[aria-selected="true"]{
  background:var(--hive);color:#fff}

section#faq .faq-card{background:var(--hive);color:#fff;
  box-shadow:none}
section#faq .faq-card h3{color:#fff}
section#faq .faq-card p{color:#9CA2AE}

/* ══════════════════════════════════════════════════════════
   DATA PRICING ON NAVY
   The section was white, and everything inside it was coloured for a
   light field: navy figures, a cream hairline, a #FEF8EB wash on the
   Bees column. Flipping only the section background would have left a
   white table sitting on navy with grey-on-grey text inside it, so the
   whole block inverts the way #faq already does.

   Two things need care rather than a colour swap. The first column is
   position:sticky for the horizontal scroll, so it cannot be
   transparent — it has to be an opaque surface or the columns show
   through underneath it while you drag. And the Bees column can no
   longer be a pale cream tint; it becomes a low honey wash that still
   reads as "this one" against the neighbouring cells.
   ══════════════════════════════════════════════════════════ */
section#compare{background:var(--hive);color:#fff;
  padding:var(--sp5) 0 var(--sp5)}
section#compare .badge{background:rgba(255,255,255,.10);color:#fff;
  box-shadow:inset 0 0 0 1px rgba(255,255,255,.18)}
section#compare .cmp-head h2{color:#fff}
section#compare .cmp-head p{color:#9CA2AE}

section#compare .cmp{background:#101A30;
  box-shadow:inset 0 0 0 1px rgba(255,255,255,.10),
             0 18px 44px rgba(0,0,0,.28)}
section#compare .cmp th,
section#compare .cmp td{border-bottom-color:rgba(255,255,255,.09)}
section#compare .cmp thead th{color:#9CA2AE;background:#0B1222}
/* honey at 9-16% over navy composites to olive-brown, which looked
   like dirt rather than emphasis. The Bees column is lifted with a
   lighter navy instead and marked with a honey rule along the top of
   its header, so the accent colour stays saturated where it lands. */
section#compare .cmp thead th.us{color:#fff;background:#14213D;
  box-shadow:inset 0 3px 0 var(--honey)}
section#compare .cmp thead th:first-child{background:#0B1222}
section#compare .cmp td:first-child{color:#fff}
section#compare .cmp tbody td:first-child{background:#101A30}
section#compare .cmp .us{background:#14213D}
section#compare .cmp .val{color:#fff}
section#compare .cmp .sm{color:#9CA2AE}
section#compare .cmp .win{color:var(--honey)}
section#compare .cmp .no{color:#646C7F}
/* the shadow that marks the frozen column has to darken, not lighten */
section#compare .cmp th:first-child::after,
section#compare .cmp td:first-child::after{
  background:linear-gradient(90deg,rgba(0,0,0,.30),rgba(0,0,0,0))}
section#compare .cmp-more{color:var(--honey)}
/* The plans headline is two sentences with an authored <br> between
   them. The measure was 15ch — about 530px at 64px type — so each
   sentence wrapped again and the result was four lines.

   Widening the cap alone does not fix it: measured at 64px the longer
   English sentence is 1197px and the Filipino one 1481px, against a
   1136px column at a 1200px viewport. The type has to come down, and
   Filipino needs to come down further than the rest. These clamps keep
   both sentences on one line each from 768px up, so the only break is
   the one in the markup. */
.cta h2{max-width:none}

/* ── two of the six use-case cards now carry real photographs ──
   The placeholder rule sets background-color and a flat background-image
   on every .ushot, so a card with a photo has to override the image
   with its own. Dropping data-ph is what removes the "01"/"06" label —
   it is rendered by .ushot[data-ph]::after. */
.ushot.us-04{background-image:url(/home/home-caceceb9b671.webp)}
.ushot.us-05{background-image:url(/home/home-d6cf782473b7.webp)}
.ushot.us-02{background-image:url(/home/home-59a505f28154.webp)}
.ushot.us-03{background-image:url(/home/home-99f0660b7f8a.webp)}
.ushot.us-01{background-image:url(/home/home-7b9beb203099.webp)}
.ushot.us-06{background-image:url(/home/home-57da56ecfe57.webp)}

/* ══════════════════════════════════════════════════════════
   USE-CASE CARDS AS CARDS
   Previously the caption sat on top of the photograph behind a
   gradient scrim, and the sentence only appeared for the card the
   spotlight was on. Three things follow from moving the text onto a
   surface of its own:

   The scrim goes. It existed because a photograph cannot be trusted to
   be dark where white text lands — on a white card that problem does
   not exist, and the picture is no longer half-covered.

   Every card can now say what it says. The grid-template-rows 0fr/1fr
   trick was there to hide the body copy until you pointed at a card;
   on a phone there is no pointer, and five of six cards said nothing.

   The photo keeps its own rounded frame inset inside the card, so the
   image reads as mounted rather than bleeding to the edge.
   ══════════════════════════════════════════════════════════ */
.use{background:#FFFFFF;border-radius:calc(var(--r-md) + 6px);
  padding:10px 10px 4px;
  box-shadow:0 1px 2px rgba(20,33,61,.05),0 10px 26px rgba(20,33,61,.07);
  transition:opacity .5s var(--e),transform .45s var(--out),
             box-shadow .45s var(--e),filter .6s var(--e)}
/* ── the hovered card lifts out of the row ──
   Modelled on the reference: the card scales up, tilts a couple of
   degrees and throws a long shadow, so it reads as picked up off the
   surface rather than merely highlighted.

   z-index has to come with it. Grid items paint in source order, so
   without it the card to the right would draw over the enlarged one
   and clip the very effect being created.

   The photo's own zoom drops from 1.04 to 1.02: the two transforms
   multiply, and 1.06 x 1.04 pushed the crop noticeably off. */
.use{position:relative;z-index:1}
@media(hover:hover){
  /* .uses-grid.armed .use.is-in sets transform:none to land the
     entrance, and that selector outranks a plain .use:hover — the
     hover has to match at least as specifically or it never applies */
  .uses-grid .use:hover,
  .uses-grid.armed .use.is-in:hover{
    z-index:3;transform:translateY(-4px);
    box-shadow:0 2px 4px rgba(20,33,61,.06),0 18px 40px rgba(20,33,61,.13)}
  .use:hover .ushot{transform:scale(1.04)}
}
@media(prefers-reduced-motion:reduce){
  .uses-grid .use:hover,
  .uses-grid.armed .use.is-in:hover{transform:none}
}

.ushot{aspect-ratio:4/3;display:block;box-shadow:none;
  transition:transform .6s var(--out)}
/* the zoom is on the photograph, not the card, so the corners stay put */
.use:hover .ushot{transform:scale(1.04)}
.use .ushot{will-change:transform}
.ushot::before{display:none}

.ucap{display:block;padding:16px 8px 14px}
.ucap h3{color:var(--hive);font-size:15.5px;line-height:1.45}
.ucap p{opacity:1;overflow:visible;padding-top:8px;
  font-size:13px;line-height:1.7;color:var(--dim)}
:is(html[lang^="zh"],html[lang^="ja"]) .ucap h3{font-size:16px;line-height:1.5}
:is(html[lang^="zh"],html[lang^="ja"]) .ucap p{font-size:13.5px;line-height:1.85}

/* the states that used to reveal the sentence have nothing left to do */
.use.is-on .ucap,.use:hover .ucap,.use:focus-within .ucap,
.no-gsap .ucap,.no-gsap .ucap p{grid-template-rows:none}

/* a photo frame needs a little more room than an overlaid caption did */
@media(max-width:1100px){.uses-grid{gap:var(--sp2)}}

/* ── on a phone the row swipes, one card at a time ──
   Two columns meant six half-width cards and headings breaking after
   two characters. A horizontal scroller gives each card most of the
   screen; scroll-snap makes it stop cleanly on one rather than drift
   between two, and 82vw leaves a sliver of the next card showing so it
   is obvious there is more to the right.

   The entrance animation is switched off here: it waits for a card to
   enter the viewport, and cards parked off-screen to the side of a
   scroller never do — they would sit at opacity 0 forever. */
@media(max-width:900px){
  #trust .uses-grid{display:flex;flex-wrap:nowrap;
    overflow-x:auto;overscroll-behavior-x:contain;
    scroll-snap-type:x mandatory;
    gap:14px;padding-inline:20px;scroll-padding-inline:20px;
    -webkit-overflow-scrolling:touch;
    scrollbar-width:none}
  #trust .uses-grid::-webkit-scrollbar{display:none}
  #trust .uses-grid .use{flex:0 0 82vw;scroll-snap-align:start;
    padding:8px 8px 2px}
  #trust .uses-grid.armed .use{opacity:1;transform:none}
  .ucap{padding:14px 8px 14px}
}

/* eSIM is a lower-case brandmark. text-transform:uppercase was
   rendering it "ESIM" in three places: the hero eyebrow, the stat
   labels, and the FAQ group heading. CSS cannot uppercase everything
   except one word, so those three lose the transform. */
/* The all-caps eyebrow style stays; the brandmark opts out of it.
   text-transform applies to whole elements, so the exception has to
   be an element: every "eSIM" inside an uppercased label is wrapped
   in .nocaps. The wrapper lives inside the data-* strings too, which
   is fine — the language switcher writes them with innerHTML. */
.nocaps{text-transform:none}

/* ══════════════════════════════════════════════════════════
   PRICE COMPARISON — the panel
   A dialog rather than a new section: the question "is this actually
   cheaper" turns up while someone is looking at the catalogue, and an
   answer that costs them their place on the page is a worse answer.
   ══════════════════════════════════════════════════════════ */
.cat-cta{display:flex;flex-wrap:wrap;gap:12px;align-items:center}
#numbers .cat-cta .b-line{border-color:#CBCED4;color:var(--hive)}
#numbers .cat-cta .b-line:hover{border-color:var(--hive)}

.aic[hidden]{display:none}
/* above the fixed nav, which sits at 90 — at 60 the bar was painting
   over the top of the panel */
.aic{position:fixed;inset:0;z-index:120;display:grid;place-items:center;
  padding:20px}
.aic-back{position:absolute;inset:0;background:rgba(11,18,34,.55)}
/* 560px was set before the panel held a four-column matrix. At that
   width the table cells were wrapping every second word. */
.aic-box{position:relative;width:min(820px,100%);max-height:88svh;
  overflow:auto;background:#FFFFFF;border-radius:24px;
  padding:34px 38px 30px;
  box-shadow:0 30px 80px rgba(11,18,34,.35);
  animation:aicIn .32s var(--out) both}
@keyframes aicIn{from{opacity:0;transform:translateY(14px) scale(.98)}
  to{opacity:1;transform:none}}
@media(prefers-reduced-motion:reduce){.aic-box{animation:none}}

.aic-x{position:absolute;top:16px;right:16px;width:34px;height:34px;
  display:grid;place-items:center;border-radius:50%;
  background:#ECEDEF;color:var(--hive);cursor:pointer}
.aic-x svg{width:16px;height:16px}
.aic-box h3{margin-top:16px;font-size:23px;letter-spacing:-.02em;
  color:var(--hive)}
.aic-lead{margin-top:8px;font-size:14.5px;line-height:1.7;color:var(--dim)}

.aic-picks{display:flex;flex-wrap:wrap;gap:8px;margin-top:20px}
.aic-pick{padding:9px 16px;border-radius:var(--r-pill);font-size:13.5px;
  font-weight:600;cursor:pointer;color:var(--dim);
  box-shadow:inset 0 0 0 1px #CBCED4;transition:all .2s var(--e)}
.aic-pick:hover{color:var(--hive)}
.aic-pick.on{background:var(--hive);color:#FFFFFF;box-shadow:none}

.aic-out{margin-top:20px}
.aic-row{display:flex;justify-content:space-between;align-items:baseline;
  gap:14px;padding:12px 0;border-bottom:1px solid #ECEDEF}
.aic-row:last-child{border-bottom:0}
.aic-row.us{font-weight:700;color:var(--hive)}
.aic-row .who{font-size:14.5px}
.aic-row .amt{font-family:var(--mono);font-size:15px;white-space:nowrap}
.aic-row.us .amt{color:var(--honey-lo)}
.aic-row .amt small{font-size:11.5px;color:var(--dim);margin-left:5px}
.aic-verdict{margin-top:16px;padding:14px 16px;border-radius:var(--r-md);
  background:#FEF8EB;font-size:14.5px;line-height:1.65;color:var(--hive)}
/* no pill, no border — it sits in a row of plain labels and a boxed
   control there reads as a form field rather than a label you can
   change. The caret is the only affordance it needs. */
.aic-country{font:inherit;color:var(--hive);font-weight:700;
  background:transparent;border:0;padding:0 20px 0 0;cursor:pointer;
  -webkit-appearance:none;appearance:none;
  background-image:url("data:image/svg+xml;charset=utf-8,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='%23646C7F' stroke-width='2.5' stroke-linecap='round'%3E%3Cpath d='M6 9l6 6 6-6'/%3E%3C/svg%3E");
  background-repeat:no-repeat;background-position:right 7px center;
  background-size:12px 12px}
.aic-ways{width:100%;margin-top:18px;border-collapse:collapse;
  table-layout:fixed}
.aic-ways th,.aic-ways td{padding:11px 12px;font-size:13px;line-height:1.5;
  text-align:left;border-bottom:1px solid #ECEDEF;vertical-align:top}
.aic-ways thead th{font-size:12px;letter-spacing:.02em;color:var(--dim);
  font-weight:600}
.aic-ways tbody th{color:var(--hive);font-weight:600;width:22%}
.aic-ways td{color:var(--dim)}
.aic-ways .us{background:#FEF8EB;color:var(--hive);font-weight:600}
.aic-ways tr:last-child th,.aic-ways tr:last-child td{border-bottom:0}
.aic-note{margin-top:16px;font-family:var(--mono);font-size:11px;
  line-height:1.7;color:var(--dim)}

@media(max-width:640px){
  .aic-box{padding:26px 18px 22px;border-radius:20px}
  .aic-box h3{font-size:20px}
  .aic-ways th,.aic-ways td{padding:9px 7px;font-size:11.5px;line-height:1.4}
  .aic-ways tbody th{width:20%}
}

/* ══════════════════════════════════════════════════════════
   USE-CASE CARDS: THE CAPTION SITS ON THE PHOTOGRAPH
   The caption moves back inside .ushot, so the picture fills the card
   and the words sit on it. That brings back the one problem the白
   card版 did not have: a photograph cannot be trusted to be dark where
   white type lands. The gradient scrim comes back with it — it is the
   only thing keeping the text legible over a bright sky or a pale wall.

   Taller frame too. 4:3 left almost no room under the subject for two
   lines of type; 3:4 gives the caption a band of its own.
   ══════════════════════════════════════════════════════════ */
.use{padding:0;overflow:hidden}
.uses-grid .ushot{aspect-ratio:3/4;display:flex;align-items:flex-end;
  position:relative;isolation:isolate;border-radius:inherit}
.uses-grid .ushot::before{content:"";position:absolute;inset:0;
  display:block;z-index:1;border-radius:inherit;
  background:linear-gradient(180deg,
    rgba(11,18,34,0) 38%,rgba(11,18,34,.55) 72%,rgba(11,18,34,.88) 100%)}

.uses-grid .ucap{position:relative;z-index:2;width:100%;
  padding:18px 18px 20px}
.uses-grid .ucap h3{color:#FFFFFF;font-size:16px;line-height:1.45;
  text-shadow:0 1px 12px rgba(11,18,34,.45)}
.uses-grid .ucap p{color:rgba(255,255,255,.86);font-size:13px;
  line-height:1.7;padding-top:8px;
  text-shadow:0 1px 10px rgba(11,18,34,.45)}
:is(html[lang^="zh"],html[lang^="ja"]) .uses-grid .ucap h3{font-size:16.5px;line-height:1.5}
:is(html[lang^="zh"],html[lang^="ja"]) .uses-grid .ucap p{font-size:13.5px;line-height:1.85}

@media(max-width:600px){
  .uses-grid .ucap{padding:16px 15px 18px}
}

/* ══════════════════════════════════════════════════════════
   HOW IT WORKS — three steps
   The reference's move is the two-tone paragraph: the first sentence
   in full contrast, the rest dropped to grey. It gives each card one
   line you cannot miss and puts the detail underneath without a second
   heading. Here that is <b> and <span> inside one <p>, which also
   means the language switcher can replace each half on its own.

   The oversized number is decoration, so it is aria-hidden by being
   pure presentation — screen readers get the label and the sentence,
   which is the whole content.
   ══════════════════════════════════════════════════════════ */
#howto{padding:var(--sp5) 0 var(--sp4)}
/* The heading used to run the full width above the two columns, which
   left the top of the left column empty and started the picture level
   with nothing. It now sits inside that column, so its first line and
   the top edge of card 01 begin on the same grid row, and the phone
   follows underneath it. */
.hw-head{max-width:none;margin-bottom:clamp(22px,2.6vw,38px)}
/* not sticky and not align-self:start any more. The sticky went when the
   heading had to stay level with card 01; the align-self has to go too,
   or the column keeps its content height and the video below it has no
   free space to grow into. */
.hw-left{position:static}
/* the column is the heading plus a whole phone; on a short window that
   is taller than the viewport, and a sticky element taller than its
   scrollport simply never finishes scrolling */
@media(max-height:840px){.hw-left{position:static}}
.hw-head h2{margin-top:20px;font-size:var(--fs6);
  letter-spacing:-.035em;line-height:1.18}
:is(html[lang^="zh"],html[lang^="ja"]) .hw-head h2{line-height:1.3}
.hw-head p{margin-top:16px;max-width:52ch;
  font-size:16.5px;line-height:1.7;color:var(--dim)}
:is(html[lang^="zh"],html[lang^="ja"]) .hw-head p{font-size:16px;line-height:1.9;max-width:34em}

/* Photograph on the left, steps stacked on the right — the reference's
   arrangement. The picture is sticky: three stacked cards are taller
   than one image, so the column has travel and the visual stays put
   while the steps move past it. Below 901px it goes back to a single
   column and the image leads. */
.hw-body{padding-inline:var(--sp3);
  display:grid;grid-template-columns:minmax(0,.95fr) minmax(0,1.05fr);
  gap:clamp(24px,3vw,48px);align-items:start}
/* The visual beside the three steps is a video. It replaces a phone
   mock-up that was drawn here in CSS — chassis, screen, three
   interfaces — all of which is gone rather than left commented out.

   --vr is the one number to change if the frame should be a different
   shape; object-fit:cover means the clip fills it either way.

   The <video> is muted, looped and playsinline, which is what browsers
   require before they will autoplay anything. Playback is not started
   here — the script at the foot of the page starts it when the frame
   is on screen and pauses it when it is not, so a clip nobody is
   looking at is not decoding frames. */
/* .hw-visual is a plain block, not a flex row. As a flex container its
   percentage width would not resolve for the child — width:100% came
   out as 0 and the frame collapsed — while a block container gives the
   percentage something definite to measure against. Centring is done
   with auto margins instead. */
/* The left column is not sticky any more. Sticky meant the heading
   drifted out of line with card 01 the moment the reader scrolled, and
   the two columns are now within about 30px of each other in height, so
   there was almost nothing for it to stick through anyway. Static keeps
   the heading and the first card starting on the same line, always. */
.hw-visual{position:static;display:block}
/* Fills the column rather than sitting in a 420px box inside it, and
   6:5 rather than square. The clip is 1:1, so object-fit:cover takes the
   crop off the top and bottom — which is the cheap direction to lose,
   the action sits in the middle of frame. */
.hw-video{position:relative;width:100%;max-width:none;
  aspect-ratio:var(--vr,6/5);border-radius:calc(var(--r-md) + 8px);
  overflow:hidden;background:#EFEDE7;
  box-shadow:0 1px 2px rgba(20,33,61,.05),
             0 26px 50px -28px rgba(20,33,61,.45)}
.hw-video-el{position:absolute;inset:0;width:100%;height:100%;
  object-fit:cover;display:block;background:transparent}

/* the placeholder. It is drawn by the note, not by the video element,
   so it disappears the moment a real file is in place — nothing to
   remember to delete. */
.hw-video-note{position:absolute;inset:0;display:flex;
  flex-direction:column;align-items:center;justify-content:center;gap:8px;
  text-align:center;pointer-events:none;
  box-shadow:inset 0 0 0 2px rgba(20,33,61,.10)}
.hw-video:has(source) .hw-video-note{display:none}
.hw-video-note b{font-size:15px;font-weight:700;color:#8A91A0}
.hw-video-note i{font-style:normal;font-family:var(--mono);font-size:11px;
  letter-spacing:.08em;color:#AEB4C0}

.hw-grid{list-style:none;margin:0;display:flex;flex-direction:column;gap:18px}
.hw-step{position:relative;background:#FFFFFF;
  border-radius:calc(var(--r-md) + 4px);
  padding:26px 26px 30px;
  box-shadow:inset 0 0 0 1px #ECEDEF}

.hw-top{display:flex;align-items:baseline;justify-content:space-between;
  gap:16px}
.hw-num{font-size:clamp(46px,5vw,68px);line-height:.9;font-weight:800;
  letter-spacing:-.05em;color:var(--hive)}
.hw-label{font-size:15px;font-weight:600;color:var(--dim);
  text-align:right;line-height:1.4}

.hw-copy{margin-top:20px;font-size:15px;line-height:1.75;color:#9CA2AE}
.hw-copy b{color:var(--hive);font-weight:600}
:is(html[lang^="zh"],html[lang^="ja"]) .hw-copy{font-size:15px;line-height:1.95}

.hw-star{position:absolute;right:20px;bottom:18px;
  width:16px;height:16px;color:#CBCED4}
.hw-star svg{width:100%;height:100%;display:block}

@media(max-width:900px){
  .hw-body{grid-template-columns:minmax(0,1fr);gap:16px;
    padding-inline:20px}
  .hw-left{position:static}
  .hw-head{margin-bottom:var(--sp2)}
  .hw-visual{padding:2px 0 10px}
  .hw-phone{width:min(62vw,260px)}
  .hw-grid{gap:14px}
  .hw-head{padding-inline:20px}
  .hw-step{padding:22px 20px 26px}
}

/* ══════════════════════════════════════════════════════════
   WHY A LONG-TERM NUMBER — four benefit cards
   Same shape as the reference: centred head, then a row of four
   coloured cards, each an icon badge over a title and two lines.

   Colour is the one deliberate departure. The reference fills its
   cards with the brand colour, but ours is navy and this section sits
   between two navy blocks — a third would flatten the whole middle of
   the page. The cards take navy, the section keeps the cream it
   inherits, so the row reads as four objects on the page rather than
   one more dark band.

   The icons are inline SVG on currentColor, so the badge colour is set
   once on the wrapper and the stroke follows.
   ══════════════════════════════════════════════════════════ */
#whyus{padding:var(--sp5) 0}
.wcu-head{text-align:center;max-width:760px}
.wcu-head h2{margin-top:20px;font-size:var(--fs6);
  letter-spacing:-.035em;line-height:1.18}
:is(html[lang^="zh"],html[lang^="ja"]) .wcu-head h2{line-height:1.3}
.wcu-head p{margin:16px auto 0;max-width:52ch;
  font-size:16.5px;line-height:1.7;color:var(--dim)}
:is(html[lang^="zh"],html[lang^="ja"]) .wcu-head p{font-size:16px;line-height:1.9;max-width:34em}

.wcu-grid{list-style:none;margin:var(--sp3) auto 0;padding-inline:var(--sp3);
  display:grid;grid-template-columns:repeat(4,minmax(0,1fr));gap:20px}
.wcu-card{background:var(--hive);color:#FFFFFF;
  border-radius:calc(var(--r-md) + 4px);
  padding:34px 28px 30px;text-align:center;
  transition:transform .45s var(--out)}
/* ── hover on the reason cards ──
   This used to scale, tilt a couple of degrees, invert navy to white and
   throw a long shadow, all at once. It was borrowed from a reference
   where the same treatment marks a clickable tile — and that is the
   problem here twice over: these cards are not links, and a section
   whose whole job is to be believed should not be the liveliest thing
   on the page.

   What is left is a 4px lift, a hairline that warms towards honey, and
   a shadow deep enough to read as raised. Nothing rotates, nothing
   changes size, and the card stays navy, so the four of them still look
   like one set while the pointer is over one.

   z-index stays: with a shadow this soft a neighbouring card painting
   over it would still clip the edge. */
@media(hover:hover){
  .wcu-card{position:relative;z-index:1;
    box-shadow:inset 0 0 0 1px rgba(255,255,255,.06);
    transition:transform .3s var(--e),box-shadow .3s var(--e)}
  .wcu-card:hover{z-index:3;
    transform:translateY(-4px);
    box-shadow:inset 0 0 0 1px rgba(240,165,0,.35),
               0 2px 6px rgba(20,33,61,.10),
               0 18px 34px -18px rgba(20,33,61,.35)}
}
@media(prefers-reduced-motion:reduce){
  .wcu-card:hover{transform:none}
}

.wcu-ico{display:grid;place-items:center;width:56px;height:56px;
  margin:0 auto 20px;border-radius:50%;
  background:rgba(255,255,255,.10);color:var(--honey)}
.wcu-ico svg{width:26px;height:26px;display:block}

.wcu-card h3{font-size:17px;line-height:1.4;letter-spacing:-.02em}
.wcu-card p{margin-top:10px;font-size:13.5px;line-height:1.75;color:#9CA2AE}
:is(html[lang^="zh"],html[lang^="ja"]) .wcu-card h3{font-size:17.5px}
:is(html[lang^="zh"],html[lang^="ja"]) .wcu-card p{font-size:14px;line-height:1.9}

@media(max-width:1000px){
  .wcu-grid{grid-template-columns:repeat(2,minmax(0,1fr))}
}
@media(max-width:560px){
  .wcu-grid{grid-template-columns:minmax(0,1fr);gap:14px;
    padding-inline:20px}
  .wcu-card{padding:28px 22px 24px}
  .wcu-head{padding-inline:20px}
}

/* The stacking list is gone. Six sticky panels ran to 4.3 screens —
   about a third of the page — and the covering effect stops being a
   surprise after the second one. The row is back: six white cards in
   one line, arriving left to right, and the page carries on. */

/* ── on a pointer device the sentence waits for the pointer ──
   Only where there is a pointer to wait for: @media(hover:hover) keeps
   phones and tablets showing everything, which is the whole reason the
   old always-hidden version was wrong.

   The paragraph keeps its space in the layout and is hidden with
   opacity, not with height. Animating the height would be the obvious
   move, but the six cards share one grid row: growing one card grows
   the row, and everything below the section jumps down. Reserving the
   space means the card never changes size and nothing moves. The cost
   is a gap under the title while idle, which reads as breathing room. */
@media(hover:hover) and (min-width:901px){
  .ucap p{opacity:0;transform:translateY(6px);
    transition:opacity .3s var(--e),transform .45s var(--out)}
  .use:hover .ucap p,
  .use:focus-within .ucap p,
  .use.is-on .ucap p{opacity:1;transform:none}
}

/* ══════════════════════════════════════════════════════════
   USE CASES: STICKY STACK BESIDE THE HEADING (desktop)
   The heading held the left half and the right half was empty, so the
   cases move up into it. Each card is landscape and sticks at the same
   offset, which is what makes them pile: the second stops where the
   first stopped and covers it, and so on down the six.

   The tops are staggered by a few pixels per card so the edges of the
   ones underneath stay visible — without that the stack looks like a
   single card and the reader has no idea how many are left.

   The heading is sticky too, so it stays alongside its own cards
   instead of scrolling away while they are still arriving.

   Everything here is a media query for 901px and up. The phone keeps
   the swipeable row, which suits a narrow screen far better than six
   stacked landscape cards.
   ══════════════════════════════════════════════════════════ */
@media(min-width:901px){
  #trust .uses-body{display:grid;
    grid-template-columns:minmax(0,.8fr) minmax(0,1.2fr);
    gap:clamp(28px,4vw,64px);align-items:start}
  #trust .uses-head{position:sticky;top:120px;margin-bottom:0;max-width:none}

  #trust .uses-grid{display:flex;flex-direction:column;gap:26px;
    width:auto;padding:0;margin:0;list-style:none}
  #trust .uses-grid .use{position:sticky;flex:none;
    top:calc(120px + var(--st,0px))}
  #trust .uses-grid .use:nth-child(1){--st:0px}
  #trust .uses-grid .use:nth-child(2){--st:14px}
  #trust .uses-grid .use:nth-child(3){--st:28px}
  #trust .uses-grid .use:nth-child(4){--st:42px}
  #trust .uses-grid .use:nth-child(5){--st:56px}
  #trust .uses-grid .use:nth-child(6){--st:70px}

  /* landscape, and the caption gets a wider column to sit in */
  #trust .uses-grid .ushot{aspect-ratio:16/9}
  #trust .uses-grid .ucap{padding:22px 24px 24px;max-width:34em}
  #trust .uses-grid .ucap h3{font-size:20px}
  #trust .uses-grid .ucap p{font-size:14px;max-width:44ch}

  /* the fly-in came from the right for a row; a stack rises instead */
  #trust .uses-grid.armed .use{transform:translateY(40px)}
  #trust .uses-grid.armed .use.is-in{transform:none}

  /* a stacked card lifting on hover would shove itself out of the pile */
  #trust .uses-grid .use:hover,
  #trust .uses-grid.armed .use.is-in:hover{transform:none;z-index:3}
}

/* ── the card row runs the full width of the window ──
   .wrap caps at 1400px, so on a wide screen the six cards sat in a
   band with a lot of cream either side.

   The row is now a sibling of .wrap rather than a child of it, so it
   fills the section on its own. The obvious alternative — leaving it
   in place and giving it width:100vw with negative margins — measures
   100vw as including the scrollbar, which is 10px of sideways scroll
   on every desktop that has one. Moving the element sidesteps that
   arithmetic entirely.

   The section head stays inside .wrap: it is a paragraph and wants a
   readable measure, while the cards want room. */
#trust .uses-grid{padding-inline:clamp(20px,2.4vw,40px)}

/* The section head's line-height was being decided elsewhere and came
   out at 1.04 — fine for the two-line Chinese, too tight for the
   three-line Filipino, where the descenders of "pangalawang" ran into
   the line below. Set on the section so it wins wherever the other
   rule lives. */
#trust .uses-head h2{line-height:1.18}
:is(html[lang^="zh"],html[lang^="ja"]) #trust .uses-head h2{line-height:1.3}

/* the use-case row gets a proper section head, same parts and the same
   order as the one over the comparison table so the two sections read
   as siblings. Left-aligned rather than centred: the row it introduces
   is a left-to-right spotlight, and a centred head would point away
   from where the eye needs to go next. */
.uses-head{margin-bottom:var(--sp3);max-width:640px}
.uses-head h2{margin-top:20px;font-size:var(--fs6);letter-spacing:-.035em;
  line-height:1.12}
.uses-head p{margin-top:16px;font-size:16.5px;line-height:1.7;color:var(--dim)}
:is(html[lang^="zh"],html[lang^="ja"]) .uses-head h2{line-height:1.3}
:is(html[lang^="zh"],html[lang^="ja"]) .uses-head p{font-size:16px;line-height:1.9}
@media(max-width:900px){
  .uses-head{padding-inline:20px;margin-bottom:var(--sp2)}
}

/* the rail's dots are controls now, not decoration */
.hero-rail{pointer-events:auto}
.hero-rail .hd{cursor:pointer}

/* Sentence-level wrapping for CJK. Chinese has no spaces, so a line
   can break between any two characters and sentences get cut in half —
   "開帳號免 / 費" in the middle of a clause. Wrapping each sentence in an
   inline-block makes the boundary between sentences the preferred break
   point: the browser fills a line with whole sentences and only breaks
   inside one when a single sentence is too long for the measure on its
   own. Unlike a hard <br> this stays correct at every width. */
.snt{display:inline-block}

/* ══════════════════════════════════════════════════════════
   RESTORED WITH THE HERO MEASURE
   Removing my duplicate reveal took out an adjacent CSS block with it —
   these four rules are back, plus the hero paragraph fix.

   The Chinese hero paragraph ran to three lines. Its cap was 32ch, and
   ch is the width of "0", so against full-width glyphs it is about half
   of what it reads as: 32ch measured 401px, room for roughly 24 Han
   characters against a 55-character sentence. Stated in em, where one
   unit is one glyph, 30em gives 540px and two lines.

   body carried overflow-x:hidden, which makes the element a scroll
   container and breaks every position:sticky inside it. clip does the
   same clipping without that side effect.
   ══════════════════════════════════════════════════════════ */
/* 36em was one glyph short: panel 2's second sentence measures 648px
   against a 648px box, so it wrapped and the paragraph ran to three
   lines. 38em gives it the room. Not wider than that — at 42em panel 4
   collapses to a single line and the four panels stop matching. */
:is(html[lang^="zh"],html[lang^="ja"]) .hero .hp p{max-width:38em}

/* clip on body alone is not enough: the document element is the scroll
   container, so an overflowing descendant still moves the page sideways.
   The hero's background layers are scaled past their frame on purpose,
   which is exactly that case. Clipping at :root stops it, and unlike
   hidden, clip does not turn the element into a scroll container and so
   leaves position:sticky working. */
html{overflow-x:clip}
body{overflow-x:clip}
#numbers .cat-left{align-self:stretch}
#numbers .cat-grid{padding-top:calc(var(--sp5) + 40px)}
section[id],.anchor,header[id]{scroll-margin-top:clamp(112px,10vw,140px)}

/* Two products, two groups. The billing question is tagged
   data-topic="num esim" because it answers for both; it stays with
   the numbers, which is where it is reached first. */
.faq-group{margin:var(--sp3) 0 4px;font-family:var(--mono);
  font-size:11.5px;letter-spacing:.14em;text-transform:uppercase;
  color:var(--honey-lo);text-align:left}
.faq-list > .faq-group:first-of-type{margin-top:var(--sp2)}

/* ══════════════════════════════════════════════════════════
   FAQ: ONE CENTRED COLUMN, SUPPORT CARD LAST
   The support card was an <aside> in the left half of a two-column
   grid, so the questions sat off to the right of a mostly empty
   column. It now follows the list in the DOM as well as on screen —
   "still not sure?" only makes sense after you have read the answers,
   and a screen reader hits it in that order too.

   The heading and the topic tabs centre. The question rows do not: a
   .qa row is a flex with the text at one end and the + at the other,
   and centring the text would leave the icon stranded and make the
   answer paragraphs read badly. The list is centred as a block with a
   readable measure instead, which is what puts it on the page's axis.
   ══════════════════════════════════════════════════════════ */
section#faq .faq-grid{grid-template-columns:minmax(0,1fr);
  justify-items:center;gap:var(--sp4)}
section#faq .faq-list{width:100%;max-width:860px}
section#faq .faq-title{text-align:center}
section#faq .faq-tabs{display:inline-flex}
section#faq .faq-list > .faq-tabs{margin-left:auto;margin-right:auto}
section#faq .faq-list{text-align:center}
section#faq .qa,section#faq .qa .q,section#faq .qa .a p{text-align:left}
section#faq .faq-side{position:static;width:100%;max-width:560px}

/* ══ the support card, by width ══
   This card is a heading, one line of copy and a button. Below 900px
   that is a short column and it reads best centred, on the same axis
   as the title and the topic tabs above it.

   From 901px there is room to lay it out as a row instead: the copy on
   the left, the button on the right, and the card widened to the same
   860px measure the question list uses so the two edges line up. The
   card has no wrapper around its text, so the row is built with grid
   areas rather than flex — h3 and p stack in the left column while the
   button spans both rows on the right. */
@media(max-width:900px){
  section#faq .faq-card{text-align:center}
}
@media(min-width:901px){
  section#faq .faq-side{max-width:860px}
  section#faq .faq-card{
    display:grid;
    grid-template-columns:minmax(0,1fr) auto;
    grid-template-areas:"head cta" "copy cta";
    align-items:center;
    column-gap:var(--sp3);
    padding:36px 40px}
  section#faq .faq-card h3{grid-area:head}
  section#faq .faq-card p{grid-area:copy;margin-top:10px}
  section#faq .faq-card .btn{grid-area:cta;margin-top:0;align-self:center}
}


/* ── one size for every section heading ──
   The six section headings were running at three different sizes: 44px
   for numbers, data pricing and the closing ring, 58px for plans, 64px
   for the FAQ. Nothing distinguished them in the page hierarchy — they
   are all the same rank — so they all take --fs6 now. The hero keeps
   --fs7 because it genuinely does sit a level above.

   At 44px both halves of the plans headline hold one line down to
   768px in all four languages, so the Filipino-specific size it needed
   at 58px is gone too. */
#numbers h2,
section#compare .cmp-head h2,
.cta h2,
.faq-title{font-size:var(--fs6);letter-spacing:-.035em}

/* At hero size the question no longer fits the 430px well the ring
   left for it — it went to three lines and started crowding tiles 02
   and 06. The ring opens up to make room: the tiles sit further out
   and the copy takes a wider measure. */
.ring-stage{--r:clamp(215px,27.5vw,395px)}
@media(min-width:901px){
  /* this is a % of .ring-stage, not of the viewport — below 901px the
     stage collapses to a two-column grid and a percentage here would
     have squeezed the copy to about 180px */
  .ring-copy{width:min(760px,62%)}
}

/* the one deliberate exception: the closing question is the last thing
   on the page and the only other place asking for the sign-up, so it
   matches the hero rather than the section rank */
.ring-copy h2{font-size:var(--fs7);font-weight:900;
  line-height:1.1;letter-spacing:-.04em}
:is(html[lang^="zh"],html[lang^="ja"]) .ring-copy h2{font-size:var(--fs6);
  font-weight:900;line-height:1.28}
/* Filipino stays a step down even with the break: its first half is
   34 characters against the English 16 */
html[lang="fil-PH"] .ring-copy h2{font-size:var(--fs6)}

section#compare .cmp-note{color:#9CA2AE;
  /* the 88ch cap held the note to about half the table's width, so both
     sentences wrapped mid-clause with empty space to their right. The
     note is two sentences separated by a <br>; at the table's own width
     each one fits on a single line. */
  max-width:none}

/* ══════════════════════════════════════════════════════════
   NO FILTERS ANYWHERE
   Beyond the colour grading on the photographs themselves, nine rules
   were running backdrop-filter — blur(8px) to blur(20px) with
   saturate() up to 150% — on the nav capsule, the language button,
   the hero badge, the carrier band and the floating message pills.
   Each of those frosts the part of the photograph sitting behind it,
   so the picture was still being filtered, just in patches. All off.
   The wheel thumbnails dropped their blur(1.5px)/blur(4px) too.
   Every surface keeps its own translucent background colour, so the
   type stays legible — the photo is now simply sharp behind it. */
/* RESTORED: the frosted glass is back on the chrome. What stays off is
   anything that touches a photograph as an image — the colour grading
   on .bgshot, the hero scrim, and the depth blur on the wheel
   thumbnails. backdrop-filter on a nav capsule or a message pill is a
   property of the panel, not of the picture, and taking it away left
   those surfaces reading as flat translucent slabs. */
.slot.near .card,.slot.off .card{filter:none}

/* ══════════════════════════════════════════════════════════
   PHOTOGRAPHS RUN CLEAN
   Five separate rules were grading the hero photographs
   (brightness .9 to 1.1, saturate, contrast) and a scrim was laying a
   navy wash over the bottom of the frame. None of it is mine and none
   of it stays — the images now render exactly as supplied.
   The headline keeps its text-shadow: that sits on the type, not on
   the picture, and it is the only thing holding white type over a
   bright sky at a readable contrast.
   ══════════════════════════════════════════════════════════ */
.bgshot,
.bgshot.px-hero,.bgshot.px-home,.bgshot.px-room,.bgshot.px-friends,
.bgshot.px-number,.bgshot.px-partner{filter:none}
.hero-scrim{background:none}

/* ══════════════════════════════════════════════════════════
   MOBILE PASS — everything below is inside a max-width query,
   so the desktop layout above is untouched.
   ══════════════════════════════════════════════════════════ */

@media(max-width:900px){

  /* ── hero: the pinned carousel becomes a plain stack ── */

  /* .hero-s is a flex ROW. On desktop the carrier band is absolutely
     positioned so it never joins the flow; on mobile it goes static and
     became a second flex item sitting BESIDE the copy, which squeezed the
     hero to 248px and pushed it off-screen. It stacks here, so it does
     not need to be a flex container at all. */
  .hero-s{display:block;padding:104px 0 0}

  /* the two-column track is re-declared after the 900px query further up,
     so it survived into mobile and handed the copy ~1fr of a split that
     no longer has a right-hand column. Restate it, last. */
  .hero-grid{grid-template-columns:minmax(0,1fr);gap:0}

  /* align-items:center is inherited from the desktop grid. Under
     flex-direction:column that sizes every panel to fit-content and then
     centres it — which is why the copy sat half off the screen. */
  .hero-text{align-items:stretch;gap:0}
  .hp{align-items:stretch}

  /* Panel 1 is the hero. Panels 2-4 are the same copy the desktop
     carousel rotates through, so on mobile they read as three follow-on
     sections rather than three more hero screens: no repeated button
     pair, a rule to separate them, and a smaller heading. */
  .hp{padding-block:34px}
  .hp.on{padding-top:0}
  .hp + .hp{border-top:1px solid rgba(255,255,255,.10)}
  .hp:not(.on) .hero-cta{display:none}
  .hp h1,.hp h2{font-size:clamp(33px,8.6vw,42px);max-width:none}
  /* the Filipino halves are ~26 characters and will not sit on one line
     at the shared size in a 326px column */
  html[lang="fil-PH"] .hp h1,
  html[lang="fil-PH"] .hp h2{font-size:clamp(27px,7vw,34px)}
  /* the ring copy goes full width on a phone, where --fs7 put the
     closing question on five lines */
  .ring-copy h2{font-size:clamp(28px,7.6vw,36px)}
  .hp p{max-width:none}
  .hero .hp p{font-size:16px;line-height:1.7}
  .hero-cta{margin-top:26px;gap:10px}
  .hero-cta .btn{width:100%;max-width:320px}

  /* ── catalogue: the sticky two-column split has no mobile rule at all,
     so the copy was living in a ~90px column ── */
  /* .cat-grid replaces .wrap's own side padding, so it has to pay it
     back — the rows go full-bleed otherwise and .crow::before, which
     bleeds 10px either side for the hover surface, falls off the edge
     and gives the page a sideways scroll. */
  .cat-grid{grid-template-columns:minmax(0,1fr);
    gap:var(--sp2);padding:var(--sp4) 20px}
  .cat-sticky{position:static;top:auto}
  .cat-copy h2{line-height:1.14}
  .cat-copy p{max-width:none}

  /* ── closing ring: 94vw sits inside a wrap that already pays 32px of
     padding, so the third column fell off the edge ── */
  .ring-stage{width:100%;grid-template-columns:repeat(2,1fr);gap:12px}
  .ring-copy{margin-bottom:24px}
}

/* ── nav capsule: brand + language + CTA needed 435px of a 350px bar,
   so the sign-up button was cut off at every scroll position ── */
@media(max-width:900px){
  .nav{padding:0 14px}
  .cap{gap:10px;padding:6px 6px 6px 14px}
  .cap .brand img{height:18px}
  .cap .navcta{padding:10px 15px;font-size:12.5px}
}
@media(max-width:400px){
  .nav{padding:0 10px}
  .cap{gap:7px;padding:5px 5px 5px 11px}
  .cap .brand img{height:16px}
  .cap .navcta{padding:9px 12px;font-size:12px}
  .lang-btn{padding:8px 9px;gap:5px}
}

@media(max-width:560px){
  /* the number rows keep a third auto column for the price, which pushed
     the grid 10px past the screen and gave the whole page a sideways
     scroll. Two columns, and the long country names get to wrap. */
  .crow,.crow.dst{grid-template-columns:auto minmax(0,1fr)}
  .cname{overflow-wrap:anywhere}
  .cmeta,.cprice{white-space:normal}
  .cmoney,.cstock{grid-column:2/3}
}

@media(max-width:760px){
  /* .marqRow turns column here. In a column flex box, align-items:center
     sizes children to fit-content, so min-width:0 no longer restrained the
     ticker and it grew to ~4000px, dragging the whole page into a sideways
     scroll. The cross size has to be stated outright. */
  .marqView{width:100%;align-self:stretch}
}

/* ══ USE CASES — an irregular mosaic that arrives as you reach it ══
   Three things were wrong with the sticky pile this replaces.

   1. Every photograph in the set is a 1086×1448 portrait. The pile
      cropped them to 16:9, which is most of a person's height thrown
      away — heads and shoulders were landing outside the frame.
   2. Piled cards overlap by design, so a hover that lifted one card
      dragged its caption across the card above it.
   3. The whole pile was already sitting in the viewport when the
      section arrived, so there was nothing left to reveal on scroll.

   The cards now flow down two masonry columns at ratios that differ
   from card to card, which is what knocks the two columns out of
   lockstep and gives the block its irregular edge. Nothing overlaps,
   so hover is a plain lift again, and each card waits for its own
   scroll position before it fades up. */
@media(min-width:901px){
  #trust .uses-grid{display:block;columns:2;
    column-gap:clamp(18px,1.8vw,30px);padding:0;margin:0;width:auto}
  #trust .uses-grid .use{position:static;top:auto;flex:none;
    break-inside:avoid;-webkit-column-break-inside:avoid;
    margin:0 0 clamp(18px,1.8vw,30px);
    transition:opacity .55s var(--e),transform .7s var(--out),
      filter .55s var(--e),box-shadow .35s var(--e)}

  /* tall frames, and no two neighbours the same */
  #trust .uses-grid .ushot{aspect-ratio:var(--ar,3/4)}
  #trust .uses-grid .use:nth-child(1){--ar:3/4}
  #trust .uses-grid .use:nth-child(2){--ar:1/1}
  #trust .uses-grid .use:nth-child(3){--ar:4/5}
  #trust .uses-grid .use:nth-child(4){--ar:1/1}
  #trust .uses-grid .use:nth-child(5){--ar:4/5}
  #trust .uses-grid .use:nth-child(6){--ar:3/4}
  /* The right column starts lower than the left so the two never line
     up across the gutter. It has to be a transform, not a margin: the
     card is the first box in its column, and a top margin there is
     dropped at the column break. The entrance animation also wants the
     transform, so the two are added together through a variable and
     the offset survives being revealed — and being hovered. */
  #trust .uses-grid .use{--off:0px;--rise:0px;
    transform:translateY(calc(var(--off) + var(--rise)))}
  #trust .uses-grid .use:nth-child(n+4){--off:clamp(30px,3.4vw,58px)}

  #trust .uses-grid .ucap{padding:20px 22px 22px;max-width:none}
  #trust .uses-grid .ucap h3{font-size:18px}
  #trust .uses-grid .ucap p{font-size:13.5px;max-width:32ch}

  /* the caption sits on top of the photograph, so showing the sentence
     costs no height — there is nothing to hold back and nothing to
     jump when the pointer arrives. */
  #trust .uses-grid .ucap p{opacity:1;transform:none}

  /* separate cards can lift without touching anything */
  #trust .uses-grid .use:hover,
  #trust .uses-grid.armed .use.is-in:hover{
    transform:translateY(calc(var(--off) - 5px));z-index:2;
    box-shadow:0 2px 4px rgba(20,33,61,.06),0 22px 46px rgba(20,33,61,.15)}

  /* entrance: held until the card itself reaches the viewport.
     The transform is restated on both of these because the sticky-pile
     rules above set transform:none on .is-in, and that selector carries
     a class more than the base rule — left alone it wins and takes the
     column offset with it. */
  #trust .uses-grid.armed .use{opacity:0;--rise:38px;
    transform:translateY(calc(var(--off) + var(--rise)))}
  #trust .uses-grid.armed .use.is-in{opacity:1;--rise:0px;filter:blur(0);
    transform:translateY(var(--off))}
}
@media(min-width:901px) and (prefers-reduced-motion:reduce){
  #trust .uses-grid.armed .use{opacity:1;--rise:0px;filter:none}
  #trust .uses-grid .use:hover,
  #trust .uses-grid.armed .use.is-in:hover{
    transform:translateY(var(--off))}
}

/* ══ USE CASES — the heading holds the middle, the pictures move ══
   The cases used to sit in a block beside a heading that scrolled with
   them. Here the heading takes the centre column and stays put: it is
   sticky against a box one viewport tall, so it reads as fixed in the
   middle of the screen for as long as the section is on screen, while
   the two outer columns of photographs travel past it.

   The travel is a scrubbed parallax, not a pin. Pinning would hold the
   page still and add the section's whole length to the scroll; this way
   the section is no taller than its own two columns and the movement
   comes from the columns running at different speeds — one drifting up,
   the other down — which is what makes them read as arriving from the
   left and the right rather than simply scrolling. */
@media(min-width:901px){
  #trust .uses-body{display:grid;
    grid-template-columns:minmax(0,1fr) minmax(0,1.3fr) minmax(0,1fr);
    column-gap:clamp(18px,2.4vw,42px);align-items:start;gap:0;
    column-gap:clamp(18px,2.4vw,42px)}

  /* the <div> that wraps the two columns steps out of the way so the
     columns themselves are the grid items, one either side */
  #trust .uses-grid{display:contents}

/* ══ use cases: same composition, less waiting ══
   The layout stays as it was — fixed centre heading, cards staggered
   either side. What changes is the pace. The opening run of empty space
   was half a screen at the top and nearly as much at the foot, the right
   column started 310px lower than the left, and the cards sat up to
   112px apart. Scrolling through it turned up very little new per screen.

   Roughly a third comes off the head and foot padding, the stagger is
   cut to about 60% of what it was, and the gaps close by a third. The
   offset is deliberately kept rather than removed: it is what stops the
   two columns reading as a plain grid, and at 180px it still does that
   while bringing the next card into view sooner.

   The heading is unaffected — it is sticky across the whole grid row,
   so it holds until the last card in the taller column has passed. */
  /* The gap between cards and the offset on the right column are both
     large on purpose: they are what keeps the two sides from ever
     sitting level with each other. At any point in the scroll one card
     is arriving on one side while the other side is halfway out, which
     is the diagonal reading the layout is after — evenly spaced columns
     would just look like a two-column grid however they move. */
  #trust .uses-col{list-style:none;margin:0;padding:0;grid-row:1;
    display:flex;flex-direction:column;gap:clamp(36px,4.4vw,76px);
    padding-top:clamp(160px,33vh,330px);
    padding-bottom:clamp(130px,25vh,280px);will-change:transform}
  #trust .uses-col:first-child{grid-column:1}
  #trust .uses-col:last-child{grid-column:3;
    margin-top:clamp(90px,11vw,180px)}

  /* A sticky box releases when its own bottom reaches the bottom of its
     containing block — so a box one viewport tall lets go a full screen
     early, and the heading was sliding away while the last two cards
     were still arriving.

     It is its own height now, stuck at the middle of the screen and
     pulled back up by half of itself to sit centred. The layout box is
     a few hundred pixels rather than 100vh, so it holds almost to the
     end of the column. */
  /* above the veils. Those two white bands are stretched across the whole
     block at z-index 5 to fade the cards in and out at its edges, and
     they were painting over the centre column as well — the lead
     paragraph came out as a ghost with only its last few characters
     legible. They still cover the cards, which is all they were for. */
  #trust .uses-head{grid-column:2;grid-row:1;align-self:start;z-index:6;
    position:sticky;top:50vh;height:auto;margin:0;max-width:none;
    transform:translateY(-50%);
    padding:0 clamp(4px,1vw,18px);
    display:flex;flex-direction:column;align-items:center;
    justify-content:center;text-align:center}
  /* the centre column is narrower than a full-width heading, so the
     display size comes down a step rather than breaking mid-phrase */
  #trust .uses-head h2{margin-top:18px;line-height:1.22;
    font-size:clamp(26px,2.6vw,38px);letter-spacing:-.035em;
    text-wrap:balance}
  :is(html[lang^="zh"],html[lang^="ja"]) #trust .uses-head h2{line-height:1.4;letter-spacing:-.01em}
  #trust .uses-head p{margin-top:16px;max-width:24em;font-size:15.5px}
  :is(html[lang^="zh"],html[lang^="ja"]) #trust .uses-head p{font-size:15px;max-width:22em}

  /* One square frame for all six. The mixed ratios were there to break
     the two columns out of lockstep, but the column offset and the gaps
     already do that, and six different heights made the block read as
     unresolved rather than irregular. */
  #trust .uses-grid .ushot{aspect-ratio:1/1}

  #trust .uses-grid .use{position:static;top:auto;flex:none;margin:0;
    --off:0px;--rise:0px;transform:translateY(var(--rise));
    break-inside:auto}
  #trust .uses-grid.armed .use{opacity:0;--rise:34px;
    transform:translateY(var(--rise))}
  #trust .uses-grid.armed .use.is-in{opacity:1;--rise:0px;filter:blur(0);
    transform:none}
  #trust .uses-grid .use:hover,
  #trust .uses-grid.armed .use.is-in:hover{
    transform:translateY(-5px);z-index:2;
    box-shadow:0 2px 4px rgba(20,33,61,.06),0 22px 46px rgba(20,33,61,.15)}
}
@media(min-width:901px) and (prefers-reduced-motion:reduce){
  #trust .uses-col{transform:none!important}
}
/* narrow: the columns dissolve and the six cards go back to being one
   swipeable row, which is what the scroller rule below already expects */
@media(max-width:900px){
  #trust .uses-col{display:contents}
}

/* ══ CLOSING BLOCK — one frame, not a ring of empty tiles ══
   Everything above about .ring-stage and .ring-shot is now dead: the six
   tiles are gone from the markup. What is left is a full-bleed dark
   frame. The rules below have to restate position and colour because the
   old ring put .ring-copy at absolute centre of a square stage and the
   light theme painted the whole section white. */
.ring{position:relative;overflow:hidden;background:#080C16;color:#fff;
  min-height:min(86vh,840px);display:grid;place-items:center;
  padding:var(--sp5) 0}

/* .ushot carries a frame's worth of styling — aspect ratio, radius,
   shadow — that a full-bleed backdrop wants none of. Only the class's
   background-image is being borrowed. */
.ring-bg{position:absolute;inset:0;z-index:0;
  aspect-ratio:auto;border-radius:0;box-shadow:none;display:block;
  background-size:cover;background-position:50% 32%;
  /* 1.30 rather than the 1.06 this rested at before: at 1.06 the left third of
     the frame was bare table. The crop is already pushed right, so zooming in
     is what walks the phone across into that space. */
  transform:scale(1.30)}
.ring-veil{position:absolute;inset:0;z-index:1;pointer-events:none;
  background:
    radial-gradient(115% 78% at 50% 44%,rgba(8,12,22,.28),rgba(8,12,22,.82)),
    linear-gradient(180deg,rgba(8,12,22,.80),rgba(8,12,22,.42) 38%,
      rgba(8,12,22,.94))}

.ring .wrap{position:relative;z-index:2}
.ring-copy{position:static;left:auto;top:auto;transform:none;
  width:auto;max-width:none;text-align:center}
@media(min-width:901px){.ring-copy{width:auto}}

.ring-eyebrow{display:inline-flex;align-items:center;
  font-family:var(--mono);font-size:11.5px;letter-spacing:.2em;
  text-transform:uppercase;color:rgba(255,255,255,.55)}
:is(html[lang^="zh"],html[lang^="ja"]) .ring-eyebrow{letter-spacing:.14em;font-size:12px}

.ring-copy h2{margin-top:clamp(20px,2.4vw,34px);color:#fff;font-weight:900;
  font-size:clamp(46px,8.2vw,118px);line-height:.98;letter-spacing:-.05em}
:is(html[lang^="zh"],html[lang^="ja"]) .ring-copy h2{font-size:clamp(38px,6.2vw,86px);
  line-height:1.14;letter-spacing:-.02em}
html[lang="fil-PH"] .ring-copy h2{font-size:clamp(38px,6vw,84px)}
/* the second line drops back, so the question reads in two beats
   instead of one solid slab. At 50% it dropped further than intended —
   on the navy it read as greyed out rather than as a second beat, and
   at this size the weight alone already separates the two lines. */
.ring-copy h2 .rc-dim{color:rgba(255,255,255,.7)}

.ring-copy .btn{margin-top:clamp(28px,3.4vw,46px)}

@media(max-width:900px){
  .ring{min-height:auto;padding:var(--sp4) 0}
  .ring-copy{margin-bottom:0}
}

/* ══ CURSOR GLOW ══
   A soft two-layer honey light that trails the pointer. Two layers
   because one blur cannot be both tight enough to feel attached to the
   cursor and wide enough to light the area around it: the core follows
   closely, the aura lags and spreads.

   It is fixed at z-index 40, under the nav (90) and over everything
   else, so it stays visible across cards instead of vanishing behind
   them. Desktop pointers only — there is no pointer to trail on a
   touch screen, and the rAF loop is never started there. */
.cursor-glow{display:none;position:fixed;top:0;left:0;width:1px;height:1px;
  z-index:40;pointer-events:none;opacity:0;visibility:hidden;
  will-change:opacity}
@media (hover:hover) and (pointer:fine){.cursor-glow{display:block}}
@media (hover:none),(pointer:coarse){.cursor-glow{display:none!important}}
@media (prefers-reduced-motion:reduce){.cursor-glow{display:none!important}}

.cursor-glow.is-visible{opacity:var(--cursor-glow-opacity,.78);
  visibility:visible;transition:opacity 420ms cubic-bezier(.16,1,.3,1)}
.cursor-glow-aura,.cursor-glow-core{position:fixed;top:0;left:0;
  border-radius:50%;pointer-events:none;will-change:transform}
.cursor-glow-aura{width:186px;height:154px;margin:-77px 0 0 -93px;
  background:radial-gradient(ellipse at center,
    rgba(245,184,0,.16) 0%,
    rgba(181,132,10,.08) 38%,
    rgba(245,184,0,.024) 65%,
    transparent 78%);
  filter:blur(28px)}
.cursor-glow-core{width:74px;height:58px;margin:-29px 0 0 -37px;opacity:.9;
  background:radial-gradient(ellipse at center,
    rgba(181,132,10,.18) 0%,
    rgba(245,184,0,.09) 52%,
    transparent 76%);
  filter:blur(15px);transition:opacity 380ms cubic-bezier(.16,1,.3,1)}
.cursor-glow.is-tight .cursor-glow-core{opacity:1}

.cursor-glow[data-tone="soft"]{--cursor-glow-opacity:.6}
.cursor-glow[data-tone="normal"]{--cursor-glow-opacity:.78}
/* the closing frame is the one dark field on the page, where the same
   light reads far weaker against the photograph */
.cursor-glow[data-tone="strong"]{--cursor-glow-opacity:1}

/* overflow-x:clip rather than hidden — hidden would make an ancestor
   scroll container and kill the sticky heading outright. */
#trust{overflow-x:clip}

/* the dashed rings that used to sit behind this heading are gone */

/* Cards now arrive from the side they live on rather than straight up:
   the left column slides in from the left, the right from the right.
   The offset rides in its own variable so it can be composed with the
   column stagger and the scrubbed parallax without any of the three
   overwriting the others. */
/* Position and opacity of a card are now written by GSAP every frame,
   tied to scroll rather than fired once. Nothing in CSS may set
   transform or opacity on .use above 901px or it will fight the scrub
   — including the hover lift, which is why hover is down to a shadow
   and the photograph's own zoom. */
@media(min-width:901px){
  #trust .uses-grid .use{transform:none}
  #trust .uses-grid.armed .use{opacity:0;filter:none}
  #trust .uses-grid .use:hover,
  #trust .uses-grid.armed .use:hover{transform:none;z-index:2;
    box-shadow:0 2px 4px rgba(20,33,61,.06),0 26px 52px rgba(20,33,61,.17)}
  #trust .uses-grid .use{transition:box-shadow .35s var(--e)}
}

/* ══ CLOSING BLOCK — the frame opens, then the words arrive ══
   The photograph and its veil are clipped together by one wrapper, so
   the darkening travels with the image instead of sitting over the
   shutter. The clip is an inset from both edges at once: at 50% it is a
   closed seam across the middle, at 0% the full frame.

   Both initial states hang off .ring-armed, which the script adds only
   when it is going to animate them. If GSAP never loads, the class is
   never added and the section simply renders — nothing is left clipped
   shut or invisible. */
.ring-media{position:absolute;inset:0;z-index:0}
.ring.ring-armed .ring-media{clip-path:inset(50% 0 50% 0)}
.ring.ring-armed .ring-eyebrow,
.ring.ring-armed .ring-copy h2,
.ring.ring-armed .ring-copy .btn{opacity:0}
@media(prefers-reduced-motion:reduce){
  .ring.ring-armed .ring-media{clip-path:none}
  .ring.ring-armed .ring-eyebrow,
  .ring.ring-armed .ring-copy h2,
  .ring.ring-armed .ring-copy .btn{opacity:1}
}

/* ══ CLOSING BLOCK — the frame needs room to open in ══
   The section used to be about one screen tall, so the clip finished
   while most of it was still below the fold: what the reader saw was a
   black band that became a photograph, never the seam opening. The
   section is taller than the viewport now and its contents sit on a
   sticky stage — the frame locks to the screen, and the extra height is
   the scroll the opening is scrubbed against. It is sticky rather than
   a ScrollTrigger pin: pinning rewrites the document height and every
   trigger below it has to be recalculated. */
/* NB: not .ring-stage — that name still belongs to the dead hexagon-ring
   CSS above, which carries width:min(1080px,94vw) and would have held
   this frame to three quarters of the window.

   overflow must be released here. The original rule set overflow:hidden
   on .ring, which makes it a scroll container — and a sticky child can
   never stick to a scroll container that is itself scrolling past. The
   clipping moves down to .ring-frame, which is where it is needed. */
/* 170svh gave 70svh of pinned scroll, and the reveal used every pixel
   of it — the frame unstuck the instant it finished, so the finished
   state was never actually on screen. 240svh leaves roughly 60svh of
   dwell after the animation ends, which is the part you read. */
.ring{display:block;place-items:normal;min-height:240svh;padding:0;
  overflow:visible}
.ring-frame{position:sticky;top:0;height:100vh;overflow:hidden;
  display:grid;place-items:center}
.ring-frame > .wrap{position:relative;z-index:2;width:100%}

/* The stage used to be switched off below 901px, which meant the whole
   opening — the seam, the words arriving — simply did not exist on a
   narrow window. It runs at every width now.

   svh rather than vh: on a phone, 100vh is the height of the viewport
   with the browser chrome hidden, so a vh-based stage is taller than
   what is actually on screen and the frame never quite fills it. */
.ring{min-height:240svh}
.ring-frame{height:100svh}
@media(max-width:600px){
  .ring{min-height:210svh}
}

/* ══ FOOTER BACK TO DARK ══
   The light-theme block above turned the footer white; this returns it
   to a dark field so the closing frame and the footer read as one
   continuous end to the page rather than dark, white, dark again.

   #0B1220 rather than --hive: the closing block's veil bottoms out at
   about #080C16, and the standard navy sitting under it left a visible
   step where the two met.

   Everything the white version recoloured has to be named again — the
   body copy, the links, the social outlines, the rule above the legal
   line — because those rules are more specific than the element
   selector and are not going anywhere. */
footer{background:#0B1220;color:#fff;border-top:0}
.f-tag,.f-grid a{color:#9CA2AE}
.f-grid a:hover{color:#fff}
.f-grid h4{color:var(--honey)}
.f-social a{color:#9CA2AE;background:transparent;
  box-shadow:inset 0 0 0 1px rgba(255,255,255,.16)}
.f-social a:hover{color:var(--hive);background:var(--honey);
  box-shadow:inset 0 0 0 1px var(--honey)}
.f-btm{color:#7C8598;border-top-color:rgba(255,255,255,.12)}
.f-btm a{color:#9CA2AE}
.f-btm a:hover{color:#fff}
/* the wordmark is white now, so it needs the low opacity back — at full
   strength it would be a solid white slab across the foot of the page */
.f-ghost .f-logo{opacity:.15;
  -webkit-mask-image:linear-gradient(180deg,#000 40%,rgba(0,0,0,0) 96%);
          mask-image:linear-gradient(180deg,#000 40%,rgba(0,0,0,0) 96%)}

/* ══ USE CASES — the edges fade, not the cards ══
   The blur was on each card, so a card that was only halfway through
   its entrance was soft all over, wherever it happened to be on the
   screen. What was wanted is a soft edge to the block itself.

   These are two bands of the page's own colour fading to transparent,
   one stuck to the top of the screen and one to the bottom, painted
   over the cards. Sticky rather than fixed so they are bounded by the
   card block — fixed bands would still be lying over the sections
   before and after it. They sit in a flex column at full height with
   space-between, which is what puts one at each end. */
#trust .uses-body{position:relative}
.uses-veils{position:absolute;inset:0;z-index:5;pointer-events:none;
  display:flex;flex-direction:column;justify-content:space-between}
.uses-veils i{position:sticky;display:block;flex:0 0 auto;
  height:clamp(90px,19vh,210px)}
.uses-veils i:first-child{top:0;
  background:linear-gradient(180deg,var(--void) 12%,rgba(250,247,240,0))}
.uses-veils i:last-child{bottom:0;
  background:linear-gradient(0deg,var(--void) 12%,rgba(250,247,240,0))}
@media(max-width:900px){.uses-veils{display:none}}

/* ══ the join between the closing frame and the footer ══
   The two were different darks — the veil bottoms out around #080C16
   over a photograph, the footer is a flat #0B1220 — so where they met
   there was a straight line across the page.

   Rather than trying to match two colours that can never match (one of
   them is a photograph), the frame now fades to the footer's exact
   colour over its last third. By the time the two edges meet, the pixel
   above the seam and the pixel below it are the same value and there is
   nothing to see. This layer goes first in the background stack, which
   is the top of it. */
.ring-veil{
  background:
    linear-gradient(180deg,rgba(11,18,32,0) 56%,rgba(11,18,32,.72) 84%,
      #0B1220 100%),
    radial-gradient(115% 78% at 50% 44%,rgba(8,12,22,.28),rgba(8,12,22,.82)),
    linear-gradient(180deg,rgba(8,12,22,.80),rgba(8,12,22,.42) 38%,
      rgba(8,12,22,.94))}
/* the section's own field shows for a moment before the frame settles,
   so it has to end on the same colour too */
.ring{background:linear-gradient(180deg,#080C16 0 60%,#0B1220 100%)}

/* The curved seam that used to sit above this section is gone. It
   fought the 3D tilt the section already arrives with: the tilt makes
   the top of the panel narrower than the window, and a full-width arc
   above it left wedges of the hero showing between the two — badly, on
   a wide window. Bringing the curve back means dropping the tilt. */

/* a link inside running body copy: honey, no rule under it. */
.inline-link{color:var(--honey);text-decoration:none;
  transition:color .2s var(--e)}
.inline-link:hover{color:#F5C457}

/* ══ curved seam into the closing block ══
   The same idea that did not work over the catalogue works here: this
   section arrives flat, with no 3D tilt narrowing its top edge, so a
   full-width arc has nothing to disagree with.

   #080C16 is the colour the section's own field starts on, so the arc
   and the first pixel below it are the same value and the join is
   invisible. The width decides how much curve is on screen — 124% puts
   a drop of roughly 40px across a normal window, which reads as a curve
   rather than as a straight band. */
.ring-arc{position:absolute;left:50%;bottom:calc(100% - 1px);z-index:1;
  transform:translateX(-50%) scaleY(var(--arc,1));transform-origin:50% 100%;
  width:124%;height:clamp(64px,8vw,136px);pointer-events:none;
  border-radius:50% 50% 0 0 / 100% 100% 0 0;
  background:#080C16}
@media(prefers-reduced-motion:reduce){.ring-arc{--arc:0}}

/* The closing question was three characters on its first line; this
   headline is eleven, and the second line is twelve. At the old display
   size the second line ran wider than the page. */
.ring-copy h2{font-size:clamp(34px,5.6vw,74px)}
:is(html[lang^="zh"],html[lang^="ja"]) .ring-copy h2{font-size:clamp(28px,4.4vw,62px);
  line-height:1.3}
html[lang="fil-PH"] .ring-copy h2{font-size:clamp(26px,3.6vw,52px)}

/* ══ curved seam between the hero and the catalogue ══
   This replaces the 3D tilt the section used to arrive with. The two
   cannot both exist: the tilt is a perspective rotateX, which makes the
   top of the panel narrower than the window, and a full-width arc above
   a narrower panel leaves wedges of the hero showing between them. The
   panel now comes straight up with a curved top edge instead.

   #fff matches the section's own field, so the arc and the first pixel
   below it are the same value. 124% of the width puts a drop of about
   40px across a normal window — wide enough to read as a curve, narrow
   enough not to flatten into a straight band. */
.sec-arc{position:absolute;left:50%;bottom:calc(100% - 1px);z-index:0;
  transform:translateX(-50%) scaleY(var(--arc,0));transform-origin:50% 100%;
  width:124%;height:clamp(64px,8vw,136px);pointer-events:none;
  border-radius:50% 50% 0 0 / 100% 100% 0 0;
  background:#fff}
@media(max-width:900px){.sec-arc{display:none}}
@media(prefers-reduced-motion:reduce){.sec-arc{--arc:0}}

/* three short lines instead of two long ones, so the display size goes
   back up — the cap came down when the headline was eleven characters
   across, and these are five. */
.ring-copy h2{font-size:clamp(38px,6.4vw,86px);line-height:1.06}
:is(html[lang^="zh"],html[lang^="ja"]) .ring-copy h2{font-size:clamp(34px,5.4vw,78px);
  line-height:1.24}
html[lang="fil-PH"] .ring-copy h2{font-size:clamp(30px,4.4vw,64px)}

/* the hero fisheye and its displacement map have been removed */

/* ══ the use-case block on white, curving back into the page ══
   #trust had no background of its own, so it showed the cream page
   underneath. It is white now, which means the two gradient bands that
   soften its top and bottom edges have to be white as well — they fade
   the section's own colour to nothing, and a cream band on a white
   field would read as a stain.

   The seam at the foot is the same device as the closing block: a wide,
   shallow ellipse in the *next* section's colour, sitting above its top
   edge. Cream over white here, rather than white over a photograph. */
#trust{background:#fff;position:relative}
.uses-veils i:first-child{
  background:linear-gradient(180deg,#fff 12%,rgba(255,255,255,0))}
.uses-veils i:last-child{
  background:linear-gradient(0deg,#fff 12%,rgba(255,255,255,0))}

/* The curve belongs to the white block and hangs below it, bulging
   down into the cream, rather than being a cream shape pushing up. Same
   seam, opposite reading: the section above ends in a dome instead of
   the section below starting with one.

   opacity rides on the same variable as the scale. Without it the arc
   still painted its drop-shadow after it had flattened to nothing, and
   that shadow of a zero-height box is a hairline straight across the
   page — the line that was showing at the join.

   #fff and #FAF7F0 are a handful of levels apart, so the curve alone is
   nearly invisible whatever shape it is; the shadow is what draws its
   edge. drop-shadow follows the border-radius, unlike a box-shadow,
   which would outline the element's rectangle instead. */
/* The arc sits inside a box that starts exactly at the section's bottom
   edge and clips. Without it the drop-shadow blurs in every direction
   from the shape, and this shape's top edge is a straight line wider
   than the page — the shadow reached back up over it and drew a grey
   band clean across the white section. Raising the shadow's offset only
   thinned the band; the blur has a tail whatever the offset. The clip
   removes it outright.

   The box is wider than the page so the ellipse keeps its shallow
   curve; the arc inside stays the same share of the window it was. */
.trust-arc-clip{position:absolute;left:-13%;right:-13%;top:calc(100% - 1px);
  height:clamp(78px,9.5vw,168px);overflow:hidden;pointer-events:none;z-index:1}
.trust-arc{position:absolute;left:50%;top:0;display:block;
  transform:translateX(-50%) scaleY(var(--arc,1));transform-origin:50% 0;
  width:98%;height:clamp(52px,6.5vw,116px);
  border-radius:0 0 50% 50% / 0 0 100% 100%;
  background:#fff;opacity:var(--arc,1);
  filter:drop-shadow(0 3px 9px rgba(20,33,61,.10))}
@media(prefers-reduced-motion:reduce){.trust-arc{--arc:0}}

/* ══ the cards gain depth as they cross the middle of the screen ══
   A soft-UI treatment, but only half of one: the classic pair of a white
   highlight and a dark shadow needs a field that is slightly off-white
   for the highlight to have anything to lift off. On #fff it is
   invisible, so the lift is carried by the dark side plus a hairline of
   white inside the top edge, which reads as a lit edge rather than as a
   glow that is not there.

   Depth rides on --dep, written by the same timeline that fades the
   card. Alpha is multiplied by it inside the colour, so one number moves
   three shadows at once and the shape of the shadow never changes —
   only its strength. Animating the blur radii instead would force a
   fresh shadow to be rasterised on every frame. */
@media(min-width:901px){
  #trust .uses-grid .use{
    box-shadow:
      0 2px 4px rgba(20,33,61,calc(var(--dep,0) * .05)),
      0 14px 26px -10px rgba(20,33,61,calc(var(--dep,0) * .13)),
      0 34px 60px -24px rgba(20,33,61,calc(var(--dep,0) * .22)),
      inset 0 1px 0 rgba(255,255,255,calc(var(--dep,0) * .5))}
  #trust .uses-grid .use:hover{
    box-shadow:
      0 2px 4px rgba(20,33,61,.06),
      0 18px 32px -12px rgba(20,33,61,.16),
      0 44px 76px -28px rgba(20,33,61,.28),
      inset 0 1px 0 rgba(255,255,255,.55)}
}

/* ══ the catalogue no longer sits at the top of its own dead space ══
   #numbers carries min-height:100svh because it is pulled up a whole
   viewport to cover the end of the hero — anything shorter and the hero
   shows underneath it. That minimum is structural and cannot go.

   What could go is where the slack landed. The content is around 675px
   in a 900px box, and all 225px of the difference was piling up below
   the last button. The section is a column flexbox now with its content
   centred, so the slack splits above and below, and the block's own
   padding comes down to stop the two adding up. */
@media(min-width:901px){
  #numbers .cat-grid{padding-top:var(--sp5);padding-bottom:var(--sp5)}
}

/* Real flag artwork sits in the same circular holder as the drawn ones.
   It goes in as an <img> rather than inline SVG on purpose: these files
   carry their own element ids (a, b, s, t) and xlink references, and
   three of them inlined into one document would collide on those ids —
   the second flag would start drawing pieces of the first. An image is
   its own document and cannot. */
.cflagx img{width:100%;height:100%;display:block;object-fit:cover}

/* The social buttons ask for place-items:center, which would centre the
   glyph both ways — on a grid. A broader rule for .f-grid a turns them
   into flex containers, and justify-items does nothing in flex, so the
   icon was pinned to the left edge and only looked centred vertically.
   justify-content is the flex spelling of the same intent. */
.f-social a{justify-content:center}

/* The closing frame gets its own photograph instead of borrowing use
   case 01. That one was a 1086x1448 portrait being stretched across a
   full-bleed landscape frame — about 1.4x at 1440px, nearly 3x on a
   retina screen, which is where the softness came from. This file is
   1885x834 and lands close to 1:1 at common widths.

   .ring-bg no longer carries the .ushot classes, so the frame styling
   those brought has to be restated here.

   background-position leans right: the composition puts the group on
   the right third and leaves dark carpet on the left, and the headline
   sits over the middle. Pulling the frame right keeps the faces clear
   of the type instead of centring them behind it. */
/* .ring-bg is a <video> now rather than a painted div. background-size
   and -position become object-fit and object-position; the scroll zoom
   already drives this element's scale and is untouched, which is why it
   kept the class name. */
.ring-bg{object-fit:cover;object-position:50% 50%;
  width:100%;height:100%;display:block;background:#080C16}
@media(max-width:900px){
  /* A narrow frame keeps roughly a third of the width, and the middle third of this picture is carpet — which is the point on desktop, where the headline sits over it. On a phone that crop is a
     photograph of a rug, so it moves off centre: 26% catches the woman with the phone and still leaves the type on the pillow behind her. */
  /* On a 390px portrait frame there is no crop of this landscape shot
     that keeps a readable phone screen clear of three centred lines of
     type. 62% is the compromise: hand, phone and laptop read as someone
     working at a desk, and the headline sits on the dark laptop rather
     than across the screen. */
  .ring-bg{object-position:50% 50%;transform:scale(1.0)}
}

/* The veil was mixed for the night shot this replaces — three stacked
   darkening layers, which on a warm, evenly lit picture reads as a
   photograph someone forgot to turn the lights on for. It still has to
   hold white type, so the bottom fade into the footer stays as it was
   and only the two layers over the middle come down. */
.ring-veil{
  background:
    linear-gradient(180deg,rgba(11,18,32,0) 62%,rgba(11,18,32,.55) 86%,
      #0B1220 100%),
    radial-gradient(120% 80% at 50% 46%,rgba(8,12,22,.10),rgba(8,12,22,.55)),
    linear-gradient(180deg,rgba(8,12,22,.42),rgba(8,12,22,.20) 40%,
      rgba(8,12,22,.62))}

/* ══ the scroll hint under the use-case heading ══
   A short rail with a dot falling down it, rather than a bouncing
   chevron: the gesture being asked for is a continuous scroll, not a
   tap, and a dot that keeps travelling in one direction reads that way.

   It lives inside .uses-head, so it inherits the sticky position and
   sits with the heading rather than scrolling away from it.

   aria-hidden because it is an instruction about a mouse wheel, which
   is meaningless read aloud — the content below it is reachable without
   this element existing. */
.uses-scroll{display:flex;flex-direction:column;align-items:center;gap:12px;
  margin-top:clamp(26px,3.2vw,44px);pointer-events:none}
.uses-scroll-t{font-family:var(--mono);font-size:10.5px;letter-spacing:.22em;
  text-transform:uppercase;color:#A8AEBA}
:is(html[lang^="zh"],html[lang^="ja"]) .uses-scroll-t{letter-spacing:.14em;font-size:11px}

.uses-scroll-rail{position:relative;display:block;width:1px;height:46px;
  background:linear-gradient(180deg,rgba(20,33,61,.16),rgba(20,33,61,0))}
.uses-scroll-rail i{position:absolute;left:50%;top:0;width:5px;height:5px;
  margin-left:-2.5px;border-radius:50%;background:var(--honey);
  animation:usesFall 2.1s var(--e) infinite}
@keyframes usesFall{
  0%   {transform:translateY(0);   opacity:0}
  18%  {opacity:1}
  72%  {opacity:1}
  100% {transform:translateY(40px);opacity:0}
}
@media(prefers-reduced-motion:reduce){
  .uses-scroll-rail i{animation:none;opacity:1}
}

/* the same hint on the dark closing frame. Only the rail's colour has
   to change: it fades a dark line into nothing, which on a dark field
   is invisible. The dot is already honey and reads on either. */
.uses-scroll.on-dark .uses-scroll-t{color:rgba(255,255,255,.45)}
.uses-scroll.on-dark .uses-scroll-rail{
  background:linear-gradient(180deg,rgba(255,255,255,.28),rgba(255,255,255,0))}

/* In the closing block the hint sits above the copy rather than under
   the button, so it needs its spacing on the other side. The rail keeps
   pointing down — it is indicating the direction to scroll, not the
   direction of the thing it is next to. */
/* The hint is a child of the frame rather than of the copy block, and
   pinned near the top of it. Inside the copy it could only sit as far up
   as the headline let it — the whole group is centred, so lifting the
   hint pushed the words down by half as much again. Out of that flow it
   can be placed on its own. */
#promise .uses-scroll{position:absolute;left:50%;z-index:2;margin:0;
  top:clamp(80px,14vh,170px);transform:translateX(-50%)}

/* ══ the video fills the column down to the last step card ══
   The frame had a fixed 6:5 ratio, so where it ended depended on the
   column's width rather than on the cards beside it — close to level at
   1440px and visibly out at anything else.

   It stretches instead. flex-basis 0 means the left column's intrinsic
   height is the heading alone, so the grid row is still sized by the
   three cards; the video then takes whatever is left. No circularity,
   and the two columns end on the same line at any width. */
@media(min-width:901px){
  /* The frame is square again rather than stretched to whatever height
     the step column happens to be. Once the steps lost their card
     padding that column got much shorter, and a stretched video came out
     as a letterbox strip. Now the picture sets the panel's height and
     the steps spread to meet it, which is the way round the reference
     has it. */
  /* The picture takes whatever height the step column leaves and crops
     top and bottom to fit — object-fit:cover was already doing that, the
     frame just was not allowed to be any shape but square. Locking it to
     a square meant the panel height came from the picture, and in
     English, where the heading runs to two lines and the steps are
     taller, the two columns could not both be satisfied. Now the steps
     set the height and the picture fills what is left. */
  .hw-body{align-items:stretch}
  .hw-left{display:flex;flex-direction:column}
  .hw-visual{flex:1 1 0;min-height:0;display:flex}
  .hw-video{aspect-ratio:auto;height:100%;min-height:clamp(320px,40vh,520px)}
}

/* the per-month figures in the rows are an average over the term, which
   the rows themselves have no room to say. Small, quiet, and inside the
   list so it cannot drift away from the numbers it qualifies. */
#numbers .cnote{margin:16px 4px 0;font-size:12px;line-height:1.7;
  color:#A8AEBA;text-align:right}
@media(max-width:900px){#numbers .cnote{text-align:left;margin:14px 2px 0}}

/* ══ three steps: the action leads, the number identifies ══
   The numeral was set at 68px and the step name at 15px grey, so the
   first thing read was "01" — which tells the reader nothing they did
   not already know from the order of the cards. The name is what they
   are looking for.

   So the two swap weight. The row becomes a column: a small monospaced
   number on top as a label, the action underneath at heading size in
   full-strength navy. Nothing moves in the markup; this is the same two
   elements re-ranked.

   The body copy keeps its two tiers — the sentence in <b> is the one
   that matters and stays at reading size, the rest drops a step. */
#howto .hw-top{flex-direction:column;align-items:flex-start;gap:10px;
  padding-bottom:18px}
#howto .hw-num{font-family:var(--mono);font-size:12px;font-weight:500;
  letter-spacing:.2em;line-height:1;color:#A8AEBA}
#howto .hw-label{font-size:clamp(21px,2.1vw,28px);font-weight:700;
  line-height:1.3;letter-spacing:-.01em;color:var(--hive);text-align:left}
:is(html[lang^="zh"],html[lang^="ja"]) #howto .hw-label{letter-spacing:0;line-height:1.4}

#howto .hw-copy{font-size:13.5px;line-height:1.8;color:#A8AEBA}
#howto .hw-copy b{display:block;margin-bottom:6px;font-size:15px;
  font-weight:600;line-height:1.6;color:var(--hive)}
:is(html[lang^="zh"],html[lang^="ja"]) #howto .hw-copy{font-size:13.5px;line-height:1.95}
:is(html[lang^="zh"],html[lang^="ja"]) #howto .hw-copy b{font-size:15px;line-height:1.7}

/* the phrase the note exists to deliver, lifted out of the sentence:
   two points larger and a good deal darker than the text around it, so
   it is legible at a glance without turning the whole line into a
   heading. */
#numbers .cnote b{font-size:13px;font-weight:600;color:#6B7386}

/* the outline button carries an arrow like the hero's, and the label is
   in a span so the language switch — which rewrites innerHTML — cannot
   take the arrow with it */
.btn.b-line svg{width:17px;height:17px;flex:none;margin-left:2px}
#numbers .cat-cta{display:flex;flex-wrap:wrap;gap:12px;align-items:center}

/* ══ how it works, rebuilt as one panel ══ */
@media(min-width:901px){
  /* The section is a single white card on the cream page rather than a
     bare column beside three smaller cards. One surface instead of four
     means the three steps read as one sequence. */
  #howto{padding-block:var(--sp4)}
  #howto .hw-body{background:#fff;border-radius:clamp(28px,2.6vw,40px);
    padding:clamp(38px,4vw,60px) clamp(34px,3.6vw,56px);
    box-shadow:0 1px 2px rgba(20,33,61,.04),
               0 30px 60px -40px rgba(20,33,61,.30);
    column-gap:clamp(40px,5vw,90px)}

  /* badge and lead share the top line, heading underneath — placed by
     grid rather than reordered in the markup, so the reading order for
     a screen reader is still badge, heading, lead. */
  #howto .hw-head{display:grid;grid-template-columns:auto minmax(0,1fr);
    column-gap:clamp(16px,1.8vw,28px);row-gap:14px;align-items:center;
    margin-bottom:clamp(24px,2.6vw,38px)}
  #howto .hw-head .badge{grid-column:1;grid-row:1;margin:0}
  #howto .hw-head p{grid-column:2;grid-row:1;margin:0;font-size:14.5px}
  #howto .hw-head h2{grid-column:1 / -1;grid-row:2;margin:0}

  /* the steps lose their boxes. On a white panel a white card with a
     hairline is a box drawn for no reason; a rule under each title does
     the same separating work. */
  #howto .hw-grid{gap:clamp(34px,4vw,64px);justify-content:center}
  #howto .hw-step{background:transparent;box-shadow:none;padding:0;
    border-radius:0}

  /* the numeral sits behind the name, in the page's own pale grey. It is
     an index, not a headline — large enough to mark the place, light
     enough that the eye lands on the words. */
  #howto .hw-top{position:relative;display:block;padding:0 0 14px;
    border-bottom:1px solid #EAECEF}
  /* everything in this column steps up a size: the column is the width
     of a comfortable measure and was set as if it were a sidebar. */
  #howto .hw-num{position:absolute;left:0;top:50%;z-index:0;
    transform:translateY(-56%);
    font-family:var(--display);font-size:clamp(74px,6.8vw,108px);
    font-weight:800;letter-spacing:-.05em;line-height:1;
    color:#E9ECF1}
  #howto .hw-label{position:relative;z-index:1;display:block;
    padding-left:clamp(44px,4vw,64px);text-align:left;
    font-size:clamp(25px,2.4vw,33px);font-weight:700;line-height:1.35;
    letter-spacing:-.01em;color:var(--hive)}
  :is(html[lang^="zh"],html[lang^="ja"]) #howto .hw-label{letter-spacing:0}

  #howto .hw-copy{margin-top:18px;padding-left:clamp(44px,4vw,64px);
    font-size:15px;line-height:1.85}
  #howto .hw-copy b{font-size:16.5px;line-height:1.6}
  :is(html[lang^="zh"],html[lang^="ja"]) #howto .hw-copy{font-size:15px;line-height:2}
  :is(html[lang^="zh"],html[lang^="ja"]) #howto .hw-copy b{font-size:16.5px;line-height:1.75}

  /* and the column fills the panel rather than sitting in the middle of
     it, so the first step lines up nearer the top and the last one
     reaches the foot */
  #howto .hw-grid{height:100%;justify-content:space-between}

}

/* The two white bands that used to sit at the top and bottom of the
   use-case block are gone with the exit fade — fading a card out against
   a gradient of the page colour was the same effect twice, and with the
   cards now leaving at full opacity the bands had nothing left to do but
   wash out whatever passed under them. Their rules stay in the sheet
   above; the element is no longer in the markup. */
.uses-veils{display:none}

/* ══ the same panel in English ══
   Latin runs far longer than the Chinese it was set against: the heading
   goes to two lines at 44px and the lead to two at full width, so the
   top of the column arrived as a wall of text with the badge lost in it.

   The heading comes down a size and is given a measure to break on, the
   lead is capped so it wraps where it is meant to, and the row aligns to
   the top so a two-line lead does not drag the badge down with it. */
@media(min-width:901px){
  #howto .hw-head{align-items:start}
  #howto .hw-head .badge{margin-top:4px}
  #howto .hw-head p{max-width:42ch;line-height:1.65}
  html[lang="en"] #howto .hw-head h2{font-size:clamp(30px,2.9vw,40px);
    max-width:15ch;line-height:1.18}
  html[lang="fil-PH"] #howto .hw-head h2{font-size:clamp(28px,2.7vw,38px);
    max-width:16ch;line-height:1.18}
}

/* ══ how it works: navy fading to white ══
   The section opens in the brand navy where it meets the white dome of
   the use-case block, and lightens down the height of the section until
   it is pure white at the foot, so it runs straight into the white
   catalogue below with no seam. The middle stops lean blue rather than
   grey — a straight navy-to-white mix passes through a flat slate that
   reads as dirty. A faint lighter lift near the top left keeps the dark
   end from being a flat fill. */
#howto{position:relative;
  background:
    radial-gradient(110% 45% at 18% 0%,rgba(60,86,140,.40) 0%,rgba(60,86,140,0) 62%),
    linear-gradient(180deg,#14213D 0%,#1C2E54 18%,#3A5486 40%,
      #8EA2C8 64%,#D6DEEC 84%,#FFFFFF 100%)}

/* on a dark field the panel's navy-tinted shadow disappears; a deeper,
   neutral one keeps the white card lifted off it */
@media(min-width:901px){
  /* kept short and light: the panel ends about 70px above the foot of
     the section, and a longer shadow ran past that edge and was cut off
     in a straight line where the white catalogue section begins */
  #howto .hw-body{box-shadow:0 1px 2px rgba(11,18,34,.06),
    0 22px 44px -26px rgba(11,18,34,.18)}
}

/* below 901px the heading sits on the section itself, not inside the
   white panel, so it has to turn light; the step cards stay white */
@media(max-width:900px){
  #howto .hw-head h2{color:#fff}
  #howto .hw-head p{color:rgba(255,255,255,.68)}
  #howto .hw-head .badge{background:rgba(255,255,255,.10);color:#fff;
    box-shadow:inset 0 0 0 1px rgba(255,255,255,.14)}
  #howto .hw-step{box-shadow:inset 0 0 0 1px #ECEDEF,0 18px 36px -24px rgba(11,18,34,.35)}
}


/* ══ the dome at the foot of the use-case block, over a dark field ══
   It used to fade its opacity down with its scale, so that the
   drop-shadow of a flattened, zero-height shape could not leave a
   hairline across the page. On cream a half-transparent white dome is
   invisible; on the navy that now sits below it, it came out as a grey
   band across the whole width. The shape stays solid white and only the
   shadow fades with the scale, which still leaves nothing behind at zero. */
.trust-arc{opacity:1;
  filter:drop-shadow(0 3px 9px rgba(20,33,61,calc(.10 * var(--arc,1))))}


/* ══ gradients on every solid navy fill ══
   The navy blocks were flat #14213D. Each now runs top to bottom, from
   a lighter navy along the top edge through the flat value to a step
   darker at the foot — light always above, the way light falls on a
   surface — so the colour is the same brand navy at a glance but the
   surface has some light on it.

   Only background-image is set, never the background shorthand, so the
   solid colour underneath stays as the fallback. Each selector matches
   the rule that currently wins for that element, and sits later in the
   sheet, so it applies without !important. Translucent badges (on dark
   sections, and in the mobile how-it-works heading) use the shorthand in
   more specific rules and are left alone. */
:root{
  --grad-navy-card:linear-gradient(180deg,#2A3F70 0%,#1D2F57 34%,#14213D 70%,#0F192F 100%);
  --grad-navy-pill:linear-gradient(180deg,#2F4679 0%,#1C2D53 50%,#14213D 100%);
  --grad-navy-btn:linear-gradient(180deg,#2C4374 0%,#1A2B50 50%,#14213D 100%);
  --grad-navy-btn-hover:linear-gradient(180deg,#223663 0%,#14213D 55%,#0E182D 100%);
}

/* section labels */
.badge{background-image:var(--grad-navy-pill)}

/* the four reason cards */
.wcu-card{background-image:var(--grad-navy-card)}

/* the support card at the foot of the FAQ */
section#faq .faq-card{background-image:var(--grad-navy-card)}

/* the plans section, and the member card inside it. The card starts a
   touch lighter than the field so the two do not merge at its edge. */
#plans.cta{background-image:
  radial-gradient(80% 42% at 50% 30%,rgba(58,84,134,.32) 0%,rgba(58,84,134,0) 70%),
  linear-gradient(180deg,#1A2B50 0%,#14213D 48%,#0E182E 100%)}
.plan-member{background-image:linear-gradient(180deg,#2E4577 0%,#1D2F57 38%,#14213D 72%,#101A30 100%)}

/* navy buttons and selected pills */
.b-ink,.plan-free .plan-cta,
.cat-tabs button[aria-selected="true"],.aic-pick.on{background-image:var(--grad-navy-btn)}
.b-ink:hover,.plan-free .plan-cta:hover{background-image:var(--grad-navy-btn-hover)}

/* the footer starts on #0B1220, the colour the closing frame ends on, so
   the join stays invisible; it lifts slightly towards the foot */
footer{background-image:linear-gradient(180deg,#0B1220 0%,#0E182C 45%,#16254A 100%)}


/* ══ how it works: smaller numerals, clear of the rule ══
   The numerals were set at up to 108px and centred on the title row, so
   their lower half ran through the hairline under each title and the
   digit sat behind the first letters of the heading. They are now about
   half that size and stand in the gutter to the left of the title,
   sitting on roughly the title's baseline, well clear of the rule — the same bottom edge for all
   three, whatever the title's height. Still the pale grey index they
   were; only the size and the anchor changed. */
@media(min-width:901px){
  #howto .hw-num{top:auto;bottom:16px;transform:none;
    font-size:clamp(40px,3.6vw,56px);line-height:1}
}


/* ══ why Bees Mobile: a honey gradient behind the section ══
   The section had no background of its own and showed the cream page.
   It now opens white, level with the white catalogue above it, so there
   is no seam at the top, and warms only slightly down the height of the
   section — the lightest end of the gold ramp, never past a pale cream
   (#FDEFD6) at the foot, where the navy plans block takes over. A tint,
   not a colour. A faint warmer glow sits
   behind the heading so the centre of the section is not a flat band.
   The navy cards and the headline read at full contrast on every stop;
   the lead paragraph stays a step darker than the page's usual grey. */
#whyus{position:relative;
  background:
    radial-gradient(70% 55% at 50% 38%,rgba(252,235,199,.28) 0%,rgba(252,235,199,0) 70%),
    linear-gradient(180deg,#FFFFFF 0%,#FFFCF6 30%,#FEF6E6 65%,#FDEFD6 100%)}
#whyus .wcu-head p{color:#555D70}


/* ══ curved seams around the plans block ══
   Top edge: the plans block rises into the honey section with a dome of
   its own navy bulging up above its top edge, and the dome flattens as
   the block arrives — the same shape, size and timing as the white dome
   the use-case block rises over the hero with (.sec-arc). #1A2B50 is the
   plans gradient's first stop; the glow in that gradient was moved down
   off the top edge so the edge is one flat value the dome can match.

   Bottom edge: the navy foot of the plans block hangs down into the
   white FAQ as a dome of #0E182E, that gradient's last stop, and
   flattens as the FAQ scrolls up. It sits in a clip box that starts on
   the section's bottom edge, so neither the shape nor its shadow can
   reach back up over the navy.

   --arc on both is written by the script at the foot of the page. */
#plans{position:relative;z-index:2}
.seam-arc-up{position:absolute;left:50%;bottom:calc(100% - 1px);z-index:0;
  width:124%;height:clamp(64px,8vw,136px);pointer-events:none;
  transform:translateX(-50%) scaleY(var(--arc,1));transform-origin:50% 100%;
  border-radius:50% 50% 0 0 / 100% 100% 0 0;
  background:#1A2B50;will-change:transform}
.seam-arc-clip{position:absolute;left:-13%;right:-13%;top:calc(100% - 1px);
  height:clamp(78px,9.5vw,168px);overflow:hidden;pointer-events:none;z-index:2}
.seam-arc{position:absolute;left:50%;top:0;display:block;
  width:98%;height:clamp(52px,6.5vw,116px);
  transform:translateX(-50%) scaleY(var(--arc,1));transform-origin:50% 0;
  border-radius:0 0 50% 50% / 0 0 100% 100%;
  background:var(--seam,#fff);will-change:transform}
.seam-arc.to-white{--seam:#0E182E;
  filter:drop-shadow(0 6px 14px rgba(11,18,34,calc(.16 * var(--arc,1))))}
@media(prefers-reduced-motion:reduce){.seam-arc,.seam-arc-up{--arc:0!important}}


/* ══ the four reason icons move a little ══
   Each one does the thing it stands for, quietly and on a loop:
     · carrier lines — the two pairs of signal waves light in turn,
       inner then outer, like a mast broadcasting;
     · simple to manage — the two slider knobs glide along their tracks
       in opposite directions (the tracks are now whole lines, drawn
       fainter, with solid knobs riding on them);
     · clear pricing — the coin turns over once every few seconds;
     · support — the three dots in the bubble hop in sequence, the usual
       someone-is-typing signal.
   Movement is a few units inside a 24-unit icon, so it reads as life
   rather than as something asking to be clicked. On hover the round
   badge warms toward honey and grows slightly.

   The loops pause while the section is off screen (the script at the
   foot of the page adds .wcu-paused) and are removed for readers who
   have asked for reduced motion. */
.wcu-ico{transition:background-color .35s var(--e),transform .35s var(--e)}
.wcu-card:hover .wcu-ico{background-color:rgba(240,165,0,.16);transform:scale(1.07)}

.ico-signal .wv-in{animation:icoWave 2.6s ease-in-out infinite}
.ico-signal .wv-out{animation:icoWave 2.6s ease-in-out .4s infinite}
@keyframes icoWave{0%,100%{opacity:.3}35%,55%{opacity:1}}

.ico-sliders .trk{opacity:.45}
.ico-sliders .kn{transform-box:fill-box;transform-origin:center}
.ico-sliders .kn-a{animation:knobA 3.4s cubic-bezier(.65,0,.35,1) infinite}
.ico-sliders .kn-b{animation:knobB 3.4s cubic-bezier(.65,0,.35,1) infinite}
@keyframes knobA{0%,12%,100%{transform:translateX(0)}50%,62%{transform:translateX(-6px)}}
@keyframes knobB{0%,12%,100%{transform:translateX(0)}50%,62%{transform:translateX(6px)}}

.ico-coin svg{animation:coinTurn 4.2s ease-in-out 1s infinite;backface-visibility:visible}
@keyframes coinTurn{
  0%,64%{transform:perspective(160px) rotateY(0deg)}
  86%,100%{transform:perspective(160px) rotateY(360deg)}}

.ico-chat .dt{transform-box:fill-box;transform-origin:center;
  animation:dotHop 1.5s ease-in-out infinite}
.ico-chat .dt2{animation-delay:.18s}
.ico-chat .dt3{animation-delay:.36s}
@keyframes dotHop{0%,55%,100%{transform:translateY(0);opacity:.55}
  25%{transform:translateY(-2px);opacity:1}}

#whyus.wcu-paused .wcu-ico *,#whyus.wcu-paused .wcu-ico svg{animation-play-state:paused}
@media(prefers-reduced-motion:reduce){
  .wcu-ico,.wcu-ico *{animation:none!important;transition:none!important}
  .wcu-card:hover .wcu-ico{transform:none}
}


/* ══ catalogue tabs: an iOS-style segmented control ══
   The selected fill used to jump from one button to the other. It is now
   one sliding thumb behind both labels, the way an iPhone segmented
   control works:
     · switching slides the thumb across on a spring — it travels, runs a
       few percent past the target and settles — and resizes to the new
       label's width on the same curve;
     · pressing and holding the selected segment shrinks the thumb a
       little, the "picked up" state; pressing the other one dims its
       label until release;
     · the thumb can be dragged: it follows the finger, the labels turn
       white exactly where the thumb covers them, and on release it
       springs into the nearest segment and selects it.
   The thumb is added by the script, so without JS the buttons keep their
   own fill (the rules above) and still work. Everything here only
   applies once the control carries .has-thumb.

   The spring is a linear() curve sampled from a damped spring (about 4%
   overshoot, settled in 0.6s); browsers without linear() get a
   cubic-bezier with a similar small overshoot. */
.cat-tabs.has-thumb{position:relative;isolation:isolate;
  -webkit-user-select:none;user-select:none;touch-action:pan-y}
.cat-tabs.has-thumb button,
.cat-tabs.has-thumb button[aria-selected="true"]{position:relative;z-index:1;
  background:transparent;background-image:none;color:#646C7F;
  transition:color .2s var(--e),opacity .2s var(--e)}
.cat-tabs.has-thumb button:hover{color:var(--hive)}
.cat-tabs.has-thumb button.is-held{opacity:.5}

/* The thumb is one layer: a copy of the labels in white on the navy
   fill, laid exactly over the grey labels and cut to the thumb's shape
   with clip-path. Moving the thumb means moving the clip, so the fill and
   the white text cannot drift apart for even a frame, and a label half
   under the thumb is half white and half grey — as on an iPhone. The
   drop shadow is on a wrapper, so it follows the clipped shape too.

   --tx and --tw are the thumb's left edge and width in px, written by the
   script; --tp is how far a press draws it in. */
.cat-thumb{position:absolute;inset:0;z-index:2;pointer-events:none;
  filter:drop-shadow(0 1px 1.5px rgba(11,18,34,.20)) drop-shadow(0 5px 8px rgba(11,18,34,.22))}
/* the spring runs the thumb a few px past its target; at either end of
   the track that would push it out over the rim, so a pill-shaped box the
   size of the track's inside holds it in — at the ends it presses into
   the wall and comes back, instead of poking through it */
.cat-clamp{position:absolute;top:0;bottom:0;left:4px;right:4px;
  overflow:hidden;border-radius:999px}
.cat-lit{position:absolute;top:0;bottom:0;left:-4px;right:-4px;
  background:var(--hive);background-image:var(--grad-navy-btn);
  clip-path:inset(calc(4px + var(--tp,0px))
    calc(100% - var(--tx,0px) - var(--tw,0px) + var(--tp,0px))
    calc(4px + var(--tp,0px)) calc(var(--tx,0px) + var(--tp,0px)) round 999px);
  transition:clip-path .6s cubic-bezier(.3,1.25,.5,1)}
@supports (transition-timing-function:linear(0,1)){
  .cat-lit{transition:clip-path .6s linear(0, 0.059, 0.194, 0.359, 0.524, 0.672, 0.793, 0.886, 0.952, 0.996, 1.022, 1.035, 1.038, 1.036, 1.031, 1.025, 1.019, 1.013, 1.008, 1.005, 1.002, 1, 0.999, 0.999, 1)}
}
.cat-lit span{position:absolute;display:flex;align-items:center;justify-content:center;
  white-space:nowrap;color:#fff;font-family:var(--display);font-size:14px;
  font-weight:600;letter-spacing:-.015em;line-height:1.3}

/* pressing the selected segment draws the thumb in by 3px all round,
   quickly and without the spring. It is the clip that shrinks, not a
   scale, so the white text stays glyph-for-glyph over the grey text. */
.cat-tabs.is-pressing .cat-lit{--tp:3px;transition:clip-path .16s ease-out}
/* while dragging it follows the pointer exactly */
.cat-tabs.is-dragging .cat-lit{transition:none}
/* the first placement, and re-measuring after a language change, snap */
.cat-tabs.no-anim .cat-lit{transition:none}

@media(prefers-reduced-motion:reduce){
  .cat-lit,.cat-tabs.has-thumb button{transition:none!important}
  .cat-tabs.is-pressing .cat-lit{--tp:0px}
}


/* ══ use-case photos keep their people in frame ══
   On a wide screen the frame is square and the photos are 3:4, so cover
   crops a quarter of their height. Centred, that crop took the tops off
   the heads in several of them — the people all sit in the upper third.
   Anchoring near the top keeps every face whole whether or not the
   scroll drift runs (it moves between 24% and 0%; see the script). The
   tall 3:4 frames below 901px show the whole photo and are unaffected. */
@media(min-width:901px){
  #trust .ushot{background-position:50% 10%}
}


/* ══ section labels: small text instead of a navy pill ══
   Every section label was a solid navy capsule with a blinking dot.
   Beside the navy cards and buttons it was one more dark shape on the
   screen, it looked pressable, and it outranked headings that already
   say what each section is about. The label is now what the hero
   eyebrow and the FAQ group names already are on this page: small
   monospaced capitals in gold, letter-spaced, with a still gold dot in
   front. It marks where you are on a long page and leaves the heading
   to be the first thing read.

   Deep gold #845B00 on light fields (the brand gold is 2.2:1 on white
   and fails as text); the brand gold on dark ones — the plans block,
   the compare block, and the how-it-works heading on mobile, which sits
   on the navy end of that section. Chinese is not uppercased and takes
   the display face with a little less tracking. The long list of
   selectors is there to match the specificity of each old pill rule. */
.badge,
.cta .badge,
section#compare .badge,
#howto .hw-head .badge{
  background:none;background-image:none;box-shadow:none;
  padding:0;border-radius:0;gap:8px;
  font-family:var(--mono);font-size:12px;font-weight:500;line-height:1.4;
  letter-spacing:.16em;text-transform:uppercase;color:#845B00}
.badge::before{width:6px;height:6px;flex:none;background:var(--honey);animation:none}

.cta .badge,
section#compare .badge{color:var(--honey)}
@media(max-width:900px){
  #howto .hw-head .badge{color:var(--honey)}
}

:is(html[lang^="zh"],html[lang^="ja"]) .badge,
:is(html[lang^="zh"],html[lang^="ja"]) .cta .badge,
:is(html[lang^="zh"],html[lang^="ja"]) section#compare .badge,
:is(html[lang^="zh"],html[lang^="ja"]) #howto .hw-head .badge{
  font-family:var(--display);font-size:13px;font-weight:600;
  letter-spacing:.12em;text-transform:none}

/* a label this small sits closer to its heading */
.uses-head .badge + h2,.hw-head .badge + h2,.wcu-head .badge + h2,
.cta .badge + h2{margin-top:14px}
@media(min-width:901px){
  #trust .uses-head .badge + h2{margin-top:14px}
}


/* ══ how it works: no label, heading first, lead underneath ══
   The "How it works" label is gone from this section; the heading says
   the same thing. Heading and lead now stack in reading order, both
   flush left in the left column — the heading on top, the lead as its
   subtitle directly under it. This replaces the earlier grid that put
   the label and the lead side by side on one line above the heading.
   The lead takes a normal body size again now that it is a subtitle,
   not a side note squeezed next to a label. */
#howto .hw-head{display:block;text-align:left}
#howto .hw-head h2{margin:0}
#howto .hw-head p{margin:14px 0 0;font-size:16px;line-height:1.7;max-width:none}
/* the lead is one sentence; it used to be capped at 42ch, which broke
   "all of it online." onto a second line with room to spare. Uncapped,
   it runs the width of the column and only wraps where the column is
   genuinely too narrow. */
:is(html[lang^="zh"],html[lang^="ja"]) #howto .hw-head p{font-size:16px;line-height:1.85;max-width:30em}


/* ══ hero: a slideshow instead of a pinned scroll track ══
   The hero was a 380vh track with the panel pinned inside it, and the
   use-case block was pulled up a full screen to slide over its last
   viewport. Both are undone: the hero is one screen tall and scrolls
   away normally, and the next section simply follows it. The panels
   rotate on a timer (the script at the foot of the page). */
@media(min-width:901px){
  .hero-h{height:auto}
  .hero-s{position:relative;top:auto;height:100svh;min-height:640px;
    transform:none!important;will-change:auto}
  .cut-veil{display:none}
  #trust{margin-top:0;min-height:0}
}

/* on a phone the four panels used to be stacked as four blocks, so the
   reader scrolled through all of them before the next section. They
   share one slot now, like the desktop, and the tallest panel sets the
   height so nothing below jumps as they change. */
@media(max-width:900px){
  .hero-text{display:grid;gap:0}
  .hero .hp{grid-area:1/1;padding-block:0;justify-content:flex-start;
    opacity:0;transform:translateY(14px);visibility:hidden;pointer-events:none;
    transition:opacity .5s var(--e),transform .5s var(--e),visibility 0s .5s}
  .hero .hp.on{padding-top:0;opacity:1;transform:none;visibility:visible;pointer-events:auto;
    transition:opacity .5s var(--e),transform .5s var(--e),visibility 0s}
  .hero .hp + .hp{border-top:0}
  .hero .hp .hero-cta{display:flex}
  .hero-rail{display:block;position:relative;bottom:auto;margin:30px 0 34px}
  .hero-s{touch-action:pan-y}
}

/* the bars: the active one fills over the slide's time */
.hero-rail .wrap{display:flex;align-items:center;gap:14px}
.hd-bars{gap:8px}
.hero-rail .hd{position:relative;overflow:hidden;height:4px;cursor:pointer}
.hero-rail .hd::before{content:"";position:absolute;inset:-10px -3px}   /* larger hit area */
.hero-rail .hd.on{background:rgba(255,255,255,.26);width:52px}
.hero-rail .hd.on::after{content:"";position:absolute;inset:0;border-radius:inherit;
  background:var(--honey);transform-origin:0 50%;
  animation:heroFill var(--hero-dur,6500ms) linear forwards}
@keyframes heroFill{from{transform:scaleX(0)}to{transform:scaleX(1)}}
.hero.is-held .hero-rail .hd.on::after{animation-play-state:paused}
.hero.is-stopped .hero-rail .hd.on::after{animation:none;transform:none}
.hero-rail .hd:focus-visible{outline:2px solid var(--honey);outline-offset:4px}

/* previous / next and pause share one round glass button style; the
   arrows are the pair a reader reaches for, so they sit first and a
   little larger, and pause follows after a gap */
.hero-pager{display:inline-flex;gap:8px;margin-left:6px}
.hero-btn,.hero-pause{display:grid;place-items:center;padding:0;border:0;
  border-radius:50%;cursor:pointer;color:#fff;
  background:rgba(9,15,28,.28);
  -webkit-backdrop-filter:blur(8px);backdrop-filter:blur(8px);
  box-shadow:inset 0 0 0 1px rgba(255,255,255,.30);
  transition:background-color .25s var(--e),transform .25s var(--e),box-shadow .25s var(--e)}
.hero-btn{width:40px;height:40px}
.hero-pause{width:32px;height:32px;margin-left:4px}
.hero-btn:hover,.hero-pause:hover{background:rgba(255,255,255,.22);
  box-shadow:inset 0 0 0 1px rgba(255,255,255,.55)}
.hero-btn:active{transform:scale(.92)}
.hero-btn:focus-visible,.hero-btn svg{width:18px;height:18px;fill:none;stroke:currentColor;
  stroke-width:2.2;stroke-linecap:round;stroke-linejoin:round}
.hero-prev:hover svg{transform:translateX(-2px)}
.hero-next:hover svg{transform:translateX(2px)}
.hero-btn svg{transition:transform .25s var(--e)}
.hero-pause svg{width:12px;height:12px;fill:none;stroke:currentColor;
  stroke-width:2.6;stroke-linecap:round;stroke-linejoin:round}
.hero-pause .i-play{display:none;fill:currentColor;stroke-width:1.6}
.hero-pause.is-paused .i-play{display:block}
.hero-pause.is-paused .i-pause{display:none}

@media(prefers-reduced-motion:reduce){
  .hero-rail .hd.on::after{animation:none;transform:none}
}


/* ══ breathing room between the reason cards and the plans block ══
   The cards ended close to the section's foot and the navy dome of the
   plans block rose to within 18px of them. The section gets extra space
   at the bottom, and the dome now stops 56px short of the cards (see
   the seam script), so a clear band of the pale field always separates
   the two. */
#whyus{padding-bottom:calc(var(--sp5) + clamp(36px,4.5vw,72px))}


/* ══ hero controls sit on top of the progress bars ══
   The arrows and pause were in one line to the right of the bars. They
   now form their own row directly above the bars, both flush left with
   the copy: buttons first, the bars underneath as their caption. The
   rail is anchored at its bottom edge, so the bars stay exactly where
   they were and the buttons take the space above them. */
.hero-rail .wrap{flex-direction:column;align-items:flex-start;gap:16px}
.hero-pager{order:0;margin-left:0;align-items:center}
.hero-rail .hd-bars{order:1}
.hero-pause{margin-left:6px}


/* ══ the hero keeps room for its controls ══
   With the buttons stacked over the bars the control block is 60px tall,
   anchored above the carrier band. On a short window (720-760px) the
   longest panel's buttons ran into it. Two things were eating the
   height: the right-hand column still reserved 620px for the ring even
   though the ring is hidden, and the copy was centred in that inflated
   grid rather than in the space that was actually free.

   The empty column now takes no height, and the grid's bottom padding
   is exactly the control block plus a gap, so the copy is centred
   between the nav and the controls. If a panel needs more height than
   the window has, the hero grows instead of letting the two overlap. */
@media(min-width:901px){
  .hero-vis{height:auto}
  .hero-s{height:auto;min-height:max(640px,100svh);padding:0}
  .hero-grid{padding-top:96px;
    padding-bottom:calc(clamp(56px,7vh,72px) + 20px + 32px + 32px)}
}


/* ══ server-room slide: pulled back so the pills clear the engineer ══
   The photo was zoomed to 1.18 and lifted 5% on the layer, which put the
   kneeling engineer's head right under the stack of message pills at the
   lower right. It is zoomed out now, and framed so both faces sit in the
   gap between the copy and the pills rather than under either.

   The photo is 1.75:1, so which way it has room to move depends on the
   window. On windows wider than that the crop comes from the bottom of
   the picture and the layer rises 3%, which lifts the engineer's head
   above the top of the pills; on narrower ones the crop comes from the
   right and the layer shifts 2% right, which puts her head just left of
   them. Both were fitted against the measured positions of the headline,
   the lead, the buttons and the pills at 1180-1920px wide.
   (Shown scale first, then the small settle every slide makes on entry.) */
.bgstage .px-room{background-position:50% 100%}
.bgstage .bgshot.px-room.on{transform:scale(1.08) translate(-3%,-3%)}
.bgstage .bgshot.px-room{transform:scale(1.14) translate(-3%,-3%)}
@media (max-aspect-ratio:1753/1000){
  .bgstage .px-room{background-position:100% 50%}
  .bgstage .bgshot.px-room.on{transform:scale(1) translate(2%,0)}
  .bgstage .bgshot.px-room{transform:scale(1.06) translate(2%,0)}
}


/* ══ Paris slide: the photo is reframed; the pills stay where they are ══
   The five faces sit in the lower right of this photograph, where the
   message pills are on every slide. Only the picture moves: it is
   zoomed to 1.25, anchored to its bottom edge, and the layer is lifted
   9% and shifted 3% left, which carries the group up and away from the
   pills. Fitted against the measured headline, lead, buttons and pill
   stack at eight window sizes from 1180 to 1920px wide: at 1901x864 the
   faces overlap the pill column's box by about 5% of their area (it was
   43%), and that sliver is at the box's left edge, where most pills —
   right-aligned and shorter than the box — do not reach. */
.bgstage .px-friends{background-position:40% 100%}
.bgstage .bgshot.px-friends.on{transform:scale(1.25) translate(-3%,-9%)}
.bgstage .bgshot.px-friends{transform:scale(1.31) translate(-3%,-9%)}


/* ══ plan buttons on one line ══
   Both cards push their actions to the foot, but the member card has a
   "How the rewards plan works" link under its button, so its button sat
   28px higher than the free card's. The link gets a fixed line height,
   and while the two cards stand side by side the free card keeps an
   empty slot of the same height under its button — the two buttons
   share a baseline, and so do the card bottoms. Stacked on a phone the
   slot is dropped. */
/* (the link has since moved up beside the referral item, so the actions
   of both cards are a single button and line up without a spacer) */


/* ══ member card, rearranged ══
   · the small print about activating a number and the non-refundable
     fee now sits under "One-time joining fee" inside the price box, next
     to the price it qualifies;
   · the limited-time waiver moves below the benefit list, directly above
     the button it applies to at checkout;
   · "How the rewards plan works" follows the referral-rewards benefit
     instead of hanging under the button. */
.plan-member .plan-price{align-items:flex-start}
.plan-price-meta{display:flex;flex-direction:column;align-items:flex-end;gap:6px;
  text-align:right;max-width:62%}
.plan-member .plan-price .plan-price-note{display:block;font-size:11.5px;font-weight:400;
  line-height:1.6;color:#8A91A0}
:is(html[lang^="zh"],html[lang^="ja"]) .plan-member .plan-price .plan-price-note{font-size:12px;line-height:1.7}

.plan-member .plan-list + .plan-waive{margin-top:22px;margin-bottom:24px}

.plan-li-txt{display:inline}
.plan-more-inline{display:inline;margin-left:6px;font-size:13px;line-height:inherit;
  white-space:nowrap;color:var(--honey)}
.plan-more-inline:hover{text-decoration:underline;text-underline-offset:3px}


/* ══ floating support: iPhone-style material and motion ══
   The button and its panel are rebuilt as iOS controls rather than flat
   fills:
     · the button is honey glass — a translucent tint over a background
       blur, a specular highlight across its top half, a hairline inner
       rim and a soft two-layer shadow. Pressing it squeezes it to 94%,
       and it springs back when released;
     · opening morphs the button instead of swapping it: the label folds
       away while the chat bubble turns and fades into a close cross, and
       the pill closes to a circle on the same spring;
     · the panel is frosted white glass (blur plus saturation, like an
       iOS sheet). It grows out of the button — scaling up from the
       button's corner, coming into focus from a slight blur — and its
       contents follow a beat apart;
     · the two actions are an iOS grouped list: one rounded group, a
       hairline between the rows inset past the icon, a chevron, and a
       grey press state.
   Closing runs quicker and without the overshoot, as iOS does. Browsers
   without backdrop-filter get near-opaque fills instead of glass, and
   reduced motion keeps the fades but drops scale, blur and spring. */
.help{--spring:cubic-bezier(.3,1.25,.5,1);
  transition:opacity .35s ease,transform .6s var(--spring)}
@supports (transition-timing-function:linear(0,1)){ .help{--spring:linear(0, 0.059, 0.194, 0.359, 0.524, 0.672, 0.793, 0.886, 0.952, 0.996, 1.022, 1.035, 1.038, 1.036, 1.031, 1.025, 1.019, 1.013, 1.008, 1.005, 1.002, 1, 0.999, 0.999, 1)} }
.help:not(.show){transform:translateY(18px) scale(.9)}

/* ── the button ── */
.help .help-btn{position:relative;isolation:isolate;overflow:hidden;
  display:inline-flex;align-items:center;gap:0;height:48px;padding:0 19px 0 15px;
  border:0;border-radius:999px;cursor:pointer;color:#241A02;
  font-family:var(--display);font-size:14.5px;font-weight:600;letter-spacing:-.01em;
  background:linear-gradient(180deg,rgba(255,204,71,.90) 0%,rgba(240,165,0,.90) 100%);
  -webkit-backdrop-filter:blur(18px) saturate(180%);backdrop-filter:blur(18px) saturate(180%);
  box-shadow:
    inset 0 1px 0 rgba(255,255,255,.70),
    inset 0 0 0 .5px rgba(255,255,255,.35),
    inset 0 -1px 1px rgba(122,72,0,.20),
    0 1px 2px rgba(20,33,61,.14),
    0 12px 30px -10px rgba(20,33,61,.42);
  -webkit-tap-highlight-color:transparent;
  transition:transform .55s var(--spring),padding .55s var(--spring),
             box-shadow .3s ease,filter .2s ease}
.help .help-btn::before{content:"";position:absolute;z-index:-1;left:6%;right:6%;top:1px;height:52%;
  border-radius:999px 999px 60% 60% / 100% 100% 40% 40%;pointer-events:none;
  background:linear-gradient(180deg,rgba(255,255,255,.55),rgba(255,255,255,0))}
.help .help-btn:hover{background:linear-gradient(180deg,rgba(255,211,92,.94) 0%,rgba(245,172,10,.94) 100%);
  transform:translateY(-1px)}
.help .help-btn:active{transform:scale(.94);filter:brightness(.97);
  transition:transform .12s ease-out,padding .55s var(--spring),filter .12s ease-out}
.help .help-btn:focus-visible{outline:2px solid var(--navy);outline-offset:3px}

.help-ic{display:grid;width:20px;height:20px;flex:none}
.help .help-btn .help-ic svg{grid-area:1/1;display:block;width:20px;height:20px;
  transition:opacity .22s ease,transform .55s var(--spring)}
.help .help-btn .help-close{display:block;opacity:0;transform:rotate(-90deg) scale(.5)}
.help.open .help-btn .help-open{display:block;opacity:0;transform:rotate(90deg) scale(.5)}
.help.open .help-btn .help-close{display:block;opacity:1;transform:none}

.help .help-label{display:inline-block;overflow:hidden;white-space:nowrap;
  max-width:140px;margin-left:8px;opacity:1;
  transition:max-width .55s var(--spring),margin .55s var(--spring),opacity .2s ease}
.help.open .help-label{display:inline-block;max-width:0;margin-left:0;opacity:0}
.help.open .help-btn{padding:0 14px}
@media(max-width:560px){
  .help .help-label{max-width:0;margin-left:0;opacity:0}
  .help .help-btn{padding:0 14px}
}

/* ── the panel ── */
.help .help-panel{position:relative;width:min(320px,calc(100vw - 32px));
  padding:20px 16px 14px;border-radius:28px;
  background:rgba(250,250,252,.74);
  -webkit-backdrop-filter:blur(30px) saturate(190%);backdrop-filter:blur(30px) saturate(190%);
  box-shadow:
    inset 0 0 0 .5px rgba(255,255,255,.75),
    0 0 0 .5px rgba(20,33,61,.10),
    0 2px 6px rgba(20,33,61,.06),
    0 28px 64px -14px rgba(20,33,61,.34);
  transform-origin:calc(100% - 24px) calc(100% + 30px);
  opacity:0;transform:translateY(10px) scale(.86);filter:blur(8px);
  /* closing is the opening played backwards, a little quicker: the panel
     shrinks toward the button and fades on the same beat. It used to fade
     out in .18s against a curve that barely moved for its first third,
     so it was invisible before it had travelled and read as a cut. */
  transition:opacity .26s ease .02s,
             transform .3s cubic-bezier(.2,.6,.35,1),
             filter .26s ease}
.help.open .help-panel{opacity:1;transform:none;filter:none;
  transition:opacity .25s ease,transform .6s var(--spring),filter .35s ease}
@supports not ((-webkit-backdrop-filter:blur(1px)) or (backdrop-filter:blur(1px))){
  .help .help-panel{background:rgba(250,250,252,.98)}
  .help .help-btn{background:linear-gradient(180deg,#FFCC47,#F0A500)}
}

.help .help-panel > *{opacity:0;transform:translateY(6px);
  transition:opacity .18s ease,transform .24s cubic-bezier(.32,0,.5,1)}
.help.open .help-panel > *{opacity:1;transform:none;
  transition:opacity .35s ease,transform .6s var(--spring)}
.help.open .help-panel > :nth-child(1){transition-delay:.05s}
.help.open .help-panel > :nth-child(2){transition-delay:.09s}
.help.open .help-panel > :nth-child(3){transition-delay:.13s}
.help.open .help-panel > :nth-child(4){transition-delay:.17s}
.help.open .help-panel > :nth-child(5){transition-delay:.21s}

.help .help-title{font-size:17px;font-weight:700;letter-spacing:-.02em;color:#0B1222;padding:0 4px}
.help .help-sub{margin-top:6px;padding:0 4px;font-size:13px;line-height:1.6;color:rgba(60,60,67,.66)}

.help .help-item{position:relative;display:flex;align-items:center;gap:12px;
  margin-top:0;padding:11px 14px 11px 12px;border-radius:0;
  background:rgba(255,255,255,.82);font-size:15px;font-weight:500;letter-spacing:-.01em;color:#0B1222;
  -webkit-tap-highlight-color:transparent;transition:background-color .15s ease}
.help .help-item:first-of-type{margin-top:16px;border-radius:16px 16px 0 0}
.help .help-item:last-of-type{border-radius:0 0 16px 16px}
.help .help-item:first-of-type:last-of-type{border-radius:16px}
.help .help-item + .help-item::before{content:"";position:absolute;top:0;right:0;left:54px;
  height:.5px;background:rgba(60,60,67,.22)}
.help .help-item::after{content:"";margin-left:auto;width:7px;height:7px;flex:none;
  border-top:1.8px solid rgba(60,60,67,.32);border-right:1.8px solid rgba(60,60,67,.32);
  transform:rotate(45deg);margin-right:3px}
.help .help-item:hover{background:rgba(255,255,255,.95)}
.help .help-item:active{background:rgba(209,209,214,.85)}
.help .help-ico{width:30px;height:30px;border-radius:8px;color:#241A02;
  background:linear-gradient(180deg,#FFCC47,#F0A500);
  box-shadow:inset 0 .5px 0 rgba(255,255,255,.6),0 1px 2px rgba(122,72,0,.2)}
.help .help-note{margin-top:12px;padding:0 4px;text-align:center;
  font-size:11px;letter-spacing:.02em;color:rgba(60,60,67,.5)}

@media(prefers-reduced-motion:reduce){
  .help,.help .help-btn,.help .help-panel,.help .help-panel > *,
  .help .help-label,.help .help-btn .help-ic svg{transition-duration:.15s!important;
    transition-timing-function:ease!important;transition-delay:0s!important}
  .help:not(.show),.help .help-panel,.help .help-panel > *{transform:none;filter:none}
  .help .help-btn:active{transform:none}
}


/* ══ hero controls: bare icons beside a hairline progress ══
   The round glass buttons stacked over the bars are replaced by the
   quieter treatment of a media player: the progress bars, then on the
   same line a left arrow, a right arrow, a hairline divider and pause —
   plain white strokes with no fill or rim, brightening on hover. The
   bars are 2px instead of 4px. Each icon keeps a 34px hit area, so they
   are no harder to press for being drawn smaller. */
.hero-rail .wrap{flex-direction:row;align-items:center;gap:26px}
.hero-rail .hd-bars{order:0;gap:8px}
.hero-pager{order:1;display:inline-flex;align-items:center;gap:6px;margin-left:0}

.hero-rail .hd{height:2px}
.hero-rail .hd.on{width:48px}
.hero-rail .hd::before{inset:-12px -3px}

.hero-btn,.hero-pause{position:relative;display:grid;place-items:center;
  width:34px;height:34px;margin:0;padding:0;border:0;border-radius:8px;
  background:none;box-shadow:none;
  -webkit-backdrop-filter:none;backdrop-filter:none;
  color:rgba(255,255,255,.78);cursor:pointer;
  transition:color .2s ease,transform .2s ease}
.hero-btn:hover,.hero-pause:hover{background:none;box-shadow:none;color:#fff}
.hero-btn:active,.hero-pause:active{transform:scale(.9)}
.hero-btn svg{width:20px;height:20px;fill:none;stroke:currentColor;
  stroke-width:1.7;stroke-linecap:round;stroke-linejoin:round}
.hero-prev:hover svg{transform:translateX(-2px)}
.hero-next:hover svg{transform:translateX(2px)}

/* the hairline between the arrows and pause */
.hero-pause{margin-left:15px}
.hero-pause::before{content:"";position:absolute;left:-9px;top:50%;
  width:1px;height:20px;transform:translateY(-50%);
  background:rgba(255,255,255,.32)}
.hero-pause svg{width:16px;height:16px;fill:none;stroke:currentColor;
  stroke-width:1.9;stroke-linecap:round}
.hero-pause .i-play{fill:currentColor;stroke-width:1.2}


/* white hairlines vanish on the bright sky of the first slide; a faint
   dark halo keeps icons, divider and bars legible on any photograph */
.hero-btn svg,.hero-pause svg{filter:drop-shadow(0 1px 2px rgba(9,15,28,.38))}
.hero-pause::before,.hero-rail .hd{box-shadow:0 1px 3px rgba(9,15,28,.22)}


/* ══ catalogue rows: an iPadOS-style pointer highlight ══
   Each row used to fade its own grey background in and out, so moving
   down the list blinked one box off and the next one on. There is now a
   single highlight per list, the way the pointer behaves on an iPad:
     · it springs from row to row, stretching to the new row's height,
       and fades in only when the pointer first enters the list;
     · it leans a few pixels toward the pointer inside the row, which
       gives the row the slight "lifted" parallax of iPadOS;
     · pressing sinks it to 98.5% and it springs back on release;
     · the separators above and below the highlighted row fade out, as
       they do around a selected cell in iOS;
     · the flag, name and arrow inside the row move on the same spring.
   It follows keyboard focus too. Touch screens and reduced motion get
   the plain per-row background instead. */
/* the rows carried a border-radius with a bottom border, which bent the
   ends of every separator up into faint rounded corners; the rounded
   shape belongs to the highlight, the rows stay square */
.cat-list .crow{border-radius:0}
.cat-list.has-hl{position:relative;isolation:isolate}
.cat-list.has-hl .crow{z-index:1}
.cat-list.has-hl .crow::before{display:none}
.crow-hl{position:absolute;z-index:0;left:calc(-1 * clamp(10px,1.4vw,18px));
  right:calc(-1 * clamp(10px,1.4vw,18px));top:0;height:var(--hl-h,0px);
  border-radius:18px;pointer-events:none;
  background:linear-gradient(180deg,#F7F8FA,#F1F2F5);
  box-shadow:0 0 0 .5px rgba(20,33,61,.06),0 1px 2px rgba(20,33,61,.05),
    0 14px 30px -18px rgba(20,33,61,.30);
  opacity:0;
  transform:translate3d(var(--hl-x,0px),var(--hl-y,0px),0) scale(var(--hl-s,1));
  transition:opacity .22s ease,
    transform .55s cubic-bezier(.3,1.25,.5,1),height .55s cubic-bezier(.3,1.25,.5,1)}
@supports (transition-timing-function:linear(0,1)){
  .crow-hl{transition:opacity .22s ease,transform .55s linear(0, 0.059, 0.194, 0.359, 0.524, 0.672, 0.793, 0.886, 0.952, 0.996, 1.022, 1.035, 1.038, 1.036, 1.031, 1.025, 1.019, 1.013, 1.008, 1.005, 1.002, 1, 0.999, 0.999, 1),height .55s linear(0, 0.059, 0.194, 0.359, 0.524, 0.672, 0.793, 0.886, 0.952, 0.996, 1.022, 1.035, 1.038, 1.036, 1.031, 1.025, 1.019, 1.013, 1.008, 1.005, 1.002, 1, 0.999, 0.999, 1)}
}
.cat-list.hl-on .crow-hl{opacity:1}
.cat-list.hl-snap .crow-hl{transition:opacity .22s ease}
.cat-list.hl-press .crow-hl{--hl-s:.985;background:linear-gradient(180deg,#EEF0F3,#E8EAEE)}

.cat-list.has-hl .crow{transition:border-color .25s ease}
#numbers .cat-list.has-hl .crow.is-hot,
#numbers .cat-list.has-hl .crow.is-above{border-bottom-color:transparent}
/* the list's own top rule is the separator above the first row */
#numbers .cat-list.has-hl.hl-first{border-top-color:transparent}
#numbers .cat-list.has-hl{transition:border-color .25s ease}

.cat-list.has-hl .crow .cflagx,
.cat-list.has-hl .crow .cname,
.cat-list.has-hl .crow .go{transition:transform .5s cubic-bezier(.3,1.25,.5,1),
  opacity .25s ease,color .25s ease}
@supports (transition-timing-function:linear(0,1)){
  .cat-list.has-hl .crow .cflagx,
  .cat-list.has-hl .crow .cname,
  .cat-list.has-hl .crow .go{transition:transform .5s linear(0, 0.059, 0.194, 0.359, 0.524, 0.672, 0.793, 0.886, 0.952, 0.996, 1.022, 1.035, 1.038, 1.036, 1.031, 1.025, 1.019, 1.013, 1.008, 1.005, 1.002, 1, 0.999, 0.999, 1),opacity .25s ease,color .25s ease}
}
.cat-list.has-hl .crow:hover .cname,
.cat-list.has-hl .crow.is-hot .cname{transform:translateX(5px)}
.cat-list.has-hl .crow.is-hot .cflagx{transform:scale(1.08)}
.cat-list.has-hl .crow.is-hot .go{opacity:1;transform:translateX(4px);color:var(--hive)}
.cat-list.has-hl .crow:active .cflagx{transform:scale(1.02)}


/* ══ use cases (#trust): copy, caption type, veil, shadow, spacing ══
   One consolidated set for this block. Every selector here is written to
   match or outrank the rules it replaces further up — the base .ucap
   reveal, the "only the landed card shows its sentence" state, the
   hover-only captions above 901px, the per-width caption sizes, the old
   three-stop veil and the four-layer depth shadow — so nothing earlier
   can reassert itself. The photo pairings, sticky heading, column drift,
   arcs, mobile swipe row and the head-protecting background-position
   are untouched.

   Heading and lead: display face at 700, lead at 400, no shadows. The
   English heading breaks between its two sentences.

   Captions: always visible, never clamped or ellipsised. Title
   18-20px / 600 (700 in Chinese, the weight the face ships), body
   14-15px / 400 at 1.6, 8px between them, 22-24px of room at the sides
   and foot. Narrow cards simply take more lines.

   Veil: the photograph keeps its own light over the top half; the dark
   comes in from 50% of the height and deepens toward the foot, the same
   on all six.

   Shadow: one soft layer. Above 901px its strength still follows --dep,
   so cards fade their shadow in and out with the scroll; with no
   timeline running (mobile, no GSAP) --dep is unset and it sits at full
   strength. No inner rim, no heavier hover shadow. */
#trust .uses-head h2{font-weight:700;text-shadow:none}
/* each sentence is its own line box, balanced on its own: the break
   always falls between the two sentences, and if a sentence has to wrap
   on a narrow screen it splits evenly instead of leaving one word */
#trust .uses-head h2 .uh-line{display:block;text-wrap:balance}
/* on a phone the second sentence ran one word past the column ("connect."
   and 「色。」 alone on a line); a size that follows the viewport keeps
   each sentence on its line down to 360px, and balance splits it evenly
   below that instead of stranding a word */
@media(max-width:900px){
  #trust .uses-head h2{font-size:clamp(23px,6.4vw,30px);letter-spacing:-.03em}
  :is(html[lang^="zh"],html[lang^="ja"]) #trust .uses-head h2{letter-spacing:0}
}
#trust .uses-head p{font-weight:400;text-shadow:none}

#trust .uses-grid .ushot::before{content:"";position:absolute;inset:0;display:block;
  z-index:1;border-radius:inherit;opacity:1;pointer-events:none;
  background:linear-gradient(180deg,
    rgba(11,18,34,0) 50%,
    rgba(11,18,34,.30) 64%,
    rgba(11,18,34,.58) 80%,
    rgba(11,18,34,.78) 100%)}
/* When a narrow card or a longer language takes the caption above the
   halfway line, the caption carries a little shade of its own: it fades
   in over the 40px above the title and holds under the text. On the
   usual two-line caption it sits entirely inside the photo veil, where
   it only adds a touch of depth at the foot. */
#trust .uses-grid .ucap::before{content:"";position:absolute;z-index:-1;
  left:0;right:0;bottom:0;top:-40px;pointer-events:none;border-radius:inherit;
  background:linear-gradient(180deg,rgba(11,18,34,0) 0,rgba(11,18,34,.32) 40px,
    rgba(11,18,34,.36) 100%)}

#trust .uses-grid .ucap,
#trust .uses-grid .use.is-on .ucap,
#trust .uses-grid .use:hover .ucap,
#trust .uses-grid .use:focus-within .ucap{
  position:relative;z-index:2;display:block;width:100%;max-width:none;
  grid-template-rows:none;
  padding:22px clamp(22px,1.7vw,24px) clamp(22px,1.7vw,24px)}
#trust .uses-grid .ucap h3{margin:0;color:#FFFFFF;
  font-size:clamp(18px,1.4vw,20px);font-weight:600;line-height:1.35;
  letter-spacing:-.015em;text-shadow:none}
:is(html[lang^="zh"],html[lang^="ja"]) #trust .uses-grid .ucap h3{font-weight:700;line-height:1.45;letter-spacing:0}
#trust .uses-grid .ucap p,
#trust .uses-grid .use.is-on .ucap p,
#trust .uses-grid .use:hover .ucap p,
#trust .uses-grid .use:focus-within .ucap p{
  margin:0;padding-top:8px;max-width:none;overflow:visible;
  opacity:1;transform:none;text-shadow:none;
  color:rgba(255,255,255,.9);font-size:clamp(14px,1.05vw,15px);
  font-weight:400;line-height:1.6;
  -webkit-line-clamp:unset;display:block}
:is(html[lang^="zh"],html[lang^="ja"]) #trust .uses-grid .ucap p{line-height:1.7}

#trust .uses-grid .use,
#trust .uses-grid .use:hover,
#trust .uses-grid.armed .use:hover,
#trust .uses-grid.armed .use.is-in:hover{
  box-shadow:0 12px 28px -16px rgba(20,33,61,.18)}
@media(min-width:901px){
  #trust .uses-grid .use,
  #trust .uses-grid .use:hover,
  #trust .uses-grid.armed .use:hover,
  #trust .uses-grid.armed .use.is-in:hover{
    box-shadow:0 12px 28px -16px rgba(20,33,61,calc(var(--dep,1) * .18))}

  /* a little less air between the photographs; the stagger stays */
  #trust .uses-col{gap:clamp(28px,3.4vw,58px)}
  #trust .uses-col:last-child{margin-top:clamp(72px,8.5vw,140px)}
}


/* ══ member card: a leaner price block ══
   · the amount is the headline of the card now — display face, large,
     honey — and still goes through the currency picker like every other
     price on the page (it is found and wrapped by the same text scan);
   · one line under it, "One-time membership fee", and nothing else in
     the box: the box is shorter and both lines range left;
   · the number-activation requirement moved into the plan list as a
     detail row (an "i" instead of a tick, so it does not read as a
     perk);
   · the offer box is one sentence with a "View conditions" link, which
     opens the membership terms just below it;
   · the terms — non-refundable fee, and the waiver's limited-time,
     applied-at-checkout conditions — sit in a disclosure above the
     button, with a link out to the full terms page. The waiver line in
     them is gated on data-promo exactly like the offer box. */
.plan-member .plan-price.plan-price-hero{display:flex;flex-direction:column;
  align-items:flex-start;justify-content:flex-start;gap:3px;
  padding:13px 18px 12px;text-align:left}
.plan-member .plan-price-hero .plan-amount{font-family:var(--display);
  font-size:clamp(38px,3.2vw,46px);font-weight:700;line-height:1;
  letter-spacing:-.035em;color:var(--honey);white-space:nowrap;
  font-variant-numeric:tabular-nums}
.plan-member .plan-price-hero .plan-amount-label{font-size:13px;font-weight:500;
  line-height:1.35;color:#9CA2AE;letter-spacing:0}
:is(html[lang^="zh"],html[lang^="ja"]) .plan-member .plan-price-hero .plan-amount-label{font-size:13.5px}

/* the currency script wraps the amount in a span, and the price box's
   generic "span = small grey label" rule was shrinking it back to 13px */
.plan-member .plan-price-hero .plan-amount .money{font:inherit;color:inherit;
  letter-spacing:inherit}
.plan-member .plan-list .plan-li-detail{color:#9CA2AE;font-size:13.5px}
.plan-member .pk.pk-info{background:rgba(255,255,255,.10);color:#CBCED4}

[data-promo~="fee-waiver"] .plan-member .plan-waive{margin-top:22px;max-width:none;width:auto}
.plan-waive-link{display:inline-block;margin-left:4px;font-weight:600;
  color:var(--honey);white-space:nowrap;text-decoration:none}
.plan-waive-link:hover{text-decoration:underline;text-underline-offset:3px}

.plan-terms{margin:14px 0 22px;color:#9CA2AE;font-size:12.5px;line-height:1.7}
.plan-terms summary{display:inline-flex;align-items:center;gap:6px;cursor:pointer;
  list-style:none;font-weight:600;color:#CBCED4}
.plan-terms summary::-webkit-details-marker{display:none}
.plan-terms summary::after{content:"";width:6px;height:6px;margin-left:2px;
  border-right:1.6px solid currentColor;border-bottom:1.6px solid currentColor;
  transform:translateY(-2px) rotate(45deg);transition:transform .25s var(--e)}
.plan-terms[open] summary::after{transform:translateY(1px) rotate(-135deg)}
.plan-terms summary:focus-visible{outline:2px solid var(--honey);outline-offset:3px;border-radius:4px}
.plan-terms-list{margin:8px 0 0;padding:0 0 0 16px}
.plan-terms-list li{margin:2px 0}
.plan-terms-list .plan-waive-term{display:none}
[data-promo~="fee-waiver"] .plan-terms-list .plan-waive-term{display:list-item}
.plan-terms-full{display:inline-block;margin-top:6px;font-weight:600;color:var(--honey)}
:is(html[lang^="zh"],html[lang^="ja"]) .plan-terms{font-size:13px}
/* the old promo box had its own bottom margin to clear the button */
.plan-member .plan-list + .plan-waive{margin-bottom:0}


/* ══ Support button: plain, precise ══
   Back to the original flat pill, finished carefully rather than
   decorated: solid honey, navy text and line icon, one faint shadow.
   Everything the glass version added to the button is switched off
   here — tinted gradient, top highlight (::before), rim, inner shadows,
   background blur, the springy morph and the press squeeze. Scoped to
   #help, so no other button on the page is touched; the panel that
   opens above it is left as it is.
     · 46px tall, 20px either side, 8px between icon and label
     · label 14px / 500, icon 18px, both #14213D
     · hover darkens the fill slightly over 180ms; press scales to .98
     · keyboard focus: a navy ring with a white gap, visible on light
       and dark sections alike
   Open state and small screens keep the original behaviour: the label
   drops out and the pill closes to a 46px circle showing the close icon. */
#help{transition:opacity .45s var(--ease),transform .45s var(--ease)}
#help:not(.show){transform:translateY(14px)}

#help .help-btn{position:relative;display:inline-flex;align-items:center;gap:0;
  height:46px;padding:0 20px;border:0;border-radius:999px;overflow:visible;
  background:#F0A500;background-image:none;color:#14213D;
  font-family:var(--display);font-size:14px;font-weight:500;letter-spacing:0;
  -webkit-backdrop-filter:none;backdrop-filter:none;filter:none;
  box-shadow:0 4px 14px rgba(20,33,61,.10);
  transform:none;cursor:pointer;-webkit-tap-highlight-color:transparent;
  transition:background-color .18s ease,transform .12s ease}
#help .help-btn::before,#help .help-btn::after{content:none;display:none}
#help .help-btn:hover{background:#E39C00;background-image:none;transform:none;filter:none}
#help .help-btn:active{transform:scale(.98);filter:none;
  transition:background-color .18s ease,transform .12s ease}
#help .help-btn:focus{outline:none}
#help .help-btn:focus-visible{outline:2px solid #14213D;outline-offset:2px;
  box-shadow:0 0 0 4px #FFFFFF,0 4px 14px rgba(20,33,61,.10)}

#help .help-ic{display:grid;width:18px;height:18px;flex:none}
#help .help-btn .help-ic svg{grid-area:1/1;display:block;width:18px;height:18px;
  stroke-width:2;transform:none;transition:opacity .22s ease}
#help .help-btn .help-open{opacity:1}
#help .help-btn .help-close{display:block;opacity:0}
#help.open .help-btn .help-open{display:block;opacity:0}
#help.open .help-btn .help-close{opacity:1}

#help .help-label{display:inline-block;max-width:none;margin-left:8px;opacity:1;
  overflow:visible;white-space:nowrap;transition:none}
#help.open .help-label{display:none}
#help.open .help-btn{padding:0 14px}
@media(max-width:560px){
  #help .help-label{display:none}
  #help .help-btn{padding:0 14px}
}
@media(prefers-reduced-motion:reduce){
  #help .help-btn,#help .help-btn:active{transition:none;transform:none}
}


/* ══ hero headline and lead: weight and shadow ══
   The headline was set heavier with a three-layer glow behind it, and the
   lead carried a two-layer one. Headline at 700 and lead at 400 now,
   each with a single tight, faint shadow — enough to hold the white
   edge on the bright sky of the Paris slide, not enough to read as a
   glow. No outline on either. The eyebrow above is untouched. */
.hero .hp h1,.hero .hp h2{font-weight:700;text-shadow:0 1px 3px rgba(9,15,28,.22)}
.hero .hp p{font-weight:400;text-shadow:0 1px 2px rgba(9,15,28,.28);-webkit-text-stroke:0}


/* ══ one Ken Burns for all four backgrounds ══
   Every slide settles with the same slow move: it arrives 8% larger and
   eases down to its resting size over 8 seconds, centred on the window.
   The first two slides do exactly that (1.08 → 1). The server-room and
   Paris slides had been reframed with an extra zoom and an offset, and
   their entry zoom was left at +0.06 on top of that — a smaller relative
   move (5.3% and 4.6%), and because the offset sat inside the scale it
   drifted a few pixels sideways as it went. They now enter at their
   resting scale × 1.08, and the offset is applied outside the scale so
   it stays put while the picture zooms. The resting framing — what is
   on screen once the move ends — is unchanged. */
.bgstage .bgshot.px-room.on{transform:translate(-3.24%,-3.24%) scale(1.08)}
.bgstage .bgshot.px-room{transform:translate(-3.24%,-3.24%) scale(1.1664)}
@media (max-aspect-ratio:1753/1000){
  .bgstage .bgshot.px-room.on{transform:translate(2%,0) scale(1)}
  .bgstage .bgshot.px-room{transform:translate(2%,0) scale(1.08)}
}
.bgstage .bgshot.px-friends.on{transform:translate(-3.75%,-11.25%) scale(1.25)}
.bgstage .bgshot.px-friends{transform:translate(-3.75%,-11.25%) scale(1.35)}


/* ══ member card: one line of fine print ══
   The activation row in the list and the "Membership terms" disclosure
   are folded into a single sentence above the button: joining includes
   activating one number, the fee is non-refundable, and the full
   membership details are one click away on the rewards page (and in
   the account once it is open). "View conditions" in the offer box
   goes to the same page. */
/* .cta p (the plans section's lead style: 16.5px, centred, 44ch) also
   matches this line, so the reset has to outrank it */
.cta .plan-card .plan-fine{margin:14px 0 22px;max-width:none;
  font-size:12.5px;line-height:1.7;color:#9CA2AE;text-align:left}
.plan-fine a{color:var(--honey);font-weight:600;text-decoration:none}
.plan-fine a:hover{text-decoration:underline;text-underline-offset:3px}
:is(html[lang^="zh"],html[lang^="ja"]) .cta .plan-card .plan-fine{font-size:13px;line-height:1.8}


/* ══ member card: the offer becomes the button's title ══
   The separate offer box is gone. While the fee-waiver promotion is on
   (data-promo="fee-waiver" on the section), the button reads as the
   offer — a small navy "Limited time" tag, then "Join with no joining
   fee" — and the fine print just above it states the condition: the
   waiver needs the required steps completed. Take the attribute off
   and the button falls back to plain "Become a member" and the
   condition drops out of the fine print, both together. */
.plan-member .plan-cta .cta-offer{display:none}
[data-promo~="fee-waiver"] .plan-member .plan-cta .cta-offer{display:inline}
[data-promo~="fee-waiver"] .plan-member .plan-cta .cta-plain{display:none}
.plan-member .plan-cta .cta-tag{display:inline-block;margin:-4px 9px -4px 0;padding:4px 9px;
  border-radius:999px;background:#14213D;color:#F0A500;
  font-size:11.5px;font-weight:700;line-height:1;letter-spacing:.03em;vertical-align:1px}
:is(html[lang^="zh"],html[lang^="ja"]) .plan-member .plan-cta .cta-tag{letter-spacing:.08em}
.plan-waive-clause{display:none}
[data-promo~="fee-waiver"] .plan-waive-clause{display:inline}


/* ══ both price blocks share one layout ══
   The free card still had the old block — a small monospaced "$0" on
   the left and its label pushed to the right — beside the member card's
   large amount with the label under it. The free card now uses the
   same block: same padding, same height, amount large and set in the
   display face, one line of label underneath, both ranged left. Only
   the colours differ with the card: navy on the honey-cream box here,
   honey on the translucent box on the navy card. The layout rules are
   written once for both cards. */
.plan-card .plan-price.plan-price-hero{display:flex;flex-direction:column;
  align-items:flex-start;justify-content:flex-start;gap:3px;
  padding:13px 18px 12px;text-align:left}
.plan-card .plan-price-hero .plan-amount{font-family:var(--display);
  font-size:clamp(38px,3.2vw,46px);font-weight:700;line-height:1;
  letter-spacing:-.035em;white-space:nowrap;font-variant-numeric:tabular-nums}
.plan-card .plan-price-hero .plan-amount .money{font:inherit;color:inherit;letter-spacing:inherit}
.plan-card .plan-price-hero .plan-amount-label{font-size:13px;font-weight:500;
  line-height:1.35;letter-spacing:0}
:is(html[lang^="zh"],html[lang^="ja"]) .plan-card .plan-price-hero .plan-amount-label{font-size:13.5px}
.plan-free .plan-price-hero .plan-amount{color:#14213D}
.plan-free .plan-price-hero .plan-amount-label{color:#646C7F}
.plan-member .plan-price-hero .plan-amount{color:var(--honey)}
.plan-member .plan-price-hero .plan-amount-label{color:#9CA2AE}




/* at the narrowest two-column widths the offer can still take two lines;
   both buttons then take the same two-line height so they stay level */
@media(min-width:821px) and (max-width:1000px){
  #plans .plan-cta{display:flex;align-items:center;justify-content:center;
    flex-wrap:wrap;min-height:58px;padding-top:8px;padding-bottom:8px;text-align:center}
}


/* ══ member price: the offer shown on the price itself ══
   While the fee-waiver promotion runs, the amount reads $0 with the
   regular $40 struck through beside it, and the label under it carries
   the condition — limited time, after the starter tasks — so the $0
   is never shown without what it takes to get it. Both amounts go
   through the currency picker. With data-promo removed from the section
   the block falls back to a plain $40 and the plain label. */
.plan-amount-row{display:flex;align-items:baseline;gap:10px;flex-wrap:wrap}
.plan-member .plan-price-hero .plan-was{font-family:var(--display);font-size:18px;
  font-weight:600;line-height:1;color:#8A91A0;text-decoration:line-through;
  text-decoration-thickness:1.5px;text-decoration-color:rgba(203,206,212,.8)}
.plan-member .plan-price-hero .plan-was .money{font:inherit;color:inherit}
.plan-member .amt-promo,.plan-member .amt-promo-note{display:none}
[data-promo~="fee-waiver"] .plan-member .amt-promo{display:inline}
[data-promo~="fee-waiver"] .plan-member .amt-promo-note{display:inline}
[data-promo~="fee-waiver"] .plan-member .amt-regular{display:none}


/* ══ "Limited time" moves from the button to the price ══
   The tag now sits on the price line after the struck regular amount,
   in honey on the navy card, and the button carries only the offer
   sentence. Both plan buttons use the same type size at every width —
   the step-down that shrank the member label between 1000 and 1240px
   is gone; where the sentence needs two lines (821-1000px) both
   buttons already take the same two-line height. */
/* written through .plan-price-hero .plan-amount-row so it outranks
   ".plan-member .plan-price b", which paints every <b> in the box honey */
.plan-member .plan-price-hero .plan-amount-row .price-tag{display:inline-block;align-self:center;margin-left:2px;
  padding:4px 9px;border-radius:999px;background:#F0A500;color:#14213D;
  font-family:var(--display);font-size:11.5px;font-weight:700;line-height:1;
  letter-spacing:.03em;white-space:nowrap}
:is(html[lang^="zh"],html[lang^="ja"]) .plan-member .plan-price-hero .plan-amount-row .price-tag{letter-spacing:.08em}
.plan-member .plan-price-hero .plan-amount-row .price-tag.amt-promo{display:none}
[data-promo~="fee-waiver"] .plan-member .plan-price-hero .plan-amount-row .price-tag.amt-promo{display:inline-block}
#plans .plan-cta{font-size:15px}


/* ══ member card: sold as a one-time, lifetime membership ══
   Membership is paid once and never lapses: after the $40, every number
   is at member price, including a number bought after an earlier one
   has expired. The card leads with that instead of with the fee:
     · under the price, "One-time fee · lifetime membership" (during the
       waiver offer: "Lifetime membership · fee waived after starter
       tasks"), gated on data-promo like the rest of the offer;
     · a "Lifetime" row second in the list, straight after the 25% off,
       spelling out that it covers every later number and a return after
       a gap;
     · the number that has to be opened when joining is described as the
       first number, at member price, in the fine print;
     · outside the offer the button reads "Become a lifetime member". */
.plan-member .lbl-promo{display:none}
[data-promo~="fee-waiver"] .plan-member .lbl-promo{display:inline}
[data-promo~="fee-waiver"] .plan-member .lbl-regular{display:none}
.plan-member .plan-list .plan-li-life b{color:#fff;font-weight:600}


/* ══ free card: support, said with some reassurance ══
   "Telegram support" read as a channel name. The row now says what it
   means for the customer — a dedicated team, reachable whenever there
   is a question — and the channel and hours (the same "24/7, all year
   round" the support panel already states) sit under it in small print. */
.plan-free .plan-list .plan-li-support b{font-weight:600;color:var(--navy)}
.plan-list .plan-li-sub{display:block;margin-top:2px;font-size:12.5px;line-height:1.5;color:#8A91A0}
:is(html[lang^="zh"],html[lang^="ja"]) .plan-list .plan-li-sub{font-size:13px}


/* a Chinese caption made of two clauses breaks between the clauses, not
   inside a word: each clause is kept whole, so 「朋友。」 can no longer be
   left alone on the last line */
#trust .uses-grid .ucap .cl{display:inline-block}


/* how it works: the catalogue reference in step 1 is a real link to the
   number list (it also switches the list to the numbers tab) */
#howto .hw-copy .hw-link{color:inherit;text-decoration:underline;
  text-decoration-color:rgba(100,108,127,.45);text-underline-offset:3px}
#howto .hw-copy .hw-link:hover{color:var(--navy);text-decoration-color:currentColor}


/* ══ catalogue rows: a quiet hover ══
   The floating grey card that sprang from row to row is gone (its script
   is removed, so the .has-hl rules above never apply). Hovering a row
   now draws a short honey rule in the gutter to its left and nudges the
   country name and the arrow a few pixels right; the arrow darkens. No
   fill, no shadow, no spring — 220ms eases, and the same state on
   keyboard focus. The per-row grey box from before is not coming back
   either: the row's ::before is repurposed as the rule. */
#numbers .cat-list .crow::before{content:"";position:absolute;z-index:0;
  left:calc(-1 * clamp(10px,1.2vw,16px));right:auto;top:26%;bottom:26%;
  width:3px;border-radius:3px;background:var(--honey);
  transform:scaleY(0);transform-origin:50% 50%;opacity:1;
  transition:transform .22s ease}
#numbers .cat-list .crow:hover::before,
#numbers .cat-list .crow:focus-visible::before{background:var(--honey);transform:scaleY(1)}
#numbers .cat-list .crow:focus-visible{outline:none}

#numbers .cat-list .crow .cname,
#numbers .cat-list .crow .cflagx,
#numbers .cat-list .crow .go{transition:transform .22s ease,color .22s ease,opacity .22s ease}
#numbers .cat-list .crow:hover .cname,
#numbers .cat-list .crow:focus-visible .cname{transform:translateX(4px);color:var(--navy)}
#numbers .cat-list .crow:hover .go,
#numbers .cat-list .crow:focus-visible .go{opacity:1;transform:translateX(4px);color:var(--navy)}
#numbers .cat-list .crow:hover .cflagx{transform:none}
@media(prefers-reduced-motion:reduce){
  #numbers .cat-list .crow::before,
  #numbers .cat-list .crow .cname,
  #numbers .cat-list .crow .go{transition:none}
}



/* Chinese fine print breaks between its clauses, never inside a word */
.plan-fine .cl{display:inline-block}




/* ══ why Bees Mobile: the four cards rise in one after another ══
   When the row comes into view the cards enter from below in order, left
   to right, 160ms apart: each starts 60px low and transparent and
   settles over 0.9s on a soft ease-out, the way the team cards arrive in
   the reference. On a phone, where the cards stack, each rises as it
   reaches the screen. The hidden state is only set once the script has
   armed the cards, and it is removed entirely once they have arrived, so
   the normal hover lift and shadow keep their own timing afterwards.
   Reduced motion gets a plain fade. */
/* the bento tiles overrode transform to none (nothing lifts on hover),
   which also cancelled the 60px start of this entrance — the tiles were
   fading in on the spot. Written through the grid so it outranks that. */
.wcu-card.wcu-armed,
#whyus .wcu-grid .wcu-card.wcu-armed{opacity:0;transform:translate3d(0,60px,0);transition:none}
.wcu-card.wcu-armed.wcu-in,
#whyus .wcu-grid .wcu-card.wcu-armed.wcu-in{opacity:1;transform:none;
  transition:opacity .7s cubic-bezier(.33,.1,.3,1) var(--wcu-delay,0ms),
             transform .9s cubic-bezier(.25,.8,.3,1) var(--wcu-delay,0ms)}
@media(prefers-reduced-motion:reduce){
  .wcu-card.wcu-armed,
  #whyus .wcu-grid .wcu-card.wcu-armed{transform:none}
  .wcu-card.wcu-armed.wcu-in,
  #whyus .wcu-grid .wcu-card.wcu-armed.wcu-in{transition:opacity .3s ease var(--wcu-delay,0ms)}
}


/* ══ how it works: the white panel rises with the scroll ══
   The one-shot entrance was easy to miss: it fired as the panel's top
   edge crossed the bottom of the window, so most of the movement
   happened below the fold, and on a reload mid-page it was skipped
   altogether. The rise now follows the scroll instead. While the
   panel's top travels from the bottom of the window to 35% of the way
   down it, the panel comes up 180px, fades in over the first part of
   that and grows from 96% to full size, eased in and out so the
   movement happens where it can be seen. Scroll back and it sinks again, so
   it is seen every time the section is reached, from any starting
   point. --rise (0 → 1) is written by the script; wide layouts only,
   and nothing moves with reduced motion. */
@media(min-width:901px){
  #howto .hw-body{
    opacity:var(--rise-o,1);
    transform:translate3d(0,var(--rise-y,0px),0) scale(var(--rise-s,1));
    transform-origin:50% 0;will-change:transform,opacity}
}
@media(min-width:901px) and (prefers-reduced-motion:reduce){
  #howto .hw-body{opacity:1;transform:none;will-change:auto}
}


/* ══ one type scale for the section headings and leads ══
   The section titles had drifted to four different sizes (the use-case
   heading 37px, "How it works" 40px in English, the rest 44px), three
   line heights, and leads between 15 and 16.5px. On wide layouts they
   now share one set:
     · heading 40px at 1440 (clamp 30-40px), weight 700; line height 1.3
       in Chinese, 1.15 in Latin scripts;
     · lead 16px, weight 400; line height 1.85 in Chinese, 1.7 otherwise.
   40 rather than 44 so the use-case heading, which lives in the narrow
   centre column, fits the same size as everything else without breaking
   mid-phrase. Selectors carry html[lang] so they outrank the per-language
   size rules scattered above. The closing "promise" line is a display
   statement and keeps its own size; phones keep their own scale. */
@media(min-width:901px){
  html[lang] #trust .uses-head h2,
  html[lang] #howto .hw-head h2,
  html[lang] #numbers .cat-copy h2,
  html[lang] #whyus .wcu-head h2,
  html[lang] #plans.cta > .wrap > h2,
  html[lang] #faq .faq-title{
    font-size:clamp(30px,2.8vw,40px);font-weight:700;
    line-height:1.15;letter-spacing:-.03em}
  :is(html[lang^="zh"],html[lang^="ja"]) #trust .uses-head h2,
  :is(html[lang^="zh"],html[lang^="ja"]) #howto .hw-head h2,
  :is(html[lang^="zh"],html[lang^="ja"]) #numbers .cat-copy h2,
  :is(html[lang^="zh"],html[lang^="ja"]) #whyus .wcu-head h2,
  :is(html[lang^="zh"],html[lang^="ja"]) #plans.cta > .wrap > h2,
  :is(html[lang^="zh"],html[lang^="ja"]) #faq .faq-title{line-height:1.3;letter-spacing:0}

  html[lang] #trust .uses-head p,
  html[lang] #howto .hw-head p,
  html[lang] #numbers .cat-copy > p,
  html[lang] #whyus .wcu-head p,
  html[lang] #plans.cta > .wrap > p{
    font-size:16px;font-weight:400;line-height:1.7}
  :is(html[lang^="zh"],html[lang^="ja"]) #trust .uses-head p,
  :is(html[lang^="zh"],html[lang^="ja"]) #howto .hw-head p,
  :is(html[lang^="zh"],html[lang^="ja"]) #numbers .cat-copy > p,
  :is(html[lang^="zh"],html[lang^="ja"]) #whyus .wcu-head p,
  :is(html[lang^="zh"],html[lang^="ja"]) #plans.cta > .wrap > p{line-height:1.85}

  /* the use-case centre column gains a little width so the heading at
     the shared size keeps each sentence on one line; the photo columns
     give up about 4% each */
  #trust .uses-body{grid-template-columns:minmax(0,1fr) minmax(0,1.45fr) minmax(0,1fr)}
}


/* ══ Japanese, Thai, Vietnamese and Indonesian ══
   Japanese shares the Chinese typographic rules (every html[lang^="zh"]
   rule in this sheet now also matches ja), but it gets a Japanese font
   stack first — through the Chinese stack its kanji would be drawn in
   Traditional Chinese glyph shapes. Thai gets a Thai-capable stack (Inter
   has no Thai) and taller lines: its vowels and tone marks sit above and
   below the letters and clip at the tight line heights the Latin headings
   use; letter-spaced capitals are meaningless in Thai, so the tracking on
   labels is taken off. Vietnamese stacks diacritics on capitals, which
   collide at the hero's 1.0 line height, so its headings open up a
   little. Indonesian needs nothing beyond the Latin defaults. */
html[lang^="ja"]{
  --display:'Inter','Hiragino Sans','Hiragino Kaku Gothic ProN','Noto Sans JP','Yu Gothic','Meiryo',system-ui,sans-serif;
  --sans:'Inter','Hiragino Sans','Hiragino Kaku Gothic ProN','Noto Sans JP','Yu Gothic','Meiryo',system-ui,-apple-system,sans-serif;
  --mono:'IBM Plex Mono','Noto Sans JP','Hiragino Sans',ui-monospace,monospace}
html[lang^="th"]{
  --display:'Inter','Noto Sans Thai','Leelawadee UI','Thonburi','Sukhumvit Set',system-ui,sans-serif;
  --sans:'Inter','Noto Sans Thai','Leelawadee UI','Thonburi','Sukhumvit Set',system-ui,-apple-system,sans-serif;
  --mono:'IBM Plex Mono','Noto Sans Thai','Leelawadee UI',ui-monospace,monospace}
html[lang^="th"] body{font-family:var(--display)}
html[lang^="th"] :is(h1,h2,h3,h4){line-height:1.45!important;letter-spacing:0!important}
html[lang^="th"] :is(p,li,.hw-copy,.ucap p,.plan-fine){line-height:1.85}
html[lang^="th"] :is(.badge,.eyebrow,.hp .tag,.faq-group,.ticks li){letter-spacing:.02em!important}
html[lang^="vi"] :is(h1,h2){line-height:1.22!important}
html[lang^="vi"] h3{line-height:1.35}


/* headline wrapping in the longer-worded languages: balanced lines, so a
   Vietnamese or Indonesian hero title never ends on one short word */
html:is([lang^="vi"],[lang^="id"],[lang^="th"]) .hero .hp :is(h1,h2){text-wrap:balance}


/* ══ how it works: notes and numerals were too faint ══
   The grey note under each step was #A8AEBB — 2.2:1 on white, below the
   4.5:1 body text needs to be read comfortably — and the step numerals
   were #E9ECF1 at 1.2:1, close to invisible. The notes move to #6B7385
   (4.8:1): still a clear step below the navy lines above them, but
   readable. The numerals stay decorative, a quiet grey rather than a
   near-white, #C3CAD6. */
#howto .hw-copy span{color:#6B7385}
@media(min-width:901px){
  #howto .hw-num{color:#C3CAD6}
}


/* ══ nav: six links, fitted to the space ══
   "Use cases" and "How it works" join the bar ahead of the catalogue.
   The links sit centred between the logo and the language/currency/log-in
   group, and how much room that leaves depends on the window and on the
   language (Vietnamese and Filipino labels run half as long again as
   Chinese). The script at the foot of the page measures it: if the links
   would touch either side the bar first tightens — smaller gap, 13.5px
   labels — and if that is still not enough, the two new links step out
   (the sections are still one scroll away). If four still collide, the
   links hide as they do below 1081px. Re-measured on resize,
   language change and once the fonts have loaded. */
.nav.nav-tight .nav-links{gap:18px}
.nav.nav-tighter .nav-links a[data-nav-optional]{display:none}
/* last resort, where even four do not fit (long labels on a narrow
   desktop window): the bar behaves as it already does below 1081px */
.nav.nav-none .nav-links{display:none}


/* ══ why Bees Mobile: a bento layout ══
   Four identical navy tiles in a row read as a template. The same four
   points are now laid out by weight, the way a product page would:
     · the carrier line — the claim everything else rests on — is the
       large navy tile on the left, with its heading at display size and
       a field of faint honey rings spreading from the corner behind it,
       the signal the icon is broadcasting;
     · "simple to start and manage" is a wide white tile beside it;
     · pricing is a white tile, support a warm honey-cream one, sharing
       the row beneath.
   Everything ranges left, icons sit in soft squircles, text sits at the
   foot of each tile so the tops line up and the air collects above the
   words. White tiles carry a hairline and one long, light shadow; on
   hover only the edge warms — nothing lifts, since none of these are
   links. The icon loops, the staggered entrance and the copy are
   unchanged. Two columns on tablets (the large tile across the top), one
   on phones. */
#whyus .wcu-grid{max-width:1240px;gap:18px;
  grid-template-columns:repeat(14,minmax(0,1fr));grid-auto-rows:auto}
#whyus .wcu-grid .wcu-card{position:relative;overflow:hidden;isolation:isolate;
  display:flex;flex-direction:column;align-items:flex-start;text-align:left;
  min-height:0;padding:30px 30px 28px;border-radius:24px;
  transform:none;transition:box-shadow .3s var(--e)}
#whyus .wcu-grid .wcu-card:hover{transform:none}
#whyus .wcu-grid .wcu-card .wcu-ico{margin:0 0 28px;width:48px;height:48px;border-radius:14px}
#whyus .wcu-grid .wcu-card .wcu-ico svg{width:24px;height:24px}
#whyus .wcu-grid .wcu-card h3{margin-top:auto;font-size:20px;font-weight:650;
  line-height:1.35;letter-spacing:-.02em}
#whyus .wcu-grid .wcu-card p{margin-top:10px;font-size:15px;line-height:1.7;max-width:46ch}

/* 1 · the carrier line: large navy tile */
#whyus .wcu-grid .wcu-card:nth-child(1){grid-column:1 / span 6;grid-row:1 / span 2;
  min-height:440px;padding:38px 38px 36px;color:#fff;
  background:var(--hive);background-image:var(--grad-navy-card);
  box-shadow:0 24px 48px -30px rgba(11,18,34,.55)}
#whyus .wcu-grid .wcu-card:nth-child(1)::after{content:"";position:absolute;z-index:-1;
  right:-160px;top:-160px;width:560px;height:560px;pointer-events:none;
  background:repeating-radial-gradient(circle at 50% 50%,
    rgba(240,165,0,.16) 0 1px,rgba(240,165,0,0) 1.5px 34px);
  -webkit-mask-image:radial-gradient(circle at 50% 50%,#000 0,rgba(0,0,0,.55) 38%,transparent 70%);
          mask-image:radial-gradient(circle at 50% 50%,#000 0,rgba(0,0,0,.55) 38%,transparent 70%)}
#whyus .wcu-grid .wcu-card:nth-child(1) .wcu-ico{width:56px;height:56px;border-radius:16px;
  background:rgba(255,255,255,.08);box-shadow:inset 0 0 0 1px rgba(255,255,255,.10);color:var(--honey)}
#whyus .wcu-grid .wcu-card:nth-child(1) .wcu-ico svg{width:28px;height:28px}
#whyus .wcu-grid .wcu-card:nth-child(1) h3{font-size:clamp(26px,2.3vw,32px);font-weight:700;
  line-height:1.2;letter-spacing:-.025em;color:#fff}
#whyus .wcu-grid .wcu-card:nth-child(1) p{font-size:16px;color:rgba(255,255,255,.72);max-width:34ch}

/* 2 · 3 · white tiles */
#whyus .wcu-grid .wcu-card:nth-child(2){grid-column:7 / span 8;grid-row:1}
#whyus .wcu-grid .wcu-card:nth-child(2) p{max-width:62ch}
#whyus .wcu-grid .wcu-card:nth-child(3){grid-column:7 / span 4;grid-row:2}
#whyus .wcu-grid .wcu-card:nth-child(4){grid-column:11 / span 4;grid-row:2}
#whyus .wcu-grid .wcu-card:nth-child(2),
#whyus .wcu-grid .wcu-card:nth-child(3){color:var(--navy);
  background:#FFFFFF;background-image:none;
  box-shadow:0 0 0 1px rgba(20,33,61,.07),0 20px 40px -30px rgba(20,33,61,.28)}
#whyus .wcu-grid .wcu-card:nth-child(2) h3,
#whyus .wcu-grid .wcu-card:nth-child(3) h3{color:var(--navy)}
#whyus .wcu-grid .wcu-card:nth-child(2) p,
#whyus .wcu-grid .wcu-card:nth-child(3) p{color:#646C7F}
#whyus .wcu-grid .wcu-card:nth-child(2) .wcu-ico,
#whyus .wcu-grid .wcu-card:nth-child(3) .wcu-ico{background:#FFF4D9;color:#B97C00;box-shadow:none}

/* 4 · support: warm honey-cream tile */
#whyus .wcu-grid .wcu-card:nth-child(4){color:var(--navy);
  background:#FFF3D6;background-image:linear-gradient(160deg,#FFF8E8 0%,#FFEBC4 100%);
  box-shadow:0 0 0 1px rgba(240,165,0,.22),0 20px 40px -30px rgba(122,72,0,.30)}
#whyus .wcu-grid .wcu-card:nth-child(4) h3{color:var(--navy)}
#whyus .wcu-grid .wcu-card:nth-child(4) p{color:#5B6275}
#whyus .wcu-grid .wcu-card:nth-child(4) .wcu-ico{background:#FFFFFF;color:#B97C00;
  box-shadow:0 1px 2px rgba(122,72,0,.10)}
#whyus .wcu-grid .wcu-card:nth-child(4) a{color:var(--navy);font-weight:600;
  text-decoration:underline;text-decoration-color:rgba(240,165,0,.8);
  text-decoration-thickness:2px;text-underline-offset:3px}

/* hover: the edge warms, nothing moves */
@media(hover:hover){
  #whyus .wcu-grid .wcu-card:nth-child(1):hover{
    box-shadow:inset 0 0 0 1px rgba(240,165,0,.30),0 24px 48px -30px rgba(11,18,34,.55)}
  #whyus .wcu-grid .wcu-card:nth-child(2):hover,
  #whyus .wcu-grid .wcu-card:nth-child(3):hover{
    box-shadow:0 0 0 1px rgba(240,165,0,.40),0 20px 40px -30px rgba(20,33,61,.28)}
  #whyus .wcu-grid .wcu-card:nth-child(4):hover{
    box-shadow:0 0 0 1px rgba(240,165,0,.55),0 20px 40px -30px rgba(122,72,0,.30)}
  #whyus .wcu-grid .wcu-card:hover .wcu-ico{transform:none}
}

/* Chinese and Japanese: a touch more leading, no negative tracking */
:is(html[lang^="zh"],html[lang^="ja"]) #whyus .wcu-grid .wcu-card h3{letter-spacing:0;line-height:1.4}
:is(html[lang^="zh"],html[lang^="ja"]) #whyus .wcu-grid .wcu-card p{line-height:1.85}

@media(max-width:1000px){
  #whyus .wcu-grid{grid-template-columns:repeat(2,minmax(0,1fr))}
  #whyus .wcu-grid .wcu-card:nth-child(1){grid-column:1 / -1;grid-row:auto;min-height:320px}
  #whyus .wcu-grid .wcu-card:nth-child(2){grid-column:1 / -1;grid-row:auto}
  #whyus .wcu-grid .wcu-card:nth-child(3){grid-column:1;grid-row:auto}
  #whyus .wcu-grid .wcu-card:nth-child(4){grid-column:2;grid-row:auto}
}
@media(max-width:560px){
  #whyus .wcu-grid{grid-template-columns:minmax(0,1fr);gap:12px}
  #whyus .wcu-grid .wcu-card:nth-child(n){grid-column:1;padding:26px 22px 24px}
  #whyus .wcu-grid .wcu-card:nth-child(1){min-height:300px;padding:30px 24px 28px}
  #whyus .wcu-grid .wcu-card .wcu-ico{margin-bottom:22px}
}


/* the carrier-line icon, redrawn finer: on a 32-unit grid with a 1.5
   stroke, a solid centre, two true circular arcs a side, and a tapered
   mast with a brace in place of the single stick. Shown a little larger
   in its tile so the detail reads. */
#whyus .wcu-grid .wcu-card:nth-child(1) .ico-signal svg{width:32px;height:32px}


/* ══ nav links: centred in the free space, with room between them ══
   The links were pinned to the centre of the page, so the space they
   could use was set by whichever side was wider — the language, currency
   and log-in group on the right — and the bar tightened early, down to
   14px between labels. They now sit in the flow, centred between the
   logo and that group, which gives them all of the space actually free.
   The normal gap is 20-28px; if it must tighten it only goes to 18px and
   the labels keep their size, and past that the two optional links step
   out rather than squeezing the rest. */
@media(min-width:1081px){
  .nav-links{position:static;left:auto;transform:none;margin-inline:auto;gap:var(--sp2);flex-shrink:0}
}


/* use-case lead: it was capped at 352px, which pushed the last word of
   the Chinese line (「門號。」) onto a second line on its own. It now takes
   the width of the centre column; the Chinese version, when it does have
   to wrap on a narrow screen, breaks at the comma. */
/* written with html[lang] to outrank the 22em / 24em caps set per language above */
html[lang] #trust .uses-head p{max-width:none;text-wrap:wrap}
#trust .uses-head p .cl{display:inline-block}


/* catalogue lead: in Chinese each clause stays whole, so the lines break
   at punctuation instead of splitting 「12 個月」 or 「語音」 */
#numbers .cat-copy > p .cl{display:inline-block}


/* ══ how it works: the new clip is square ══
   The 24-second "how to start" film is framed 1:1 around the phone, with
   its interface text in the middle. The frame used to be 6:5, and on
   wide screens it stretched to fill the column (about 1.6:1), which would
   crop the phone's header and its confirm button. The frame is now
   square at every width so the whole shot shows; on desktop the left
   column grows by a few dozen pixels to make room. Encoded for the page
   at 1080×1080 H.264 without the audio track (the clip plays muted), about
   2.4 MB, with a still of its first frame as the poster. */
.hw-video{--vr:1/1;aspect-ratio:1/1}
@media(min-width:901px){
  #howto .hw-visual{flex:0 0 auto}
  #howto .hw-video{aspect-ratio:1/1;height:auto;min-height:0}
}


/* "coming soon", said quietly: a step down in size and weight so the
   promise does not compete with what the line actually delivers today */
/* only the parenthetical is quieter: "and calls" belongs to the sentence
   and stays at the sentence's own size and weight */
.soon{font-size:.82em;font-weight:500;opacity:.72;white-space:nowrap}


/* ══ catalogue: countries that are not open yet ══
   Rows for numbers we do not have stock for are listed at the same size
   as the live ones, so the reader can see the price and plan, but they
   are plainly not buyable: the row is a div rather than a link, its
   contents sit at 55% opacity, the badge is grey instead of green, and
   nothing lights up on hover. */
#numbers .cat-list .crow-out{cursor:default}
#numbers .cat-list .crow-out .ccode,
#numbers .cat-list .crow-out .cflagx,
#numbers .cat-list .crow-out .cmain,
#numbers .cat-list .crow-out .cmoney{opacity:.55}
#numbers .cat-list .crow-out .go{opacity:.2}
#numbers .cat-list .crow-out:hover .cname{transform:none;color:inherit}
#numbers .cat-list .crow-out:hover .go{transform:none;color:inherit;opacity:.2}
#numbers .cat-list .crow-out::before{display:none}
.cstock.cstock-out{background:#EFF0F2;color:#6B7385}
.cstock.cstock-out::before{background:#AEB4C0}


/* ══ mobile menu ══
   Below 1081px the six links dropped out of the bar and there was no
   other way to reach a section. The bar now carries a burger next to
   "Log in / Sign up", and it opens a full-screen white sheet: the mark
   and a "Menu ✕" pill across the top, the single log-in button under
   it, then the links at reading size between two hairlines, with the
   language and currency pills at the foot.

   The links are clones of the ones in the bar, rebuilt whenever the
   language changes; the two pills are the real controls, moved into the
   sheet and moved back when the window grows, so their dropdowns and
   scripts keep working untouched. */
.burger{display:none;place-items:center;width:44px;height:44px;margin-left:4px;
  padding:0;border:0;border-radius:var(--r-md);background:none;color:#fff;cursor:pointer;
  -webkit-tap-highlight-color:transparent}
.nav.stuck .burger{color:var(--navy)}
.burger-box{display:block;position:relative;width:24px;height:16px}
.burger-box i{position:absolute;left:0;width:100%;height:2px;border-radius:2px;
  background:currentColor;transition:transform .3s var(--ease),opacity .2s ease}
.burger-box i:nth-child(1){top:0}
.burger-box i:nth-child(2){top:7px}
.burger-box i:nth-child(3){top:14px}
.burger:focus-visible{outline:2px solid var(--honey);outline-offset:2px}

.mnav{position:fixed;inset:0;z-index:95}
.mnav[hidden]{display:none}
.mnav-sheet{position:absolute;inset:0;display:flex;flex-direction:column;
  padding:14px 22px calc(24px + env(safe-area-inset-bottom,0px));
  overflow-y:auto;background:#fff;color:var(--navy);
  opacity:0;transform:translateY(-8px);
  transition:opacity .25s var(--ease),transform .32s var(--ease)}
.mnav.open .mnav-sheet{opacity:1;transform:none}

.mnav-top{display:flex;align-items:center;justify-content:space-between;
  min-height:48px;margin-bottom:26px}
.mnav-brand img{height:21px;width:auto}
.mnav-x{display:inline-flex;align-items:center;gap:10px;
  padding:10px 16px;border:0;border-radius:var(--r-pill);
  background:var(--sunk);color:var(--navy);cursor:pointer;
  font-family:var(--display);font-size:15px;font-weight:600}
.mnav-x svg{width:18px;height:18px}
.mnav-x:focus-visible{outline:2px solid var(--honey);outline-offset:2px}

/* the foot: the two pills reduced to their icons on the left, the single
   log-in button beside them on the right */
.mnav-foot{display:flex;align-items:center;gap:12px;margin-top:auto;padding-top:22px}
/* the button takes what is left of the row and may shrink: a long label
   (Vietnamese, Filipino) would otherwise push it past the right edge */
/* the button takes what is left of the row: on a narrow phone with a long
   label (Vietnamese, Filipino) the type steps down rather than the words
   being cut off */
.mnav-cta{flex:1 1 auto;min-width:0;text-align:center;padding:15px 12px;
  font-size:clamp(13.5px,3.8vw,16px);white-space:nowrap}

.mnav-links{display:flex;flex-direction:column;gap:2px;
  margin:26px 0;padding:22px 0;
  border-top:1px solid #ECEDEF;border-bottom:1px solid #ECEDEF}
.mnav-links a{padding:14px 2px;font-family:var(--display);font-size:21px;
  font-weight:600;letter-spacing:-.02em;color:var(--navy)}
:is(html[lang^="zh"],html[lang^="ja"]) .mnav-links a{letter-spacing:0}
.mnav-links a:active{color:var(--honey-lo)}

/* the pills sit at the foot; their menus open upward from there so a
   long list is not pushed off the bottom of the screen */
.mnav-controls{display:flex;gap:8px;flex:none}
/* anchored to the controls row rather than to its own pill, so a wide
   menu cannot run off the right edge of a phone */
.mnav-foot{position:relative}
.mnav-controls .lang{position:static}
.mnav-controls .lang-menu{top:auto;bottom:calc(100% + 10px);left:0;right:0;
  min-width:0;max-height:min(52vh,320px);transform-origin:0 100%}
@media(prefers-reduced-motion:reduce){.mnav-sheet{transition:none}}
@media(max-width:1080px){
  .burger{display:grid}
  body.mnav-open{overflow:hidden}
}
}


/* the two pills are the real controls, borrowed from the bar, so inside
   the white sheet they need the light treatment the bar gives them when
   it is scrolled, and their dropdowns open downward in normal flow */
.mnav-controls .langbox{gap:8px;margin:0}
/* icon-only: a globe for language, the currency's own symbol for money */
.mnav-controls .lang-btn{width:48px;height:48px;padding:0;gap:0;
  justify-content:center;border-radius:var(--r-md);
  background:var(--sunk);color:var(--body);
  box-shadow:inset 0 0 0 1px rgba(20,33,61,.10);
  backdrop-filter:none;-webkit-backdrop-filter:none;font-size:16px}
.mnav-controls .lang-btn .globe{width:22px;height:22px}
.mnav-controls .lang-btn .caret{display:none}
.mnav-controls #langCur,.mnav-controls .lang-tag,.mnav-controls #curNow{display:none}
.mnav-controls .cur-sym{font-family:var(--display);font-size:18px;font-weight:600;
  opacity:1;max-width:44px;overflow:hidden;text-overflow:clip;white-space:nowrap}
/* a three-character symbol (NT$, RM) needs a wider key than a bare $ */
.mnav-controls .cur .lang-btn{width:auto;min-width:48px;padding:0 12px}
.mnav-controls .lang-menu{right:auto;left:0;min-width:100%;
  background:#FFFFFF;border-color:#CBCED4;
  box-shadow:0 18px 44px rgba(20,33,61,.18),0 2px 6px rgba(20,33,61,.08);
  max-height:min(44vh,260px)}
.mnav-controls .lang-menu button{color:var(--body)}
.mnav-controls .lang-menu button[aria-selected="true"]{background:var(--sunk)}
.mnav-controls .cur-menu-note{color:var(--dim)}


/* in the sheet there is room for the full language name, and the currency
   pill — hidden in the bar on a phone — comes back */
.mnav-controls .cur{display:block}


/* ══ hero photographs on a phone ══
   The layer was hidden below 901px, leaving a navy block behind the
   slideshow. It is back, framed for a tall screen (the subject sits in
   the upper half of each shot, so the crop is taken from the top) and
   under a scrim weighted for a single column: dark at the top where the
   copy is, opening up over the lower half so the photograph still
   reads, and dark again at the foot where the carrier band sits. */
@media(max-width:900px){
  .hero .bgstage{display:block}
  .hero .hero-scrim{display:block;
    background:
      linear-gradient(180deg,rgba(9,15,28,.92) 0%,rgba(9,15,28,.82) 30%,
                      rgba(9,15,28,.52) 56%,rgba(9,15,28,.28) 76%,
                      rgba(9,15,28,.72) 100%)}
  /* each shot framed on its subject for a tall crop */
  .hero .bgstage .px{background-position:50% 26%}
  .hero .bgstage .px-home{background-position:52% 62%}
  .hero .bgstage .px-room{background-position:58% 40%}
  .hero .bgstage .px-friends{background-position:50% 76%}
  .hero .bgstage .bgshot,
  .hero .bgstage .bgshot.on,
  .hero .bgstage .bgshot.px-room,
  .hero .bgstage .bgshot.px-room.on,
  .hero .bgstage .bgshot.px-friends,
  .hero .bgstage .bgshot.px-friends.on{transform:scale(1.06)}
  .hero .bgstage .bgshot.on,
  .hero .bgstage .bgshot.px-room.on,
  .hero .bgstage .bgshot.px-friends.on{transform:scale(1)}
}


/* the dropdowns scroll on their own on touch too: momentum inside the
   list, and no rubber-banding of the page when it reaches either end */
.lang-menu{-webkit-overflow-scrolling:touch;overscroll-behavior:contain;
  touch-action:pan-y}


/* ══ language and currency as a full page on a phone ══
   Both were dropdowns hanging off a 48px key at the foot of the menu:
   a small scrolling box, hard to aim at and hard to scan. On a phone
   they now open as their own page — a title that names the current
   choice, a search field, and the options as full-width rows.

   The rows are not a second implementation: each one is wired to the
   button it was cloned from, so choosing here runs exactly the code the
   dropdown ran, including the language swap and the price repaint. */
.picker{position:fixed;inset:0;z-index:120}
.picker[hidden]{display:none}
.picker-sheet{position:absolute;inset:0;display:flex;flex-direction:column;
  background:var(--raise);color:var(--navy);
  opacity:0;transform:translateY(10px);
  transition:opacity .22s var(--ease),transform .3s var(--ease)}
.picker.open .picker-sheet{opacity:1;transform:none}

.picker-top{display:flex;align-items:center;justify-content:space-between;gap:12px;
  padding:16px 20px 14px;background:var(--sunk)}
.picker-title{font-family:var(--display);font-size:20px;font-weight:700;
  letter-spacing:-.02em;line-height:1.3}
:is(html[lang^="zh"],html[lang^="ja"]) .picker-title{letter-spacing:0}
.picker-x{display:grid;place-items:center;width:44px;height:44px;flex:none;
  border:0;border-radius:var(--r-pill);background:#fff;color:var(--navy);cursor:pointer;
  box-shadow:0 1px 2px rgba(20,33,61,.10)}
.picker-x svg{width:20px;height:20px}

.picker-search{display:flex;align-items:center;gap:10px;margin:16px 20px 6px;
  padding:12px 16px;border-radius:var(--r-pill);background:#fff;
  box-shadow:inset 0 0 0 1px rgba(20,33,61,.14)}
.picker-search svg{width:20px;height:20px;flex:none;color:var(--dim)}
.picker-search input{flex:1;min-width:0;border:0;outline:none;background:none;
  font-family:var(--sans);font-size:16px;color:var(--navy)}
.picker-search input::-webkit-search-cancel-button{-webkit-appearance:none}

.picker-note{margin:6px 20px 0;font-size:12px;line-height:1.6;color:var(--dim)}
.picker-note:empty{display:none}
.picker-list{flex:1;overflow-y:auto;overscroll-behavior:contain;
  -webkit-overflow-scrolling:touch;padding:14px 20px calc(24px + env(safe-area-inset-bottom,0px))}
.picker-row{display:flex;align-items:center;justify-content:space-between;gap:12px;
  width:100%;margin-bottom:10px;padding:16px 18px;border:0;
  border-radius:var(--r-md);background:#fff;color:var(--navy);cursor:pointer;
  font-family:var(--display);font-size:16px;font-weight:600;text-align:left;
  box-shadow:0 1px 2px rgba(20,33,61,.06)}
.picker-row[aria-selected="true"]{box-shadow:inset 0 0 0 2px var(--honey)}
/* the tick is an svg, and the dark menu's own .lang-tick rules were
   painting it as a filled pill; this one keeps its own stroke look */
.picker-row .pick-tick{width:20px;height:20px;flex:none;color:var(--honey-lo);opacity:0}
.picker-row[aria-selected="true"] .pick-tick{opacity:1}
.picker-row:active{background:var(--sunk)}
.picker-empty{margin:10px 20px;font-size:14px;color:var(--dim)}
@media(prefers-reduced-motion:reduce){.picker-sheet{transition:none}}
@media(min-width:1081px){.picker{display:none}}


/* ══ phone hero: full-bleed bar, actions at the foot, bars centred ══
   1 · the nav capsule becomes a plain bar across the top, with the mark
       at the left margin and log-in + menu at the right;
   2 · the copy holds the top of the panel and the two buttons sit at the
       bottom of it, just above the progress bars, rather than floating
       in the middle with empty space beneath;
   3 · the arrows and pause step out — on a phone the slides are swiped
       — leaving the four bars centred on their own. */
@media(max-width:900px){
  /* 1 */
  .nav{padding:0}
  .cap,.nav.stuck .cap{width:100%;border-radius:0;padding:10px 18px;
    border-left:0;border-right:0}
  .cap .brand{margin-right:auto}

  /* 2 */
  .hero .hp.on{display:flex;flex-direction:column;min-height:52vh}
  .hero .hp .hero-cta{margin-top:auto;padding-top:28px}

  /* 3 */
  .hero-rail{margin:22px 0 30px}
  .hero-rail .wrap{justify-content:center}
  .hero-pager,.hero-pause{display:none}
  .hd-bars{gap:10px}
}

/* ══ fix: the use-case heading rode above the white section ══
   The heading is held in the middle of the screen with top:50vh plus
   translateY(-50%). The transform moves it up by half its own height
   everywhere, including before it sticks — so while #trust was still
   rising over the hero, the badge and the top of the heading sat about
   80px above the section's edge, on top of the hero photograph and
   across the curved seam.

   A top margin of that same half-height puts the resting position back
   inside the section. Once stuck nothing changes: sticky measures the
   border box, so it still settles at 50vh and the transform still
   centres it. The half-height is measured by the script at the foot of
   the page (it changes with the language); 185px is the English value. */
@media(min-width:901px){
  #trust .uses-head{margin-top:var(--uh-half,185px)}
}

/* ══════════════════════════════════════════════════════════════════
   MOBILE PASS
   Everything below was added on top of the original stylesheet. With
   three exceptions it is scoped to max-width:900px; the exceptions,
   all asked for at both widths, are:

     · the catalogue rows — country code and term line removed, stock
       pill removed, sold-out rows no longer dimmed, price spacing
     · .hero .b-line — frosted glass and the label's shadow
     · .ph — clause boxes: inline on desktop, inline-block on a phone

   These blocks override each other by position, not by specificity,
   so read them in order. Declarations that were already superseded
   have been deleted, so everything still written here is a value that
   actually applies somewhere.

   Sequence: hero (layout, art, type) · use-case row · steps row ·
   catalogue · why-us · plans · FAQ · footer · nav · shared type scale
   · clause breaking.
   ══════════════════════════════════════════════════════════════════ */

/* ══════════════════════════════════════════════════════════
   HOW IT WORKS on a phone: heading on one line, steps centred
   ──────────────────────────────────────────────────────────
   1. The CJK heading is thirteen glyphs wide and --fs6 bottoms
      out at 28px, so 13 × 28px = 364px against ~335px of
      content width on a 375px screen: it broke after the sixth
      character and left the second line short. The size is now
      tied to the viewport instead of a fixed floor, and the
      line is told not to break at all — at 375px it sets at
      ~24.7px, which fits with room to spare, and it keeps
      shrinking on anything narrower.
   2. The three step cards are full-bleed blocks with a short
      number, a short title and two lines of copy; flush left
      they read as a ragged column. Centred, each card is a
      self-contained item.
   ══════════════════════════════════════════════════════════ */
@media(max-width:900px){
  :is(html[lang^="zh"],html[lang^="ja"]) #howto .hw-head h2{
    white-space:nowrap;max-width:100%;
    line-height:1.35;letter-spacing:-.005em}

  #howto .hw-step{text-align:center}
  #howto .hw-top{align-items:center;justify-content:center;
    text-align:center}
  #howto .hw-num,
  #howto .hw-label{width:100%;text-align:center}
  #howto .hw-copy,
  #howto .hw-copy b{text-align:center}
  #howto .hw-star{left:50%;right:auto;transform:translateX(-50%)}
}

/* the scroll hint under the use-case heading is back — desktop only.
   On a phone the reader is already flicking and the section head is
   short enough that the cue only added height, so it stays hidden
   below 901px. The fade-out on scroll is handled by the script that
   was left in place when the markup went. */
@media(max-width:900px){#trust .uses-scroll{display:none}}

/* ══ phone: no text-shadow anywhere in the hero ══
   The hero type carries a wide navy shadow (18px blur under the
   headings, 14px under the lead) so white can hold up over the
   photograph. On a phone the copy sits over the dark end of the
   scrim rather than the lit part of the picture, where that blur
   stops reading as depth and starts reading as a second, softer
   copy of the same words behind them. It comes off below 901px;
   desktop keeps it. */
@media(max-width:900px){
  .hero h1,.hero h2,
  .hero .hp h1,.hero .hp h2,.hero .hp p,
  .hero .pill,.hero .hpk,
  .hero .it,.hero .tick,
  .hero-cta .btn,
  .nav:not(.stuck) .brand{text-shadow:none}
}

/* ══ phone: the hero photograph is no longer sat on ══
   .hero-scrim was carrying a five-stop navy ramp on mobile —
   92% opaque at the top of the frame, opening to 28% over the
   lower third, then back to 72% at the foot for the carrier
   band. That is what reads as a dark panel behind the copy and
   a second one across the bottom: not a shadow on the type,
   a wash over the picture. The layer stays in the markup (the
   slideshow script and the desktop rules both reference it) and
   simply carries no paint below 901px. */
@media(max-width:900px){
  .hero .hero-scrim{background:none}
}

/* ══ the phone menu sheet: close is the ✕ alone, CTA label centred ══
   Both live only inside .mnav, which is the mobile sheet — nothing
   here can reach the desktop bar.

   1. The word beside the ✕ said "Menu" while the menu was already
      open, so it named the thing rather than the action. The ✕ on
      its own is unambiguous; the button keeps its aria-label
      ("關閉選單"), which is what a screen reader reads, so nothing
      is lost for anyone not looking at it.
   2. .mnav-cta was given text-align:center, but .btn makes it an
      inline-flex box and text-align has no say over flex items —
      the label sat against the left padding with the whole flex:1
      of slack opening on its right. justify-content is the property
      that actually centres it. */
.mnav-x-word{display:none}
.mnav-x{gap:0;padding:10px 14px}
.mnav-cta{justify-content:center}

/* ══ phone hero, second pass: centred copy, one row of buttons ══
   The carousel, the rail and the full-bleed photograph were all
   already here — what the layout was still doing was the desktop's
   left-hand column: everything ragged-left against the edge, and
   the two calls to action stacked as two full-width bars.

   Centred, the panel reads as one object on the picture instead of
   a column pinned to its left side. .pill and .hpk carry
   align-self:flex-start from the base rule, which a text-align on
   the parent cannot undo — they are flex items, so they need the
   axis property.

   The buttons go side by side and share the row: flex:1 1 0 with
   min-width:0 so the pair always fits, whatever the language does
   to the labels. Padding comes down to 14px because at 26px two
   Chinese labels plus an arrow will not sit in 350px of column.

   The panel is also taller — 52vh left the photograph ending
   mid-screen with the carrier band pulled up under it. It now runs
   to about a screenful, so the band sits on the fold. */
@media(max-width:900px){

  .hero .hp.on{min-height:calc(100svh - 184px)}

  .hero .hp .hero-cta{flex-wrap:nowrap;
    align-items:stretch;gap:10px;width:100%}
  .hero .hp .hero-cta .btn{flex:1 1 0;width:auto;max-width:none;
    min-width:0}
  :is(html[lang^="zh"],html[lang^="ja"]) .hero .hp .hero-cta .btn{padding:0 12px}
  /* the arrow is the first thing worth losing when the row is tight */
  @media(max-width:380px){
    .hero .hp .hero-cta .btn svg{display:none}
  }
}

/* ══ phone: portrait art for slides 1 and 3 ══
   The desktop shots are landscape crops; on a 19.5:9 screen
   background-size:cover keeps their height and throws away most of
   the width, which is why the subject kept drifting out of frame.
   These two are cut at 1200 x 2600 for the phone and only load
   below 901px — the desktop rules above still point at the original
   landscape files, untouched.

   background-position goes back to 50% 50%: the earlier 50% 26% and
   58% 40% were nudges to rescue a landscape crop, and they fight a
   picture that is already composed for this frame. The scale/translate
   transforms on .px-room are neutralised for the same reason. */
@media(max-width:900px){
  .hero .bgstage .px-hero{background-image:url(/home/home-b5ef30169d61.webp)}
  .hero .bgstage .px-room{background-image:url(/home/home-f9784a27a0b4.webp)}
  .hero .bgstage .px-hero,
  .hero .bgstage .px-room{background-position:50% 50%}
  .hero .bgstage .bgshot.px-hero,
  .hero .bgstage .bgshot.px-room{transform:scale(1.06)}
  .hero .bgstage .bgshot.px-hero.on,
  .hero .bgstage .bgshot.px-room.on{transform:scale(1)}
}

/* ══ phone: portrait art for slides 2 and 4 ══
   Same treatment as slides 1 and 3 — 1200 x 2600 crops that only
   load below 901px, with the landscape-rescue nudges undone.
   px-friends had the heaviest of them (translate(-3.75%,-11.25%)
   with a 1.35 scale, to drag faces up out of a wide frame); the new
   crop already has the group where it should be, so it drops to the
   plain 1.06 → 1 carousel scale like the rest. */
@media(max-width:900px){
  .hero .bgstage .px-home{background-image:url(/home/home-031c0fcef8a8.webp)}
  .hero .bgstage .px-friends{background-image:url(/home/home-1313949a7f54.webp)}
  .hero .bgstage .px-home,
  .hero .bgstage .px-friends{background-position:50% 50%}
  .hero .bgstage .bgshot.px-home,
  .hero .bgstage .bgshot.px-friends{transform:scale(1.06)}
  .hero .bgstage .bgshot.px-home.on,
  .hero .bgstage .bgshot.px-friends.on{transform:scale(1)}
}



/* ══ and a shadow under that button's label ══
   The frost settles the background but it does not darken it — over
   the lime trousers on slide 1 the白 label and the pale fabric land
   at close to the same value and the text goes soft. A short, tight
   shadow (1px down, 3px blur) reads as contrast rather than as a
   drop shadow; the second, wider stop at 20% just lifts it off the
   brighter frames.

   Written as .hero .hero-cta .b-line so it outranks the phone rule
   further up that sets text-shadow:none across .hero-cta .btn —
   that one is still right for the honey button, which has its own
   solid fill and needs no help.

   The arrow is a stroked SVG, so text-shadow does not touch it; it
   takes the matching drop-shadow filter instead. */
.hero .hero-cta .b-line{
  text-shadow:0 1px 3px rgba(9,15,28,.55),
              0 2px 10px rgba(9,15,28,.2)}
.hero .hero-cta .b-line svg{
  filter:drop-shadow(0 1px 2px rgba(9,15,28,.5))}

/* ══ phone: the use-case card was wider than the box holding it ══
   The scroller sits inside .wrap, which pays --sp3 (32px on a phone)
   down each side, and #trust .uses-grid adds another 20px of its own
   padding-inline. So the strip the cards actually live in is
   100vw − 104px — about 286px on a 390px screen — while the card was
   asking for 82vw, around 320px. A flex item does not shrink below
   its basis here, so the card ran past the scroller's right edge and
   overflow-x clipped the last ~35px of it. The blank band to its
   right is .wrap's padding, which is why it looked like the card had
   been trimmed and nothing put in the space.

   Two things had to change together. The scroller goes full-bleed —
   negative margins cancel .wrap's padding so the row owns the whole
   width — and the card is sized from the viewport instead of a bare
   vw fraction: 100vw − 68px leaves 20px of gutter on the left, the
   14px gap, and about 34px of the next card showing. That peek is
   the only thing telling a reader there are five more cards, and it
   is what was being clipped away. */
@media(max-width:900px){
  #trust .uses-grid{
    margin-inline:calc(var(--sp3) * -1);
    width:auto;max-width:none;
    padding-inline:20px;scroll-padding-inline:20px}
  #trust .uses-grid .use{flex:0 0 calc(100vw - 68px)}
}

/* ══ phone: the dome on top of the use-case block comes back ══
   .sec-arc was switched off below 901px outright. The element and the
   script that drives --arc were both left in place, so this only has
   to undo the display:none — written against #trust so it outranks
   the bare .sec-arc rule in the earlier query.

   Two numbers change for a narrow screen. The width goes from 124% to
   160%: the shape is an ellipse, and on a 390px window 124% leaves
   only ~12% of it hanging past each edge, so the curve is already
   falling steeply where it meets the sides and reads as a bump rather
   than a dome. Pushing the ellipse wider brings the flatter middle of
   the curve across the visible width. The height drops to about 44px,
   because the desktop clamp bottoms out at 64px — the same drop that
   looks slight across a laptop is a sixth of the width here. */
@media(max-width:900px){
  #trust .sec-arc{display:block;
    width:160%;height:clamp(34px,11vw,48px)}
}

/* ══ desktop: the use-case badge is optically centred, not box-centred ══
   .badge is an inline-flex carrying a 6px dot and an 8px gap ahead of
   its text. Centring the box therefore centres dot-plus-text, which
   leaves the words themselves sitting 7px right of the centre line the
   headline below is set to. Reading down the column, the eye lines up
   the two pieces of text, not the two boxes, so the badge looks pushed
   right even though it is exactly centred.

   The shift is a transform rather than a margin so it stays out of
   layout: the badge is still centred as far as the box model is
   concerned, and nothing below it moves. -7px is half the dot and its
   gap, which is the amount that puts the text on the centre line. */
@media(min-width:901px){
  #trust .uses-head .badge{transform:translateX(-7px)}
}

/* ══ phone hero, third pass: nothing wider than the screen ══
   English and Japanese were running off the right edge — eyebrow,
   headline, lead and the second button all cut at the same line.
   One cause, in two parts.

   .hero-text is a grid and .hp is a grid item, and a grid item's
   min-width resolves to auto — it will not shrink below the widest
   unbreakable thing inside it. The previous pass had given the two
   buttons white-space:nowrap, so "Choose a second number" set the
   floor for the whole track. The panel grew past 100vw, and because
   everything in it is centred, the copy was then centred inside a box
   wider than the window: pushed right, clipped on the right. Chinese
   escaped it only because its labels are six characters long.

   So: min-width:0 down the chain to let the track shrink, and the
   buttons wrap their labels instead of forcing width. Two short CJK
   words stay on one line; the English pair takes two lines each and
   the row still fits.

   The headline comes down from clamp(33px,8.6vw,42px) to
   clamp(25px,7.2vw,33px). At the old size twelve Chinese characters
   measured about 400px against 350px of usable width, which is why
   the line the copy was written to break at broke again by itself and
   the block grew a third line down over the subject's face. At 7.2vw
   it lands near 326px on a 390px screen and the written break holds.
   Latin and Thai get the same reduction, which is what stops the lead
   paragraph reaching down into the photograph. */
@media(max-width:900px){
  .hero .hero-text,
  .hero .hp{min-width:0;max-width:100%}
  .hero .hp > *{min-width:0;max-width:100%}
  .hero .hp h1,.hero .hp h2,.hero .hp p{overflow-wrap:break-word}

  /* eyebrow: it is an inline-flex, so it needs the wrap and the
     centring on the box, not just on the text */
  .hero .hp .pill,.hero .hp .hpk{
    max-width:100%;white-space:normal;text-align:center;
    justify-content:center;flex-wrap:wrap;
    font-size:11px;letter-spacing:.1em;line-height:1.5}

  .hero .hp p{font-size:15.5px;line-height:1.7;max-width:none}
  :is(html[lang^="zh"],html[lang^="ja"]) .hero .hp p{
    font-size:15px;line-height:1.85}

  /* labels wrap rather than set the panel's width */
  .hero .hp .hero-cta .btn{
    white-space:normal;text-align:center;line-height:1.25;
    font-size:14.5px;padding:10px 12px;min-height:48px;
    overflow-wrap:break-word}
  :is(html[lang^="zh"],html[lang^="ja"]) .hero .hp .hero-cta .btn{
    font-size:15px;letter-spacing:.02em}
}

/* ══ the frost stops blinking between slides ══
   This is not a timing bug, it is how backdrop-filter is specified.
   An element samples "the backdrop" — everything painted behind it —
   but only up to the nearest ancestor that has been isolated into its
   own group. An ancestor with opacity below 1 is exactly that: the
   panel gets rendered separately and then composited, so while .hp is
   mid-fade the button's backdrop is the empty panel, not the
   photograph. The blur has nothing to sample and switches off; the
   moment opacity lands back on 1 the group dissolves and the blur
   returns. Hence gone, then back, on every turn of the carousel.

   The panel has to fade — that is the cross-fade — so the blur cannot
   be kept alive through it. What can be fixed is how much the loss
   shows. A 14% white fill over a bright photograph is nearly nothing
   without the blur behind it, so the button appeared to vanish. A
   navy tint at 30% is a surface in its own right: blurred it reads as
   smoked glass, unblurred it reads as a tinted pill, and the swap
   between the two passes unnoticed.

   The hover transition also drops backdrop-filter. Animating a blur
   radius re-rasterises the sampled region every frame, and on the
   frames where the value has changed but the layer has not been
   redrawn it flicks — a second, smaller version of the same fault. */
.hero .b-line{
  background:rgba(16,26,47,.30);
  border-color:rgba(255,255,255,.38);
  -webkit-backdrop-filter:blur(14px) saturate(1.2);
  backdrop-filter:blur(14px) saturate(1.2);
  transition:transform .3s var(--e),background .3s,color .3s,
             border-color .3s}

.hero .b-line:hover{
  background:rgba(16,26,47,.42);
  border-color:var(--honey);color:var(--honey);
  -webkit-backdrop-filter:blur(14px) saturate(1.2);
  backdrop-filter:blur(14px) saturate(1.2)}

@supports not (backdrop-filter:blur(1px)){
  .hero .b-line{background:rgba(16,26,47,.44)}
  .hero .b-line:hover{background:rgba(16,26,47,.56)}
}

/* ══ the two price lines were sitting on each other ══
   .cmoney stacks the list price over the member price with gap:2px.
   Two pixels is fine between two lines of the same size, but the top
   line is --fs4 mono at 600 weight and the one under it is 12px — the
   big line's descenders and the small line's caps end up closer than
   the space inside either line. The pair reads as one smudged block
   rather than as a price and its footnote.

   gap goes to 7px, and .clist gets an explicit line-height:1.15 so
   the number's own leading is not left to the font's default, which
   on the mono face is loose enough to eat part of the new gap.

   The unit also gets a little room: "/ mo" was 4px off the number,
   which at this size reads as part of it. 7px separates them without
   looking detached. Both are unscoped — desktop and phone together,
   as asked. */
.cmoney{gap:7px}
.clist{line-height:1.15}
.clist i{margin-left:7px}

/* ══ phone: the buttons hold still while the copy turns over ══
   The fade was being applied to .hp itself, so everything inside it
   went at once — eyebrow, headline, lead and the two buttons, which
   are identical on three of the four slides and so were fading out
   and back in to arrive at the same thing.

   The animation moves down one level: .hp stays at opacity 1 for
   good, and its children fade instead, with .hero-cta excluded from
   that. Each panel still carries its own buttons; the inactive ones
   are simply visibility:hidden with no transition, so the swap is a
   single frame. The second button does change text on slide 4, where
   it points at the eSIM plans rather than the how-to — that change
   now happens on its own rather than riding a half-second fade.

   Two things have to move for the buttons to land in the same place
   every time. The column layout and the min-height were set on .hp.on
   only, which left the inactive panels shorter — and since the CTA is
   pushed down with margin-top:auto, its position depended on which
   panel it belonged to. Both now apply to every .hp.

   This also ends the frosted-glass blink for free: the button is no
   longer inside anything whose opacity drops below 1, so its backdrop
   is never isolated and the blur never switches off. That is why the
   white frost can come back here — desktop panels still cross-fade,
   so they keep the navy tint that survives the isolation. */
@media(max-width:900px){
  .hero .hp{
    display:flex;flex-direction:column;
    min-height:calc(100svh - 184px);
    opacity:1;visibility:visible;transform:none;
    transition:none;pointer-events:none}
  .hero .hp.on{pointer-events:auto}

  .hero .hp > :not(.hero-cta){
    opacity:0;transform:translateY(14px);visibility:hidden;
    transition:opacity .5s var(--e),transform .5s var(--e),
               visibility 0s .5s}
  .hero .hp.on > :not(.hero-cta){
    opacity:1;transform:none;visibility:visible;
    transition:opacity .5s var(--e),transform .5s var(--e),
               visibility 0s}

  .hero .hp > .hero-cta{
    opacity:1;transform:none;transition:none;visibility:hidden}
  .hero .hp.on > .hero-cta{visibility:visible}

  /* the original frost, now that nothing isolates its backdrop */
  .hero .b-line{
    background:rgba(255,255,255,.14);
    border-color:rgba(255,255,255,.34)}
  .hero .b-line:hover{background:rgba(255,255,255,.2)}
  @supports not (backdrop-filter:blur(1px)){
    .hero .b-line{background:rgba(16,26,47,.44)}
  }
}

/* ══ phone: the four why-us cards are one set again ══
   On a wide screen the first card is a feature tile — it spans six
   columns and two rows, so it is given its own scale: 440px of
   min-height, 38px of padding, a 56px icon, a 26-to-32px heading and
   16px body against the other three at 48px / 20px / 15px. That is
   the right call in a mosaic where it is visibly the largest shape.

   Stacked in a single column, the mosaic is gone but the exceptions
   stayed, so the first card read as a different component: larger
   type, a wider frame, and — because its min-height survived while
   h3 keeps margin-top:auto — a 300px box with the heading pushed to
   the bottom and a field of empty navy above it.

   Below 901px every one of those exceptions is dropped back to the
   standard card. The min-height goes entirely rather than being
   matched to the others: in a single column the card should be as
   tall as its own text. The tile keeps its navy fill and its radar
   rings, which are what mark it as the first card — size is not
   needed to say so as well. */
@media(max-width:900px){
  #whyus .wcu-grid .wcu-card:nth-child(n){padding:26px 22px 24px}
  #whyus .wcu-grid .wcu-card:nth-child(1){min-height:0}

  #whyus .wcu-grid .wcu-card:nth-child(1) .wcu-ico{
    width:48px;height:48px;border-radius:14px}
  #whyus .wcu-grid .wcu-card:nth-child(1) .wcu-ico svg,
  #whyus .wcu-grid .wcu-card:nth-child(1) .ico-signal svg{
    width:24px;height:24px}

  #whyus .wcu-grid .wcu-card:nth-child(1) h3{font-weight:650}
  #whyus .wcu-grid .wcu-card:nth-child(1) p{
    font-size:15px;line-height:1.7;max-width:46ch}
  :is(html[lang^="zh"],html[lang^="ja"])
    #whyus .wcu-grid .wcu-card:nth-child(1) h3{
      letter-spacing:0;line-height:1.4}
  :is(html[lang^="zh"],html[lang^="ja"])
    #whyus .wcu-grid .wcu-card:nth-child(1) p{line-height:1.85}
}

/* ══ phone: the three steps swipe sideways ══
   Stacked, the sequence cost about three screens of scrolling to say
   three short things, and the reader met each step with no sense of
   how many were left. As a row they are one gesture and the peek of
   the next card carries the count.

   The same three details as the use-case row:

   1. .hw-grid is a grid item inside .hw-body, so min-width:0 — without
      it the track cannot shrink below the widest card and the row
      pushes the section sideways.
   2. The scroller goes full-bleed with a -20px margin against
      .hw-body's own 20px padding, then pays that 20px back as its own
      padding-inline. Otherwise the card is measured against the padded
      box and its right edge is clipped where the peek should be.
   3. Cards are sized calc(100vw - 68px) — 20px gutter, 14px gap, and
      roughly 34px of the next step showing.

   align-items:stretch (the flex default, restated because the column
   layout above is explicit about it) gives all three cards the height
   of the tallest, so the row does not step up and down as it scrolls.

   The entrance animation needs nothing: it is triggered off #howto and
   staggers all three at once, rather than waiting for each card to
   reach the viewport, so cards parked off to the right still arrive. */
@media(max-width:900px){
  #howto .hw-grid{
    min-width:0;
    flex-direction:row;flex-wrap:nowrap;align-items:stretch;
    margin-inline:-20px;padding-inline:20px;
    gap:14px;
    overflow-x:auto;overscroll-behavior-x:contain;
    scroll-snap-type:x mandatory;scroll-padding-inline:20px;
    -webkit-overflow-scrolling:touch;
    scrollbar-width:none}
  #howto .hw-grid::-webkit-scrollbar{display:none}

  #howto .hw-step{
    flex:0 0 calc(100vw - 68px);
    scroll-snap-align:start;
    display:flex;flex-direction:column}
  #howto .hw-copy{margin-bottom:auto}
}

/* ══ phone: the number rows go back to one line ══
   The row was breaking into three stacked bands — flag and country,
   then the price left-aligned underneath, then the availability pill
   under that. Reading down a list of twenty countries, the price of
   each one sat directly above the name of the next, so the column of
   figures never lined up with the column of names.

   Three columns instead, the way the row is built on a desktop: flag,
   country, price. The price keeps align-items:flex-end so both of its
   lines are flush right and the figures stack into a real column down
   the list. It spans both rows and centres itself against them.

   The availability pill moves under the flag rather than under the
   price. It is wider than the flag, so it is what sizes the first
   column — which is why the country name starts a little further in
   than the flag alone would put it. That is the trade for keeping the
   pill out of the middle column, where it would push the country name
   onto a second line on every row that has one.

   Scoped away from .crow.dst: the eSIM destination rows have no price
   or stock and are better off in their existing two columns. */
@media(max-width:900px){
  .crow:not(.dst){
    grid-template-columns:auto minmax(0,1fr) auto;
    column-gap:14px;align-items:center}
  .crow:not(.dst) .cflagx{grid-column:1;grid-row:1;justify-self:center}
  .crow:not(.dst) .cmain{grid-column:2;grid-row:1;min-width:0}
  .crow:not(.dst) .cmoney{
    grid-column:3;
    align-self:center;align-items:flex-end;text-align:right}
  .crow:not(.dst) .cstock{
    grid-column:1;grid-row:2;justify-self:center}
}

/* ══ desktop: the country code and the term line come out ══
   Both were repeating something the row already said. "US" sits next
   to the flag and the word 美國; the term line reads "3 / 6 / 12" on
   every row without exception, so it carries no information that
   distinguishes one country from another — it belongs in the section
   note, not twenty times down the list.

   The grid template has to be restated. .crow is six auto-placed
   columns — code, flag, name, price, stock, arrow — and the only
   flexible one is the third. A display:none item takes no cell, so
   with the code gone the name slides into column 2, which is auto:
   the name would size to its content and the row would no longer fill
   its width. Five columns with the 1fr moved to the second puts the
   flex back where the country name is.

   The phone is untouched — it already hides the code below 820px, and
   the term line is the one short piece of copy there that says the
   plan has a length to choose. */
@media(min-width:901px){
  .crow:not(.dst) .ccode,
  .crow:not(.dst) .cterm{display:none}
}

/* ══ phone: the term line goes too ══
   Kept on the phone last time on the grounds that it was the only
   place saying the plan has a length to choose. It is not worth what
   it costs here: .cmain becomes two lines, which makes the middle
   column taller than the flag column, so the availability pill and
   the two price lines stop lining up with anything. With the country
   name alone, row 1 is flag / name / list price and row 2 is pill /
   — / member price, which is the shape the row was drawn as.

   Now that .cterm is hidden at every width, .cmain holds a single
   child and its flex column and 3px gap do nothing. Left in place
   rather than unpicked: it is what the desktop rules above expect to
   find, and an empty flex container costs nothing. */
@media(max-width:900px){
  .crow:not(.dst) .cterm{display:none}
}

/* ══ the availability pill comes out, both widths ══
   Two follow-on edits, because removing a grid item is never just the
   one line.

   Desktop: the template was five columns — flag, name, price, stock,
   arrow — after the country code went. A display:none item takes no
   cell, so it drops to four. The 1fr stays on the name.

   Phone: the row is placed by hand, and .cmoney was spanning rows 1
   and 2 so it could centre itself against the name above the pill.
   With the pill gone row 2 has nothing in it, but the span still
   declares it, which would leave an empty band under every row. The
   price goes back to row 1 and row-gap to 0.

   Worth flagging: "暫無庫存" was the only thing on the row that said a
   country cannot currently be bought. What is left is .crow-out,
   which dims the whole row to 55% — a reader who does not know the
   convention may just read those rows as lower contrast. If you want
   the state back in words later, the row's aria-label or a line in
   .cnote would carry it without putting a pill on all twenty. */
.cstock{display:none}

@media(min-width:901px){
  .crow:not(.dst){
    grid-template-columns:auto minmax(0,1fr) auto auto}
}
@media(max-width:900px){
  .crow:not(.dst){row-gap:0}
  .crow:not(.dst) .cmoney{grid-row:1}
}

/* ══ sold-out rows stop being faded ══
   .crow-out dropped its flag, name and price to 55% and its arrow to
   20%. With the availability pill gone that fade was the last visual
   difference between a country you can buy and one you cannot, and on
   its own it did not read as a state — four pale rows at the foot of
   the list look like the list trailing off, or like a render that has
   not finished.

   Everything returns to full strength, and the arrow to the .45 that
   a normal row carries, so all twenty rows are one list.

   cursor:default stays and the hover lift stays suppressed — the row
   still does not lead anywhere, and a pointer that changes on some
   rows and not others is a quieter, more honest signal than a fade.
   The state is now invisible to a reader who never hovers, so if it
   matters commercially it needs saying in words somewhere. */
#numbers .cat-list .crow-out .ccode,
#numbers .cat-list .crow-out .cflagx,
#numbers .cat-list .crow-out .cmain,
#numbers .cat-list .crow-out .cmoney{opacity:1}
#numbers .cat-list .crow-out .go,
#numbers .cat-list .crow-out:hover .go{opacity:.45}

/* ══ the two country lists are set at one size ══
   The flags were never the problem: both lists use .cflagx at 24px,
   measured identical in both screenshots. What differed was the name
   beside them — .crow.dst overrode .cname down to --fs4, roughly 18px
   against the number list's --fs5 at about 26px. A 24px disc beside
   18px type reads as a large flag; the same disc beside 26px type
   reads as a small one, which is the inconsistency.

   The override is dropped so both lists take --fs5, at every width.
   It was phone-only for a while, which left the desktop eSIM list
   still at --fs4 — the same mismatch, just one breakpoint up.

   The "several data and duration options" line comes out with it. It
   is identical on every row, so twelve destinations printed it twelve
   times and it distinguished none of them; without it the country
   name is the only thing in the cell and the two lists read as one
   component. The phone already hid it — this is the desktop half. */
.crow.dst .cname{font-size:var(--fs5)}
.crow.dst .cterm{display:none}

/* ══ phone: the eSIM rows lose two lines and gain an arrow ══
   Each row was three stacked lines — country, "several data and
   duration options", "see plans" — and the second and third say the
   same thing on every row, so a list of twelve destinations repeated
   them twelve times. The country name is the only part that varies.

   The arrow replaces the "see plans" line. It was already in the
   markup and already styled at .45 opacity; it was only being hidden
   by the blanket .crow .go rule for small screens. Shown for .dst
   rows only — the number rows above have no arrow on a phone and the
   pattern there is different.

   The template gains a third auto column for it, and the row goes to
   one line with align-items:center. The rows also get shorter, which
   is what makes a twelve-country list scannable on a phone. */
@media(max-width:900px){
  .crow.dst{
    grid-template-columns:auto minmax(0,1fr) auto;
    row-gap:0;align-items:center}
  .crow.dst .go{display:none}

  /* "See plans" moves out of its own line and into the third column,
     which is where the arrow sat a moment ago. justify-self:end keeps
     the whole column flush right down the list; opacity goes to 1
     because the .65 it carries is a resting state for a label that
     brightens on hover, and there is no hover on a phone. */
  .crow.dst .cgo{
    display:block;grid-column:3;grid-row:1;
    justify-self:end;align-self:center;opacity:1}
}

/* ══ phone: the dome is drawn, not animated ══
   --arc is written by the scroll handler and only reaches its peak
   while #trust's top edge is in the bottom fifth of the window,
   flattening again as the seam rises. On a desktop that is a slow,
   readable move. On a phone the same scroll distance passes in a
   flick, so the curve is at or near zero whenever anyone actually
   looks at the seam — which is why it read as missing.

   The fade exists because on a desktop #trust is pulled up a whole
   viewport (margin-top:-100svh) to cover the hero, so an arc at full
   height on first load would stand over the carrier band. Below 901px
   that margin is 0 — the section simply follows the hero — so there
   is nothing for the dome to intrude on and no reason to animate it.

   !important is needed and is doing real work: the handler writes
   --arc as an inline style on the element every frame, and an inline
   declaration outranks any normal author rule. This is the one way to
   pin the value without unpicking the script, which desktop still
   needs. */
@media(max-width:900px){
  #trust .sec-arc{--arc:1 !important}
}

/* ══ phone: the two plans become one switch ══
   Stacked, the free card and the membership card are a long scroll
   apart, so the reader never sees them together — which is the one
   thing a two-plan block exists to let them do. A segmented control
   puts the choice at the top and swaps the card underneath, so both
   are always one tap from each other.

   Desktop is untouched: there the cards sit side by side and a switch
   would hide half of a comparison that already works.

   The tab labels are the card headings, copied with their full set of
   data-* translations. The language script re-collects [data-zh] on
   every switch rather than caching a list at load, so markup added
   here is picked up without any wiring.

   Only the panels are toggled with display:none. The section heading
   and lead above still describe both plans, which is what keeps the
   hidden one from being a surprise. */
.plan-switch{display:none}

@media(max-width:900px){
  .plan-switch{
    display:grid;grid-template-columns:1fr 1fr;gap:4px;
    width:min(100%,340px);margin:26px auto 20px;padding:4px;
    border-radius:var(--r-pill);
    background:rgba(255,255,255,.07);
    box-shadow:inset 0 0 0 1px rgba(255,255,255,.13)}

  .plan-tab{
    appearance:none;-webkit-appearance:none;border:0;cursor:pointer;border-radius:var(--r-pill);
    background:none;color:rgba(255,255,255,.62);
    font-family:var(--display);font-weight:600;letter-spacing:.01em;
    transition:background .25s var(--e),color .25s var(--e)}
  .plan-tab[aria-selected="true"]{
    background:var(--honey);color:var(--hive)}
  .plan-tab:focus-visible{
    outline:2px solid var(--honey);outline-offset:3px}

  .plans[data-plan="free"] .plan-member,
  .plans[data-plan="member"] .plan-free{display:none}
}

/* ══ phone: the why-us cards arrive from alternating sides ══
   Stacked in one column they were all rising 60px from below, so four
   identical moves in a row read as one long shrug. Coming in from the
   left, then the right, then the left again gives each card its own
   arrival and makes the column feel like a sequence.

   The offset rides in --wcu-x so the single transform can carry both
   axes: the sideways travel and a shortened 18px lift. Splitting them
   across two declarations would mean the second overwrote the first.
   The lift is cut from 60px because the two together would otherwise
   describe a long diagonal; the horizontal is now doing the work.

   64px is well past the edge on a phone, but body carries
   overflow-x:clip, so nothing can be scrolled sideways to find them.

   The reduced-motion case is restated here. The block that flattens
   this animation sits earlier in the stylesheet, and these rules are
   more specific than the ones it was written against — without this it
   would be overruled and a reader who asked for stillness would get
   cards flying in from the sides. */
@media(max-width:900px){
  #whyus .wcu-grid .wcu-card.wcu-armed{
    transform:translate3d(var(--wcu-x,0px),18px,0)}
  #whyus .wcu-grid .wcu-card:nth-child(odd){--wcu-x:-64px}
  #whyus .wcu-grid .wcu-card:nth-child(even){--wcu-x:64px}
  #whyus .wcu-grid .wcu-card.wcu-armed.wcu-in{transform:none}
}
@media(max-width:900px) and (prefers-reduced-motion:reduce){
  #whyus .wcu-grid .wcu-card.wcu-armed{transform:none}
}

/* ══ the membership tab follows the fee-waiver promotion ══
   Same switch the card itself runs on: the label is two spans, and
   [data-promo~="fee-waiver"] on the section decides which one shows.
   Delete the attribute when the offer ends and the tab reverts to
   "Membership" along with everything else — the offer is never left
   described as permanent, which is what the note above the section
   asks for.

   Each span carries its own data-* set rather than the button
   carrying one. The language script rewrites innerHTML on every node
   it translates, so a data-zh on the button would replace both spans
   with a plain string and the promo switch would be gone after the
   first language change.

   nowrap also has to go. "Free membership (limited)" and its
   equivalents do not fit half of a 340px control on one line; the tab
   takes two lines and the control's two halves stay equal because the
   grid gives them 1fr each regardless. */
.plan-tab .tab-promo{display:none}
[data-promo~="fee-waiver"] .plan-tab .tab-promo{display:inline}
[data-promo~="fee-waiver"] .plan-tab .tab-regular{display:none}

@media(max-width:900px){
  .plan-tab{white-space:normal;line-height:1.3;
    padding:9px 8px;min-height:46px;
    display:flex;align-items:center;justify-content:center}
}

/* ══ phone: the footer groups run two links wide ══
   Below 520px .f-grid collapses to a single column, so each group
   became a vertical stack of two or three short links — "Numbers",
   "FAQ", "Privacy" — each on its own line down a column barely a
   third full. Three groups that way is most of a screen of footer.

   Each group becomes its own two-column grid, filling left to right,
   so Product reads 門號 / eSIM 流量 on the first line and 數據方案價格
   on the second. The heading spans both columns with grid-column
   1 / -1, otherwise it would take the first cell and push the first
   link up beside it.

   The first child is skipped: it holds the tagline and the social
   icons, not a link list.

   The vertical padding goes up to 9px. The links are now side by side
   with the gutter between them, and at 7px a mis-tap lands on the
   neighbouring line rather than on nothing — 40px of height is the
   smallest a touch target should be. */
@media(max-width:520px){
  .f-grid > div:not(:first-child){
    display:grid;grid-template-columns:1fr 1fr;
    column-gap:18px;align-items:start}
  .f-grid > div:not(:first-child) h4{grid-column:1 / -1}
  .f-grid > div:not(:first-child) a{
    padding:9px 0;line-height:1.45;overflow-wrap:anywhere}
}

/* Back to two. On a 370px screen that is about 168px a cell, which
   holds every translation on one line — three columns fitted Chinese
   at 110px but sent "Suporta sa Telegram" and the Thai labels onto
   two and three lines each. The font size goes back to the 14.5px the
   rest of the footer uses; overflow-wrap:anywhere stays as a guard
   against a long compound in a language nobody checked. */

/* ══ and the reason the dome was invisible: z-index ══
   Pinning --arc was necessary but not sufficient. The arc was being
   drawn at full height the whole time and painted underneath the
   hero.

   .hero-h is position:relative with z-index:1. .sec-arc is
   position:absolute with z-index:0, and on a phone #trust has no
   z-index of its own, so the arc is a level-0 box in the root
   stacking context sitting under a level-1 one. DOM order never gets
   consulted — z-index is compared first.

   Desktop never hit this because the min-width:901px block gives
   #trust z-index:3, alongside the margin-top:-100svh that pulls it
   over the hero. The phone block only ever set margin-top:0.

   z-index:3 to match. The two do not overlap below 901px — the
   section follows the hero rather than covering it — so the only
   thing this reorders is the 43px of arc that is meant to sit on the
   carrier band. The nav is at 90 and the support widget higher still;
   neither is touched. */
@media(max-width:900px){
  #trust{position:relative;z-index:3}
}

/* ══ phone hero: smaller headline, two photographs nudged ══
   The headline drops from clamp(25px,7.2vw,33px) to
   clamp(22px,6.6vw,30px) — about 25.7px on a 390px screen instead of
   28px. Twelve Chinese characters were still measuring just over the
   usable width at the old size, which is why slide 1 broke its first
   written line in two and ran to three lines. At 6.6vw they measure
   around 300px and the written break holds.

   The two photographs move by transform rather than
   background-position. These crops are 1200x2600 against a frame of
   almost exactly the same ratio, so cover leaves barely a pixel of
   slack to slide within — a background-position nudge would do
   nothing at all.

   Moving the element itself does work, but it uncovers the frame on
   the opposite edge, so each one carries enough scale to cover what
   the shift exposes: a 30px move on an ~845px-tall box needs about
   1.07 (the scale is centred, so it has to pay for both edges). Both
   sit at 1.08, and their off-state keeps the same 0.06 difference the
   other slides use, so the carousel's zoom is unchanged. */
@media(max-width:900px){
  .hp h1,.hp h2{font-size:clamp(22px,6.6vw,30px)}
  html[lang="fil-PH"] .hp h1,
  html[lang="fil-PH"] .hp h2{font-size:clamp(20px,5.6vw,26px)}

  /* Slides 1 and 4 are re-shot, so the nudges that were rescuing the
     old crops are gone — both are back on the plain carousel zoom the
     other two use. Say the word if you want them shifted again.

     What does need setting is the horizontal crop. These two arrive
     at 1492x2600 where the first pair were 1200x2600, and the frame
     is nearer 0.46 than 0.57 — so cover scales them to the frame's
     height and throws away about 145px from each side. Centred, that
     eats into the group on the right of slide 4 and the edge of the
     steps on slide 1. Pushing the focal point right keeps the
     subjects whole and spends the crop on the empty sky and grass
     instead. */
  /* slide 1 — down 20px. cover already scales this crop to the frame's
     height, so there is no vertical slack to shift into: the move has
     to be paid for with scale. 20px on an ~845px box needs about 1.05
     (centred, so both edges), and 1.06 leaves a margin. The off-state
     keeps the usual 0.06 of carousel zoom. */
  .hero .bgstage .bgshot.px-hero{transform:translateY(20px) scale(1.12)}
  .hero .bgstage .bgshot.px-hero.on{transform:translateY(20px) scale(1.06)}
  .hero .bgstage .px-hero{background-position:50% 50%}

  /* slide 2 — up 20px. Same arithmetic as slide 1; this crop is 1200
     wide against a ~390px box, so cover leaves nothing spare either
     way and the lift needs the same 1.06. */
  .hero .bgstage .bgshot.px-home{transform:translateY(-20px) scale(1.12)}
  .hero .bgstage .bgshot.px-home.on{transform:translateY(-20px) scale(1.06)}
  .hero .bgstage .px-home{background-position:50% 50%}

  /* slide 4 — up 40px, left 30px. The horizontal is what sets the
     scale now: the box is only ~390px wide, so 30px sideways needs
     about 1.15 to keep the far edge covered, against the 1.10 the
     40px lift asks of an ~845px height. 1.16 satisfies both; the
     off-state keeps the usual 0.06 of zoom. */
  /* slide 4 — 20px left and 30px up in total, enlarged again to 1.20.
     Coverage asks for 1.10 from the sideways move (20px on a ~390px
     box) and 1.07 from the lift (30px on ~845px), so at 1.20 the
     enlargement is still doing the work rather than paying for the
     shift. The off-state keeps the usual 0.06 of carousel zoom. */
  /* slide 4 — 20px left, 50px up, still at 1.20. Coverage needs 1.10
     for the sideways move (20px on a ~390px box) and 1.12 for the lift
     (50px on ~845px), so the existing scale still carries both and does
     not have to rise with this one. */
  /* now 60px up: 1 + 2x60/845 = 1.14, so the existing 1.20 still
     carries the lift and the scale does not have to rise. */
  .hero .bgstage .bgshot.px-friends{
    transform:translate(-20px,-60px) scale(1.26)}
  .hero .bgstage .bgshot.px-friends.on{
    transform:translate(-20px,-60px) scale(1.20)}
  .hero .bgstage .px-friends{background-position:50% 50%}
}

/* ══ phone hero: ranged left, to look at ══
   Undoing the centring from the earlier pass. Four declarations have
   to come off together, because centring the copy took four: the
   text-align on the panel, the flex alignment (the eyebrow and the
   button row are flex items, which text-align cannot reach), the auto
   margins on the lead paragraph, and the justification of the CTA row.

   The buttons stay side by side and still share the width — flex:1 1 0
   is doing that, not the centring — so the row looks the same. What
   moves is everything above it.

   Say the word and this block comes out; nothing else depends on it. */
@media(max-width:900px){
  .hero .hp{text-align:left;align-items:flex-start}
  .hero .hp .pill,.hero .hp .hpk{align-self:flex-start}
  .hero .hp p{margin-left:0;margin-right:0}
  .hero .hp .hero-cta{justify-content:flex-start}
}

/* ══ phone: a page indicator under the use-case row ══
   A horizontal scroller with a peeking card tells the reader there is
   more to the right, but not how much more — six cards feel the same
   as two until you run out. The bars say how many and which one.

   Built by script from the cards themselves rather than written into
   the markup, so adding or removing a use case cannot leave the count
   wrong.

   Shown only below 901px: above that the cards are a masonry block
   with nothing to page through. */
.uses-dots{display:none}

@media(max-width:900px){
  .uses-dots{
    display:flex;justify-content:center;align-items:center;gap:8px;
    margin:18px 0 0;padding:0 20px}
  .uses-dots button{
    appearance:none;-webkit-appearance:none;border:0;padding:0;
    width:22px;height:3px;border-radius:var(--r-pill);cursor:pointer;
    background:rgba(20,33,61,.16);
    transition:width .3s var(--e),background .3s var(--e)}
  .uses-dots button[aria-selected="true"]{
    width:36px;background:var(--honey)}
  .uses-dots button:focus-visible{
    outline:2px solid var(--honey);outline-offset:4px}
}

/* ══ phone: room between the feature list and the button ══
   Two things were closing that gap.

   .plan-actions is pushed down with margin-top:auto. In a flex column
   that only produces space when the card is taller than its contents —
   on a phone the card is exactly as tall as what is in it, so auto
   resolves to 0 and the button sat against the last list item with
   nothing between them. A padding-top is unconditional, so the gap
   exists whether or not there is free space to distribute.

   The overlap on top of that is the entrance animation: the list items
   are set to y:34 and staggered in, so an item still waiting its turn
   is sitting 34px lower than its own line — underneath the button,
   which is painted after it. The gap covers the worst of it, and the
   switch script now clears those transforms too. */
@media(max-width:900px){
  #plans .plan-actions{padding-top:26px}
  #plans .plan-list{margin-top:22px;gap:15px}
}

/* ══ phone: the section headings come down a size ══
   The hero and the plans heading are left alone — they are the two
   places on the page that are meant to be loud.

   Everything else was still sized off --fs6, which bottoms out at
   28px, or off its own mobile clamp set when the headings were the
   largest thing in their section. Three or four of those down a phone
   screen and every section shouts equally, which is the same as none
   of them doing it. They drop roughly 15%.

   The ring's closing heading is scaled separately: it runs off a much
   larger clamp of its own, so a flat percentage would not have moved
   it into line. It is written through .ring so it outranks the
   language-specific rules that set it earlier in the sheet.

   The how-it-works heading keeps its white-space:nowrap for CJK — the
   smaller size only makes that easier to hold. */
@media(max-width:900px){

  .ring .ring-copy h2,
  :is(html[lang^="zh"],html[lang^="ja"]) .ring .ring-copy h2,
  html[lang="fil-PH"] .ring .ring-copy h2{
    font-size:clamp(24px,6.4vw,32px);line-height:1.2}
}

/* ══ phone: the brand mark goes back up ══
   It was cut to 18px (16px under 400px) when the capsule held the
   brand, the language button and the sign-up button — 435px of
   content in a 350px bar, and the logo was the thing that could give.
   The language control has since moved into the menu sheet, so the
   bar now carries the brand, one button and the burger, and the
   pixels are there to give back.

   23px rather than the desktop's 24: the mark is three overlapping
   hexagons and needs the height to stay legible, but the phone
   capsule is shorter than the desktop one and a 24px mark starts
   crowding its top and bottom padding. Under 400px it goes to 20,
   which still clears the blob threshold the desktop rule warns about
   at 21. */
@media(max-width:900px){
  .cap .brand img{height:23px}
}
@media(max-width:400px){
  .cap .brand img{height:20px}
}

/* ══ phone: the nav goes back to being a capsule ══
   An earlier block turned it into a full-bleed bar — .nav padding to
   0, .cap to width:100% with border-radius:0 and its side borders
   removed. Three separate declarations, so restoring the shape takes
   three: the radius alone would do nothing while the element is still
   100% wide inside a bar with no padding.

   width:auto lets the capsule shrink to its contents and the padding
   on .nav holds it off the screen edges. The side borders come back
   by width only — their colour is already written by the two state
   rules (translucent white over the hero, transparent once stuck) and
   restating it here would freeze the capsule in one state.

   Inner padding goes to the 6/6/6/14 the capsule uses rather than the
   bar's flat 18: the sign-up button sits flush inside the right end of
   a pill, which is what gives it the nested look. */
@media(max-width:900px){
  .nav{padding:10px 10px 0}
  /* width:100% rather than auto: auto sizes the capsule to its three
     children, which on a 390px screen left about 45px of bare
     photograph down each side. It now takes the whole bar and the
     10px of .nav padding is the only inset — still a floating pill,
     just one that uses the width it has. .cap is a flex item, so the
     100% resolves against .nav's content box and the padding is
     honoured rather than overflowed. */
  .cap,.nav.stuck .cap{
    width:100%;max-width:100%;
    border-radius:var(--r-pill);
    border-left-width:1px;border-right-width:1px;
    padding:6px 6px 6px 16px}
}

/* ══ phone: the carrier row clears the dome ══
   The white arc on top of #trust sits above that section's edge,
   which means it overlaps the last ~43px of the hero — and the last
   thing in the hero is the carrier band. The label line survives
   because it is higher up; the row of names underneath it is right in
   the overlap.

   The band keeps its 26px of top padding and gains a deep bottom one.
   Padding below the content does not move the band's top edge, so the
   label does not shift — it lengthens the band downward and gives the
   arc 84px of empty navy to cover instead of the names. The arc
   itself is only ~43px, so the extra is clearance: the dome is widest
   at the centre of the screen, which is exactly where the names run,
   and sitting a name right on the curve reads as crowding even when
   nothing is actually covered. */
@media(max-width:900px){
  .hero-s .marq{padding-bottom:84px}
}

/* ══ phone: the plans heading breaks at its comma ══
   "免費開始，常用再加入會員。" was breaking wherever the line ran out,
   which put the break one character past the comma — "免費開始，常" over
   "用再加入會員。", splitting 常用 down the middle. CJK allows a line
   break between almost any two characters, so there is no CSS property
   that can be told to prefer the punctuation: line-break and
   word-break both govern where breaks are forbidden, not preferred.

   The two clauses are wrapped in the .cl spans the rest of the page
   already uses for this, and made inline-block below 901px. An
   inline-block wraps as one unit, so the second clause moves to the
   next line whole rather than being cut at whatever character
   happens to be at the edge. Above 901px they stay inline and the
   heading sets on one line as before.

   The spans go in the data-zh and data-cn strings rather than the
   markup, because the language script replaces the heading's
   innerHTML wholesale on every switch — anything written into the
   element itself is gone after the first change of language. */
@media(max-width:900px){
  .cta h2 .cl{display:inline-block}
}

/* ══ phone: the section leads follow their headings down ══
   The headings came down about 15% last round; the paragraphs under
   them did not, so in places the lead was sitting at 16.5px under a
   heading of 21 — close enough in size that the pair read as one
   block of text rather than as a title and its explanation.

   All of them go to 14.5px (14px for CJK, which carries more weight
   per character at the same size). The hero and the plans section are
   left alone, as with the headings.

   The CJK rules are restated separately rather than relying on the
   Latin one: the existing :is(html[lang^="zh"]...) declarations are
   more specific than a bare .uses-head p, so a single rule here would
   be overruled in exactly the two languages the site leads with. */
@media(max-width:900px){
  .uses-head p,
  .hw-head p,
  .wcu-head p,
  .cmp-head p,
  .cat-copy p,
  #trust .uses-head p,
  #howto .hw-head p{font-size:14.5px;line-height:1.75}

  :is(html[lang^="zh"],html[lang^="ja"]) .uses-head p,
  :is(html[lang^="zh"],html[lang^="ja"]) .hw-head p,
  :is(html[lang^="zh"],html[lang^="ja"]) .wcu-head p,
  :is(html[lang^="zh"],html[lang^="ja"]) .cmp-head p,
  :is(html[lang^="zh"],html[lang^="ja"]) .cat-copy p,
  :is(html[lang^="zh"],html[lang^="ja"]) #trust .uses-head p,
  :is(html[lang^="zh"],html[lang^="ja"]) #howto .hw-head p{
    font-size:14px;line-height:1.9}
}

/* ══ phone: one type scale for everything between the hero and the
   closing block ══
   Those two keep their own sizes — the hero is the first thing anyone
   sees and the ring is the last, and both are meant to be larger than
   the page they bracket. Everything in between now runs on four
   sizes and nothing else:

     section heading   clamp(21px, 6.2vw, 28px)
     section lead      14.5px  (CJK 14px)
     body copy         14.5px  (CJK 14px)
     small print       12.5px

   Before this, body copy alone was set at 13px, 13.5px, 14px, 14.5px
   and 15px in five different places, all of them a defensible choice
   for their own section and none of them agreeing with the others. A
   reader scrolling past four sections reads four slightly different
   paragraph sizes, which is felt as unevenness long before it is
   noticed as a size difference.

   The plans section joins the scale: its heading drops from --fs7
   (36px on a phone) to the shared size. It was a step larger than
   everything else, which is defensible on its own — it is the page's
   last call — but it is exactly what you asked to level.

   Bold leads inside a paragraph (.hw-copy b) stay one step up at
   15.5px: they are a heading for their own card, not body copy, and
   flattening them would leave those cards with no internal hierarchy
   at all. */
@media(max-width:900px){
  /* headings */
  .cta h2,
  #plans.cta h2,
  .wcu-head h2,.cmp-head h2,.cat-copy h2,.faq-title,
  #trust .uses-head h2,
  #howto .hw-head h2{letter-spacing:-.03em}

  /* leads */
  .cta p,#plans.cta > .wrap > p{font-size:14.5px;line-height:1.75}
  :is(html[lang^="zh"],html[lang^="ja"]) .cta p,
  :is(html[lang^="zh"],html[lang^="ja"]) #plans.cta > .wrap > p{
    font-size:14px;line-height:1.9}

  /* body copy */
  .wcu-card p,
  #whyus .wcu-grid .wcu-card p,
  .hw-copy,#howto .hw-copy,
  .uses-grid .ucap p,
  #trust .uses-grid .ucap p,
  .plan-list li,
  .qa .a p{font-size:14.5px;line-height:1.75}
  :is(html[lang^="zh"],html[lang^="ja"]) .wcu-card p,
  :is(html[lang^="zh"],html[lang^="ja"]) #whyus .wcu-grid .wcu-card p,
  :is(html[lang^="zh"],html[lang^="ja"]) .hw-copy,
  :is(html[lang^="zh"],html[lang^="ja"]) #howto .hw-copy,
  :is(html[lang^="zh"],html[lang^="ja"]) .uses-grid .ucap p,
  :is(html[lang^="zh"],html[lang^="ja"]) #trust .uses-grid .ucap p,
  :is(html[lang^="zh"],html[lang^="ja"]) .plan-list li,
  :is(html[lang^="zh"],html[lang^="ja"]) .qa .a p{
    font-size:14px;line-height:1.9}

  /* the card's own lead line keeps one step of hierarchy */
  #howto .hw-copy b,
  :is(html[lang^="zh"],html[lang^="ja"]) #howto .hw-copy b{
    font-size:15.5px;line-height:1.6}

  /* small print */
  .cta .fine,
  .plan-note,
  .plan-fine,.cta .plan-card .plan-fine,
  #numbers .cnote,
  .plan-card .plan-price-hero .plan-amount-label,
  .plan-member .plan-price-hero .plan-amount-label,
  .hw-video-note i{font-size:12.5px;line-height:1.7}
  :is(html[lang^="zh"],html[lang^="ja"]) .plan-fine,
  :is(html[lang^="zh"],html[lang^="ja"]) .cta .plan-card .plan-fine,
  :is(html[lang^="zh"],html[lang^="ja"]) .plan-card .plan-price-hero .plan-amount-label,
  :is(html[lang^="zh"],html[lang^="ja"]) .plan-member .plan-price-hero .plan-amount-label{
    font-size:12.5px;line-height:1.8}
}

/* ══ phone: the FAQ topic tabs are put back ══
   The filter was entirely built already — .faq-tabs is styled, the
   .faq-list[data-filter] rules hide the non-matching rows, and the
   script at the foot binds the buttons. Only the three buttons were
   missing from the markup, so nothing was wiring them up. They are
   added back; no new behaviour was written.

   Two things did have to be added.

   The group headings had no topic, so filtering to Numbers left the
   "eSIM data" heading standing over nothing. They now carry
   data-topic and are hidden by the same rule as the rows.

   And the tabs are phone-only for now — .faq-tabs is styled for both
   widths, but the brief is mobile. One line removes the restriction
   if you want them on desktop too. */
@media(min-width:901px){
  section#faq .faq-tabs{display:none}
}
.faq-list[data-filter="num"]  .faq-group:not([data-topic~="num"]),
.faq-list[data-filter="esim"] .faq-group:not([data-topic~="esim"]){display:none}

@media(max-width:900px){
  section#faq .faq-tabs{display:inline-flex;margin-bottom:var(--sp2)}
  .faq-tabs button{padding:9px 15px}
}

/* ══ phone: the plans section joins the scale, card titles with it ══
   Three things in that section were still on their own sizes, and two
   of them turned out to be part of a wider gap.

   Card titles. .plan-card h3 was --fs4 (18px on a phone) while the
   why-us cards ran 20px, the use-case captions 16px and the step
   labels 15px — four card titles, four sizes, none of them agreeing.
   They all go to 17px (17.5px for CJK, which sits a touch small at
   the same nominal size). This is the layer the earlier pass missed:
   it set headings, leads, body and small print, but a card title is
   none of those.

   Buttons. The plans CTA was 15px against the hero's 14.5px. Both go
   to 14.5.

   Segmented controls. The plan switch was 13.5px and the FAQ tabs
   13px — same component, same job, now both 13px.

   Deliberately left alone: .plan-amount, the clamp(38px…) price. It
   is the number the whole section exists to show, and levelling it
   into the body scale would be flattening the page rather than
   unifying it. Say so if you want it in too. */
@media(max-width:900px){
  .plan-card h3,
  .wcu-card h3,
  #whyus .wcu-grid .wcu-card h3,
  #whyus .wcu-grid .wcu-card:nth-child(1) h3,
  .uses-grid .ucap h3,
  #trust .uses-grid .ucap h3,
  .hw-label,#howto .hw-label{
    font-size:17px;line-height:1.4;letter-spacing:-.02em}
  :is(html[lang^="zh"],html[lang^="ja"]) .plan-card h3,
  :is(html[lang^="zh"],html[lang^="ja"]) .wcu-card h3,
  :is(html[lang^="zh"],html[lang^="ja"]) #whyus .wcu-grid .wcu-card h3,
  :is(html[lang^="zh"],html[lang^="ja"]) #whyus .wcu-grid .wcu-card:nth-child(1) h3,
  :is(html[lang^="zh"],html[lang^="ja"]) .uses-grid .ucap h3,
  :is(html[lang^="zh"],html[lang^="ja"]) #trust .uses-grid .ucap h3,
  :is(html[lang^="zh"],html[lang^="ja"]) .hw-label{
    font-size:17.5px;line-height:1.45;letter-spacing:0}

  #plans .plan-cta{font-size:14.5px}
  .plan-tab,.faq-tabs button{font-size:13px}
  .plan-more{font-size:14.5px}
  .plan-more-inline{font-size:inherit}
}

/* ══ phone: "限時" stays on the price line ══
   .plan-amount-row is flex-wrap:wrap, so when the three items — the
   $0, the struck regular price and the tag — do not fit, the tag is
   the one that drops. On a phone the box has about 246px of inner
   width and the three were asking for a little more than that, so the
   tag landed under the amount on its own line, where it reads as a
   caption on the $0 rather than as a qualifier on the offer.

   The row is set to nowrap and the three shrink to fit instead. The
   amount goes to a viewport-relative clamp so it gives ground on
   narrow screens, and the struck price does the same — it is the least
   important of the three and can afford it. The tag keeps its
   padding but loses a point of type and its left margin.

   nowrap does mean there is no fallback below about 340px if a
   currency ever produces a longer figure than NT$1,200 — at that
   point the struck price is the thing to drop, not the tag. */
@media(max-width:900px){
  .plan-amount-row{flex-wrap:nowrap;align-items:center;gap:8px;min-width:0}

  .plan-card .plan-price-hero .plan-amount,
  .plan-member .plan-price-hero .plan-amount{
    font-size:clamp(28px,7.8vw,38px)}

  .plan-member .plan-price-hero .plan-was{
    font-size:clamp(13px,4.1vw,16px)}

  .plan-member .plan-price-hero .plan-amount-row .price-tag{
    font-size:10.5px;padding:4px 8px;margin-left:0;flex:0 0 auto}
}

/* ══ phone: the tabs sit on the list, the buttons go under it ══
   The section is a two-column grid — copy and tabs on the left, the
   country list on the right — and stacked, that order puts the tabs a
   whole heading, a lead and two buttons away from the thing they
   control. Nothing on screen says the pills and the list belong
   together.

   Reordering means reaching three levels down (.cat-grid >
   .cat-left > .cat-sticky > .cat-copy > h2), and `order` only sorts
   direct children of a flex container. display:contents on the three
   wrappers dissolves them, so the heading, the lead, the tabs, the
   button row and the list all become siblings in one flex column and
   can be sorted freely. The wrappers carry no background or padding
   of their own, so nothing is lost by removing their boxes.

   display:contents does not defeat the [hidden] attribute — the
   stylesheet's [hidden]{display:none!important} still wins — so the
   inactive pane's children stay gone, which is what keeps the tabs
   switching panes rather than showing both.

   The tabs then stretch the full width with the two pills sharing it,
   and sit 12px above the list against the 20px under the lead: the
   tighter gap is what pairs them with the list rather than with the
   copy. Flex gap is set to 0 and the spacing written as margins,
   because one gap value cannot say both things.

   The eSIM pane's buttons needed a .cat-cta wrapper to move with the
   rest — the numbers pane had one, that pane did not. That is a
   markup change, so it also applies on desktop, where it gives those
   two buttons the same 12px gap as the other pane. */
@media(max-width:900px){
  /* align-items:start comes from the desktop grid rule, where it means
     "both columns hang from the top". Turning the container into a
     flex column turns that same value into a cross-axis rule, so every
     child shrank to its own content width — which is why the eSIM
     list, whose rows are short, came out about two-thirds the width of
     the numbers list. stretch is the flex default and is what the grid
     was giving these children anyway. */
  #numbers .cat-grid{display:flex;flex-direction:column;gap:0;
    align-items:stretch}
  #numbers .cat-left,
  #numbers .cat-sticky,
  #numbers .cat-copy{display:contents}

  #numbers .cat-copy h2{order:1;margin:0 0 12px}
  #numbers .cat-copy p{order:2;margin:0 0 20px}

  #numbers .cat-tabs{
    order:3;
    display:flex;align-self:stretch;width:100%}
  #numbers .cat-tabs button{text-align:center}

  #numbers .cat-right{order:4}
  #numbers .cat-copy .cat-cta{order:5;margin:22px 0 0}
  #numbers .cat-copy .cat-cta .btn{flex:1 1 0;justify-content:center}
}

/* ══ phone: the tabs and the list are one card ══
   Sitting 12px apart, the pills and the rows still read as two
   objects that happen to be near each other. Joined, the tabs become
   the header of the thing they filter and there is nothing left to
   infer.

   The gap goes to zero and the two halves share one outline: the tab
   bar is rounded at the top only and drops its bottom border, the
   list is rounded at the bottom only and drops its top one, so the
   1px runs continuously around both. The bar keeps the --sunk grey it
   already had, which is now doing a second job — it separates the
   header from the white rows without needing a rule between them.

   The rows gain side padding. .crow pays only 2px because on the open
   page it sits against the section's own margin; inside a bordered
   card that leaves the flags and the prices against the edge.

   .cat-right takes overflow:hidden so the corners actually clip the
   first and last rows. That also clips .crow::before, the hover
   surface that bleeds 10px either side — no loss on a phone, where
   there is no hover, and it is what stops the highlight from
   squaring off the rounded corners. */
@media(max-width:900px){
  /* The field stays white. The card then has nothing to sit on — a
     white shape on a white page is not a shape — so the job that the
     grey background was doing passes to a hairline and a low shadow.
     That is the trade: the reference gets its edges for free from the
     contrast, this version has to draw them. The tab track keeps its
     grey, which is now the only tonal step in the block and does the
     work of marking the control as a control. */

  /* the control: a grey track with a white thumb, rather than two
     pills on a bar. 999px on the track and the thumb, one padding
     value between them, and the selected half is the only white. */
  #numbers .cat-tabs{
    margin:0 0 20px;padding:5px;gap:0;
    background:#E8EAED;border:0;border-radius:var(--r-pill)}
  #numbers .cat-tabs button{
    flex:1 1 0;padding:13px 8px;border-radius:var(--r-pill);
    font-size:15px;color:#6B7280;background:none;box-shadow:none}
  #numbers .cat-tabs button[aria-selected="true"]{
    background:#fff;background-image:none;color:var(--navy);
    box-shadow:0 1px 2px rgba(20,33,61,.06),
               0 3px 8px -2px rgba(20,33,61,.10)}
  #numbers .cat-list{border-top:0}

  /* rows: air above and below, and the separator inset from the card
     edge so it reads as dividing the rows rather than cutting the
     card in half. The last row has nothing under it to divide. */
  #numbers .cat-list .crow{
    padding:18px 18px;border-bottom:0;position:relative}
  #numbers .cat-list .crow + .crow::after{
    content:"";position:absolute;left:18px;right:18px;top:0;
    height:1px;background:#EDEEF1}

  #numbers .cnote{margin-top:16px}
}

/* ══ phone: explicit centring in the catalogue block ══
   Two places where the centring was being left to a default that does
   not hold here.

   1 · The tab labels. .cat-tabs button carries padding:10px 20px from
       the base rule and the phone override only replaced the values,
       not the fact that the padding is symmetrical against a button
       that is now flex:1 1 0 rather than shrink-to-fit. A button's
       text centres by default, but only while the button is a block
       of its own width — as a stretched flex item with nowrap text it
       needs justify-content as well, because the base rule makes it a
       flex box and text-align has no say over flex content.

   2 · The row. .crow is a grid with align-items:center, but .cmain
       and .cmoney are flex columns inside it and their own cross-axis
       alignment is what positions the lines within them. .cmoney
       holds two lines and .cmain one, so without align-self the
       single line sits against the top of a two-line-tall track.
       Stated on all three so the flag, the country and the price all
       share one centre line. */
@media(max-width:900px){
  #numbers .cat-tabs button{
    display:flex;align-items:center;justify-content:center}

  #numbers .cat-list .crow{align-items:center}
  #numbers .cat-list .crow .cflagx,
  #numbers .cat-list .crow .cmain,
  #numbers .cat-list .crow .cmoney{align-self:center}
  #numbers .cat-list .crow .cmain{justify-content:center}
}

/* ══ phone: the average-cost note sits outside the card ══
   It was written inside .cat-list while the card's border, radius and
   overflow:hidden live on .cat-right one level up, so the note was
   inside the box by construction — no amount of margin was going to
   get it out.

   The note moves to be a sibling of the two list panes and the card
   styling moves down a level onto .cat-list itself. It keeps a
   data-pane of its own so the tab script still hides it with the rest
   of the numbers pane: the note is about monthly averages on numbers
   and says nothing true about eSIM data.

   .cat-right is left as a bare wrapper — no background, no border, and
   overflow back to visible so the card below it can cast its shadow. */
@media(max-width:900px){
  #numbers .cat-right{
    background:none;border:0;box-shadow:none;
    border-radius:0;overflow:visible}

  #numbers .cat-list{
    background:#fff;overflow:hidden;
    border:1px solid #ECEDEF;
    border-radius:22px;
    box-shadow:0 1px 2px rgba(20,33,61,.04),
               0 12px 28px -18px rgba(20,33,61,.16)}

  #numbers .cnote{margin:14px 0 0;padding-inline:4px;text-align:left}
}

/* ══ phone: one value for every section heading ══
   The use-case heading was on clamp(20px,5.8vw,27px) and the rest on
   clamp(21px,6.2vw,28px) — about 22.6px against 24px on a 390px
   screen. Small enough that no single heading looks wrong and large
   enough that two of them in the same scroll do not look equal, which
   is exactly the kind of difference that reads as sloppiness rather
   than as hierarchy.

   Everything takes the smaller of the two, since that is the one you
   are comparing against. The how-it-works heading keeps its own
   smaller CJK clamp — it is the one that has to hold twelve
   characters on a single line. */
@media(max-width:900px){
  .cta h2,#plans.cta h2,
  .wcu-head h2,.cmp-head h2,.cat-copy h2,.faq-title,
  #trust .uses-head h2,
  #howto .hw-head h2{font-size:clamp(20px,5.8vw,27px)}
  :is(html[lang^="zh"],html[lang^="ja"]) #howto .hw-head h2{
    font-size:clamp(18px,5.6vw,25px)}
}

/* ══ phone: the plan switch gets the catalogue thumb ══
   The same component now, not a copy of it: the script mounts on both
   bars and the .cat-thumb / .cat-clamp / .cat-lit rules are shared.
   What differs is only what the thumb is made of — honey on the navy
   card rather than navy on a grey track — and how the label behaves,
   since these two labels can run to two lines where the catalogue's
   never do.

   .plan-switch is display:grid, but the thumb is position:absolute
   and an absolutely positioned grid child takes no cell, so it does
   not become a third column. Its 4px of padding already matches what
   .cat-clamp and the clip inset assume. */
@media(max-width:900px){
  .plan-switch.has-thumb{
    position:relative;isolation:isolate;
    -webkit-user-select:none;user-select:none;touch-action:pan-y}
  .plan-switch.has-thumb .plan-tab,
  .plan-switch.has-thumb .plan-tab[aria-selected="true"]{
    position:relative;z-index:1;
    background:none;box-shadow:none;
    color:rgba(255,255,255,.62);
    transition:color .2s var(--e),opacity .2s var(--e)}
  .plan-switch.has-thumb .plan-tab.is-held{opacity:.5}

  .plan-switch .cat-lit{
    background:var(--honey);background-image:none}
  .plan-switch .cat-lit span{
    color:var(--hive);font-size:13px;font-weight:600;
    white-space:normal;line-height:1.3;padding:0 8px;text-align:center}

  .plan-switch.is-pressing .cat-lit{--tp:3px;transition:clip-path .16s ease-out}
  .plan-switch.is-dragging .cat-lit{transition:none}
  .plan-switch.no-anim .cat-lit{transition:none}
}
@media(max-width:900px) and (prefers-reduced-motion:reduce){
  .plan-switch .cat-lit,
  .plan-switch.has-thumb .plan-tab{transition:none!important}
  .plan-switch.is-pressing .cat-lit{--tp:0px}
}

/* ══ phone: the eSIM list is built like the numbers list ══
   The destinations pane was shrinking to its content instead of
   filling the card, so the rows ended wherever "選擇方案" happened to
   fall and the white panel was two-thirds the width of the control
   above it. width:100% states outright what the numbers list gets by
   default, and the row is given the same three-column grid, the same
   18px of padding and the same inset separator, so the two panes are
   the same object with different contents rather than two lists that
   merely sit in the same place.

   .cgo goes to the third column with justify-self:end. It was placed
   there already, but in a track that was never allowed to grow there
   was nothing for "end" to mean — it sat against the country name.

   The last row drops its separator: ::after is drawn on every .crow
   that follows another one, and the rule is shared with the numbers
   pane, so this only has to say that the dst rows are .crow too. */
@media(max-width:900px){
  #numbers .cat-list.dests{display:block;width:100%}

  #numbers .cat-list .crow.dst{
    width:100%;
    grid-template-columns:auto minmax(0,1fr) auto;
    column-gap:14px;row-gap:0;align-items:center;
    padding:18px}
  #numbers .cat-list .crow.dst .cflagx{grid-column:1;grid-row:1}
  #numbers .cat-list .crow.dst .cmain{grid-column:2;grid-row:1;min-width:0}
  #numbers .cat-list .crow.dst .cgo{
    grid-column:3;grid-row:1;justify-self:end;align-self:center;
    margin:0;white-space:nowrap}
}

/* ══ phone: clause boxes, so a break lands on a mark ══
   .ph is written by the script around each clause. inline-block is
   the whole mechanism: the box wraps as a unit, so a line can only
   end after 、，；：。！？ — and since a box that fits needs no break,
   a short string still sets on one line. Nothing is ever forced.

   Phone only. On a wider screen the same headings have room and the
   browser's own breaking is already landing in sensible places; the
   boxes exist in the markup at every width but only behave as units
   below 901px. */
.ph{display:inline}
@media(max-width:900px){
  .ph{display:inline-block}
}

/* ══ phone: the list card breathes at top and bottom ══
   The rows run edge to edge against a 22px radius, so the first and
   last rows are cut by the curve — the flag on row one and the price
   on the last row sit right where the corner turns.

   The padding goes on the list rather than on the rows: adding it to
   .crow would space every row from its neighbours as well, and the
   separators are what divide them. 10px top and bottom is enough to
   clear the radius without making the card look like it has a header
   and a footer. */
@media(max-width:900px){
  #numbers .cat-list{padding-block:10px}
}

/* ══ phone: both panes keep the same row height ══
   The width matches now, but the card still jumped on every switch:
   a numbers row carries two lines of price and an eSIM row carries
   one name, so the same six rows came out about 80px each against
   about 61px, and the card lost a fifth of its height mid-tap.

   A min-height on the row fixes it at the taller of the two. 80px is
   not a guess — on a phone the type in these rows does not scale:
   --fs4 and --fs5 both bottom out at their clamp minimums (18px and
   22px) at every width from 320px to 440px, so the numbers row is
   80px on every phone rather than a range. The eSIM row simply
   centres its single line in the same box.

   Put on .crow rather than on the list, so it holds whichever pane is
   showing and does not depend on how many rows each one has. */
@media(max-width:900px){
  #numbers .cat-list .crow{min-height:80px}
}

/* ══ phone: the FAQ group headings come out ══
   "第二門號" and "eSIM 數據" were the only thing grouping the questions
   before the tabs existed. Now the tab above the list says which
   group is showing, and only one group is ever on screen at a time —
   so the heading repeats the tab and then heads a list of everything
   there is.

   display:none rather than removal from the markup: the headings
   still carry the data-topic the filter reads, and above 901px, where
   the tabs are hidden and both groups are listed together, they are
   the only thing separating them. */
@media(max-width:900px){
  section#faq .faq-group{display:none}
  section#faq .faq-list > .qa:first-of-type{margin-top:0}
}

/* ══ phone: a swipe hint, on the first card only ══
   The three steps are a horizontal scroller and the peek of card two
   is the only thing saying so. In the first card there is room to say
   it in words — that card's copy is the shortest of the three, so the
   space at its foot exists whether or not anything is put in it (the
   row is align-items:stretch, so every card is as tall as the
   tallest).

   Only the first card carries it. Repeating "swipe right" on all
   three would be telling someone who has already swiped how to swipe.

   It removes itself once the scroller has been moved at all: a hint
   that stays after it has been acted on stops being a hint. */
.hw-swipe{display:none}

@media(max-width:900px){
  #howto .hw-step:first-child .hw-swipe{
    display:inline-flex;align-items:center;gap:7px;
    margin-top:auto;padding-top:18px;
    align-self:center;
    font-family:var(--mono);font-size:11px;letter-spacing:.1em;
    text-transform:uppercase;color:#AEB4C0;
    transition:opacity .35s var(--e)}
  :is(html[lang^="zh"],html[lang^="ja"]) #howto .hw-step:first-child .hw-swipe{
    font-family:var(--display);font-size:12px;letter-spacing:.06em;
    text-transform:none}
  #howto .hw-swipe svg{width:14px;height:14px;flex:none}
  #howto .hw-grid.is-swiped .hw-swipe{opacity:0;pointer-events:none}
}

/* ══ phone: arrows on the use-case row ══
   The buttons sit over the left and right edge of the card, centred
   on it — --y is written by the script, because .uses-body holds the
   heading as well and the scroller's middle is not the section's.

   pointer-events are off on the strip and back on for the buttons, so
   the 40px-tall band across the card does not swallow a swipe that
   starts between them.

   :disabled is what hides them at the ends. Visibility rather than
   display so nothing reflows, and the transition makes the first
   card's missing left arrow read as "nothing to go back to" rather
   than as a button that failed to draw. */
.uses-arrows{display:none}

@media(max-width:900px){
  .uses-arrows{
    display:block;position:absolute;z-index:4;
    left:0;right:0;top:var(--y,50%);height:0;
    pointer-events:none}

  .uses-arrow{
    position:absolute;top:-20px;
    width:40px;height:40px;padding:0;border:0;
    display:grid;place-items:center;
    border-radius:var(--r-pill);cursor:pointer;
    background:rgba(255,255,255,.92);color:var(--navy);
    -webkit-backdrop-filter:blur(8px);backdrop-filter:blur(8px);
    box-shadow:0 1px 2px rgba(20,33,61,.10),
               0 6px 16px -6px rgba(20,33,61,.30);
    pointer-events:auto;
    transition:opacity .25s var(--e),transform .2s var(--e)}
  .uses-arrow svg{width:18px;height:18px}
  .uses-arrow:active{transform:scale(.92)}
  .uses-prev{left:2px}
  .uses-next{right:2px}

  .uses-arrow:disabled{opacity:0;visibility:hidden;pointer-events:none}
}

/* ══ phone: the FAQ tabs get the thumb as well ══
   Third mount of the same module. The catalogue's colouring carries
   over unchanged — a navy thumb with white labels on a pale track is
   exactly what these two already were — so this only has to hand
   .faq-tabs the structural rules that .cat-tabs.has-thumb owns:
   a positioned, isolated box, and buttons pushed above the thumb with
   their own fill removed so the thumb is the only thing painting the
   selection.

   The labels on the thumb take the 13px the FAQ tabs use rather than
   the catalogue's 14px — the white copy has to land glyph for glyph
   over the grey one underneath, and a point of difference would show
   as a blur along every edge.

   .faq-tabs already pays 4px of padding, which is what .cat-clamp and
   the clip inset assume, so the thumb sits in its track without any
   adjustment. */
@media(max-width:900px){
  section#faq .faq-tabs.has-thumb{
    position:relative;isolation:isolate;
    -webkit-user-select:none;user-select:none;touch-action:pan-y}
  section#faq .faq-tabs.has-thumb button,
  section#faq .faq-tabs.has-thumb button[aria-selected="true"]{
    position:relative;z-index:1;
    background:transparent;background-image:none;box-shadow:none;
    color:#646C7F;
    transition:color .2s var(--e),opacity .2s var(--e)}
  section#faq .faq-tabs.has-thumb button.is-held{opacity:.5}

  section#faq .faq-tabs .cat-lit span{font-size:13px}

  section#faq .faq-tabs.is-pressing .cat-lit{--tp:3px;transition:clip-path .16s ease-out}
  section#faq .faq-tabs.is-dragging .cat-lit{transition:none}
  section#faq .faq-tabs.no-anim .cat-lit{transition:none}
}
@media(max-width:900px) and (prefers-reduced-motion:reduce){
  section#faq .faq-tabs .cat-lit,
  section#faq .faq-tabs.has-thumb button{transition:none!important}
  section#faq .faq-tabs.is-pressing .cat-lit{--tp:0px}
}

/* ══ desktop: the frost stops blinking, without moving anything ══
   Same cause as the phone had: backdrop-filter samples the backdrop
   only as far as the nearest isolated ancestor, and an ancestor with
   opacity below 1 is exactly that. While .hp cross-fades, the button's
   backdrop is the half-painted panel rather than the photograph, so
   the blur has nothing to sample and switches off for the duration.

   The phone fixed it structurally — the fade moved down to .hp's
   children with .hero-cta excluded — but that only works there because
   every panel is given the same min-height and the CTA is pushed to
   the foot of it, so the buttons sit on one line whatever the copy
   does. On a desktop .hero-text is a centred grid: each panel is as
   tall as its own copy and centres itself, so the four CTAs are at
   four slightly different heights. Stopping them fading would turn a
   crossfade into a visible jump.

   So the loss is hidden instead of prevented. A 14% white fill over a
   bright photograph is nearly nothing once the blur goes, which is why
   the button appeared to vanish; a navy tint at 28% is a surface in
   its own right — blurred it reads as smoked glass, unblurred as a
   tinted pill, and the swap between them passes unnoticed.

   backdrop-filter is also out of the hover transition. Animating a
   blur radius re-rasterises the sampled region every frame, and on the
   frames where the value has moved but the layer has not been redrawn
   it flicks: the same fault in miniature. */
@media(min-width:901px){
  /* The blur is gone on desktop — the tint alone now. That settles the
     flicker at its source rather than hiding it: with no
     backdrop-filter there is nothing for the panel's opacity to
     isolate, so nothing can switch off mid-crossfade. The button looks
     the same in every frame because it is the same in every frame.

     The tint goes from 28% to 34%. The blur was doing part of the work
     of separating the label from the photograph — smoothing whatever
     detail sat behind it — and without it the sky's clouds read
     straight through. Four points of opacity is roughly what that
     smoothing was worth.

     backdrop-filter is explicitly cleared rather than just left out:
     an earlier, unscoped rule sets it for both widths, and the phone
     still wants it. And the @supports fallback goes with it — there is
     no longer a feature to fall back from. */
  .hero .b-line{
    background:rgba(16,26,47,.34);
    border-color:rgba(255,255,255,.38);
    -webkit-backdrop-filter:none;backdrop-filter:none;
    transition:transform .3s var(--e),background .3s,color .3s,
               border-color .3s}
  .hero .b-line:hover{
    background:rgba(16,26,47,.46);
    border-color:var(--honey);color:var(--honey);
    -webkit-backdrop-filter:none;backdrop-filter:none}
}

/* ══ desktop: the why-us cards answer the pointer ══
   The existing hover only warms the outline, which is a state change
   rather than a response — it looks the same wherever in the card the
   pointer is. These are not links, so nothing should lift or invite a
   click; what they can do is acknowledge where the pointer is.

   A radial highlight follows the cursor inside the card. --mx and --my
   are written by the script in px; the gradient is painted on ::before
   at z-index:-1, which inside .wcu-card's own stacking context
   (isolation:isolate is already set) puts it over the card's fill and
   under its text. ::after is taken on the first card by the radar
   rings, which is why this uses ::before.

   The colour is per card rather than one value: honey on the navy
   tile and on the two white ones, white on the honey-tinted fourth,
   where honey on honey would be invisible.

   The icon lifts 2px. Small enough not to read as a button, and it is
   the one element in the card that is already an object rather than
   text.

   @media(hover:hover) throughout, so none of it arms on a touch
   screen where :hover sticks after a tap. */
@media(min-width:901px) and (hover:hover){
  #whyus .wcu-grid .wcu-card{--glow:rgba(240,165,0,.16)}
  #whyus .wcu-grid .wcu-card:nth-child(2),
  #whyus .wcu-grid .wcu-card:nth-child(3){--glow:rgba(240,165,0,.13)}
  #whyus .wcu-grid .wcu-card:nth-child(4){--glow:rgba(255,255,255,.55)}

  #whyus .wcu-grid .wcu-card::before{
    content:"";position:absolute;inset:0;z-index:-1;
    pointer-events:none;opacity:0;
    background:radial-gradient(220px circle at var(--mx,50%) var(--my,50%),
      var(--glow), transparent 72%);
    transition:opacity .35s var(--e)}
  #whyus .wcu-grid .wcu-card:hover::before{opacity:1}

  #whyus .wcu-grid .wcu-card .wcu-ico{
    transition:transform .3s var(--e),background-color .3s var(--e)}
  #whyus .wcu-grid .wcu-card:hover .wcu-ico{transform:translateY(-2px)}
}
@media(prefers-reduced-motion:reduce){
  #whyus .wcu-grid .wcu-card::before{transition:none}
  #whyus .wcu-grid .wcu-card:hover .wcu-ico{transform:none}
}

/* ══ phone: arrows on the steps row too ══
   The swipe hint is gone; the arrows say the same thing and can also
   do it. They reuse the .uses-arrow classes rather than getting a set
   of their own — same size, same placement, same disabled behaviour at
   the two ends — so the two scrollers on the page behave identically.

   .hw-body needs position:relative to hold them. On a desktop it
   carries the scroll-linked rise transform, which would already make
   it a containing block, but below 901px that script removes its
   properties, so the position has to be stated. */
@media(max-width:900px){
  #howto .hw-body{position:relative}
  #howto .hw-arrows .uses-arrow{
    background:rgba(255,255,255,.94);color:var(--navy)}
}

/* ══ phone: every section head is centred ══
   Badge, heading and lead, in each section except the hero. The plans
   and FAQ heads were centred already; the other four were ranged left
   from the desktop two-column layouts they came from, where the head
   sits in its own column beside something else. Stacked, there is no
   second column and nothing for the left edge to align to.

   text-align on the head is enough for the badge and the eyebrow —
   both are inline-flex, which is an inline-level box, so a centred
   line centres them. What it cannot reach is a max-width: a paragraph
   capped at 24em is centred text inside a left-hung box, so the auto
   margins have to be set as well.

   #numbers is the exception in how it is written: .cat-copy is
   display:contents there (that is what let the tabs be reordered
   between the lead and the list), so its children are flex items of
   .cat-grid and are centred individually rather than through a
   parent. */
@media(max-width:900px){
  #trust .uses-head,
  #howto .hw-head,
  #whyus .wcu-head,
  #compare .cmp-head,
  .ring .ring-copy{text-align:center}

  #trust .uses-head p,
  #howto .hw-head p,
  #whyus .wcu-head p,
  #compare .cmp-head p,
  .ring .ring-copy p{margin-left:auto;margin-right:auto}

  #trust .uses-head h2,
  #howto .hw-head h2,
  #whyus .wcu-head h2,
  #compare .cmp-head h2,
  .ring .ring-copy h2{margin-left:auto;margin-right:auto}

  /* .cat-copy is display:contents, so these are flex items of the
     grid and take their own alignment */
  #numbers .cat-copy h2,
  #numbers .cat-copy > p{text-align:center;margin-left:auto;margin-right:auto}
  #numbers .cat-tabs + .cat-copy,
  #numbers .cat-copy .badge{align-self:center}
}

/* ══ desktop: the eSIM rows stand as tall as the number rows ══
   A number row is sized by its price block — two lines, 7px apart —
   while an eSIM row now holds a country name and nothing else, so the
   same six rows came out visibly tighter and the two lists stopped
   looking like one component when you switch between them.

   A min-height on the destination rows, built from the same tokens the
   number row is actually made of rather than a measured pixel value:
   the vertical padding twice, the list price at its own line-height,
   the 7px gap, and the member line's 18px box. It therefore tracks the
   viewport the way --sp2 and --fs4 do, instead of being right at one
   window width and wrong at every other.

   min-height rather than height, and only on .dst: it can make the
   short list taller, never the tall one shorter, so no row can be
   clipped if a translation runs long. The rows are already
   align-items:center, so the single line sits in the middle of the
   space it gains. */
@media(min-width:901px){
  .crow.dst{
    min-height:calc(var(--sp2) * 2 + var(--fs4) * 1.15 + 7px + 18px)}
}

/* ══ the line under each price comes out ══
   "Sign up free; buy when you need to." on the free card and the
   fee-waiver condition on the member card. Both widths — a line of
   copy that exists on a desktop and not on a phone is a different
   page, not a responsive one.

   .plan-card covers both, since .plan-member carries that class too.

   The element stays in the DOM, and that is deliberate: the script
   that levels the two price boxes observes .plan-amount-label rather
   than the boxes themselves, precisely because it writes minHeight to
   the boxes and observing what you resize is how a ResizeObserver
   loops. Hidden, it reports zero once and goes quiet; the levelling
   still runs on resize, on a language change, and at load. With both
   labels gone the two boxes are structurally identical anyway, so
   there is little left to level — but the guard costs nothing and
   removing the element would have cost the script its safe target. */
#plans .plan-price-hero .plan-amount-label{display:none}

/* ══ phone: a chevron after "See plans" ══
   The label is the only thing in that cell and it reads as a caption
   rather than as somewhere to go. A chevron says the row leads
   somewhere without adding a second tap target.

   Drawn with two borders on a rotated box rather than an SVG or a
   glyph: it inherits currentColor, so it follows the label through
   every state without a second colour to maintain, and it stays a
   crisp 1.8px at any zoom — a "›" would be the mono face's chevron,
   which is a different weight from the label beside it.

   Phone only. On a desktop .go is already showing its own arrow in the
   next column, and this would be a second one. */
@media(max-width:900px){
  #numbers .cat-list .crow.dst .cgo{
    display:inline-flex;align-items:center;gap:7px}
  #numbers .cat-list .crow.dst .cgo::after{
    content:"";width:6px;height:6px;flex:none;
    border-right:1.8px solid currentColor;
    border-top:1.8px solid currentColor;
    transform:rotate(45deg) translate(-1px,1px)}
}


/* ══ phone: the offer is written on the tab, not pointed at ══
   Replaces the pulsing dot. A dot is a notification — it says "look
   here" and makes you open the tab to find out why. The tab can just
   say why: "限時" as a honey chip, the same chip the member card wears
   over its price, then the label.

   It is the card's .price-tag, one step smaller: same fill, same
   radius, same display face at 700, the CJK letter-spacing bump
   included. Recognising the same chip in two places is most of what
   makes the tab feel like it belongs to the offer rather than
   advertising it.

   The chip and the label are separate data-* nodes rather than one
   string with markup in it, because the language script replaces the
   innerHTML of every node it translates — a chip written inside the
   parent's string would survive exactly until the first language
   change.

   Nothing needed doing about the thumb. Its white label copy is read
   with innerText, which returns "限時免費會員" with no idea a chip was
   involved; and when the tab is selected the honey thumb covers the
   honey chip anyway, which is the right outcome — once you are on the
   tab, the flag has done its job. */
@media(max-width:900px){
  .plan-switch .plan-tab .tab-promo{
    display:inline-flex;align-items:center;gap:6px;
    flex-wrap:wrap;justify-content:center}

  .plan-switch .plan-tab .tab-tag{
    display:inline-block;flex:none;
    padding:3px 7px;border-radius:var(--r-pill);
    background:#F0A500;color:#14213D;
    font-family:var(--display);font-style:normal;
    font-size:10.5px;font-weight:700;line-height:1;
    letter-spacing:.03em;white-space:nowrap}
  :is(html[lang^="zh"],html[lang^="ja"]) .plan-switch .plan-tab .tab-tag{
    letter-spacing:.08em}

  /* selected, the thumb paints over it — so the chip does not need to
     fight the honey it would be sitting on */
  .plan-switch .plan-tab[aria-selected="true"] .tab-tag{
    background:rgba(20,33,61,.14);color:var(--hive)}
}

/* ══ the sold-out rows became links ══
   They were <div> — no href, nothing to click — while the rows above
   them went to the store. Now all twenty go to the same place.

   Changing the tag is not enough on its own. .crow-out still carries
   three declarations written for a row that led nowhere: cursor
   default, the hover lift on the country name suppressed, and
   ::before — the surface the hover highlight is painted on — set to
   display:none. Left in, the row would be clickable and look
   inert, which is worse than either state on its own.

   The arrow stays at the .45 a normal row uses. It was dropped to .2
   to say "not this one", and that is no longer true. */
#numbers .cat-list .crow-out{cursor:pointer}
#numbers .cat-list .crow-out::before{display:block}
#numbers .cat-list .crow-out:hover .cname{
  transform:translateX(3px);color:var(--hive)}
#numbers .cat-list .crow-out:hover .go{
  transform:translateX(3px);color:var(--hive);opacity:.7}

/* ══ "coming soon" reads at full size ══
   .soon was written for the old wording, where it was a parenthetical
   inside a sentence — "send and receive SMS and calls (coming soon)."
   At .82em it stepped back out of the line it interrupted, which is
   what a parenthetical should do.

   It is a sentence of its own now, so the shrink has nothing left to
   do and instead reads as a size mistake next to the line above it.
   font-size back to inherit; the lighter weight and the 72% opacity
   stay, and those are enough to mark it as not-yet-available.

   white-space:nowrap also goes. It was keeping "(coming soon)" from
   splitting across a line break mid-parenthesis; as a full sentence
   it is long enough that refusing to wrap would push the paragraph
   sideways on a narrow phone.

   The weight and the opacity go the same way, and for the same reason.
   Two sentences sitting side by side in one paragraph read as one
   voice; setting the second a shade lighter and 28% faded made it look
   like a rendering fault rather than a deliberate aside. The sentence
   already says "coming soon" in words, so the styling has nothing left
   to add. Everything now inherits, and the span is kept only as a hook
   for the translated strings. */
.soon{font-size:inherit;font-weight:inherit;opacity:1;white-space:normal;color:inherit}

/* ══ CJK hero headline: measure in em, not ch ══
   .hp h1 is capped at 14ch. ch is the advance of "0", which in a CJK
   face is a half-width digit — so 14ch is about seven full-width
   characters, not fourteen, and the one 13-character line in the set
   ("也能擁有並使用當地的號碼。") fell two characters short and orphaned
   its last two onto a line of their own.

   1em is exactly one full-width character, so em says what was meant.
   14em holds the longest line with room to spare and leaves the other
   panels, which top out at 11 characters, untouched. Only panel 1 uses
   an h1 — the rest are h2 — so nothing else is affected. */
:is(html[lang^="zh"],html[lang^="ja"]) .hp h1{max-width:14em}

/* ══ closing headline, phone only ══
   The three lines are short — five characters in Chinese, ten to
   thirteen in English — so on a phone they were sitting well inside
   the measure with room to spare. The global rule caps out at the
   clamp minimum down here (38px / 34px), which is a display size
   chosen for a headline twice this long. These raise the floor for
   the three lines only; the eyebrow above and the button below are
   untouched. */
@media(max-width:900px){
  /* Written through .ring to match the rule earlier in the sheet that
     is itself written that way to outrank the language-specific ones.
     Without the .ring these lose on specificity and nothing changes. */
  .ring .ring-copy h2{font-size:clamp(34px,9vw,44px)}
  :is(html[lang^="zh"],html[lang^="ja"]) .ring .ring-copy h2{font-size:clamp(36px,9.6vw,46px)}
  html[lang="fil-PH"] .ring .ring-copy h2{font-size:clamp(30px,8vw,38px)}
}

/* ══ closing headline, desktop ══
   The global cap (86px / 78px) was set when this headline was one long
   line. Three short lines at that size overpower the ring they sit in
   and crowd the button underneath. Roughly a fifth smaller keeps the
   display weight without the block dominating the section. The phone
   sizes above are unaffected — this only applies from 901px. */
@media(min-width:901px){
  .ring-copy h2{font-size:clamp(38px,5.2vw,70px)}
  :is(html[lang^="zh"],html[lang^="ja"]) .ring-copy h2{font-size:clamp(34px,4.4vw,64px)}
  html[lang="fil-PH"] .ring-copy h2{font-size:clamp(30px,3.6vw,54px)}
}
