Report recall truncation and provide complete task discovery #215

Observed on 2026-09-13: WordsApp task_list returned all 13 open tasks (20 through 32), but memory_recall listed only 20 through 31, even with maxChars=26000, without an explicit task-section omission notice. The generic memory_search hint does not provide task discovery.

Implementation idea:

• Inspect fixed task caps and budget selection. Return authorized total/included counts and hasMore/truncated metadata per section, with a concrete task_list or paged continuation instruction.
• Preserve the strict budget and deterministic selection; reserve space for omission notices.
• Coordinate sorting/paging with #116 and task visibility with #210. Recall need not contain every task.

Acceptance criteria:

• Fixtures at 0, 12, 13 and large task counts clearly distinguish complete and partial results.
• Small budgets retain an omission notice and usable retrieval path.
• Counts/continuations leak no inaccessible tasks; stable pages have no missing or duplicate visible tasks.
• Tool documentation identifies recall as a summary and task_list as the authoritative discovery path.

Memory-MCP reproduction (2026-09-13)

The freshness audit returned 30 active tasks from task_list but only 11 from a large-budget recall. MemoryTools.AppendTasks applies both Take(12) and about 1,200 characters, so raising the overall budget cannot reveal the rest. Newer tasks #197-#212 were omitted without a task-specific continuation notice. Add a long-title fixture that truncates before twelve entries, and ensure the notice points to task_list, not memory_search.