opencli-trip

name	opencli-trip
description	Execute and troubleshoot opencli trip commands for Trip.com (Ctrip international) activities — search, detail, pricing, probe. Use when the user mentions Trip.com, 攜程, 携程, trip.com, Ctrip, or provides a Trip detail URL / numeric activity ID (e.g. 92795279); also use when opencli-router dispatches a Trip task or a tours / compare workflow targets the trip platform.

opencli-trip

• Platform: trip
• Owner: klook-cli core team ([e-mail]) — scrape logic maintained here; listing-page discovery owned by BD team (see docs/colleague-handoff.md)
• Strategy: BROWSER_BRIDGE (COOKIE flavor — Trip is SSR, no public API). Verify Browser Bridge with opencli doctor.
• Domain: trip.com (Ctrip international; the zh-CN sibling is ctrip.com but this adapter targets trip.com)
• Source: src/clis/trip/ (search.ts, detail.ts, pricing.ts — plus probe.ts debug helper)

Identifiers

• Trip activity IDs are numeric, e.g. 92795279.
• Extracted from detail URLs matching /things-to-do/detail/{id}. parseActivityId in src/clis/trip/detail.ts accepts either a full URL or the bare numeric ID.
• Canonical URL shape: https://www.trip.com/.../things-to-do/detail/{id} — the city-slug prefix is cosmetic.

Commands

search

opencli trip search-activities "<query>" --limit <N> -f json

Browser Bridge navigation → DOM extraction. Expect ~10s including cookie warm-up. Returns { id, title, price, rating, review_count, url }[]; price string includes currency code (e.g. US$89, TWD 2,800).

detail

opencli trip get-activity <id-or-url> -f json
opencli trip get-activity <id> --compare-dates -f json   # also emits date matrix

• Title selector is [class*="title_foot_warp_left"], falling back to h1 / document.title. Promotional suffixes like Promotion / Duration: are stripped from the title.
• --compare-dates walks the 7-day calendar strip and returns inline "from" prices per date — cheaper than a full pricing call, but only gives the minimum across SKUs, not per-SKU rows.

pricing

opencli trip get-pricing-matrix <id> --days 7 -f json

Extracts the SKU × date matrix:

• SKU tabs are .m_ceil elements inside .sku_tab_ceil with numeric id (date cells also use .m_ceil but their id is YYYY-MM-DD — the scraper discriminates on the id format).
• For each SKU, the scraper clicks the tab, waits for the 7-day ceil row to re-render, and reads the per-date "from" price.
• This is the canonical feed for tours ingest; prefer it over detail --compare-dates when you need per-SKU granularity.

probe (debug)

opencli trip probe <id>

Dumps SKU/date DOM structure. Use only when the pricing scraper breaks and you suspect Trip changed its class names — do not rely on probe output in production pipelines.

trending

Not supported on Trip. Do not offer this command.

Quirks

• Title pollution: the title div sometimes concatenates promotion copy after the real title; the scraper slices on Promotion / Duration: but other suffixes may slip through — verify if titles look noisy.
• Currency by geo: the returned price string uses whatever currency Trip serves based on Browser Bridge locale. Do not assume USD. Downstream consumers must normalize.
• SKU tabs vs date cells share class: both are .m_ceil. Never iterate all .m_ceil without the numeric-id filter, or you'll treat dates as SKUs.
• Cookie drift: Browser Bridge cookie staleness is the #1 cause of empty search results. Re-run opencli doctor if search returns 0 items on a known-valid keyword.
• Cancellation policy lives in a collapsed FAQ accordion: the heading walker only catches the question title (e.g. "Can I change or cancel my booking?") but not the answer. The cancellation_policy field is filled by a body-text fallback (extractCancellationFromBody) that scans for "Free cancellation", "Cancel up to N hours/days", or tiered fee schedules. Trip's tiered policy ("Free cancellation 3d before / 30% / 80% / 100%") often extracts cleanly via this path.

Fallback playbook

When opencli trip get-pricing-matrix <id> fails or returns empty:

1. Retry once. Cookie/timing flukes are the common cause.
2. Fall back to detail via node dist/cli.js tours ingest-from-detail trip <id> — fills SKU rows using the cheaper detail endpoint.
3. Snapshot replay from data/snapshots/trip-<id>-*.json with tours ingest-from-snapshot trip <file>.
4. Manual capture via the browse skill → navigate to the canonical URL → save JSON matching PricingRunRaw → tours ingest-snapshot.

