[Help wanted] Verify Sabre & Travelport infant / child name cryptic syntax in PNR Builder

[telivity-otaip]

Who this is for

GDS power users / TMC agents who still speak Sabre and Travelport cryptic daily (Amadeus too). If you can spot a wrong infant name entry before it rejects at EOT — this is your issue.

Why this hardens the system

Agent 3.2 PNR Builder generates multi-GDS commands but flags infant syntax as unverified:

// TODO: [NEEDS DOMAIN INPUT] Verify exact Sabre infant name syntax
// TODO: [NEEDS DOMAIN INPUT] Verify exact Travelport infant syntax

File: packages/agents/booking/src/pnr-builder/command-builder.ts

Wrong name elements = failed bookings, broken APIS, and mid-office cleanup queues.

What we need

1. Authoritative examples for adult / child / infant name entries on:
   • Sabre
   • Travelport (Apollo / Galileo / Worldspan — call out host differences)
   • Amadeus (sanity check against what we already emit)
2. Edge cases: infant with / without accompanying adult association, DOB formats, titles.
3. A new KB file such as docs/knowledge-base/gds-pnr-name-commands.md (path flexible).
4. Golden-string tests in packages/agents/booking/src/pnr-builder/__tests__/.

Acceptance criteria

• KB with side-by-side command examples per GDS
• Explicit note of host/version if syntax varies
• Tests for infant + child paths on Sabre and Travelport
• Source stated (official doc link or "N years cryptic booking at …")
• No speculative "probably like Amadeus" mappings

Search keywords

help wanted · Sabre · Travelport · Amadeus · cryptic · PNR · infant · child · GDS · TMC

How to contribute

Paste verified examples in a comment (redact live PNRs). Maintainers will help turn them into KB + tests.