Automation runs are spawned as siblings of the thread that created them #3060

What happens now

An automation created from inside a thread ("watch this board every morning", "run this check at 18:00") spawns each run as a top-level thread in the sidebar. The thread that set the automations up sits above a pile of siblings that cannot be collapsed and do not read as its work: after a day of running, five sibling rows say "Morning watch" and nothing connects them to the thread that asked for them.

Threads spawned by bb thread spawn from inside a thread do land under their parent, so the sidebar already knows how to show this — automations are the surface that misses it.

What I would expect

Runs of an automation that was set up from a thread appear under that thread, collapsible with it, the same as any other thread spawned from it.

Prototype

The row already records created_by_thread_id, so the fix is passing it through:

// plugins/automations/src/run.ts, executeAgentRun
await bb.sdk.threads.spawn({
  projectId: args.automation.projectId,
  // ...
  ...(args.automation.createdByThreadId === null
    ? {}
    : { parentThreadId: args.automation.createdByThreadId }),
});

An automation created outside any thread (from the project view) stays parentless, which is the current behaviour and the right one there.

Covered by three tests in the fork: the parent is passed, an automation with no creating thread stays parentless, and later runs keep the same parent. Happy to open a PR.