dsh-tool-vision 0.9.2 → 0.9.4

package/LICENSE

@@ -1,23 +1,23 @@
-MIT License
-
-Copyright (c) 2026 Scorp1o117
-Bridge image preview contributed by xing666173 (dsh-bridge-preview),
-Copyright (c) 2026 xing666173
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2026 Scorp1o117
+Bridge image preview contributed by xing666173 (dsh-bridge-preview),
+Copyright (c) 2026 xing666173
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -42,13 +42,16 @@ bridge keeps its conversion inside that durable path:
   key lives in `settings.yaml`, not the profile patch. Mount by package name
   (`name: 'dsh-tool-vision'`) so the web client bundle is discovered.
 
-## Compatibility (v0.9.1)
-
-Verified in a DSH `0.1.5-rc.3` (`next`) disposable Web profile; DSH
-`0.1.5-rc.2` remains `latest`. The rc.3 host currently references an
-unpublished `dsh-client-ui-sidebar-documentpreview@0.1.5-rc.3`, so the smoke
-profile temporarily used that unrelated UI package at rc.2. A clean rc.3
-installation is blocked upstream. Alpha releases remain `unknown`.
+## Compatibility (v0.9.4)
+
+DSH `0.1.5-rc.3` is the current npm `latest` and `next`. Alpha releases remain
+`unknown` until tested.
+
+## v0.9.4: Windows bridge export filenames
+
+- Export filenames now derive from a stable hash of the complete attachment ID. IDs such as `sha256:...` no longer create NTFS alternate data streams and zero-byte visible files.
+- The export directory is created before writing; the in-process cache now respects changes to `bridgeExportDir`.
+- Passed install, Web boot, homepage and client-bundle HTTP checks, and uninstall in a disposable DSH `0.1.5-rc.3` Profile.
 
 ## Install
 
@@ -85,7 +88,7 @@ Or load it from a local path without npm:
 | `maxImageBytes` | `10MB` | Largest accepted local image. |
 | `description` | default | Tool description shown to the model. |
 | `bridgeTextOnly` | `true` | Bridge pasted images to text hints on models that cannot see images. |
-| `bridgeExportDir` | temp | Export dir for bridged images (`os.tmpdir()/dsh-vision-bridge`). |
+| `bridgeExportDir` | temp | Export dir for bridged images (`os.tmpdir()/dsh-vision-bridge`). Filenames use a portable hash of the attachment ID. |
 | `multimodalModels` | `[]` | Model list (comma-separated). Each entry is matched case-insensitively against the full id, its bare id after the last `/`, and `provider/id`, with `*` / `?` globs (`*vl*`, `deepseek/*`). What the list *means* is set by the mode below. |
 | `multimodalListMode` | `whitelist` | **List mode (v0.9.0).** `whitelist`: listed models receive image blocks directly (the historical behaviour). `blacklist`: listed models are forced through the bridge — the correction layer for a model that claims image support it does not have. `off`: the list is ignored. An unknown value falls back to `whitelist`. |
 | `autoDetectMultimodal` | `true` | **Auto-detect (v0.9.0).** Decide from the current route's own declared `inputModalities`, then combine with the list (whitelist unions, blacklist subtracts). On by default: a text-only route is bridged, a multimodal one is treated like a whitelist member and gets images directly. The declaration is always read *before* this plugin's admission wrap, so `bridgeAutoImage` can never feed its own claim back in as evidence. Set false for the hand-maintained "list only" behaviour. |
@@ -382,6 +385,31 @@ the panel's picker carries a badge:
 > A route on an unknown protocol (e.g. `openai-responses`) returns `unknown`
 > with a reason, rather than guessing confidently with `chat/completions`.
 
+## v0.9.3: adapter snapshot model admission (pi-ai guard)
+
+**The bug.** `v0.9.2`'s `installDispatchImageAdmission` satisfied DSH core's
+`LlmService.generate` by declaring `image` on `adapterCall.model.inputModalities`.
+However, `dsh-llm-pi-ai`'s adapter executes a second internal guard inside its
+streaming path (`streamWithSnapshot`):
+
+```js
+const model = this.modelOf(snapshot, options.provider, options.model);
+if (containsImage && !model.input.includes("image"))
+  throw new LlmError(`pi-ai model "${model.id}" does not support image input`, "UNSUPPORTED_CONTENT");
+```
+
+`this.modelOf` resolves from the adapter's own `snapshot.models` catalog, which
+defaults to `input: ["text"]` unless the user explicitly declared
+`input: [text, image]` in `settings.yaml`. When admitted by `v0.9.2`, the raw image
+reached `streamWithSnapshot` and triggered `UNSUPPORTED_CONTENT`. Since the image
+was already in the session's durable transcript, every subsequent turn failed.
+
+**The fix.** On direct routes, `installDispatchImageAdmission` now additionally:
+1. Wraps `adapter.modelOf` (when present) to include `"image"` in `resolved.input`;
+2. Enriches the live snapshot model (`snapshot.models.getModel(route, model).input`)
+   with `"image"`;
+3. Fully restores `adapter.modelOf` and reverts modified input arrays upon dispose.
+
 ## v0.9.2: admission is not dispatch
 
 **The bug.** Every capability signal this plugin collects — `probeResults`,