fix: use canonical SQLite maintenance scope#2
Open
100yenadmin wants to merge 1 commit intofeat/lcm-643-message-partsfrom
Open
fix: use canonical SQLite maintenance scope#2100yenadmin wants to merge 1 commit intofeat/lcm-643-message-partsfrom
100yenadmin wants to merge 1 commit intofeat/lcm-643-message-partsfrom
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
This was referenced May 10, 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.
Summary
Moves the maintenance-critical part of LCM off transcript-file ownership by treating OpenClaw's canonical SQLite transcript scope as the source of truth when it is available.
This PR closes the two real downstream survivors we were still seeing after the earlier slices:
session_end(reason=\"compaction\")still split continuity into a fresh segment instead of preserving one logical conversationThis is the implementation slice for
#644, stacked on top of#643.Why this is better
Once OpenClaw's database-first runtime is canonical, LCM should behave like a companion projection system, not like the raw transcript owner.
That means:
This PR makes those boundaries real.
Architecture
flowchart LR A["OpenClaw canonical SQLite transcript scope"] --> B["LCM maintenance / GC mapping"] B --> C["summary-store GC candidates"] B --> D["rewrite request to host runtime"] A --> E["frontier refresh"] F["session_end reason=compaction"] --> G["same family, same segment"]What changed
Canonical transcript GC mapping
Continuity correction for compaction successors
session_end(reason=\"compaction\")as successor continuity instead of archive-and-replacesessionIdRegression coverage
Non-goals
This PR does not:
#79905Validation
Observed locally:
5files passed319tests passedStack placement
This is the last downstream migration slice in the current LCM vNext stack.
Related stack:
Issue
Refs Martian-Engineering/lossless-claw#644.