Return file paths from gguf and safetensors parsers

[julien-c]

Summary

• [gguf] ggufAllShards now returns urls (the resolved shard URLs) alongside shards and parameterCount
• [safetensors] parseSafetensorsMetadata now returns filepaths (the resolved file paths, including index + shard files for sharded models)
• Minor formatting cleanup (trailing commas, whitespace, indentation)

Test plan

• Verify ggufAllShards return type includes urls for both single and sharded GGUF files
• Verify parseSafetensorsMetadata return type includes filepaths for both single and sharded safetensors
• Run existing tests to ensure no regressions

---

Note

Medium Risk
Mostly additive API surface, but it changes TypeScript return types for ggufAllShards and parseSafetensorsMetadata, which could require downstream updates for consumers relying on the previous shapes.

Overview
Adds resolved file location outputs to weight parsers.

ggufAllShards now returns urls alongside shards and parameterCount (for both sharded and single-file GGUF), and parseSafetensorsMetadata now returns filepaths listing the weights involved (single file, or index + shard files for sharded models). Tests are updated to assert the new fields.

^{Written by Cursor Bugbot for commit 8099f34. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

[julien-c]

@mishig25 and @ngxson can i please get a review on this? 🙏

[julien-c]

CI failure seems unrelated

[mishig25]

lgtm! I pushed test cases b365d99

[mishig25]

this red CI is not relevant to this PR.

this CI passes green on rerun.

the likely scenario why the test is/was flaky is: transient network failure/timeout in CI from hub when downloading the header of one of the 64 shard files (kimi-k2.5). Re-running the CI job should made it pass