Fix OpenCode process cleanup on Obsidian shutdown

[yangyangyanghub]

Summary

This fixes an issue where opencode serve can remain running after Obsidian exits, especially on Windows.

The previous Windows cleanup only killed the parent process and direct child processes. Because the plugin starts OpenCode through a shell, the actual opencode.exe server process can remain orphaned and keep listening on the configured port.

Changes

• Use taskkill /F /T /PID on Windows to terminate the full process tree.
• Add synchronous shutdown cleanup via stopSync.
• Use synchronous cleanup during Obsidian quit.
• Avoid showing stop notices during unload/restart cleanup.
• Keep the existing safety boundary: the plugin only stops processes it started and does not kill by port or process name.

Verification

• Built successfully with:
  • bun run tsc -noEmit -skipLibCheck --ignoreDeprecations 5.0
  • bun run esbuild.config.mjs production
• Manually verified in Obsidian on Windows:
  • Start OpenCode server from the plugin.
  • Close Obsidian.
  • Confirm the configured port is released and no plugin-started opencode serve process remains.

🤖 Generated with Claude Code