Propose the checks that verify a code change
plan_verificationProposes which existing Recovery Probe checks verify a Git change by matching changed files and suspects against the scenario registry; it runs nothing and returns a plan, not a verdict.
Instructions
Experimental. Before recording a baseline, proposes which existing Recovery Probe checks verify a change: it matches the files changed since a Git reference (committed, staged, unstaged, untracked, deleted, renamed) against the project scenario registry (recovery-probe.registry.json) and the suspects on the changed lines. Each check says which file selected it, what it checks, where its expectation came from and what it does not cover. It also lists suggestions to review, changed files with no known check, and what needs a person: open questions, missing expectations, invalid entries. It runs nothing. The result is a proposal, never a verdict: no matching check does not mean the change is safe. Resolve needsInput, then record the baseline with verify_change from the version before the change.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "plan_verification"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| base | No | The Git reference the change starts from. | main |
| runs | No | Runs of each check on each side in the candidate plan. Default: 3. | |
| task | No | What the change is for, kept in the report as given. | |
| force | No | Replace an existing plan file. Only after reviewing it. | |
| write | No | Write the candidate verify plan to this relative path, such as .recovery-probe/verify.json. | |
| registry | No | The scenario registry, relative to the working directory. Default: recovery-probe.registry.json. | |
| expectations | No | Expected behavior, and where it comes from, for registry scenarios that state none, by scenario name. Only what the user said; never invent one. |