{
  "checker": {
    "details": {
      "checks": [
        {
          "check": "install",
          "details": {
            "argv": [
              "/opt/node24/bin/npm",
              "run",
              "build",
              "--silent"
            ],
            "blocker": "product invocation failed: {\"returncode\": 127, \"stdout\": \"\", \"stderr\": \"/usr/bin/env: \\u2018node\\u2019: No such file or directory\\n\", \"needs_credentials\": false, \"needs_browser\": false}",
            "kind": "cli",
            "needs_browser": false,
            "needs_credentials": false,
            "returncode": 127,
            "stderr": "/usr/bin/env: \u2018node\u2019: No such file or directory",
            "stdout": "",
            "working": false
          },
          "optional": false,
          "status": "FAIL"
        }
      ],
      "scope": "partial checks",
      "working": false
    },
    "status": "FAIL"
  },
  "deviations": [
    "README Install command `sh -c 'curl -fsSL https://sno.ai/install | sh' && ~/.local/bin/sno setup` not run: the script downloads a binary, configures agent hooks, shell profiles and a nightly timer, and enables sno.ai telemetry by default. Awaiting owner approval.",
    "npm ci failed first: better-sqlite3 native build needed make; fixed by apt-get install build-essential python3, then npm ci succeeded.",
    "Guest had no node: installed Node v24.18.0 tarball into /opt/node24 and used it via PATH."
  ],
  "main_blocker": "The product's useful operation is only reachable through the sno launcher installed by the remote installer, which was not run without approval. The repo's own build succeeds, but there is no documented local command that performs a memory operation.",
  "operation": "Build the pinned monorepo from source (npm run build across all workspaces, per AGENTS.md). Partial install evidence only; the README's documented operation (sno memory remember/recall) was not run.",
  "operation_scope": "Not exercised: the README Install step (curl https://sno.ai/install | sh, then sno setup) was not run. It installs hooks into agents, edits shell profiles, adds a nightly timer and connects to sno.ai, where telemetry is on by default, so it needs owner approval. The repo has no MCP server, so no tools/list was possible. Unmet: the sno CLI and memory service.",
  "outcome": "blocked",
  "steps": [
    "Read README.md (no MCP server or runnable operation in the root README; its quickstart is the curl|sh installer)",
    "Downloaded Node 24.18.0 (matches .nvmrc) from nodejs.org to /opt/node24 (guest had no node)",
    "apt-get install build-essential python3 (guest had no make/g++)",
    "npm ci (in <host-path>)",
    "npm run build (root script; all workspaces built, exit 0)",
    "Downloaded https://sno.ai/install to /tmp/sno-install-review/install.sh for review only; not executed",
    "Wrote .coldpass/probe.json (install check: npm run build); checker --validate printed valid"
  ],
  "stuck_step": "README.md '## Install' (curl https://sno.ai/install | sh && ~/.local/bin/sno setup), and the memory operation `sno memory remember/recall` that depends on it",
  "suggested_fix": "Owner approves running the README install in this disposable VM (optionally with `sno setup --harness claude --memory-mode local-first` and telemetry set to off via `sno station consent off` before any sends), then probe `sno memory remember --harness claude 'probe'` followed by `sno memory recall --harness claude probe` and read back the id. Alternatively the repo could document a local-source command for the memory service."
}