Split out of #1432 (item 5). Fixes 1–3 landed in #1439; this is a separate command with a separate matching bug.
Problem
fleet status matches the roster by node name, not nodeId. Two observed failures:
- It reported
no node named "kjg-laptop" in the workspace while holding the correct nodeId in the same payload.
- Separately, it matched an unrelated stale node that happened to share the repo-basename name.
Expected
Match on nodeId when one is available in the payload. Name matching should be a fallback at most, and a name collision should not silently resolve to the wrong node.
Refs #1432, #1439
Split out of #1432 (item 5). Fixes 1–3 landed in #1439; this is a separate command with a separate matching bug.
Problem
fleet statusmatches the roster by node name, notnodeId. Two observed failures:no node named "kjg-laptop" in the workspacewhile holding the correctnodeIdin the same payload.Expected
Match on
nodeIdwhen one is available in the payload. Name matching should be a fallback at most, and a name collision should not silently resolve to the wrong node.Refs #1432, #1439