… generated workspace templates: (#711)

- `templates/cu_full/components/bridges/cu_example_shared_bridge/src/messages.rs`
- `templates/cu_full/apps/cu_example_app/src/messages.rs`

You can regenerate the workspace and rerun `cargo build` to confirm the warnings are gone.

…t, and verified both dependent crates still check cleanly. (#713)

Changes:
- Updated glam version in `components/libs/cu_transform/Cargo.toml`.
- Updated glam version in `components/payloads/cu_spatial_payloads/Cargo.toml`.

Checks run:
- `cargo +stable check -p cu-transform -p cu-spatial-payloads`

Next steps (optional):
1. Run `cargo +stable check --workspace` if you want broader coverage.
2. Run `cargo +stable nextest run -p cu-transform -p cu-spatial-payloads` if you want tests as well.

…ctly use it and ran cargo check on those crates. (#714)

Changes:
- `components/sources/cu_v4l/Cargo.toml`
- `examples/cu_msp_bridge_loopback/Cargo.toml`

Checks run:
- `cargo +stable check -p cu-v4l -p cu-msp-bridge-loopback`

If you want, I can also run the broader CI-aligned checks (`just std-ci`) or `cargo +stable nextest run --workspace --all-targets`.

* (cu29_runtime) improve error handling

* cleared the async processing state and recorded the error when the output mutex is poisoned in CuAsyncTask::process

* fmt

* (cu29_unifiedlog) improve error handling

* simplify