[abruption]

Refs #34. Ready for normal review after recorded exact-content acceptance; human merge/release approval remains separate. Supporting runtime publication is now verified; skill publication is still a separate gate.

Summary

• Finalize the 0.2.1 version/profile introduction against actually published TS runtime0.3.5, exact source a2057940ba19056fcaaa5551a7820f7414bd3bfa.
• Preserve public CLI feature guidance, baseline minimum0.1.0/full0.3.2 meanings, version/help/platform/native/security/permission boundaries and unknown/no-resend/ACK limits. No future0.4 features.
• Keep public0.3.2/0.3.3/0.3.4 rejection of the new profile and finite reviewed0.3.5 support; no future wildcard acceptance.
• Fix the TS review finding about release-status wording: use time-neutral selection of an actually published immutable release/source/hash, and confine temporary unpublished/preparation status and old0.2.0 pin to dated history. If the selected tag publication/source/hash cannot be verified, stop without adopting a Draft/PR/future pin. No new published pin is assigned.
• Align TS setup/compatibility guides and four README notices. Separate the published runtime from still-unreleased skill0.2.1, with installation commands using the selected verified release source; existing published pins are not mutated.
• Preserve Python canonical bytes and existing TS0.2.0 tag/source pin8482cf644507c682915e35c85aa3384c53864906.

Exact renewed bytes

Branch: docs/ts-skill-0-2-1-candidate
Head: dc303b513d9da862f2ce21d648e168fdd847ae95
Base: eb239fb358336d85b49bab2c80e4ea39037d1374

• Complete TS SKILL: 13,996 raw UTF-8 bytes, SHA-256 8c3520f95e0d6807303be96bfa06df69887ddaf76be05f1905505d0a956820c3.
• TS setup SHA-256: 89a053a50786a4802679bd88fcb96fff0706e3789739f6a2f63b5d74ecdd2de2.
• Compatibility document SHA-256: 71a82e9d687efc9e07b550368a1e7aa95d28ff2365342a0d2dafa9ad4baa83bc.
• Metadata remains0.2.1/typescript/min0.1.0/full0.3.2/probe-help.
• Unchanged Python SKILL SHA-256: 15378c6d503a69d1d738ac4739182e23257aa6f2f7fd31ef3fd2fa60e692867f.

The previous9db5420 candidate13930bytes/SHA96d5a0... received conditional design/content acceptance, recorded in this checkpoint. Its wording changed after runtime publication, so that acceptance does not automatically freeze these renewed bytes. Current head is not an installation/release pin.

Supporting runtime publication evidence

• GitHubv0.3.5 and npm latest0.3.5 checked; preview unchanged0.1.0-preview.1.
• Actual public tarball independently read and matched SHA-25646f4a01f9570034fca49cfa5fad620f3f45b5f33b1a6714f29ea0a3c1e751ac0 and registry SHA-512 integrity.
• Public SLSA payload subject/digest, resolved sourcea2057940ba19056fcaaa5551a7820f7414bd3bfa, repository/main/workflow_dispatch/.github/workflows/publish.yml and run38380726060 were read and matched. This is payload/hash/source binding review; Sigstore/signature cryptographic verification and fresh publishing-policy settings audit were not independently run here.
• Published protocol/guard source matches the previously reviewed08c507c code: compiledVERSION0.3.5, explicit0.1.0/0.2.0/0.2.1 profile row, unchanged parser/reader/envelopes. Registry tarball also contains compiledVERSION0.3.5.
• Actual runtime publication is not skill publication, user-installation permission, delivery/ACK qualification or fleet/operations update.

Validation and review limits

