JevSeek v0.2.2 — context fix and archive recall

JevSeek v0.2.2 — context overflow fix and intent-relevant archive recall

Fixed

• Fixes the repeatable Context accounting reserve exhausted failure: archive-count metadata is now included before fitting the context budget.
• Safely removes optional duplicate/history rows from the working projection when needed, without deleting their original saved records. Latest execution/status and user instructions remain protected.
• The actual reported session was projected read-only to reproduce the old bookkeeping error and confirm the corrected projection fits; its saved log was unchanged and no actions were replayed.

Added: searchable original memory

• Private, session-local SQLite FTS5 archive of original user messages, assistant conversation and tool results, including paged full saved outputs.
• A small intent-relevant history tier alongside recent results. Jev can select recall to search for missing evidence or page a precise event sequence. Activity shows Searching saved history.
• Original provenance and status retained. Old source is not assumed current, assistant text is not execution evidence, and recall never changes workspace files or clears interrupted-effect uncertainty.

Research published alongside the implementation

Intent-relevant memory investigation covers MemGPT, Lost in the Middle and LongMemEval; the overflow diagnosis; a reproducible synthetic retrieval study; token/timing measurements; and limitations.

On the intentionally old-evidence fixture, recent-8 found 0/10 old facts, lexical top-4 found 9/10, and Jev chose the correct record or abstained on 12/12 questions from a lexical/diversity candidate pool. These are different metrics on a small constructed example, not proof of general accuracy or infinite context. The study's extra semantic reranking call remains research; production uses local retrieval and Jev's existing routing to request recall. No hidden extra memory-provider calls were added.

Update and resume

Close the old app and replace it with the attached JevSeek.exe. Reopen the saved conversation and choose Resume for a blocked run, or send a follow-up. Existing keys and history remain in place. Review any interrupted effects before acknowledging them; updates do not automatically replay work. Prior Bonsai and v0.2.1 follow-up fixes remain included.

Windows x64, unsigned. Verify SHA256SUMS.txt. Python/Node are bundled for the app, not for arbitrary workspace projects. Microsoft WebView2 runtime terms/privacy still apply; do not disable Windows security protections.

Honest boundaries

This is a finite working window over a growing disk archive, not a literally infinite context window. All accumulated user instructions remain pinned; if mandatory intent/schema/metadata itself cannot fit, the app can still pause safely rather than silently discard constraints. Search may miss synonyms or relevant pages; archives consume storage and logs still load into RAM. A damaged optional cache does not block ordinary context construction and can be removed with the app closed to rebuild it.

Verification for this update: scoped local retrieval/paging measurements, a 12-call Jev-only synthetic research run, read-only overflow reproduction, production build/static syntax and source/package privacy audits. No broad test suite, native UI smoke, generation-model task or Terminal-Bench sweep was run for this update. No VM was restarted. Private user traces and cancelled benchmark work are not in the release.