Uh oh!
There was an error while loading. Please reload this page.
Request: OpenClaw native session history (backfill + live settlement) [escalated from #423] - #429
Closed
philcunliffe wants to merge 1 commit into
Closed
Request: OpenClaw native session history (backfill + live settlement) [escalated from #423]#429philcunliffe wants to merge 1 commit into
philcunliffe wants to merge 1 commit into
Conversation
Escalated from issue #423. Mints LLP 0142 as a request so the work enters the pipeline family: a new backfill provider plus a settlement design keyed on the provider-issued msg_... id, not a localized fix. Co-Authored-By: Claude <noreply@anthropic.com>
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Escalates issue #423 into the pipeline family as a request LLP.
Why escalate instead of fixing
#423 is labelled
neutral:fix, but it is not bug-shaped. It asks for a newbackfill provider, a live settlement/enrichment design, new config surface
under the LLP 0037 on-join contract, a hermetic smoke, a written acceptance
procedure, and a revision of LLP 0109's open question. There is no
test-provable localized fix ahead of those design decisions, so a fix PR
would be neutral choosing the architecture unilaterally.
This follows the precedent set by #122 -> LLP 0039 (PR #152).
Claims verified before writing
Each load-bearing claim in the issue was re-checked against
origin/master@6a64273, not taken on trust:activate()(.../openclaw/src/index.js) registers a config section and anupstream preset, and no backfill provider.
config.js's own header comment states there is nobackfillblock"the plugin registers no backfill provider".
openclawSessionId()(.../openclaw/src/projector.js) hashes the firstSESSION_HASH_HEAD_CHARSof the system prompt, confirming the collapsingsynthetic session id.
NON_ANTHROPIC_PRIMARYis a hard refusal at.../openclaw/src/settings.js:161,confirming that non-Anthropic-primary traffic never reaches the gateway.
question.
The on-disk format survey in the issue (OpenClaw
2026.7.1-2, macOS, node26.5.0) is not re-verified here: no OpenClaw install was available. The
spec cites it as the issue's contribution and points the design at it, rather
than restating it as independently confirmed.
What this PR contains
One new file,
llp/0142-openclaw-native-history.spec.md(Type: Spec, Status:Active). No code. 0142 was free across
masterand every open branch (0139 and0140 are claimed by open PR #422, 0141 by merged #425).
Once merged,
neutral backlogsurfaces LLP 0142 as an uncovered request andthe pipeline family mints a design for it. The issue stays open until that work
lands, so this PR intentionally uses
Refs, notFixes.Refs #423