• Current node scripts/validate-skill.mjs --tag session-peer-ts-v0.2.1 and git diff --check: PASS; tag-rule validation only, no tag created.
• Python canonical is byte-identical to origin/main; existing feature/command instructions are preserved except the reader version list now explicitly includes0.3.5.
• Renewed full-byte static Codex/subagent review: no blockers; README4/setup/compatibility and guard-publication/skill-unreleased distinctions agree.
• Earlier9db5420 quick_validate and disposable Skills lifecycle checks passed. No local runtime install/execute/native send/ACK test was added for this wording-only update. Fresh CI reruns the repository lifecycle gate on the new head.
• Exact headdc303b513d9da862f2ce21d648e168fdd847ae95 CI2/2 PASS (skill-package, GitGuardian); automatic code/security review completed on that same head with no new reported findings. Earlier-head results are not reused.
• No external Claude Code/Antigravity CLI was used for this release-guidance task.

Remaining gates

1. TS maintainer reviews the renewed exact full bytes/profile and records acceptance or concrete remaining findings.
2. Human review/merge and separate approval for immutable skill tag/release, after current-head checks/reviews.
3. Four-language TS runtime guidance/PARITY adopt that same actually published skill pin.

No merge, tag, skill/npm publication, user-installed skill/runtime update or operations change. Python snapshot and0.4 work stay separate.

Renewed time-neutral wording review

The preceding0fcdc63 full bytes received conditional exact-content acceptance from the TS reviewer, with one final-artifact status wording finding. This new head resolves that finding. Primary and separate read-only Codex review found no further issue; exact renewed bytes have not yet been accepted by the TS maintainer. No merge/tag/release/pin promotion occurred.

Current-head automatic review amendment

The a4c1d0c code review raised one P2: active SKILL/setup reader passages did not list0.3.5. Commitdc303b5 updates only those two sentences to include the actual public version; bounded/stability-check guarantees and all limits are unchanged. This changes whole SKILL bytes/hash, so previous exact-content acceptance is historical and renewed TS review is required. Fresh current-head CI2/2 passed; renewed code/security review completed on that same head with no new reported findings. The TS review report now accepts these exact renewed bytes/profile for design/content only; this does not authorize human merge, tags, publication, installation or pin promotion.

[abruption]

Exact-candidate TS design/content review checkpoint

Correlation: STS-035-SKILL-PROFILE-REVIEW-20261013-A.

The TS project's fixed design record at 6fdf9d65fb0b62cca3801a3733af07add5fb6553 records conditional design/content acceptance of this complete candidate/profile for guard preparation. This is not final publication freeze, installation approval, or permission to merge/publish.

Independently checked:

• This PR remains OPEN/Draft at exact head 9db5420b45568dd08fc43d406dbf9ad1952f7891.
• Its complete TS SKILL is byte-identical to the runtime review fixture: 13,930 raw UTF-8 bytes, SHA-256 96d5a0d049f8a4d193703af3583b198a91079d44ae373de34e94a54e2296a4d6; strict UTF-8 decoding succeeds.
• Proposed profile remains skill0.2.1/typescript/min0.1.0/full0.3.2/probe-help. Published TS0.2.0 source pin 8482cf644507c682915e35c85aa3384c53864906 remains unchanged.
• The runtime's new exact head is OPEN/Draft, with some checks still running at observation. Previous head 08c507c success is not attributed to the new head. Local runtime test/artifact statements are the TS project's reports, not independently rerun by this documentation review.

Next gates remain actual supporting runtime publication with exact source/artifact evidence, separately approved final skill wording and renewed exact-head/full-byte review, then skill publication and synchronized runtime guidance/PARITY pin adoption. Final wording will change the candidate hash; current bytes are not an installation/release pin.

This checkpoint changes no source bytes, metadata, tags, published artifacts, installations or operations. No additional peer reply/reminder was sent.

[abruption]

Exact renewed content-contract review checkpoint

Correlation: STS-035-SKILL-GUARD-PUBLISHED-20261013-A; related STS-035-SKILL-PROFILE-REVIEW-20261013-A.

The received TS review report accepts the design/content contract for this exact head a4c1d0c2118682978b67d7691c35e0ff1c3de019, with no remaining normative findings. The report identifies renewed full-byte review and public0.3.5 bundled pure-validator/file-inspection tests; those executions are the TS reviewer's reported scope, not independently rerun here, not actual historical CLI qualification, and not live/native delivery or ACK evidence.

