[longhn0710]

Stakeholders can now open demo/dashboard/index.html directly in a browser to demonstrate the database migration workflow, without a server, backend, npm or network access. The companion migration-report.html provides a formal six-page printable report.

The dashboard covers architecture, release/SQL provenance, GitHub validation, approval, DEV → SIT → UAT → MOCKPROD rollout, independent Oracle checks, evidence chain, happy/expected/failure/correction scenarios, before/after, retention and the ODC/Flyway boundary. Presentation controls, responsive cards, source badges and an evidence-backed decision make it suitable for a 2–3 minute demo.

Current evidence is preserved: implementation PR #1 is merged and its validation/report/CodeQL runs passed; the happy batch is 2000015 / APPROVING, with incomplete approval nodes, waiting stages and no post-migration Oracle acceptance. Failure and correction remain explicitly labelled fixtures. Historical retention proof is separate from the current batch. Authenticated Actions-to-ODC handoff and production rollout remain pending.

Generated JSON and both standalone HTML files share a sanitized snapshot. The read-only refresh command checks source hashes and provenance; it performs no ODC/Oracle acceptance, approval or execution. Rendering escapes data in text and attribute contexts; the browser regression verifies that hostile values cannot introduce HTML. Existing Markdown/JSON audit outputs remain available. The original dirty runtime worktree was preserved using an isolated worktree based on current main.

Validation:

• 42 local tests passed: 34 existing plus 8 dashboard evidence-integrity regressions.
• Three manifests validated; release packaging and happy/failure/correction fixture reports passed.
• Offline Chromium file:// checks passed with zero network requests, missing local links or JavaScript errors.
• Scenario/keyboard/presentation interactions and 390px mobile layout passed.
• Printed six-page A4 PDF inspected; dashboard, scenario, mobile and report screenshots recorded.
• actionlint, JavaScript syntax, repository document verification and diff checks passed.
• db-validate now verifies the standalone artifacts and recorded evidence hashes in CI.

Start at dashboard instructions. See visual acceptance and captured evidence. No runtime acceptance was expanded and no infrastructure was changed. Do not merge automatically.