Skip to content

Return an explicit empty Memory recall reason - #25

Merged
hamzamerzic merged 2 commits into
mobius-os:mainfrom
hamzamerzic:fix/explicit-empty-recall
Jul 29, 2026
Merged

Return an explicit empty Memory recall reason#25
hamzamerzic merged 2 commits into
mobius-os:mainfrom
hamzamerzic:fix/explicit-empty-recall

Conversation

@hamzamerzic

Copy link
Copy Markdown
Contributor

Summary

  • add the stable no_relevant_result reason to structured receipts whose status is empty
  • keep empty lookup as a successful outcome and preserve the existing human-readable answer
  • make the Python test suite runnable directly without a caller-supplied import path
  • bump the app version to 2.2.3

Context

This is a compatible follow-up to #14, which introduced structured hit/empty/failed outcomes, and #23, which added safe failure reasons. Unlike failure reasons, no_relevant_result describes a successful lookup that selected no notes; older consumers continue to rely on status: empty and may ignore the additive field.

Validation

  • pytest -q --tb=short (83 passed)

Co-authored-by: Möbius Agent <mobius-agent@users.noreply.github.com>
@hamzamerzic hamzamerzic added the enhancement New feature or request label Jul 29, 2026
Co-authored-by: Möbius Agent <mobius-agent@users.noreply.github.com>
@hamzamerzic
hamzamerzic merged commit c4853be into mobius-os:main Jul 29, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant