chore(deps): bump mcp-toolsets-runtime to 0.4.2

[ciaransweet]

0.3.0 -> 0.4.2. Nothing breaking in between, so the pin moves to <0.5.0,>=0.4.2
and uv lock is the whole of the code change.

release	what it brought
0.4.0	mcp_agent.host — host helpers that import no UI framework
0.4.1	documentation only
0.4.2	the chat's tool step says what an @state:<key> handle resolved to

The README needed correcting

It claimed handle-path receipts are "rendered on neither side". True at 0.3.0;
0.4.2 changed it for the host side, so the tool step now annotates a handle with
the kind, the value's shape and the publishing tool.

It also gave one reason no receipt is visible in this repo. There are two, and
tagging a Kind alone would not have produced one:

• nothing tags a Kind, so no parameter is ever filled by declaration;
• the @state:<key> form is only offered on object and array parameters,
  and every tool here takes scalars — hello(name), whoami(),
  search_collections(query, limit), show_map(collection_id).

The example line in that section was generated by running step_input against a
simulated handle rather than written by hand.

Checked

./scripts/lint and ./scripts/test (18 passed) both clean, but neither covers
what the images install — the Dockerfiles sync dependency groups, not the main
deps. Both groups were synced into throwaway venvs:

• chat (Dockerfile.chat) — resolves 0.4.2, has mcp-agent-web and chainlit,
  mcp_agent.host imports;
• index (Dockerfile) — resolves 0.4.2, has mcp-serve, mcp-index,
  mcp-toolset.

mcp-agent install-elements re-run per CLAUDE.md: McpView.jsx is byte-identical
to 0.3.0's, so views are unaffected.

Note this redeploys every toolset — the bump lands in uv.lock, which is a
shared path.

🤖 Generated with Claude Code