Vect v0.3.5

Vect leaves the window. The same agent, the same memory, the same record, in
whatever terminal you already had open.

Added

• vect chat opens an agent session where you are, with the streamed answer, the tool calls, the permission prompts and the project's memory that the window has. It runs the code the app runs rather than a second implementation of it, so a fix to one is a fix to both. vect chat -p "..." prints one answer for a pipe, --json gives a script the whole turn, and cat error.log | vect chat -p "what happened here" sends the log with the question
• vect room "<task>" puts several agents in one directory, reading each other. They can take rounds, and the room says when two of them touched one file before the next round starts; or --free, where nobody waits and a seat that finishes goes again, and a clash is two turns that overlapped. Either way it ends by printing what changed and who changed it. Asked to fix two bugs in one file, one agent fixed both and the other read the file, found the work already done, and stopped rather than redoing it
• vect doctor answers the question every failure here looks like: whether an agent can start on this machine at all, which ones are installed, and what they would be handed
• The model, where the agent lets a client choose one. /model in a session lists what that agent offers with a mark on the current one; --model sets it from the command line, and a room can name one per seat since the agents do not share a list
• The app carries the command and can put it on your PATH. One button in Settings links the copy inside Vect.app into a directory your shell already searches
• What a terminal session did shows up in the audit view, because it is the same product doing the same work as the window

Fixed

• Two things written to the record at the same moment could merge into one unreadable line. The event and the newline after it were two separate writes, so another writer could land between them
• A tool row now says which file, even for an agent whose edit tool is handed no arguments and names the file alongside them instead, or only in the question it asks before making the change