Skip to content

chore(release): prepare 0.3.5 stable staging - #144

Merged
abruption merged 4 commits into
mainfrom
abruption/release-0.3.5
Oct 13, 2026
Merged

abruption merged 4 commits into
mainfrom
abruption/release-0.3.5

Conversation

@abruption

@abruption abruption commented Oct 13, 2026 •

Copy link
Copy Markdown
Owner

Summary

Refs #143 and #139. Release preparation ready for human review. No merge, dispatch, staging, tag, release or publication.

Latest head: 6fdf9d65fb0b62cca3801a3733af07add5fb6553. This main-based candidate includes unmerged dependency PR #140 at b917769047db41dedcb4aa1367a1b89915beb000. Human review/merge of that dependency comes first, then rebase/current-head checks for this preparation.

Changes

  • Runtime/package/lock/banner and current four-language installation examples: 0.3.5.
  • Activate only the finite skill 0.2.1 / typescript / min 0.1.0 / full 0.3.2 / probe-help proposal in compiled 0.3.5; retain exact legacy 0.1.0/0.2.0 rows and explicit historical runtime verdicts. Future versions remain incompatible. Parser/reader behavior unchanged.
  • Previous stable is public 0.3.4, exact integrity sha512-O9Uwpa0x1NZ8MNZCk0a1Z4hj7S+v0F0QeOJa+rKfbwcAYzBCSMwqmEWQWZQMWM36SbxVu3RowTSvpwPiKd/BDA==; preview remains 0.1.0-preview.1. Registry read confirmed target 0.3.5 absent at preparation. This is not an authenticated publisher/stage/MFA audit.
  • Published skill 0.2.0 pin 8482cf644507c682915e35c85aa3384c53864906, SHA 00c6fc343fdbeb8f6dc1b1ee1b730f04cef71bbfb08205a7be3559202f1d8804, Python reference 1.0.2 and historical evidence stay unchanged. Dependencies/engines/exports/allowlist/workflows unchanged. Drafts 106–109/82/142 excluded.

Exact companion review

Companion Draft #35, exact source 9db5420b45568dd08fc43d406dbf9ad1952f7891, supplies complete SKILL candidate 13,930 raw UTF-8 bytes, SHA 96d5a0d049f8a4d193703af3583b198a91079d44ae373de34e94a54e2296a4d6. Setup SHA b9f34cf06840c63c1d26dd835c512ce4b6e457063d1808eb73bc7e9f5ebc70e7; compatibility SHA 495420a268841c8da6f9bc68039e65dc52cb95aba52e33ab906710826eeb2b43. API bytes/hashes and unchanged functional/safety body after the introduction were independently compared, with another read-only Codex subagent review: no blocker.

Companion accepted the release-default source/fixture amendment at TS 08c507c for design only. TS accepts these exact full candidate bytes/profile for guard-preparation design/content only, not a final joint publication freeze, adoption, install pin or release permission. Final skill wording after actual runtime publication changes the bytes and requires new exact review and separate approval. The review reply under STS-035-SKILL-PROFILE-REVIEW-20261013-A was queued once; consumption is not inferred.

Full bytes are mirrored only in test/fixtures/ts-skill-0.2.1-candidate.md, excluded from npm. Tests verify length/hash/fatal UTF-8, default/undefined/explicit 0.3.5 and outer inspectSkill acceptance, old 0.3.2/0.3.3/0.3.4 and future 0.3.6/0.4.0 rejection. Skill instructions are never executed. Metadata compatibility is not content authenticity, send permission, consumption or ACK.

Validation

