Workspace numpy conflict: ssik>=2.0 vs geodude-assets[assembly]<2

[siddhss5]

Bug

Workspace uv sync fails with an unsatisfiable resolution:

× No solution found when resolving dependencies:
  ╰─▶ Because ssik>=1.1.0 depends on numpy>=2.0 and only the following versions of ssik are available:
          ssik<=1.1.0, ssik==1.1.1, ssik==1.2.0
      we can conclude that ssik>=1.1.0 depends on numpy>=2.0.
      And because mj-manipulator depends on ssik>=1.1.0 and
      geodude-assets[assembly] depends on numpy>=1.26,<2, we can conclude that
      mj-manipulator and geodude-assets[assembly] are incompatible.

The Workspace Integration CI workflow has been failing every nightly run since at least 2026-05-24 (sha b1564a63).

Out of scope

Not introduced by #63 (setup.sh wipe of stale per-package venvs). Filing separately to unblock that merge.

Fix direction

Either:

1. Pin geodude-assets[assembly] to numpy>=2.0 (if its build pipeline supports it).
2. Drop the numpy<2 upper bound in geodude-assets[assembly] if it's only there defensively.
3. If geodude-assets[assembly] is no longer needed in the integration matrix, drop it from the workspace deps.

Worth a quick audit of why [assembly] was pinned to numpy<2.

[siddhss5]

Fixed upstream by personalrobotics/geodude_assets#17 (drop numpy<2 upper bound). Workspace uv sync resolves cleanly now.