v0.2.3 — Multi-image separation robustness
What's new
- Per-attachment boundary labels. Multi-image Vision requests now interleave an explicit boundary label (
Image i of N:) immediately before each native image block, improving separation robustness for visually adjacent attachments. This targets intermittent real-world failures where the Vision model merged two adjacent same-class attachments into one Evidence entry (images.length (expected N, got 1)→ retry exhausted). - Evidence policy version 3 → 4. The request the Vision model receives changes for the same attachment set, so the session-scoped Evidence cache key version is bumped.
Unchanged by design
- Strict cardinality validation (
images.length === N, indexes1..N), fail-closed behavior, and the bounded two-attempt output-contract retry (no Attempt 3) remain the final safety boundary. - Single-image behavior, temperature-0 multi-image retries, the Stage 3B cache architecture, and the leading U+200B tolerance are unchanged.
- Distribution remains GitHub Release only — no npm publication.
Installer
- Default version and trusted release map updated to v0.2.3 (v0.2.2 and v0.2.1 remain trusted; unknown versions still fail closed).
Verification
- Deterministic suite: 292/292 pass, 0 fail/skip/todo/cancelled (installer suite 70/70).
- Packaged verification: fresh standalone installer install, same-version no-op rerun, single-image and two-image real smokes all PASS.
Assets
| Asset | SHA-256 |
|---|---|
| dsh-vision-bridge-0.2.3.tgz | D6D5D2A3FFECA2FD9213DA9A34A527E19321E8DB44CD0FCFCFCC168B42FE16C1 |
| setup.mjs | 7DBFF7AEB70D3589B28C78E5DECC06E1FE462B31CCCB6D24824AE9A65EF6BF24 |
Both .sha256 sidecars are attached for machine verification.