docs: find prints paths that cat cannot open (e.g. the @vgpu/wgsl Vite loader doc)

Environment

Windows 11, Node v22.18.0, vgpu 0.3.1 via npx -y vgpu.

Steps

docs find returns paths that docs cat cannot open. Repro with the Vite loader doc:

$ npx -y vgpu docs find "vite"
/@vgpu/wgsl/loader-vite/index.docs.md    docs/topics/nextjs.docs.md
ViteLoadResult    @vgpu/wgsl/loader-vite    ...
wgslVitePlugin    @vgpu/wgsl/loader-vite    ...

$ npx -y vgpu docs cat "@vgpu/wgsl/loader-vite/index.docs.md"
Symbol not found: @vgpu/wgsl/loader-vite/index.docs.md

$ npx -y vgpu docs cat "/@vgpu/wgsl/loader-vite/index.docs.md"
Symbol not found: /@vgpu/wgsl/loader-vite/index.docs.md

$ npx -y vgpu docs cat "packages/wgsl/src/loader-vite/index.docs.md"
Symbol not found: packages/wgsl/src/loader-vite/index.docs.md

Expected

Every path or symbol that docs find prints should be resolvable by docs cat. Package-internal guides that ship with the npm package (here: the Vite loader doc for wgslVitePlugin / transformWgsl, which exists at packages/wgsl/src/loader-vite/index.docs.md in the repo) should be discoverable from the CLI.

Context

docs find is the discovery entry point for the agent workflow, so a find → cat dead end silently pushes consumers out of the CLI and into the GitHub repo. I only found the Vite loader content by cloning the repo and reading the file directly. A find <path> that echoed the resolved doc content (or a cat accepting the exact find output) would close the loop.