Install a team from a manifest

Adds a team to this daemon’s catalog from a manifest you supply (the CLI reads team.yml from disk and sends its text). Use teams/hub_install to install from CliqHub instead.

What happens, in order:

1. agent_settings, if sent, are saved as agents.<agent>.<key> settings — so you can supply a missing API key in the same call.
2. The manifest is parsed and validated (YAML, schema, phase graph).
3. Every agent the manifest uses is checked against this daemon (TEAM_AGENT_CONFIG_REQUIRED lists what is missing).
4. Any scope other than local needs a CliqHub sign-in.
5. The team is stored, then settled with CliqHub, which may assign its CliqHub id. If CliqHub says the team isn’t on this daemon’s realm team list, it is removed again and the call fails with TEAM_NOT_IN_REALM.

An installed team is replaced only with force: true; otherwise the call fails with TEAM_ALREADY_EXISTS. To move an installed team to a newer version, prefer teams/update, which refuses downgrades.

From the CLI: cliq team install ./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.