crew 5.3.0

5.2.0 broke switching in a way I hit straight away: "go into crew" or "can you check out crew?" got sent to the session on screen as words for it, and "can you stop?" got refused as a listening command. Going to a session is never words for it now, and stop reads as a stop again. I went through the rest of that day's log and debug notes too. Questions like "status" or "how far are you?" about the session on screen go to that session instead of being answered by the router. Text over 20,000 characters stays in the box with a warning where it used to vanish. And a yes to "want me to ask it?" sends your actual question, not the word "yes".

The off-screen conversation stuff from 5.2.0 got a cleanup as well. Replies to the meanwhile line go to the sessions it named, an update is said once, and the switch offers are down to one: "Sent to X. Switch there?", only on your first reply to an update you heard to the end. The per-session topic is gone because it went stale and nobody used it; tiles show the last real request instead. Long streams open at their end and stay there now. On remotes, crew voice remote restarts a daemon on another release right away instead of waiting for busy sessions to finish.

Pull requests

• Voice OS: a session's stream opens at its end and stays there (#27)
• Voice OS: switching regressions from 5.2.0 — 'go into crew', 'can you stop?', answers, meanwhile (#28)
• Voice OS: older bugs from today's log and debug notes; remotes restart at once (#29)
• Voice OS: conversation routing works as designed — replies to updates, one switch offer, nothing said twice (#30)
• Voice OS: remove the session topic (#31)