If multiple Trip targets fail in the same run, the issue is almost always Browser Bridge / cookie — refresh it before retrying individual targets.

Known failure modes

• Empty SKU list: Trip occasionally lazy-renders the SKU tab row if the page loaded while scrolled past it. The scraper scrolls to top before extracting — if you still get empty, check whether Trip redesigned .sku_tab_ceil.
• Date cell "TBD": Some SKUs don't have availability for all 7 days; the scraper returns empty-string price rather than dropping the row. Downstream consumers should treat empty price as "unknown", not "zero".
• Region redirect: Requests from a non-en locale sometimes redirect to zh-CN Ctrip (DOM differs completely). Pin Browser Bridge to an en-US cookie.
• No .sku_tab_ceil row — two distinct UI variants behind one symptom (partial fix shipped 2026-04-27): Initial diagnosis was "single-package products don't render the tab row." That's true for genuinely single-package listings (fallback shipped: when LIST_SKUS_JS returns 0 tabs, synthesize one synthetic SKU keyed off activityId and read whatever date cells are visible). But probing Mt Fuji 105146444 revealed a second variant: a multi-package product that uses a vertical package list instead of horizontal tabs. Probe excerpt:

  packages-vertical_package_wrapper_outer__OQPH4 contains N
  packages-vertical_package_item_new__c5XR_ rows, each with
  inline "FromUS$109.77" prices. The default date strip shows only
  3 hint dates (e.g. May 11/12/13) — clicking a package opens its
  own calendar.
  

  The current single-package fallback does not correctly cover this layout — it produces 0 rows because (a) it loses the multi-package fan-out and (b) the visible 3-day hint strip rarely overlaps the user's target days. Proper fix (separate work): detect packages-vertical_package_wrapper presence, iterate packages-vertical_package_item_new__ items to extract titles + "From $X" prices, then for each package open its calendar widget and read true per-date pricing. Half-day of adapter work; mirrors the pattern used by Klook's per-package detail flow rather than the tab-click pattern Trip's other layout uses.

Touchpoints

• src/clis/trip/search.ts — search DOM extractor, currency regex
• src/clis/trip/detail.ts — parseActivityId, title selectors, --compare-dates handler
• src/clis/trip/pricing.ts — SKU tab enumeration, .m_ceil discriminator, date click loop
• src/clis/trip/probe.ts — debug-only DOM dump

After any change: npm run build. Symlink at ~/.opencli/plugins/trip (if registered) picks up dist/ automatically; otherwise run via node dist/cli.js.

I/O Schema

Canonical reference: docs/io-schemas.md — input args, output JSON shapes, DB column mappings.

Trip-specific nuances:

• get-activity --compare-dates emits an additional field with the 7-day inline "from" price strip — useful when you want date coverage without the full SKU walk
• get-pricing-matrix output's package_id is the numeric SKU tab id (distinguishes from date cells that share the .m_ceil class)
• Currency is whatever Trip serves the Browser Bridge cookie → normalize before inserting into skus.price_usd
• cancellation_policy (cross-platform field, Trip-specific extraction path): filled via body-text fallback because Trip's FAQ accordion is collapsed at scrape time. Output is typically the richest of the four platforms (full tiered fee schedule with timing windows). If you see only "Free cancellation 3 days before" without the tiered fees, the page may have lazy-rendered after the body read — retry once.

Writes when called via tours pipeline: same tables as Klook. package_id maps to packages.platform_package_id; keep it stable across runs so upserts don't create duplicates.

---

Listing (new pipeline)

Trip.com listing URL pattern is not yet documented in this repo. Recon needed: identify the destination + category page form (analogous to Klook's /destination/c{N}-{slug}/...), then add to data/listings/trip-destinations.csv.

Locality: search.ts:37 currently returns cityName: ''. Until trip listing is wired, every Listing JSON for trip should set locality: undefined — applyListingFilter will pass cards through as kept_unchecked.

TODO: pattern recon → data/listings/trip-destinations.csv → opencli trip search-by-url <url>. See docs/listings/design.md §6.