Skip to content

Preserve explicit remembers in bounded hot continuity - #19

Merged
jbwinters merged 1 commit into
mainfrom
fix/remember-hot-continuity-20261109
Nov 9, 2026
Merged

jbwinters merged 1 commit into
mainfrom
fix/remember-hot-continuity-20261109

Conversation

@jbwinters

Copy link
Copy Markdown
Contributor

An explicit remember --content could emit a valid lifecycle event while its text stayed out of the next session’s hot context. Preserve each explicit write as a bounded checkpoint with its own provenance, so later turn/session acknowledgments do not overwrite it. Source-excerpt capture remains opt-in; the quickstart explains both choices and their disclosure tradeoff.

Validation: clean typecheck and build, boundary check, 57 test files / 473 tests passed, independent review, and alpha.10 archive verification with a clean smoke install. The benchmark-container silent-exit bug is a separate private-harness fix. An installed-artifact regression also checks exact remembered text across a daemon restart and both host wrappers before paid trials.

@jbwinters
jbwinters merged commit 1bc155a into main Nov 9, 2026
8 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.

1 participant