chore(deps)!: bump mcp-toolsets-runtime to 0.8.0

[ciaransweet]

0.8.0 removes Kind and everything that resolved a parameter by type, and
lengthens a state key from <toolset>/<field> to <toolset>/<tool>/<field>.

No code changed. Nothing in this repo ever tagged a Kind, so the whole
cost was documentation — but it was a real cost, because the README explained
the old model at length and every state key it quoted is now wrong.

The pin

mcp-toolsets-runtime[web]<0.8.0,>=0.7.0 → <0.9.0,>=0.8.0, re-locked.
uv.lock is a shared build input, so merging redeploys all three toolsets and
the chat.

The README

Rewritten around what replaced Kind: the three-part key is the whole
contract — there is no type to agree on, the producer names the value and a
consumer names the same key — and NotAuthored is a constraint rather than a
type, saying only that a model must not write this value.

One claim in the old text was not merely stale but inverted. It said /health
reports state.produces as the list of distinct kinds, so the [] you see
means "nothing is tagged". Read off a running stac-explorer on 0.8.0:

"produces": [
  {"tool": "search_collections", "field": "collections",
   "state_key": "stac-explorer/search_collections/collections"},
  {"tool": "show_map", "field": "collection",  "state_key": "stac-explorer/show_map/collection"},
  {"tool": "show_map", "field": "tile_url",    "state_key": "stac-explorer/show_map/tile_url"}
],
"not_authored": []

produces is one entry per published data key and is not empty. not_authored
is the [], and that is the field meaning "nothing is tagged". The sample
handle annotation was obtained the same way rather than transcribed.

The paragraph explaining receipts on a parameter filled by declaration is
gone, because that path no longer exists — a value reaches a tool only because
the model wrote an @state: handle.

Checks

18 tests and ./scripts/lint clean against the published wheel, plus a live
mcp-serve for the /health shape above. The three per-toolset docker builds
are the ones that matter here: they catch 0.8.0 failing to resolve under
uv sync --package <toolset>, which the workspace venv cannot.

🤖 Generated with Claude Code