Milestones
List view
Unversioned isolated #81 Side Session and #141 turn/steer research. Drafts #82/#142 remain distribution-excluded. Native version/provider/owner-generation/lifecycle/race qualification and go/no-go precede any shipping-version assignment. Fake tests and Python historical results do not establish TS native support. No implicit live-test/merge/release authorization.
No due date•0/4 issues closedProvisional long-term target: #29 current Python/TS wire/auth/scope design, then #30 device endpoints, #31 routing/enrollment, #32 backup/rotation/fenced recovery. Reuse existing hosted services where reviewed; infrastructure cloning or production operations are not implied. Scope can be revised after design; no due date or release approval.
No due datePlanning target: #24 reusable execution/capability contracts before #26 MCP, #27 explicit bounded wake and #28 registered Antigravity bridge. Ordinary local/SSH behavior preserved; opt-in packages and independent permissions/lifecycle qualification. Native input experiments remain in separate Research milestone. No release/ops approval.
No due datePlanning target after0.4.0: #132 voluntary receipt-only producer/authenticated collector bootstrap, #73 Claude privacy go/no-go research. Same-machine route first; installed trusted reverse SSH only after qualification. No transcript-derived ACK, no prompt/wake on receipt, no dedup/resend guarantee. A no-go research result is valid; no promised Claude observer.
No due datePlanning target after0.4.0: #130 Linux client-ID observation, #131 Windows private storage/native observation, #20 Windows-client typed jump, #23 current remote provisioning/recovery qualification. Independent platform evidence and no-resend guards required. No implicit deploy helper, automatic installation or automatic ACK. No due date or release authorization.
No due datePlanning target: #139 finite successor TS skill profile. Exact companion metadata/fixtures must be agreed; publish the reviewed guard runtime before separate skill publication, then immutable guidance pin. Does not authorize merge/publication or infer general future-version compatibility.
No due date•5/5 issues closedPlanning milestone for verified ordinary SSH patch corrections and published skill guidance follow-up. No release or publication authorization.
No due date•7/7 issues closedPlanning-only next patch candidate: preserve independently verified ordinary SSH submission evidence, strict bounded response parsing, accurate migration documentation, and reviewed TS-specific skill guidance/metadata compatibility. No handoff/ACK/ledger/observer implementation; the four 0.4.0 issues remain together. No date or release/publication approval is implied.
Overdue by 11 day(s)•Due by October 8, 2026•8/8 issues closedMinor release target: multi-host/constrained SSH options, sender and return-route handling, npm-aware updates, and a reviewed Python-free remote deployment/version compatibility design. #23 is a design deliverable; new provisioning implementation may require follow-up scope. Version is a planning target, not a publication approval or committed date. Audit and issue index: https://github.com/abruption/session-peer-ts/issues/33
No due date•20/22 issues closedUnversioned, design-gated TS endpoint interoperability: device identities/policy/journaling, authenticated WSS/enrollment, backup/rotation/recovery. Begin with #29; assign versions after protocol and packaging decisions. Existing Relay/control production deployment remains separate. Audit and index: https://github.com/abruption/session-peer-ts/issues/33
No due date•0/4 issues closedUnversioned follow-up scope: reusable typed execution contracts, optional MCP/plugin, bounded Codex wake and experimental Antigravity bridge. Assign release versions after runtime/protocol validation and scope review. TS-aware skill #25 is targeted to 0.2.0. Audit and index: https://github.com/abruption/session-peer-ts/issues/33
No due date