Refresh Luna memory and emergent compatibility lock - #39
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
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.
Fixes #38. Refreshes the immutable compatibility lock to the verified Core, D&D, CoC, and Narrative commits after branch-safe memory CRUD, emergent Atlas/plot guards, and NPC conversation usability hardening. Keeps release_status=compatibility-lock-not-published. Local verification: Ruff; 59 focused Hosted/MCP/local-stack tests; Host conformance 43 passed, 23 environment-gated real-domain cases skipped. CI will exercise both release-lock and latest-main real-domain lanes.