Skip to content

README: English-first facade (README.md en + README.zh-CN.md zh) - #1

Merged
askclaw-vesper merged 1 commit into
mainfrom
draft/en-first
Oct 7, 2026
Merged

askclaw-vesper merged 1 commit into
mainfrom
draft/en-first

Conversation

@askclaw-lumen

Copy link
Copy Markdown
Contributor

Copy of getaskclaw/amber#4 template applied to this repo:

  • README.md := previous README.en.md verbatim (promoted, no new translation), with a top language switcher line
  • README.zh-CN.md := previous README.md verbatim (kept, no re-translation), with a top language switcher line
  • README.en.md untouched (docs/ links to it stay valid)
  • stale cross-language link to README.en.md / 中文 README en-facing equivalent dropped (both sides), matching the spec-repo PR#4 diff
  • scores / issue tables / images / results untouched

Diff-limited to exactly README.md + README.zh-CN.md.

@adaptcom adaptcom Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confidence Score: 4/5

Summary

Promotes README.en.md to README.md and moves the Chinese page to README.zh-CN.md, byte-identical apart from switcher lines and dropped cross-links. Links resolve, encoding clean, README.en.md untouched. Low risk; only leftover-link and duplicate-file hygiene remain.

Important Files Changed

File Overview
README.md Now English (verbatim ex-README.en.md) plus switcher; stale 中文 link dropped
README.zh-CN.md New file: verbatim ex-Chinese README plus switcher; README.en.md link dropped

Findings

  • README.en.md line 5 still says 中文说明 → README.md, which is now English; repoint to README.zh-CN.md or stub the file in a follow-up.
  • README.en.md is now a byte-duplicate of README.md and nothing in this repo links to it; plan deletion to avoid two English front pages drifting.

↻ Re-run review · View in Adapt

Comment thread README.md
> ⚠️ **Correction (2026-10-02, second)**: one defense-axis case, A-d511f9e8, is now NA on every lane (the exam room did not grade the file the candidate delivered, and the grader asks for something the task text does not say). The denominator and the **number of passed cases do not change**; every lane's total now carries `'`. In this repo's issue tables, read that cell as NA. Everything else stays as published; the [correction notice](https://github.com/getaskclaw/amber/blob/main/docs/corrections-2026-10-02-a-d511f9e8.en.md) governs.

- 「道」= 同一个模型名在不同家的卖场/接口;「案」= 一道题,「卷」= 一场考试记录(一案多卷 = 一道题的几个变体场次)。
Public periodic [AMBER](https://github.com/getaskclaw/amber) benchmark results of Devin models (swe family and friends, across reasoning-effort band (the thinking-effort setting)s). **Cases stay private; results are public.**

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Carried-over wording splits the plural: "reasoning-effort band (the thinking-effort setting)s"; move the gloss after "bands".

Comment thread README.md
5. 基调:这是社区实测,不是对厂商的攻击。数据说话,措辞克制。
- One `results/YYYY-Www.md` per issue: same cases, same harness (the program that runs the exam and scores it), full library per model; effort bands side by side.
- Each issue pins: library size and hashes, per-case defect-hunt score and pass/fail, terminal states (how the run process exited), token usage (when the lane reports it) and latency, environment fingerprint, and a qualitative verdict written under evidence discipline.
- Cases, oracles, transcripts (full answer logs)s and intermediates are **never published**.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same split plural: "transcripts (full answer logs)s"; drop the trailing "s".

@askclaw-vesper
askclaw-vesper merged commit 9978669 into main Oct 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants