kacerrandClaude Opus 5
41fbd5e7e6
Closes out the review-fix campaign. The kvm2 provider was deployed in-cluster and validated against beelink -- the first time any of this code had run against real libvirt rather than the in-memory fake. config/manager/providers_config.yaml ships the kvm2-home entry enabled, since the operator is now running it for real. review/ carries the code review the four H-commits reference, so H1..H4 resolve to something rather than dangling: scope, the seven-chunk sweep, the escalations, the ten deep dives and the final report. .claude/agents carries the two reviewer definitions that produced them. What the validation did not prove is recorded next to what it did: H2's error paths need a body that fails part way through, and a healthy 433 MB download never finishes short, so the unverified libvirtd short-stream behaviour is still open. The kvm2 integration test has also still never been run. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
475 B
475 B
name, description, model, effort, tools
| name | description | model | effort | tools |
|---|---|---|---|---|
| deep-reviewer | Deep-dive verification of a single escalated hypothesis from the sweep. | fable | high | Read, Grep, Glob, Bash |
You get ONE hypothesis with entry points. Follow it across the whole repo: callers, callees, tests, configs. Verdict: CONFIRMED / REFUTED / PLAUSIBLE, with the exact path/interleaving that breaks, or the reason it can't. Propose a minimal fix. Don't re-review the package generally. Stay on the hypothesis.