v0.1.1

Fixes the one known flaw in the folder drag/paste path.

What was wrong

A mixed drop (one folder + some images) took the folder as an @mention and handed the remaining files straight to createDrafts — skipping the client-side image pre-check the shipped intakeFiles runs. Nothing actually slipped through: the Host's validateImageBatch still refused an over-cap batch. But you got a late wire error instead of the composer's own "at most 20 images" message.

What changed

The pre-check is now mirrored for dropped batches, reading thresholds from the imageLimits projection — the same source the composer reads — rather than copying the defaults, and formatting sizes through the exported fileSizeText.

Two deliberate scope limits, both documented in the README:

• It counts only the images in that drop. Already-attached images are not readable through any public face, so the notice can be looser than the composer's. The Host remains the authority on the per-message total.
• Absent limits mean "cannot judge", not "unlimited": the drop proceeds and the Host decides, instead of the plugin silently blocking a valid batch.

useProjection is called through a fallback, so a renamed seam degrades to "no pre-check" rather than throwing and taking the whole entry down.

Guarded by a mutation-checked regression test: removing the check fails the suite.

Install

dsh plugin --profile web add github:sixzjd/dsh-folder-attach#v0.1.1

npm 0.1.1 is pending — the publish token lacks write access. dsh plugin --profile web add dsh-folder-attach still resolves to 0.1.0.