[Help wanted] TMC mid-office: TTL timezone edge cases + Travelport host queue commands

[telivity-otaip]

Who this is for

TMC mid-office automation engineers and queue supervisors (Amadeus Q, Sabre queues, Travelport hosts). If your overnight TTL sweeps still miss same-day-deadline tickets — we need your scars.

Why this hardens the system

Two related gaps:

1. Agent 8.3 Mid-Office Automation flags TTL urgency but timezone / "issued on deadline day" ADM patterns need practitioner input.
2. Queue Management notes Travelport queue commands vary by host (packages/agents/booking/src/queue-management/queue-engine.ts).

Also relevant: Agent 8.2 Corporate Account policy validation & Agent 8.5 Duty of Care — comment if mid-office should hand off differently.

Docs: docs/agents/stage-8-tmc.md

What we need

1. How you compute "TTL urgent" in production (agency TZ vs airport TZ vs UTC).
2. Travelport per-host queue place/list/remove examples you trust.
3. The top 10 mid-office issue codes you actually chase (map to our 10 types or propose new ones).
4. Golden tests for timezone boundary tickets.

Acceptance criteria

• KB: TTL timezone policy recommendation for OTAIP defaults
• Travelport host command table (Apollo / Galileo / Worldspan as applicable)
• Tests for deadline-day edge cases
• Clear DOMAIN_QUESTIONs where host docs conflict

Search keywords

help wanted · TMC · mid-office · TTL · ticketing time limit · Travelport · queue · corporate travel

How to contribute

Queue command snippets (no live PNRs) in comments are enough to start a KB PR.