Add canonical server start command #33
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "review/cli-server-start"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Exposes server startup as the canonical wraptool server start lifecycle command, retains root-level wraptool serve as a hidden compatibility alias for persisted MCP configs and service units, and updates user-facing documentation. Decision: adopt grouped server start, status, and stop commands without breaking generated configuration. Verified with go test ./..., go vet ./..., golangci-lint run ./..., and CLI help checks.
server start, keepserveas a hidden alias`serve` was a root-level verb for what is really an operation on the `server` noun, so the group read as incomplete: `server` had stop and status but no start, and start lived elsewhere. newServeCmd is now parameterised on name/visibility and registered twice — as `server start` (canonical) and as a hidden root-level `serve`. Same command object, so flags and behavior can't drift. The alias is permanent, not a deprecation window: internal/harness writes `args: ["serve", ...]` into every generated .mcp.json and the documented systemd unit invokes it, and those files outlive an upgrade. Generated configs keep emitting `serve` for the same reason — a config written today should survive a rollback to an older binary. Docs move to `server start`; prose sites that read badly under a mechanical substitution ("a restart of `wraptool serve`") were reworded to "the server" instead. design/ left as a record. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QPkao1ADjUP2i7uRsHJB7P