0.6.3 — bl_graph_evidence takes run_ref

Fixed

bl_graph_evidence advertised the wrong argument name.

Its published MCP schema said run_id, while bl_graph_terminal_runs returns the address as run_ref, the documentation says to pass run_ref, and the resolver wants the directory name. A consumer reading the tool schema would pass the run's identity — which does not resolve, because a run usually lives in a directory named something else.

The tool did the right thing under the wrong name. The argument is now run_ref.

Nothing else moved: no change to resolution behaviour, evidence shape, contract id, trust semantics, or terminal-run handling. bounded-loops.dev/slm-bridge/v1 is unchanged, and a consumer branching on the contract id rather than the version is unaffected either way.

Two tests were added — one asserts the real registered signature rather than the docstring, the other performs the round trip a consumer actually makes: whatever the listing returns as run_ref must work as the fetch argument. That round trip is what would have caught this before publication.

Found by the SuperLocalMemory 4.0.4 bridge audit.

Verification

3338 passed, 15 skipped. ruff and mypy clean.