Validate a team

Checks a team’s files without installing it — everything teams/install would reject, and more. Send the files as cliq team install would (team.yml, roles/, dependencies.yml, README.md, hugs/<name>/dist/). Returns every problem at once, warnings, and a summary of the team (name, version, phase count, agents referenced).

Errors — any one of these and the team won’t install:

1. team.yml: YAML, schema, phase graph; a name of the form @scope/slug.
2. Files that aren’t part of a team.
3. Lines a phase’s agent doesn’t accept, and required agent inputs missing.
4. A role: naming a file the team doesn’t have (the run would fail at that phase).
5. A team hug whose dist/ isn’t a valid hug build.
6. Agents that aren’t on this daemon’s agents path (CLIQ_AGENTS_PATH, agents.path, ~/.cliqrc/agents), or are missing a required setting.
7. Phases asking with a hug this daemon can’t find (not built in, not on the hugs path, not in the team).

Also errors, though install doesn’t check them: inputs declared but not used by any phase or role; a dependencies.yml that isn’t a YAML array. Warnings: orphan phases.

The response always has valid: true/false, an errors array, a warnings array and a summary object.

From the CLI: cliq team validate ./path/to/team.

No credential is needed from this machine. From another host, send Authorization: Bearer with a dispatch token CliqHub signed for this daemon or a cliq_tok_… personal token of a user in the daemon’s realm; this only works once the daemon is connected to CliqHub. See Authentication.