Adopt Ground Control from the published grndctl package

[Brad-Edwards]

Summary

Ground Control is now published on npm as grndctl. This repository already uses Ground Control, but its .mcp.json starts the server from a local clone (node /home/atomik/src/Ground-Control/mcp/ground-control/index.js). Move it to the released package so agents run a pinned release instead of whatever branch a local Ground Control clone has checked out.

Work

Follow Moving from a checkout install:

1. On the host: npm install -g grndctl (Node.js 22+, gh signed in) and grndctl install-skills.
2. In this repository: grndctl init. It keeps the existing .ground-control.yaml and .env and only adds or replaces the ground-control entry in .mcp.json so it runs grndctl mcp.
3. Run grndctl doctor and fix anything it reports (for example, a missing Phase E workflow or .env not being ignored).
4. Remove any docs or scripts in this repo that tell contributors to run Ground Control from a clone (node …/mcp/ground-control/index.js, GROUND_CONTROL_DIR, symlinked skills).

Acceptance criteria

• .mcp.json starts Ground Control with grndctl mcp, with no absolute or clone-relative path to a Ground Control checkout.
• grndctl doctor passes in a fresh clone once .env is filled in.
• No repo docs still describe the checkout install.