release: unilab 1.3.4

[TATP-233]

Summary

• Release UniLab 1.3.4.
• Bump the package version in pyproject.toml, pyproject.rocm.toml, and the root unilab entries in both lockfiles.
• Add the bilingual 1.3.4 changelog entry covering the release contents since 1.3.3.

Linked Work

• Issue: release maintenance (no new implementation issue)
• Parent roadmap: roadmap: tensor-only Manager-Based runtime and three-backend scope reduction #1811 tensor runtime roadmap and related ADRs linked from the changelog
• Roadmap declared base: not applicable
• Milestone: none
• Base branch: main

Release contents summarized in the changangelog

• Breaking: tensor-only Manager runtime (TorchEnv), deletion of NpEnv/NpEnvState, sole Manager-Based factory and scoped tensor backend set, removal of retired task owners/WarpSAC config tree.
• Dependencies: unisim-core>=1.7.15, unilab-rl==1.4.11, mjbatch-uni~=0.2.5, upstream SAC learner naming.
• Added: tensor selected-reset lifecycle, device reset/startup DR, packed entity tensor reads, backend-declared sensor inventory, Manager Torch RNG, CUDA MPS execution sharing and uni-cumps, production soak/diagnostics, off-policy resume, FlashSAC update/CUDA Graph controls, generic motion-tracking capabilities.
• Changed: reduced Manager host boundaries, explicit MuJoCo host-bridge carrier placement, removal of the repository-wide uv pin.
• Fixed: tensor motion/runtime and backend owner contract issues; FlashMimic task ownership moved downstream.

Validation

• make test-all passed on the final local head before this PR was created or updated
• Additional task-specific validation listed below

Commands actually run:

# Final release head (interactive rank-local CUDA_VISIBLE_DEVICES unset for the
# environment-sensitive process-device test)
unset CUDA_VISIBLE_DEVICES
make test-all
# Result:
#   ruff format/check: passed
#   mypy: passed
#   pyright: 0 errors
#   non-slow coverage suite: 1895 passed, 43 skipped, 495 deselected
#   benchmark import smoke: module 34/34, script 35/35

# Distribution build and metadata verification
uv build --out-dir /tmp/unilab-1.3.4-dist
uvx --from twine twine check /tmp/unilab-1.3.4-dist/*
# Result:
#   unilab-1.3.4.tar.gz PASSED
#   unilab-1.3.4-py3-none-any.whl PASSED

# Version consistency
rg -n '^version = "1\\.3\\.4"|name = "unilab"' pyproject.toml pyproject.rocm.toml uv.lock uv.rocm.lock
# Result: package profiles and root unilab lock entries are 1.3.4

Remote CI route:

• Base main: current-head CI will run on this pull request. The release tag should be pushed only after this exact release commit merges and its ci.yml run succeeds.

Impact

• Backend impact: mujoco / motrix / MJWarp tensor runtime and scoped backend surface; version-only plus changelog in this PR
• Platform impact: macOS / Linux
• Training effect expected: no behavior change from this release commit itself; the release metadata covers the tensor runtime already merged on main

Artifacts

• W&B: none
• benchmark result: none
• video / screenshot: none
• ONNX / checkpoint: none
• local distributions: unilab-1.3.4.tar.gz, unilab-1.3.4-py3-none-any.whl (built only for verification; official artifacts are produced by the tag workflow)

Checklist

• Added or updated tests where needed — no test change required for version/changelog metadata
• Updated docs if behavior or workflow changed — changelog updated
• Linked the driving issue — release maintenance PR, roadmap links included in changelog
• Noted any follow-up work explicitly

Follow-up after merge:

1. Dispatch ci.yml on the exact merged release commit if a current-head run is not already attached.
2. Push annotated tag v1.3.4 to that exact commit.
3. Confirm the release workflow builds/publishes distributions and creates the GitHub release.