Repository navigation
Keep local hot memory responsive and validate real coding hosts - #12
Merged
Merged
Conversation
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.
Enable durable local hot memory by default so coding hooks can capture and recall while the hosted service is slow or offline. Keep archive work outside the lifecycle lock, preserve concurrent queue arrivals, and migrate pending legacy checkpoints with durable recovery copies and deterministic cross-device provenance. Explicit CROSSHEAD_HOT_SYNC_ENABLED=false retains the legacy mode.
Cache background capability/discovery requests, invalidate migration decisions when workspace mapping changes, and add an offline, purpose-specific owner signature for private-memory deletion requests. Version: 0.5.0-alpha.7 candidate.
Validation: full CI on Node 22/24, reproducible release build, real Claude Code → fresh Codex lifecycle tests on Linux and macOS, and Hermes/OpenCode Docker checks passed on the preceding runtime commit. Those host tests use a deterministic local model and establish hook behavior, not model quality. This revision adds manual production acceptance across separate Linux/macOS runners with real Docker network disconnection, restart/reconnect, reset epochs, tenant/profile isolation, and verified fixture cleanup. Run that workflow after merge and before tagging the release. A bounded production profiler is included.