[enricopiovesan]

Summary

Traverse v0.16.2 is fully published (GitHub Release Latest Nov 4, all 6 crates, npm, Maven, NuGet at 0.16.2; swift-host, traverse-mcp, onnx-runner and runtime-wasm v0.16.2 releases). This PR brings the site up to it.

• Version currency to 0.16.2: home hero and JSON-LD, What ships today, quickstart, agents, MCP setup, CLI Q&A, llms.txt current packages.
• Changelog: new v0.16.2 entry (host-connector invokes in CLI workspace manifests, registry 0.31.0), Latest badge moved, arrow dropped from the "View all releases" button.
• #1772 flipped to shipped: Nov 5 blog "On main, not released" section is now "Shipped in v0.16.2" with a dated update; upgrade Q&A gets a "Then take v0.16.2" section.
• runtime.wasm: #1784 closed by #1797, so the BundleEmbedder Q&A now points at the runtime-wasm-v0.16.2 / v0.16.1 releases (digest checked locally, b313b5c5…). Related gap lines updated, with dated records kept.
• ONNX: current instructions move to onnx-runner-v0.16.2. All three 0.16.x runner releases have the same sha256 (ac5591fa…).
• Stale 0.15.0 sweep: unit-test, which-hosts exact-ref, Node.js, ExactModelHost, connector_invoke error and website-embedder Q&As. Run records stay "as of v0.15.0"; current-instruction lines move to 0.16.2.
• Known issue noted (on main, not released): native RuntimeTraverseEmbedder envelope fix #1800.
• New Q&A: Can a Traverse application manifest invoke a host connector? (Spec 1773; activate catalog gap #1791 noted.)
• Site dependency traverse-embedder-web ^0.16.2. The /discover execute panel's own runtime.wasm is still the v0.13.0 copy; the Q&A says so.

Validation

• npm run build (Node 22.23.4): 235 pages, sitemap includes the new Q&A.
• npm test: 11 pass, 0 fail.
• npx playwright test: 6 passed.
• No em dashes added; no arrows in new titles or buttons.