fix(memory): wire LearningBridge into intelligence module (WM-013)

[invidias-codem]

Summary

Fixes #1213

LearningBridge was exported from @claude-flow/memory but never instantiated at runtime inside intelligence.ts (compiled: dist/src/memory/memory-initializer.js). Config keys learningBridge.sonaMode, confidenceDecayRate, accessBoostAmount, and consolidationThreshold were read by WM-007b but never wired to an actual LearningBridge instance, leaving confidence decay, trajectory tracking, and pattern consolidation as dead code.

Changes

Following the WM-011 (ReasoningBank) initialization pattern:

Op	Target	Change
WM-013a	intelligence.ts	Add let _learningBridge: any | null = null; module-level variable after reasoningBank
WM-013b	intelligence.ts	Instantiate LearningBridge after ReasoningBank init block, reading config from finalConfig.learningBridge.*
WM-013c	intelligence.ts	Export getLearningBridge() getter function

Additional:

• Add optional learningBridge? field to SonaConfig interface
• Add learningBridgeEnabled: boolean to IntelligenceStats
• Update initializeIntelligence() return type to surface learningBridgeEnabled
• Call _learningBridge.destroy() inside clearIntelligence() to flush active trajectories before teardown

Implementation Notes

@claude-flow/memory is not a direct dependency of @claude-flow/cli, so LearningBridge is loaded via dynamic import (same optional-peer pattern that LearningBridge itself uses internally for @claude-flow/neural). The backend is resolved through ControllerRegistry via memory-bridge.js. When either is unavailable, _learningBridge stays null and all paths degrade gracefully — no change in behavior for environments without @claude-flow/memory installed.

Testing

Existing learning-bridge.test.ts covers the LearningBridge class API. The wiring in intelligence.ts degrades silently when the package is absent, so no new required tests — but a follow-up integration test (checking getLearningBridge() !== null after initializeIntelligence({ learningBridge: { enabled: true } }) in a full install) would be a useful addition.

Related

• Bug: ReasoningBank not instantiated — pattern-store/search hooks use generic memory instead of ReasoningBank #1210 — WM-011 wires ReasoningBank (pattern this follows)
• Bug: 12 config.json keys written during init are never consumed at runtime #1204 — WM-007 reads learningBridge config keys
• Bug: HybridBackend doesn't proxy recordFeedback/verifyWitnessChain to AgentDBBackend #1212 — WM-012 adds HybridBackend proxy methods