GitHub CLI becomes agent control plane

The pitch is right: if agents are going to do real repo work, `gh` is closer to the truth than a browser UI because it exposes the exact primitives automation needs.

• –The official site now foregrounds `gh copilot`, which signals GitHub sees the CLI as an agent entry point, not just a human convenience tool
• –CLI workflows are easier to audit and compose than click-based automation, especially for PRs, checks, releases, and issue triage
• –`gh` already spans GitHub.com and Enterprise, so teams get one toolchain instead of bespoke scripts per environment
• –The risk is obvious: once agents can run `gh`, permission boundaries and approval gates matter more, not less
• –This is less a new product story than a category shift toward terminal-first orchestration for software operations