Local macOS arm64, Node 24.16.0/npm 11.15.0:

  • Initial a774209 checkpoint: ci/build/types/full test 191 total / 186 PASS / 0 FAIL / 5 Windows-only SKIP, verified Python 47c23713d0a2a3c11ebde6186afd8c43489b8b65 oracle and byte-identical vendored fixture.
  • Runtime code unchanged in later test/doc follow-ups. Latest build/types and metadata/guidance 24/24 PASS. Historical focused metadata/release/updates/integration 47/47 PASS after fixing one notice-regex expectation.
  • Package smoke: reproducible pack, isolated installation/removal and bash/zsh shorthand contracts/lifecycles PASS. Repository/diff checks PASS; audit zero vulnerabilities.
  • Latest exact-source release pack/artifact PASS; two packs match, 57 files, installed banner session-peer 0.3.5 (typescript), launcher removed on uninstall. All 18 packaged Markdown files match source; test fixtures/experiments excluded.

Latest head checks: 12/12 SUCCESS, no reruns. CLI 38368924868 includes macOS/Ubuntu Node 22/24, Windows native 22/24, policy and release gate. CodeQL 38368918377, aggregate CodeQL and GitGuardian pass. No automatic Code/Security review comments, formal reviews or inline findings submitted for #140/#144 at this checkpoint; no manual mentions. CI fixtures are not live native observer/steering qualification.

Current local artifact, separate from later merged-main/Actions artifacts:

  • Source 6fdf9d65fb0b62cca3801a3733af07add5fb6553
  • SHA-256 86a962405a7eb3e823df68715380367dd50517fc274612710d72965af4789387
  • Integrity sha512-T4L9ZIx5+F9QC4cPYxMh7qSIiKAeIUF6fa+26XkiCpTWvsDRQqUgcqAMkSQQwstUvWuIWaNknp1Rk0ahRaLf9Q==
  • Filename session-peer-0.3.5.tgz

Earlier artifacts at a774209 (SHA 4d196d73…) and 08c507c (SHA 84cf6d5d…) are superseded, retained locally; their CI/local records remain checkpoint-specific.

Remaining human/publication gates

  1. Review dependency feat(skill): add a finite successor profile for refreshed TS documentation #140 and preparation chore(release): prepare 0.3.5 stable staging #144, then human merge/rebase and exact merged-main CI/CodeQL/Windows checks. Candidate-specific design/content acceptance does not authorize merge or publication.
  2. Fresh authenticated owner/pending-stage/stage-only publisher/package MFA/protected npm environment checks; previous exceptions do not carry forward. Recheck registry integrity/provenance/source and target absence.
  3. Exact SHA/0.3.5/stable-stage/latest approval, Actions artifact/document review, protected environment and final npm 2FA.
  4. Actual supporting runtime publication before separately approved final skill wording/metadata/content/tag/pin; review new final bytes and synchronize guides/PARITY only after that skill is published.

No global/fleet install, installed skill/runtime update, native/model/ACK experiment, operations/configuration change, protection bypass or publication. #139 remains open until the full rollout succeeds.

Ready-for-review transition — 2026-10-13 KST

Converted from Draft after exact complete candidate review, scoped24/24 checks and current-head12/12CI. Source/artifact unchanged. Human review/merge and publication gates still apply; no automatic merge or manual review mention.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 13, 2026 •

Copy link
Copy Markdown

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-13T08:36:58.819869Z 6fdf9d6 Draft marked ready
🔒 Security Review ✅ Completed 2026-10-13T08:38:32.456036Z 6fdf9d6 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.

@abruption
abruption merged commit 5409d0a into main Oct 13, 2026
12 checks passed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6fdf9d65fb

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

Comment thread README.md
**Documentation and source version: 0.3.4.** 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.3 and 0.3.4 refuse each other’s SSH preflight.
**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.

Version 0.3.5 is an unmerged preparation candidate, not a publication record.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Remove the unmerged label from the release artifact

Once this change is merged, the stable publication workflow runs only from main and packages README.md, so every staged or published 0.3.5 tarball will incorrectly state that its own release preparation is “unmerged.” The same claim is copied into the localized READMEs and guides, meaning the documented artifact-state check cannot pass without another source change and a newly reviewed artifact. Describe 0.3.5 as unpublished instead, or confine the pre-merge status to a dated preparation record.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant