Merge FlowChain private testnet setup package

Integrates the local/private FlowChain testnet package, one-command Windows setup, and guarded Base bridge POC after local validation and green CI.

Author: FlowmemoryAI

AGENTS.md

@@ -26,7 +26,7 @@ These instructions apply to every agent, assistant, script, and human operating
 - Use `docs/PR_PROCESS.md` for branch naming, draft PRs, merge order, dirty worktrees, and issue closing.
 - Use `docs/DAILY_HQ_RUNBOOK.md` for morning review, triage, monitoring, and handoff.
 - Use `infra/scripts/status-report.ps1` for read-only local worktree, PR, and issue status.
-- The immediate major milestone is the Rootflow V0 and Flow Memory V0 launch core. Do not reinterpret that as approval for production deployment.
+- The immediate major milestone is the FlowChain private/local L1 testnet package for second-computer validation, with Rootflow V0 and Flow Memory V0 kept green as the baseline. Do not reinterpret that as approval for production deployment.
 
 ## Engineering Rules
 

README.md

@@ -32,6 +32,17 @@ This repository contains the FlowMemory V0 foundation: project operating docs, l
 
 ## Start Here
 
+For a second computer or a non-technical local test, use the beginner setup
+guide:
+
+```powershell
+git clone -b release/flowchain-private-testnet https://github.com/FlowmemoryAI/FlowMemory.git
+cd FlowMemory
+powershell -ExecutionPolicy Bypass -File .\START_FLOWCHAIN_LOCAL.ps1
+```
+
+Detailed guide: `docs/EASY_SECOND_COMPUTER_SETUP.md`.
+
 Every contributor and agent should read:
 
 1. `AGENTS.md`
@@ -61,7 +72,7 @@ FlowMemory is managed as a multi-agent program. The management layer is part of
 - `docs/MARKETING_CLAIMS_GUARDRAILS.md`: allowed and blocked launch claims for docs and marketing
 - `infra/scripts/status-report.ps1`: read-only local worktree, PR, and issue status report
 
-Immediate major milestone: keep the Rootflow V0 and Flow Memory V0 launch core green. This means local contracts/tests, FlowPulse fixtures, Uniswap swap-derived memory-signal fixtures, Rootflow transitions, Flow Memory schemas, verifier reports, crypto fixtures, dashboard-readable state, Base Sepolia testnet read/deploy commands, and local smoke-test gates. It does not mean production deployment.
+Immediate major milestone: keep the Rootflow V0 and Flow Memory V0 launch core green while packaging the FlowChain private/local L1 testnet path for second-computer validation. This means local contracts/tests, FlowPulse fixtures, Uniswap swap-derived memory-signal fixtures, Rootflow transitions, Flow Memory schemas, verifier reports, crypto fixtures, dashboard-readable state, Base Sepolia testnet read/deploy commands, Windows-first wrapper scripts, and local smoke-test gates. It does not mean production deployment.
 
 Run the local launch-core path:
 
@@ -79,6 +90,31 @@ npm run launch:candidate
 
 That command runs contract hardening, the launch flow, runtime schema validation, fixture drift checks, and claim guardrails.
 
