How does it handle concurrent agent/subagent spawning?
Do they fall under the same sessionId (where they're potentially fighting over the warm route breaking it with every task-type change) or get their own individual sessionIds (where you must rewrite the shared prefix for each agent)?
I would vote for the alternative: "Sloppy McSlopGate"