fix: audit and correct the compare pages — real APIs, valid HTML, honest examples

[enricopiovesan]

Summary

Follow-up to the content restructure (#34, #35), which only touched one overclaiming table row per compare page during the sitewide AI-pipeline sweep. Went back and gave all three /compare/* pages the full audit — these are exactly the pages a skeptical technical evaluator reads closest, so they deserved the same scrutiny as everything else.

Fabricated code samples

All three pages had "integration" code importing a package that has never existed — @traverse-framework/runtime — with an invented TraverseRuntime.init() / .execute() API. Anyone who copied any of these would hit a wall immediately.

• vs-function-calling: the "using them together via MCP" section invented a hand-rolled MCP tool wrapper. The real story is simpler and better — traverse-mcp -- stdio already exposes every governed capability as an MCP tool, no wrapper code needed. Replaced with the real invocation and a link to /agents.html. Also fixed an example contract whose placement array listed ai-pipeline as a valid value.
• vs-microservices: replaced the fake Rust sample with the real traverse-embedder crate API (BundleEmbedder::init, .submit, .subscribe).
• vs-serverless: the sample was a Cloudflare Worker — i.e. edge, a placement Traverse hasn't shipped, making the whole example unverifiable. Reframed as a Rust AWS Lambda handler using the same real traverse-embedder crate, which sidesteps the edge-WASM question entirely by just being an ordinary Rust process.

Malformed HTML

All three pages' CTA bands had a stray </section> landing mid-block (evidently copy-pasted from one page to the next), closing the section early and leaving the button row and final closing tags orphaned outside it. Browsers silently recover from this kind of thing, so it happened to render fine by accident — but it's invalid structure. Fixed the tag order in all three so the section closes where the markup says it does.

Test plan

• npm run build clean after each of the three edits (caught nothing this time — no repeat of the escaping bug from feat: content restructure phase 2 — remove Solutions/Use-cases, honest sitewide language #35)
• Verified rendered dist/ output: all three CTA bands close correctly, both buttons present and visible, real API names (BundleEmbedder, traverse_embedder, lambda_runtime) present in the rendered code samples, zero remaining references to the fabricated TraverseRuntime/@traverse-framework/runtime anywhere in src/
• Browser-verified all three pages: CTA band dimensions/buttons, terminal block on vs-function-calling shows the real command, no console errors

🤖 Generated with Claude Code