+Run the current FlowChain private/local wrapper path:
+
+```powershell
+npm run flowchain:prereq
+npm run flowchain:init
+npm run flowchain:start
+npm run flowchain:demo
+npm run flowchain:export
+```
+
+Run the merged-surface smoke path when Foundry, Python, dashboard dependencies,
+and crypto dependencies are installed:
+
+```powershell
+npm install --prefix apps/dashboard
+npm install --prefix crypto
+npm run flowchain:smoke
+```
+
+Run the existing dashboard as the local workbench:
+
+```powershell
+npm run workbench:dev
+```
+
 Build the dashboard after regenerating launch data:
 
 ```powershell

START_FLOWCHAIN_LOCAL.ps1

@@ -0,0 +1,67 @@
+param(
+    [switch]$SkipInstall,
+    [switch]$SkipSmoke,
+    [switch]$NoServers
+)
+
+$ErrorActionPreference = "Stop"
+
+Set-Location -LiteralPath $PSScriptRoot
+
+function Run-Step {
+    param(
+        [string]$Name,
+        [scriptblock]$Command
+    )
+
+    Write-Host ""
+    Write-Host "== $Name ==" -ForegroundColor Cyan
+    & $Command
+}
+
+Write-Host "FlowChain local/private testnet setup" -ForegroundColor Cyan
+Write-Host "This starts a local test package only. It is not production mainnet."
+
+if (-not $SkipInstall) {
+    Run-Step "Install root dependencies" { npm install }
+    Run-Step "Install dashboard dependencies" { npm install --prefix apps/dashboard }
+    Run-Step "Install crypto dependencies" { npm install --prefix crypto }
+}
+
+Run-Step "Check prerequisites" { npm run flowchain:prereq }
+Run-Step "Initialize local state" { npm run flowchain:init }
+Run-Step "Start bounded local stack" { npm run flowchain:start }
+Run-Step "Run deterministic demo" { npm run flowchain:demo }
+
+if (-not $SkipSmoke) {
+    Run-Step "Run full local smoke" { npm run flowchain:smoke }
+}
+
+Run-Step "Export local bundle" { npm run flowchain:export }
+Run-Step "Run bridge mock" { npm run bridge:mock }
+
+if (-not $NoServers) {
+    Write-Host ""
+    Write-Host "Starting control plane and dashboard in separate PowerShell windows..." -ForegroundColor Cyan
+
+    Start-Process powershell.exe -ArgumentList @(
+        "-NoExit",
+        "-ExecutionPolicy",
+        "Bypass",
+        "-Command",
+        "Set-Location -LiteralPath '$PSScriptRoot'; npm run control-plane:serve -- --host 127.0.0.1 --port 8675"
+    )
+
+    Start-Process powershell.exe -ArgumentList @(
+        "-NoExit",
+        "-ExecutionPolicy",
+        "Bypass",
+        "-Command",
+        "Set-Location -LiteralPath '$PSScriptRoot'; npm run workbench:dev"
+    )
+}
+
+Write-Host ""
+Write-Host "FlowChain local setup completed." -ForegroundColor Green
+Write-Host "Dashboard usually opens at http://127.0.0.1:5173/"
+Write-Host "Control plane listens on http://127.0.0.1:8675/ when the server window is running."

apps/dashboard/README.md

@@ -1,6 +1,6 @@
-# FlowMemory Dashboard V0
+# FlowMemory Dashboard / FlowChain Workbench V0
 
-Local operator/explorer app for inspecting FlowMemory V0 fixture output. It is intentionally fixture-backed and does not claim production live data, wallet support, token pricing, or hosted deployment.
+Local operator/explorer app for inspecting FlowMemory V0 fixture output and the FlowChain private/local testnet workbench surface. It is intentionally local-first and does not claim value-bearing wallet support, token pricing, or hosted deployment.
 
 ## Run Locally
 
@@ -25,6 +25,28 @@ npm test
 npm run build
 ```
 
+From the repo root, the same checks are:
+
+```powershell
+npm test --prefix apps/dashboard
+npm run build --prefix apps/dashboard
+```
+
+The first route is the FlowChain workbench. It tries the local control-plane API at:
+
+```text
+http://127.0.0.1:8787
+```
+
+Override that endpoint when needed:
+
+```powershell
+$env:VITE_FLOWCHAIN_CONTROL_PLANE_URL="http://127.0.0.1:8787"
+npm run dev
+```
+
+If the API is not running, the workbench marks the control-plane as offline, shows stale fixture fallback where appropriate, and keeps rendering deterministic local data. This app is for private/local validation and canary review only; it does not initiate value-bearing wallet flows.
+
 ## Data Boundary
 
 The canonical dashboard fixture is generated by the launch-core command and lives at:
@@ -33,13 +55,27 @@ The canonical dashboard fixture is generated by the launch-core command and live
 fixtures/dashboard/flowmemory-dashboard-v0.json
 ```
 
+The guarded Base canary review fixture is separate:
+
+```text
+fixtures/dashboard/flowmemory-dashboard-base-canary-v0.json
+```
+
 The app loads its runtime copy from:
 
 ```text
 apps/dashboard/public/data/flowmemory-dashboard-v0.json
+apps/dashboard/public/data/flowmemory-dashboard-base-canary-v0.json
 ```
 
-The `dev` and `build` scripts run `npm run sync:fixtures`, which copies the canonical fixture into the Vite public data folder before the app starts or builds.
+The `dev` and `build` scripts run `npm run sync:fixtures`, which copies the canonical dashboard fixture and the existing launch-core devnet state into the Vite public data folder before the app starts or builds.
+
+Workbench fixture fallback paths:
+
+```text
+apps/dashboard/public/data/flowchain-local-devnet-state.json
+apps/dashboard/public/data/flowchain-local-devnet-dashboard-state.json
+```
 
 Generated local source outputs land under the fixture boundary first:
 
@@ -54,7 +90,9 @@ fixtures/dashboard/generated/hardware-heartbeats.json
 
 ## Current Views
 
+- FlowChain workbench
 - Overview
+- Base canary review
 - Flow Memory / Rootflow
 - FlowPulse stream
 - Rootfields
@@ -67,6 +105,16 @@ fixtures/dashboard/generated/hardware-heartbeats.json
 
 Every displayed record carries source subsystem, fixture/local origin, chain context, ID/hash, status, and last-updated metadata when available.
 
+The workbench adds local setup/API status plus object views for blocks, transactions, agents, models, receipts, memory cells, artifacts, verifier reports, challenges, finality, provenance, and raw JSON. When a current fixture does not yet contain a private-testnet object type, the view stays empty and names the expected control-plane endpoint.
+
+Workbench object coverage:
+
+```text
+node/chain status, blocks, transactions, rootfields, agents, models, work receipts,
+memory cells, artifacts, verifier modules, verifier reports, challenges, finality,
+provenance/source, hardware signals, raw JSON
+```
+
 ## Status Vocabulary
 
 Dashboard V0 visually distinguishes: