{
  "checker": {
    "details": {
      "argv": [
        "npm",
        "run",
        "compile"
      ],
      "kind": "cli",
      "needs_browser": false,
      "needs_credentials": false,
      "returncode": 0,
      "scope": "product operation",
      "stderr": "",
      "stdout": "\n> xlide@11.1.22 compile\n> npm run check-types && node esbuild.js\n\n\n> xlide@11.1.22 check-types\n> tsc --noEmit\n\n[watch] build started\n[watch] build started\n[watch] build finished\n[watch] build finished",
      "working": true
    },
    "status": "PASS"
  },
  "main_blocker": null,
  "operation": "Developer setup from README 'For Developers And Contributors': npm install, then npm run compile (type-check plus esbuild bundle of the VS Code extension). Both succeeded and produced out/extension.js and out/web/extension.js.",
  "operation_scope": "Build only. The extension runs inside VS Code via F5 (Extension Development Host), which is not available in this headless VM, and the VBA/Office features need Windows and Office. The README's npm test, test:integration, and test:office were not run, per the smoke-task rules. The separate xlide-mcp server (README 'Outside VS Code', uvx) is not in the pinned repo and was not started.",
  "outcome": "working",
  "steps": [
    "apt-get install -y nodejs npm (Node v18.19.1, npm 9.2.0)",
    "npm install (first attempt: registry 500 on tunnel-0.0.6.tgz; second attempt: exit 0, 402 packages)",
    "npm run compile (exit 0)"
  ],
  "stuck_step": null,
  "suggested_fix": "Node 18 is older than the lockfile engines (vite 8 and vitest 4 want Node >=20.19 or >=22.12). The build works anyway; installing Node 20.19+ or 22 would remove the EBADENGINE warnings. The transient registry 500 is resolved by retrying npm install."
}