feat(sites): surface sites in the root command

[jamie-at-bunny]

No description provided.

[bogdan-at-bunny]

@codex review

[changeset-bot]

⚠️ No Changeset found

Latest commit: fbbe4b3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[greptile-apps]

Greptile Summary

The PR promotes the static-sites namespace into the root CLI experience.

• Registers sites among the normal root commands and gives the namespace a visible help description.
• Adds package-level usage guidance, examples, and a flag reference for site management.
• Updates the architecture reference to mark sites as a supported command group.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
packages/cli/src/cli.ts	Moves the sites namespace from the hidden experimental command collection into the normal root command list.
packages/cli/src/commands/sites/index.ts	Gives the sites namespace a visible help description while retaining its existing subcommand wiring.
packages/cli/README.md	Adds package-level documentation and examples for the newly surfaced sites command group.
AGENTS.md	Updates the architecture and command reference to describe sites as a supported root namespace.

_{Reviews (2): Last reviewed commit: "update descriptions to include sites" | Re-trigger Greptile}

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Can't wait for the next one!

Reviewed commit: 915adf5d37

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".