{
  "checker": {
    "details": {
      "argv": [
        "/workspace/evonic",
        "agent",
        "get",
        "probe_bot"
      ],
      "kind": "cli",
      "needs_browser": false,
      "needs_credentials": false,
      "returncode": 0,
      "scope": "product operation",
      "stderr": "",
      "stdout": "ID:          probe_bot\nName:        Probe Bot\nDescription: \nStatus:      enabled\nSuper:       no\nModel:       (default)",
      "working": true
    },
    "status": "PASS"
  },
  "deviations": [
    "Manual install step 'python3 -m venv .venv' failed: ensurepip not available on Ubuntu. Ran apt-get install -y python3.12-venv, then recreated the venv. The apt step also printed debconf frontend warnings, which are harmless.",
    "README one-liner install (curl evonic.dev/install.sh | bash) was not used; the manual install path was used instead to keep source unchanged and avoid network-fetched scripts."
  ],
  "main_blocker": null,
  "operation": "Created agent 'probe_bot' via ./evonic agent add, then read it back with ./evonic agent get probe_bot and ./evonic agent list",
  "operation_scope": "Exercises the local CLI and SQLite-backed agent store. Web UI/API (/api/agents) requires first-time super-agent setup (/setup) and was not exercised. No LLM endpoint, browser, or credentials were used.",
  "outcome": "working",
  "steps": [
    "apt-get install python3.12-venv (python3 -m venv failed with ensurepip missing)",
    "python3 -m venv .venv",
    ".venv/bin/pip install -r requirements.txt",
    "chmod +x ./evonic",
    "./evonic status (generated SECRET_KEY into .env)",
    "./evonic start -d (server on 0.0.0.0:8080, PID 882)",
    "./evonic agent add probe_bot --name \"Probe Bot\"",
    "./evonic agent get probe_bot",
    "./evonic agent list"
  ],
  "stuck_step": null,
  "suggested_fix": null
}