Memory Explorer lookup missing entity for Manoj github username

Current behavior

• During the GitHub issue creation flow, the agent triggers a Memory Explorer lookup for Manoj’s GitHub username.
• Memory Explorer returns no entity for Manoj (no username), so the assignee/mention lookup fails.
• Example conversation: https://app.getcore.me/home/conversation/a345fb3a-f8bf-49a1-92bf-c42edc3a0dde

Expected behavior

• Memory Explorer should return a Manoj entity with a resolvable github_username (or a clear ‘unknown’ state + next-step capture).
• The GitHub issue creation flow should be able to resolve Manoj’s GitHub username when it exists in memory, or reliably prompt/store it when missing.

Suggested implementation notes

• Inspect Memory Explorer indexing/ingestion path for contact entities and github_username attributes (creation, update, normalization).
• Verify the search query construction used by the GitHub issue creation flow (name variants, email -> username join, fuzzy match).
• Add instrumentation around: (1) entity lookup inputs, (2) search results, (3) fallback path when 0 results.
• If entity truly missing: add a capture step that stores github_username on the contact entity and re-tries resolution.

Acceptance criteria

• Given a memory store containing Manoj’s github_username, the lookup returns the correct entity/username.
• When Manoj is not present, the system records the missing-field state and provides a deterministic capture path (no silent failure).
• Add logs/metrics for 0-result lookups, including the query and any candidate matches.