[abruption]

Summary

Prepare the stable v1.0.2 maintenance release after the merged #200–#210 fixes. #161 remains a separate monitoring issue because its network root cause is unconfirmed.

• Bump the canonical/generated Python version to 1.0.2; no additional runtime behavior changes relative to main d33ca9b.
• Add English/Korean/Japanese/Simplified Chinese release notes, update current README and documentation links, and advance the release runbooks and candidate/translation checks.
• Document recovery approval v2 upgrade order, preserved unknown outcomes, explicit proxy configuration, Control capacity limits, and platform-specific cleanup boundaries.
• Preserve the historical RC4 20/21 ACK evidence without claiming a new live campaign. Keep bug: public Relay intermittently loses authenticated routes during RC2 multi-host validation #161 open with its external-path root cause unconfirmed.

Related: #200, #201, #202, #203, #204, #205, #206, #207, #208, #209, #210. Those fixes are already merged and their issues closed; this is release preparation only.

Type

• feat
• fix
• docs
• chore / refactor / test / perf

Checklist

• Generated source check and git diff --check
• Package version and four-language documentation agree
• Commits follow Conventional Commits
• No credentials, device state, session keys or production evidence in the diff
• Fresh installed CLI list validated against a synthetic initialized Codex home; an explicit missing database fails closed
• Live SSH / real-agent dry-run (not performed; preparation uses isolated fixtures, not the frozen legacy cc_peer.py)

Verified against

macOS arm64, Python 3.14.7, Node 22.14.0:

• Python suite: 557 tests, OK (12 skips in the default suite).
• Repeated with the built Control integration and archive checks enabled: 557 tests, OK (2 skips).
• Documentation: 10 tests pass, including four-language structure and manifest consistency.
• Control typecheck, 92 tests, runtime dependency audit (0 vulnerabilities).
• Two independent wheel/sdist builds match byte for byte at the same SOURCE_DATE_EPOCH; exact archive/private-state exclusion checks: 3 pass.
• Rebuilt twice from clean preparation commit c397dfb using its commit timestamp; both wheel and sdist hashes match again. Final release artifacts must still be rebuilt after merge.
• Wheel and sdist each installed independently into a fresh virtualenv, core first and then Relay/MCP extras: version 1.0.2, installed import path, initialized-home JSON list, missing-home refusal, pip check, Relay/device/MCP help smoke all pass.

Notes

• The optional authenticated proxy identity is not enabled by installing this package; it needs a separate operator change. Control is deployed separately from the Python CLI.
• Upgrade the recovery-committing device before generating schema-v2 approvals. Older saved recovery plans are not silently rewritten.
• The local build is candidate evidence, not the immutable publisher artifact. After this PR merges, require exact-main CI and rebuild from the final release commit.
• As checked during preparation on 2026-09-27, PyPI 1.0.2 returns 404 and no v1.0.2 remote tag exists. Recheck before publishing.
• Final user approval is still required before publication. No GitHub Release draft/tag, PyPI upload, production restart, proxy setting, device identity or fleet installation was changed.