feat(skill): prepare a finite successor profile for refreshed TS documentation #139

Current roadmap — 2026-10-13 KST

• Target milestone: 0.3.5 — TS skill profile compatibility.
• Planning priority: P1 (priority:P1).
• Dependencies/order: Companion exact metadata/fixture agreement; reviewed guard runtime publication before separate skill finalization.
• Remaining scope: Finite successor profile only; published pins stay unchanged until the approved rollout.

This section supersedes older milestone/version/priority statements below. Existing acceptance criteria, evidence limits and historical records remain applicable. Versioned milestones are provisional planning targets, not committed dates or implementation/live-test/merge/release authorization. P1 means a milestone prerequisite/current-release item; P2 a planned extension/research track; P3 later dependent work.

Scope and priority

P2 follow-up to closed #118. Public npm 0.3.4 accepts exactly skill 0.1.0 and 0.2.0. The refreshed TS instructions in companion PR #33, source eb239fb358336d85b49bab2c80e4ea39037d1374, are merged but are not a replacement publication of immutable session-peer-ts-v0.2.0.

Prepare a separately reviewed candidate documentation revision: skill 0.2.1 / implementation typescript / min 0.1.0 / full 0.3.2 / policy probe-help, supported only by a candidate runtime 0.3.5. These numbers are proposals for companion agreement, not frozen metadata or a release commitment. This ordinary documentation-profile follow-up is distinct from companion #31's unshipped 0.4 handoff guidance.

Acceptance criteria

• Agree exact successor metadata and complete fixture bytes with the skill maintainer before merge/release. Keep min/full meanings separate from finite doctor acceptance.
• Add only an explicit candidate runtime/profile row; preserve published 0.3.2/0.3.3/0.3.4 results and compiled default until a separately reviewed version preparation. Do not accept future versions via SemVer ranges.
• Cover existing and successor profiles, wrong name/implementation/min/full/policy, mixed metadata, duplicates/missing/malformed fields, runtime identity and unsupported versions. Keep unknown/incompatible/metadata_only envelopes and bounded reader protections.
• Preserve published skill pin 8482cf644507c682915e35c85aa3384c53864906; no new candidate SHA becomes an installation pin and no 0.4 features become supported through metadata.
• Publish the approved guard runtime first, under separate release approval; then separately finalize and publish the skill revision. Record immutable tag/source/file hash.
• After that publication, update four-language guides/PARITY and guidance tests to the same reviewed immutable pin. Runtime and skill updates remain separately managed; no postinstall, global install or implicit update.
• Build/types, scoped metadata/guidance tests and current-head CI/reviews pass before human merge.

Boundaries

Issue and Draft PR preparation only. No merge, tag, runtime/skill publication, installation, live delivery/ACK, operational changes or Python parity-pin changes. The current public 0.3.4 artifact remains immutable and rejects a new 0.2.1 profile. compatible is metadata inspection only, not authenticity/send permission/delivery/ACK.

Related #118, #70, and companion #31/#32/PR #33. The existing immutable TS skill 0.2.0 release remains valid for public runtime 0.3.4; a newer Python skill release does not change this TS contract.

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.

Renewed exact skill-content acceptance — 2026-10-13 KST

Companion PR35 exact head a4c1d0c2118682978b67d7691c35e0ff1c3de019: complete SKILL13989rawUTF8bytes/SHA256 f870c294cb79e5b7117bb497aac54c535f4d12b3560ebcd9cdf2f3fdeae148e2, setupSHA a62e23403b7e8347a44d64b9046d36b6a9656a23e5eab563eb8cd932d75f49fe, compatibilitySHA 71a82e9d687efc9e07b550368a1e7aa95d28ff2365342a0d2dafa9ad4baa83bc directly verified. Prior temporal artifact wording finding is resolved; verified release/source/hash selection and REVIEWED_COMMIT40 placeholder precede installation, oldhistory/locales/guards preserved.

Actual published0.3.5tarball bundled pure validator/compiled VERSION/default/undefined/explicit/outer inspect accepted the exact newfullbytes. Explicit historical/future identity rows reject; not an actualoldCLI run. Seven documents independently read; no new contract/content blocker. No install/CLI/body/childprocess/native/model/ACK execution. Acceptance of this exactnewhead/content is designonly, not reused from previoushash or usermerge/tag/skillrelease/installpin authorization. A single acceptance reply was queued to stablelive companion under STS-035-SKILL-GUARD-PUBLISHED-20261013-A; consumption not claimed.

Runtime0.3.5is already public. Remaining: human-approved companionmerge/tag/release, verified immutable publishedskill pin, then synchronizedfour-languageTSguidance/PARITYadoption. Issue remainsOPEN; publishedskill0.2.0pin stays until that authorizedpublication.

Reader-version wording exact acceptance — 2026-10-13 KST

CompanionPR35 head dc303b513d9da862f2ce21d648e168fdd847ae95: SKILL13996rawUTF8bytes/SHA256 8c3520f95e0d6807303be96bfa06df69887ddaf76be05f1905505d0a956820c3, setupSHA 89a053a50786a4802679bd88fcb96fff0706e3789739f6a2f63b5d74ecdd2de2, compatibilitySHA unchanged 71a82e9d687efc9e07b550368a1e7aa95d28ff2365342a0d2dafa9ad4baa83bc. Diffagainstaccepteda4 is exactlytwo readerverlist additions0.3.5, resolvingCodexP2. Actualpublished0.3.5 bundled purevalidator accepted exactnewfullbytes/default/undefined/explicit/outer; historical/future suppliedidentity rows reject. Extra read-only source audit confirms unchangedreader protections/limits. No remainingcontent/normativefinding; design-content only acceptance queuedonce tostablelive owner. No oldhash acceptance reuse or install/CLI/body/native/model/ACK execution.

CurrentheadCI2/2 observed. At reviewcheckpoint currentCodeReview complete, SecurityReviewrunning; no allreviewpassed/merge/publication permission claim. Humanmerge/tag/skillrelease/pinrollout remainseparate; existingpublicruntime andpins unchanged.