Pulling main from Git actions pane can kill active sessions

[arul28]

Problem

Pulling from main via the Git actions pane in ADE can kill active ADE CLI sessions and/or ADE chats. This appears to be a distinct user-triggered Git/sync failure mode, not covered by ADE-91 or ADE-92.

Expected

Running a Git pull/sync from ADE should update the lane/worktree or fail in a controlled way without killing active CLI sessions, chats, or project/runtime state. Active sessions should remain visible and resumable after the operation.

Actual

Using the Git actions pane to pull from main can terminate or crash active sessions. The failure feels similar to the lane lifecycle crash cascade, but the trigger is a Git action rather than lane create/delete.

Investigation requirement

First identify the root cause of the Git pull/sync failure path. Then trace why that specific Git operation can propagate into killing active CLI sessions, ADE chats, or project/runtime state. Do not close this with only a UI guard or retry button unless the session-killing cascade is understood.

Areas to inspect

• Git actions pane pull/sync flow and any ade git/runtime action it invokes.
• Worktree refresh, lane metadata refresh, project registry refresh, and session list refresh triggered after pulling from main.
• PTY/session ownership when a worktree branch is rebased, fast-forwarded, or otherwise updated under active sessions.
• Whether pull/sync invalidates cwd/path assumptions for running PTYs or causes the runtime daemon/session manager to restart.
• Whether failures are isolated to the affected Git action or accidentally tear down shared runtime/socket state.

Relationship to existing tickets

ADE-91 is done and covers lane create/delete lifecycle crashes. ADE-92 is done and covers prompt clipboard recovery. This ticket should verify whether those fixes incidentally solve this Git pull path; if not, fix this path separately.

Acceptance criteria

• Pulling from main via the Git actions pane does not kill active CLI sessions or ADE chats.
• Active sessions remain discoverable and resumable after a successful pull, failed pull, fast-forward, or rebase-like sync path.
• The root cause of the session-killing cascade is documented.
• A regression test or targeted validation covers pulling/syncing while sessions are active.

[linear-code]

ADE-95