fix(memory): emit real scoringTimeMs + vectorSearchTimeMs diagnostics

Previously these fields were hardcoded to 0 in three places
(CognitiveMemoryManager.retrieve success + weak-hit paths, plus
an AgentMemory shim). The shim's zero is correct (standalone
Memory doesn't separate stages), but the cognitive path was
lying.

Fix: MemoryStore.query now returns a timings object with
vectorSearchMs (wall time around the vectorStore.query loop) and
scoringMs (wall time around scoreAndRankTraces + detectPartiallyRetrieved).
CognitiveMemoryManager threads these into diagnostics instead of 0.

agentos-bench latencyBreakdown.scoring no longer reports n=0 for
every case.

Author: jddunn

dist/memory/CognitiveMemoryManager.d.ts.map

@@ -72,6 +72,15 @@ export declare class MemoryStore {
     query(queryText: string, currentMood: PADState, options?: CognitiveRetrievalOptions): Promise<{
         scored: ScoredMemoryTrace[];
         partial: PartiallyRetrievedTrace[];
+        /**
+         * Per-stage wall-clock timings. Surfaced so
+         * {@link CognitiveMemoryManager} can populate its diagnostics
+         * with real numbers instead of the former 0-placeholder.
+         */
+        timings: {
+            vectorSearchMs: number;
+            scoringMs: number;
+        };
     }>;
     /**
      * Record that a memory was accessed (retrieved).