abruption · Oct 14, 2026 · Oct 14, 2026 · Oct 14, 2026 · Oct 14, 2026
diff --git a/PARITY.md b/PARITY.md
@@ -2,7 +2,7 @@
 
 Updated 2026-10-14 KST. Python reference: **1.0.2**,
 [`47c2371`](https://github.com/abruption/session-peer/tree/47c23713d0a2a3c11ebde6186afd8c43489b8b65/session_peer_core).
-This matrix describes the **TS 0.3.5 source/package contract**: the 0.2.0 unified listing, safe home selection,
+This matrix describes the **TS 0.3.6 source/package contract**: the 0.2.0 unified listing, safe home selection,
 read-only doctor, text/help/positional input, Unicode 14.0.0 name matching and
 separately managed TS skill guidance (#16/#17/#18/#19/#25), the
 [0.2.1 reliability and hardening](#021-reliability-and-hardening) changes, and the
@@ -15,6 +15,12 @@ between releases, operators should also align reviewed commits; the wire does no
 verify a source commit. `referenceVersion: "1.0.2"` identifies the comparison baseline,
 not complete parity. See [VALIDATION.md](VALIDATION.md) for dated evidence.
 
+## 0.3.6 documentation patch
+
+This source/package carries the [published skill 0.2.1 guidance](#published-skill-021-adoption--2026-10-14-kst) adopted in PR #146, merge source `602cfc09b31ce8aad23e1dd9382a2448a61143f9`. All four guides use immutable skill source `0f494cabd05901c03161dc91792dcf89f8e96631`; skill metadata/full-version and Python reference remain unchanged. TS 0.3.6 adds only its explicitly reviewed finite row with the same skill 0.1.0/0.2.0/0.2.1 acceptance as public 0.3.5. Historical rows stay unchanged and unreviewed future versions remain incompatible.
+
+The patch updates package/banner/current examples and the stable release baseline to previous public 0.3.5. SSH still requires exact matching TS versions; 0.3.5 and 0.3.6 refuse each other. No native delivery behavior, platform qualification, automatic ACK/wait, retry, installation manager, skill publication or 0.4 experiment is added. Public availability must be checked in the registry; this source description is not publication evidence. Dated preparation and publication checks belong in VALIDATION.md and release notes.
+
 ## Published skill 0.2.1 adoption — 2026-10-14 KST
 
 The four guides now pin the independently published [TS skill 0.2.1 release](https://github.com/abruption/session-peer-skill/releases/tag/session-peer-ts-v0.2.1) to immutable source [`0f494cabd05901c03161dc91792dcf89f8e96631`](https://github.com/abruption/session-peer-skill/tree/0f494cabd05901c03161dc91792dcf89f8e96631/session-peer-ts). Annotated tag object `4e7df7d8f99863e86b477eacce958033d7280246` peels to that source. The complete `SKILL.md` is **13,996 raw UTF-8 bytes**, SHA-256 `8c3520f95e0d6807303be96bfa06df69887ddaf76be05f1905505d0a956820c3`. The tag, source and file identities were independently rechecked after publication; the reviewed PR head `dc303b513d9da862f2ce21d648e168fdd847ae95` and published source have identical SKILL bytes.

diff --git a/README.ja.md b/README.ja.md
@@ -15,7 +15,7 @@
 
 <!-- docs-contract: stable-release-source; package=session-peer; bin=session-peer; node=22.13+/24; python-reference=1.0.2 -->
 
-**文書・ソースのバージョン: 0.3.5。** インストール前に、選択したリリースとレジストリのメタデータを確認してください。日付付きの準備・検証記録は [VALIDATION.md](VALIDATION.md)、リリース手順は [RELEASING.md](RELEASING.md) にあります。SSH の両端には同じ TypeScript クライアントのバージョンが必要で、0.3.4 と 0.3.5 は互いの SSH 事前確認を拒否します。
+**文書・ソースのバージョン: 0.3.6。** インストール前に、選択したリリースとレジストリのメタデータを確認してください。日付付きの準備・検証記録は [VALIDATION.md](VALIDATION.md)、リリース手順は [RELEASING.md](RELEASING.md) にあります。SSH の両端には同じ TypeScript クライアントのバージョンが必要で、0.3.5 と 0.3.6 は互いの SSH 事前確認を拒否します。
 
 **実行中の Claude Code・Codex セッションを見つけ、ローカルまたは SSH でメッセージを送信します。**
 Python 不要の Node.js クライアントです。パッケージ名とコマンド名は `session-peer` です。
@@ -56,15 +56,15 @@ SSH は既存の鍵・ホスト信頼設定と両端の**同じバージョン
 `Get-Command session-peer -All` で PATH を確認してください。利用する実装を選び、
 別の管理ツールのファイルを `--force` で上書きしないでください。
 
-**0.3.5 のインストール:** npm の導入・更新例を実行する前に、レジストリで公開状況と選択したリリースを確認してください。利用できない場合は[レビュー済みソースビルド](docs/guide.ja.md#ソースからビルド)を使います。
+**0.3.6 のインストール:** npm の導入・更新例を実行する前に、レジストリで公開状況と選択したリリースを確認してください。利用できない場合は[レビュー済みソースビルド](docs/guide.ja.md#ソースからビルド)を使います。
 
 ```sh
-npm view session-peer@0.3.5 version dist.integrity
-npm install --global --ignore-scripts session-peer@0.3.5
+npm view session-peer@0.3.6 version dist.integrity
+npm install --global --ignore-scripts session-peer@0.3.6
 session-peer --version
 ```
 
-期待する出力: `session-peer 0.3.5 (typescript)`。分離インストール・ソースビルド・
+期待する出力: `session-peer 0.3.6 (typescript)`。分離インストール・ソースビルド・
 Windows・削除の手順は以下の詳細ガイドを参照してください。
 
 任意の `sp` 短縮名は 0.3.0 以降に含まれ（0.2.1 以前にはありません）、自動では有効になりません。
@@ -73,12 +73,12 @@ Windows・削除の手順は以下の詳細ガイドを参照してください
 ### Update
 
 npm で導入したクライアントは npm で更新します。タグと対象バージョンを確認してから
-正確なバージョンを指定してください。以下は古い npm 版を選択した 0.3.5 に更新する例です。
+正確なバージョンを指定してください。以下は古い npm 版を選択した 0.3.6 に更新する例です。
 CLI は更新をインストールせず、`session-peer update --check` は確認のみ行います。
 
 ```sh
 npm view session-peer dist-tags
-npm install --global --ignore-scripts session-peer@0.3.5
+npm install --global --ignore-scripts session-peer@0.3.6
 session-peer --version
 ```
 

diff --git a/README.ko.md b/README.ko.md
@@ -20,7 +20,7 @@ Python을 설치하지 않아도 Node.js에서 실행되는 TypeScript 클라이
 
 <!-- docs-contract: stable-release-source; package=session-peer; bin=session-peer; node=22.13+/24; python-reference=1.0.2 -->
 
-**문서·소스 기준 버전: 0.3.5.** 설치 전에 선택한 릴리스와 레지스트리 메타데이터를 확인하세요. 날짜별 준비·검증 기록은 [VALIDATION.md](VALIDATION.md), 릴리스 절차는 [RELEASING.md](RELEASING.md)에 있습니다. SSH 양쪽에는 같은 TypeScript 클라이언트 버전이 필요하며, 0.3.4와 0.3.5는 서로의 SSH 사전 확인을 거부합니다.
+**문서·소스 기준 버전: 0.3.6.** 설치 전에 선택한 릴리스와 레지스트리 메타데이터를 확인하세요. 날짜별 준비·검증 기록은 [VALIDATION.md](VALIDATION.md), 릴리스 절차는 [RELEASING.md](RELEASING.md)에 있습니다. SSH 양쪽에는 같은 TypeScript 클라이언트 버전이 필요하며, 0.3.5와 0.3.6는 서로의 SSH 사전 확인을 거부합니다.
 
 <a id="demo"></a>
 ## 시연
@@ -65,15 +65,15 @@ PowerShell에서는 `Get-Command session-peer -All`로 PATH(명령 검색 경로
 실행 파일을 찾는지 확인하세요. 사용할 구현을 선택하고 다른 패키지 관리자가 설치한
 파일을 `--force`로 덮어쓰지 마세요. 설치와 갱신은 사용자가 npm으로 직접 수행합니다.
 
-**0.3.5 설치:** npm 설치·업데이트 예시를 실행하기 전에 레지스트리 제공 여부와 선택한 릴리스를 확인하세요. 해당 버전이 제공되지 않으면 [검토한 소스 빌드](docs/guide.ko.md#소스에서-빌드)를 사용하세요.
+**0.3.6 설치:** npm 설치·업데이트 예시를 실행하기 전에 레지스트리 제공 여부와 선택한 릴리스를 확인하세요. 해당 버전이 제공되지 않으면 [검토한 소스 빌드](docs/guide.ko.md#소스에서-빌드)를 사용하세요.
 
 ```sh
-npm view session-peer@0.3.5 version dist.integrity
-npm install --global --ignore-scripts session-peer@0.3.5
+npm view session-peer@0.3.6 version dist.integrity
+npm install --global --ignore-scripts session-peer@0.3.6
 session-peer --version
 ```
 
-예상 결과는 `session-peer 0.3.5 (typescript)`입니다. 별도 경로에 설치하거나,
+예상 결과는 `session-peer 0.3.6 (typescript)`입니다. 별도 경로에 설치하거나,
 소스에서 빌드하거나, Windows에서 설치·제거하는 방법은 [사용자 가이드](docs/guide.ko.md#설치)를 참고하세요.
 
 선택 사항인 `sp` 단축 명령은 0.3.0 이상에 포함되며(0.2.1 이하에는 없음) 자동으로
@@ -84,13 +84,13 @@ session-peer --version
 ### 업데이트
 
 npm으로 설치한 클라이언트는 사용자가 직접 npm으로 업데이트합니다. 사용 가능한 배포 태그
-(dist-tag)와 대상 버전을 확인한 뒤 해당 버전을 지정해 설치하세요. 아래 예시는 이전 npm 설치본을 선택한 0.3.5로
+(dist-tag)와 대상 버전을 확인한 뒤 해당 버전을 지정해 설치하세요. 아래 예시는 이전 npm 설치본을 선택한 0.3.6로
 업데이트합니다. `session-peer` CLI는 업데이트를 설치하지 않습니다. `session-peer
 update --check`는 새 버전이 있는지 확인할 뿐입니다.
 
 ```sh
 npm view session-peer dist-tags
-npm install --global --ignore-scripts session-peer@0.3.5
+npm install --global --ignore-scripts session-peer@0.3.6
 session-peer --version
 ```
 

diff --git a/README.md b/README.md
@@ -15,7 +15,7 @@
 
 <!-- docs-contract: stable-release-source; package=session-peer; bin=session-peer; node=22.13+/24; python-reference=1.0.2 -->
 
-**Documentation and source version: 0.3.5.** Review the selected release and registry metadata before installation. Dated preparation and validation records are in [VALIDATION.md](VALIDATION.md); release procedures are in [RELEASING.md](RELEASING.md). SSH endpoints require the same TypeScript client version; 0.3.4 and 0.3.5 refuse each other’s SSH preflight.
+**Documentation and source version: 0.3.6.** Review the selected release and registry metadata before installation. Dated preparation and validation records are in [VALIDATION.md](VALIDATION.md); release procedures are in [RELEASING.md](RELEASING.md). SSH endpoints require the same TypeScript client version; 0.3.5 and 0.3.6 refuse each other’s SSH preflight.
 
 **Find and message running Claude Code and Codex sessions, locally or over SSH.**
 A Node.js client that runs without Python. Package and command: `session-peer`.
@@ -56,15 +56,15 @@ Check `type -a session-peer` on macOS/Linux or `Get-Command session-peer -All`
 in PowerShell before installing. Choose the intended PATH entry; do not use
 `--force` to overwrite another manager’s files.
 
-**Version 0.3.5 installation:** check registry availability and review the chosen release before running the npm install/update examples. If that version is unavailable, use the [reviewed source build](docs/guide.md#build-from-source).
+**Version 0.3.6 installation:** check registry availability and review the chosen release before running the npm install/update examples. If that version is unavailable, use the [reviewed source build](docs/guide.md#build-from-source).
 
 ```sh
-npm view session-peer@0.3.5 version dist.integrity
-npm install --global --ignore-scripts session-peer@0.3.5
+npm view session-peer@0.3.6 version dist.integrity
+npm install --global --ignore-scripts session-peer@0.3.6
 session-peer --version
 ```
 
-Expected: `session-peer 0.3.5 (typescript)`. For isolated installation, source
+Expected: `session-peer 0.3.6 (typescript)`. For isolated installation, source
 builds, Windows and removal, see the detailed guide below.
 
 Optional `sp` shorthand ships with 0.3.0 and later (not 0.2.1 or earlier) and is
@@ -74,12 +74,12 @@ never enabled automatically. See [explicit activation and collisions](docs/short
 
 Use npm for an npm-managed installation. Check the available tags and review
 the target version, then install that exact version; this example updates an
-older npm installation to the selected 0.3.5 release. The CLI does not install updates;
+older npm installation to the selected 0.3.6 release. The CLI does not install updates;
 `session-peer update --check` only reports them.
 
 ```sh
 npm view session-peer dist-tags
-npm install --global --ignore-scripts session-peer@0.3.5
+npm install --global --ignore-scripts session-peer@0.3.6
 session-peer --version
 ```
 

diff --git a/README.zh-CN.md b/README.zh-CN.md
@@ -15,7 +15,7 @@
 
 <!-- docs-contract: stable-release-source; package=session-peer; bin=session-peer; node=22.13+/24; python-reference=1.0.2 -->
 
-**文档和源码版本：0.3.5。** 安装前，请审核所选发布版本和注册表元数据。按日期记录的准备与验证结果见 [VALIDATION.md](VALIDATION.md)，发布流程见 [RELEASING.md](RELEASING.md)。SSH 两端必须使用相同的 TypeScript 客户端版本；0.3.4 与 0.3.5 会拒绝彼此的 SSH 预检。
+**文档和源码版本：0.3.6。** 安装前，请审核所选发布版本和注册表元数据。按日期记录的准备与验证结果见 [VALIDATION.md](VALIDATION.md)，发布流程见 [RELEASING.md](RELEASING.md)。SSH 两端必须使用相同的 TypeScript 客户端版本；0.3.5 与 0.3.6 会拒绝彼此的 SSH 预检。
 
 **发现正在运行的 Claude Code 和 Codex 会话，并在本机或通过 SSH 发送消息。**
 这是不需要 Python 的 Node.js 客户端。包名与命令名均为 `session-peer`。
@@ -54,15 +54,15 @@ session-peer send --to CLAUDE_PID --message '请检查 API 契约并回复。' -
 `Get-Command session-peer -All` 检查 PATH。选择所需实现，不要用 `--force`
 覆盖其他安装管理器的文件。
 
-**安装 0.3.5：** 运行 npm 安装或更新示例前，请确认注册表可用性并审核所选发布版本。如该版本不可用，请使用[已审核的源码构建](docs/guide.zh-CN.md#从源码构建)。
+**安装 0.3.6：** 运行 npm 安装或更新示例前，请确认注册表可用性并审核所选发布版本。如该版本不可用，请使用[已审核的源码构建](docs/guide.zh-CN.md#从源码构建)。
 
 ```sh
-npm view session-peer@0.3.5 version dist.integrity
-npm install --global --ignore-scripts session-peer@0.3.5
+npm view session-peer@0.3.6 version dist.integrity
+npm install --global --ignore-scripts session-peer@0.3.6
 session-peer --version
 ```
 
-预期输出：`session-peer 0.3.5 (typescript)`。隔离安装、源码构建、Windows 和
+预期输出：`session-peer 0.3.6 (typescript)`。隔离安装、源码构建、Windows 和
 卸载步骤见下方详细指南。
 
 可选的 `sp` 简写包含在 0.3.0 及更高版本中（0.2.1 及更早版本没有），不会自动启用。
@@ -71,11 +71,11 @@ session-peer --version
 ### Update
 
 使用 npm 更新由 npm 管理的安装。先检查标签并审阅目标版本，再安装指定版本。
-下面示例将旧 npm 安装更新至所选的 0.3.5。CLI 不会安装更新，`session-peer update --check` 只做检查。
+下面示例将旧 npm 安装更新至所选的 0.3.6。CLI 不会安装更新，`session-peer update --check` 只做检查。
 
 ```sh
 npm view session-peer dist-tags
-npm install --global --ignore-scripts session-peer@0.3.5
+npm install --global --ignore-scripts session-peer@0.3.6
 session-peer --version
 ```
 

diff --git a/RELEASING.md b/RELEASING.md
@@ -9,6 +9,23 @@ the historical 0.3.2 settings-read exception is recorded below. The workflow
 uses OIDC and no npm token. The protected GitHub environment requires a reviewer
 and permits deployments from `main` only.
 
+## 0.3.6 stable release procedure
+
+This patch carries PR #146's published TS skill 0.2.1 pin and multilingual guidance from main `602cfc09b31ce8aad23e1dd9382a2448a61143f9`. It preserves the skill's immutable source/hash and all historical release evidence. Package/banner/examples use 0.3.6; its finite metadata row accepts the same three profiles as public 0.3.5. Draft #106–#109, #82 and #142 remain excluded.
+
+Read-only preparation baseline on 2026-10-14 KST: latest=0.3.5, preview=0.1.0-preview.1, target 0.3.6 absent. Previous stable integrity: `sha512-EJc2B5tcruzHXiHDd7tyJjv2DBLYE7IHJiPVHBzLY9fSVasEQRdwx+ZZmiyBF8WHpQ7+pI3SO2VXwsQTgOWP+Q==`; attestation metadata https://registry.npmjs.org/-/npm/v1/attestations/session-peer@0.3.5. Recheck before staging. Historical settings-read exceptions do not carry forward.
+
+At the 2026-10-14 preparation checkpoint, the user explicitly skipped the fresh Trusted Publisher lookup for this 0.3.6 publication. The current mapping/permissions are therefore not freshly confirmed; prior stage-only evidence is historical. Pending stages and ownership were checked after npm login. The user separately skipped the web package publish-MFA policy lookup for this 0.3.6 publication; that current policy is also not freshly confirmed. GitHub environment protection and actual final npm stage 2FA approval remain required. No settings, secrets, tokens or protections were changed.
+
+1. Review/merge the release preparation and require exact merged-main CLI/release gate, Windows Node 22/24 and CodeQL success.
+2. Fresh authenticated reads verify ownership, pending stages, stage-only Trusted Publisher mapping, package publish-MFA and GitHub npm environment reviewer/main-only protections. Any unread gate remains incomplete unless the user explicitly grants a current exception; settings/protections are never bypassed.
+3. Verify exact-source reproducible packing, isolated installation/removal and every packaged Markdown document under the [artifact documentation gate](#documentation-gate-for-the-next-release). Historical and public skill pins remain intact.
+4. Obtain separate approval naming the exact merged 40-character main SHA, `session-peer@0.3.6`, `stable-stage` and eventual latest promotion to 0.3.6.
+5. Dispatch publish.yml only with that approved SHA/version/mode/confirmation. Review retained Actions bytes before protected environment approval; verify staged bytes/provenance and obtain separate final npm 2FA approval. Never retry an uncertain upload.
+6. Verify public bytes/integrity/provenance/signatures and isolated version/install/removal. Preserve preview. Append dated evidence and create the user-requested GitHub v0.3.6 tag/release against the verified publication source, with exact-version SSH and separate skill/runtime lifecycle notes. No fleet install is authorized.
+
+The historical 0.3.5 preparation and settings exceptions below apply to that completed publication only.
+
 ## 0.3.5 publication checkpoint — 2026-10-13 KST
 
 PR #144 is merged as `5409d0acd4b559c09920a63c5fd7f11fd10f5737`; its tree matches reviewed preparation `6fdf9d65fb0b62cca3801a3733af07add5fb6553`. Exact-main CLI and CodeQL runs passed. Publication has not started: artifact review found stale current-facing unmerged/candidate text, which requires a document-only correction, human merge and new exact-source/artifact approval. The dated preparation sections below retain their historical scope.