Generate daemon install command

A pure, idempotent builder — it never mints or persists anything. The api key in an install or rekey command is a placeholder (<API_KEY>) the caller substitutes from the plaintext it holds; a reconfigure command carries no key at all. Minting is a separate mutation (POST /provision), so regenerating a command here (advanced-setting change, OS switch, the Details reconfigure view) never rotates the daemon's key.

The server derives the exact command shape from the record: DaemonPoll vs ServerPoll for the flags, and — for rekey — whether the daemon has checked in (last_seen) to decide whether the command names the existing install it re-keys. An install command reads the same before and after the daemon's first handshake.

curl -X GET "https://example.com/api/v1/daemons/497f6eca-6276-4993-bfeb-53cbbbba6f08/install-command?purpose=install"

{
  "meta": {
    "api_version": 1,
    "server_version": "0.19.6"
  },
  "success": true,
  "data": {
    "docker": {
      "env": [
        "string"
      ],
      "compose": "string"
    },
    "freebsd": "string",
    "linux": "string",
    "macos": "string",
    "msi": {
      "filename": "string",
      "omitted_config_keys": [
        "string"
      ]
    },
    "windows": "string"
  },
  "error": "string"
}

{
  "meta": {
    "api_version": 1,
    "server_version": "0.19.6"
  },
  "success": true,
  "code": "string",
  "error": "string",
  "params": {
    "property1": null,
    "property2": null
  }
}