[michaellchung]

Summary

• The Miles, SGLang and verl forks and the yeto-miles-ports / yeto-release images moved to the agentenv organization. Only repository names change; commits and digests are identical.
• MILES_NEXT_REPOSITORY, SGLANG_NEXT_REPOSITORY, VERL_REPOSITORY, MILES_NEXT_IMAGE (same digest sha256:5b9dc2a9...), the Dockerfiles, build/check scripts, stage1 examples and probes now name agentenv.
• Images built before the move keep https://github.com/michaellchung/miles as the /root/miles origin. MilesRevisionPins gains former_repositories; the island revision check (including --miles-commit overrides) accepts the current and the former origin. check_miles_ports_image.sh does the same. New unit tests cover both origins.
• Historical evidence under openspec/ is unchanged. yeto/rl/algos/vendor/miles_mis.py is unchanged (its source hash is pinned).

Migration record

• Images: all 25 tagged yeto-miles-ports versions and both yeto-release versions copied with crane copy; crane digest on each ghcr.io/agentenv/... tag equals the source digest.
• Forks: every non-main branch of michaellchung/miles and michaellchung/sglang pushed to agentenv/{miles,sglang} (no force; remote heads equal the source heads). agentenv/verl created as a fork of michaellchung/verl (main = acad9875).
• Nothing under michaellchung was deleted; in-flight runs still use it.

Before merge

• The agentenv packages yeto-miles-ports and yeto-release are still private. An org/package admin must set them public in the package settings; otherwise anonymous pulls of the default image fail.
• Other in-flight S26 branches still reference michaellchung (e.g. new MILES_NEXT_COMMIT / image pins and build records on s26-e2-async, s26-e03-ablation). They need the same rename when they merge; the new pins live on agentenv already (yeto/s26-e6-fp8-ignore, yeto/fp8-act-cast, and the 9462de5-* image tags).

Test plan

• Full suite on yeto-cpu-test: 6634 passed, 94 skipped, 0 failed.

🤖 Generated with Claude Code