[upgrade] StarDist: identify current Wave-container version pin vs upstream 0.9.2

Current state

• Pinned: container community.wave.seqera.io/library/python_pip_imagecodecs_nvidia-cublas-cu12_pruned:b668bcb6d531d350 at modules/nf-core/stardist/main.nf:9
• Modules: modules/nf-core/stardist
• Pipeline modes: image (when --method stardist)

Latest upstream

• 0.9.2 (released 2025-12-15): https://github.com/stardist/stardist/releases/tag/0.9.2
• 0.9.0 (2024-04): GPU improvements
• 0.8.5 (2023-07): older patch baseline

Investigation needed

1. Decode the Wave container to determine the current stardist pin
2. Review release notes between current pin and 0.9.2 for behavioral changes affecting --prob_thresh, --nms_thresh, --n_tiles
3. Verify both CPU and GPU container variants stay aligned

Migration plan

• Determine current pinned stardist version (via Wave decode or container pull)
• Bump container to 0.9.2 (or latest compatible)
• Re-run image-mode StarDist tests on Xenium v1 bundle

Risks

• CPU vs GPU containers: ensure both flavors are bumped consistently
• Model file compatibility: stardist ships pretrained models — verify they're compatible at the new version
• Atera relevance: image-mode is XR-gated (out of scope per user direction); primary benefit is for Xenium v1 image mode

Cross-links

• Triggered by: Atera compatibility session 2026-05-28 (broader tool inventory check).

Start at modules/nf-core/stardist/main.nf:9 and inspect or pull the pinned Wave container to identify its StarDist version. Compare the relevant release notes through 0.9.2, checking CPU and GPU variants and model compatibility. Done means a compatible container pin is updated consistently and image-mode StarDist tests pass on the Xenium v1 bundle.