[codex] Expand FlowChain workbench live console

[FlowmemoryAI]

What changed

• Expanded the existing dashboard workbench to probe the local control-plane API via /health, /state, and a read-only /rpc batch.
• Added workbench views for peers, mempool, accounts, balances, faucet events, wallet public accounts, verifier modules, bridge test-lane records, hardware signals, and raw control-plane JSON alongside the existing lifecycle views.
• Added API-gated action cards for refresh, local faucet request, sample transaction, and bridge test-deposit inspection; submit/inspect actions remain disabled unless the control plane advertises matching local-only methods.
• Synced the deterministic bridge mock deposit into dashboard public data and updated dashboard docs/README boundaries.

Why

The workbench should feel like a real local chain console for second-computer validation without claiming production mainnet, real funds, wallet custody, or production bridge readiness.

Checks

• npm test --prefix apps/dashboard
• npm run build --prefix apps/dashboard
• npm run flowchain:smoke after installing missing root and crypto dependencies
• git diff --check
• Local HTTP verification: Vite workbench responded on http://127.0.0.1:5177/; control-plane /health and /state responded on http://127.0.0.1:8788/ because port 8787 was already occupied by an existing node process whose /state returned 404.

Notes

• npm run flowchain:full-smoke is not present in the current root package.json; npm run flowchain:smoke is the available full merged-surface smoke wrapper.
• Browser screenshot verification was not available because the in-app browser Node REPL tool was not exposed in this session.

HQ Required Review Metadata (2026-05-14)

Issue status: Original #102 lane is closed on GitHub; needs new/open issue if work remains
Worktree / branch ownership: E:\FlowMemory\flowmemory-dashboard
Allowed folders: apps/dashboard/, docs/DASHBOARD_MVP.md
Forbidden folders: crates/, services/, crypto/, contracts/, hardware/, unrelated docs/infra
Exact checks recorded:

• npm test --prefix apps/dashboard; npm run build --prefix apps/dashboard; npm run flowchain:smoke after installing missing root and crypto dependencies; git diff --check; local HTTP verification on Vite/control-plane endpoints; GitHub CI checks listed below.
• GitHub CI Repository hygiene: SUCCESS
• GitHub CI Contracts: SUCCESS
• GitHub CI Services and launch core: SUCCESS
• GitHub CI Launch-core acceptance command: SUCCESS
• GitHub CI Crypto: SUCCESS
• GitHub CI Dashboard: SUCCESS
• GitHub CI Local devnet: SUCCESS
• GitHub CI Hardware POC: SUCCESS
  HQ readiness: Draft; merge state DIRTY; close as superseded or refresh against current main and a new/open issue.

[FlowmemoryAI]

HQ review note, 2026-05-13: this draft matches the #102 dashboard/workbench lane and stays in apps/dashboard plus docs/DASHBOARD_MVP. Please link issue #102 in the PR body before merge. Merge order: after #111 lands or rebase onto it, because #111 adds the root flowchain:full-smoke command that this PR currently notes as missing; also coordinate with #101 so API-gated actions only enable when matching local-only control-plane methods exist. Main review focus: no browser private-key handling, no production/mainnet or real-funds UX claims, and no second dashboard surface.

[FlowmemoryAI]

HQ review blocker, 2026-05-14: before merge readiness review, please update the PR body to name the linked issue, allowed folders, forbidden folders, worktree path, and exact checks run. Current changed files appear to stay in apps/dashboard/ plus docs/DASHBOARD_MVP.md, but the PR body needs to say that explicitly and list the local dashboard/workbench checks with results.

[FlowmemoryAI]

HQ reconciliation note, 2026-05-14: GitHub now shows linked dashboard/workbench issue #102 as closed. Before merge review, please either close this draft if it was superseded by merged main, or refresh the PR body with the exact remaining delta and a new/open issue reference for anything still needed.