OpenTM v0.0.2

Fixed

• Editing a target's port or type after it had been connected once had no effect, the session server kept the old address and refused to move it, so the app kept dialling the original port (Connection refused). Reopening a target now reconnects it at its new address. #1
• After a failed target.open, the app connected anyway using whatever address the server still held under that handle, rather than the one just configured.

Changed

• A connect requested while target.open is still in flight now waits for it instead of being treated as a failure.
• The connecting log line names the address actually being dialled, instead of the previous target or nothing.