fix(auto-recall): respect recall.maxResultsDefault config instead of hardcoding 10

[octo-patch]

Fixes #1514

Problem

The auto-recall before_prompt_build hook hardcodes maxResults: 10 for both local and Hub memory searches, ignoring the user-configured recall.maxResultsDefault value. This means users who set a lower limit (e.g. 3 or 5) to reduce token consumption still get up to 10+10 candidates fetched on every turn.

Solution

Read ctx.config?.recall?.maxResultsDefault ?? DEFAULTS.maxResultsDefault (default: 6) and use it for both the local engine search and Hub search calls.

const arMaxResults = ctx.config?.recall?.maxResultsDefault ?? DEFAULTS.maxResultsDefault;
const arLocalP = engine.search({ query, maxResults: arMaxResults, ... });
const arHubP = ctx.config?.sharing?.enabled
  ? hubSearchMemories(store, ctx, { query, maxResults: arMaxResults, ... })
  ...

Testing

• Configured recall.maxResultsDefault: 3 in plugin config; verified auto-recall now fetches at most 3 results from local search instead of 10.
• Default behavior (no config set) uses DEFAULTS.maxResultsDefault (6), unchanged from existing behavior intent.