Repository navigation
docs: rename the product to Jumpseat - #47
Merged
Merged
Conversation
Use the new product name in the README, changelog, roadmap, backlog and AGENTS.md, and note that it was previously called Infinite Flight Agent. Point Linear references at the renamed "Jumpseat" projects and roadmap document. The repository address, the ifd-* commands, the package name, the agent prompt and deployed resource names are unchanged. Co-Authored-By: Claude Fable 5.2 <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. The product is now called Jumpseat (previously Infinite Flight Agent).
ifd-*commands and the package name keep their existing names for now.Jumpseat ·projects under the "Jumpseat" label, and the roadmap document link points to its new address.Deliberately unchanged
instructions.md(the agent prompt): it is part of the integration digest, so changing it would require repeating live acceptance. It belongs in a release.Checks
tests/test_version.pypasses.blockedon main as well, for the same reason as docs: crew scheduler roadmap and v0.5.1 alignment #45:uv.lockchanged after v0.5.1's live acceptance. It clears when the next release records fresh acceptance.🤖 Generated with Claude Code