chore: delete outdated docs

[ssnd]

Summary by CodeRabbit

• Documentation
  • Removed English and Russian pages describing long-term/cold storage architecture, store types, read/write/query semantics, migration and deployment procedures.
  • Removed English and Russian pages describing rate-limiting behavior and configuration.
  • Added a Telegram badge to the README Overview.
  • Documentation-only changes; no runtime or API behavior altered. Links/bookmarks to removed pages will no longer work.

[coderabbitai]

📝 Walkthrough

Walkthrough

Deletes four documentation pages (English and Russian long-term store and rate-limiting docs) and updates README.md to add a Telegram badge. No code or API changes.

Changes

Cohort / File(s)	Summary of Changes
Docs: remove long-term store design docs/en/07-long-term-store.md, docs/ru/07-long-term-store.md	Deleted documents describing long-term/cold storage architecture, migration procedures, read/write/query semantics, time-field rules, and deployment plan.
Docs: remove rate-limiting docs docs/en/08-rate-limiting.md, docs/ru/08-rate-limiting.md	Deleted documents describing rate-limiting concepts, use-cases, references to internal rate limiter components, and enabling configuration.
README: add badge README.md	Inserted a Telegram badge image in the Overview section (added after CI badge and before coverage badge).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• docs: add docs for config file #88 — touches/removes rate-limiting documentation and likely overlaps with the deleted rate-limiting docs.

Suggested labels

documentation

Suggested reviewers

• eguguchkin
• forshev
• moflotas
• dkharms

Pre-merge checks (3 passed)

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title “chore: delete outdated docs” succinctly identifies the primary operation of removing obsolete documentation files, which constitutes the bulk of this pull request. It is concise, clear, and avoids listing individual filenames, while accurately reflecting the main intent of the change. Although a Telegram badge is added to the README, that is a minor documentation tweak that does not warrant explicit mention in the title. Consequently, the title aligns well with the PR’s objectives and content.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8e13405 and b55b496.

📒 Files selected for processing (3)

• README.md (1 hunks)
• docs/en/08-rate-limiting.md (0 hunks)
• docs/ru/08-rate-limiting.md (0 hunks)

💤 Files with no reviewable changes (2)

• docs/ru/08-rate-limiting.md
• docs/en/08-rate-limiting.md

✅ Files skipped from review due to trivial changes (1)

• README.md

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: test

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch 0-remove-long-term-docs

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 71.51%. Comparing base (df0eb6f) to head (b55b496).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #126      +/-   ##
==========================================
+ Coverage   71.37%   71.51%   +0.14%     
==========================================
  Files         201      201              
  Lines       18167    18167              
==========================================
+ Hits        12967    12993      +26     
+ Misses       4475     4454      -21     
+ Partials      725      720       -5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.