v1.8.3

Fixed

• OpenCode 2: updating the plugin without restarting OpenCode works. When OpenCode 2 reloaded openai-auth from an older version inside a running service, several parts could call into the older version's leftover state and fail: the /openai command, OpenCode 2 session records, session pins and the shared vault connection. Each now leaves the older state alone and starts its own.
• No file move while an older version may still be writing. A reload doesn't stop the older version's timers, so a version before 1.8 can keep writing to OpenCode's config folder until OpenCode restarts. If an older openai-auth ran in the process, the plugin keeps its files in the config folder until the next restart and blocks other OpenCode processes from moving them meanwhile. It says so once in the log, and never refuses to start. The files move on the next start after every OpenCode has restarted.