All releases
v0.4.4
Better connections and route checks
Connection planning uses sourced proposed arrivals before a prior plan is retained, reports unavailable timing explicitly, and preserves itinerary order when departures change.
View on GitHubFixed
- Connection planning uses sourced proposed arrivals before a prior plan is retained, reports unavailable timing explicitly, and preserves itinerary order when departures change. Settled inputs proceed to exact dispatch approval without repeated chat confirmation.
- Retained SimBrief routes must match the approved route or recorded automatic route readback. A mismatch stops finalization before saving a snapshot or briefing.
Added
- Briefings show the OFP route and available navlog evidence, with no route-validity claim based on waypoint count alone.
- A dated official aircraft catalog and v26 change/capability matrix: 51 current aircraft, 11 legacy records retained separately, profile candidates and explicit evidence gaps. Catalog assessment establishes no new verified aircraft support.
- Expanded matched workflow evaluations through the production MCP tools over local HTTP, covering planning, routing, provider failures, approved revisions and persisted recovery.