✅ Done! Reviewed PR #17279 and approved it ✅ TL;DR: it does what it says — named OpenHands/ACP profile launches now carry the

<RUNTIME_SERVICES>

block via

agent_launch_additions.system_message_suffix_append

, so a profile-launched agent can discover the local automation backend instead of guessing the Cloud URL. The earlier blocking finding (the router-at-start instruction being emitted on the profile path where the resolved agent has no

route_task_to_model

tool) is now fixed —

profileLaunchSuffix

only carries runtime services, and the new test locks that boundary in. Things I checked: the change stays on the right side of the ownership boundary (uses the published SDK contract, no server logic reimplemented), CI is green on head

ef11390da

, and

agent_launch_additions

exists back to SDK v1.51.0, which is already the

minimumAgentServer

— so no compatibility bump needed. The saved profile isn't mutated and the change is local-only (cloud never advertised runtime services). One non-blocking note (flagged as eval risk, not a defect): the before/after capture in

.pr/live-check.md

was recorded on the old 1.50.1 pin with a mock LLM and hasn't been rerun on the current 1.53.0 pin, so a maintainer may still want a quick live check on a named-profile launch before merging.