Rename our "host" vocabulary to "agent", the term DWService uses

[ale-rinaldi]

Terminology only — no behaviour change, no breaking change.

Why

dwshell called the machine you connect to a "host". DWService does not. Its own English strings, shipped with the agent (ui/messages/default.py), say:

'agentName':  u'Agent name'
'groupName':  u'Group name'
'errorAgentAlreadyExsists': u'The agent {0} already exists.'

39 occurrences of "agent" against exactly one of "host" — and that one is proxyHost, a network proxy setting. The protocol modules are agent, share, group.

This matters now because agent management is coming: a command group named after the thing it manages reads wrong if the rest of the CLI calls that thing something else.

Not breaking: "host" was never a flag or a config key — only variable names, help text and prose.

What keeps the word

Where "host" means a network host, renaming would be wrong or would falsify a record:

• internal/client — the local hostname labelling a registered trusted device (dwshell on <hostname>)
• internal/session/socket.go — the relay host (u.Host)
• docs/PROTOCOL.md — "Hosts and terminology" is about the service's domains; two further hits are captured terminal output (user@host:~#) and a file literally named hosts
• conhost (the Windows console host) in DESIGN.md, and "repositories are hosted at" in the README

parseUserHost becomes parseUserAndAgent, not parseUserAgent, which would read as the HTTP header.

Verification

• 130 insertions against 130 deletions — a pure rename, no logic touched
• gofmt, go vet, go test -race ./... green
• Exercised against live agents, not just the suite: list, -c with its exit code propagated, and ls on a remote directory

🤖 Generated with Claude Code

https://claude.ai/code/session_01MvidAFW9a2r4hTgHPW9ywG