Implement or hide 'agentops config validate' (currently a stub)

[Dongbumlee]

Source

Discovered during E2E validation of #78.

Problem

agentops config validate --help advertises:

Validate configuration files (planned).

…with no flags. The command appears in the top-level help (agentops config) and looks usable, but invoking it with any argument returns:

No such option: -c

This is a poor user experience: users discover the command, attempt to validate their run.yaml, and get a confusing error.

Two options

Option A — implement it properly (recommended, small change)
Add -c/--config <path> and exercise the existing core/config_loader.py Pydantic models. Print pass/fail and any validation errors. Example:

$ agentops config validate -c .agentops/run.yaml
✅ run.yaml is valid (version=1, target.type=agent, bundle=conversational_agent_baseline, dataset=smoke-conversational)

Option B — hide it
Remove from the CLI surface until implemented.

Per CONTRIBUTING.md ("Do not add CLI commands or flags unless intentionally expanding the product contract"), the contract already advertises this command as planned, so Option A is preferable.

Severity

Low (UX)

[Dongbumlee]

Fix in flight: PR #118 → develop. Will auto-close when merged.

[Dongbumlee]

Reopening — PR #118 is being reverted via #119 because PR #108 (1.0 revamp) supersedes most of those fixes by deleting the systems they patched. Defects still apply; we'll re-scope against the flat agentops.yaml schema after #108 merges. See #119 for details.