[UI] Surface translation confidence and WASM-sandboxed parser provenance in the dashboard

[grantfox-oss]

Problem

With both first-party blueprints and community-submitted WASM parsers able to produce a translated sentence, the dashboard currently has no way (per the README) to tell a user which mechanism produced a given sentence, or whether that parser is sandboxed/untrusted vs. an official blueprint. For a transparency tool, hiding the provenance of the translation itself is an odd blind spot.
Proposed work

Add a small badge/tooltip on each translated event indicating its source: Official blueprint, Community WASM parser (sandboxed), or Unrecognized — fallback.
For WASM-sourced translations, surface the execution result metadata already available from WasmSandboxRunner (e.g. execution time, success flag) in an expandable detail panel.
Link from the badge to the relevant blueprint/parser source file or registry entry where possible.

Acceptance criteria

All three provenance states render distinctly and correctly using realistic mock data for each case.
WASM-sourced events show real sandbox execution metadata, not placeholder text.
No UI regression for events that have no provenance metadata (e.g. very old cached events).

[Ebenezer199914]

i will love to work on this issue

[gloskull]

Hi, I’d love to work on this issue. I have 4 years of experience across backend, frontend, full-stack, and smart contract development. I understand the task clearly and can deliver a clean, efficient, well-tested solution on time, with strong focus on code quality and maintainability. My PR will be submitted in under 10 hours.