V2 P2: Memory abstention + KnowledgeGap detection

[cursor]

Background

V2 Enhancement 7: Cortex must say when it lacks reliable information.

Problem Statement

Low-confidence retrieval still forces a match; gaps are not aggregated; coverage_score UI field is unused (#62).

Proposed Solution

• Typed abstention (e.g. INSUFFICIENT_EVIDENCE) with missing[] and next_action
• KnowledgeGap nodes: domain, gap_type, frequency, coverage_score
• Gap types: MISSING_KNOWLEDGE, STALE_KNOWLEDGE, CONTRADICTORY_KNOWLEDGE, …
• Wire into reliability gate; MCP cortex_get_gap
• Implement / align with Phase 8: Implement coverage scorer on /query and MCP inject #62 coverage scorer

Acceptance Criteria

• Low-confidence path can abstain with reasons
• Gaps aggregate across repeated requests
• Coverage reporting by domain/system
• Gate consumes gap data

Related

#62 coverage scorer

Plan ref

todo p2-later — V2 Enhancement 7