docs(host-directory-picker-native): describe the in-process IFileOpenDialog primary in the module header
The @module header still described the Windows adapter as the pre-PR 'STA PowerShell FolderBrowserDialog' while the README and Agent Notes document the koffi IFileOpenDialog primary with the PowerShell chain as fallback; mirror the README's platform summary.
This commit is contained in:
@@ -1,10 +1,12 @@
|
||||
/**
|
||||
* Native backend of the directory-picker seam: registers `ctx.directoryPicker`
|
||||
* with the `native` capability, opening one native OS chooser on the host
|
||||
* display per pick (macOS `osascript`, Windows STA PowerShell
|
||||
* `FolderBrowserDialog`, Linux Zenity with a KDialog fallback). Only viable
|
||||
* when the operator sits at the host's screen; remote deployments compose the
|
||||
* browse backend instead.
|
||||
* display per pick (macOS `osascript`, Linux Zenity with a KDialog fallback;
|
||||
* Windows opens the modern `IFileOpenDialog` in-process — a koffi-driven COM
|
||||
* conversation on a worker thread — and falls back to a PowerShell-hosted
|
||||
* dialog (`pwsh`, then Windows PowerShell 5.1) when that native surface is
|
||||
* unavailable). Only viable when the operator sits at the host's screen;
|
||||
* remote deployments compose the browse backend instead.
|
||||
* @module @deepseek-ai/dsh-host-directory-picker-native
|
||||
*/
|
||||
|
||||
|
||||
Reference in New Issue
Block a user