Skip to content

docs: clarify EverOS former name - #432

Merged
cyfyifanchen merged 1 commit into
mainfrom
codex/clarify-everos-former-name
Sep 4, 2026
Merged

docs: clarify EverOS former name#432
cyfyifanchen merged 1 commit into
mainfrom
codex/clarify-everos-former-name

Conversation

@cyfyifanchen

Copy link
Copy Markdown
Collaborator

Summary

  • Update the public EverMem use-case copy to identify the current product as EverOS while retaining formerly called EverMemOS for historical context.
  • Keep the English README, Chinese README, and both use-case documentation mirrors aligned without changing historical project URLs or compatibility identifiers.

Area

  • Architecture method
  • Benchmark
  • Use case
  • Documentation
  • Developer experience
  • CI, build, or release

Verification

make docs-check
make ci
make check-cjk  # advisory; reports 10 existing repo-wide hits outside the changed locale mirror
make check-commits RANGE=origin/main..HEAD
make check-pr-title PR_TITLE='docs: clarify EverOS former name'

Checklist

  • I kept the change scoped to the relevant area.
  • I am opening this from a separate branch, not pushing directly to main.
  • I updated docs, examples, or setup notes when behavior changed.
  • I added or updated tests when the change affects behavior.
  • I did not commit secrets, .env files, dependency folders, or generated output.
  • Active relative links in Markdown files resolve.

Notes for Reviewers

Historical external repository URLs and demo compatibility identifiers still contain EverMemOS intentionally. Renaming those would break links or interfaces; this PR only updates the product name shown on the main repository's public documentation surfaces.

By submitting this pull request, I agree that my contribution is licensed under
the Apache License 2.0.

@cyfyifanchen
cyfyifanchen merged commit 6ff07ef into main Sep 4, 2026
9 checks passed
@cyfyifanchen
cyfyifanchen deleted the codex/clarify-everos-former-name branch September 4, 2026 00:31
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