[codex] Add launch contract event spine

[FlowmemoryAI]

What changed

• Added a generated contractEvent spine to MemorySignals so each signal records IFlowPulse.FlowPulse event semantics, topic0 matching, pulse type names, indexed fields, payload fields, and receipt-derived locator fields.
• Added contractEventRef to RootflowTransitions so transition output traces back to the contract event behind the MemorySignal.
• Updated canonical schemas, generated launch-core fixtures, dashboard runtime data, and tests for the new contract-event linkage.
• Polished the Flow Memory / Rootflow dashboard route with a launch summary, contract-event spine, transition status counts, rootfield bundle summary, and agent warning panel.
• Added a decision record and boundary-claims audit to keep V0 language honest.

Why

The launch-core path needed to show the concrete bridge from contract events to Flow Memory outputs without implying contracts know receipt-only fields such as txHash or logIndex during execution.

Validation

• npm run launch:v0
• npm test
• npm run e2e
• npm test --prefix services/flowmemory
• npm test --prefix apps/dashboard
• npm run build --prefix apps/dashboard
• Browser smoke check at http://127.0.0.1:5173/#/flowmemory with zero console errors
• forge test
• cargo test --manifest-path crates/flowmemory-devnet/Cargo.toml
• npm test, npm run validate:vectors, and python validate_test_vectors.py in crypto/
• python hardware/simulator/flowrouter_sim.py --validate-file hardware/fixtures/flowrouter_sample_seed42.json

Boundaries

Still local/test V0 only. This does not claim production L1 readiness, Base mainnet readiness, production Uniswap v4 deployment, full trustless verification, free storage, AI running on-chain, or production hardware readiness.