[Bug]: ocx link status on a Home-initiated Child reports role: standalone, and ocx status calls the Home a hub #6944

Client or integration

Other

Area

CLI

Summary

On a Child linked from the Home, with /healthz reporting "role":"client" and requests relayed to the Home, the Child's own CLI describes the link inconsistently:

• ocx link status --json → {"role":"standalone","listener":{"state":"off","port":null},"links":[],"child":null}.
• ocx connect status --json correctly reports state: connected and transport: link.
• ocx status prints Hub http://127.0.0.1:<tunnel>: state unavailable (this hub is too old to report its state; upgrade the hub) and Remote hub: connected (http://127.0.0.1:<tunnel>).

For a Home-initiated link the record lives in the Home's link store, so the Child's store is empty and the status projection falls back to standalone. A user checking the Child with ocx link status concludes the link did not apply.

The dashboard uses the same internal wording: on the Home, each Child row reads "Connected · Hub 시작" (from hub-initiated) on a page that otherwise says Home and Child.

Reproduction

1. Link a Child from the Home dashboard, then restart the Child's proxy so it serves as a client.
2. On the Child: ocx link status --json, ocx connect status --json, ocx status.

Expected: ocx link status on a Child reports the Child side (role client or child, direction home-initiated, tunnel port, tunnel state from clientLinkTunnelStatus), and ocx status describes a Remote Link Home rather than a hub.

Version

Child 2.83.0; Home 2.81.0. The "too old" line may be accurate for a 2.81.0 Home. The role: standalone answer comes from the Child's local projection and does not depend on the Home's version.

Operating system

Children macOS 27 arm64 and Ubuntu 24.04 x86_64

Provider and model

No response

Logs or error output

$ ocx link status --json
{"role":"standalone","listener":{"state":"off","port":null},"links":[],"child":null}
$ ocx status
⚠️  Hub http://127.0.0.1:54958: state unavailable (this hub is too old to report its state; upgrade the hub) — provider and login lines below are LOCAL and do not describe the hub.
   Remote hub: connected (http://127.0.0.1:54958)

Screenshots and supporting files

No response

Redacted configuration

No response

Checks

• I searched existing issues and documentation.
• I removed secrets, tokens, account details, request credentials, and personal data.