{
  "checker": {
    "details": {
      "argv": [
        "<host-path>",
        "run",
        "--root",
        ".",
        "--file",
        "src/calc.py",
        "--format",
        "human",
        "--allow-best-effort-memory",
        "--",
        "/tmp/hoimin-venv/bin/python",
        "-m",
        "pytest",
        "-q"
      ],
      "blocker": "a unit suite does not establish a useful product operation",
      "kind": "cli",
      "working": false
    },
    "status": "FAIL"
  },
  "deviations": [
    "README 'Quick start' command without --allow-best-effort-memory failed: 'portable resource limits require --allow-best-effort-memory: failed enabling delegated controllers with +memory +pids ... Permission denied'. Reran with --allow-best-effort-memory placed before -- as the README instructs for Linux without delegated cgroup v2.",
    "README's example target src/calc.py does not exist in the workspace; used the existing fixture tests/fixtures/projects/basic (src/calc.py + tests) copied to /tmp/hoimin-basic.",
    "Installed uv via its curl|sh installer and a Python 3.14 interpreter via uv, since the guest only has python3 3.12."
  ],
  "main_blocker": "The documented operation (hoimin run ... -- <project test command>) requires a test runner after --. The checker bans any argv token in {pytest, unittest, jest, vitest, mocha, tox, nox}, so no run-based probe passes validation. hoimin plan also requires a test argv after -- (verified: \"at least one test argv element is required after `--`\"), so it has the same conflict.",
  "operation": "Ran the README quick-start mutation test (hoimin run --root . --file src/calc.py --format human -- <test command>) on the pinned repo's basic Python fixture (tests/fixtures/projects/basic, copied to /tmp/hoimin-basic): baseline pytest passed, 3 mutants generated and all 3 killed, score 1.00, exit 0.",
  "operation_scope": "CLI mutation run only. The README's 'Plan and verify with an agent' workflow and the Rust build were not exercised. Full test/lint suites were not run per instructions. The run uses --allow-best-effort-memory because this guest lacks delegated cgroup v2 controllers, so memory is not hard-capped. hoimin is a CLI, so the MCP start/list_tools step does not apply.",
  "outcome": "blocked",
  "steps": [
    "curl -LsSf https://astral.sh/uv/install.sh | sh (uv 0.13.1; prerequisite for the README install)",
    "uv python install 3.14",
    "uv tool install --python 3.14 hoimin (installed hoimin 0.13.1)",
    "hoimin --help (verified)",
    "copied tests/fixtures/projects/basic to /tmp/hoimin-basic; uv venv -p 3.14 /tmp/hoimin-venv; uv pip install pytest",
    "baseline: python -m pytest -q (1 passed)",
    "hoimin run --root . --file src/calc.py --format human -- /tmp/hoimin-venv/bin/python -m pytest -q (first attempt refused, see deviations)",
    "hoimin run ... --allow-best-effort-memory -- /tmp/hoimin-venv/bin/python -m pytest -q (exit 0, score 1.00)"
  ],
  "stuck_step": "checker --validate rejects .coldpass/probe.json: \"a unit suite does not establish a useful product operation\" (the probe argv contains the token pytest, which is the README test command passed after -- to hoimin run)",
  "suggested_fix": "Allow the test runner token when argv[0] is the product (for example, exempt hoimin run/plan/verify from the UNIT_SUITE rule), or accept an explicit check role for mutation-testing runs. Do not rename the runner to evade the rule."
}