Independently rechecked this head and exact downloaded files:

• TS SKILL: 13,989rawUTF8bytes, SHA256 f870c294cb79e5b7117bb497aac54c535f4d12b3560ebcd9cdf2f3fdeae148e2.
• Setup SHA256 a62e23403b7e8347a44d64b9046d36b6a9656a23e5eab563eb8cd932d75f49fe.
• Compatibility SHA256 71a82e9d687efc9e07b550368a1e7aa95d28ff2365342a0d2dafa9ad4baa83bc.
• Same head CI2/2 SUCCESS. Prior candidate acceptance is not reused for a changed hash.

The final-artifact status wording finding is resolved: approved published immutable release/source/hash selection is time-neutral; temporary preparation status and old0.2.0 pin are dated history; tag-name/metadata/PR-head existence never proves publication or installation authorization.

This is recorded as design/content acceptance, not a formal GitHub approving review, joint final publication freeze, human merge/tag/release authorization, pin promotion or installation/operations permission. Future SKILL-byte changes need renewed exact-content review. Source bytes, tags and published pins are unchanged by this checkpoint.

Supporting runtime publication and exact-content review are complete, so the PR can enter normal current-head review. Human merge/release gates remain separate. No peer reply/reminder was sent for this checkpoint.

[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-13T10:49:38.929812Z	dc303b5	Draft marked ready
🔒 Security Review	✅ Completed 2026-10-13T10:51:37.129411Z	dc303b5	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.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a4c1d0c211

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[abruption]

Final current-head content/review checkpoint

Exact head dc303b513d9da862f2ce21d648e168fdd847ae95: complete TS SKILL13,996rawUTF8bytes/SHA256 8c3520f95e0d6807303be96bfa06df69887ddaf76be05f1905505d0a956820c3, setupSHA 89a053a50786a4802679bd88fcb96fff0706e3789739f6a2f63b5d74ecdd2de2, compatibilitySHA 71a82e9d687efc9e07b550368a1e7aa95d28ff2365342a0d2dafa9ad4baa83bc.

The received TS review report accepts the exact reader-amended content contract with no remaining normative findings. It reports direct public0.3.5 pure-validator/file inspection against these new bytes, while explicitly excluding installation, historical CLI qualification, instruction execution, child processes, native/model/delivery/ACK tests. These executions are the TS reviewer's reported validation, not independent runs here.

Independently observed in GitHub: same-head CI2/2 SUCCESS and automatic Code+Security Review completed. No new review findings were submitted. The previous a4c1d0c P2 was addressed by the two active reader-version sentence updates and its fix reply; no reader guarantee/limit or metadata change.

All publication-status/immutable-source and finite-profile boundaries remain. This is design/content review plus current-head automated review evidence, not formal human merge/tag/release approval or joint publication freeze. No source bytes, tags, pins, installations or operations were changed by this checkpoint. No additional peer reply/reminder was sent.

[abruption]

Released after explicit user approval: PR35 MERGED at 0f494cabd05901c03161dc91792dcf89f8e96631; annotated tag session-peer-ts-v0.2.1 and GitHub Release published.

Canonical TS SKILL13,996rawUTF8bytes/SHA256 8c3520f95e0d6807303be96bfa06df69887ddaf76be05f1905505d0a956820c3 matches the reviewed dc303b5 bytes and the public tag. Exact mainCI38490286639 and tagCI38490439448 passed; public annotated tag/source/hash verified. Python0.3.3 canonical and Latest channel unchanged.

TS maintainer follow-up for four-language runtime guidance/PARITY adoption was sent once under correlation STS-TS-SKILL-021-PUBLISHED-20261014, with queued status, not confirmed consumption. No runtime/npm republication, user-installed skills/runtime update, live/native ACK or operations change. Separate runtime pin-adoption work remains with its owning session; this companion candidate/release issue is complete.