Skip to content

fix: refuse unsafe graph snapshot rebuild stubs#1026

Merged
wbugitlab1 merged 3 commits into
mainfrom
issue/330-legacy-graph-rebuild-reset
Jun 20, 2026
Merged

fix: refuse unsafe graph snapshot rebuild stubs#1026
wbugitlab1 merged 3 commits into
mainfrom
issue/330-legacy-graph-rebuild-reset

Conversation

@wbugitlab1

Copy link
Copy Markdown
Owner

Summary

  • Refuse unforced mem::graph-snapshot-rebuild before graph-scope kv.list when the snapshot is missing, empty, or carries a resetAt boundary.
  • Keep populated non-reset snapshots rebuildable under the existing safe ceiling.
  • Add regressions for empty legacy stubs, post-reset snapshots, populated reset snapshots, populated safe snapshots, and reset enumeration-free behavior.

Closes #330.

Verification

  • corepack pnpm exec vitest run test/graph.test.ts --exclude test/integration.test.ts
  • corepack pnpm run lint
  • corepack pnpm test
  • semgrep scan --config p/default --error --metrics=off .
  • gitleaks detect --source . --redact --log-opts refs/remotes/origin/main..HEAD
  • Codex Security diff scan: no findings

@wbugitlab1 wbugitlab1 merged commit a461f1e into main Jun 20, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug: no path to rebuild or reset a >25K legacy graph — snapshot-rebuild + graph-reset both heartbeat-crash on state::list (follow-up to #816)

1 participant