{ "checker": { "claims": [ { "claim": "Capito turns an OpenAPI spec into compact help the agent can read step by step", "command": " -m capito operations items", "evidence": "api:GET /items/{itemId} Get item\n", "expected": "operation listed with its summary", "input": "items.yaml contract with GET /items/{itemId}", "kind": "claim", "outcome": "Real input produced the expected result: api:GET /items/{itemId} Get item", "returncode": 0, "source": "Capito turns an OpenAPI spec into compact help the agent can read step by step.", "source_checked": true, "source_file": "README.md", "verdict": "yes" }, { "claim": "describe prints a help card for an operation", "command": " -m capito describe 'api:GET /items/{itemId}'", "evidence": "Get item\nauth: \nrequest: path itemId: string\nreturns: Result\n body on 200 (The item): Item\n body on 404 (Not found): not described\nItem = {\n id: string\n name: string # Shown in the catalog\n status?: DRAFT|ACTIVE|ARCHIVED\n}\nexample: client.call('GET', '/items/{itemId}', path={'itemId': 'example'})\n", "expected": "help card with the summary", "input": "api:GET /items/{itemId}", "kind": "claim", "outcome": "Real input produced the expected result: Get item", "returncode": 0, "source": "python -m capito describe \"api:GET /items/{itemId}\"", "source_checked": true, "source_file": "README.md", "verdict": "yes" } ], "cycle_checks": [ { "claim": "Scheduled or looping main behavior", "command": "", "evidence": "Entry points inspected (capito/__main__.py CLI, capito/__init__.py Client API). grep for cron/schedule/webhook/--once/--now/loop/daemon in capito/ and README found nothing. Capito is a request-by-request library and CLI with no scheduler; the CI schedule in .github/workflows is not a product cycle.", "expected": "identify the product trigger", "input": "source inspection", "kind": "cycle", "outcome": "Entry points inspected (capito/__main__.py CLI, capito/__init__.py Client API). grep for cron/schedule/webhook/--once/--now/loop/daemon in capito/ and README found nothing. Capito is a request-by-request library and CLI with no scheduler; the CI schedule in .github/workflows is not a product cycle.", "source": "repository entry points", "verdict": "yes" } ], "details": { "argv": [ "", "-m", "capito", "describe", "api:GET /items/{itemId}" ], "kind": "cli", "needs_browser": false, "needs_credentials": false, "returncode": 0, "scope": "product operation", "stderr": "", "stdout": "api:GET /items/{itemId} \u2014 Get item\nauth: \nrequest: path itemId: string\nreturns: Result\n body on 200 (The item): Item\n body on 404 (Not found): not described\nItem = {\n id: string\n name: string # Shown in the catalog\n status?: DRAFT|ACTIVE|ARCHIVED\n}\nexample: client.call('GET', '/items/{itemId}', path={'itemId': 'example'})", "working": true }, "evidence_strength": "readme_checked", "example_checks": [ { "claim": "docs usage prints the usage guide", "command": " -m capito docs usage", "deferred": false, "evidence": "ate is shared and protected by a lock; requests run in parallel. Run dependent steps of one script sequentially.\n- **Connections are reused.** The client has a connection pool; `client.close()` or `with Client.from_config() as client:` closes it, otherwise it closes with the process.\n- **The process environment does not affect requests.** Proxies from `HTTP(S)_PROXY`, `.netrc` and certificates from environment variables are not used; redirects are not followed: a 3xx response is returned as is.\n- **Do not go through the operation catalog blindly**: some operations create, delete or cost money.", "expected": "usage guide heading", "input": "docs usage", "kind": "example", "outcome": "command completed successfully", "returncode": 0, "source": "README.md docs table", "verdict": "yes" }, { "claim": "the documented test suite passes", "command": " -m pytest -q", "deferred": false, "evidence": "........................................................................ [ 24%]\n........................................................................ [ 48%]\n........................................................................ [ 72%]\n........................................................................ [ 96%]\n............ [100%]\n300 passed in 24.34s", "expected": "all tests pass", "input": "pytest -q", "kind": "example", "outcome": "command completed successfully", "returncode": 0, "source": "AGENTS.md Checks", "verdict": "yes" } ], "status": "PASS" }, "deviations": [ "README Install says `pip install capito` (PyPI). Used the editable install from the pinned source per AGENTS.md so the tested code is the pinned commit.", "The workspace had no capito.toml, so a demo project was created at with a made-up items.yaml contract and capito.toml (outside the checkout). Its base_url is a placeholder and no server was started.", "No live HTTP request was made: the README's `client.call` example needs a running API, which this repo does not provide." ], "fault_owner": null, "main_blocker": null, "operation": "Read an OpenAPI contract and print compact help for an operation with `python -m capito operations` and `python -m capito describe` (plus docs usage and the offline pytest suite)", "operation_scope": "Linux guest, Python 3.12.3 (README requires 3.12+), pinned source 47d1fde (capito 0.4.1). Offline: help reads a local contract and sends no API requests. Live HTTP calls were not exercised because the repo ships no server and no project client.", "outcome": "working", "plain_failure": null, "steps": [ "git init; git remote add origin https://github.com/aartikov/capito; git fetch --depth 1 origin 47d1fde56edb1294286c4f38d13adc7b82c8a7b3; git reset --mixed FETCH_HEAD", "python3 -m venv .venv; .venv/bin/python -m pip install -r requirements.lock; .venv/bin/python -m pip install --no-deps -e . (per AGENTS.md Environment)", ".venv/bin/python -m pytest -q (300 passed)", "python -m capito docs usage", "python -m capito operations items", "python -m capito describe \"api:GET /items/{itemId}\"" ], "stuck_step": null, "suggested_fix": "None required for the tested path. To cover live calls, add a documented mock server or a project client to the probe setup." }