Fix summarizer hot path: capture on SessionEnd, drain in background

[jamby77]

Problem

The Stop hook fires on every turn, so the plugin re-summarized the whole session on each response — burning minutes of local LLM time on a hook, blocking the turn, and discarding the work when the Ollama client timed out. The success path stored empty husks (SessionSummarySchema.parse({}) passes and yields "Session recorded — summary unavailable"). Net result over 8 days: one memory, and it was empty; after a GPU fix, near-duplicate memories appeared one-per-turn.

Change

• Capture on SessionEnd (fires once), not Stop (every turn) — with a migration that strips the stale Stop registration from existing installs.
• Queue-only capture hook — the hook parses the transcript, pushes to the existing ingest queue, spawns a detached drainer, and exits in milliseconds. No LLM ever runs on a hook.
• Reject empty summaries before they reach the store (isEmptySummary predicate); husks are dropped, not re-queued.
• Plus small fixes made while verifying: correct the stale Stop label in the install summary, fix an integration test that recalled by the wrong embed text, and gitignore .idea/.

Verification

bun run typecheck clean · bun test tests/unit green · bun test tests/integration green (against Valkey on 6390).

Stack

Bottom of a 2-PR stack. The follow-on #9 (checkpoint capture) builds directly on this branch — merge this one first.

---

Note

Medium Risk
Changes when and how session memories are captured (hook lifecycle + async drain); misconfiguration could leave transcripts queued until drain runs, but hooks no longer block on LLM calls.

Overview
Moves session memory capture off the per-turn Stop hook to SessionEnd, so summarization no longer runs on every assistant response or blocks the hook path.

The session-end hook now only parses the transcript, pushes to the Valkey ingest queue, and spawns a detached drain process (compiled binary or bun run source). AgingPipeline.processIngestQueue performs LLM summarization and storage. Install and register-hooks register SessionEnd instead of Stop, and stripLegacyBetterdbHooks removes stale Stop entries on upgrade without touching third-party hooks.

Adds isEmptySummary so default-schema “husks” are dropped from the ingest queue (not stored or re-queued). New betterdb-memory drain command and drain binary in the install set. Hook payload schema switches from StopPayload to SessionEndPayload.

^{Reviewed by Cursor Bugbot for commit 2e3e752. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 2e3e752. Configure here.}

[cursor]

Install omits dev hook markers

Medium Severity

betterdb-memory install calls stripLegacyBetterdbHooks with only the default betterdb marker, while register-hooks.ts also passes the plugin src/hooks path. A leftover Stop registration whose command path does not contain betterdb can survive install and keep firing the old per-turn hook alongside SessionEnd.

Additional Locations (1)

• scripts/register-hooks.ts#L69-L73

 

^{Reviewed by Cursor Bugbot for commit 2e3e752. Configure here.}