[nick2781]

Bus configuration described service relationships but did not establish the corresponding inter-process connections, so adding a registry alone could not produce a working service path.

During Net startup, queue each configured relation-selected target in the same channel and zone through the existing SS client service. Exclude self and deduplicate target IDs. Reuse registration, heartbeat and the existing 30-second reconnect policy. Reject ambiguous configuration and unusable selected dial endpoints with actionable startup errors. No additional registry process, public API or wire format is introduced.

Validation on local macOS TCP loopback:

• Bus configuration: 8 cases / 191 assertions; existing Bus and Net plugin checks passed.
• Five launcher error modes and seven selected-target endpoint controls passed.
• Two real plugin/DSO processes completed SS registration and a Protobuf roundtrip, observed disconnected send rejection, restarted the target at the same ID/endpoint, reconnected and completed another roundtrip, then stopped normally.
• 157 policy tests, clang-format 18 and Nimbus passed; canonical English/Chinese HTML and Markdown were checked.

This is startup-only static discovery. It provides no hot reload, dynamic membership, global identity authority, cross-zone routing, cross-host or capacity proof. UDP/native Windows controller execution were not covered locally. Shipped deployment configuration was inspected without modification; migration and bind-versus-dial distinctions are documented.

BREAKING CHANGE: Bus rejects duplicate application names/types, directed relations and process IDs. Net now automatically connects selected same-channel/same-zone processes and rejects missing or non-dialable TCP/UDP intranet endpoints. Remove duplicates and unwanted outgoing relations and provide reachable peer endpoints before upgrading; wildcard addresses remain valid for listening, not dialing.