fix: prevent memory pollution and API waste on automated runs (Resolves #20)

[franksde]

Summary

Currently, Supermemory executes recall and capture hooks on all agent turns, including automated background tasks like heartbeat and cron. This leads to significant token waste and pollutes the memory database with irrelevant background logs.

While there is an existing SKIPPED_PROVIDERS array in capture.ts, it is insufficient because automated triggers often lack a distinct messageProvider.

Now that the OpenClaw SDK exposes the trigger field in the hook context (merged in openclaw/openclaw#24585), we can accurately identify and skip non-interactive automated runs.

Key Changes

• hooks/recall.ts: Safely extracts ctx.trigger. If the trigger exists and is NOT "user" or "manual", it skips the memory recall process entirely.
• hooks/capture.ts: Applies the same trigger-based whitelist before deciding to capture memories, working alongside the existing SKIPPED_PROVIDERS check.

Compatibility

This change is 100% backward compatible. If a user is on an older version of OpenClaw where ctx.trigger is undefined, the logic safely bypasses the guard and falls back to the legacy behavior.

Resolves #20

[franksde]

@Dhravya mind taking a look when you have a moment? Happy to adjust if the approach doesn't fit.

[vorflux]

The approach is sound and backward-compatible. A few things worth fixing:

[ved015]

@franksde can you pls have a look at the suggestions

[franksde]

Pushed an update for the review suggestions. The trigger check now happens before capture logging, and the interactive trigger allowlist lives in a shared helper with a short note about the OpenClaw trigger values and legacy undefined behavior.

[ved015]

@MaheshtheDev good to merge