fix: hybridSearch at INIT_LEVELS Level 1 depends on Level 2 vectorBackend

[sparkling]

Bug

hybridSearch is initialized at Level 1 in INIT_LEVELS. Its factory calls this.get('vectorBackend'), but vectorBackend is not initialized until Level 2. Result: hybridSearch always receives null for its vector backend, silently falling back to degraded behavior.

Impact

HybridSearchController never gets a real vector backend during normal startup. BM25+HNSW fusion search is non-functional.

Fix

Move hybridSearch from Level 1 to Level 3 (after vectorBackend completes at Level 2). Single-line change in INIT_LEVELS.

Note: This fix is identified but not yet applied — tracked for next implementation pass.

ADR Reference

ADR-0076 Track B, identified by controller architect and PR strategist

[sparkling]

Fixed in 29437fcdd.

hybridSearch moved from Level 1 to Level 3 in INIT_LEVELS so that its factory (which calls this.get('vectorBackend')) runs after Level 2 initializes the vectorBackend controller. Before: Level 1 factory always saw vectorBackend === null and silently fell back to this.agentdb. After: proper hybrid search wiring.

Verified by 6-agent fix swarm (2026-04-15).