Fix cloud command documentation

[arsalann]

Summary

Correct the bruin cloud command reference so its examples, flags, scopes, and documented subcommands match the current CLI.

• Fix invalid run, pipeline, instance, glossary, and agent command examples.
• Document all agent create, read, update, and prompt operations.
• Use generic placeholders in the project-list output example.

Why

Several documented commands omitted required flags, accepted unsupported flags, or described behavior the CLI does not support. This made otherwise copyable examples fail.

Impact

Users can rely on the Cloud command page for accurate command syntax and behavior.

Validation

• make build
• npm run docs:build
• ./node_modules/.bin/markdownlint-cli2 --no-globs docs/commands/cloud.md
• git diff --check

[greptile-apps]

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
docs/commands/cloud.md:354-357
**`diagnose` marks `--project-id` as required but the CLI auto-resolves it**

The new flag table lists `--project-id` as `(required)` for `diagnose`, but the implementation calls `resolveProjectID`, which auto-resolves to the single project when only one exists. Only `--pipeline` is unconditionally required. A user with a single project can omit `--project-id` successfully — labelling it required here will confuse them and diverges from how the same flag is described for `runs list`, where the auto-resolve path isn't available.

_{Reviews (1): Last reviewed commit: "Fix cloud command documentation" | Re-trigger Greptile}

[greptile-apps]

_{Reviews (2): Last reviewed commit: "Clarify diagnose project selection" | Re-trigger Greptile}