docs(site): v0.14.0 truth-pass (llms, exact-ref, current pins)

[enricopiovesan]

Summary

Afternoon CEO truth-pass after eng cut Traverse v0.14.0 (CloudAgents exhausted — shipped locally).

Changes

• EDIT public/llms.txt — intro + Current packages → 0.14.0 / registry =0.25.0; exact-ref blurb for signed schema 2.0.0 + digits-mlp test-key + native+web only
• EDIT questions/what-is-exact-ref-model-execution.astro — signed packages, host-owned trust, digits-mlp caveat, host honesty
• EDIT current-state pins (what-is-real-today, Footer, system, platforms, consumers Q&A, quickstart, faq, about, roadmap, concepts, index, production-ready, what-is-traverse)
• EDIT changelog.astro — add v0.14.0 Latest; keep v0.13.0 historical entry
• EDIT package.json + lock — traverse-embedder-web@^0.14.0

Not in this PR

• Historical blog facts (same-wasm v0.13.0, exact-ref v0.12.0 blog) left alone
• weekly-demos visibility (.github#30 — owner)
• Dependabot left alone

Related

• Product Release: https://github.com/traverse-framework/traverse/releases/tag/v0.14.0
• Announcement: https://github.com/orgs/traverse-framework/discussions/1576

[enricopiovesan]

CI note: bumped traverse-embedder-web to 0.14.0 briefly; node --test failed because ExactModelBrowserHost now requires signed schema 2.0.0 single wasm-cpu pins + host trust roots (model_incompatible on the discover-generate fixture). Reverted the site dependency to @0.13.0 so discover keeps working. Public docs/llms.txt still pin published crates/npm at 0.14.0 / registry =0.25.0. Follow-up (not this PR): migrate discover-generate fixture to signed exact-ref.