docs: CHANGELOG.md with the version history (#59)

[compot-dev]

Closes #59.

• CHANGELOG.md in the vtesse format: a header (where the version lives, the latest release from 3.0.2 on, this file is the history) and one section per version, newest first, 3.0.2 down to 2.2.0, plus a short "Before 2.2.0". Sections were filled from the commits between the version bumps (the table in Add CHANGELOG.md with the version history #59) and the notes of the v2.3.8, v3.0.0 and v3.0.1 releases. 3.0.0 is marked as breaking (protocol v2 replaces v1). Dates are those of the commit that set the version.
• The 3.0.2 section already names the release change from Release: one release "latest" titled "Camex <version>", stable file names, SHA256SUMS #60, which comes next and makes the header true. The two PRs are meant to be merged one after the other.
• README (en/ru/zh-CN, one commit): the "Versioning & Release Process" section points to CHANGELOG.md and says a version bump adds its section in the same PR. The rest of that section (tags, versioned asset names) is rewritten in Release: one release "latest" titled "Camex <version>", stable file names, SHA256SUMS #60.

Note: #59 and #60 say main; the default branch of camex is master, and the text uses that.

[qodo-free-for-open-source-projects]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Tip of the day

💡 Did you know, you can see how risky a PR is at a glance with blast radius labels

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[qodo-free-for-open-source-projects]

PR Summary by Qodo

Add version history and link it from all READMEs

📝 Documentation 🕐 10-20 Minutes

AI Description

• Add a newest-first changelog from 3.0.2 through 2.2.0, including the protocol v2 compatibility
 break.
• Document the planned latest release model ahead of the separate release-workflow PR.
• Link the changelog from the English, Russian, and Simplified Chinese release guides.

Diagram

graph TD
  V["Version source"] --> C["CHANGELOG.md"] --> U["Readers"]
  E["English README"] --> C
  L["Localized READMEs"] --> C

Loading

High-Level Assessment

A standalone changelog linked from each existing language guide is appropriate: it gives release history one maintained location without duplicating the entries across translations. The latest release behavior is documented in anticipation of #60, not implemented by this PR.

Files changed (4) +122 / -0

Documentation (4) +122 / -0

CHANGELOG.mdEstablish the version-by-version change history +113/-0

Establish the version-by-version change history

• Adds dated entries from 3.0.2 back to 2.2.0 and a brief earlier-history note. Calls out the protocol v2 breaking change and describes the planned 'latest' release model.

CHANGELOG.md

README.mdLink the English release guide to the changelog +3/-0

Link the English release guide to the changelog

• Adds a changelog link and says version bumps should add their changelog section in the same PR.

README.md

README.ru.mdLink the Russian release guide to the changelog +3/-0

Link the Russian release guide to the changelog

• Adds the same version-bump guidance in Russian and identifies the linked changelog as English-language.

README.ru.md

README.zh-CN.mdLink the Chinese release guide to the changelog +3/-0

Link the Chinese release guide to the changelog

• Adds the same version-bump guidance in Simplified Chinese and identifies the linked changelog as English-language.

README.zh-CN.md