[earakely-scale]

What

task_images refused a task with an image stored only as a tarball under a bare name, raising "stored only as a docker save tarball". It ran the import's walk with no refs, and without one the import can't write that image. But that image is exactly what an export loads on its VM, pushes, and then hands back as a ref. So the listing was refusing the images it exists to find.

The listing now names every image without judging how it's stored. It still raises on the import's other problems, such as an env the store doesn't hold. The previous test asserted the wrong behaviour and is replaced:

• New: a tarball-only image is listed, and the import then accepts a ref for it.
• Refusal: the listing still refuses a task whose env isn't in the store.

Testing

tst/unit/bundle passes (1134), and lint is clean.

🤖 Generated with Claude Code

Confidence Score: 5/5

The PR appears safe to merge.

Summary

task_images now lists images regardless of how they are stored, so callers can push them and supply references to import_task.

• Task image listings include tarball-only images for later registry imports.

_{Reviews (1) · Last reviewed commit: "fix(bundle): task_images lists every ima..." · Reviewed by Greptile}