Archived
Everything downstream reads the port: the provider is told where to reach the consumer, and the redirection that turns a declared port into the number the machine published is keyed on it. A route naming only its endpoint left the proxy with no port at all, and a proxy with no port has nothing to dial. Caught after the catalogue had already been changed to name endpoints and before the mesh picked those manifests up, which is the only reason nothing broke: every module's manifest is behind its source right now, so the plan still renders from the old shape. The declared port, not the machine one — the redirection happens later and is keyed on the declared number, so filling in the machine port here would be redirected twice or not at all. A route that repeats a port keeps it.