v0.2.0

v0.2.0 — Open PowerShell from the folder context menu

New: right-click a single folder in the Obsidian file explorer → Open PowerShell here (terminal icon) → opens PowerShell 7+ in that folder's real Windows absolute path. The vault root folder is supported too.

• The ribbon still opens the vault root; both entries share one launch pipeline, one pwsh verification cache and one single-flight lock.
• The menu item never appears for plain files, multi-selection, non-Windows platforms, or non-local (remote) vaults. No files-menu batch entry, no commands, no hotkeys, no settings page.
• Behavior change (semicolon paths): paths containing ; are no longer launched at all — Windows Terminal splits on ; (verified). The plugin now shows PowerShell cannot be opened for paths containing a semicolon (;). and creates no process (not even the version probe). The wt.exe-missing fallback to a direct pwsh.exe spawn is unchanged.

Also in this release:

• 84 automated tests (up from 63) covering the context menu, the shared cache/single-flight, reload without duplicate handlers, and the zero-process semicolon guard.
• Docs updated: README (zh/en), MANUAL_TESTS.md, AGENTS.md.

Manually verified in real Obsidian:

• Ribbon → vault root (2026-08-08)
• Folder context menu → right-clicked folder's absolute path (2026-08-09, core flow)
• Pending manual acceptance: semicolon-folder notice, root-folder right-click, file right-click, reload dedup (see MANUAL_TESTS.md #28–#33).

Scope & constraints (unchanged):

• Windows + PowerShell 7+ only (5.1 not supported); local file system vaults only
• No commands, settings, keybindings, batch/file context menus, or embedded terminal
• No telemetry, no network, no vault modification; never invokes cmd.exe / powershell.exe / conhost.exe / shell:true; real sessions never use -NoProfile / -NonInteractive / -Command

Assets: main.js, manifest.json, versions.json (no styles.css — the plugin ships no CSS), plus the vault-powershell-0.2.0.zip install bundle.