fix: WebMCP execution input compatibility for v0.5.1

[TueJon]

Summary

• adapt the verification template and visual Workbench to current object-shaped executeTool() input
• preserve Chrome 150 JSON-string compatibility with a temporary side-effect-free probe
• invoke every real application tool exactly once; update ambient types, proof, docs, manifests, changelog, and v0.5.1 notes

Evidence

• WebMCP CG draft 97da8f5: optional any input object
• Chrome imperative guide updated 2026-09-11: object input; JSON strings deprecated from Chrome 155
• WPT commits 1a21db90ad and c94abb33b8 cover object input and object-shaped enumerated schemas
• official webmcp-tools PR #447 moved to object input with legacy compatibility

Verification

• npm run check — 43/43
• npm run workbench:verify — Chromium desktop/mobile/native/CSP gates pass
• npm run proof:verify — native Chrome 150, detected JSON-string mode, UI delta/invalid input/cleanup pass
• npm audit --omit=dev — 0 vulnerabilities

No merge, tag, release, package publication, or directory mutation is part of this PR.

[TueJon]

skills/webmcpify/templates/webmcp.spec.ts:71 and skills/webmcpify/references/verify.md:76 — the remaining runner guidance still says native getTools() always returns a stringified inputSchema, while this release correctly documents and supports object-shaped schemas in current native implementations. The shipped parsing logic already handles both shapes, so this is non-blocking, but these comments can mislead agents adapting the template.

Closure checklist:

• Update the listTools comment in skills/webmcpify/templates/webmcp.spec.ts to describe older-string/current-object compatibility.
• Update the LLM-runner bullet in skills/webmcpify/references/verify.md to say native inputSchema may be either shape.

[TueJon]

Resolved the documentation-consistency caveat at b8a4881:

• skills/webmcpify/templates/webmcp.spec.ts now describes older-string/current-object schema compatibility.
• skills/webmcpify/references/verify.md now documents both native inputSchema shapes.

Verification: npm run check passes all 43 tests; the stale native-string-only wording is absent repo-wide.

[TueJon]

No blocking findings. The prior two-item schema-shape documentation checklist is fully closed, with no regression in the compatibility adapter or release surfaces.
Verified with npm run check (43/43), native Chrome 150 proof, and the Workbench browser matrix.