Repository navigation
docs: add Simplified Chinese and Japanese READMEs - #85
Conversation
Re-land of #81 by tura-ai-agent: the fork PR cannot trigger CI runs (first-time contributor), so the identical content is landed in-repo where checks run automatically. Co-authored-by: tura-ai-agent <302527399+tura-ai-agent@users.noreply.github.com>
DonPrus
left a comment
DonPrus
left a comment
There was a problem hiding this comment.
Reviewed both translations against the English README, including the installation prerequisites, CLI behavior, proxy configuration, Mission Control/replay contracts and development instructions. All fenced code blocks and inline technical identifiers match the English source, and the relative navigation/documentation links resolve. I found no omitted technical sections or translation changes that alter the documented behavior.
I also read the original #81 discussion/review and compared its three README files byte-for-byte with this PR: the content is identical, and the original contributor is credited in the commit. #81 is already closed as superseded, so this is a replacement rather than an additional competing implementation. The PR merges cleanly with current main and the four CI checks are green. No blocking findings.
2 participants
Re-land of #81 (@tura-ai-agent) with identical content. The original fork PR cannot produce CI runs — GitHub holds workflow runs for first-time contributors and none were ever created, so the four required checks can never report there (no "Approve and run" affordance either). Landing the same diff in-repo, where checks run automatically.
README.zh-CN.mdandREADME.ja.mdmirror the current English README (features, quick start, CLI usage, architecture)README.mdgains the language nav lineCredited via Co-authored-by. Closes #81 once merged.