chore: add sponsor zai

[zerob13]

Summary by CodeRabbit

• Documentation

  • Added a sponsor section to README files (English, Japanese, Chinese) promoting Z.ai GLM CODING PLAN with badge, description, TOC entries, and a 10% discount link.

• Chores

  • Minor internal code adjustments in calculation-related code; no user-facing behavior changes.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds localized sponsor sections to three README files and modifies src/calculator.py by renaming a global variable, adding a new method, and changing an existing method signature.

Changes

Cohort / File(s)	Summary
README Sponsor Sections README.md, README.jp.md, README.zh.md	Inserted a localized sponsor block (heading, linked badge image, Z.ai GLM CODING PLAN description, 10% off link) and updated Table of Contents entries; added horizontal separators.
Calculator code changes src/calculator.py	Renamed global var old_global_var → new_global_var; added def coderabbit_add(x, y) to Calculator; changed coderabbit_formula(x, y) → coderabbit_formula(x, y, z) (signature update).

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰✨ I hopped through docs in morning light,
Pushed badges, links—made READMEs bright.
I tweaked a var, a method new,
A little change from me to you.
Happy hops for code and cheer—hooray!

Pre-merge checks

✅ 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: add sponsor zai' accurately reflects the main change—adding sponsor information (Zai/Z.ai) to multiple README files across different languages.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 043025d and dad13e4.

📒 Files selected for processing (3)

• README.jp.md
• README.md
• README.zh.md

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

• README.md

🚧 Files skipped from review as they are similar to previous changes (1)

• README.zh.md

🧰 Additional context used

🪛 markdownlint-cli2 (0.18.1)

README.jp.md

40-40: Link fragments should be valid

(MD051, link-fragments)

⏰ 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: build-check (x64)

🔇 Additional comments (1)

README.jp.md (1)

40-40: Verify link fragment validity.

The TOC entry on Line 40 links to #-スポンサー for the header ## ❤️ スポンサー. Static analysis flagged this link fragment (MD051). Ensure the anchor format correctly matches the Markdown parser's header-to-anchor conversion, particularly with emoji handling. If valid per your Markdown renderer, this can be dismissed as a false positive.

---

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.}

[coderabbitai]

Actionable comments posted: 4

Fix all issues with AI Agents 🤖

In @README.jp.md:
- Around line 27-35: Add the new "## ❤️ スポンサー" section to the document's table
of contents by inserting a TOC entry that links to that header (e.g., add a line
like "- [❤️ スポンサー](#-スポンサー)") inside the existing TOC block so the "❤️ スポンサー"
header is discoverable; update the TOC where other top-level entries are listed
to match the same indentation/style as the surrounding entries.
- Around line 27-35: README.jp.md references docs/images/zai.en.png while
README.zh.md uses docs/images/zai.zh.png, causing inconsistent localization;
either add a Japanese-localized image docs/images/zai.jp.png and update the
reference in README.jp.md to use that file, or explicitly document in
README.jp.md why the English asset (docs/images/zai.en.png) is intentionally
reused (e.g., add a short note under the sponsor section); locate and change the
image reference in README.jp.md (the line containing docs/images/zai.en.png) or
add the new image file docs/images/zai.jp.png as appropriate.

In @README.md:
- Around line 27-35: Add an entry for the new "## ❤️Sponsor" section into the
README table of contents so it’s discoverable; insert a line like `- [❤️
Sponsor](#-sponsor)` into the TOC block (the section currently spanning lines
around the existing links) so the "❤️ Sponsor" header defined as `## ❤️Sponsor`
is referenced.

In @README.zh.md:
- Around line 27-35: Add the new "## ❤️ 赞助商" section to the README TOC by
inserting an entry like `- [❤️ 赞助商](#-赞助商)` into the existing table of contents
block (the lines around the current TOC, referenced in the review comment), so
the "❤️ 赞助商" header appears in the list and links correctly to the section.

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 84940b2 and 043025d.

⛔ Files ignored due to path filters (2)

• docs/images/zai.en.png is excluded by !**/*.png
• docs/images/zai.zh.png is excluded by !**/*.png

📒 Files selected for processing (3)

• README.jp.md
• README.md
• README.zh.md

🧰 Additional context used

🧠 Learnings (1)

📓 Common learnings

Learnt from: CR
Repo: ThinkInAIXYZ/deepchat PR: 0
File: .cursor/rules/i18n.mdc:0-0
Timestamp: 2026-01-05T02:41:13.293Z
Learning: Applies to src/renderer/src/i18n/**/*.json : Add new translations to ALL language files (da-DK, en-US, fa-IR, fr-FR, he-IL, ja-JP, ko-KR, pt-BR, ru-RU, zh-CN, zh-HK, zh-TW) with consistent key names across all locales

🔇 Additional comments (2)

README.zh.md (1)

29-33: Content localization looks good.

The Chinese version properly localizes pricing (20 元 vs. $3) and uses the Chinese-specific image asset zai.zh.png, which is consistent with the localization strategy seen in README.zh.md.

README.md (1)

29-29: No action required. The sponsor image file docs/images/zai.en.png exists in the repository and the badge link is valid.

Likely an incorrect or invalid review comment.