agentdb-service.js uses dead pre-extraction relative imports (PR #152 Folge)

Bug

agentic-flow/dist/services/agentdb-service.js uses relative imports ../../../packages/agentdb/src/index.js (+ RVFOptimizer.js, factory.js, MutationGuard.js) that don't ship in the published npm package (only dist/ ships). After PR #152 extracted packages/agentdb to a dedicated ruvnet/agentdb repo as a git submodule, these paths are dead in npm installs.

Impact

AutopilotLearning.initialize() falls back to in-memory (agentdb-service catches the import failure silently). No published agentdb version (1.6.1 / 2.0 / 3.0-alpha) exports the expected names (AgentDB, RVFOptimizer, createBackend, MutationGuard) — they use a different controller API (createDatabase, ReflexionMemory, SkillLibrary, ReasoningBank).

Fix options

1. Ship packages/agentdb/src/ in the npm package, OR
2. Rewrite the 4 relative imports to use the published agentdb package API.

Context

Discovered while fixing ruflo autopilot learning. Workaround in ruflo: a ruflo-native learning adapter bypasses the broken path.

Start with agentic-flow/dist/services/agentdb-service.js and inspect its four relative imports into packages/agentdb/src/. Compare the expected exports with the published agentdb APIs, then determine which fix option fits the package layout. Done means AutopilotLearning.initialize() uses the intended AgentDB integration from an npm install instead of silently falling back to in-memory storage.