docs(i18n): align operator guide and README terminology #373

Problem and evidence

The owner expanded this existing translation issue and PR #374 on 2026-11-05 from localized READMEs to operator-guide terminology. English remains the canonical contract; runtime behavior is outside this maintenance.

Context-sensitive terms are currently conflated in several guides:

• Handoff ACK receipts are protocol acknowledgement/confirmation information. Paired-request receipts are persisted request processing/result records; Control operation receipts are historical management result records. Neither latter record proves an agent read a message or reflects current device state.
• Literal commercial-receipt wording (영수증, 收据, or unclear レシート) obscures those distinctions. API identifiers and already-correct technical terms must remain intact.
• Security replay is not media playback or an unrestricted retry; process crash differs from an identifier/body conflict; redaction hides sensitive values rather than deleting evidence.
• Configured policy capabilities are permissions, while declared native capabilities describe support. Agent-qualified sender fields do not confer authority. A 64-character hexadecimal identity is not a 64-bit identity; cooperative/advisory locks do not provide a stronger mandatory exclusion guarantee.

Source review also found ambiguous/stale English discovery wording: the current registry includes all three adapters; Codex not_installed follows automatic discovery with no readable state DB and no errors; Antigravity uses no_live_registration when no live bridge is found. The selected-home guard does not attest effective native storage. These descriptions are clarified in English and all three translations from existing implementation evidence, without new support claims. The same source checks clarify enabled SSH BatchMode, the real operator-entered trusted fingerprint, and the one-of-two provider-credential refusal condition.

Expected behavior / scope

Keep one PR covering README.ko.md / README.ja.md / README.zh-CN.md plus terminology corrections in the Korean/Japanese/Simplified Chinese operator and reference guides. Compare corresponding English sections before each semantic correction. Audit all current guide/reference files; inspect related historical records where target terms occur, preserving dated evidence rather than converting history into current operational guarantees.

The shared audit inventory contains 51 localized documentation files per language: 21 guide/reference entries and 30 historical records (the dated public pilot is classified as history). Historical term-context inspection is not a claim of a complete historical retranslation. Record per-file coverage and unchanged/changed/source-ambiguity decisions.

Minimal canonical wording clarification is allowed only where existing source/code proves an ambiguity or stale description. Keep runtime/code, CLI behavior, machine-readable schemas, frozen English handoff contract and existing release artifacts unchanged.

Acceptance checks

• Distinguish handoff acknowledgement receipts, paired request processing records and Control management result records throughout relevant guides; do not bulk-replace every receipt with ACK.
• Correct concrete policy/native capability, replay/retry, crash/conflict, identity-length, transcript/redaction and other operational term mistranslations against source.
• Resolve ambiguous canonical discovery/storage descriptions with current registry, adapter and storage-selection evidence, then align all translations without promoting experimental support.
• Preserve commands, flags, code fences, API/error/schema identifiers, numeric values, dates, historical evidence, links and prior anchors; retain aliases if translated headings change.
• Preserve the already-reviewed README corrections and each centered hero.
• Obtain user-requested Antigravity CLI Gemini 3.8 Flash translation QA over the complete changed scope; record actual model/input coverage and limitations, source hashes and corrections. Current supported identifier: gemini-3.8-flash-medium, medium effort.
• Validate documentation/i18n/source-manifest/link/anchor consistency, inspect the expanded current-head CI/code review and make no completion claim from the earlier README-only green run.

Validation and related work

The README-only revision 40864f0 already passed its Flash review, 91 documentation tests and all 43 remote checks. That is historical evidence for the smaller revision, not final validation of the operator-guide expansion. Expanded per-file audits and QA evidence will be recorded in the PR before completion is claimed.

This follows the current concrete terminology findings rather than reopening the historical scope of completed issue #279. #370 / PR #372 remain independent test-fixture work. No merge, release, installation, live target-agent activation or operational changes are authorized by this issue; explicitly requested read-only translation-review model calls are separate.

Expanded implementation and validation

PR #374 now covers 93 files, including 81 localized operator/history documents. The full audit has 153 per-file decisions with no unresolved source ambiguity. Local documentation checks pass (92 tests), generated-standalone consistency and diff checks pass, and code fences, link targets and old anchors are preserved. Source-backed omitted qualifiers and existing agent selectors/status reasons were restored rather than silently changing historical values.

Antigravity Gemini 3.8 Flash completed 18 initial, 7 correction and 3 targeted read-only translation calls; detailed scope, observed CLI versions, model checks, input hashes and post-review Codex-only small corrections are recorded in the PR. Final head: 92643d40a1b5f94d926d4aad433544e041fdd2c1. Current-head checks are now 43/43 successful, and Codex code re-review completed at the exact final head with no reported or unresolved findings; earlier README-only green checks are not substituted.

Current-head CI: https://github.com/abruption/session-peer/actions/runs/41993415553 (SUCCESS). PR #374 remains OPEN for owner review; all documentation acceptance checks above are satisfied. No merge or publication was performed. The earlier security-review metadata is not represented as a new-head security review.