SIF-005: add an optional web dashboard for execution history and diagnostics

[jmrpineda]

Reported by: codex
Requested by: jmr.pineda
Priority: P3
Affected surfaces: execution history, diagnostics UX, optional hosted or local web surfaces
Constraints: dashboard work must remain optional and must not become a hard dependency for the core runtime

Summary

Add an optional web dashboard to inspect execution history and diagnostics across runs without changing the core local-first runtime model.

Problem / opportunity

Execution information already exists in local artifacts, but cross-run diagnostics and history review are still file-centric. A dashboard would improve discoverability and comparison for teams that need a richer inspection surface.

Requested behavior

Users should be able to browse execution history and diagnostics through an optional web dashboard while keeping the YAML runtime and local artifact model intact.

Scope

• In scope: run history browsing, diagnostic drill-down, optional deployment or local hosting path.
• Out of scope: replacing the CLI/runtime with a dashboard-first product.

Acceptance criteria

1. Users can inspect multiple runs and their diagnostics from a web surface.
2. The dashboard remains optional and does not block core CLI usage.
3. The data model stays aligned with existing execution artifacts or equivalent persisted run data.

Notes

• Source: local roadmap at .doc/positioning-and-roadmap.md.
• This issue was created while migrating local backlog ownership to GitHub.