Bloks 2.5.8

Bloks starts even when its port is taken

Bloks used to give up if another program was using its usual ports, and it didn't say which port or why. Now:

• It finds a free port. A busy port is skipped straight away. If all the usual ones are taken, Bloks uses any free port instead of failing.
• It remembers the port that worked, so your paired phone keeps finding your Mac.
• You can choose a port. Add "port": 9123 to ~/.bloks/config.json, which works however you open the app. BLOKS_PORT works when starting from a terminal.
• It says what went wrong. If Bloks still can't start, it lists each port it tried and which program holds it. If the server itself crashed, it shows the error instead of blaming ports.
• Helper tools follow along. The command-line tools and the Claude Desktop connection find Bloks on whichever port it ends up on.
• Clear message for bloks-server. When its port is busy, it now says so in a sentence instead of printing a stack trace.

Settings also stops checking chat and local VM status while the window is hidden.

Thanks to @grantterra for #80.