{
  "unbreak_version": "0.1.7",
  "repo": "fixtures/apibr-vagas-aggregator-ui-892",
  "pr": 1,
  "head_sha": "bench:apibr-vagas-aggregator-ui-892:1",
  "base_sha": "bench:apibr-vagas-aggregator-ui-892:base",
  "package": {
    "name": "vitest",
    "from": "4.1.11",
    "to": "5.0.1",
    "ecosystem": "npm"
  },
  "skill": "peer-conflict",
  "outcome": "green",
  "billable": true,
  "baseline": {
    "passed": 131,
    "failed": 0,
    "flaky": []
  },
  "candidate": {
    "passed": 131,
    "failed": 0
  },
  "regressions": [],
  "missing": [],
  "runner": {
    "name": "vitest",
    "command": "vitest run --coverage"
  },
  "characterization": {
    "generated": 0,
    "passed": 0
  },
  "changes": [
    {
      "file": "package-lock.json",
      "reason": "regenerated by the package manager"
    },
    {
      "file": "package.json",
      "reason": "\"@vitest/coverage-v8\": \"^4.1.10\", → \"@vitest/coverage-v8\": … — I bumped `@vitest/coverage-v8` from `^4.1.10` to `^5.0.1` in `package.json` so it matches the `vitest@5.0.1` peer requirement (its newest release, 5.0.2, satisfies the new major and is what got installed). I ran `npm install` to resync the lockfile (required since `npm ci` demands sync), then verified `vitest run --coverage` passes (26 files, 131 tests, coverage report generated normally) with no…"
    }
  ],
  "forbidden_touches": [],
  "cost": {
    "input_tokens": 21452,
    "cached_tokens": 137246,
    "output_tokens": 1868,
    "usd": 0.1285
  },
  "turns": 10,
  "wall_seconds": 183,
  "attestation": "unsigned"
}