[OMEGA-391] [OMEGA-392] Rename OmegaClaw to Omega

[TossSky]

Closes OMEGA-391 and OMEGA-392 of epic OMEGA-387.

The project name moves from OmegaClaw to Omega across the code base, the scripts and the documentation. Nothing is left carrying the old name except the SonarCloud key, which holds a server-issued UUID and can only change when the project is recreated under the new organisation.

What changed

Launcher and runtime names. scripts/omegaclaw becomes scripts/omega, the container becomes omega, the volume becomes omega-memory, and the default IRC channel becomes ##omega.

Environment variables. Everything moves to the OMEGA_ prefix: the config lookup prefix, OMEGA_AUTH_SECRET, OMEGA_OPENCLAW_TOKEN, OMEGA_CONTAINER, OMEGA_IRC_CHANNEL, OMEGA_GIT_TOKEN, OMEGA_DIR and the AUTOTESTS_OMEGA_* pair in CI. Note that OMEGA_OPENCLAW_TOKEN keeps its OPENCLAW segment on purpose, since OpenClaw is a separate product and is untouched throughout.

Plugin API. The entry point is now loadOmegaPlugin, in both loaders (Python, MeTTa) and in every in-tree channel, provider and plugin. Documented in reference-plugin-api.md.

MeTTa side. lib_omegaclaw.metta becomes lib_omega.metta, the library alias becomes Omega, the agent entry function becomes (omega), and run.metta points git-import! at singnet/Omega.

In-image layout. OMEGA_DIR is /PeTTa/repos/Omega, followed by MEMORY_DIR, the entrypoint allowlist, the Landlock grant in profile/policy.yaml, the ENTRYPOINT, and the hardcoded paths in the test harness.

Licence. The disclaimer in the README and the launcher named the MIT licence, while NOTICE records the move to Apache 2.0 in July. Corrected to match.

Version string. The agent reports Omega version=. Three call sites reference that function by string rather than as an identifier, in the launcher, the Dockerfile and src/skills.metta; all three moved with it.

Documentation. 23 markdown files, plus the six README PDFs under Autotests/. Those held 118 occurrences that no text search reaches, including instructions for a launcher and variables this PR deletes. Three of them had no markdown source in the repository at all, so the sources are added and the PDFs are removed, since they only duplicated them.

CI. Only what would otherwise break in autotests.yml: the script path, the env var names, the container name in the readiness polling, and the asserted version literal. The rest of the configuration sweep belongs to OMEGA-390.

Breaking changes

No compatibility shims are kept. Out-of-tree plugins that still define loadOmegaClawPlugin will not load: Python ones fail loudly at startup, MeTTa ones fail silently, logging "Plugin X is loaded" while none of their skills register. Operators exporting OMEGACLAW_* variables will find them ignored, and the config lookup falls through to the config file rather than erroring. Existing installations keep a container named omegaclaw and a volume omegaclaw-memory, which the new launcher never touches, so the agent starts on a fresh volume and previous memory stays in the old one.

Verification

Built from this branch and run end to end:

• tests/mettatest.sh in the container: 6 suites, 38 asserts, 0 failures.
• tests/pytest.sh on the host: 12 passed.
• Autotests Phase 1 @run_mandatory: 125 passed, 0 skipped, 0 failed.
• Host launcher and image entrypoint report the same version string.
• Agent ready in 19s.
• The six README PDFs are gone, their markdown sources carry no occurrence of the old name.

git-import! now points at a repository that had not been created when this work started. It does not clone: the Dockerfile copies the sources in, so the alias and the in-image path resolve locally.

Still open

sonar-project.properties deliberately keeps the old project key. It carries a UUID issued by the server when the project was created, so it cannot be rewritten blind; the project has to be recreated under the new organisation and the key copied from there. The analysis is skipped on this PR by design, since the shared workflow skips any pull request whose head is a fork, so it will first run on merge to main and will report against the old project until the key moves. Renovate is the same class of thing: the slug is updated here, but the GitHub App is still installed on the old organisation. Both belong to OMEGA-390.

docs/assets/banner.png still renders the old wordmark and is the first element of the README. Only the alt text moved. It needs the brand asset regenerated, along with a decision on whether the claw mascot stays.

[anseliv]

PDF files should be removed if we have .md to avoid duplication.

[anseliv]

Looks good. I think we are ready to merge this