[codex] Add FlowRouter control-plane signal handoff

[FlowmemoryAI]

Summary

• extend the FlowRouter simulator with control-plane-ready hardware/operator signal handoff fixtures
• add bridge alert and negative validation schemas/fixtures
• add PowerShell wrappers for deterministic fixture generation and simulator smoke

Validation

• powershell -NoProfile -ExecutionPolicy Bypass -File hardware/simulator/flowrouter-smoke.ps1
• git diff --check

Notes

This is local/private testnet support only. Hardware remains optional and does not gate the full smoke path.

HQ Required Review Metadata (2026-05-14)

Issue status: Refs #105
Worktree / branch ownership: E:\FlowMemory\flowmemory-hardware
Allowed folders: hardware/, fixtures/hardware/, schemas/flowmemory/hardware-control-plane-handoff.schema.json
Forbidden folders: crates/, services/, crypto/, contracts/, apps/dashboard/, unrelated infra/docs
Exact checks recorded:

• powershell -NoProfile -ExecutionPolicy Bypass -File hardware/simulator/flowrouter-smoke.ps1; git diff --check; 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 CLEAN; PR body metadata now present, but merge after control-plane/dashboard labels are stable unless fixture-only.

[FlowmemoryAI]

HQ review blocker, 2026-05-14: before merge readiness review, please update the PR body to include linked issue #105, allowed folders, forbidden folders, worktree path, and exact checks run with results. Current changed files appear to be hardware fixtures/simulator/docs plus the hardware handoff schema, but the PR body needs to make that scope and the local evidence explicit, including git diff --check.

[FlowmemoryAI]

HQ overlap note: PR #117 and PR #139 both target #105 and touch the hardware/operator-signal fixture lane (hardware/, ixtures/hardware/, schemas/flowmemory/hardware-control-plane-handoff.schema.json). Do not merge both independently. Pick the current successor, close/supersede the other, or explicitly rebase/reconcile so only one reviewed hardware-signal delta lands.