Agent team leadership state contradicts teammate state after session reset

TL;DR

• TeamCreate still holds that I am leading session-2026-02-25, but TaskCreate/TaskUpdate claim I am an in-process teammate.
• TeamDelete cannot finish because the session reports active members that refuse to shut down.
• In-process team state blocks background agent spawns; synchronous spawns still work but must run sequentially.

Problem

TeamCreate says I'm leading session-2026-02-25, yet TaskCreate refuses to create new agents in background mode because it identifies me as an in-process teammate. Foreground (synchronous) spawns succeed, but the system still prevents background agents from launching until the stale team state is cleared. TeamDelete also fails because the session reports active teammates that I cannot stop.

Workaround attempt

Running tasks without any team context or handpicking synchronous mode both leave the stale teammate state unchanged, so the only workable path is to run synchronized agents sequentially while waiting for the platform to reset the leader role.

Additional context

Several earlier background tasks (for example, task #4, #12, #22) eventually completed despite the errors, confirming the issue is specifically the background spawn check.

Impact

I cannot lead new background agents or clean up the stale teammates. Everything beyond sequential foreground work is blocked until the team/session state is reconciled or the zombie teammates are evicted.