Skip to content

fix(prefill): resolve promoted final snapshots directly - #173

Merged
FluffyAIcode merged 1 commit into
mainfrom
AgentMemory/sparse-hot-kv-lookup-0716
Jul 16, 2026
Merged

fix(prefill): resolve promoted final snapshots directly#173
FluffyAIcode merged 1 commit into
mainfrom
AgentMemory/sparse-hot-kv-lookup-0716

Conversation

@FluffyAIcode

Copy link
Copy Markdown
Owner

Summary

  • resolve the longest available chained snapshot even when intermediate checkpoint entries are absent
  • let Primary hot promotion store only the final complete snapshot instead of duplicating every boundary
  • retain full-prefix integrity because each chained hash commits all preceding token blocks
  • update ADR/runbook semantics and add sparse promoted lookup regression coverage

Live root cause

Remote import promoted the final 217-token snapshot to Primary, but the next request still queried allens because local lookup required boundary 1..N to all exist. The final chained snapshot is independently sufficient and safe.

Tests

  • focused cache/service/orchestrator suite — 32 passed
  • full platform-neutral suite — 838 passed, 1 skipped
  • diff checks pass

Made with Cursor

Use the longest available chained boundary so Primary hot promotion stores one complete snapshot without copying every intermediate checkpoint, while preserving full-prefix integrity.

Co-authored-by: Cursor <cursoragent@cursor.com>
@cursor

cursor Bot commented Jul 16, 2026

Copy link
Copy Markdown

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@FluffyAIcode
FluffyAIcode merged commit f033f9f into main Jul 16, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant