Repository navigation
feat(web): clarify cross-environment Squadron selection for existing drafts #154
Description
The draft-local Squadron chip currently offers only Squadrons on the draft's current environment. The global new-thread picker offers Squadrons across environments. This is pre-existing PR125 behavior, confirmed in the upstream integration's live smoke test and independent Fable review; it is not a merge regression.
Decide whether an existing unsent draft should be retargetable to another environment through its Squadron chip. If so, use environment-qualified choices and per-source availability/write authority, preserve typed content/model choice through the existing retargetSquadronDraft helper, and keep ownership frozen at first send. Do not copy a bare Squadron ID to another server. Otherwise make the refusal hint explicitly direct the user to the global new-thread picker.
Current environment controls safely refuse moving a selected Squadron draft. Their “Choose another Squadron to use a different machine” hint can be read as pointing to the chip, where remote choices are unavailable. Relevant files: SquadronDraftChip.tsx, retargetSquadronDraft.ts, ChatView.tsx. The helper's cross-environment unit test establishes capability, not current UI reachability. Avoid broadening this feature inside the upstream merge.
Activity
Jacksondr5 commentedon Oct 8, 2026
Closing: Squadrons are retired and their behaviour is folded into projects (#412; merged in #454, #455, #456, #457, #482, #483, #484 and #489). A thread's home is now its project, so the Squadron this issue is about no longer exists. If part of this still applies to projects, reopen it or file it in those terms.