[codex] Build bridge relayer credit handoff smoke

[FlowmemoryAI]

Summary

• Adds bridge relayer support for decoded BaseBridgeLockbox.BridgeDeposit logs from mock fixtures, local Anvil, and explicit Base Sepolia RPC ranges.
• Produces deterministic BridgeObservation, BridgeCredit, test-mode withdrawal intent, replay keys, and a runtime handoff at fixtures/bridge/local-runtime-bridge-handoff.json.
• Adds bridge schemas, guarded Sepolia/Anvil observe wrappers, bridge:local-credit:smoke, and flowchain:full-smoke command wiring.
• Updates bridge docs to keep the lane test-only and explicit about no real release or production bridge claim.

Scope

Allowed folders touched: services/bridge-relayer/, schemas/flowmemory/bridge-*.schema.json, fixtures/bridge/, infra/scripts/bridge-*.ps1, package.json, and docs/bridge/.

Forbidden folders were not edited in the final commit. npm run flowchain:full-smoke refreshed generated dashboard/launch artifacts during verification; those worktree changes were restored before pushing.

No GitHub issue number was provided in the goal; this PR is scoped to the bridge-agent mission prompt.

Validation

• npm run bridge:test
• npm run bridge:mock
• npm run bridge:local-credit:smoke
• forge test --match-path tests/bridge/BaseBridgeLockbox.t.sol
• npm test
• npm run flowchain:full-smoke
• git diff --check

Risk / Follow-ups

• Base Sepolia observation is read-only and requires explicit RPC URL, lockbox, and block range; no private key is required.
• Runtime/control-plane bridge intake is not merged in this scope, so the bridge writes the deterministic handoff file for the runtime agent to consume.
• Withdrawal records are test-mode intents only and never broadcast a release transaction.

HQ Required Review Metadata (2026-05-14)

Issue status: Refs #104
Worktree / branch ownership: E:\FlowMemory\flowmemory-bridge-full
Allowed folders: services/bridge-relayer/, schemas/flowmemory/bridge-.schema.json, fixtures/bridge/, infra/scripts/bridge-.ps1, package.json, docs/bridge/
Forbidden folders: crates/, apps/dashboard/, crypto/ except bridge schema coordination, hardware/, unrelated contracts/
Exact checks recorded:

• npm run bridge:test; npm run bridge:mock; npm run bridge:local-credit:smoke; forge test --match-path tests/bridge/BaseBridgeLockbox.t.sol; npm test; npm run flowchain:full-smoke; 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 DIRTY; add explicit [bridge] Build test bridge observation and local credit path #104 linkage and coordinate with [codex] harden bridge lockbox settlement spine #110/[codex] add FlowChain local wallet envelopes #115 schema ownership.

[FlowmemoryAI]

HQ review note, 2026-05-13: this draft matches the #104 bridge lane and its CI is passing. Please link issue #104 in the PR body before merge. Merge order: after #111 lands, then after #110's bridge/settlement event schema is accepted; coordinate with #114 if local API bridge intake is required. Main review focus: schema/event compatibility with #110, runtime handoff shape for #99/#101, explicit Base Sepolia ranges, no private-key requirement for reads, and no production bridge or real-funds default path.

[FlowmemoryAI]

HQ review blocker, 2026-05-14: before merge readiness review, please add a dedicated Checks run section with exact local commands and results, including git diff --check. The PR already names allowed and forbidden folders; it also still needs explicit issue linkage to #104 in the PR body.