Repository navigation
Conversation
Owner
(ai: vllm-qwen/qwen3.8-27b) 查重:不重复。open+closed 里针对「reap 先于 epoch-confirm 置位」这一根因只有本 PR;同家族但机制不同的:#3641/#3644(epoch 保留契约,本 PR 的实现对象)、#2915/#3724/#3734(clean-slate / sanctioned rewind)、#4050/#4085(inactive+id churn 恢复)、#4216/#4218(orphan originals 持久化冻结,PR 已明确区分)。无第二个同根因在途 PR。 标签:bug / scope/kernel / p2(代理 repair 模式折叠判定面;命中后 decompress 失败+摘要丢失,但会话仍可透传使用,故 p2 不升 p1)。 已拉取分支 |
Owner
This was referenced Oct 24, 2026
This was referenced Oct 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When a large verified fold loses most of its covered history, the proxy's third reconciliation pass can reap and archive the fold immediately before entering epoch confirmation. The next pass sees no coverage and clears the pause. Cached originals remain, but normal decompression fails and returning the original history cannot restore the summary.
Compute the existing epoch classifier before the reap loop. Retain the fold snapshot while confirmation is pending, including passes that already qualify for the epoch gate. Genuine small zombie blocks below the existing epoch threshold still follow the original reap lifecycle. No new classifier, threshold, config, schema, kernel, or package-version change.
Fixes #4260. Implements the snapshot-retention contract from #3641/#3644; distinct from #4216/#4218 persistence synchronization.
Verification
npm run typecheck,npm run build, unused-export and test-import-graph gates passed. Full-suite result is reserved for remote CI.Behavior and review boundary
This deliberately favors recoverability over automatic cleanup for epoch-qualified large folds: an unresolved episode can retain the snapshot and pause automatic compression longer. Existing realignment clears the pause. Please review that conservative behavior against the existing confirmation workflow.
The issue also records an isolated SQLite cold-load A/B and a successful D-render/foreign-raw case. This PR does not fix the separate raw/render epoch-classification boundary, repair already archived blocks, or establish a complete production-incident causal chain. Both compression modes retain existing behavior except the proxy-only reap guard; plugin mode already excludes reaping. The branch contains only this fix and its tests, based on master
8f2b8de1, without #4218 or the separate judge fix.