amadan
A platform alias keeps the flat socket after its instance nests (502) open
Found during the v0.28.7 flagship roll (2026-10-21 14:42Z). The log is own/after236/flagship-roll-v0.28.7.md on docs-t1.
Symptom: a --platform alias host (#209 shape) answers 502. The edge logs proxy error: dial unix /run/carlos/<instance>.sock: connect: no such file or directory.
Cause: the alias's registry row still has socket=/run/carlos/<instance>.sock, the legacy flat path. The instance it points at has been nested since before 2026-10-20, and its own row has socket=/run/carlos/instances/<instance>/app.sock. The nesting migration rewrites the instance's row but not the rows of aliases that share its process. carlos status --layout lists the alias as external, which hides that it is broken.
Scope: one alias on flagship today, on two boxes. The instance itself serves 200. The roll did not cause it; it predates v0.28.7.
Wanted:
- Nesting (and un-nesting) moves every row that shares the instance's socket: the platform alias rows.
- A layout and status check that flags an alias whose socket does not exist, rather than calling it
external. - A one-time repair for rows already stranded.