glam is stuck at 0.29.3 because the valence fork pins it, and that fork is 47 commits behind upstream

[andrewgazelka]

glam is the one workspace dependency that cannot be updated, and it is pinned four minors behind: 0.29.3 against 0.33.2 on crates.io.

The block on it is not in this repo. valence_protocol exposes glam types (Vec3, Quat, BlockPos) across its whole public API, and the vendored fork pins 0.29.3. Anything newer here puts two glam crates in the tree, and every valence signature stops accepting the vectors hyperion holds.

So the fix has to land in TestingPlant/valence first, on both pinned branches, before this repo can move.

While checking this during #991 I also measured where that fork sits: feat-bytes (locked at fb792dc, from 2025-06-29) is 18 commits ahead and 47 behind valence-rs/valence main. So the glam bump and the general staleness of the fork are the same piece of work.

What would close this:

1. Bump glam in TestingPlant/valence on feat-bytes, ideally while catching the branch up on upstream main.
2. Repoint the ten [workspace.dependencies.valence_*] entries at the new revision.
3. Drop the glam hold comment in Cargo.toml and run cargo upgrade -p glam.

Filed by an agent from a dependency-update pass; not reviewed by a human.