Road to v1.0.0

[punitarani]

fli v1.0.0 ships when we reach full parity with Google Flights — every filter the UI exposes, every field the response carries, every public RPC the web client calls.

Here's where we stand on main:

	Today	v1.0.0
Request filters	13 / 18	18 / 18
Response fields	6 / 25	25 / 25
RPC endpoints	2 / 3	3 / 3
Wire format	single-chunk	multi-chunk
Locale	—	curr · hl · gl

What works

One-way, round-trip, and multi-city search with full passenger, cabin, stop, time-window, airline, layover, and bag filters. Seven sort modes. Cheapest-dates discovery. The core itinerary — price, duration, stops, per-leg airline, flight number, airports, and times — is parsed end-to-end.

What's missing

Filters. Alliance, airline exclude, minimum layover, hide self-transfer, and locale (curr / hl / gl).

Response. Layover airports and durations. CO₂ and delta-vs-typical. Aircraft type. In-flight amenities. Operating vs. marketing carrier. Fare brand, seat pitch. Booking token, OTA list, baggage-policy URLs. Price insights and the full date-grid matrix.

Endpoints. GetBookingResults — gated on booking-token construction.

Wire format. The parser assumes one chunk. Real Google responses stream in framed chunks with UTF-8 byte-counted length headers and dual-newline bracketing. Multi-chunk unlocks everything GetBookingResults returns.

Out of scope

Refundable and aircraft-type filters — Google Flights doesn't expose them either, so there's nothing to map to.

The plan

1. Multi-chunk wire parser — unblocks the rest of the response surface
2. Locale URL params — small change, broad reach
3. Response enrichment — layovers, CO₂, aircraft, amenities, codeshare
4. GetBookingResults — booking token, OTAs, baggage URLs
5. Remaining filters — alliance, exclude, min layover
6. Price insights & full date grid