Thank you for being patient! We're working hard on resolving the issue
tento-flights extracts flight metadata from calendar events and enriches it
with airport and timezone data.
FlightTitleParser parses Google Calendar flight summaries.FlightInfo represents parsed event-level flight data.FlightInfoResolved adds timezone, gate, terminal, and FlightAware fields.FlightInfoStore combines parsing with an AirportDatabase.airports::{AirportDatabase, AirportsDat} loads airport reference data.flight_aware contains FlightAware-specific client and response logic.The crate may consume tento-google event types because flight detection starts
from calendar data, but higher-level calendar code should not parse flight title
formats directly. Airport and timezone resolution belong here.
External provider lookups should stay optional at the edge of the crate. The core parser and airport database need to work from local reference data so sync paths can degrade gracefully when enrichment is unavailable.