bmersereau puts a time limit on hung chat streams

When you chat with Mike, answers stream back to your screen live. But the AI provider behind it can occasionally accept a request and then simply never finish replying. When that happens, the connection stays open with nobody on the other end - and under heavy use, those dead connections pile up until they choke off capacity for everyone else.

bmersereau's change puts a hard three-minute ceiling on each streaming reply. If the provider hasn't finished by then, Mike cleanly tells the user the request timed out and closes the connection instead of leaving it hanging. The fix covers both the general chat and chat inside a specific project, so the behaviour is the same wherever you're working, and it ships with tests to keep it in place. It's plumbing, not a feature - but it's the kind of plumbing that keeps a busy deployment from quietly falling over.