Cloud: cloud.machines reports the app server link's route
The app server link's launcher (CloudService) now records its route, and cloud.machines reports it as link_route: legacy, link, native, or link (native failed: <error>) when CloudNativeFirstLauncher fell back to cmux link.
Why: the item-14 capture v12 baked CMUX_NEXT_CLOUD_NATIVE_LINK=1 and still showed only "cmux link refused the dial: unreachable", so nobody could tell whether Native fell back or never started. Captures record cloud.machines into result.json, so the next run says which path it took.
This is diagnostics only and doesn't change behaviour.
🤖 Generated with Claude Code
Agent session: agent session
![Autofix with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/autofix-with-codesmith-dark-3x.png)
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.
Summary by cubic
Reports which route the app server link launched so cloud.machines shows it as link_route: legacy, link, native, or link (native failed: <error>) when the Native-first launcher fell back.
Previously the v12 capture with CMUX_NEXT_CLOUD_NATIVE_LINK=1 only logged "cmux link refused the dial: unreachable", so it was impossible to tell whether Native fell back or never started. Captures record cloud.machines into result.json, so the next run will show the path taken. Diagnostics only; no behavior change.