Design a default CodeGuard install CLI

[thomas-bartlett]

Summary

Design a default CodeGuard install/update entry point so new users can get started without choosing between rule files, skills, MCP, and per-agent install paths.

Goals

• Provide a simple default path for common users.
• Keep advanced per-agent installation paths available for users who need them.
• Avoid adding another confusing install option unless it clearly becomes the recommended default.

Design Questions

• Should this be a CLI, a uvx entry point, or another lightweight install mechanism?
• What should the first version support: install only, install plus update, or install plus validation?
• How should it detect the user's environment and choose the right CodeGuard delivery path?
• How should packaging, versioning, release signing, and update behavior work?

Acceptance Criteria

• A first-version scope is proposed.
• Tradeoffs between CLI, uvx, and other install mechanisms are documented.
• The recommended user flow is clear enough to drive docs updates.
• Follow-up implementation work can be split into focused issues or PRs.

Related: discussion #59

[thomas-bartlett]

Current direction: evaluate Vercel Skills / npx skills as the default install and update path before building a CodeGuard-specific CLI.

This seems preferable as a first step because it avoids maintaining a custom installer, already supports multiple agent environments, and may cover the common install/update workflow directly.

Suggested next step: test the CodeGuard skill install/update flow with npx skills, then update the docs if it works cleanly.