Refine Simplified Chinese token tagline

[Jerry-CodeHub]

Summary

• Update the Simplified Chinese tagline to use "Token" instead of "词元"
• Keep the existing informal "你" tone for consistency with the rest of zh-Hans localization
• Apply the same wording to the About tagline

Why

"Token" is more natural in Chinese developer-facing AI product copy than the more literal "词元", while still matching the English source text:

May your tokens never run out—keep agent limits in view.

This is intended as a tagline-specific wording choice. Other usage labels can continue using the existing glossary terms where they read better as formal UI labels.

Proof

Verified the changed Simplified Chinese localization entries are present and parseable:

plutil -p Sources/CodexBar/Resources/zh-Hans.lproj/Localizable.strings | rg 'May your tokens never run out|about_tagline'

Output:

"about_tagline" => "愿你的 Token 永不耗尽——随时关注智能体限制。"
"May your tokens never run out—keep agent limits in view." => "愿你的 Token 永不耗尽——随时关注智能体限制。"

Testing

• Verified zh-Hans localization resource parsing with plutil -p

[clawsweeper]

Codex review: needs maintainer review before merge. Reviewed May 25, 2026, 11:23 PM ET / 03:23 UTC.

Summary
The branch updates two Simplified Chinese localized tagline string values from “词元” to Latin “Token” in Localizable.strings.

Reproducibility: not applicable. this is a localization copy PR rather than a bug report. The relevant verification is source inspection plus the contributor’s resource-parse output for the two changed zh-Hans values.

Review metrics: 1 noteworthy metric.

• Localization scope: 1 file changed, 2 strings updated. The patch is limited to Simplified Chinese tagline copy, keeping review focused on wording and localization proof.

Merge readiness
Overall: 🐚 platinum hermit
Proof: 🐚 platinum hermit
Patch quality: 🐚 platinum hermit
Result: ready for maintainer review.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Rank-up moves:

• Have a maintainer or native speaker confirm the tagline-specific “Token” terminology choice before merging.

Risk before merge

• The wording intentionally diverges from current zh-Hans usage-token terms such as “词元”, so a maintainer or native speaker should confirm that this tagline-specific exception is preferred.

Maintainer options:

1. Decide the mitigation before merge
   Merge the narrow localization copy change if maintainers accept “Token” as the tagline-specific zh-Hans term; otherwise ask for a copy revision that keeps both tagline keys synchronized.
2. Pause or close
   Do not merge this PR until maintainers decide whether the risk is worth taking.

Next step before merge
No automated repair is needed; maintainers or native speakers should decide whether the tagline-specific “Token” wording is the desired zh-Hans copy before merge.

Security
Cleared: The diff only changes localized string values and does not touch code execution, dependencies, CI, secrets, scripts, packaging, or credential handling.

Review details

Best possible solution:

Merge the narrow localization copy change if maintainers accept “Token” as the tagline-specific zh-Hans term; otherwise ask for a copy revision that keeps both tagline keys synchronized.

Do we have a high-confidence way to reproduce the issue?

Not applicable; this is a localization copy PR rather than a bug report. The relevant verification is source inspection plus the contributor’s resource-parse output for the two changed zh-Hans values.

Is this the best way to solve the issue?

Yes, if the copy choice is accepted: changing exactly the two localized string values is the narrowest maintainable implementation path. The remaining concern is terminology preference, not code structure.

AGENTS.md: found and applied where relevant.

Codex review notes: model gpt-5.5, reasoning high; reviewed against 7c751570b7e9.

Label changes

Label changes:

• add proof: sufficient: Contributor real behavior proof is sufficient. The PR body includes copied terminal output from plutil -p showing both changed zh-Hans entries parse to the new Token wording.
• add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🐚 platinum hermit and patch quality is 🐚 platinum hermit.
• add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (terminal): The PR body includes copied terminal output from plutil -p showing both changed zh-Hans entries parse to the new Token wording.
• remove rating: 🧂 unranked krab: Current PR rating is rating: 🐚 platinum hermit, so this older rating label is no longer current.
• remove status: 📣 needs proof: Current PR status label is status: 👀 ready for maintainer look.

Label justifications:

• P3: This is low-risk localization polish with no runtime, data, auth, or availability impact.
• rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🐚 platinum hermit and patch quality is 🐚 platinum hermit.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Sufficient (terminal): The PR body includes copied terminal output from plutil -p showing both changed zh-Hans entries parse to the new Token wording.
• proof: sufficient: Contributor real behavior proof is sufficient. The PR body includes copied terminal output from plutil -p showing both changed zh-Hans entries parse to the new Token wording.

Evidence reviewed

What I checked:

• Current main wording: Current main still uses “词元” for the main Simplified Chinese tagline, so this PR is not already implemented on main. (Sources/CodexBar/Resources/zh-Hans.lproj/Localizable.strings:174, 7c751570b7e9)
• Current About wording: Current main also uses “词元” for about_tagline, matching the PR’s second targeted string. (Sources/CodexBar/Resources/zh-Hans.lproj/Localizable.strings:525, 7c751570b7e9)
• PR diff scope: The proposed commit changes only the two zh-Hans tagline values from “词元” to “Token”. (Sources/CodexBar/Resources/zh-Hans.lproj/Localizable.strings:174, 038a3eddeb4a)
• Resource packaging: The app target processes Resources, so the edited localization file is part of the app resource bundle. (Package.swift:94, 7c751570b7e9)
• About tagline call site: The About pane renders L("about_tagline"), so the second edited key is a live UI string rather than dead text. (Sources/CodexBar/PreferencesAboutPane.swift:61, 7c751570b7e9)
• Contributor proof: The updated PR body includes copied plutil -p output showing both changed zh-Hans entries parse to “愿你的 Token 永不耗尽——随时关注智能体限制。”. (038a3eddeb4a)

Likely related people:

• narallee: Authored the recent zh-Hans localization pass that contains the current tagline wording and broader token terminology choices. (role: recent Simplified Chinese localization contributor; confidence: high; commits: 573652ae89f9; files: Sources/CodexBar/Resources/zh-Hans.lproj/Localizable.strings)
• steipete: Recent blame and release history show Peter Steinberger carrying the current zh-Hans resource file on main and the latest release/base commits around this file. (role: recent resource maintainer; confidence: medium; commits: 333d584a4950, 7c751570b7e9; files: Sources/CodexBar/Resources/zh-Hans.lproj/Localizable.strings)
• zzj: Introduced the original zh-Hans localization file and localization plumbing, making them relevant for terminology provenance even though later commits changed this specific copy. (role: original Simplified Chinese localization contributor; confidence: medium; commits: dd54a28d509b; files: Sources/CodexBar/Resources/zh-Hans.lproj/Localizable.strings)

What the crustacean ranks mean

• 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
• 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
• 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
• 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
• 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
• 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
• 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

[Jerry-CodeHub]

@clawsweeper re-review

[clawsweeper]

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

Re-review progress:

• State: Complete
• Detail: The targeted re-review finished, the durable review comment was updated, and the synced verdict was routed.
• Run: https://github.com/openclaw/clawsweeper/actions/runs/26430268784
• Updated: 2026-05-26T03:27:22.819Z

[steipete]

Thanks for the careful wording pass. This is now covered by the newer Simplified Chinese localization polish that landed in #1165 (62535877): current main already keeps the tagline on token, preserves consistency with the rest of zh-Hans, and also updates the agent-limits wording plus the missing notification strings.

Closing this as superseded so we do not merge a conflicting tagline-only branch.