Changelog

Naver Flight search operations now use the APIFuse-standard snake_case public contract for request and response fields.

This is a hard-breaking contract standardization. Naver Flight keeps the same operation ids, upstream behavior, anonymous NNB acquisition, and search semantics, but the public API now follows APIFuse snake_case naming.

Replace departure/arrival with departure_airport/arrival_airport, departureDate/returnDate with departure_date/return_date, and maxResults with limit. Update response readers from camelCase fields such as tripType, returnedCount, totalKnownCombinations, lowestGeneralFare, lowestCardFare, actionHint, airlineCode, depAirport, durationMin, generalFare, bestCardFare, curationTags, and carbonEmission to the new snake_case names.