[codex] Add Telegram timing and martingale policies

[LimiNode]

What changed

• Preserve Telegram date_ms through parsed signals/outcomes and into TradeSignal / TradeRequest as source timing metadata.
• Add a configurable live stale-signal guard and explicit martingale recognition rules.
• Add opt-in dispatch policies for all signals, first signal only, and strictly contiguous source-side steps.
• Stream exported JSONL through the archive parser smoke and print aggregate replay totals.

Safety semantics

• Unknown martingale_policy values fail configuration validation; they never fall back to ALL_SIGNALS.
• CONTIGUOUS_STEPS requires a fresh step 0. Only a validated later N+1 may bypass freshness.
• Intake is serialized through allocator/callback completion, with each contiguous step marked pending. Concurrent or re-entrant later steps cannot dispatch before their predecessor commits, and failed dispatch rolls back both dedupe and sequence state.
• Strategy suffixes such as COBRA -5 are never inferred as martingale steps. A source must opt in with a regex capture rule; configured markers normalize strategy names consistently for signals and outcomes.

Validation

• telegram_signal_parser_test: 28/28 passed.
• telegram_signal_bridge_test: 12/12 passed, including unknown policy, stale MG-0, delayed MG-1, concurrent intake, re-entry, and rollback regressions.
• telegram_archive_parser_smoke default replay passed.
• Local replay of a private 1000-message export: signals=463 outcomes=457 diagnostics=0 unparsed=80.
• bridge_umbrella_include_test passed with MinGW -Wa,-mbig-obj.

No credentials, session data, proxy configuration, raw archive, or build output are included.