Today some threads are born with no Squadron home: mobile launches, server bootstrap, and plan-to-implementation children of a parent with no home are named exemptions (SquadronLaunchPolicy.ts). Threads from before Squadrons existed have no home either.
The only ways to fix that are the agent calling join_squadron itself (Squadron AC14), and onboarding import, which only assigns v1_import threads (ImportedThreadsHttp.ts). A person can't give such a thread a home, and choosing a Squadron scope hides it (Fleet page AC1).
Full behavior: the person can set a thread's original home once, under AC14's rules, and the Fleet page footer counts the threads that still have none (Fleet page AC13).
Carried over from the dogfood v0 plan's "what the current build narrows" table, which #354 removes.
Today some threads are born with no Squadron home: mobile launches, server bootstrap, and plan-to-implementation children of a parent with no home are named exemptions (
SquadronLaunchPolicy.ts). Threads from before Squadrons existed have no home either.The only ways to fix that are the agent calling
join_squadronitself (Squadron AC14), and onboarding import, which only assignsv1_importthreads (ImportedThreadsHttp.ts). A person can't give such a thread a home, and choosing a Squadron scope hides it (Fleet page AC1).Full behavior: the person can set a thread's original home once, under AC14's rules, and the Fleet page footer counts the threads that still have none (Fleet page AC13).
Carried over from the dogfood v0 plan's "what the current build narrows" table, which #354 removes.