/* ═══════════════════════════════════════════════════════════════════════════════════════════
   PAGE-SCOPED FIXES FOR THE OPERATOR PROFILE (application/themes/nextgen/vendor/view.php).
   Same pattern, and the same reason, as common/css/ngf-destination-view.css: self-contained,
   loads only on this view, every rule under .ng-landing--vendor. Kept OUT of the theme bundle.
   ═══════════════════════════════════════════════════════════════════════════════════════════

   ARRIVAL COLUMN HUGS THE RIGHT EDGE ON THE OPERATOR ROUTES CARDS — bug #319.

   The reporter drew a box round the schedule cluster on the first Operator Routes card and wrote
   "not centered". What is off is the ARRIVAL column. .ngr-sched is a `1fr auto 1fr` grid
   (99-result.css:211), so the middle duration/stops cell already sits at the geometric centre of
   the space between the operator logo column and the amenity chips — but the arrival cell's
   contents are left-aligned inside their track, so they start immediately after the middle cell
   and leave ALL the slack as one wide dead gap before the chips. Measured on the rendered page at
   the reporter's 1710px viewport: the .ngr-sched area is ~526px wide, the arrival track ~194px,
   and "10:00 / Phuket / Rassada Pier" is ~90px of it — ~104px of empty card, on one side only.
   The cluster then reads as pushed left, which is the complaint.

   THIS IS THE THIRD SURFACE WITH THE SAME DEFECT AND THE FIX IS THE ONE ALREADY PROVEN TWICE.
   The result card is one component (section/inc_resultcard_render.php) rendered on several
   surfaces, and each has needed this rule separately:
     · responsive.css:21          — every surface, but only inside @media (max-width:991px).
     · 97-schedule.css:387        — above that breakpoint, but only under .ng-schedule (bug #20/#46).
   The operator profile is neither, so it falls through the gap: at <=900px the card stacks and the
   mobile rule already right-aligns it, and above 991px nothing does. That is why the card renders
   correctly on a phone and lopsided on the desktop the bug was reported from.

   WHY RIGHT-ALIGN AND NOT literally centre the three blocks as a group. Centring them would put
   equal slack on both sides of the cluster, which also removes the gap — but the two side blocks
   would then start at a different x on every card, because their width follows the length of the
   place and pier names ("Koh Phi Phi / Laemtong Bay" vs "Phuket / Rassada Pier"). The cards in the
   list would no longer line up with each other, which is the other half of what this bug asks for.
   Anchoring departure left and arrival right keeps every card's columns on the same two edges AND
   leaves the middle cell on the centre line, so the cluster is symmetric about the centre of the
   space rather than bunched into the left of it. It also makes this page agree with the schedule
   surface, where the identical rule is live today.

   ONE DECLARATION IS ENOUGH HERE, and the companion rules the other two copies carry are not.
   Those add `justify-content:flex-end; margin-left:auto` for span.rrt-address, because on their
   surfaces the 1-line clamp gives it `display:-webkit-box` with `max-width:190px` — a block that
   text-align cannot move. Both clamps are scoped (.ngf-result in 99-result.css:218, .ng-schedule in
   97-schedule.css:356) and neither matches this page, so here .rrt-address keeps the base
   `display:inline-flex` (99-result.css:214) — an inline-level box that text-align does move. The
   Drop-Off row that needs the .d-flex escape hatch elsewhere is rendered .d-none on this page.
   If a clamp is ever un-scoped onto this surface, this rule needs that companion line too.

   WHY THIS FILE EXISTS AT ALL, rather than the rule living where it belongs. The right home is
   99-result.css (the shared card) or responsive.css. Both are drift-gated sources — every theme
   partial, and every .css with a committed .min sibling, is checked by
   scripts/check-artifact-drift.sh, and the lab deploy gate refuses a commit whose sources moved
   without their artifacts rebuilt. 99-result.css is in themeBundleCore(), so editing it invalidates
   all 27 per-type bundles at once. Rebuilding needs cleancss, which the box this was fixed on does
   not have. A page-scoped sheet has no committed .min sibling, so it is not a drift source and
   nothing needs rebuilding. The cost is one small extra request on this view — the same trade
   ngf-destination-view.css already makes. If the shared card is ever touched by a box that CAN
   build, move this rule to 99-result.css unscoped and delete this file: it fixes /searchresult too,
   which still has the gap. */

.ng-landing--vendor .ngr-sched > :last-child { text-align: right; }