odin dev_2026_07-1.1: vendored raylib libs are unresolved git-lfs pointer files

The `odin` package (dev_2026_07-1.1, x86_64_v4, cachyos-extra-znver4) ships
`/usr/lib/odin/vendor/raylib/linux/{libraylib.a,libraylib.so.600,libraygui.a,libraygui.so}`
as raw Git LFS pointer text files (~130 bytes each) instead of the resolved
binaries. Example content:

version https://git-lfs.github.com/spec/v1
oid sha256:1199fb5be52a663c099ed42eae5eabba83754ca9a8d7f82e1514ae4d6623874b
size 2869420

This breaks linking for any program using `vendor:raylib`:

/usr/bin/ld:///usr/lib/odin/vendor/raylib/linux/libraylib.a: file format not recognized; treating as linker script
/usr/bin/ld:///usr/lib/odin/vendor/raylib/linux/libraylib.a:1: syntax error
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Root cause looks like the package build didn't run `git lfs pull` (or fetch
with LFS smudging enabled) before packaging vendor/raylib, so the pointer
files got copied verbatim.

Workaround: fetch the odin-lang/Odin repo at the matching tag (`dev-2026-07`,
commit `301c287de9`) and run `git lfs pull --include="vendor/raylib/linux/*"`,
then copy the resolved files over the pointer files in
`/usr/lib/odin/vendor/raylib/linux/`.

Fix: ensure the PKGBUILD runs `git lfs pull` (or clones with LFS enabled)
before packaging.

Start by inspecting the PKGBUILD and the packaging step for the odin dev-2026-07 sources. Ensure Git LFS fetches vendor/raylib/linux/* before those files are copied, then verify the packaged files are resolved binaries rather than pointer text. Confirm that a program using vendor:raylib links successfully.

Written by the indexing model from the issue text.