[OMEGA-402] Rename OmegaClaw to Omega in memory portability - #3
Merged
TossSky merged 1 commit intoSep 3, 2026
Merged
Conversation
The archive format name, the archive filename and the omega_version manifest key all carry the project name, so archives exported before this change no longer validate.
anseliv
approved these changes
Sep 2, 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.
Part of OMEGA-402, epic OMEGA-387.
Renames the product across
memory_portabilityand the README, on top of the knowledge base covered by the companion pull request.Four of these are data, not just identifiers, so this is a breaking change for archives already exported:
FORMAT_NAMEbecomesomega-user-memory, andvalidator.pyrejects a manifest whoseformatdoes not match.omega-memory-<timestamp>.tar.gz.omega_version, read fromOMEGA_VERSION.DEFAULT_OMEGA_ROOTbecomes/PeTTa/repos/Omega, matching the core rename in singnet/Omega#331.Since this branch has not merged yet, archives in that format are unlikely to exist outside development. If any do, they will need re-exporting.
The suite passes with the same result as before the rename, 12 passed on both.