docs: zh-CN/ko-KR/pt-BR package-legitimacy docs still describe pre-ADR-0656 slopcheck design

Pre-submission checklist

• I have searched existing issues and this documentation problem has not already been reported

Issue type

Outdated (no longer matches behavior)

Where is the issue?

docs/zh-CN/, docs/ko-KR/, docs/pt-BR/ — package-legitimacy gate sections

What's wrong?

Follow-up to #2775. That fix corrected the English docs (and the ja-JP mirror) that described the pre-ADR-0656 design — slopcheck as the install-or-degrade gate, with unavailability degrading every package to [ASSUMED]. ADR-0656 inverted this: registry-API verdicts (npm/PyPI/crates.io) are the gate; slopcheck is an optional escalate-only adapter that no shipped configuration wires.

The mechanical parts of that correction (command-string swaps, table-header words, and single already-attested-term swaps) have now been mirrored inline into zh-CN, ko-KR, and pt-BR in the same PR — 8 of 19 zh-CN, 7 of 15+1 ko-KR (the +1 is a transliterated heading found after this issue was filed, see the ko-KR section below), and 8 of 17 pt-BR occurrences (case-insensitive slopcheck count, Latin string only — a follow-up sweep also checked all four locales for non-Latin transliterated forms of "slopcheck"; see the ko-KR note below for the one hit). What's left below is content that needs real prose composed in each language, not just a token swap, so it was intentionally left for a fluent contributor rather than risk mistranslation:

docs/zh-CN/ — 11 remaining occurrences across 9 lines

• docs/zh-CN/explanation/security-model.md:49 — "Graceful degradation" paragraph still describes the old slopcheck-unavailable → [ASSUMED] fallback (2 occurrences on this line). Needs the corrected mechanics (5s timeout, null-signal degrade, unknown-age/unknown-downloads → [SUS], same checkpoint:human-verify as [ASSUMED]) plus the "slopcheck is optional escalate-only" closer — see the English original at docs/explanation/security-model.md:96-112 for the target content.
• docs/zh-CN/explanation/security-model.md:51 — "External dependency" sentence pair (slopcheck is MIT/pip-installable, abandonment fallback) was deleted in the English fix and folded into the Graceful Degradation closer above. Needs the equivalent structural change.
• docs/zh-CN/explanation/security-model.md:102 — "is not caught by slopcheck...slopcheck checks registration signals" (2 occurrences on this line) → needs to become "is not caught by the registry-API gate, which checks registration signals" (English: docs/explanation/security-model.md:250-252).
• docs/zh-CN/ARCHITECTURE.md:666 — "Graceful degradation" bullet, same rewrite as security-model.md:49 (English target: docs/ARCHITECTURE.md:856).
• docs/zh-CN/ARCHITECTURE.md:668 — "External dependency" bullet; English deleted this bullet entirely (folded into Graceful degradation). Needs the equivalent removal/fold.
• docs/zh-CN/COMMANDS.md:194 — "If slopcheck cannot be installed..." sentence needs to become the registry-lookup-failure-degrades-to-[SUS] explanation (English target: docs/COMMANDS.md:236).
• docs/zh-CN/USER-GUIDE.md:405,408,409 — "Manually install slopcheck" + pip install slopcheck code block needs to become the "verdicts computed from live registry APIs, no separate tool to install" paragraph (English target: docs/USER-GUIDE.md:435-438).

docs/ko-KR/ — 9 Latin slopcheck occurrences across 8 lines, plus 1 transliterated occurrence — 10 total across 9 lines

Update: the transliterated heading at docs/ko-KR/USER-GUIDE.md:398 ("슬롭체크 판정:") has since been fixed inline (mechanical swap to "적법성 판정:", reusing the already-attested 적법성/legitimacy word from the same table two lines below) — it is no longer outstanding. A second transliterated occurrence was found immediately below it and is still outstanding (added below). A parallel sweep across zh-CN and pt-BR for phonetic-transliteration forms of "slopcheck" (not just the Latin string) found none — those two locales keep "slopcheck" in Latin script everywhere, so their inventories above are already complete.

• docs/ko-KR/explanation/security-model.md:55 — Graceful degradation paragraph (2 occurrences on this line), same rewrite as zh-CN above.
• docs/ko-KR/explanation/security-model.md:57 — External dependency sentence pair, same as zh-CN above.
• docs/ko-KR/explanation/security-model.md:108 — "not caught by slopcheck" → "not caught by the registry-API gate".
• docs/ko-KR/ARCHITECTURE.md:667 — Graceful degradation bullet.
• docs/ko-KR/ARCHITECTURE.md:669 — External dependency bullet (deleted/folded in English).
• docs/ko-KR/COMMANDS.md:194 — "if slopcheck cannot be installed" → registry-lookup-failure-degrades-to-[SUS] explanation.
• docs/ko-KR/USER-GUIDE.md:406 — "슬롭체크를 수동으로 설치하려면:" ("To install slopcheck manually:", transliterated — not Latin-grep-catchable) — the lead-in sentence to the code block below; needs to become the "computed from live registry APIs, no separate tool to install" paragraph together with the block it introduces.
• docs/ko-KR/USER-GUIDE.md:409,410 — pip install slopcheck code block → "computed from live registry APIs" paragraph (same paragraph as :406 above).

docs/pt-BR/ — 9 remaining occurrences across 9 lines

• docs/pt-BR/explanation/security-model.md:106 — Graceful degradation paragraph (Se \slopcheck` não estiver disponível...`), same rewrite as above.
• docs/pt-BR/explanation/security-model.md:112 — continuation of the same paragraph ("a indisponibilidade do slopcheck significa que...").
• docs/pt-BR/explanation/security-model.md:115 — External dependency sentence ("A ferramenta slopcheck é licenciada sob MIT...").
• docs/pt-BR/ARCHITECTURE.md:698 — Graceful degradation bullet ("Degradação graceful").
• docs/pt-BR/ARCHITECTURE.md:700 — External dependency bullet (deleted/folded in English).
• docs/pt-BR/COMMANDS.md:194 — "Se slopcheck não puder ser instalado" → registry-lookup-failure-degrades-to-[SUS] explanation.
• docs/pt-BR/USER-GUIDE.md:406,409,410 — "Para instalar o slopcheck manualmente" + pip install slopcheck code block → "computed from live registry APIs" paragraph.

Suggested fix

For each locale, translate the corresponding corrected English passage (cited above by file:line, all already merged to next via #2775) rather than translating from the stale original — the English is the ground truth for what the design actually does now (verified against src/package-legitimacy.cts in #2775). A fluent speaker of each language should do the actual prose composition; this issue exists specifically because that step was out of reach for the agent that did the mechanical (command-string / table-header / single-attested-term) portion of the fix in #2775.