glob (V2) drops the truncation flag, model can't tell results were limited

Describe the bug

The V2 glob tool drops the truncation flag. ripgrep's glob service already discards { truncated } (it maps to result.items), and the tool returns a bare path list with no "results truncated" notice. So when a limit is passed, the model can't tell "exactly N files" from "N of many files", and will reason as if the result set is complete.

The V1 glob tool reported this (it computed truncated = files.length === limit and emitted a note).

Suggested fix

Surface a truncated marker in the glob output (or keep limit unbounded by default and document truncation when a limit is set).

Environment

• opencode version: latest dev