style(validate): say the coverage findings in one language (closes #84) - #91
Merged
Merged
Conversation
同一個模組裡三筆中文、一筆英文,同一份 validation 報告因此以兩種語言對 operator 說話。零實質引用那筆改成繁體中文,與較早且數量較多的那批一致。 順手把判準寫進 docstring:validation 報告是產品輸出,依 AGENTS.md 的語言政策屬 zh-TW 那一側(英文是教學/推廣文件的語言)。少了這行,下一個新增檢查的人只能各寫各的。 純措辭,無行為變更:issue code 與 severity 不變,benchmark 的 current_issue_classes 只數 code.severity,期望值一格未動。
This was referenced Aug 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #84。基於
main,與 #87/#88/#89 無檔案重疊。改了什麼
validate/coverage.py裡三筆中文、一筆英文,同一份 validation 報告因此以兩種語言對 operator 說話。零實質引用那筆改成繁體中文:source has no material citation in provenance→來源在 provenance 中沒有任何實質引用Re-read the source and cite its material claims…→重讀這份來源並引用它的實質主張;若它不是 API 證據,請明確排除。順手把判準寫進 docstring:validation 報告是產品輸出,依
AGENTS.md的語言政策屬 zh-TW 那一側(英文是教學/推廣文件的語言)。少了這行,下一個新增檢查的人只能各寫各的——這次的不一致就是這樣來的。影響面
純措辭,無行為變更。issue code 與 severity 不變,benchmark 的
current_issue_classes只數code.severity,期望值一格未動。字串在 repo 裡只有一處被斷言(tests/validate/test_coverage.py),已更新;docs/與skills/描述的是行為而非訊息字串。一個範圍外的發現
掃過整個
loop_apidoc/validate/之後,還有一筆英文訊息:response_contract.py的successful response has no usable schema contract。刻意沒改——#84 的範圍寫死在來源涵蓋檢查,擴進來會讓「哪個 diff 造成哪個期望值變動」分不清。已開 #90 追蹤,影響面同樣量測過(只有一處測試斷言)。Test plan
uv run pytest2175 passeduv run ruff check ./uv run python scripts/quality_gate.py --strict-localPASS