onboardlisted

Kraft's tools come from the `kraft` MCP server. If `kraft` is not on PATH, this plugin has been installed without the program it drives: say so and point at https://github.com/itsOmidKarami/kraft#install rather than reporting a connection error. # Onboarding a repo Four mechanical steps, each followed by a check against the repo itself — a zero exit code says the command ran, not that what it did was right. 1. **Connect.** `ensure_repo()` (or `kraft repo connect [PATH]` from a terminal) - files the repo and probes it: test command, forge. Read back the probed `test_command`. Check it against what the repo actually runs: is there a `Justfile` or `justfile` at the repo root with a `test` recipe? If so, and it differs from the probed command, prefer that recipe's command and say so — `probe_repo` has no `Justfile` marker yet (Kraft-reriq), so a repo like this one gets probed with raw `pytest`, which its own CLAUDE.md says never to run directly. Neither `ensure_repo`/`kraft repo connect` nor any MCP tool takes a `test_command` override — only `PATCH /repos` on the API does, and there is no CLI/MCP verb for it. So correct a wrong probe by editing this repo's entry in `repos.yaml` (under Kraft's templates dir) directly, setting `test_command` to the right command, and say what you changed — the running server reads that file fresh on each request, no restart needed. If the repo has submodules, connect writes each `.gitmodules` p