Repository navigation
docs: crew scheduler roadmap and v0.5.1 alignment - #45
Merged
Merged
Conversation
Reorganize the roadmap around three roles: crew scheduler, dispatcher and a local flight engineer using Infinite Flight Connect API v2. Summarize what shipped through v0.5.1, re-sequence the unshipped v0.5.0 scope, and set the release order v0.5.2 through v0.11.0 with the Connect manifest spike first and arrival ops ahead of assisted autothrust. Point to the IFA projects in Linear. Amend goal.md (2026-11-13) to bring telemetry-driven assistance into planned scope, with no LLM in the real-time control loop. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Document trip_progress and cancel_trip as shipped in the README and agent guide, replace the v0.4.6 quality and live-acceptance figures with v0.5.1's, and note the release-image browser check. Update stale status lines in the backlog, goal, technical design and aircraft coverage, fix deployment anchors that pointed at superseded "current release" headings, point Linear references at the IFA projects, and add an Unreleased changelog entry for the roadmap and alignment. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documentation only; no code, dependency or deployment change.
Roadmap (
docs/roadmap.md,docs/goal.md)goal.mdrecords the dated November 13 amendment that brings telemetry-driven assistance into planned scope.IFA ·projects with version milestones and target dates (roadmap document).Alignment with production v0.5.1
trip_progressandcancel_triplisted and described; trip-control evaluation suite and release-image browser check under Quality; v0.5.1 live acceptance replaces v0.4.6 figures; cancellation limits added; "What's next" follows the new roadmap.#current-release-v042/v046anchors fixed.CHANGELOG.md: Unreleased → Documentation entry. The existing changelog capability is unchanged: the Release workflow requires a section for the version and publishes it as the GitHub Release notes.Checks
tests/test_version.py(changelog/version agreement) passes;scripts/release_notes.pystill extracts sections.blockedon main as well, not because of this PR. Dependabot PRs build(deps): bump the uv-minor-and-patch group with 2 updates #42 and build(deps-dev): bump pytest from 8.4.2 to 9.2.0 #35 changeduv.lockafter v0.5.1's live acceptance on238f05c, anduv.lockis part of the acceptance integration digest. It clears when the next release (v0.5.2) records fresh live acceptance.🤖 Generated with Claude Code