Harden recall and capture reliability

[ishaanxgupta]

Keeps recall fail-open and responsive while making background capture bounded, serialized, and reliable.

[ishaanxgupta]

• Make Supermemory pet state aware #49
• Show update notice outside memory context #48
• Add persistent Supermemory CLI mark #47
• Adopt hook and hosted MCP architecture #46
• Harden recall and capture reliability #44 👈 (View in Graphite)
• Prioritize human-memorable capture #43
• Add bounded direct prompt recall #42
• Improve recall result quality #41
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• merging - adds this PR to the back of the merge queue
• fast-track - for urgent changes, fast-track this PR to the front of the merge queue

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[Dhravya]

Merge activity

• Aug 30, 6:57 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Aug 30, 6:58 PM UTC: Graphite couldn't merge this pull request because a downstack PR Add bounded direct prompt recall #42 failed to merge.
• Aug 30, 8:48 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Aug 30, 8:51 PM UTC: Graphite couldn't merge this pull request because a downstack PR Prioritize human-memorable capture #43 failed to merge.
• Aug 30, 9:16 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Aug 30, 9:18 PM UTC: Graphite rebased this pull request as part of a merge.
• Aug 30, 9:18 PM UTC: Graphite couldn't merge this PR because it was not satisfying all requirements (PR does not have required approvals).
• Aug 30, 10:18 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Aug 30, 10:18 PM UTC: Graphite couldn't merge this PR because it was not satisfying all requirements (PR does not have required approvals).
• Aug 30, 10:19 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Aug 30, 10:39 PM UTC: Graphite couldn't merge this PR because it failed for an unknown reason (GitHub is reporting that this PR is not mergeable, despite passing required status checks defined by your branch protection rules. Please check your rulesets for additional blocking criteria. Graphite Merge Queue does not currently support rulesets. Please contact Graphite support for further assistance.).
• Sep 1, 4:46 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Sep 1, 4:47 AM UTC: Graphite couldn't merge this PR because it had merge conflicts.
• Sep 1, 4:48 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Sep 1, 5:08 AM UTC: Graphite couldn't merge this PR because it failed for an unknown reason (GitHub is reporting that this PR is not mergeable, despite passing required status checks defined by your branch protection rules. Please check your rulesets for additional blocking criteria. Graphite Merge Queue does not currently support rulesets. Please contact Graphite support for further assistance.).
• Sep 1, 5:24 AM UTC: Dhravya added this pull request to the Graphite merge queue.
• Sep 1, 5:28 AM UTC: Merged by the Graphite merge queue.

The base branch was changed.