[abruption]

Summary

Closes #302. Related #232; abruption/session-peer-skill#29/#30/#33. Target milestone: v1.2.1 (planning only; no publication authorization).

Refreshes this existing PR onto protected main 4fc526f36afc65bb6ec460439eb0986c09ecc8ee; new head 9a06a6f4e79d7d96361432e18cfb2882a474005a. No duplicate PR is created. Relative to main, the change remains exactly one file: skills/session-peer/SKILL.md.

• Canonical source: https://github.com/abruption/session-peer-skill/blob/eb239fb358336d85b49bab2c80e4ea39037d1374/session-peer/SKILL.md
• Published annotated v0.3.3 tag object 95434883d8894a6d723ca41efcee4c67579e6ff6, peeled commit eb239fb358336d85b49bab2c80e4ea39037d1374, verified through GitHub API.
• Canonical Git blob 4f02688971f8a811d7a0aa9ccbae0ca40478e22d equals the local blob. Direct cmp against the canonical API bytes passes; SHA-256 15378c6d503a69d1d738ac4739182e23257aa6f2f7fd31ef3fd2fa60e692867f.
• Skill version 0.3.3, compatibility minimum 0.9.1 / full 1.0.1 and Python security recommendation 1.0.3+ remain independent of runtime/package versions.
• No locally rewritten canonical instructions, runtime version/code change, new skill release or global skill update.

Independent review and known pre-existing consumer defect

Both non-interactive source reviewers read the same immutable input SHA-256 f90b0c759a3bce6efda836b6b15934a400d811d13ef5b8d1db5efc978ff663c6 before any PR update. Claude Code 2.1.303, requested and response-confirmed claude-opus-5-5; Codex CLI 0.163.0, isolated default (actual model name unexposed). Parallel processes, no reviewer tools, tests, network or writes; both exit 0 with complete final responses and unchanged input/source hashes.

Codex found no mandatory snapshot change. Claude raised a conditional size-limit finding, which the coordinator independently reproduced:

• Existing installed_skill_metadata() returns unknown metadata for files larger than 16,384 bytes.
• Current main v0.3.2 snapshot: 16,459 bytes. New canonical v0.3.3 snapshot: 18,824 bytes.
• Actual calls return version: null and runtimeMinVersion: null for both. The new snapshot does not introduce this runtime defect, but cannot claim that the current runtime recognizes its metadata.

The owner approved a separate bounded runtime fix in v1.2.1, tracked in #318 and implementation PR #320. That exact source (3b90b7fcff5d1168a180b43394b0cc4e25e38e61) passed related tests and independent pre-PR review; direct calls recognize the real v0.3.2/v0.3.3 files. Both PRs are now available for review, not merged. Do not truncate or diverge from the released canonical skill to satisfy the reader. This documentation-only PR does not change the reader or claim that the runtime fix is published. Suggested wording changes in the canonical instructions are upstream follow-up proposals, not local edits.

Validation of this exact refreshed head

• Canonical tag/peeled commit/blob, direct byte cmp and SHA-256: pass.
• skill-creator quick validation: pass in a private validation venv with PyYAML 6.0.2. The first tool invocation lacked PyYAML; only the private tool environment was corrected. This validates frontmatter format, not runtime reader acceptance or agent behavior.
• Documentation: 62 tests pass.
• Installer/release-artifact/verified-release/client-update tests: 52 pass.
• Generated standalone --check and git diff --check: pass.
• No live send/dry-run, native model, remote delivery, installation or operational experiment was used for this one-file snapshot update.
• Current-head CI and automatic review remain separate from the source-only independent review. No review mention is needed on PR creation.

Boundaries

No merge, tag/release, package publication, TypeScript synchronization, independently managed global installation, credentials access, permission/settings change or operational/fleet update. The compatibility snapshot remains excluded from wheel/sdist by the existing package contract; a future authorized standalone release uses its exact reviewed bytes. Historical release records and the frozen handoff contract/fixture are unchanged.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-19T04:34:39.905281Z	9a06a6f	Draft marked ready
🔒 Security Review	✅ Completed 2026-10-19T04:36:05.651644Z	9a06a6f	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.