Repository navigation
chore(release): prepare session-peer 0.3.5 stable staging #143
Description
Scope
Prepare session-peer@0.3.5 stable staging from reviewed #139/Draft #140 finite TS skill-profile support. Preserve ordinary CLI/SSH behavior, historical platform evidence, published skill pin and Python reference. Exclude handoff, Side Session and Steer Drafts.
Acceptance
- Agree the exact companion successor profile and full candidate instruction bytes; no Draft SHA becomes a published installation pin.
- Runtime/package/lock/banner and current examples agree on0.3.5; retain explicit historical0.3.2/0.3.3/0.3.4 profile verdicts.
- Pin previousStable0.3.4 integrity and unchanged preview baseline;0.3.5 absent at preparation checkpoint.
- Build/types/full tests, package smoke, policy, audit, reproducible pack and artifact/document gates pass. Distinguish fixture/CI from native or installed-skill support.
- Open a preparation Draft PR with exact source/artifact evidence and remaining review/rollout gates.
Publication boundary
Preparation only. Human merge, exact-main CI, fresh authenticated publication settings/stages audit, exact SHA/version/stable-stage approval, protected environment and final npm2FA remain separate. No merge, dispatch, tag, GitHub Release, npm/skill publication, global/fleet install, configuration or operational change. Skill publication follows actual supporting runtime publication under separate approval. Refs #139, not Closes until its full rollout completes.
Preparation checkpoint — 2026-10-13 KST
Draft PR #144, exact head a77420918e5c9c97571c1a482d1b8a1596ca33ca: local full tests191/186PASS/0FAIL/5Windows-onlySKIP, package/repository/audit/pack/artifact/18Markdown byte checks PASS; current-head CI12/12 PASS. Dependency Draft140 remains unmerged and companion exact-profile/complete-bytes agreement remains pending. Automatic reviews have not been submitted; no approval/publication claim. Local artifact SHA256 4d196d73e6aa7d08baa350ccd02dfe8ec8f24b3ec0962ca21c90436a0c1a8776; later merged-main/Actions artifacts require independent validation.
Latest follow-up head 08c507ca1c2a3805b189ee05bfdd32b0d3d2dacb: compiled default/undefined/outer inspection now directly checks all3profiles; scoped23/23, build/types, pack/artifact/18Markdown byte comparisons and CI12/12 PASS. Current artifact SHA256 84cf6d5da3f40a09addaf16f97be66c3dd4cf40eced267e48b300f8332519d59 supersedes priora774209 bytes. Exact release-default companion review and complete0.2.1SKILL bytes/hash remain pending despite conditional profile-direction acceptance. No freeze/merge/publication.
Exact complete candidate review checkpoint — 2026-10-13 KST
Companion Draft35 exact9db5420 provides complete0.2.1SKILL13930bytes/SHA256 96d5a0d049f8a4d193703af3583b198a91079d44ae373de34e94a54e2296a4d6. TS directly verified bytes/hash, unchanged functional/safety body and pure/full-file compiled guard/outer inspection (scoped24/24PASS), and accepts this candidate profile/content for guard preparation design review only. TS Draft144 latesthead 6fdf9d65fb0b62cca3801a3733af07add5fb6553: CI12/12PASS, exact pack/artifact and18Markdown comparisons PASS; artifact SHA256 86a962405a7eb3e823df68715380367dd50517fc274612710d72965af4789387.
This is not final joint publication freeze, installpin/metadata publication, merge or release authorization. After actual guard publication, separately approved final skill wording changes bytes and needs a new exactreview; published8482cf6pin stays. Automatic reviews remain unsubmitted. Human merge/main verification and publication gates remain open. Earlier pending-source statements are checkpoint history, not claims that the complete candidate is still absent.
Pre-staging correction checkpoint — 2026-10-13 KST
#144merged to5409d0a, exactmainCI/CodeQLPASS. Its lateCodexP2 artifact-state finding requires documentation correction #145. Current correctionhead4d918dcf6c72ce351bfa0c30528886a1d99f1bc2 passes12/12CI and exactartifact docgate (57files/18Markdownmatches), SHA25646f4a01f9570034fca49cfa5fad620f3f45b5f33b1a6714f29ea0a3c1e751ac0. #145CodeReview6dd reported2P2, bothaddressed4d918; latestfreshGitHubreviewnotclaimed. Humanmerge/newexactmainverification/SHAstageapprovalpending; no dispatch orstagecreated.
Operator explicitly skipped fresh TrustedPublisher AND webpublishMFApolicy reads for this0.3.5release; no currentpolicy/mapping verification claimed. Authenticatednpmaccountmatches soleownerabruption, stageslistempty, publicpackage. GitHubnpmreviewer/mainonly/adminbypassfalse/secrets0observed. Registrylatest0.3.4/preview0.1.0-preview.1/0.3.5absent; previousstableintegrity/attestationURL/provenance sourceafed4a5+publish.ymlcontentmatch (not cryptographic verification). Actualenvironmentapproval and finalnpm2FAremainseparate.
Exact merged-main staging candidate — 2026-10-13 KST
#145 merged as a2057940ba19056fcaaa5551a7820f7414bd3bfa, tree identical to independently audited4d918dc. Exactmain CLI38375588539 and CodeQL38375587883 PASS, including Windows22/24/releasegate. Local exactmain build/types/repository/reproduciblepack/artifact/isolatedinstall-remove/18Markdowncomparisons PASS;57files, SHA256 46f4a01f9570034fca49cfa5fad620f3f45b5f33b1a6714f29ea0a3c1e751ac0, integrity sha512-EJc2B5tcruzHXiHDd7tyJjv2DBLYE7IHJiPVHBzLY9fSVasEQRdwx+ZZmiyBF8WHpQ7+pI3SO2VXwsQTgOWP+Q==. Main remainsatthisSHA. Authenticatednpmowner/stage and publicregistrypreconditionsrechecked; no pendingstage/latest0.3.4/preview0.1.0-preview.1/0.3.5absent. Publisher/MFApolicyreadsskippedbyexplicitcurrentoperatorinstructions, actualenvironment/final2FAstillrequired. No workflow dispatch/stage/tag/publication yet. Exact SHA/version/stable-stage/latest approval is next.
Public0.3.5 completed — 2026-10-13 KST
User approved exacta2057940ba19056fcaaa5551a7820f7414bd3bfa/0.3.5/stable-stage/latest and subsequent GitHubrelease plan. Dispatched once: workflow38380726060, prepare/publishSUCCESS. GitHubapprovalAPI records requirednpm environment approval byabruption. Stage6eaa19fb-94e1-4dc6-a310-b6a528f28f8f was staged/taglatest/trustedautomation; user confirmed finalnpmstageapproval.
Publicregistry latest0.3.5/preview0.1.0-preview.1. Publicrawtarball=retainedActions=reviewedlocalbytes, SHA25646f4a01f9570034fca49cfa5fad620f3f45b5f33b1a6714f29ea0a3c1e751ac0, integritysha512-EJc2B5tcruzHXiHDd7tyJjv2DBLYE7IHJiPVHBzLY9fSVasEQRdwx+ZZmiyBF8WHpQ7+pI3SO2VXwsQTgOWP+Q==. Stage metadata SHA1 matchedthearchive; user approval arrivedbefore stagedtarballdownload, so no preapproval stagedbytes download/comparison is claimed. Publicbyteequality verifiedafterward. PublicSLSASHA512subject/source/repo/publish.yml/main/event/workflowrun38380726060 tuplematches. Initiallocalprovenancechecker assumedSHA256subject; corrected to actualSHA512subject and passed. npmreleasehelperverify passed registryintegrity/latest/attestationmetadata, npm signatureaudit, exactversionisolatedpublicinstall/uninstall. All18MarkdownsourcebytecomparisonsPASS. No fleet/globalinstallation or native/model/ACKexperiment.
GitHubReleasev0.3.5 is public/nonDraft/nonprerelease/Latest; tagtargeta205794verified. No stagingretry, permissions/config/manager changes. FreshTrustedPublisher andwebpublishMFApolicyreads were explicitlyskippedfor thisrelease; actualenvironment/finalstageapproval werenot skipped and no freshpolicyconfirmationclaimed.
#139 remains OPEN for separatelyapproved finalskillwording/publication/immutablepin/guidance rollout. Publishedskill0.2.0pinunchanged. A single notification of actualguardpublication was sent/queued to discoveredlive skillowner; queued isnot consumption/approval.
Activity