Raise the version to 0.0.2 so the channel can carry this description

[T-K-233]

The channel has been serving a description from before #16

ros-jazzy-lite-description on prefix.dev/berkeley-humanoids is 0.0.1, and so is this tree. Berkeley-Humanoids-Buildfarm uploads with --skip-existing, so every change since that first build has been a silent no-op — the upload skips a version the channel already holds.

I pulled the published package and diffed its lite_dummy.urdf.xacro against this tree:

-  <xacro:arg name="use_fake_hardware" default="true"/>
-  <xacro:arg name="use_sim" default="false"/>
-  <xacro:arg name="mode" default="arms"/>
+  <xacro:arg name="use_mock_hardware" default="true"/>
+  <xacro:arg name="sim_mujoco" default="false"/>

So the published copy predates #16's two-boolean backend convention. It is not merely stale — it is incompatible: every bring-up passes use_mock_hardware:= / sim_mujoco:=, which that xacro does not declare, so a consumer installing it from the channel fails at xacro expansion. #17's backend test matrix and #18's component-name parity are missing from it too.

The fix is the one the recipe asks for

deps/lite_description/pixi.toml in the buildfarm:

[package.build.source]
git = "https://github.com/Berkeley-Humanoids/Lite-Description.git"
branch = "main" # Our fork. Raise its package.xml version when you patch it.

Bumping package.xml to 0.0.2 is what makes the next buildfarm run actually publish. Patch bump, matching how humanoid_control versions (it is at 0.0.4 across breaking changes).

Why now

This blocks the channel-first switch for the deployment repos: ros-jazzy-humanoid-bringup-lite pulls ros-jazzy-lite-description from the channel, so a deployment that installed binaries today would get a description its own launches cannot expand.

After this merges, the shared buildfarm needs a run to publish 0.0.2.

🤖 Generated with Claude Code

https://claude.ai/code/session_01EotyWG9YmYvg5xE2v3Zkpt